| 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 | The service map name specified could not be found. |
| Action | Specify a existing service map name. |
| Explanation | The specified service map name is not valid. The error message lists restrictions to service map names. |
| Action | Specify a name which does not violate any of the stated restrictions. |
| Explanation | A new service map cannot be created with the same name as an existing service map. |
| Action | Choose a name which does not conflict with an existing service map. |
| Explanation | The supplied service map library file did not contain a service map file. |
| Action | Check that the service map library file contains a valid "*.srvcmap" service map file. |
| Explanation | The specified file was not a valid ".slibzip" or ".zip" file. Service map library files are ".slibzip" or ".zip" files containing a service map file. |
| Action | Specify a valid ".slibzip" or ".zip" file. |
| Explanation | The specified file could not be found |
| Action | Specify a valid file. |
| Explanation | The specified local mapping service name is not valid. The error message lists restrictions to local mapping service names. |
| Action | Specify a name which does not violate any of the stated restrictions. |
| Explanation | A new local mapping service cannot be created with the same name as an existing local mapping service. |
| Action | Choose a name which does not conflict with an existing local mapping service. |
| Explanation | The local mapping service name specified could not be found. |
| Action | Specify an existing local mapping service name. |
| Explanation | The local mapping service name specified did not have any attached service maps. |
| Action | Specify a local mapping service name that has an attached service map. |
| Explanation | The local mapping service name specified could not be found. |
| Action | Specify an existing local mapping service name to delete. Use "listLMServices" to find the name of the local mapping service that you want to delete. |
| Explanation | The local mapping service name specified could not be deleted as there is existing service map attached to the local mapping service. |
| Action | Detach the attached service map using the "detachServiceMap" command and then run the "deleteLMService" command again. |
| Explanation | Validation of the service map file inside the supplied service map library file failed. |
| Action | Check that the "*.srvcmap" service map file inside the supplied service map library file is valid. |
| Explanation | A new service map cannot be created with the same name as an existing business-level application. |
| Action | Choose a service map name which does not conflict with an existing business-level application. |
| Explanation | A new service map cannot be created with the same name as an existing WebSphere enterprise application. |
| Action | Choose a service map name which does not conflict with an existing WebSphere enterprise application. |
| Explanation | A new service map cannot be created with the same name as an existing enterprise bundle archive. |
| Action | Choose a service map name which does not conflict with an existing WebSphere enterprise bundle archive. |
| Explanation | Service map cannot be uninstalled as it doesn't exist. |
| Action | Specify an existing service map. Use "listServiceMaps" to find the name of the installed service map that you want to uninstall. |
| Explanation | The specified service map is in use so it cannot be deleted. |
| Action | Detach the service map from all local mapping services by using the "detachServiceMap" command before uninstalling. |
| Explanation | Informational message indicating that the specified service map has been uninstalled. |
| Action | No action is necessary. |
| Explanation | No service map deployment targets were detected. |
| Action | Use the optional -deploymentTargets parameter to specify the required deployment targets for the service map. |
| Explanation | The service map name specified could not be found. |
| Action | Specify an existing service map name. |
| Explanation | A local mapping service cannot have more than one attached service map at any one time. |
| Action | Detach the attached service map from local mapping service and then retry the attach command. |
| Explanation | The specified local mapping service parameter is not valid. The error message lists restrictions to local mapping service parameter values. |
| Action | Specify a value which does not violate any of the stated restrictions. |
| Explanation | The specified local mapping service parameter is not valid because it contains whitespace characters. |
| Action | Specify a value which does not violate any of the stated restrictions. |
| Explanation | A new local mapping service cannot be created with the same "targetEndpoint" as an existing local mapping service. |
| Action | Choose a "targetEndpoint" which does not conflict with an existing local mapping service. |
| Explanation | The local mapping service name specified could not be found. |
| Action | Specify an existing local mapping service name. Use "listLMServices" to find the name of the local mapping service that you want to start. |
| Explanation | Informational message indicating that the specified local mapping service was started successfully. |
| Action | No action is necessary. |
| Explanation | The local mapping service name specified could not be found. |
| Action | Specify an existing local mapping service name. Use "listLMServices" to find the name of the local mapping service that you want to stop. |
| Explanation | Informational message indicating that the specified local mapping service was stopped successfully. |
| Action | No action is necessary. |
| Explanation | The specified service map parameter is not valid. The error message lists restrictions to service map parameter values. |
| Action | Specify a value which does not violate any of the stated restrictions. |
| Explanation | Informational message indicating that the specified local mapping service has already been started. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified local mapping service has already been stopped. |
| Action | No action is necessary. |
| Explanation | A local mapping service cannot be updated with the same name as an existing local mapping service. |
| Action | Choose a name which does not conflict with an existing local mapping service. |
| Explanation | A local mapping service cannot be updated with the same "targetEndpoint" as an existing local mapping service. |
| Action | Choose a "targetEndpoint" which does not conflict with an existing local mapping service. |
| Explanation | The local mapping service could not be updated in the mapping services configuration. |
| Action | Please check that the parameters specified are valid and try the update command again. |
| Explanation | Multiple possible service map deployment targets were detected, but no deployment targets for the service map were specified. |
| Action | Use the optional "-deploymentTargets" parameter to specify the required deployment targets for the service map. |
| Explanation | Informational message indicating that the specified service map has been attached. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified local mapping service has been deleted. |
| Action | No action is necessary. |
| Explanation | The local mapping service could not be deleted in the mapping services configuration. |
| Action | Please check that the parameters specified are valid and try the delete command again. |
| Explanation | Informational message indicating that the specified service map has been detached. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified local mapping service map has been updated. |
| Action | No action is necessary. |
| Explanation | A local mapping service cannot have more than one event point at any one time. |
| Action | Delete the existing event point from local mapping service and then retry the create event point command. |
| Explanation | The specified parameter is not valid. The command description lists valid parameter values. |
| Action | Specify a parameter value which does not violate any of the stated restrictions. |
| Explanation | Informational message indicating that the specified event point was created successfully. |
| Action | No action is necessary. |
| Explanation | No event point has not been created for the local mapping service. |
| Action | Create an event point for for the local mapping service. |
| Explanation | The event point for the local mapping service is already enabled. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified event point was enabled successfully. |
| Action | No action is necessary. |
| Explanation | The event point for the local mapping service is already disabled. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified event point was disabled successfully. |
| Action | No action is necessary. |
| Explanation | Informational message indicating that the specified event point was deleted successfully. |
| Action | No action is necessary. |
| Explanation | The state of the BLA for the attached service map must be known before attempting to start a local mapping service. |
| Action | Verify that the attached service map is saved to the master configuration and that the service map BLA has a known state. |
| Explanation | To be able to start a local mapping service, the BLA for the attached service map must also be started. |
| Action | Verify that the attached service map BLA can be started and then try starting the local mapping service again. |
| Explanation | The service map specified could not be installed. |
| Action | Ensure the service map library specified is valid and contains a valid "*.srvcmap" file. |
| Explanation | The local mapping service parameter must correspond to a valid value for the target service map if it is to attach the service map. |
| Action | Specify a value which is valid for the target service map. Use the "showServiceMap" command on the target service map to see what values are valid. |
| Explanation | When there are multiple service map files in a service map library a source service map must be specified as only a single service map can be installed. |
| Action | Specify a source service map by setting the "sourceServiceMap" parameter that indicates the service map file to be installed. |
| Explanation | When there are multiple service map files in a service map library a valid source service map must be specified. |
| Action | Specify a valid source service map for the service map library. Use the "inspectServiceMapLibrary" command to find out the service map files in the service map library. |
| Explanation | The name of the target service to be overridden must reside in the service map file that is to be installed. |
| Action | Specify a valid target service name. Use the "inspectServiceMapLibrary" command to find out the target services for each service map file in the service map library. |
| Explanation | The specified service map target service endpoint URL is not valid. The error message lists restrictions to service map endpoint URLs. |
| Action | Specify a value which does not violate any of the stated restrictions. |
| Explanation | The local mapping service parameter must correspond to a valid value for the currently attached service map. |
| Action | Specify a value which is valid for the attached service map. Use the "showServiceMap" command on the attached service map to see what values are valid. |
| 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. |
| Explanation | The specified message data is provided to the service map for processing. |
| Action | None. |
| Explanation | The specified target service is selected for the request message to be sent to. |
| Action | None. |
| Explanation | No target service is selected so the request message will continue to the original intercepted service. |
| Action | None. |
| Explanation | The specified data map is being used to transform the message. |
| Action | None. |
| Explanation | The data map transformation has finished, and the transformed data is displayed. |
| Action | None. |
| Explanation | Service map processing has finished, and the message is returned to the original service client. |
| Action | None. |
| Explanation | An internal error has been detected with the specified error message. |
| Action | Please contact your IBM service representative and provide them with this error message. |
| Explanation | A validation failure has been detected in the specified service map. |
| Action | Ensure the content of the specified service map is valid. |
| Explanation | A validation failure has been detected in the specified service map. |
| Action | Ensure the specified target service in the service map file correctly references a WSDL import. |
| Explanation | A validation failure has been detected in the specified service map. |
| Action | Ensure the source service in the service map file correctly references a WSDL import. |
| Explanation | A validation failure has been detected in the specified service map. |
| Action | Ensure the operation map in the service map file correctly references a set of data map imports. |
| Explanation | The service map tried to load a resource that could not be found. |
| Action | Ensure resource {0} exists in the service map and is valid. |
| Explanation | A failure occurred during service map parsing. |
| Action | Ensure the service map is valid. |
| Explanation | The specified operation has been called but no mapping exists in the specified service map. |
| Action | Update the service map so that all required operations are mapped, then reinstall the service map. |
| Explanation | The specified message on the operation has been intercepted but no message mapping exists for it in the specified service map. |
| Action | Update the service map so that all mapped operations are defined with the necessary message mappings, then reinstall the service map. |