WebSphere Process Server messages     Operating Systems: All supported
CWSXM0054E: Key {0} not found in context store when locating correlation information for module {1}
Explanation: The key identifies the correlation information for the reply message. The key may be absent if a reply has already been received with the same ticket, or if the corresponding message has been deleted from the modules correlation destination
User Action: If the problem recurs, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM0055E: Key {0} is already present in the context store when storing correlation information for module {1}
Explanation:
User Action: If the problem recurs, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM0100E: Multiple replies have been produced for a single request flow in module {0}
Explanation: A mediation request flow has called multiple request/reply services, and more than one of the responses have produced reply messages from the response flows. Alternatively the request or response flow has produced more than one result or fault.
User Action: Return to theMediation Flow Editor in WebSphere Integration Developer and update the mediation flow so that that either the request flow is limited to making a single request/reply call or result or fault, or that only one response flow produces a reply.

 

CWSXM0102E: The operation {0} cannot be resolved.
Explanation: The named operation cannot be found for the reference that is called by the mediation flow indicating that there is an inconsistency between the various artifacts used to deploy the mediation application. This inconsistency should not occur.
User Action: Return to WebSphere Integration Developer and perform a ''clean'' then ''build'' and re-install the application.

 

CWSXM0103E: Could not locate the EJB session bean for component {0} in module {1}
Explanation: The requested EJB session bean could not be located indicating that there is an inconsistency between the various artifacts used to deploy the mediation application. This inconsistency should not occur.
User Action: Return to WebSphere Integration Developer and perform a ''clean'' then ''build'' and re-install the application.

 

CWSXM0104E: A runtime error occurred when saving context for a mediation flow in mediation component {0} in module {1}
Explanation: An error occurred when saving the context information used by a mediation flow for the given component.
User Action: Use the FFDC logs to check the validity and correct deployment of the mediation flow component.

 

CWSXM0105E: A runtime error occurred when saving context for a mediation flow in mediation component {0} in module {1}
Explanation: An error occurred when saving the context information used by a mediation flow for the given component.
User Action: Use the SystemOut and FFDC logs to determine the original failure.

 

CWSXM0106E: A runtime error occurred when receiving a response for mediation component {0} in module {1}
Explanation: An error occurred when the mediation flow component processed a response message.
User Action: Return to WebSphere Integration Developer and perform a ''clean'' then ''build'' and re-install the application. If the failure still occurs you should contact IBM support.

 

CWSXM0107E: A runtime error occurred when receiving a response for mediation component {0} in module {1}
Explanation: An error occurred when the mediation flow component processed a response message.
User Action: Return to WebSphere Integration Developer and perform a ''clean'' then ''build'' and re-install the application. If the failure still occurs you should contact IBM support.

 

CWSXM0108E: A runtime error occurred when creating an outbound message in mediation component {0} and module {1}
Explanation: An error occurred when the mediation flow component was creating an outbound message.
User Action: Return to WebSphere Integration Developer and perform a ''clean'' then ''build'' and re-install the application. If the failure still occurs you should contact IBM support.

 

CWSXM0109E: Multiple connections to reference {0} in mediation component {1} and module {2}
Explanation: The reference is connected to multiple services but only a single service can be connected to a reference in a mediation flow.
User Action: Return to WebSphere Integration Developer and edit the mediation module so that each reference on the component is wired to a single import. After making any wiring updates, re-build, and re-install the mediation module application.

 

CWSXM0110E: Service runtime exception calling a Java component implementing a custom primitive in mediation component {0} in module {1}: {2}
Explanation: An exception occurred when calling the Java component implementing a custom primitive. This error can be generated when calling either a v6.0.1 style custom mediation primitive that is implemented by a SCA component, or when calling a ServiceInvoke mediation primitive. The error occurs because a runtime exception has been returned from either the SCA component, or from the called service, indicating that the SCA component or service has encountered an error condition that is not declared on the interface that it provides.
User Action: Check the validity of the deployed custom mediation component by using the SystemOut or the FFDC logs to determine the cause of the error.

 

CWSXM0111E: Service runtime exception calling an import from mediation component {0} in module {1}: {2}
Explanation: An exception occurred when calling an import from the mediation flow.
User Action: Check the availability of the service referred to by the import by using the SystemOut or the FFDC logs to determine the cause of the error.

 

CWSXM0112E: Dynamic endpoint selection is disabled and there are no wired connections to reference {0} in mediation component {1} and module {2}
Explanation: The reference is not connected to any import and the use of dynamic endpoint address selection is disabled. A Callout or a Service Invoke primitive has a property ''Use dynamic endpoint if set in the message header''. If this property is not checked, then the associated reference on the mediation flow component must be wired to an import. This import then defines the endpoint. If the reference is not wired to an import, then there is no way that any service can be called, since no endpoint for the service has been specified.
User Action: Use the mediation flow editor in WebSphere Integration Developer to update the properties of the Callout or Service Invoke mediation primitive associated with the given reference to check ''Use dynamic endpoint...'', or use the WebSphere Integration Developer assembly diagram to wire the reference to an import.

 

CWSXM0200E: Could not locate the mediation flow for component {0} in module {1}
Explanation: The requested mediation flow session bean could not be located.
User Action: Return to WebSphere Integration Developer and run ''clean'', ''build'' and then re-install the application. If the failure recurs you should call IBM Support.

 

CWSXM0201E: Exception returned by mediation flow for component {0} in module {1}
Explanation: The mediation flow returned an exception that was not handled by the mediation flow. An exception may be returned if the mediation primitive does not define a failure terminal, or the failure terminal is not wired.
User Action: Use the WebSphere Integration Developer mediation flow editor to check that all failure terminals on the mediation primitives, in the flow, are wired.

 

CWSXM0202E: An unexpected exception occurred when processing mediation flow for component {0} in module {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem recurs, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM0203E: An unexpected exception occurred when accessing the persistent store for component {0} in module {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem recurs, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM0204E: A configuration error occurred when calling a mediation flow.
Explanation: A previous error may indicate that a primitive in the flow did not obtain a required resource.
User Action: Use the FFDC logs to determine more details of the cause of the configuration error.

 

CWSXM0205E: An unexpected business logic exception occurred.
Explanation: The mediation flow returned an exception that indicated that a business logic error occurred.
User Action: Use the FFDC logs to determine details of the business logic error.

 

CWSXM0206E: An unexpected exception occurred.
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem recurs, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM1000E: Could not locate runtime mediation flow for mediation component {0} in module {1}
Explanation: No runtime mediation flow definitions were found for the mediation component.
User Action: Check the mediation component has a mediation flow defined and check for any earlier errors in loading the definition.return to WebSphere Integration Developer and ensure all artifcats have been correctly created.

 

CWSXM1001E: No request flow found for operation {0} on port type {1}. In mediation component {2} in module {3}
Explanation: The request flow for the operation could not be found by the flow engine. This could be because no request flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
User Action: Return to WebSphere Integration Developer and create a request flow for the operation.

 

CWSXM1002E: No response flow found for operation {0} on reference {1}. In mediation component {2} in module {3}
Explanation: The response flow for the operation called on the reference could not be found by the flow engine. This could be because no response flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
User Action: Check that the mediation component has a response flow defined for the operation and check for any earlier errors in loading the response flow. Return to WebSphere Integration Developer and create a response flow for the operation.

 

CWSXM1003E: No response fault flow found for fault message {0} from operation {1} on reference {2}. In mediation component {3} in module {4}
Explanation: The response flow for the operation called on the reference could not be found by the flow engine. This could be because no response flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
User Action: Check that the mediation component has a response fault flow defined for the fault message and operation and check for any earlier errors in loading the response fault flow. Return to WebSphere Integration Developer and wire the relevent fail terminal on the response flow.

 

CWSXM1004E: An invalid input is specified for a flow. In mediation component {0} in module {1}
Explanation: The flow has an invalid or unknown input.
User Action: Return to WebSphere Integration Developer and open the mediation module and ensure that the initial node in the Request and response flow is valid. You can find a valid list of nodes in the Information Center.

 

CWSXM1005E: Error whilst creating mediation primitive {0}. In mediation component {1} in module {2}
Explanation: The mediation primitive could not be created.
User Action: Validate the mediation flow definition, and check for additional errors.

 

CWSXM1006E: Error whilst setting properties of mediation primitive {0}. In mediation component {1} in module {2}
Explanation: An error occurred whilst trying to set the properties of the mediation primitive.
User Action: Check that the correct properties are defined for the mediation primitive in the mediation flow definition. Return to WebSphere Integration Developer and set a valid value in the stated mediation primitive.

 

CWSXM1007E: Mediation primitive {0} in mediation component {1} in module {2} encountered a problem during initialization.
Explanation: During the primitives initialization, the named mediation primitive encountered an error.
User Action: Check the configuration of the mediation primitive in the mediation flow definition and check additional errors for more information.

 

CWSXM1008E: Key of type {0} is not of expected type.
Explanation: The key class is not of the expected type for this flow engine.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM1009E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
Explanation: There was a problem in locating the runtime instance of the mediation flow.
User Action: Return to WebSphere Integration Developer and fix any issues in the Application and then attempt to redeploy.

 

CWSXM1010E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
Explanation: There was a problem in locating the runtime instance of the mediation flow.
User Action: Return to WebSphere Integration Developer, resolve the reported issues, clean the project and then re-deploy.

 

CWSXM1011E: A runtime error occurred calling the request flow for operation {0}, on port type {1}. In mediation component {2} in module {3}
Explanation: An error occurred when calling the request flow for the operation.
User Action: Return to WebSphere Integration Developer, resolve the reported issues, clean the project and then re-deploy.

 

CWSXM1012E: A runtime error occurred calling the response flow for operation {0} on reference {1}. In mediation component {2} in module {3}
Explanation: An error occurred when calling the response flow for the operation on the named reference.
User Action: Return to WebSphere Integration Developer, resolve the reported issues, clean the project and then re-deploy.

 

CWSXM1013E: A runtime error occurred calling the response fault flow for fault message {0} and operation {1} on reference {2}. In mediation component {3} in module {4}
Explanation: An error occurred when calling the fault response flow for the fault message and operation on the named reference.
User Action: Return to WebSphere Integration Developer, resolve the reported issues, clean the project and then re-deploy.

 

CWSXM1016E: The reference {0} for custom mediation {1} is undefined.
Explanation: The reference for the custom mediation is not defined on the mediation component.
User Action: The reference being used by the custom mediation is not available. Return ti WQebSphere Integration Developer and ensure the custom mediation is configured to use a valid reference.

 

CWSXM1017E: Request flow runtime instance is unavailable.
Explanation: The request flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User Action: Check the validity of the mediation flow component, and check for previous errors by returning to WebSphere Integration Developer and checking in SystemOut.

 

CWSXM1018E: Response flow runtime instance is unavailable.
Explanation: The response flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User Action: Check the validity of the mediation flow component, and check for previous errors by returning to WebSphere Integration Developer and checking in SystemOut.

 

CWSXM1019E: Response fault flow runtime instance is unavailable.
Explanation: The response fault flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User Action: Check the validity of the mediation flow component, and check for previous errors by returning to WebSphere Integration Developer and checking in SystemOut.

 

CWSXM1020E: An unknown exception occurred during the processing of mediation primitive {0}: {1}
Explanation: The fail terminal of mediation primitive is not wired causing an exception during processing.
User Action: Return to WebSphere Integration Developer and wire the fail terminal of the primitive, or correct the logic so the primitive does not throw the exception.

 

CWSXM1021E: Mediation primitive {1} attempted to obtain input terminal named {0} which does not exist
Explanation: No input terminal named {0} is defined defined for mediation primitive {1}.
User Action: If the primitive is a WebSphere Enterprise Service Bus built-in primitive (a list can be found in the Information Center) then the flow has become corrupted. Regenerate the flow in Websphere Integration Developer. If the primitive is a customer defined primitive then the problem can occur if the primitive calls the Mediation Service getInputTerminal with an invalid value.

 

CWSXM1022E: Mediation primitive {1} attempted to obtain output terminal named {0} which does not exist.
Explanation: The output terminal named {0} is not defined for mediation flow {1}.
User Action: If the primitive is a WebSphere Enterprise Service Bus built-in primitive (a list can be found in the Information Center) then the flow has become corrupted. Regenerate the flow in Websphere Integration Developer. If the primitive is a customer defined primitive then the problem can occur if the primitive calls the Mediation Service getOutputTerminal with an invalid value.

 

CWSXM1023E: Exception when calling flow action: {0}
Explanation:
User Action: Check the log for previous errors to determine the underlying issue.

 

CWSXM1024E: The reference {0} for callout {1} is undefined.
Explanation:
User Action: Return to WebSphere integration Developer and correct the references for the mediation modules.

 

CWSXM1025E: An unexpected exception occurred when the flow was called: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM1026E: Null is an invalid argument for a datasource JNDI name.
Explanation: A mediation primitive tried to locate a datasource with a null JNDI name.
User Action: Return to WebSphere Integration Developer and ensure that any primitives referencing a JNDI value is valid.

 

CWSXM1027E: An exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
Explanation: The datasource with the JNDI name ''{0}'' could not be located.
User Action: Ensure that the JNDI service is available and an appropriate datasource has been configured. Use the Administrative Console to check that the system configuration exists.

 

CWSXM1028E: A class cast exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
Explanation: The object with the JNDI name ''{0}'' was not of type DataSource.
User Action: Ensure that the object bound into JNDI is a DataSource. Use the Administrative Console to check that the system configuration exists.

 

CWSXM1032E: Reference {0} for custom mediation {1} does not define an operation named {2}
Explanation: There is no operation of the specified name defined on the reference for the custom mediation.
User Action: Return to WebSphere Integration Developer and ensure that the reference of the customer mediation exists on the mediation module.

 

CWSXM1033E: Reference {0} for custom mediation {1} defines a one-way interface when only two-way interfaces are allowed.
Explanation: Custom mediations may only define a two-way interface.
User Action: Return to WebSphere Integration Developer and ensure that the reference of the customer mediation exists on the mediation module.

 

CWSXM1034E: Mediation primitive {0} in mediation flow {1} did not initialize.
Explanation: The mediation primitive threw an exception during its initialization meaning the flow will be unavailable.
User Action: Check the configuration of the mediation primitive, and the value of any module properties it uses. Also check the FFDC log file for any exceptions generated by the primitive.

 

CWSXM1035E: Mediation flow {0} in mediation component {1} in module {2} could not be build and will be unavailable.
Explanation: An exception occurred during the building of the mediation flow which will render it unavailable for calling.
User Action: Check the FFDC log file for any exceptions arising from the building of the flow, and check the flow configuration and values of any module properties used within the flow.

 

CWSXM1036E: Custom mediation {0} contains an invalid root property value of {1}
Explanation: The root property of the custom mediation is invalid. It must be either ''/'' or ''/body''
User Action: Modify the root property within the tooling to be either ''/'' or ''/body''

 

CWSXM1037E: Custom mediation {0} does not specify a root property value
Explanation: The root property of the custom mediation is not specified.
User Action: Use the tooling to set the root property for the custom mediation.

 

CWSXM1038E: Input node {0} of request flow for component {1} in module {2} is not wired to any other node.
Explanation: The input node of the request flow is not wired to any other node in the flow.
User Action: Use the tooling to wire the input node of the request flow to another node.

 

CWSXM1039E: Input node {0} of response flow for component {1} in module {2} is not wired to any other node in the flow.
Explanation:
User Action: Use the tooling to wire the input node of the response flow to another node.

 

CWSXM1040E: Input node {0} of fault flow for component {1} in module {2} is not wired to any other node in the flow.
Explanation: The input node of the fault flow must be wired to another node in the flow.
User Action: Use the tooling to wire the input node of the fault flow to another node.

 

CWSXM1041E: Exception calling custom mediation: {0}
Explanation: The nested exception occurred when calling a custom mediation.
User Action: Inspect the nested exception in the log file generated from your custom code.

 

CWSXM1042E: A runtime flow associated with mediation primitive {0} in mediation component {1} in module {2} could not be built and will be unavailable.
Explanation: An exception occurred during the building of the mediation flow which will render it unavailable for calling.
User Action: Check the FFDC log files for any exceptions arising from the building of the flow, and, in WebSphere integration Developer, check the flow configuration and values of any module properties used within the flow.

 

CWSXM1043E: A runtime error occurred calling an event flow produced from mediation primitive {0} for operation {1}, on port type {2}. In mediation component {3} in module {4}
Explanation: An error occurred when calling an event flow for the operation.
User Action: Contact IBM Support.

 

CWSXM1044E: Event flow runtime instance is unavailable.
Explanation: An event flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User Action: Contact IBM Support.

 

CWSXM1045E: No event flow found for event {0} in request flow for operation {1} on port type {2}. In mediation component {3} in module {4}
Explanation: The event flow related to the request flow could not be found by the flow engine. This could be because no event flow is defined for this event in the request flow, or because of an earlier problem in loading the mediation flow.
User Action: Contact IBM Support.

 

CWSXM1046E: No event flow found for event {0} in response flow for operation {1} on reference {2}. In mediation component {3} in module {4}
Explanation: The event flow related to the response flow could not be found by the flow engine. This could be because no event flow is defined for this event in the response flow, or because of an earlier problem in loading the mediation flow.
User Action: Contact IBM Support.

 

CWSXM1047E: No event fault flow found for event {0} in response fault flow for for fault message {1} from operation {2} on reference {3}. In mediation component {4} in module {5}
Explanation: The event flow related to the response fault flow could not be found by the flow engine. This could be because no event flow is defined for this event in the response fault flow, or because of an earlier problem in loading the mediation flow.
User Action: Contact IBM Support.

 

CWSXM1048E: Policy resolution primitive {0} is not permitted inside an aggregation. In mediation component {1} in module {2}
Explanation: A policy resolution primitive has been detected on a branch of the flow between a Fan Out and a Fan In mediation primitive. This configuration is not permitted.
User Action: Return to WebSphere Integration Developer, open the mediation module and remove the policy resolution primitive from the aggregation branch.

 

CWSXM1049E: Subflow runtime instance is unavailable.
Explanation: The subflow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User Action: Check the validity of the mediation flow component, and check for previous errors by returning to WebSphere Integration Developer and checking in SystemOut.

 

CWSXM1050E: No model found for subflow {0} associated with subflow mediation primitive {1} in {2} operation {3} in module {4} and component {5}.
Explanation: The subflow could not be found by the flow engine. This could be because of an earlier problem in loading the mediation flow.
User Action: Use the SystemOut and FFDC logs to determine the original failure.

 

CWSXM1051E: The subflow reference {1} used by service invoke primitive {0} in mediation flow component {2} in module {3} does not have a value.
Explanation: The given service invoke primitive is using a reference defined on the subflow that has not been mapped to a reference on the mediation flow component.
User Action: Return to WebSphere Integration Developer, open the mediation module and ensure that the subflow reference is mapped to a reference on the mediation flow component.

 

CWSXM2003E: The contents of ''{0}'' in the ServiceMessageObject did not meet their constraints because of {1}.
Explanation: During validation of a ServiceMessageObject, the contents of the message were found to be inconsistent with constraints. For example, a value might be out of bounds, or a required attribute might be unset.
User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect. You may be able to disable message validation in order to ignore this condition.

 

CWSXM2004E: The ServiceMessageObject body was not of expected type ''{0}''
Explanation: The body of a ServiceMessageObject was not of the expected type. This message usually refers to SMO validation in a mediation primitive, which compares the SMO to a type specified on one of the primitive''s terminals.
User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect, or correct the expected type.

 

CWSXM2005E: The ServiceMessageObject body was not set.
Explanation: A ServiceMessageObject was found to have no body, but validation required the SMO body to be set.
User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect.

 

CWSXM2006E: Malformed QName: ''{0}''
Explanation: The system encountered an expanded QName which was not of correct format
User Action: If the malformed QName is contained within a user message, then determine why the message contains a badly formatted QName.

 

CWSXM2007E: Error: multiple type or message definitions for {0}
Explanation: There is a WSDL Message definition with the same name (namespace and local part) as an XSD type definition.
User Action: Return to WebSphere Integration Developer and modify the referenced WSDL message definition so that multiple objects do not share the same name.

 

CWSXM2008E: No wired connections to reference {0} and the service message object does not contain a target endpoint.
Explanation: The reference is not connected to any import and a target endpoint was not provided in the service message object. When a reference on a mediation flow component is not wired to any import, then the logic in the mediation flow must set in the ServiceMessageObject (SMO) header the endpoint to be used for invoking the service. This must be set in the SMO prior to calling the Callout node or Service Invoke mediation primitive by the mediation flow. The logic of the mediation flow must ensure that the target endpoint is set. Since the reference is not wired to an import, there is no way that any service can be invoked, since the endpoint for the service has not been specified.
User Action: Use the WebSphere Integration Developer mediation flow editor to inspect the logic in the mediation flow to ensure that all paths to the Callout or Service Invoke primitive have the function to set the target endpoint in the ServiceMessageObject.

 

CWSXM2009E: The dynamic endpoint {0} specified in the service message object was not found when calling reference {1}
Explanation: The dynamic endpoint address specified in the service message object was not found. This error is reported when the dynamic endpoint that was set in the ServiceMessageObject header does not contain an endpoint address that can be used by the runtime to locate a service that can be called.
User Action: Inspect the dynamic endpoint insert contained in the message and verify that it has the correct format for a dynamic endpoint using the required bindings. The format of the endpoint may represent an endpoint with either a SCA or a Web Service binding. If the format is incorrect, use the WebSphere Integration Developer mediation flow editor to determine the source of the endpoint definition, and correct the problem in the format. If the format of the endpoint is correct, and the endpoint specifies SCA bindings, then also verify that the SCA endpoint itself has been deployed to the server.

 

CWSXM2010I: Service Calling failed with a timeout
Explanation: The service calling failed with a timeout which caused the timeout terminal to be fired
User Action: No action required.

 

CWSXM3000E: {0} is not a valid value for property ''{1}''. This has been reported by the following entity: {2}
Explanation: A setter method on a mediation primitive has been called with a value which is not allowed. Usually this means that the mediation configuration is not correct.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and correct the configuration of the mediation primitive.

 

CWSXM3001E: Property ''{0}'' is not set. This has been reported by the following entity: {1}
Explanation: The mediation primitives configuration is missing a required property. Usually this means that the mediation configuration is not correct.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and correct the configuration of the mediation primitive.

 

CWSXM3002E: MediationServices object not set. This has been reported by the following entity: {0}
Explanation: The mediation primitives configuration was incomplete.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and correct the configuration of the mediation primitive. If the problem persists you should contact IBM Support.

 

CWSXM3003E: Input message is null. This has been reported by the following entity: {0}
Explanation: A mediation primitive was called without a message to mediate.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3004E: Mediation parameter is null for property ''{0}''. This has been reported by the following entity: {1}
Explanation: A setter method on a mediation primitive has been called with a null value. A null value is not valid for the named property. Usually this means that the mediation configuration is not correct.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and correct the configuration of the mediation primitive.

 

CWSXM3005E: SCAServices object not set. This has been reported by the following entity: {0}
Explanation: The mediation primitives configuration was incomplete.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and check that the configuration of the mediation primitive and mediation flow is valid. If the problem persists you should contact IBM Support.

 

CWSXM3006E: RuntimeServices object not set. This has been reported by the following entity: {0}
Explanation: The mediation primitives configuration was incomplete.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and check that the configuration of the mediation primitive and mediation flow is valid. If the problem persists you should contact IBM Support.

 

CWSXM3007E: The mediation primitive was called with a message which was not a ServiceMessageObject. This has been reported by the following entity: {0}
Explanation: The mediation primitive attempted to mediate a message which was not a ServiceMessageObject. This is not allowed.This problem can occur if a transform to a non-ServiceMessageObject structure has occured in a previous primitive.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and check that the configuration of the mediation primitive and mediation flow is valid.

 

CWSXM3008E: The StockQuote sample released with v6.0 of this product is no longer supported. Please upgrade the StockQuote sample, and any projects based upon it, to the version shipped with v6.0.1.1 or later. This has been reported by the following entity: {0}
Explanation: The v6.0 StockQuote sample should be replaced with later versions of the sample.
User Action: Upgrade the version of the StockQuote sample. If this message is issued while running a user Mediation Module which was based on the StockQuote sample, it may be necessary to reconstruct the user application based on the updated version of the sample.

 

CWSXM3009E: SIBXServices object not set. This has been reported by the following entity: {0}
Explanation: The mediation primitives configuration was incomplete.
User Action: Return to the Mediation Flow Editor in WebSphere Integration Developer and check that the configuration of the mediation primitive and mediation flow is valid. If the problem persists you should contact IBM Support.

 

CWSXM3100E: Root property evaluated to null. This has been reported by the following entity: {0}
Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. This suggests that the value is not set.
User Action: Return to WebSphere Integration Developer and ensure that the configuration of the Root property is set to a valid value.

 

CWSXM3101E: Root property evaluated to multiple elements which is not allowed. This has been reported by the following entity: {0}
Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. However, in the message being mediated, it evaluated to multiple elements.
User Action: Return to WebSphere Integration Devleoper and correct the Root property.

 

CWSXM3102E: Root property evaluated to a {0}. This has been reported by the following entity: {1}
Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. It must not evaluate to a collection of DataObjects or to a value other than a single DataObject.
User Action: Return to WebSphere Integration Developer and correct the Root property.

 

CWSXM3103E: Exception while evaluating the Root property. This has been reported by the following entity: {0}
Explanation: An Exception was caught while XSLTransform was evaluating the Root, prior to transformation.
User Action: Refer to the FFDC log to diagnose the problem. If the problem persists you should contact IBM Support.

 

CWSXM3104E: Exception while generating XML prior to transformation. This has been reported by the following entity: {0}
Explanation: The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation.
User Action: Refer to the FFDC log and look for the previous error to identify the underlying problem.

 

CWSXM3105E: Exception during transformation. This has been reported by the following entity: {0}
Explanation:
User Action: Refer to the FFDC log and return to WebSphere Integration Developer and correct the XSLT style sheet.

 

CWSXM3106E: Exception while parsing transformed XML: {0}. This has been reported by the following entity: {1}
Explanation: The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject.
User Action: Use the nested Exception to diagnose the problem.

 

CWSXM3107E: Exception while setting the transformed DataObject back into the root location. This has been reported by the following entity: {0}
Explanation: The XSL transformation completed successfully, but the transformed DataObject could not be set into the root position in the ServiceMessageObject.
User Action: Refer to the FFDC log to diagnose the problem. If the problme persists you should contact IBM Support.

 

CWSXM3108E: XSLTransform primitive could not find or load the resource ''{0}''. This has been reported by the following entity: {1}
Explanation: The XSLTransform primitive tried to load the named resource (which is likely to be a stylesheet), which was not found at runtime.
User Action: This often relates to the XSLT property. If so, return to WebSphere Integration Developer and correct the XSLT property, or make the appropriate stylesheet available. If it relates to a stylesheet or other XML resource loaded during the transformation, correct the definition or make the resource available.

 

CWSXM3109E: Unexpected Exception while initializing the XSL transformation engine. This has been reported by the following entity: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3110E: Exception while initializing the XSL transformation engine with stylesheet ''{0}''. This has been reported by the following entity: {1}
Explanation: An Exception occured while initializing the XSL transformation engine. This usually indicates a syntax or other error relating to the source stylesheet.
User Action: Return to WebSphere Integration Developer and correct the XSLT style sheet.

 

CWSXM3111E: XSL transformation file not specified for {0}. This has been reported by the following entity: {1}
Explanation: The mediation primitives configuration does not specify the XSL transformation file to use.
User Action: Return to WebSphere Integration Developer and correct the configuration of the mediation primitive.

 

CWSXM3112E: Message {1} in namespace {0} could not be found. This has been reported by the following entity: {2}
Explanation: The mediation primitive configuration specified a WSDL message definition which was not found.
User Action: Return to WebSphere Integration Developer and ensure the WSDL defining the message is available, or correct the mediation flow

 

CWSXM3113E: Unexpected element ''{0}'' encountered as child of SMO body. This has been reported by the following entity: {1}
Explanation: The XSLTransform primitive encountered an unexpected element in XML, in either the input or output of the transformation
User Action: Return to WebSphere Integration Developer and ensure the input to the primitive, and the stylesheet, are correct

 

CWSXM3114E: Unexpected repetition of element ''{0}'' in SMO body. This has been reported by the following entity: {1}
Explanation: The XSLTransform primitive encountered an element too many times in XML, in either the input or output of the transformation
User Action: Return to WebSphere Integration Developer and ensure the input to the primitive, and the stylesheet, are correct

 

CWSXM3115E: Undefined namespace prefix ''{0}'' encountered in XML. This has been reported by the following entity: {1}
Explanation: The XSLTransform primitive encountered an undefined namespace prefix, either in the input or output XML
User Action: Return to WebSphere Integration Developer and ensure the input to the primitive, and the stylesheet, are correct

 

CWSXM3116E: SMO body has type {0}; expected {1}. This has been reported by the following entity: {2}
Explanation: The XML representation of the SMO, either before or after the transformation, includes an xsi:type attribute on body. This did not have the expected value.
User Action: Return to WebSphere Integration Developer and ensure the input to the primitive, and the stylesheet, are correct

 

CWSXM3117E: XSLTransform primitive encounted ''{0}'', which is a malformed URI
Explanation: Either during initialization or while executing the transform, the XSLTransform primitive tried to use the given, malformed, URI
User Action: Return to WebSphere Integration Developer and correct the malformed URI

 

CWSXM3150E: Mediation primitive {2} in module {1} was unable to connect to the database using datasource {0}: {3}. This has been reported by the following entity: {4}
Explanation: Unable to obtain a connection to the database.
User Action: Use the Administrative console to ensure that the database is available for connection and any authentication settings have been configured.

 

CWSXM3151E: Database schema is invalid for the mediation primitive {0} in module {1}: {2}. This has been reported by the following entity: {3}
Explanation: The database schema is invalid for the named mediation primitive.
User Action: Ensure that the database schema conforms to the IBM supplied schema. Please refer to the Information Center to locate the schema.

 

CWSXM3152E: Mediation primitive {1} in module {0} was unable to access the database to store the message. This may be due to the database being unavailable, incorrect access rights or invalid database schema: {2}. This has been reported by the following entity: {3}
Explanation: Unable to access the database to store the message.
User Action: Use the Administrative Console to ensure that the correct access rights have been set and that the database is available. Refer to the Information Center to chekc that the schema conforms to the IBM supplied schema.

 

CWSXM3153E: Mediation primitive {1} in module {0} was unable to serialize the message information as an XML document: {2}. This has been reported by the following entity: {3}
Explanation: The most likely cause of this error is that a prior transform has converted the message into a valid format.
User Action: Use the WebSphere Integration Developer debug feature to view the value sent to the primitive.

 

CWSXM3154E: Mediation primitive {1} in module {0} was unable to store the message within the configured transaction: {2}. This has been reported by the following entity: {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3156E: A problem occurred obtaining the JNDI InitialContext in mediation primitive {1} in module {0}: {2}. This has been reported by the following entity: {3}
Explanation: A problem occurred obtaining the JNDI InitialContext.
User Action: Ensure that the JNDI service is available. A previous error will have ben reported in the log files which will provide yoiu with more information. Refer to the problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3157E: A class cast exception occurred in mediation primitive {2} in module {1} when attempting to obtain a String from JNDI with the name {0}: {3}. This has been reported by the following entity: {4}
Explanation: The object with the JNDI name was not of type String.
User Action: Ensure that the object bound into JNDI is a String. See the problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3158W: The format of service message objects (SMO) that is shown in the Message Logger output is deprecated. This has been reported by the following entity: {0}
Explanation: The SMO format is valid but is deprecated.
User Action: This is a warning message only. To update applications to use and accept the latest SMO format, refer to the WebSphere Enterprise Service Bus information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.

 

CWSXM3159W: The way in which the schema qualifier value is specified is deprecated. This has been reported by the following entity: {0}
Explanation: Schema qualifier values are no longer String objects bound into the Java Naming and Directory Interface (JNDI) at esb/messageLogger/qualifier. The values are now specified by the ESB_MESSAGE_LOGGER_QUALIFIER environment variable.
User Action: This is a warning message only. To specify the schema qualifier value in the ESB_MESSAGE_LOGGER_QUALIFIER environment variable, refer to the WebSphere Enterprise Service Bus information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.

 

CWSXM3160E: The stylesheet ''{0}'' is too large to be processed.
Explanation: The Java VM does not have enough memory available to handle the XSLT stylesheet. This error has occurred after attempting to use all available XSLT transformation engines.
User Action: Return to WebSphere Integration Developer to optimize the contents of the XSLT style sheet if possible.

 

CWSXM3201E: Mediation primitive {2} in module {1} was unable to locate a key value from {0} within the message. This has been reported by the following entity: {3}
Explanation: An unsuccessful attempt was made to locate a value in the message to be used as a key into the database.
User Action: Return to WebSphere Integration Developer and verify that the properties of the primitive are correct for the expected message type.

 

CWSXM3202E: An exception occurred in mediation primitive ''{1}'' in module ''{0}'' when attempting to locate information in the configured database: {2}. This has been reported by the following entity: {3}
Explanation: An exception occurred when attempting to locate the information in the database. Ensure that the mediation primitive is configured correctly. Incorrect configuration may consist of an incorrect table name, database column names or the use of unsupported database column types.
User Action: Return to WebSphere Integration Developer to check the configuration of the primitive. Use the Administrative Console for your Database Management System to check that the database is available, configuration is correct and refer to the documentation for supported database column types.

 

CWSXM3203E: An exception occurred in mediation primitive {1} in module {0} when communicating with the database: {2}. This has been reported by the following entity: {3}
Explanation:
User Action: Use the Administrative Console for your Database Management System to ensure that the database is available and configured correctly. You can also view the FFDC logfiles for exception information.

 

CWSXM3204E: An exception occurred in mediation primitive {3} in module {2}. More than one row was returned from the database column {1} using the key {0}. This has been reported by the following entity: {4}
Explanation: More than one row of data was returned from the database. This is not allowed.
User Action: Refer to your database schema and check that the database key column only contains unique values.

 

CWSXM3205E: Mediation primitive {1} in module {0} was unable to obtain a connection to the database: {2}. This has been reported by the following entity: {3}
Explanation: Unable to obtain a connection to the database.
User Action: Use the Administrative Console to ensure that the database is available for connection and any necessary authentication rights have been configured in the appropriate datasource. See the problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3206E: Mediation primitive {3} in module {2} could not connect to the database using table {0} with column(s) {1}: {4}. This has been reported by the following entity: {5}
Explanation: An exception occurred when attempting to read from the database. The most probable cause of this error is an invalid table or column name.
User Action: Return to WebSphere Integration Developer and ensure that the property values for the table and column have been specified correctly.

 

CWSXM3207E: An exception occurred in mediation primitive {3} in module {2}. Unable to convert the value of type {0} which was obtained from the database into the specified type {1}. This has been reported by the following entity: {4}
Explanation: A type mismatch occurred between the type of the value obtained from the database and the type configured in mediation primitive.
User Action: Return to WebSphere Integration Developer and ensure the mediation primitive is configured correctly and the type of the value obtained from the database is one of the supported types.

 

CWSXM3208E: An exception occurred in mediation primitive {3} in module {2} when attempting to set the value {1} into the message with a location path of {0}. Ensure that the path specified is a valid location to store the value. This has been reported by the following entity: {4}
Explanation: An exception occurred attempting to set a value into the specified path location. This may be because the location path was not a valid location.
User Action: Return to WebSphere Integration Developer and ensure that the primitive properties define valid locations of the Service Message Object for the expected data.

 

CWSXM3209E: An exception occurred in mediation primitive {4} in module {3}. The value obtained from the {2} column using the key {1} was null and could not be set in the message because it has a type of {0}. This has been reported by the following entity: {5}
Explanation: A null value was obtained from the database column using the named key. This is not allowed.
User Action: Return to WebSphere Integration Developer and ensure that the value contained in the database is compatible with the message element type.

 

CWSXM3210E: An exception occurred in mediation primitive {2} in module {1}. The value obtained from the message at location {0} did not return a single element to be used as a key into the database. This has been reported by the following entity: {3}
Explanation: The value obtained from the message at the specified location did not return a single element to be used as a key into the database. This is not allowed.
User Action: Return to WebSphere Integration Developer and ensure that the location in the message to be used as a key is a single element and not a collection of elements.

 

CWSXM3250E: The list of filter expressions contains null in one or more positions. This has been reported by the following entity: {0}
Explanation: A MessageFilter primitive configuration contains a null Filter definition. Usually this means that the mediation flow configuration is not correct.
User Action: Return to WebSphere Integration Developer and correct the mediation flow configuration.

 

CWSXM3251E: The list of filter expressions contains duplicate terminal name ''{0}''. This has been reported by the following entity: {1}
Explanation: A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name.
User Action: Return to WebSphere Integration Developer and correct the mediation primitive configuration, ensuring that terminal names are used only once for a MessageFilter primitive.

 

CWSXM3300E: Fail primitive ''{0}'', component ''{1}'', module ''{2}'', interface ''{3}'', operation ''{4}'', raised a FailFlowException. The user-supplied error message is ''{5}''
Explanation: A Fail mediation primitive has raised a FailFlowException.
User Action: Examine any user-supplied error message.

 

CWSXM3401E: Incorrect parameters given. Usage: {0}
Explanation: The script was called with an incorrect set of parameters.
User Action: Call the script again with parameters described in the message.

 

CWSXM3402E: -createDb cannot be used in a Network Deployment environment.
Explanation: The "-createDb" option creates an embedded Derby database.
User Action: See the InfoCenter for instructions on how to install the database in a Network Deployment environment.

 

CWSXM3403E: The script cannot be used when multiple servers share one node. There are {0} servers on node {1}.
Explanation: There is more than one server configured for the node.
User Action: See the InfoCenter for instructions on how to create data sources for multiple servers.

 

CWSXM3404I: Saving configuration.
Explanation: The configuration changes are being saved.
User Action: None.

 

CWSXM3405I: Data source configuration completed successfully.
Explanation: The data source configuration changes have been completed.
User Action: None.

 

CWSXM3406I: Data source for {0} already exists.
Explanation: A data source with the specified JNDI name already exists.
User Action: None.

 

CWSXM3407I: Data source for {0} does not exist.
Explanation: A data source with the specified JNDI name does not exist.
User Action: None.

 

CWSXM3408I: Database {0} already exists.
Explanation: A database with the specified location and name already exists.
User Action: None.

 

CWSXM3409I: Database {0} does not exist.
Explanation: A database with the specified location and name does not exist.
User Action: None.

 

CWSXM3410E: Database {0} already exists.
Explanation: The script cannot create a database in the named location because a database already exists there.
User Action: Contact your Database Administrator to check whether the database has already been installed correctly. If it has not been installed correctly, check with your Database Administrator whether it is safe to delete the database and run this script again.

 

CWSXM3411E: The ''ij'' command was not found. The expected location of ''ij'' is "{0}"
Explanation: The script cannot find the ij.bat or ij.sh command in the named directory. If this file does not exist the server installation is corrupted.
User Action: Reinstall the application server to repair the installation.

 

CWSXM3412I: Creating DDL file {0}
Explanation: The script is creating the DDL file for the Derby database.
User Action: None.

 

CWSXM3413I: Creating Derby database. See log file for details at {0}
Explanation: The script is creating a Derby database using the DDL file. The results of the database creation are saved to a log file.
User Action: None.

 

CWSXM3414E: Configuration failed. JDBC provider {0} does not exist.
Explanation: The script needs this JDBC provider to configure the data source.
User Action: Restore the named JDBC provider or manually configure the data source.

 

CWSXM3415E: Data source for {0} already exists.
Explanation: A data source with the specified JNDI name already exists.
User Action: If the data source is already correctly configured, do not configure it again. Otherwise manually configure the data source to avoid naming conflicts with the existing configuration.

 

CWSXM3416E: CMP connection factory {0} already exists.
Explanation: The script cannot continue because the connection factory it would create already exists.
User Action: If the data source is already correctly configured, do not configure it again. Otherwise manually configure the data source to avoid naming conflicts with the existing configuration.

 

CWSXM3417I: Creating data source {0} under JDBC provider {1}
Explanation: The script is creating a data source for the named JDBC provider.
User Action: None.

 

CWSXM3418I: Configuring data source {0}
Explanation: The script is creating the data source configuration object.
User Action: None.

 

CWSXM3419I: Creating CMP connection factory for data source {0}
Explanation: The script is creating a CMP connection factory for the data source.
User Action: None.

 

CWSXM3420I: Successfully removed CMP connection factory {0}
Explanation: The script has removed the connection factory used by the data source.
User Action: None.

 

CWSXM3421W: Cannot find CMP connection factory {0}
Explanation: The CMP connection factory associated with the data source was not found.
User Action: Check whether the CMP connection factory exists and, if neccesary, manually remove it.

 

CWSXM3422I: Successfully removed data source {0}
Explanation: The script has removed the data source.
User Action: None.

 

CWSXM3423W: Cannot find data source {0}
Explanation: The data source was not found.
User Action: Check whether the data source exists and, if neccesary manually remove it.

 

CWSXM3424E: Node name and server name must be specified in a Network Deployment environment.
Explanation: The script was used in a Network Deployment environment but the node name and server name were not specified on the command line.
User Action: Call the script again specifying the node name and server name as the last two arguments on the command line

 

CWSXM3425E: The node name ''{0}'' or server name ''{1}'' are invalid.
Explanation: The node and server name combination could not be found.
User Action: Call the script again specifying a valid node name and server name as the last two arguments on the command line.

 

CWSXM3426I: Created Derby database successfully.
Explanation: The script has created a Derby database using the DDL file.
User Action: None.

 

CWSXM3427E: Derby database creation encountered errors. See log file for details at {0}
Explanation: The script attempted to create a Derby database using the DDL file. The results of the database creation are saved to a log file.
User Action: Check the log file for problems creating the database.

 

CWSXM3428I: The database will not be deleted. If the database is no longer required then it must be removed manually.
Explanation: The script does not remove the database.
User Action: If required, ask your Database Administrator to remove the database manually.

 

CWSXM3429E: Cannot create the requested dbLocation {0}. {1}
Explanation: The script cannot write files to the location specified in the -dbLocation parameter
User Action: If the location exists, ask your Database Administrator to check it is a directory, and the script has write access. If the location does not exist, your database Administrator should check that the script has write access to the parent directory.

 

CWSXM3430I: Modifying existing J2C authentication data alias: {0}.
Explanation: A J2C authentication alias with the required name was found and it is modified with the new username and password.
User Action: None.

 

CWSXM3431I: Creating new J2C authentication data alias: {0}.
Explanation: A J2C authentication alias with the required name was not found and a new one is created.
User Action: None.

 

CWSXM3432W: Found JDBC provider template {0}, but it might be the wrong one.
Explanation: A matching JDBC provider template was found but it may not be the correct one.
User Action: Check the JDBC Provider used for the Data Source and inform the System Administrator if it is the wrong one.

 

CWSXM3433E: The JDBC provider cannot be used because a template was not found for it: {0}.
Explanation: The script could not find a template for the required JDBC provider, so the JDBC provider cannot be used.
User Action: Report the problem to your WebSphere Application Server System Administrator.

 

CWSXM3434I: Using existing JDBC provider: {0}.
Explanation: The required JDBC provider already exists.
User Action: None.

 

CWSXM3435I: Creating JDBC provider: {0}.
Explanation: The required JDBC provider does not exist and is being created.
User Action: None.

 

CWSXM3436E: The -userid <userid> and -passwd <passwd> parameters are required for this script.
Explanation: The username and password parameters are required for this script but one or both of them were empty.
User Action: Run the script again, specifying values for both the username and password.

 

CWSXM3437E: Database {0} does not exist.
Explanation: A database with the specified location and name does not exist. this maybe because a remote database is to be used, but it has not yet been created.
User Action: Ask you Database Administrator to create database before attempting to create the table.

 

CWSXM3438I: Creating table in Derby database. See log file for details at {0}
Explanation: The script is creating a table in Derby database using the DDL file. The results of the table creation are saved to a log file.
User Action: None.

 

CWSXM3439I: Created table in Derby database successfully.
Explanation: The script has created a table in Derby database using the DDL file.
User Action: None.

 

CWSXM3440E: Derby database table creation encountered errors. See log file for details at {0}
Explanation: The script attempted to create a table in Derby database using the DDL file. The results of the database creation are saved to a log file.
User Action: Check the log file for ''ERROR'' lines, indicating problems creating the table in the database.

 

CWSXM3441E: Database type {0} is invalid.
Explanation: The supplied database type is invalid.
User Action: Supply a valid database type. You can find further information in the Information Center topic ''Prerequistites for creating or augmenting profiles''.

 

CWSXM3442E: Database driver type {0} is invalid.
Explanation: The supplied database driver type is invalid.
User Action: Supply a valid database driver type. You can find further information in the Information Center topic ''Prerequistites for creating or augmenting profiles''.

 

CWSXM3443E: Cluster name must be specified for cluster scope level.
Explanation: Cluster name must be specified for cluster scope level.
User Action: Supply a cluster name. You can use the administrative console to find a list of valid cluster names.

 

CWSXM3444E: Cluster name {0} is invalid.
Explanation: The supplied cluster name is invalid.
User Action: Supply a valid cluster name. You can use the administrative console to find a list of valid cluster names.

 

CWSXM3445E: Node name must be specified for node scope level in ND environment.
Explanation: Node name must be specified for node scope level in ND environment.
User Action: Supply a node name. You can use the administrative console to find a list of valid node names.

 

CWSXM3446E: Node name {0} is invalid.
Explanation: The supplied node name is invalid.
User Action: Supply a valid node name. You can use the administrative console to find a list of valid node names.

 

CWSXM3447E: Node name and server name must be specified for server scope level in ND environment.
Explanation: Node name and server name must be specified for server scope level in ND environment.
User Action: Supply a node name and a server name. You can use the administrative console to find a list of valid node and server names.

 

CWSXM3448E: Server name must be specified for server scope level in ND environment.
Explanation: Server name must be specified for server scope level in ND environment.
User Action: Supply a server name. You can use the administrative console to find a list of valid server names.

 

CWSXM3449E: Scope level {0} is invalid.
Explanation: The supplied scope level is invalid.
User Action: Supply a valid scope level. You can use the administrative console to find a list of valid scope levels.

 

CWSXM3450E: An exception occurred when attempting to set the value ''{1}'' into the message with a location path of ''{0}''. Ensure that the path specified is a valid location to store the value. This has been reported by the following entity: {2}
Explanation: An exception occurred attempting to set the given value into the message at the specified location.
User Action: Ensure that the path location is a valid location for the message being mediated.

 

CWSXM3451E: {0} is not a valid XPath expression for property ''value''. This has been reported by the following entity: {1}
Explanation: When the property ''type'' is ''copy'', then the value must be an XPath expression describing the location of the source element. The mediation configuration is not correct.
User Action: Correct the configuration of the mediation primitive.

 

CWSXM3452E: property ''target'' {0} is an XPath expression that resolves to more than one message element. This has been reported by the following entity: {1}
Explanation: The target must be a valid XPath expression that resolves to one message element. The mediation configuration is not correct.
User Action: Correct the configuration of the mediation primitive.

 

CWSXM3453W: An attempt to delete an element using a target which matches no message elements ''target'' {0}. This has been reported by the following entity: {1}
Explanation: The target must be a valid XPath expression that resolves to one message element.
User Action: Verify the configuration of the mediation primitive.

 

CWSXM3454E: property ''value'' {0} is not compatible with property ''type'' {1}. This has been reported by the following entity: {2}
Explanation: The value must be compatible with the type specified. The mediation configuration is not correct.
User Action: Correct the configuration of the mediation primitive.

 

CWSXM3455E: property ''type'' {0} is not compatible with existing ServiceMessageObject property at path ''target'' {1} of ''type'' {2}. This has been reported by the following entity: {3}
Explanation: The message element must be compatible with the existing SMO property being set.
User Action: Correct the configuration of the mediation primitive.

 

CWSXM3456E: property ''value'' {0} is an XPath expression that resolves to more than one message element. This has been reported by the following entity: {1}
Explanation: The value must be a valid XPath expression that resolves to one message element. The mediation configuration is not correct.
User Action: Correct the configuration of the mediation primitive.

 

CWSXM3457E: Cannot set value ''{1}'' into location ''{0}'' because location ''{0}'' cannot be created using the Message Element Setter primitive. Please use another primitive, such as XSLTransform or a custom mediation, to create this location. This has been reported by the following entity: {2}
Explanation: An exception occurred attempting to set the given value into the message at the specified location.
User Action: Use another primitive, such as XSLTransform or a custom mediation, to create this location.

 

CWSXM3500E: Mediation primitive {1} in module {0} was unable to send the event to the Common Event Infrastructure: {2}. This has been reported by the following entity: {3}
Explanation: An exception occurred when sending an event to the Common Event Infrastructure service.
User Action: Inspect the nested exception to diagnose the problem.

 

CWSXM3501E: Mediation primitive {3} in module {2} has an event label property {0} with a length of {1} which exceeded the maximum length of 64 characters. This has been reported by the following entity: {4}
Explanation: The event label exceeded the maximum length of 64 characters.
User Action: Reduce the value of the event label property to 64 or less characters. Remember to keep event labels unique.

 

CWSXM3502E: Mediation primitive {1} in module {0} was unable to send the event to the Common Event Infrastructure. Ensure that the Common Event Infrastructure is available. This has been reported by the following entity: {2}
Explanation: The event emitter primitive was unable to send the event to the Common Event Infrastructure.
User Action: Ensure that the Common Event Infrastructure and associated resources are available for access.

 

CWSXM3550E: Unable to connect to the service registry defined by ''{0}''. Refer to the nested exception for more information. This has been reported by the following entity: {1}
Explanation: Unable to connect to the service registry.
User Action: Ensure that the service registry is available and administration settings for the service registry definition have been correctly configured.

 

CWSXM3551E: Service registry definition ''{0}'' set on node ''{1}'' in module ''{2}'' could not be found. This has been reported by the following entity: {3}
Explanation: The service registry definition could not be found.
User Action: Ensure a service registry definition is configured with the required definition name or a default service registry definition exists.

 

CWSXM3552E: User property ''{0}'' has in invalid xpath value ''{1}''. This has been reported by the following entity: {2}
Explanation: The primitive has been configured with a user property that has in invalid xpath value.
User Action: Ensure that the path specified is a valid location within the Service Message Object.

 

CWSXM3553E: Authentication error for service registry definition ''{0}''. Either the specified authentication alias does not exist or the supplied credentials are incorrect. This has been reported by the following entity: {1}
Explanation: Either the specified authentication alias for registry definition does not exist, or the supplied credentials are incorrect.
User Action: Ensure the authentication alias exists and has the correct credentials.

 

CWSXM3554E: The registry URL supplied for service registry definition ''{0}'' is not a valid URL. This has been reported by the following entity: {1}
Explanation:
User Action: Ensure that the registry URL is correctly specified in the service registry definition.

 

CWSXM3555E: The service registry connection type specified by service registry definition ''{0}'' is not supported. This has been reported by the following entity: {1}
Explanation: The service registry connection type specified by the service registry definition is not supported.
User Action: Select a supported connection type for the service registry definition.

 

CWSXM3562E: The service registry specified by service registry definition ''{0}'' called by node ''{1}'' in module ''{2}'' has returned an invalid result. This has been reported by the following entity: {3}
Explanation: The service registry has returned an invalid result.
User Action: Ensure the server and service registry have started without error.

 

CWSXM3563E: An unexpected exception has been thrown by node ''{1}'' in module ''{2}'' when trying to call the service reqistry specified by service registry definition ''{0}''. This has been reported by the following entity: {3}
Explanation: An unexpected exception has been thrown when trying to call the service registry.
User Action: Use the FFDC log file to determine the cause of the error.

 

CWSXM3564E: A service registry proxy exception has occurred when node ''{1}'' in module ''{2}'' called the service registry specified by service registry definition ''{0}''. The exception message is ''{3}''. This has been reported by the following entity: {4}
Explanation: A service registry proxy exception.
User Action: Use the FFDC log file to determine the cause of the problem.

 

CWSXM3565W: Using a JNDI namespace binding to specify a repertoire to be associated with web service communication between an endpoint lookup mediation primitive and service registry is now deprecated. Please update the repertoire property of WSRR definition ''{0}'' and delete the JNDI namespace binding ''{1}''.
Explanation: Using a JNDI namespace binding to specify a repertoire to be associated with web service communication between an endpoint lookup mediation primitive and service registry is now deprecated. The repertoire should be specified using the repertoire property of a WSRR definition.
User Action: Specify a repertoire using the repertoire property of a WSRR definition within the administration console and delete the JNDI namespace binding.

 

CWSXM3600I: Created schema variable successfully.
Explanation: Created schema variable successfully.
User Action: None.

 

CWSXM3601E: Failed to create schema variable.
Explanation:
User Action: Check the installation logs and rerun script as necessary.

 

CWSXM3650E: Root property evaluated to multiple elements which is not allowed. This has been reported by the following entity: {0}
Explanation: The Root property on the Business Object Map mediation primitive must evaluate to a single DataObject. It evaluated to multiple elements in the message being mediated.
User Action: Correct the Root property in the Business Object Map mediation primitive.

 

CWSXM3651E: Root property evaluated to a {0}. This has been reported by the following entity: {1}
Explanation: The Root property on the Business Object Map mediation primitive must evaluate to a single DataObject. It must not evaluate to a collection of DataObjects or to a value other than a single DataObject.
User Action: Correct the Root property in the Business Object Map mediation primitive.

 

CWSXM3652E: Exception while evaluating the Root property. This has been reported by the following entity: {0}
Explanation: An Exception was caught while the Business Object Map mediation primitive was evaluating the Root, prior to transformation.
User Action: Use the FFDC log file sto determine the problem.

 

CWSXM3653E: Exception while executing Business Object map: {0}. This has been reported by the following entity: {1}
Explanation: An Exception was caught while the Business Object Map primitive was executing the map.
User Action: Use the FFDC log file sto determine the problem.

 

CWSXM3654E: Exception while executing Business Object map: {0}. This has been reported by the following entity: {1}
Explanation: The map service could not load the map.
User Action: Use the FFDC log file sto determine the problem.

 

CWSXM3655E: Exception while executing Business Object map: {0}. This has been reported by the following entity: {1}
Explanation: An Exception was caught while the Business Object Map primitive was executing the map.
User Action: Use the FFDC log file sto determine the problem.

 

CWSXM3700E: The reference {0} for Service Invoke primitive {1} is undefined. This has been reported by the following entity: {2}
Explanation: The reference for the Service Invoke primitive is not defined on the mediation component.
User Action: Check the validity and correct deployment of the mediation component.

 

CWSXM3701E: Reference {0} for Service Invoke primitive {1} does not define an operation named {2}. This has been reported by the following entity: {3}
Explanation: There is no operation of the specified name defined on the reference for the Service Invoke primitive.
User Action: Check the configuration of the Service Invoke primitive.

 

CWSXM3702E: The component {0} containing Service Invoke primitive {1} could not be found at runtime. This has been reported by the following entity: {2}
Explanation: The component containing the Service Invoke primitive could not be found at runtime.
User Action: Check the validity and correct deployment of the mediation component.

 

CWSXM3703E: Exception when calling the service for operation {0} on reference {1}: {2}. This has been reported by the following entity: {3}
Explanation: An error occurred when the action of a flow was called.
User Action: Use the FFDC log file to determine the problem.

 

CWSXM3704E: The response from the service invocation of operation {0} on reference {1} was of an unknown type. This has been reported by the following entity: {2}
Explanation: The response was neither a valid response, modeled fault or unmodeled fault.
User Action: Validate the expected responses from the operation of the reference, and that the service is acting correctly.

 

CWSXM3705E: No matching output terminal found for modeled fault {0} returned by operation {1} on reference {2}. This has been reported by the following entity: {3}
Explanation: There was no matching output terminal found for the modeled fault returned from the service calling. This could be because the service interface has changed since the Service Invoke mediation primitive was created.
User Action: Check if the Service Invoke mediation primitive needs to be updated to reflect a new interface.

 

CWSXM3706E: A terminal with an empty name was found. This has been reported by the following entity: {0}
Explanation: During the processing of the mediation flow a terminal on the Service Invoke mediation primitive was identified as having an empty name.
User Action: Check if the service invocation primitive needs to be updated within the mediation flow tooling.

 

CWSXM3708E: Unexpected response received by Service Invoke primitive. This has been reported by the following entity: {0}
Explanation: An unexpected response message was received by a ServiceInvoke primitive which was configured with a one-way operation and has no output terminals to propagate the response.
User Action: Review mediation primitive configuration in tooling.

 

CWSXM3709E: An unexpected event key {0} was received by a Service Invoke primitive in mediation component {1}. This has been reported by the following entity: {2}
Explanation: An unexpected event key was received by a ServiceInvoke mediation primitive which was configured for asynchronous response. Event keys are used by the system to correlate asynchronous requests.
User Action: Check the validity and correct deployment of the mediation flow component.

 

CWSXM3710E: An unexpected handleEvent with event key {0} was called on a Service Invoke primitive in mediation {1}. This has been reported by the following entity: {2}
Explanation: The ServiceInvoke primitive was not configured for an asynchronous response but was called using asynchronous event processing.
User Action: Check the validity and correct deployment of the mediation flow component.

 

CWSXM3750E: Invalid aggregation state transition from {0} to {1}
Explanation: An aggregation between a Fan Out and Fan In primitive tried to make an invalid state transition
User Action: Check the wiring between the Fan Out and Fan In primitive is correct.

 

CWSXM3751E: An exception occurred in an aggregation: {0}. This has been reported by the following entity: {1}
Explanation: An internal problem occurred during the flow execution of an aggregation between a Fan Out and Fan In primitive.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3752E: Error using XPath expression {0} to locate repeating element: {1}. This has been reported by the following entity: {2}
Explanation: An error occurred when using the supplied XPath to locate the repeating element in the message.
User Action: Check that the XPath in the Fan Out mediation primitive is valid and points to a repeating element in the message.

 

CWSXM3753E: Aggregation state could not be obtained. This has been reported by the following entity: {0}
Explanation: An internal problem occurred when trying to obtain the state of an aggregation between a Fan Out and Fan In primitive.
User Action: If the problem continues, see problem determination information on the WebSphere Enterprise Service Bus Support page at http://www.ibm.com/software/integration/wsesb/support/.

 

CWSXM3801E: Message validation failed due to schema validation returning {1} for parameter {0}. This has been reported by the following entity: {2}
Explanation: A problem occurred when trying schema validation on the message.
User Action: The message failed schema validation, use WebSphere Integration Developer to ensure that the interface has the correct types defined for the expected messages.

 

CWSXM3802E: The type at {0} is ''{1}'', while the asserted type states it should be ''{2}''. This has been reported by the following entity: {3}
Explanation: A problem occurred when comparing the asserted type to the type within the message.
User Action: The asserted type did not match that of the message, use WebSphere Integration Developer to ensure that the asserted type is correct for the expected messages.

 

CWSXM3803E: Error using XPath expression {0} to locate the asserted element: {1}. This has been reported by the following entity: {2}
Explanation: An error occurred when using the supplied XPath to locate the asserted element in the message.
User Action: Use WebSphere Integration Developer to check that the XPath in the SetmessageType mediation primitive is valid and points to an asserted element in the message.

 

CWSXM3850E: Error unable to load Primitive Property schema
Explanation: During the processing of a Policy Resolution primitive, the Primitive Property schema did not load.
User Action: This is an unexpected internal error that would suggest a fundamental error with the installation. Please ensure that your installation was successful and if you are unable to resolve the problem contact IBM support.

 

CWSXM3851E: Unable to connect to the service registry defined by ''{0}''. Refer to the nested exception for more information. This has been reported by the following entity: {1}
Explanation: Unable to connect to the service registry.
User Action: Ensure that the service registry is available and administration settings for the service registry definition have been correctly configured.

 

CWSXM3852E: Service registry definition ''{0}'' set on node ''{1}'' in module ''{2}'' could not be found. This has been reported by the following entity: {3}
Explanation: The service registry definition could not be found.
User Action: Ensure a service registry definition is configured with the required definition name or a default service registry definition exists.

 

CWSXM3854E: Authentication error for service registry definition ''{0}''. Either the specified authentication alias does not exist or the supplied credentials are incorrect. This has been reported by the following entity: {1}
Explanation: Either the specified authentication alias for registry definition does not exist, or the supplied credentials are incorrect.
User Action: Ensure the authentication alias exists and has the correct credentials.

 

CWSXM3855E: The registry URL supplied for service registry definition ''{0}'' is not a valid URL. This has been reported by the following entity: {1}
Explanation:
User Action: Ensure that the registry URL is correctly specified in the service registry definition.

 

CWSXM3856E: The service registry connection type specified by service registry definition ''{0}'' is not supported. This has been reported by the following entity: {1}
Explanation: The service registry connection type specified by the service registry definition is not supported.
User Action: Select a supported connection type for the service registry definition.

 

CWSXM3863E: The service registry specified by service registry definition ''{0}'' called by node ''{1}'' in module ''{2}'' has returned an invalid result. This has been reported by the following entity: {3}
Explanation: The service registry has returned an invalid result.
User Action: Ensure the server and service registry have started without error.

 

CWSXM3864E: An unexpected exception has been thrown by node ''{1}'' in module ''{2}'' when trying to call the service reqistry specified by service registry definition ''{0}''. This has been reported by the following entity: {3}
Explanation: An unexpected exception has been thrown when trying to call the service registry.
User Action: Use the FFDC log file to determine the cause of the error.

 

CWSXM3865E: A service registry proxy exception has occurred when node ''{1}'' in module ''{2}'' called the service registry specified by service registry definition ''{0}''. The exception message is ''{3}''. This has been reported by the following entity: {4}
Explanation: A service registry proxy exception.
User Action: Use the FFDC log file to determine the cause of the problem.

 

CWSXM3866E: Failed to merge the mediation policies that did not have associated gate conditions
Explanation: When merging mediation policies retrieved from the registry, conflicting assertions were found.
User Action: In the registry, ensure there are no conflicting assertions in the mediation policies, without gate conditions, that are attached to the module.

 

CWSXM3867E: Failed to merge mediation policies that had associated gate conditions: {0}
Explanation: When merging mediation policies retrieved from the registry, conflicting assertions were found.
User Action: In the registry, ensure there are no conflicting assertions in the mediation policies that are attached to the module, and that have gate conditions satisfied by the current message .

 

CWSXM3868E: Failed to merge mediation policies, some of which had gate conditions and some of which did not. Gate conditions: {0}
Explanation: When merging mediation policies retrieved from the registry, conflicting assertions were found.
User Action: In the registry, ensure there are no conflicting assertions in the mediation policies that might apply to the current message (a mediation policy has the potential to apply, if it is attached to the current module).

 

CWSXM3869E: A failure occurred when processing mediation policies. The mediation policy assertion ''{0}'' has no value specified
Explanation: When processing mediation policies retrieved from the registry, a policy assertion was encountered that did not have a value.
User Action: In the registry, ensure that mediation policies attached to the module, do not have assertions without values.

 

CWSXM3871E: Condition property ''{0}'' has in invalid xpath value ''{1}''. This has been reported by the following entity: {2}
Explanation: The primitive has been configured with a condition property that has an invalid xpath value.
User Action: Ensure that the path specified is a valid location within the Service Message Object.

 

CWSXM3900E: Subflow mediation primitive ''{0}'' failed to obtain flows for component ''{1}'' in module ''{2}''.
Explanation: A subflow mediation primitive failed to obtain the component flows during initialization.
User Action: Contact IBM support.

 

CWSXM3901E: Subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'' failed to load subflow ''{3}'' from file ''{4}''.
Explanation: A subflow mediation primitive failed to load the definition of the subflow from the given file.
User Action: Ensure that the subflow file exists in the module or one of its dependent libraries.

 

CWSXM3902E: Subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'' failed to parse the subflow ''{3}'' from file ''{4}''.
Explanation: A subflow mediation primitive failed to parse the definition of the given subflow.
User Action: Ensure that the subflow definition is valid.

 

CWSXM3903E: Subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'' has an empty subflow file name property.
Explanation: A subflow mediation primitive has an empty subflow file name property.
User Action: Ensure that the subflow mediation primitive has been configured with a subflow file name property.

 

CWSXM3904E: The following error occurred during initialization of subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'': ''{3}''
Explanation: Initialization of the subflow mediation primitive failed with the given error.
User Action: Investigate the cause of the given error.

 

CWSXM3905E: The following error occurred during execution of subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'': ''{3}''
Explanation: Execution of the subflow mediation primitive failed with the given error.
User Action: Investigate the cause of the given error.

 

CWSXM3906E: The input terminal ''{0}'' was fired on subflow mediation primitive ''{1}}'' in component ''{2}}'' and module ''{3}'' but the subflow does not have a corresponding in node.
Explanation: A subflow mediation primitive received a message on the input terminal with the given name but the associated subflow does not have an in node with the same name.
User Action: Ensure that the subflow mediation primitive and associated subflow are synchronized.

 

CWSXM3907E: The out node ''{0}'' was reached in a subflow but the subflow mediation primitive ''{1}}'' in component ''{2}}'' and module ''{3}'' does not have a corresponding output terminal node.
Explanation: A subflow received a message at the out node with the given name but the associated subflow mediation primitive does not have an output terminal node with the same name.
User Action: Ensure that the subflow mediation primitive and associated subflow are synchronized.

 

CWSXM3908E: The subflow mediation primitive ''{0}}'' in component ''{1}}'' and module ''{2}'' has a subflow name of ''{3}'' which is not of the expected format.
Explanation: A subflow mediation primitive has been configured with a subflow name property that is not of the expected format.
User Action: Ensure that the associated subflow has a valid name and that the subflow name property on the mediation primitive matches.

 

CWSXM4000E: Error parsing the Mediation Flow definition: unexpected format.
Explanation: Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4001E: Error parsing the Mediation Flow definition: cannot parse the terminal type.
Explanation: Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4002E: Error parsing the Mediation Flow definition: Response flow with no preceding Request flow.
Explanation: The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4003E: Error parsing the Mediation Flow definition: there are no flows.
Explanation: The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4004E: Error parsing the Mediation Flow definition: no Operation Name for node, ''{0}''.
Explanation: Missing value for the named node''s Operation Name.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4005E: Error parsing the Mediation Flow definition: no Reference Name for node, ''{0}''.
Explanation: Missing value for the named node''s Reference Name.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4006E: Error parsing the Mediation Flow definition: no Operation Name for the Custom Mediation node, ''{0}'' (of type ''{1}'').
Explanation: Missing value for the Custom Mediation node''s Operation Name.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4007E: Error parsing the Mediation Flow definition: no Reference Name for the Custom Mediation node, ''{0}'' (of type ''{1}'').
Explanation: Missing value for the Custom Mediation node''s Reference Name.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4008E: Error parsing the Mediation Flow definition: node name, ''{0}''.
Explanation: An exception occurred when parsing the named mediation flow node.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4010E: Error parsing the Mediation Flow definition: found {0} InputNodes.
Explanation: The Request Flow must have one, and only one Input node.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4011E: Error parsing the Mediation Flow definition: Request Flow, Operation Name=''{0}''.
Explanation: An exception occurred when parsing the named mediation flow Request Flow.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4012E: Error parsing the Mediation Flow definition: Response Flow.
Explanation: An exception occurred when parsing the mediation flow Response Flow.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4013E: Error parsing the Mediation Flow definition: Terminal types do not match.
Explanation: The types of the terminals that are connected together must be the same.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4014E: Error parsing the Mediation Flow definition: Node, ''{0}'' has an incorrectly defined or missing terminal.
Explanation: The node is missing an expected terminal, named with one of the standard names, ''in'' or ''out''.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4019E: Error parsing the Mediation Flow definition: Node ''{0}'' is an unidentified type of node (''{1}''): not standard, nor mediation primitive, nor custom mediation node.
Explanation: The Mediation Flow definition file may have been corrupted or the Mediation Flow may have been produced on a version of the tooling greater than the version of the runtime.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4025E: Error parsing the Mediation Flow definition: missing value for source Terminal type.
Explanation: No value for the sub-type of the complex-type for a source terminal in a connection.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4026E: Error parsing the Mediation Flow definition: missing value for target Terminal type.
Explanation: No value for the sub-type of the complex-type for a target terminal in a connection.
User Action: Use WebSphere Integration Developer to verify that the Mediation Flow definition is correct.

 

CWSXM4030W: Warning multiple medflow files were defined within the MFC file.
Explanation: The MFC file has more than one medflow file specified, the first medflow file defined will be assumed to be correct. If the incorrect behaviour is observed, correct the MFC file within the tooling and re-deploy the application to the server.
User Action: Use WebSphere Integration Developer to verify that the MFC file definition is correct.

 

CWSXM4031W: A response flow does not have a corresponding CallOut node.
Explanation: This problem is caused when a medflow file has become corrupted.
User Action: Use WebSphere Integration Developer to verify that the medflow file definition is correct.

 

CWSXM4100E: Mediation flow component definition file {0} could not be loaded.
Explanation: The named mediation flow component definition file could not be loaded.
User Action: Use WebSphere Integration Developer to check the validity of the deployed mediation component.

 

CWSXM4101E: Mediation flow definition file {0} could not be loaded.
Explanation: The named mediation flow definition file could not be loaded.
User Action: Use WebSphere Integration Developer to check the validity of the deployed mediation component.

 

CWSXM4102E: Error in parsing mediation flow component definition file {0}: {1}
Explanation: An exception occurred when parsing the named mediation flow component definition file.
User Action: Use WebSphere Integration Developer to check the validity of the deployed mediation component.

 

CWSXM4103E: Error in parsing mediation flow, unable to find mednode file ''{0}''
Explanation: An exception occurred when parsing the mediation flow due to a missing mednode file.
User Action: Ensure that all user defined mediation primitive mednode files are available to the runtime. Install the missing mediation primitives to the runtime. See the InfoCenter for instructions on how to install user defined mediation primitives to the runtime.

 

CWSXM4104E: Error parsing the subflow definition ''{0}''.
Explanation: An exception occurred when parsing the named mediation subflow.
User Action: Use WebSphere Integration Developer to verify that the mediation subflow definition is correct.

 

CWSXM4105E: The subflow ''{0}'' does not have any in nodes.
Explanation: A subflow must have at least one in node.
User Action: Use WebSphere Integration Developer to add an in node to the mediation subflow.

 

CWSXM4106E: The subflow ''{0}'' does not have any out nodes.
Explanation: A subflow must have at least one out node.
User Action: Use WebSphere Integration Developer to add an out node to the mediation subflow.

 

CWSXM4107E: The mediation subflow {0} could not be loaded from file {1}.
Explanation: The named mediation subflow could not be loaded from the given file.
User Action: Use WebSphere Integration Developer to check the validity of the deployed mediation component.

 

CWSXM9998I: This is a test message
Explanation: This is a unit test message
User Action: No action necessary

 

CWSXM9999I: This is a test parameterised message: {0}
Explanation: This is a unit test message
User Action: No action necessary

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009