Messages for SIBX.common component
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
Inform the user.
The requested key is already in the context store.
Inform the user.
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.
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.
Mediation response or fault flow cannot invoke services.
Mediation response and fault flows are not permitted to invoke services.
Inform the user.
Ensure that the response and fault flows in the module do not invoke services.
Flow Action cannot resolve the named operation.
The named operation cannot be found for the reference that is invoked by the mediation flow.
Inform the user.
Ensure that the operation name that is used in the mediation flow is correct.
The mediation flow session bean for the specified SCA mediation
The requested EJB session bean could not be located.
Inform the user.
Check the deployment of the mediation flow component.
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.
Inform the user.
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
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.
Inform the user.
Check the causal exception for more information.
The mediation flow encountered an error when receiving a response
An internal error occured when the mediation flow component processed a response message.
Inform the user.
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
The mediation flow component encountered an internal error when receiving
An internal error occured when the mediation flow component processed a response message.
Inform the user.
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
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.
Inform the user.
Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
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.
Inform the user.
Check the validity of the mediation flow and the validity of references that are invoked.
The mediation flow session bean for the specified SCA mediation
The requested mediation flow session bean could not be located.
Inform the user.
Check the deployment of the mediation flow component.
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.
Inform the user.
Check the mediation flow to ensure that all failure terminals on primitives are wired.
An unexpected exception has occured during the processing
Inform the user.
An unexpected error occurred when accessing the persistent store.
Inform the user.
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.
Inform the user.
Check the underlying exception for more details of the cause of the configuration error.
An unexpected business logic exception has occured during the processing
The mediation flow returned an exception that indicated that a business logic error occurred.
Inform the user.
Check the underlying exception for details of the business logic error.
An unexpected exception has occured during the processing
Inform the user.
There is no lightweight flow defined for the specified SCA
No runtime mediation flow definitions were found for the mediation component.
Inform the user.
Check the mediation component has a mediation flow defined and check for any earlier exceptions in loading the definition.
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.
Inform the user.
Verify that the mediation component has a request flow defined for the operation.
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.
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.
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.
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.
An invalid input is specified for a flow.
The flow has an invalid or unknown input.
Inform the user.
Validate the mediation flow definition.
The primitive class could not be loaded. Check the causal
The mediation primitive could not be instantiated.
Inform the user.
Validate the mediation flow definition, and check the causal exception for more information.
An error occured when setting the properties of the mediation
An error occured whilst trying to set the properties of the mediation primitive.
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.
The mediation primitive encountered a configuration error during
During the primitives initialization, the named mediation primitive encountered an error.
Inform the user.
Verify that the configuration of the mediation primitive in the mediation flow definition, and check the causal exception for more information.
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.
Inform the user to contact IBM support.
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.
Inform the user.
Check the causal exception for more information.
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.
Inform the user.
Check the causal exception for more information, and validate that the SCA module started with no errors.
The mediation engine encountered an error whilst processing the
An internal error occured when invoking the request flow for the operation.
Inform the user.
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
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.
Inform the user.
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
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.
Inform the user.
Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
The reference representing the custom mediation is not defined
The reference for the custom mediation is not defined on the mediation component.
Inform the user.
Check the validity and correct deployment of the mediation component.
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.
Inform the user.
Check the validity of the mediation flow component, and check for previous errors.
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.
Inform the user.
Check the validity of the mediation flow component, and check for previous errors.
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.
Inform the user.
Check the validity of the mediation flow component, and check for previous errors.
An unknown exception occured during the processing of the
An unknown exception occurred during the processing of the specified mediation primitive or custom mediation.
Inform the user.
Check the causal exception for more information.
A mediation primitive has attempted to obtain an input terminal
A mediation primitive attempted to obtain an input terminal which does not exist.
Inform the user.
Check the validity of the mediation flow component.
A mediation primitive has attempted to obtain an output terminal
A mediation primitive attempted to obtain an output terminal which does not exist.
Inform the user.
Check the validity of the mediation flow.
An error occured when invoking a flow action. Check the causal
An error occurred when the action of a flow was invoked.
Inform the user.
Check the causal exception for more information.
The reference representing the callout is not defined
The reference for the callout is not defined on the mediation component.
Inform the user.
Check the validity and correct deployment of the mediation component.
An unexpected exception has occured during the processing
Inform the user.
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.
Inform the user.
Ensure that the JNDI name is valid.
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.
Inform the user.
Ensure that the JNDI service is available and an appropriate datasource has been configured.
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.
Inform the user.
Ensure that the object bound into JNDI is a DataSource.
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.
Inform the user.
Check the configuration of the custom mediation.
The interface of the custom mediation defines a one-way
Custom mediations may only define a two-way interface.
Inform the user.
Check the configuration of the custom mediation.
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.
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.
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.
Inform the user.
Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect, or correct the expected type.
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.
Inform the user.
Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect.
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.
Inform the user.
Correct the configuration of the mediation primitive.
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.
Inform the user.
Correct the configuration of the mediation primitive.
The mediation flow engine has attempted to use a mediation primitive before
The mediation primitives configuration was incomplete.
Inform the user.
Ensure that the configuration of the mediation primitive and mediation flow is valid.
A mediation primitive was called with a null message parameter
A mediation primitive was invoked without a message to mediate.
Inform the user.
A setter method on a mediation primitive has been called with
A null value is not valid for the named property.
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.
The mediation flow engine has attempted to use a mediation primitive before
The mediation primitives configuration was incomplete.
Inform the user.
Ensure that the configuration of the mediation primitive and mediation flow is valid.
The mediation flow engine has attempted to use a mediation primitive before
The mediation primitives configuration was incomplete.
Inform the user.
Ensure that the configuration of the mediation primitive and mediation flow is valid.
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.
Inform the user.
Ensure that the configuration of the mediation flow is valid.
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.
Inform the user.
Ensure that the configuration of the Root property is set to a valid value.
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.
Inform the user.
Correct the Root property.
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.
Inform the user.
Correct the Root property.
Exception while evaluating Root property
An Exception was caught while XSLTransform was evaluating the Root, prior to transformation.
Inform the user.
Use the nested Exception to diagnose the problem.
Exception while serializing DataObject prior to transformation
The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation.
Inform the user.
Use the nested Exception to diagnose the problem.
Exception during transformation
An Exception occurred during XSL transformation.
Inform the user.
Use the nested Exception to diagnose the problem.
Exception while parsing transformed XML
The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject.
Inform the user.
Use the nested Exception to diagnose the problem.
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.
Inform the user.
Use the nested Exception to diagnose the problem.
The specified XSL transform file was not found
The XSLTransform property named the given file, which was not found at runtime.
Inform the user.
Correct the XSLTransform property, or make the stylesheet available.
Unexpected Exception while initializing the XSL transformer
Inform the user.
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.
Inform the user.
Inspect the nested exception to diagnose the problem.
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.
Inform the user.
Ensure that the database is available for connection and any authentication settings have been configured.
The database schema is invalid
The database schema is invalid for the named primitive.
Inform the user.
Ensure that the database schema conforms to the IBM supplied schema. Please refer to the documentation to locate the schema.
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.
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.
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.
Inform the user.
Ensure that the message being mediated is valid.
Unable to store the message within the configured transaction.
Inform the user.
CMSG0002
A problem occurred communicating with the database.
A problem occurred communicating with the database. The nested exception, if available, will contain more information.
Inform the user.
Ensure that the database is available and configured correctly.
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.
Inform the user.
Ensure that the message contains a value in the specified location.
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.
Inform the user.
Check that the database is available and refer to the documentation for supported database column types.
An exception occurred when communicating with the database
See the nested exception for more information.
Inform the user.
Ensure that the database is available and configured correctly.
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.
Inform the user.
Ensure that the database key column only contains unique values.
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.
Inform the user.
Ensure that the database is available for connection and any necessary authentication rights have been configured in the appropriate datasource.
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.
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.
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.
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.
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}''
Inform the user.
Ensure that the path location is a valid location for the message being mediated.
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.
Inform the user.
Ensure that the value contained in the database is compatible with the message element type.
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.
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.
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.
Inform the user.
Correct the mediation flow configuration.
The list of Filter objects contains a duplicate terminal name
A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name.
Inform the user.
Correct the mediation primitive configuration, ensuring that terminal names are used only once for a MessageFilter primitive.
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.
Inform the user.
Examine any user-supplied error message.
Incorrect parameters passed to script
The script was called with an incorrect set of parameters.
Inform the user
Call the script again with parameters described in the message.
Script cannot create a database in ND
The "-createDb" option creates an embedded Cloudscape database.
Inform the user
See the InfoCenter for instructions on how to install the database in a Network Deployment environment.
Script cannot be used for multiple servers per node
There is more than one server configured for the node.
Inform the user
See the InfoCenter for instructions on how to create data sources for multiple servers.
Saving the configuration changes
The configuration changes are being saved.
none
None.
Configuration changes were successful
The data source configuration changes have been completed.
none
None.
Data source exists
A data source with the specified JNDI name already exists.
none
None.
Data source does not exist
A data source with the specified JNDI name does not exist.
none
None.
Database exists
A database with the specified location and name already exists.
none
None.
Database does not exist
A database with the specified location and name does not exist.
none
None.
Database exists
The script cannot create a database in the named location because a database already exists there.
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.
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.
Inform User
Reinstall the application server to repair the installation.
ddl file is being created
The script is creating the DDL file for the Cloudscape database.
none
None.
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.
none
None.
jdbc provider does not exist
The script needs this JDBC provider to configure the data source.
Inform user
Restore the named JDBC provider or manually configure the data source.
Data source exists
A data source with the specified JNDI name already exists.
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.
CMP connection factory exists
The script cannot continue because the connection factory it would create already exists.
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.
Creating datasource
The script is creating a data source for the named JDBC provider.
None
None.
Configuring datasource
The script is creating the data source configuration object.
None
None.
Creating CMP connection factory
The script is creating a CMP connection factory for the data source.
None
None.
Deleted CMP connection factory
The script has removed the connection factory used by the data source.
None
None.
Cannot find CMP connection factory
The CMP connection factory associated with the data source was not found.
None
Check whether the CMP connection factory exists and manually remove it.
Deleted data source
The script has removed the data source.
None
None.
Cannot find data source
The data source was not found.
None
Check whether the data source exists and manually remove it.
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
Call the script again specifying the node name and server name on the command line
Node name or server name are invalid
The node and server name combination could not be found.
None
Call the script again specifying a valid node name and server name
database created successfully
The script has created a Cloudscape database using the DDL file.
none
None.
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.
none
Check the log file for problems creating the database.
User can remove database manually
The script does not remove the database.
none
If desired, remove the database manually.
Error detected when accessing the database location
The script cannot write files to the location specified in the -dbLocation parameter
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.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
Missing value for the node's Operation Name.
Missing value for the named node''s Operation Name.
Inform the user.
Verify that the Mediation Flow definition is correct.
Missing value for the node's Reference Name.
Missing value for the named node''s Reference Name.
Inform the user.
Verify that the Mediation Flow definition is correct.
Missing value for the Custom Mediation node's Operation Name.
Missing value for the Custom Mediation node''s Operation Name.
Inform the user.
Verify that the Mediation Flow definition is correct.
Missing value for the Custom Mediation node's Reference Name.
Missing value for the Custom Mediation node''s Reference Name.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
Found zero or more than 1 InputNodes.
The Request Flow must have one, and only one Input node.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
Terminal types not equal on connection.
The types of the terminals that are connected together must be the same.
Inform the user.
Verify that the Mediation Flow definition is correct.
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''.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
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.
Inform the user.
Verify that the Mediation Flow definition is correct.
The named mediation flow component definition file could not be
The named mediation flow component definition file could not be loaded.
Inform the user.
Check the validity of the deployed mediation component.
The named mediation flow definition file could not be loaded.
The named mediation flow definition file could not be loaded.
Inform the user.
Check the validity of the deployed mediation component.
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.
Inform the user.
Check the validity of the deployed mediation component.
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)