CWSXMMessages

Messages for SIBX.common component

CWSXM0054E: Key {0} not found in context store when locating correlation information for module {1}

The requested key is not present in the context store.

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

{0}
Context store key
{1}
SCA module name

Inform the user.

CWSXM0055E: Key {0} is already present in the context store when storing correlation information for module {1}

The requested key is already in the context store.

{0}
Context store key
{1}
SCA module name

Inform the user.

CWSXM0100E: Multiple replies have been produced for a single request flow in module {0}

Multiple replies have been produced for a single request flow.

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.

{0}
SCA module name

Inform the user.

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}

Mediation response or fault flow cannot invoke services.

Mediation response and fault flows are not permitted to invoke services.

{0}
SCA module name

Inform the user.

Ensure that the response and fault flows in the module do not invoke services.

CWSXM0102E: The operation {0} cannot be resolved.

Flow Action cannot resolve the named operation.

The named operation cannot be found for the reference that is invoked by the mediation flow.

{0}
Operation name

Inform the user.

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}

The mediation flow session bean for the specified SCA mediation

The requested EJB session bean could not be located.

{0}
the SCA component name
{1}
the SCA module name

Inform the user.

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}

The mediation flow encountered an error when saving context

An internal error occured when saving the context information used by a mediation flow for the given component.

{0}
the SCA component name
{1}
SCA module name

Inform the user.

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}

The mediation flow encountered an error when saving context

An error occured when saving the context information used by a mediation flow for the given component.

{0}
the SCA component name
{1}
SCA module name

Inform the user.

Check the causal exception for more information.

CWSXM0106E: A runtime error occured when receiving a response for mediation component {0} in module {1}

The mediation flow encountered an error when receiving a response

An internal error occured when the mediation flow component processed a response message.

{0}
the SCA component name
{1}
SCA module name

Inform the user.

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}

The mediation flow component encountered an internal error when receiving

An internal error occured when the mediation flow component processed a response message.

{0}
the SCA component name
{1}
SCA module name

Inform the user.

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}

The mediation flow encountered an error when processing an outbound message.

An internal error occured when the mediation flow component was creating an outbound message.

{0}
the SCA component name
{1}
SCA module name

Inform the user.

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}

The mediation flow encountered an error when processing an outbound message.

The reference is connected to multiple services but only a single service can be connected to on a reference in a mediation flow.

{0}
the reference name
{1}
the SCA component name
{2}
SCA module name

Inform the user.

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}

The mediation flow session bean for the specified SCA mediation

The requested mediation flow session bean could not be located.

{0}
the SCA component name
{1}
the SCA module name

Inform the user.

Check the deployment of the mediation flow component.

CWSXM0201E: Exception returned by mediation flow for component {0} in module {1}

The mediation flow for the specified SCA mediation component and

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.

{0}
the SCA component name
{1}
the SCA module name

Inform the user.

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}

An unexpected exception has occured during the processing

{0}
the SCA component name
{1}
the SCA module name

Inform the user.

CWSXM0203E: An unexpected exception occurred when accessing the persistent store for component {0} in module {1}

An unexpected error occurred when accessing the persistent store.

{0}
the SCA component name
{1}
the SCA module name

Inform the user.

CWSXM0204E: A configuration error occurred when invoking a mediation flow.

A configuration error occurred when invoking a mediation flow.

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.

None.

Inform the user.

Check the underlying exception for more details of the cause of the configuration error.

CWSXM0205E: An unexpected business logic exception occurred.

An unexpected business logic exception has occured during the processing

The mediation flow returned an exception that indicated that a business logic error occurred.

None.

Inform the user.

Check the underlying exception for details of the business logic error.

CWSXM0206E: An unexpected exception occurred.

An unexpected exception has occured during the processing

None.

Inform the user.

CWSXM1000E: Could not locate runtime mediation flow for mediation component {0} in module {1}

There is no lightweight flow defined for the specified SCA

No runtime mediation flow definitions were found for the mediation component.

{0}
SCA mediation component name
{1}
SCA module name

Inform the user.

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}

The lightweight request flow model for the specified request flow,

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.

{0}
operation name
{1}
port type
{2}
SCA mediation component name
{3}
SCA module name

Inform the user.

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}

The lightweight response flow model for the specified operation name invoked

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.

{0}
reference operation name
{1}
reference
{2}
SCA mediation component name
{3}
SCA module name

Inform the user.

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}

The lightweight fault flow model for the specified fault message and

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.

{0}
fault name
{1}
reference operation name
{2}
reference
{3}
SCA mediation component name
{4}
SCA module name

Inform the user.

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}

An invalid input is specified for a flow.

The flow has an invalid or unknown input.

{0}
SCA mediation component name
{1}
SCA module name

Inform the user.

Validate the mediation flow definition.

CWSXM1005E: Error whilst instantiating mediation primitive {0}. In mediation component {1} in module {2}

The primitive class could not be loaded. Check the causal

The mediation primitive could not be instantiated.

{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name

Inform the user.

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}

An error occured when setting the properties of the mediation

An error occured whilst trying to set the properties of the mediation primitive.

{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name

Inform the user.

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}

The mediation primitive encountered a configuration error during

During the primitives initialization, the named mediation primitive encountered an error.

{0}
mediation primitive name
{1}
SCA mediation component name
{2}
SCA module name

Inform the user.

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.

The key is not of the expected type. Check the causal exception

The key class is not of the expected type for this flow engine.

{0}
the key class

Inform the user to contact IBM support.

CWSXM1009E: Could not locate the runtime mediation flow for mediation component {0} in module {1}

There was a problem in locating the runtime instance for the SCA

There was a problem in locating the runtime instance of the mediation flow.

{0}
SCA mediation component name
{1}
SCA module name

Inform the user.

Check the causal exception for more information.

CWSXM1010E: Could not locate the runtime mediation flow for mediation component {0} in module {1}

There was a problem in locating the runtime instance for the SCA

There was a problem in locating the runtime instance of the mediation flow.

{0}
SCA mediation component name
{1}
SCA module name

Inform the user.

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}

The mediation engine encountered an error whilst processing the

An internal error occured when invoking the request flow for the operation.

{0}
the operation name
{1}
port type name
{2}
SCA component name
{3}
SCA module name

Inform the user.

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}

The mediation engine encountered an error whilst processing the

An internal error occured when invoking the response flow for the operation on the named reference.

{0}
reference operation name
{1}
reference
{2}
SCA component name
{3}
SCA module name

Inform the user.

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}

The mediation engine encountered an error whilst processing the

An internal error occured when invoking the fault response flow for the fault message and operation on the named reference.

{0}
fault name
{1}
reference operation name
{2}
reference
{3}
SCA component name
{4}
SCA module name

Inform the user.

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.

The reference representing the custom mediation is not defined

The reference for the custom mediation is not defined on the mediation component.

{0}
reference
{1}
custom mediation name

Inform the user.

Check the validity and correct deployment of the mediation component.

CWSXM1017E: Request flow runtime instance is unavailable.

The request flow runtime instance is not available due to

The request flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.

None.

Inform the user.

Check the validity of the mediation flow component, and check for previous errors.

CWSXM1018E: Response flow runtime instance is unavailable.

The response flow runtime instance is not available due to

The response flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.

None.

Inform the user.

Check the validity of the mediation flow component, and check for previous errors.

CWSXM1019E: Response fault flow runtime instance is unavailable.

The response fault flow runtime instance is not available due to

The response fault flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.

None.

Inform the user.

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}

An unknown exception occured during the processing of the

An unknown exception occurred during the processing of the specified mediation primitive or custom mediation.

{0}
mediation primitive name
{1}
exception message

Inform the user.

Check the causal exception for more information.

CWSXM1021E: No input terminal named {0} defined for mediation primitive {1}

A mediation primitive has attempted to obtain an input terminal

A mediation primitive attempted to obtain an input terminal which does not exist.

{0}
input terminal name
{1}
mediation primitive name

Inform the user.

Check the validity of the mediation flow component.

CWSXM1022E: No output terminal named {0} defined for mediation primitive {1}

A mediation primitive has attempted to obtain an output terminal

A mediation primitive attempted to obtain an output terminal which does not exist.

{0}
output terminal name
{1}
mediation primitive name

Inform the user.

Check the validity of the mediation flow.

CWSXM1023E: Exception when invoking flow action: {0}

An error occured when invoking a flow action. Check the causal

An error occurred when the action of a flow was invoked.

{0}
exception message

Inform the user.

Check the causal exception for more information.

CWSXM1024E: The reference {0} for callout {1} is undefined.

The reference representing the callout is not defined

The reference for the callout is not defined on the mediation component.

{0}
reference
{1}
callout name

Inform the user.

Check the validity and correct deployment of the mediation component.

CWSXM1025E: An unexpected exception occurred during flow invocation: {0}

An unexpected exception has occured during the processing

{0}
Exception message

Inform the user.

CWSXM1026E: Null is an invalid argument for a datasource JNDI name.

A mediation primitive tried to locate a datasource with a null JNDI name.

A mediation primitive tried to locate a datasource with a null JNDI name.

None.

Inform the user.

Ensure that the JNDI name is valid.

CWSXM1027E: An exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''

An exception occurred when attempting to obtain a datasource from JNDI.

The datasource with the JNDI name ''{0}'' could not be located. The causal exception if available will contain more information.

{0}
JNDI name

Inform the user.

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}''

A class cast exception occurred when attempting to obtained a datasource from JNDI.

The object with the JNDI name ''{0}'' was not of type DataSource. The causal exception if available will contain more information.

{0}
JNDI name

Inform the user.

Ensure that the object bound into JNDI is a DataSource.

CWSXM1032E: Reference {0} for custom mediation {1} does not define an operation named {2}

The operation to be called for a custom mediation does not

There is no operation of the specified name defined on the reference for the custom mediation.

{0}
Reference name
{1}
custom mediation name
{2}
operation name

Inform the user.

Check the configuration of the custom mediation.

CWSXM1033E: Reference {0} for custom mediation {1} defines a one way interface.

The interface of the custom mediation defines a one-way

Custom mediations may only define a two-way interface.

{0}
Reference name
{1}
custom mediation name

Inform the user.

Check the configuration of the custom mediation.

CWSXM2003E: The ServiceMessageObject''s contents did not meet its constraints.

The contents of the ServiceMessageObject did not meet its constraints

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.

None.

Inform the user.

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}

The contents of the ServiceMessageObject are not of the expected type

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.

{0}
Expected type

Inform the user.

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.

The body of the ServiceMessageObject is not set

A ServiceMessageObject was found to have no body, but validation required the SMO body to be set.

None.

Inform the user.

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}''

A setter method on a mediation primitive has been called with

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.

{0}
Value
{1}
Property name

Inform the user.

Correct the configuration of the mediation primitive.

CWSXM3001E: Property ''{0}'' is not set.

The issuing object is being used, but a required property

The mediation primitives configuration is missing a required property. Usually this means that the mediation configuration is not correct.

{0}
Property name

Inform the user.

Correct the configuration of the mediation primitive.

CWSXM3002E: MediationServices object not set.

The mediation flow engine has attempted to use a mediation primitive before

The mediation primitives configuration was incomplete.

None.

Inform the user.

Ensure that the configuration of the mediation primitive and mediation flow is valid.

CWSXM3003E: Input message is null.

A mediation primitive was called with a null message parameter

A mediation primitive was invoked without a message to mediate.

None.

Inform the user.

CWSXM3004E: Mediation parameter is null for property ''{0}''

A setter method on a mediation primitive has been called with

A null value is not valid for the named property.

None.

Inform the user.

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.

The mediation flow engine has attempted to use a mediation primitive before

The mediation primitives configuration was incomplete.

None.

Inform the user.

Ensure that the configuration of the mediation primitive and mediation flow is valid.

CWSXM3006E: RuntimeServices object not set.

The mediation flow engine has attempted to use a mediation primitive before

The mediation primitives configuration was incomplete.

None.

Inform the user.

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.

The mediation primitive was called with a message not of type ServiceMessageObject

The mediation primitive attempted to mediate a message which was not a ServiceMessageObject. This is not allowed.

None.

Inform the user.

Ensure that the configuration of the mediation flow is valid.

CWSXM3100E: Root property evaluated to null.

Root evaluated to null

The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. This suggests that the value is not set.

None.

Inform the user.

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.

Root evaluated to multiple elements

The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. However, in the message being mediated, it evaluated to multiple elements.

None.

Inform the user.

Correct the Root property.

CWSXM3102E: Root property evaluated to a {0}

Root evaluated to non-DataObject

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.

{0}
Type of object

Inform the user.

Correct the Root property.

CWSXM3103E: Exception while evaluating the Root property.

Exception while evaluating Root property

An Exception was caught while XSLTransform was evaluating the Root, prior to transformation.

None.

Inform the user.

Use the nested Exception to diagnose the problem.

CWSXM3104E: Exception while generating XML prior to transformation.

Exception while serializing DataObject prior to transformation

The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation.

None.

Inform the user.

Use the nested Exception to diagnose the problem.

CWSXM3105E: Exception during transformation.

Exception during transformation

An Exception occurred during XSL transformation.

None.

Inform the user.

Use the nested Exception to diagnose the problem.

CWSXM3106E: Exception while parsing transformed XML.

Exception while parsing transformed XML

The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject.

None.

Inform the user.

Use the nested Exception to diagnose the problem.

CWSXM3107E: Exception while setting the transformed DataObject back into the root location.

Exception while setting transformed DataObject into ServiceMessageObject

The XSL transformation completed successfully, but the transformed DataObject could not be set into the root position in the ServiceMessageObject.

None.

Inform the user.

Use the nested Exception to diagnose the problem.

CWSXM3108E: XSLTransform could not find or load the stylesheet ''{0}''

The specified XSL transform file was not found

The XSLTransform property named the given file, which was not found at runtime.

{0}
filename

Inform the user.

Correct the XSLTransform property, or make the stylesheet available.

CWSXM3109E: Unexpected Exception while initializing the XSL transformation engine.

Unexpected Exception while initializing the XSL transformer

None.

Inform the user.

CWSXM3110E: Exception while initializing the XSL transformation engine with stylesheet ''{0}''

Exception while initializing the XSL transformer

An Exception was caught while initializing the XSL transformation engine. This usually indicates a syntax or other error relating to the source stylesheet.

{0}
Stylesheet filename

Inform the user.

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.

Unable to obtain the connection to the database

Unable to obtain a connection to the database. The nested exception, if available, will contain more information.

None.

Inform the user.

Ensure that the database is available for connection and any authentication settings have been configured.

CWSXM3151E: Database schema is invalid for the ''{0}'' primitive.

The database schema is invalid

The database schema is invalid for the named primitive.

{0}
Database schema name.

Inform the user.

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.

Unable to interpret the database to store the message information. This exception might occur in a number of cases such as invalid database schema,

Unable to access the database to store the message. The nested exception, if available, will contain more information.

None.

Inform the user.

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.

Unable to convert the message into XML.

Unable to serialize the message information as an XML document. The nested exception, if available, will contain more information.

None.

Inform the user.

Ensure that the message being mediated is valid.

CWSXM3154E: Unable to store the message within the configured transaction.

Unable to store the message within the configured transaction.

None.

Inform the user.

If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wsesb/support/.

CWSXM3155E: A problem occurred communicating with the database.

A problem occurred communicating with the database.

A problem occurred communicating with the database. The nested exception, if available, will contain more information.

None.

Inform the user.

Ensure that the database is available and configured correctly.

CWSXM3201E: Unable to locate a key value from ''{0}'' within the message.

Unable to obtain a value from the location in the message specified as the key into the database.

An unsuccessful attempt was made to locate a value in the message to be used as a key into the database.

{0}
The location of the key

Inform the user.

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.

An exception occurred when attempting a lookup the information in the database.

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.

None.

Inform the user.

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.

An exception occurred when communicating with the database

See the nested exception for more information.

None.

Inform the user.

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}''

More than one row in the database was returned for the key value. The database column must contain unique keys.

More than one row of data was returned from the database. This is not allowed.

{0}
Database key value
{1}
key column name

Inform the user.

Ensure that the database key column only contains unique values.

CWSXM3205E: Unable to obtain a connection to the database.

Unable to obtain the connection to the database

Unable to obtain a connection to the database. The nested exception, if available, will contain more information.

None.

Inform the user.

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.

Unable to connect to the database using the property values specified in the primitive.

An exception occurred when attempting to read from the database. The nested exception, if available, will contain more information.

None.

Inform the user.

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}''

A value obtained from the database could not be converted to the Java type specified by the user.

A type mismatch occurred between the type of the value obtained from the database and the type configured in mediation primitive.

{0}
database value type
{1}
message value type

Inform the user.

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.

An exception was thrown attempting to set a value into the message.

An exception occurred attempting to set value ''{1}'' into the message at location ''{0}''

None.

Inform the user.

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}''

The value obtained from the database was null and could not be stored in the message with a type defined other than String.

A null value was obtained from the database column using the named key. This is not allowed.

{0}
message value type
{1}
key
{2}
key column name

Inform the user.

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.

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

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.

{0}
key path location

Inform the user.

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.

The list of Filter objects contains a null entry

A MessageFilter primitive configuration contains a null Filter definition. Usually this means that the mediation flow configuration is not correct.

None.

Inform the user.

Correct the mediation flow configuration.

CWSXM3251E: The list of filter expressions contains duplicate terminal name ''{0}''

The list of Filter objects contains a duplicate terminal name

A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name.

{0}
Duplicated terminal name

Inform the user.

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}''

A Fail Primitive has raised a FailFlowException. This is expected behaviour. The Fail primitive identified has been fired and has

A Fail mediation primitive has raised a FailFlowException.

{0}
component name
{1}
module name
{2}
reference name
{3}
interface name
{4}
user-supplied error message

Inform the user.

Examine any user-supplied error message.

CWSXM3401E: Incorrect parameters given. Usage: {0}

Incorrect parameters passed to script

The script was called with an incorrect set of parameters.

{0}
script usage message

Inform the user

Call the script again with parameters described in the message.

CWSXM3402E: -createDb cannot be used in a Network Deployment environment.

Script cannot create a database in ND

The "-createDb" option creates an embedded Cloudscape database.

None.

Inform the user

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}.

Script cannot be used for multiple servers per node

There is more than one server configured for the node.

{0}
number of servers
{1}
node name

Inform the user

See the InfoCenter for instructions on how to create data sources for multiple servers.

CWSXM3404I: Saving configuration.

Saving the configuration changes

The configuration changes are being saved.

None.

none

None.

CWSXM3405I: Data source configuration completed successfully.

Configuration changes were successful

The data source configuration changes have been completed.

None.

none

None.

CWSXM3406I: Data source for {0} already exists.

Data source exists

A data source with the specified JNDI name already exists.

{0}
data source JNDI name

none

None.

CWSXM3407I: Data source for {0} does not exist.

Data source does not exist

A data source with the specified JNDI name does not exist.

{0}
data source JNDI name

none

None.

CWSXM3408I: Database {0} already exists.

Database exists

A database with the specified location and name already exists.

{0}
database directory

none

None.

CWSXM3409I: Database {0} does not exist.

Database does not exist

A database with the specified location and name does not exist.

{0}
database directory

none

None.

CWSXM3410E: Database {0} already exists.

Database exists

The script cannot create a database in the named location because a database already exists there.

{0}
database directory

Inform User

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}"

ij command cannot be found

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.

{0}
expected location of ij command

Inform User

Reinstall the application server to repair the installation.

CWSXM3412I: Creating DDL file {0}

ddl file is being created

The script is creating the DDL file for the Cloudscape database.

{0}
location of the ddl file

none

None.

CWSXM3413I: Creating Cloudscape database. See log file for details at {0}

database is being created

The script is creating a Cloudscape database using the DDL file. The results of the database creation are saved to a log file.

{0}
location of the log file

none

None.

CWSXM3414E: Configuration failed. JDBC provider {0} does not exist.

jdbc provider does not exist

The script needs this JDBC provider to configure the data source.

{0}
jdbc provider name

Inform user

Restore the named JDBC provider or manually configure the data source.

CWSXM3415E: Data source for {0} already exists.

Data source exists

A data source with the specified JNDI name already exists.

{0}
data source JNDI name

Inform user

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.

CMP connection factory exists

The script cannot continue because the connection factory it would create already exists.

{0}
CMP connection factory name

Inform user

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}

Creating datasource

The script is creating a data source for the named JDBC provider.

{0}
datasource name
{1}
jdbc provider name

None

None.

CWSXM3418I: Configuring data source {0}

Configuring datasource

The script is creating the data source configuration object.

{0}
datasource name

None

None.

CWSXM3419I: Creating CMP connection factory for data source {0}

Creating CMP connection factory

The script is creating a CMP connection factory for the data source.

{0}
datasource name

None

None.

CWSXM3420I: Successfully removed CMP connection factory {0}

Deleted CMP connection factory

The script has removed the connection factory used by the data source.

{0}
CMP connection factory

None

None.

CWSXM3421W: Cannot find CMP connection factory {0}

Cannot find CMP connection factory

The CMP connection factory associated with the data source was not found.

{0}
CMP connection factory

None

Check whether the CMP connection factory exists and manually remove it.

CWSXM3422I: Successfully removed data source {0}

Deleted data source

The script has removed the data source.

{0}
datasource name

None

None.

CWSXM3423W: Cannot find data source {0}

Cannot find data source

The data source was not found.

{0}
datasource name

None

Check whether the data source exists and manually remove it.

CWSXM3424E: Node name and server name must be specified in a Network Deployment environment.

Node name and server name must be specified

The script was used in a Network Deployment environment but the node name and server name were not specified on the command line.

None.

None

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.

Node name or server name are invalid

The node and server name combination could not be found.

{0}
node name
{1}
server name

None

Call the script again specifying a valid node name and server name

CWSXM3426I: Created Cloudscape database successfully.

database created successfully

The script has created a Cloudscape database using the DDL file.

None.

none

None.

CWSXM3427E: Cloudscape database creation encountered errors. See log file for details at {0}

Errors detected when creating database

The script attempted to create a Cloudscape database using the DDL file. The results of the database creation are saved to a log file.

{0}
location of the log file

none

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.

User can remove database manually

The script does not remove the database.

None.

none

If desired, remove the database manually.

CWSXM3429E: Cannot create the requested dbLocation {0}. {1}

Error detected when accessing the database location

The script cannot write files to the location specified in the -dbLocation parameter

{0}
location of the Cloudscape database
{1}
possible error message from jacl command

none

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.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4001E: Error parsing the Mediation Flow definition: cannot parse the terminal type.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4002E: Error parsing the Mediation Flow definition: Response flow with no preceding Request flow.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4003E: Error parsing the Mediation Flow definition: there are no flows.

Found at runtime while trying to parse the Mediation Flow file produced by the tooling.

The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4004E: Error parsing the Mediation Flow definition: no Operation Name for node, ''{0}''.

Missing value for the node's Operation Name.

Missing value for the named node''s Operation Name.

{0}
Node display name.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4005E: Error parsing the Mediation Flow definition: no Reference Name for node, ''{0}''.

Missing value for the node's Reference Name.

Missing value for the named node''s Reference Name.

{0}
Node display name.

Inform the user.

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}'').

Missing value for the Custom Mediation node's Operation Name.

Missing value for the Custom Mediation node''s Operation Name.

{0}
Custom Mediation node display name
{1}
type of Custom Mediation node.

Inform the user.

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}'').

Missing value for the Custom Mediation node's Reference Name.

Missing value for the Custom Mediation node''s Reference Name.

{0}
Custom Mediation node display name
{1}
type of Custom Mediation node.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4008E: Error parsing the Mediation Flow definition: node name, ''{0}''.

Wrapper giving node name for a more specific exception.

An exception occurred when parsing the named mediation flow node. Check the causal exception information for more detail.

{0}
Node display name.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4010E: Error parsing the Mediation Flow definition: found {0} InputNodes.

Found zero or more than 1 InputNodes.

The Request Flow must have one, and only one Input node.

{0}
foundCount (Integer)

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4011E: Error parsing the Mediation Flow definition: Request Flow, Operation Name=''{0}''.

Wrapper giving Request Flow name for a more specific exception.

An exception occurred when parsing the named mediation flow Request Flow. Check the causal exception information for more detail.

{0}
Flow Operation Name.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4012E: Error parsing the Mediation Flow definition: Response Flow.

Response Flow wrapper of a more specific exception.

An exception occurred when parsing the mediation flow Response Flow. Check the causal exception information for more detail.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4013E: Error parsing the Mediation Flow definition: Terminal types do not match.

Terminal types not equal on connection.

The types of the terminals that are connected together must be the same.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4014E: Error parsing the Mediation Flow definition: Node, ''{0}'' has an incorrectly defined or missing terminal.

The node is missing an expected terminal, named with one of the standard names, 'in' or 'out'.

The node is missing an expected terminal, named with one of the standard names, ''in'' or ''out''.

{0}
Node display name.

Inform the user.

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.

Unidentified node type.

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.

{0}
Node display name
{1}
node type.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4025E: Error parsing the Mediation Flow definition: missing value for source Terminal type.

No value for the sub-type of the complex-type for a source terminal in a connection.

No value for the sub-type of the complex-type for a source terminal in a connection.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4026E: Error parsing the Mediation Flow definition: missing value for target Terminal type.

No value for the sub-type of the complex-type for a target terminal in a connection.

No value for the sub-type of the complex-type for a target terminal in a connection.

None.

Inform the user.

Verify that the Mediation Flow definition is correct.

CWSXM4100E: Mediation flow component definition file {0} could not be loaded.

The named mediation flow component definition file could not be

The named mediation flow component definition file could not be loaded.

{0}
File name

Inform the user.

Check the validity of the deployed mediation component.

CWSXM4101E: Mediation flow definition file {0} could not be loaded.

The named mediation flow definition file could not be loaded.

The named mediation flow definition file could not be loaded.

{0}
File name

Inform the user.

Check the validity of the deployed mediation component.

CWSXM4102E: Error in parsing mediation flow component definition file {0}: {1}

An exception occurred when parsing the named mediation flow component

An exception occurred when parsing the named mediation flow component definition file. Check the causal exception information for more detail.

{0}
File name
{1}
exception message

Inform the user.

Check the validity of the deployed mediation component.


Terms of use |

Last updated: Tue Feb 21 17:57:13 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)