Messages for SIBX.common component
CWSXM0054E: Key {0} not found in context store when locating correlation information for module {1}
Description
The requested key is not present in the context store. 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 Variables
{0}
Context store key
{1}
SCA module name
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM0055E: Key {0} is already present in the context store when storing correlation information for module {1}
Description
The requested key is already in the context store. Explanation
This exception is unexpected. The cause is not immediately known. Variables
{0}
Context store key
{1}
SCA module name
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM0100E: Multiple replies have been produced for a single request flow in module {0}
Description
Multiple replies have been produced for a single request flow. Explanation
A mediation request flow has invoked multiple request/reply services, and nore 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. Variables
{0}
SCA module name
System action
Inform the user. User action
Ensure that either the request flow is limited to making a single request/reply invocation or result or fault, or that only one response flow produces a reply.
CWSXM0101E: A mediation response or fault flow attempted to invoke a service in module {0}
Description
Mediation response or fault flow cannot invoke services. Explanation
Mediation response and fault flows are not permitted to invoke services. Variables
{0}
SCA module name
System action
Inform the user. User action
Ensure that the response and fault flows in the module do not invoke services.
CWSXM0102E: The operation {0} cannot be resolved.
Description
Flow Action cannot resolve the named operation. Explanation
The named operation cannot be found for the reference that is invoked by the mediation flow. Variables
{0}
Operation name
System action
Inform the user. User action
Ensure that the operation name that is used in the mediation flow is correct.
CWSXM0103E: Could not locate the EJB session bean for component {0} in module {1}
Description
The mediation flow session bean for the specified SCA mediation Explanation
The requested EJB session bean could not be located. Variables
{0}
the SCA component name
{1}
the SCA module name
System action
Inform the user. User action
Check the deployment of the mediation flow component.
CWSXM0104E: A runtime error occured when saving context for a mediation flow in mediation component {0} in module {1}
Description
The mediation flow encountered an error when saving context Explanation
An internal error occured when saving the context information used by a mediation flow for the given component. Variables
{0}
the SCA component name
{1}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
CWSXM0105E: A runtime error occured when saving context for a mediation flow in mediation component {0} in module {1}
Description
The mediation flow encountered an error when saving context Explanation
An error occured when saving the context information used by a mediation flow for the given component. Variables
{0}
the SCA component name
{1}
SCA module name
System action
Inform the user. User action
Check the causal exception for more information.
CWSXM0106E: A runtime error occured when receiving a response for mediation component {0} in module {1}
Description
The mediation flow encountered an error when receiving a response Explanation
An internal error occured when the mediation flow component processed a response message. Variables
{0}
the SCA component name
{1}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
CWSXM0107E: A runtime error occured when receiving a response for mediation component {0} in module {1}
Description
The mediation flow component encountered an internal error when receiving Explanation
An internal error occured when the mediation flow component processed a response message. Variables
{0}
the SCA component name
{1}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
CWSXM0108E: A runtime error occured when creating an outbound message in mediation component {0} and module {1}
Description
The mediation flow encountered an error when processing an outbound message. Explanation
An internal error occured when the mediation flow component was creating an outbound message. Variables
{0}
the SCA component name
{1}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
CWSXM0109E: Multiple connections to reference {0} in mediation component {1} and module {2}
Description
The mediation flow encountered an error when processing an outbound message. Explanation
The reference is connected to multiple services but only a single service can be connected to on a reference in a mediation flow. Variables
{0}
the reference name
{1}
the SCA component name
{2}
SCA module name
System action
Inform the user. User action
Check the validity of the mediation flow and the validity of references that are invoked.
CWSXM0200E: Could not locate the mediation flow for component {0} in module {1}
Description
The mediation flow session bean for the specified SCA mediation Explanation
The requested mediation flow session bean could not be located. Variables
{0}
the SCA component name
{1}
the SCA module name
System action
Inform the user. User action
Check the deployment of the mediation flow component.
CWSXM0201E: Exception returned by mediation flow for component {0} in module {1}
Description
The mediation flow for the specified SCA mediation component and 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. Variables
{0}
the SCA component name
{1}
the SCA module name
System action
Inform the user. User action
Check the mediation flow to ensure that all failure terminals on primitives are wired.
CWSXM0202E: An unexpected exception occurred when processing mediation flow for component {0} in module {1}
Description
An unexpected exception has occured during the processing Explanation
This exception is unexpected. The cause is not immediately known. Variables
{0}
the SCA component name
{1}
the SCA module name
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM0203E: An unexpected exception occurred when accessing the persistent store for component {0} in module {1}
Description
An unexpected error occurred when accessing the persistent store. Explanation
This exception is unexpected. The cause is not immediately known. Variables
{0}
the SCA component name
{1}
the SCA module name
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM0204E: A configuration error occurred when invoking a mediation flow.
Description
A configuration error occurred when invoking a mediation flow. Explanation
The mediation flow returned a configuration exception when invoked. The exception may indicate that a primitive in the flow failed to obtain a required resource. Variables
None.
System action
Inform the user. User action
Check the underlying exception for more details of the cause of the configuration error.
CWSXM0205E: An unexpected business logic exception occurred.
Description
An unexpected business logic exception has occured during the processing Explanation
The mediation flow returned an exception that indicated that a business logic error occurred. Variables
None.
System action
Inform the user. User action
Check the underlying exception for details of the business logic error.
CWSXM0206E: An unexpected exception occurred.
Description
An unexpected exception has occured during the processing Explanation
This exception is unexpected. The cause is not immediately known. Variables
None.
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM1000E: Could not locate runtime mediation flow for mediation component {0} in module {1}
Description
There is no lightweight flow defined for the specified SCA Explanation
No runtime mediation flow definitions were found for the mediation component. Variables
{0}
SCA mediation component name
{1}
SCA module name
System action
Inform the user. User action
Check the mediation component has a mediation flow defined and check for any earlier exceptions in loading the definition.
CWSXM1001E: No request flow found for operation {0} on port type {1}. In mediation component {2} in module {3}
Description
The lightweight request flow model for the specified request flow, 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. Variables
{0}
operation name
{1}
port type
{2}
SCA mediation component name
{3}
SCA module name
System action
Inform the user. User action
Verify that the mediation component has a request flow defined for the operation.
CWSXM1002E: No response flow found for operation {0} on reference {1}. In mediation component {2} in module {3}
Description
The lightweight response flow model for the specified operation name invoked Explanation
The response flow for the operation invoked 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. Variables
{0}
reference operation name
{1}
reference
{2}
SCA mediation component name
{3}
SCA module name
System action
Inform the user. User action
Verify that the mediation component has a response flow defined for the operation and check for any earlier exceptions in loading the response flow.
CWSXM1003E: No response fault flow found for fault message {0} from operation {1} on reference {2}. In mediation component {3} in module {4}
Description
The lightweight fault flow model for the specified fault message and Explanation
The response flow for the operation invoked 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. Variables
{0}
fault name
{1}
reference operation name
{2}
reference
{3}
SCA mediation component name
{4}
SCA module name
System action
Inform the user. User action
Verify that the mediation component has a response fault flow defined for the fault message and operation and check for any earlier exceptions in loading the response fault flow.
CWSXM1004E: An invalid input is specified for a flow. In mediation component {0} in module {1}
Description
An invalid input is specified for a flow. Explanation
The flow has an invalid or unknown input. Variables
{0}
SCA mediation component name
{1}
SCA module name
System action
Inform the user. User action
Validate the mediation flow definition.
CWSXM1005E: Error whilst instantiating mediation primitive {0}. In mediation component {1} in module {2}
Description
The primitive class could not be loaded. Check the causal Explanation
The mediation primitive could not be instantiated. Variables
{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name
System action
Inform the user. User action
Validate the mediation flow definition, and check the causal exception for more information.
CWSXM1006E: Error whilst setting properties of mediation primitive {0}. In mediation component {1} in module {2}
Description
An error occured when setting the properties of the mediation Explanation
An error occured whilst trying to set the properties of the mediation primitive. Variables
{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name
System action
Inform the user. User action
Verify that the correct properties are defined for the mediation primitive in the mediation flow definition, and check the causal exception for more information.
CWSXM1007E: Mediation primitive {0} failed to initialize. In mediation component {1} in module {2}
Description
The mediation primitive encountered a configuration error during Explanation
During the primitives initialization, the named mediation primitive encountered an error. Variables
{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name
System action
Inform the user. User action
Verify that the configuration of the mediation primitive in the mediation flow definition, and check the causal exception for more information.
CWSXM1008E: Key of type {0} is not of expected type.
Description
The key is not of the expected type. Check the causal exception Explanation
The key class is not of the expected type for this flow engine. Variables
{0}
the key class
System action
Inform the user to contact IBM support. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM1009E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
Description
There was a problem in locating the runtime instance for the SCA Explanation
There was a problem in locating the runtime instance of the mediation flow. Variables
{0}
SCA mediation component name
{1}
SCA module name
System action
Inform the user. User action
Check the causal exception for more information.
CWSXM1010E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
Description
There was a problem in locating the runtime instance for the SCA Explanation
There was a problem in locating the runtime instance of the mediation flow. Variables
{0}
SCA mediation component name
{1}
SCA module name
System action
Inform the user. User action
Check the causal exception for more information, and validate that the SCA module started with no errors.
CWSXM1011E: A runtime error occured invoking the request flow for operation {0}, on port type {1}. In mediation component {2} in module {3}
Description
The mediation engine encountered an error whilst processing the Explanation
An internal error occured when invoking the request flow for the operation. Variables
{0}
the operation name
{1}
port type name
{2}
SCA component name
{3}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
CWSXM1012E: A runtime error occured invoking the response flow for operation {0} on reference {1}. In mediation component {2} in module {3}
Description
The mediation engine encountered an error whilst processing the Explanation
An internal error occured when invoking the response flow for the operation on the named reference. Variables
{0}
reference operation name
{1}
reference
{2}
SCA component name
{3}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
CWSXM1013E: A runtime error occured invoking the response fault flow for fault message {0} and operation {1} on reference {2}. In mediation component {3} in module {4}
Description
The mediation engine encountered an error whilst processing the Explanation
An internal error occured when invoking the fault response flow for the fault message and operation on the named reference. Variables
{0}
fault name
{1}
reference operation name
{2}
reference
{3}
SCA component name
{4}
SCA module name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
CWSXM1016E: The reference {0} for custom mediation {1} is undefined.
Description
The reference representing the custom mediation is not defined Explanation
The reference for the custom mediation is not defined on the mediation component. Variables
{0}
reference
{1}
custom mediation name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation component.
CWSXM1017E: Request flow runtime instance is unavailable.
Description
The request flow runtime instance is not available due to Explanation
The request flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow. Variables
None.
System action
Inform the user. User action
Check the validity of the mediation flow component, and check for previous errors.
CWSXM1018E: Response flow runtime instance is unavailable.
Description
The response flow runtime instance is not available due to Explanation
The response flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow. Variables
None.
System action
Inform the user. User action
Check the validity of the mediation flow component, and check for previous errors.
CWSXM1019E: Response fault flow runtime instance is unavailable.
Description
The response fault flow runtime instance is not available due to Explanation
The response fault flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow. Variables
None.
System action
Inform the user. User action
Check the validity of the mediation flow component, and check for previous errors.
CWSXM1020E: An unknown exception occured during the processing of mediation primitive {0}: {1}
Description
An unknown exception occured during the processing of the Explanation
An unknown exception occurred during the processing of the specified mediation primitive or custom mediation. Variables
{0}
mediation primitive name
{1}
exception message
System action
Inform the user. User action
Check the causal exception for more information.
CWSXM1021E: No input terminal named {0} defined for mediation primitive {1}
Description
A mediation primitive has attempted to obtain an input terminal Explanation
A mediation primitive attempted to obtain an input terminal which does not exist. Variables
{0}
input terminal name
{1}
mediation primitive name
System action
Inform the user. User action
Check the validity of the mediation flow component.
CWSXM1022E: No output terminal named {0} defined for mediation primitive {1}
Description
A mediation primitive has attempted to obtain an output terminal Explanation
A mediation primitive attempted to obtain an output terminal which does not exist. Variables
{0}
output terminal name
{1}
mediation primitive name
System action
Inform the user. User action
Check the validity of the mediation flow.
CWSXM1023E: Exception when invoking flow action: {0}
Description
An error occured when invoking a flow action. Check the causal Explanation
An error occurred when the action of a flow was invoked. Variables
{0}
exception message
System action
Inform the user. User action
Check the causal exception for more information.
CWSXM1024E: The reference {0} for callout {1} is undefined.
Description
The reference representing the callout is not defined Explanation
The reference for the callout is not defined on the mediation component. Variables
{0}
reference
{1}
callout name
System action
Inform the user. User action
Check the validity and correct deployment of the mediation component.
CWSXM1025E: An unexpected exception occurred during flow invocation: {0}
Description
An unexpected exception has occured during the processing Explanation
This exception is unexpected. The cause is not immediately known. Variables
{0}
Exception message
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM1026E: Null is an invalid argument for a datasource JNDI name.
Description
A mediation primitive tried to locate a datasource with a null JNDI name. Explanation
A mediation primitive tried to locate a datasource with a null JNDI name. Variables
None.
System action
Inform the user. User action
Ensure that the JNDI name is valid.
CWSXM1027E: An exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
Description
An exception occurred when attempting to obtain a datasource from JNDI. Explanation
The datasource with the JNDI name ''{0}'' could not be located. The causal exception if available will contain more information. Variables
{0}
JNDI name
System action
Inform the user. User action
Ensure that the JNDI service is available and an appropriate datasource has been configured.
CWSXM1028E: A class cast exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
Description
A class cast exception occurred when attempting to obtained a datasource from JNDI. Explanation
The object with the JNDI name ''{0}'' was not of type DataSource. The causal exception if available will contain more information. Variables
{0}
JNDI name
System action
Inform the user. User action
Ensure that the object bound into JNDI is a DataSource.
CWSXM1032E: Reference {0} for custom mediation {1} does not define an operation named {2}
Description
The operation to be called for a custom mediation does not Explanation
There is no operation of the specified name defined on the reference for the custom mediation. Variables
{0}
Reference name
{1}
custom mediation name
{2}
operation name
System action
Inform the user. User action
Check the configuration of the custom mediation.
CWSXM1033E: Reference {0} for custom mediation {1} defines a one way interface.
Description
The interface of the custom mediation defines a one-way Explanation
Custom mediations may only define a two-way interface. Variables
{0}
Reference name
{1}
custom mediation name
System action
Inform the user. User action
Check the configuration of the custom mediation.
CWSXM2003E: The ServiceMessageObject''s contents did not meet its constraints.
Description
The contents of the ServiceMessageObject did not meet its constraints 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. Variables
None.
System action
Inform the user. 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}
Description
The contents of the ServiceMessageObject are not of the expected type 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. Variables
{0}
Expected type
System action
Inform the user. 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.
Description
The body of the ServiceMessageObject is not set Explanation
A ServiceMessageObject was found to have no body, but validation required the SMO body to be set. Variables
None.
System action
Inform the user. User action
Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect.
CWSXM3000E: {0} is not a valid value for property ''{1}''
Description
A setter method on a mediation primitive has been called with 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. Variables
{0}
Value
{1}
Property name
System action
Inform the user. User action
Correct the configuration of the mediation primitive.
CWSXM3001E: Property ''{0}'' is not set.
Description
The issuing object is being used, but a required property Explanation
The mediation primitives configuration is missing a required property. Usually this means that the mediation configuration is not correct. Variables
{0}
Property name
System action
Inform the user. User action
Correct the configuration of the mediation primitive.
CWSXM3002E: MediationServices object not set.
Description
The mediation flow engine has attempted to use a mediation primitive before Explanation
The mediation primitives configuration was incomplete. Variables
None.
System action
Inform the user. User action
Ensure that the configuration of the mediation primitive and mediation flow is valid.
CWSXM3003E: Input message is null.
Description
A mediation primitive was called with a null message parameter Explanation
A mediation primitive was invoked without a message to mediate. Variables
None.
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM3004E: Mediation parameter is null for property ''{0}''
Description
A setter method on a mediation primitive has been called with Explanation
A null value is not valid for the named property. Variables
None.
System action
Inform the user. User action
A setter method on a mediation primitive has been called with a null value. This is not allowed. Usually this means that the mediation configuration is not correct.
CWSXM3005E: SCAServices object not set.
Description
The mediation flow engine has attempted to use a mediation primitive before Explanation
The mediation primitives configuration was incomplete. Variables
None.
System action
Inform the user. User action
Ensure that the configuration of the mediation primitive and mediation flow is valid.
CWSXM3006E: RuntimeServices object not set.
Description
The mediation flow engine has attempted to use a mediation primitive before Explanation
The mediation primitives configuration was incomplete. Variables
None.
System action
Inform the user. User action
Ensure that the configuration of the mediation primitive and mediation flow is valid.
CWSXM3007E: The mediation primitive was called with a message which was not a ServiceMessageObject.
Description
The mediation primitive was called with a message not of type ServiceMessageObject Explanation
The mediation primitive attempted to mediate a message which was not a ServiceMessageObject. This is not allowed. Variables
None.
System action
Inform the user. User action
Ensure that the configuration of the mediation flow is valid.
CWSXM3100E: Root property evaluated to null.
Description
Root evaluated to null Explanation
The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. This suggests that the value is not set. Variables
None.
System action
Inform the user. User action
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.
Description
Root evaluated to multiple elements 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. Variables
None.
System action
Inform the user. User action
Correct the Root property.
CWSXM3102E: Root property evaluated to a {0}
Description
Root evaluated to non-DataObject 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. Variables
{0}
Type of object
System action
Inform the user. User action
Correct the Root property.
CWSXM3103E: Exception while evaluating the Root property.
Description
Exception while evaluating Root property Explanation
An Exception was caught while XSLTransform was evaluating the Root, prior to transformation. Variables
None.
System action
Inform the user. User action
Use the nested Exception to diagnose the problem.
CWSXM3104E: Exception while generating XML prior to transformation.
Description
Exception while serializing DataObject prior to transformation Explanation
The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation. Variables
None.
System action
Inform the user. User action
Use the nested Exception to diagnose the problem.
CWSXM3105E: Exception during transformation.
Description
Exception during transformation Explanation
An Exception occurred during XSL transformation. Variables
None.
System action
Inform the user. User action
Use the nested Exception to diagnose the problem.
CWSXM3106E: Exception while parsing transformed XML.
Description
Exception while parsing transformed XML Explanation
The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject. Variables
None.
System action
Inform the user. User action
Use the nested Exception to diagnose the problem.
CWSXM3107E: Exception while setting the transformed DataObject back into the root location.
Description
Exception while setting transformed DataObject into ServiceMessageObject Explanation
The XSL transformation completed successfully, but the transformed DataObject could not be set into the root position in the ServiceMessageObject. Variables
None.
System action
Inform the user. User action
Use the nested Exception to diagnose the problem.
CWSXM3108E: XSLTransform could not find or load the stylesheet ''{0}''
Description
The specified XSL transform file was not found Explanation
The XSLTransform property named the given file, which was not found at runtime. Variables
{0}
filename
System action
Inform the user. User action
Correct the XSLTransform property, or make the stylesheet available.
CWSXM3109E: Unexpected Exception while initializing the XSL transformation engine.
Description
Unexpected Exception while initializing the XSL transformer Explanation
This exception is unexpected. The cause is not immediately known. Variables
None.
System action
Inform the user. User action
If the problem persists, see problem determination information on the WebSphere ESB Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSXM3110E: Exception while initializing the XSL transformation engine with stylesheet ''{0}''
Description
Exception while initializing the XSL transformer Explanation
An Exception was caught while initializing the XSL transformation engine. This usually indicates a syntax or other error relating to the source stylesheet. Variables
{0}
Stylesheet filename
System action
Inform the user. User action
Inspect the nested exception to diagnose the problem.
CWSXM3150E: Unable to connect to the database using datasource ''{0}''. Refer to the nested exception for more information.
Description
Unable to obtain the connection to the database Explanation
Unable to obtain a connection to the database. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the database is available for connection and any authentication settings have been configured.
CWSXM3151E: Database schema is invalid for the ''{0}'' primitive.
Description
The database schema is invalid Explanation
The database schema is invalid for the named primitive. Variables
{0}
Database schema name.
System action
Inform the user. User action
Ensure that the database schema conforms to the IBM supplied schema. Please refer to the documentation to locate the schema.
CWSXM3152E: 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. Please refer to the nested exception for more information.
Description
Unable to interpret the database to store the message information. This exception might occur in a number of cases such as invalid database schema, Explanation
Unable to access the database to store the message. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the correct access rights have been set, the database is available and the schema conforms to the IBM supplied schema.
CWSXM3153E: Unable to serialize the message information as an XML document.
Description
Unable to convert the message into XML. Explanation
Unable to serialize the message information as an XML document. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the message being mediated is valid.
CWSXM3154E: Unable to store the message within the configured transaction.
Description
Unable to store the message within the configured transaction. Explanation
This exception is unexpected. The cause is not immediately known. Variables
None.
System action
Inform the user. User action
CMSG0002
CWSXM3155E: A problem occurred communicating with the database.
Description
A problem occurred communicating with the database. Explanation
A problem occurred communicating with the database. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the database is available and configured correctly.
CWSXM3201E: Unable to locate a key value from ''{0}'' within the message.
Description
Unable to obtain a value from the location in the message specified as the key into the database. Explanation
An unsuccessful attempt was made to locate a value in the message to be used as a key into the database. Variables
{0}
The location of the key
System action
Inform the user. User action
Ensure that the message contains a value in the specified location.
CWSXM3202E: An exception occurred when attempting to lookup the information in the specified database.
Description
An exception occurred when attempting a lookup the information in the database. Explanation
An exception occurred when attempting to locate the information in the database. Ensure that the mediation primitive is configured to read only from supported database column types. Variables
None.
System action
Inform the user. User action
Check that the database is available and refer to the documentation for supported database column types.
CWSXM3203E: An exception occurred when communicating with the database.
Description
An exception occurred when communicating with the database Explanation
See the nested exception for more information. Variables
None.
System action
Inform the user. User action
Ensure that the database is available and configured correctly.
CWSXM3204E: More than one row was returned from the database column ''{1}'' using the key ''{0}''
Description
More than one row in the database was returned for the key value. The database column must contain unique keys. Explanation
More than one row of data was returned from the database. This is not allowed. Variables
{0}
Database key value
{1}
key column name
System action
Inform the user. User action
Ensure that the database key column only contains unique values.
CWSXM3205E: Unable to obtain a connection to the database.
Description
Unable to obtain the connection to the database Explanation
Unable to obtain a connection to the database. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the database is available for connection and any necessary authentication rights have been configured in the appropriate datasource.
CWSXM3206E: Unable to connect to the database using the property values specified in the mediation primitive.
Description
Unable to connect to the database using the property values specified in the primitive. Explanation
An exception occurred when attempting to read from the database. The nested exception, if available, will contain more information. Variables
None.
System action
Inform the user. User action
Ensure that the property values have been specified correctly because the more probable cause of this exception is an invalid table or column name.
CWSXM3207E: Unable to convert the value of type ''{0}'' which was obtained from the database into the specified type ''{1}''
Description
A value obtained from the database could not be converted to the Java type specified by the user. Explanation
A type mismatch occurred between the type of the value obtained from the database and the type configured in mediation primitive. Variables
{0}
database value type
{1}
message value type
System action
Inform the user. User action
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 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.
Description
An exception was thrown attempting to set a value into the message. Explanation
An exception occurred attempting to set value ''{1}'' into the message at location ''{0}'' Variables
None.
System action
Inform the user. User action
Ensure that the path location is a valid location for the message being mediated.
CWSXM3209E: 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}''
Description
The value obtained from the database was null and could not be stored in the message with a type defined other than String. Explanation
A null value was obtained from the database column using the named key. This is not allowed. Variables
{0}
message value type
{1}
key
{2}
key column name
System action
Inform the user. User action
Ensure that the value contained in the database is compatible with the message element type.
CWSXM3210E: The value obtained from the message at location ''{0}'' did not return a single element to be used as a key into the database.
Description
The value from the message to be used as the key into the database is either a Collection or a DataElement and is not a valid value 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. Variables
{0}
key path location
System action
Inform the user. User action
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.
Description
The list of Filter objects contains a null entry Explanation
A MessageFilter primitive configuration contains a null Filter definition. Usually this means that the mediation flow configuration is not correct. Variables
None.
System action
Inform the user. User action
Correct the mediation flow configuration.
CWSXM3251E: The list of filter expressions contains duplicate terminal name ''{0}''
Description
The list of Filter objects contains a duplicate terminal name Explanation
A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name. Variables
{0}
Duplicated terminal name
System action
Inform the user. User action
Correct the mediation primitive configuration, ensuring that terminal names are used only once for a MessageFilter primitive.
CWSXM3300E: Fail primitive component ''{0}'', module ''{1}'', reference ''{2}'', interface ''{3}'' raised a FailFlowException. The user-supplied error message is ''{4}''
Description
A Fail Primitive has raised a FailFlowException. This is expected behaviour. The Fail primitive identified has been fired and has Explanation
A Fail mediation primitive has raised a FailFlowException. Variables
{0}
component name
{1}
module name
{2}
reference name
{3}
interface name
{4}
user-supplied error message
System action
Inform the user. User action
Examine any user-supplied error message.
CWSXM3401E: Incorrect parameters given. Usage: {0}
Description
Incorrect parameters passed to script Explanation
The script was called with an incorrect set of parameters. Variables
{0}
script usage message
System action
Inform the user User action
Call the script again with parameters described in the message.
CWSXM3402E: -createDb cannot be used in a Network Deployment environment.
Description
Script cannot create a database in ND Explanation
The "-createDb" option creates an embedded Cloudscape database. Variables
None.
System action
Inform the user 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}.
Description
Script cannot be used for multiple servers per node Explanation
There is more than one server configured for the node. Variables
{0}
number of servers
{1}
node name
System action
Inform the user User action
See the InfoCenter for instructions on how to create data sources for multiple servers.
CWSXM3404I: Saving configuration.
Description
Saving the configuration changes Explanation
The configuration changes are being saved. Variables
None.
System action
none User action
None.
CWSXM3405I: Data source configuration completed successfully.
Description
Configuration changes were successful Explanation
The data source configuration changes have been completed. Variables
None.
System action
none User action
None.
CWSXM3406I: Data source for {0} already exists.
Description
Data source exists Explanation
A data source with the specified JNDI name already exists. Variables
{0}
data source JNDI name
System action
none User action
None.
CWSXM3407I: Data source for {0} does not exist.
Description
Data source does not exist Explanation
A data source with the specified JNDI name does not exist. Variables
{0}
data source JNDI name
System action
none User action
None.
CWSXM3408I: Database {0} already exists.
Description
Database exists Explanation
A database with the specified location and name already exists. Variables
{0}
database directory
System action
none User action
None.
CWSXM3409I: Database {0} does not exist.
Description
Database does not exist Explanation
A database with the specified location and name does not exist. Variables
{0}
database directory
System action
none User action
None.
CWSXM3410E: Database {0} already exists.
Description
Database exists Explanation
The script cannot create a database in the named location because a database already exists there. Variables
{0}
database directory
System action
Inform User User action
Check whether the database has already been installed correctly. If not, check 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}"
Description
ij command cannot be found 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. Variables
{0}
expected location of ij command
System action
Inform User User action
Reinstall the application server to repair the installation.
CWSXM3412I: Creating DDL file {0}
Description
ddl file is being created Explanation
The script is creating the DDL file for the Cloudscape database. Variables
{0}
location of the ddl file
System action
none User action
None.
CWSXM3413I: Creating Cloudscape database. See log file for details at {0}
Description
database is being created Explanation
The script is creating a Cloudscape database using the DDL file. The results of the database creation are saved to a log file. Variables
{0}
location of the log file
System action
none User action
None.
CWSXM3414E: Configuration failed. JDBC provider {0} does not exist.
Description
jdbc provider does not exist Explanation
The script needs this JDBC provider to configure the data source. Variables
{0}
jdbc provider name
System action
Inform user User action
Restore the named JDBC provider or manually configure the data source.
CWSXM3415E: Data source for {0} already exists.
Description
Data source exists Explanation
A data source with the specified JNDI name already exists. Variables
{0}
data source JNDI name
System action
Inform user 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.
Description
CMP connection factory exists Explanation
The script cannot continue because the connection factory it would create already exists. Variables
{0}
CMP connection factory name
System action
Inform user 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}
Description
Creating datasource Explanation
The script is creating a data source for the named JDBC provider. Variables
{0}
datasource name
{1}
jdbc provider name
System action
None User action
None.
CWSXM3418I: Configuring data source {0}
Description
Configuring datasource Explanation
The script is creating the data source configuration object. Variables
{0}
datasource name
System action
None User action
None.
CWSXM3419I: Creating CMP connection factory for data source {0}
Description
Creating CMP connection factory Explanation
The script is creating a CMP connection factory for the data source. Variables
{0}
datasource name
System action
None User action
None.
CWSXM3420I: Successfully removed CMP connection factory {0}
Description
Deleted CMP connection factory Explanation
The script has removed the connection factory used by the data source. Variables
{0}
CMP connection factory
System action
None User action
None.
CWSXM3421W: Cannot find CMP connection factory {0}
Description
Cannot find CMP connection factory Explanation
The CMP connection factory associated with the data source was not found. Variables
{0}
CMP connection factory
System action
None User action
Check whether the CMP connection factory exists and manually remove it.
CWSXM3422I: Successfully removed data source {0}
Description
Deleted data source Explanation
The script has removed the data source. Variables
{0}
datasource name
System action
None User action
None.
CWSXM3423W: Cannot find data source {0}
Description
Cannot find data source Explanation
The data source was not found. Variables
{0}
datasource name
System action
None User action
Check whether the data source exists and manually remove it.
CWSXM3424E: Node name and server name must be specified in a Network Deployment environment.
Description
Node name and server name must be specified Explanation
The script was used in a Network Deployment environment but the node name and server name were not specified on the command line. Variables
None.
System action
None User action
Call the script again specifying the node name and server name on the command line
CWSXM3425E: The node name ''{0}'' or server name ''{1}'' are invalid.
Description
Node name or server name are invalid Explanation
The node and server name combination could not be found. Variables
{0}
node name
{1}
server name
System action
None User action
Call the script again specifying a valid node name and server name
CWSXM3426I: Created Cloudscape database successfully.
Description
database created successfully Explanation
The script has created a Cloudscape database using the DDL file. Variables
None.
System action
none User action
None.
CWSXM3427E: Cloudscape database creation encountered errors. See log file for details at {0}
Description
Errors detected when creating database Explanation
The script attempted to create a Cloudscape database using the DDL file. The results of the database creation are saved to a log file. Variables
{0}
location of the log file
System action
none User action
Check the log file for problems creating the database.
CWSXM3428I: The Cloudscape database will not be deleted. If the database is no longer required then it must be removed manually.
Description
User can remove database manually Explanation
The script does not remove the database. Variables
None.
System action
none User action
If desired, remove the database manually.
CWSXM3429E: Cannot create the requested dbLocation {0}. {1}
Description
Error detected when accessing the database location Explanation
The script cannot write files to the location specified in the -dbLocation parameter Variables
{0}
location of the Cloudscape database
{1}
possible error message from jacl command
System action
none User action
If the location exists, check it is a directory, and the script has write access. If the location does not exist, check the script has write access to the parent directory.
CWSXM4000E: Error parsing the Mediation Flow definition: unexpected format.
Description
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Explanation
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4001E: Error parsing the Mediation Flow definition: cannot parse the terminal type.
Description
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Explanation
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4002E: Error parsing the Mediation Flow definition: Response flow with no preceding Request flow.
Description
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Explanation
The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4003E: Error parsing the Mediation Flow definition: there are no flows.
Description
Found at runtime while trying to parse the Mediation Flow file produced by the tooling. Explanation
The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4004E: Error parsing the Mediation Flow definition: no Operation Name for node, ''{0}''.
Description
Missing value for the node's Operation Name. Explanation
Missing value for the named node''s Operation Name. Variables
{0}
Node display name.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4005E: Error parsing the Mediation Flow definition: no Reference Name for node, ''{0}''.
Description
Missing value for the node's Reference Name. Explanation
Missing value for the named node''s Reference Name. Variables
{0}
Node display name.
System action
Inform the user. User action
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}'').
Description
Missing value for the Custom Mediation node's Operation Name. Explanation
Missing value for the Custom Mediation node''s Operation Name. Variables
{0}
Custom Mediation node display name
{1}
type of Custom Mediation node.
System action
Inform the user. User action
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}'').
Description
Missing value for the Custom Mediation node's Reference Name. Explanation
Missing value for the Custom Mediation node''s Reference Name. Variables
{0}
Custom Mediation node display name
{1}
type of Custom Mediation node.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4008E: Error parsing the Mediation Flow definition: node name, ''{0}''.
Description
Wrapper giving node name for a more specific exception. Explanation
An exception occurred when parsing the named mediation flow node. Check the causal exception information for more detail. Variables
{0}
Node display name.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4010E: Error parsing the Mediation Flow definition: found {0} InputNodes.
Description
Found zero or more than 1 InputNodes. Explanation
The Request Flow must have one, and only one Input node. Variables
{0}
foundCount (Integer)
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4011E: Error parsing the Mediation Flow definition: Request Flow, Operation Name=''{0}''.
Description
Wrapper giving Request Flow name for a more specific exception. Explanation
An exception occurred when parsing the named mediation flow Request Flow. Check the causal exception information for more detail. Variables
{0}
Flow Operation Name.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4012E: Error parsing the Mediation Flow definition: Response Flow.
Description
Response Flow wrapper of a more specific exception. Explanation
An exception occurred when parsing the mediation flow Response Flow. Check the causal exception information for more detail. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4013E: Error parsing the Mediation Flow definition: Terminal types do not match.
Description
Terminal types not equal on connection. Explanation
The types of the terminals that are connected together must be the same. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4014E: Error parsing the Mediation Flow definition: Node, ''{0}'' has an incorrectly defined or missing terminal.
Description
The node is missing an expected terminal, named with one of the standard names, 'in' or 'out'. Explanation
The node is missing an expected terminal, named with one of the standard names, ''in'' or ''out''. Variables
{0}
Node display name.
System action
Inform the user. User action
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.
Description
Unidentified node type. 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. Variables
{0}
Node display name
{1}
node type.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4025E: Error parsing the Mediation Flow definition: missing value for source Terminal type.
Description
No value for the sub-type of the complex-type for a source terminal in a connection. Explanation
No value for the sub-type of the complex-type for a source terminal in a connection. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4026E: Error parsing the Mediation Flow definition: missing value for target Terminal type.
Description
No value for the sub-type of the complex-type for a target terminal in a connection. Explanation
No value for the sub-type of the complex-type for a target terminal in a connection. Variables
None.
System action
Inform the user. User action
Verify that the Mediation Flow definition is correct.
CWSXM4100E: Mediation flow component definition file {0} could not be loaded.
Description
The named mediation flow component definition file could not be Explanation
The named mediation flow component definition file could not be loaded. Variables
{0}
File name
System action
Inform the user. User action
Check the validity of the deployed mediation component.
CWSXM4101E: Mediation flow definition file {0} could not be loaded.
Description
The named mediation flow definition file could not be loaded. Explanation
The named mediation flow definition file could not be loaded. Variables
{0}
File name
System action
Inform the user. User action
Check the validity of the deployed mediation component.
CWSXM4102E: Error in parsing mediation flow component definition file {0}: {1}
Description
An exception occurred when parsing the named mediation flow component Explanation
An exception occurred when parsing the named mediation flow component definition file. Check the causal exception information for more detail. Variables
{0}
File name
{1}
exception message
System action
Inform the user. User action
Check the validity of the deployed mediation component.