Explanation | An internal error has been detected, and an FFDC record has been generated with the specified source id and probe id. |
Action | Please contact your IBM service representative and provide them with this error message and the associated source id and probe id. |
Explanation | Service mapping was unable to access the business-level application that it uses to call a target service because the business-level application was not available. Because the request could not be intercepted, the request was canceled. |
Action | Ensure that the business-level application is available and started. |
Explanation | The mapping services could not be parsed as it does not adhere to the mapping services schema. |
Action | Please check the mapping services adheres to the mapping services schema. |
Explanation | Service map parameter type must be a valid XSD type. |
Action | Change the type of parameter {1} to a supported XSD type. |
Explanation | Service map parameter {0} must have a valid value. |
Action | Change the value of parameter {0} to be valid. |
Explanation | The service map tried to load a resource that could not be found. |
Action | Ensure resource exists in the service map and is valid. |
Explanation | The local mapping service is not started. The local mapping service must be started to be able to intercept messages, irrelevant of whether any service map is attached. |
Action | Ensure that the local mapping service is started. |
Explanation | Service mapping was unable to access the generated enterprise application that it uses to call a target service because the generated enterprise application was not available. Because the request could not be intercepted, the request was canceled. |
Action | Ensure that the generated enterprise application is available and started. |
Explanation | WSDL file must be valid for the service map WSDL to be parsed. |
Action | Ensure the service map WSDL file is valid and that all imported schemas are available. |
Explanation | The source service WSDL file must contain the binding specified for the source service in the service map. |
Action | Ensure the binding exists in the source service WSDL file. |
Explanation | The source service WSDL file must contain the port type specified for the source service in the service map. |
Action | Ensure the port type exists for the specified binding in the source service WSDL file. |
Explanation | The local mapping service encountered an error when sending an event. The cause of the error is contained in the message. |
Action | Correct the cause of the failure to send the event message. |
Explanation | An event that was configured to include message data has been generated. However, the system policy does not permit message data to be sent in an event. |
Action | Define the WebSphere variable "SM_EVENT_POLICY_PERMIT_MESSAGE_DATA" to "TRUE" to permit message data to be included in events. |
Explanation | A service used internally by the service mapping component could not be located. As a result the service mapping component will not function correctly. |
Action | Please contact your IBM service representative and provide them with this error message. |
Explanation | Service provider local mapping services only support flow types of IN, OUT and OUT_FAULT |
Action | Please contact your IBM service representative and provide them with this error message. |
Explanation | The context token for the invocation of service {1} has already been set. |
Action | Please contact your IBM service representative and provide them with this error message. |
Explanation | The context token for the invocation of service {1} has already been deleted. |
Action | Please contact your IBM service representative and provide them with this error message. |
Explanation | The context token for the invocation of service {1} does not exist. |
Action | Please contact your IBM service representative and provide them with this error message. |
Explanation | The service mapping component intercepted a web service request to the specified address. |
Action | None. |
Explanation | The intercepted web service request matches the configuration for the specified local mapping service. |
Action | None. |
Explanation | The attached service map will process the web service request that the local mapping service intercepted. |
Action | None. |
Explanation | A service map is not attached to this local mapping service. The web service request was not processed further. |
Action | None. |
Explanation | An event point is enabled on this local mapping service and an event was emitted. A "CLIENT_PREMAP_REQUEST" event is emitted for request messages and a "CLIENT_POSTMAP_RESPONSE" event is emitted for response and fault messages. |
Action | None. |
Explanation | Service map processing of the request message has finished, and the message is sent to the specified target service. |
Action | None. |