- CWWBO0001E: The lookup of the notification helper ''{0}'' failed.
- Explanation: The notification helper was not found in the JNDI namespace.
- User Action: Ensure that the Common Event Infrastructure is installed correctly.
- CWWBO0002E: The connection to the database ''{0}'' failed.
- Explanation: The CEI consumer received an exception while trying to get connect to the database for the data source.
- User Action: Check the nested SQL exception for more information about the exception. Also ensure that the data source is configured correctly.
- CWWBO0003E: The data source was not found {0}.
- Explanation: The data source was not found in the JNDI namespace.
- User Action: Check that the resource reference for the CEI consumer is mapped to the correct data source.
- CWWBO0004E: The event could not be added to the database. Event: ''{0}''.
- Explanation: The insertion of the event in the Business Process Choreographer Observer database failed.
- User Action: Check the nested SQL exception.
- CWWBO0005W: Events with the extension name ''{0}'' are not supported
- Explanation: The extension names of events must start with 'BPC.BFM.*'.
- User Action: Check the event selector string in the event group profile.
- CWWBO0006W: The literal ''{0}'' could not be parsed as a timestamp.
- Explanation: The timestamp literal in the event has the wrong format.
- User Action: Open a service request at www.ibm.com to report this error.
- CWWBO0007W: Updating or removing events is not supported
- Explanation: CEI sent an update or remove event notification.
- User Action: Open a service request at www.ibm.com to report this error.
- CWWBO0008E: The transformation of the event failed. Event: ''{0}''
- Explanation: The transformation of the event failed.
- User Action: Check the nested exception.
- CWWBO0009E: The following data could not be added to the database: ''{0}''.
- Explanation: The insertion of data in the Business Process Choreographer Observer database failed.
- User Action: Check the nested SQL exception.
- CWWBO0010E: The following data could not be retrieved from the database: ''{0}''.
- Explanation: The retrieval of data from the Business Process Choreographer Observer database failed.
- User Action: Check the nested SQL exception.
- CWWBO0011E: Updating of data in the database failed. Data: ''{0}''.
- Explanation: The update of data in the Business Process Choreographer Observer database failed.
- User Action: Check the nested SQL exception.
- CWWBO0012E: The retrieval of events from the database failed. PIID: ''{0}''.
- Explanation: The retrieval of events from the Business Process Choreographer Observer database failed.
- User Action: Check the nested SQL exception.
- CWWBO0013E: The notification of the event Transformer failed.
- Explanation: The notification that was sent by the CEI consumer was not received by the event transformer.
- User Action: Check the nested exception.
- CWWBO0014I: A Process Started event was not found for the process instance with the PIID ''{0}''. Discarding events.
- Explanation: The specified process instance does not have a Process Started event. Therefore the events cannot be processed.
- User Action: Make sure that you have enabled event generation in the process model.
- CWWBO0015W: More than 1000 events with the same timestamp were found for process instance with PIID ''{0}''. Discarding events.
- Explanation: The Transformer corrects the nanoseconds of the timestamps to ensure the proper sequence of events. With more than 1000 events from the same process instance, the Transformer cannot guarantee the proper sequence.
- User Action: If you are in a clustered environment, make sure that your servers are synchronized.
- CWWBO2500E: The query did not return an item in the result set.
- Explanation: CWWBO2500E: The query did not return an item in the result set.
- User Action: CWWBO2500E: Check the log files for JDBC errors.
- CWWBO2501E: The EJB could not be invoked due to a remote exception.
- Explanation: CWWBO2501E: The EJB could not be invoked due to a remote exception.
- User Action: CWWBO2501E: Check that the remote EJB interface is available.
- CWWBO2502E: The EJB returned an AuditLog exception.
- Explanation: CWWBO2502E: The EJB faced a database error and returned an exception.
- User Action: CWWBO2502E: Check the error code of the nested EJB exception.
- CWWBO2503E: For the query to be run, it must be properly structured.
- Explanation: CWWBO2503E: For the query to be run, it must be properly structured.
- User Action: CWWBO2503E: Check the error code of the nested exception.
- CWWBO3500E: Check the nested JDBC exception for the reason code.
- Explanation: CWWBO3500E: The EJB could not connect to the JDBC database.
- User Action: CWWBO3500E: Check the nested JDBC exception for the reason code.
- CWWBZ0001E: One or more required parameters are missing: ''{0}''.
- Explanation: The specified administrative command requires one or more parameters that were not supplied.
- User Action: Run the command again with the correct syntax.
- CWWBZ0002E: The application ''{0}'' could not be installed. Messages: {1}
- Explanation: An error occurred during the installation of the specified application.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0003E: An error occurred while retrieving the attribute ''{0}'' from the object ''{1}''.
- Explanation: The administrative command encountered an exception while querying the configuration.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0004E: An error occurred while retrieving the configuration object: ''{0}''.
- Explanation: The administrative command encountered an exception while querying the configuration.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0005E: An error occurred while querying configuration data for the object type ''{0}'' in the scope ''{1}''.
- Explanation: The administrative command encountered an exception while querying the configuration.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0006E: An error occurred while querying the parent of the object ''{0}''.
- Explanation: The administrative command encountered an exception while querying the configuration.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0007E: An error occurred while registering or unregistering the notification listener for the AppManagement object ''{0}''.
- Explanation: The administrative command encountered an exception while registering or unregistering the notification listener for the AppManagement object.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0008E: An error occurred while resolving the configuration object based on the configuration path ''{0}''.
- Explanation: The administrative command encountered an exception while identifying a target object for the administrative command.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0009E: Multiple configuration objects were found with the same configuration path ''{0}''.
- Explanation: The administrative command parameters do not represent a single target object instance. This might happen if objects with the same configuration path exist in more than one scope (server or cluster).
- User Action: Run the command again with the correct parameters, specifying a scope if necessary.
- CWWBZ0010E: No configuration objects were found with the configuration path ''{0}''.
- Explanation: The administrative command parameters do not represent a target object instance in the specified scope.
- User Action: Run the command again with the correct parameters.
- CWWBZ0011E: An error occurred while creating the configuration object ''{0}'' of type or template ''{1}'' with attributes ''{2}'' under configuration object ''{3}''.
- Explanation: The administrative command encountered an exception while creating an object.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0012E: An error occurred while creating an instance of the administrative command ''{0}''.
- Explanation: The AdminTask object encountered an exception while creating an instance of the specified administrative command.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0013E: The parameter is not valid: ''{0}''.
- Explanation: The specified parameter is not valid.
- User Action: Run the command again with correct parameters.
- CWWBZ0014E: The server ''{0}'' in node ''{1}'' is a member of the cluster ''{2}'' and it cannot be used as a target for this administrative command.
- Explanation: The administrative commands do not support cluster members as target objects.
- User Action: Run the command again and specify a target server that is not a cluster member.
- CWWBZ0015E: The Common Event Infrastructure (CEI) is not configured. Resource ''{0}'' was not found in the scope ''{1}''.
- Explanation: Business Process Choreographer Observer needs the Common Event Infrastructure.
- User Action: Configure CEI.
- CWWBZ0016E: The specified combination of parameters ''{0}'' is not valid.
- Explanation: A node or server name cannot be specified with a cluster name. Specify either a node name and a server name, or a cluster name.
- User Action: Run the command again with the correct parameters.
- CWWBZ0017E: The parameter(s) ''{0}'' are missing.
- Explanation: To federate a standalone Business Process Choreographer server into a cell use the parameters '-includebuses' and -'includeapps'.
- User Action: Run addNode.bat again with '-includebuses' and '-includeapps'.
- CWWBZ0018E: The version of the deployment manager (''{0}'') is incompatible to the version of the server (''{1}'').
- Explanation: To federate a standalone Business Process Choreographer server into a cell the deployment manager and the server must have a compatible version.
- User Action: Ensure that the Deployment Manager and the Server have a compatible versions and update if necesarry.
- CWWBZ0019E: The Business Process Choreographer is not installed on the deployment manager.
- Explanation: To federate a standalone Business Process Choreographer server into a cell the Business Process Choreographer has to be installed on the deployment manager.
- User Action: Ensure that the Business Process Choreographer is installed on the deployment manager.
- CWWBZ0020E: The Business Process Choreographer database is not accessible from remote systems. Database type: ''{0}''.
- Explanation: The database has to be accessible from the Deployment Manager.
- User Action: Use a remotable database like IBM DB2.
- CWWBZ0021E: The Business Process Choreographer is already configured on the deployment manager.
- Explanation: To federate a standalone Business Process Choreographer server into a cell it is not allowed to have the Business Process Choreographer already configured on the deployment manager.
- User Action: Ensure that the Business ProcessChoreographer is not configured on the deployment manager.
- CWWBZ0022E: An error occurred while removing the configuration object ''{0}'' of type or template ''{1}'' with attributes ''{2}'' under configuration object ''{3}''.
- Explanation: The administrative command encountered an exception while removing an object.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0023E: An error has occurred querying template object with type ''{0}'' and name''{1}''.
- Explanation: The administrative command encountered an exception while retrieving a template object.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0024E: The template ''{0}'' could not be found.
- Explanation: The administrative command could not find a template with the specified name in the configuration respository.
- User Action: Run the command again with the correct template name.
- CWWBZ0025E: An application management operation for application ''{0}'' failed.
- Explanation: The administrative command encountered an exception while executing an application management operation.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0026E: Multiple buses with pattern ''{0}'' found in configuration: ''{1}''.
- Explanation: The administrative command has found more than one bus which matches the naming convention fo the Business Process Choreographer Bus.
- User Action: Ensure that there is only only Business Process Choreographer Bus in you cell.
- CWWBZ0027E: No buses with pattern ''{0}'' found in configuration.
- Explanation: The administrative command has not found a bus which matches the naming convention fo the Business Process Choreographer Bus.
- User Action: Ensure that the Business Process Choreographer Bus is configured correctly.
- CWWBZ0028E: Clearing the cache for the authentication data failed.
- Explanation: The administrative command encountered an exception while clearing the cache for the authentication data.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0029I: An empty JDBC provider for BPC has been created on the Deployment Manager. Please set the appropriate WebSphere variable at the Deployment Manager's node.
- Explanation: The deployment manager needs the appropriate WebSphere variables for the JDBC provider.
- User Action: Please set the appropriate WebSphere variable at the Deployment Manager's node.
- CWWBZ0030E: The server ''{0}'' in node ''{1}'' is configured for the Business Process Choreographer and cannot be used as template for the cluster ''{2}''.
- Explanation: Creating a cluster from an existing as template is not supported if the Business Process Choreographer is configured on this server.
- User Action: Choose another template or add this server as first member to the cluster.