Explanation The script cannot write files to the location specified in the -dbLocation parameter
User response 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.
Explanation There was a problem in locating the runtime instance of the mediation flow.
User response Check the causal exception for more information.
Explanation The script does not remove the database.
User response If desired, remove the database manually.
Explanation The key class is not of the expected type for this flow engine.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User response Check the log file for problems creating the database.
Explanation During the primitives initialization, the named mediation primitive encountered an error.
User response Verify that the configuration of the mediation primitive in the mediation flow definition, and check the causal exception for more information.
Explanation The script has created a Cloudscape database using the DDL file.
User response None.
Explanation An error occured whilst trying to set the properties of the mediation primitive.
User response Verify that the correct properties are defined for the mediation primitive in the mediation flow definition, and check the causal exception for more information.
Explanation The node and server name combination could not be found.
User response Call the script again specifying a valid node name and server name
Explanation The mediation primitive could not be instantiated.
User response Validate the mediation flow definition, and check the causal exception for more information.
Explanation The script was used in a Network Deployment environment but the node name and server name were not specified on the command line.
User response Call the script again specifying the node name and server name on the command line
Explanation The flow has an invalid or unknown input.
User response Validate the mediation flow definition.
Explanation The data source was not found.
User response Check whether the data source exists and manually remove it.
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.
User response 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.
Explanation The script has removed the data source.
User response None.
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.
User response Verify that the mediation component has a response flow defined for the operation and check for any earlier exceptions in loading the response flow.
Explanation The CMP connection factory associated with the data source was not found.
User response Check whether the CMP connection factory exists and manually remove it.
Explanation The request flow for the operation could not be found by the flow engine. This could be because no request flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
User response Verify that the mediation component has a request flow defined for the operation.
Explanation A Fail mediation primitive has raised a FailFlowException.
User response Examine any user-supplied error message.
Explanation The script has removed the connection factory used by the data source.
User response None.
Explanation No runtime mediation flow definitions were found for the mediation component.
User response Check the mediation component has a mediation flow defined and check for any earlier exceptions in loading the definition.
Explanation The script is creating a CMP connection factory for the data source.
User response None.
Explanation The script is creating the data source configuration object.
User response None.
Explanation The script is creating a data source for the named JDBC provider.
User response None.
Explanation The script cannot continue because the connection factory it would create already exists.
User response 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.
Explanation A data source with the specified JNDI name already exists.
User response 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.
Explanation The script needs this JDBC provider to configure the data source.
User response Restore the named JDBC provider or manually configure the data source.
Explanation The script is creating a Cloudscape database using the DDL file. The results of the database creation are saved to a log file.
User response None.
Explanation The script is creating the DDL file for the Cloudscape database.
User response None.
Explanation The script cannot find the ij.bat or ij.sh command in the named directory. If this file does not exist the server installation is corrupted.
User response Reinstall the application server to repair the installation.
Explanation The script cannot create a database in the named location because a database already exists there.
User response 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.
Explanation A database with the specified location and name does not exist.
User response None.
Explanation A database with the specified location and name already exists.
User response None.
Explanation A data source with the specified JNDI name does not exist.
User response None.
Explanation A data source with the specified JNDI name already exists.
User response None.
Explanation The data source configuration changes have been completed.
User response None.
Explanation The configuration changes are being saved.
User response None.
Explanation There is more than one server configured for the node.
User response See the InfoCenter for instructions on how to create data sources for multiple servers.
Explanation The "-createDb" option creates an embedded Cloudscape database.
User response See the InfoCenter for instructions on how to install the database in a Network Deployment environment.
Explanation The script was called with an incorrect set of parameters.
User response Call the script again with parameters described in the message.
Explanation An exception occurred when invoking an import from the mediation flow. Check the causal exception information for more detail.
User response Check the availability of the service referred to by the import.
Explanation An exception occurred when invoking the Java component implementing a custom primitive. Check the causal exception information for more detail.
User response Check the validity of the deployed custom mediation component.
Explanation The reference is connected to multiple services but only a single service can be connected to on a reference in a mediation flow.
User response Check the validity of the mediation flow and the validity of references that are invoked.
Explanation An internal error occured when the mediation flow component was creating an outbound message.
User response Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
Explanation An internal error occured when the mediation flow component processed a response message.
User response Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
Explanation An internal error occured when the mediation flow component processed a response message.
User response Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
Explanation An error occured when saving the context information used by a mediation flow for the given component.
User response Check the causal exception for more information.
Explanation An internal error occured when saving the context information used by a mediation flow for the given component.
User response Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
Explanation The requested EJB session bean could not be located.
User response Check the deployment of the mediation flow component.
Explanation The named operation cannot be found for the reference that is invoked by the mediation flow.
User response Ensure that the operation name that is used in the mediation flow is correct.
Explanation Mediation response and fault flows are not permitted to invoke services.
User response Ensure that the response and fault flows in the module do not invoke services.
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.
User response 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.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation The mediation flow returned an exception that indicated that a business logic error occurred.
User response Check the underlying exception for details of the business logic error.
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.
User response Check the underlying exception for more details of the cause of the configuration error.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation The mediation flow returned an exception that was not handled by the mediation flow. An exception may be returned if the mediation primitive does not define a failure terminal, or the failure terminal is not wired.
User response Check the mediation flow to ensure that all failure terminals on primitives are wired.
Explanation The requested mediation flow session bean could not be located.
User response Check the deployment of the mediation flow component.
Explanation This is a unit test message
User response No action necessary
Explanation This is a unit test message
User response No action necessary
Explanation No value for the sub-type of the complex-type for a target terminal in a connection.
User response Verify that the Mediation Flow definition is correct.
Explanation No value for the sub-type of the complex-type for a source terminal in a connection.
User response Verify that the Mediation Flow definition is correct.
Explanation The Mediation Flow definition file may have been corrupted or the Mediation Flow may have been produced on a version of the tooling greater than the version of the runtime.
User response Verify that the Mediation Flow definition is correct.
Explanation The node is missing an expected terminal, named with one of the standard names, ''in'' or ''out''.
User response Verify that the Mediation Flow definition is correct.
Explanation The types of the terminals that are connected together must be the same.
User response Verify that the Mediation Flow definition is correct.
Explanation An exception occurred when parsing the mediation flow Response Flow. Check the causal exception information for more detail.
User response Verify that the Mediation Flow definition is correct.
Explanation An exception occurred when parsing the named mediation flow Request Flow. Check the causal exception information for more detail.
User response Verify that the Mediation Flow definition is correct.
Explanation The Request Flow must have one, and only one Input node.
User response Verify that the Mediation Flow definition is correct.
Explanation An exception occurred when parsing the named mediation flow node. Check the causal exception information for more detail.
User response Verify that the Mediation Flow definition is correct.
Explanation Missing value for the Custom Mediation node''s Reference Name.
User response Verify that the Mediation Flow definition is correct.
Explanation Missing value for the Custom Mediation node''s Operation Name.
User response Verify that the Mediation Flow definition is correct.
Explanation Missing value for the named node''s Reference Name.
User response Verify that the Mediation Flow definition is correct.
Explanation The object with the JNDI name ''{0}'' was not of type String. The causal exception, if available, will contain more information.
User response Ensure that the object bound into JNDI is a String.
Explanation Missing value for the named node''s Operation Name.
User response Verify that the Mediation Flow definition is correct.
Explanation A problem occurred obtaining the JNDI InitialContext. The nested exception, if available, will contain more information.
User response Ensure that the JNDI service is available.
Explanation The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
User response Verify that the Mediation Flow definition is correct.
Explanation A problem occurred communicating with the database. The nested exception, if available, will contain more information.
User response Ensure that the database is available and configured correctly.
Explanation The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
User response Verify that the Mediation Flow definition is correct.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
User response Verify that the Mediation Flow definition is correct.
Explanation Unable to serialize the message information as an XML document. The nested exception, if available, will contain more information.
User response Ensure that the message being mediated is valid.
Explanation Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
User response Verify that the Mediation Flow definition is correct.
Explanation Unable to access the database to store the message. The nested exception, if available, will contain more information.
User response Ensure that the correct access rights have been set, the database is available and the schema conforms to the IBM supplied schema.
Explanation The database schema is invalid for the named primitive.
User response Ensure that the database schema conforms to the IBM supplied schema. Please refer to the documentation to locate the schema.
Explanation Unable to obtain a connection to the database. The nested exception, if available, will contain more information.
User response Ensure that the database is available for connection and any authentication settings have been configured.
Explanation An exception occurred when parsing the named mediation flow component definition file. Check the causal exception information for more detail.
User response Check the validity of the deployed mediation component.
Explanation The named mediation flow definition file could not be loaded.
User response Check the validity of the deployed mediation component.
Explanation The named mediation flow component definition file could not be loaded.
User response Check the validity of the deployed mediation component.
Explanation A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name.
User response Correct the mediation primitive configuration, ensuring that terminal names are used only once for a MessageFilter primitive.
Explanation A MessageFilter primitive configuration contains a null Filter definition. Usually this means that the mediation flow configuration is not correct.
User response Correct the mediation flow configuration.
Explanation The v6.0 StockQuote sample is deprecated, and should be replaced with later versions of the sample. The v6.0 sample is unlikely to work with future versions of the runtime. User-created Mediation Modules are not affected.
User response Upgrade the version of the StockQuote sample. If this message is issued while running a user Mediation Module which was based on the StockQuote sample, it may be necessary to reconstruct the user application based on the updated version of the sample.
Explanation The mediation primitive attempted to mediate a message which was not a ServiceMessageObject. This is not allowed.
User response Ensure that the configuration of the mediation flow is valid.
Explanation The mediation primitives configuration was incomplete.
User response Ensure that the configuration of the mediation primitive and mediation flow is valid.
Explanation The mediation primitives configuration was incomplete.
User response Ensure that the configuration of the mediation primitive and mediation flow is valid.
Explanation A null value is not valid for the named property.
User response 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.
Explanation A mediation primitive was invoked without a message to mediate.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation The mediation primitives configuration was incomplete.
User response Ensure that the configuration of the mediation primitive and mediation flow is valid.
Explanation The mediation primitives configuration is missing a required property. Usually this means that the mediation configuration is not correct.
User response Correct the configuration of the mediation primitive.
Explanation A setter method on a mediation primitive has been called with a value which is not allowed. Usually this means that the mediation configuration is not correct.
User response Correct the configuration of the mediation primitive.
Explanation The mediation primitives configuration does not specify the XSL transformation file to use.
User response Correct the configuration of the mediation primitive.
Explanation An Exception was caught while initializing the XSL transformation engine. This usually indicates a syntax or other error relating to the source stylesheet.
User response Inspect the nested exception to diagnose the problem.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation The XSLTransform property named the given file, which was not found at runtime.
User response Correct the XSLTransform property, or make the stylesheet available.
Explanation The XSL transformation completed successfully, but the transformed DataObject could not be set into the root position in the ServiceMessageObject.
User response Use the nested Exception to diagnose the problem.
Explanation The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject.
User response Use the nested Exception to diagnose the problem.
Explanation An Exception occurred during XSL transformation.
User response Use the nested Exception to diagnose the problem.
Explanation The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation.
User response Use the nested Exception to diagnose the problem.
Explanation An Exception was caught while XSLTransform was evaluating the Root, prior to transformation.
User response Use the nested Exception to diagnose the problem.
Explanation The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. It must not evaluate to a collection of DataObjects or to a value other than a single DataObject.
User response Correct the Root property.
Explanation The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. However, in the message being mediated, it evaluated to multiple elements.
User response Correct the Root property.
Explanation The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. This suggests that the value is not set.
User response Ensure that the configuration of the Root property is set to a valid value.
Explanation There is a WSDL Message definition with the same name (namespace and local part) as an XSD type definition.
User response Alter either the WSDL or the XSD definitions so that multiple objects do not share the same name.
Explanation The system encountered an expanded QName which was not of correct format
User response If the malformed QName is contained within a user message, then determine why the message contains a badly formatted QName.
Explanation A ServiceMessageObject was found to have no body, but validation required the SMO body to be set.
User response Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect.
Explanation The body of a ServiceMessageObject was not of the expected type. This message usually refers to SMO validation in a mediation primitive, which compares the SMO to a type specified on one of the primitive''s terminals.
User response Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect, or correct the expected type.
Explanation During validation of a ServiceMessageObject, the contents of the message were found to be inconsistent with constraints. For example, a value might be out of bounds, or a required attribute might be unset.
User response 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.
Explanation Custom mediations may only define a two-way interface.
User response Check the configuration of the custom mediation.
Explanation The target must be a valid XPath expression that resolves to one message element. The mediation configuration is not correct.
User response Correct the configuration of the mediation primitive.
Explanation There is no operation of the specified name defined on the reference for the custom mediation.
User response Check the configuration of the custom mediation.
Explanation The value obtained from the message at the specified location did not return a single element to be used as a key into the database. This is not allowed.
User response Ensure that the location in the message to be used as a key is a single element and not a collection of elements.
Explanation When the property 'type' is 'copy', then the value must be an XPath expression describing the location of the source element. The mediation configuration is not correct.
User response Correct the configuration of the mediation primitive.
Explanation An exception occurred attempting to set value ''{1}'' into the message at location ''{0}''
User response Ensure that the path location is a valid location for the message being mediated.
Explanation A null value was obtained from the database column using the named key. This is not allowed.
User response Ensure that the value contained in the database is compatible with the message element type.
Explanation An exception occurred attempting to set value ''{1}'' into the message at location ''{0}''
User response Ensure that the path location is a valid location for the message being mediated.
Explanation A type mismatch occurred between the type of the value obtained from the database and the type configured in mediation primitive.
User response Ensure the mediation primitive is configured correctly and the type of the value obtained from the database is one of the supported types.
Explanation The object with the JNDI name ''{0}'' was not of type DataSource. The causal exception if available will contain more information.
User response Ensure that the object bound into JNDI is a DataSource.
Explanation An exception occurred when attempting to read from the database. The nested exception, if available, will contain more information.
User response Ensure that the property values have been specified correctly because the more probable cause of this exception is an invalid table or column name.
Explanation The datasource with the JNDI name ''{0}'' could not be located. The causal exception if available will contain more information.
User response Ensure that the JNDI service is available and an appropriate datasource has been configured.
Explanation Unable to obtain a connection to the database. The nested exception, if available, will contain more information.
User response Ensure that the database is available for connection and any necessary authentication rights have been configured in the appropriate datasource.
Explanation A mediation primitive tried to locate a datasource with a null JNDI name.
User response Ensure that the JNDI name is valid.
Explanation More than one row of data was returned from the database. This is not allowed.
User response Ensure that the database key column only contains unique values.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation See the nested exception for more information.
User response Ensure that the database is available and configured correctly.
Explanation The reference for the callout is not defined on the mediation component.
User response Check the validity and correct deployment of the mediation component.
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.
User response Check that the database is available and refer to the documentation for supported database column types.
Explanation An error occurred when the action of a flow was invoked.
User response Check the causal exception for more information.
Explanation An unsuccessful attempt was made to locate a value in the message to be used as a key into the database.
User response Ensure that the message contains a value in the specified location.
ExplanationThis exception is unexpected. The cause is not immediately known.
User responseIf the problem persists, see problem determination information on the product support page at http://www-306.ibm.com/software/integration/wps/support/.
Explanation A mediation primitive attempted to obtain an output terminal which does not exist.
User response Check the validity of the mediation flow.
Explanation The key identifies the correlation information for the reply message. The key may be absent if a reply has already been received with the same ticket, or if the corresponding message has been deleted from the modules correlation destination
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation A mediation primitive attempted to obtain an input terminal which does not exist.
User response Check the validity of the mediation flow component.
Explanation An unknown exception occurred during the processing of the specified mediation primitive or custom mediation.
User response Check the causal exception for more information.
Explanation The response fault flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User response Check the validity of the mediation flow component, and check for previous errors.
Explanation The response flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User response Check the validity of the mediation flow component, and check for previous errors.
Explanation The request flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
User response Check the validity of the mediation flow component, and check for previous errors.
Explanation The username and password parameters are required for this script but one or both of them were empty.
User response Run the script again, specifying values for both the username and password.
Explanation The reference for the custom mediation is not defined on the mediation component.
User response Check the validity and correct deployment of the mediation component.
Explanation The required JDBC provider does not exist and is being created.
User response None.
Explanation The required JDBC provider already exists.
User response None.
Explanation The script could not find a template for the required JDBC provider, so the JDBC provider cannot be used.
User response Report the problem to the System Administrator.
Explanation An internal error occured when invoking the fault response flow for the fault message and operation on the named reference.
User response Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
Explanation A matching JDBC provider template was found but it may not be the correct one.
User response Check the JDBC Provider used for the Data Source and inform the System Administrator if it is the wrong one.
Explanation An internal error occured when invoking the response flow for the operation on the named reference.
User response Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
Explanation A J2C authentication alias with the required name was not found and a new one is created.
User response None.
Explanation An internal error occured when invoking the request flow for the operation.
User response Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
Explanation A J2C authentication alias with the required name was found and it is modified with the new username and password.
User response None.
Explanation There was a problem in locating the runtime instance of the mediation flow.
User response Check the causal exception for more information, and validate that the SCA module started with no errors.