- 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: One or more parameters are missing: ''{0}''.
- Explanation: To federate a stand-alone Business Process Choreographer server into a cell, use the '-includebuses' and -'includeapps' parameters.
- User Action: Run addNode.bat again with the '-includebuses' and '-includeapps' parameters.
- CWWBZ0018E: The version of the deployment manager (''{0}'') is incompatible with the version of the server (''{1}'').
- Explanation: To federate a stand-alone Business Process Choreographer server into a cell, the version of the deployment manager must be compatible with the version of the server.
- User Action: Ensure that the version of the deployment manager is compatible with the version of the server. If the versions are not compatible, update your system.
- CWWBZ0019E: Business Process Choreographer is not installed in the deployment manager.
- Explanation: To federate a stand-alone Business Process Choreographer server into a cell, Business Process Choreographer must be installed in the deployment manager.
- User Action: Ensure that Business Process Choreographer is installed in the deployment manager.
- CWWBZ0020E: The Business Process Choreographer database is not accessible from remote systems. Database type: ''{0}''.
- Explanation: The database must be accessible from the deployment manager.
- User Action: Use a remote database, such as IBM DB2.
- CWWBZ0021E: Business Process Choreographer is already configured in the deployment manager.
- Explanation: To federate a stand-alone Business Process Choreographer server into a cell, Business Process Choreographer cannot be configured already in the deployment manager.
- User Action: Ensure that Business Process Choreographer is not configured in the deployment manager.
- CWWBZ0022E: An error occurred during the removal of the configuration object ''{0}'' of the type, or the template ''{1}'' with the attributes ''{2}'' under the 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 occurred during the query of the template object with the 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 repository.
- User Action: Run the command again with the correct template name.
- CWWBZ0025E: An application management operation for the 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 the pattern ''{0}'' were found in the configuration: ''{1}''.
- Explanation: The administrative command found more than one bus that matches the naming convention of the Business Process Choreographer bus.
- User Action: Ensure that your cell has only one Business Process Choreographer bus.
- CWWBZ0027E: The configuration does not contain any buses with the pattern ''{0}''.
- Explanation: The administrative command did not find a bus that matches the naming convention of the Business Process Choreographer bus.
- User Action: Ensure that the Business Process Choreographer bus is configured correctly.
- CWWBZ0028E: The cache for the authentication data cannot be cleared.
- 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 Business Process Choreographer was created in the deployment manager. Set the appropriate WebSphere variables at the deployment manager node.
- Explanation: The deployment manager needs the appropriate WebSphere variables for the JDBC provider.
- User Action: Set the appropriate WebSphere variables at the deployment manager node.
- CWWBZ0030E: The server ''{0}'' in node ''{1}'' is configured for Business Process Choreographer and cannot be used as a template for the cluster ''{2}''.
- Explanation: Creating a cluster from an existing template is not supported if Business Process Choreographer is configured on this server.
- User Action: Choose another template, or add this server to the cluster as the first member.
- CWWBZ0031E: The JNDI name ''{0}'' of the data source ''{1}'' is not valid for Business Process Choreographer. The JNDI name must be ''{2}''.
- Explanation: The data source used for Business Process Choreographer must have the JNDI name ''{2}''.
- User Action: Change the JNDI name of the data source, or use another data source with the correct JNDI name.
- CWWBZ0032E: The scope ''{0}'' of the data source ''{1}'' is not valid for Business Process Choreographer. The data source must be at the scope ''{2}''.
- Explanation: Both Business Process Choreographer and the data source that it uses must be configured at the same scope.
- User Action: Change the scope of the data source or use another data source with the scope.
- CWWBZ0033E: The validation of the data source ''{0}'' failed because it is not XA enabled.
- Explanation: The data source used for Business Process Choreographer must be XA enabled.
- User Action: Use an XA enabled data source to configure Business Process Choreographer.
- CWWBZ0034E: The authentication alias ''{0}'' does not exist.
- Explanation: The authentication alias with this name could not be found.
- User Action: Create the authentication alias, or correct the name.
- CWWBZ0035E: The deployment target ''{0}'' is not enabled for Business Process Choreographer.
- Explanation: To configure Business Process Choreographer, the server must be created from a Business Process Choreographer enabled server template.
- User Action: Use a server or cluster that was created with a Business Process Choreographer enabled server template.
- CWWBZ0036E: The specified combination of parameters ''{0}'' is not valid.
- Explanation: You cannot use both '-bfm' parameters and '-htm' parameters with this command.
- User Action: Run the command again with the correct parameters.
- CWWBZ0037E: The Service Component Architecture (SCA) is not configured on the deployment target ''{0}''.
- Explanation: SCA is a prerequisite for the configuration of Business Process Choreographer.
- User Action: Configure SCA on the deployment target where you want to configure Business Process Choreographer.
- CWWBZ0038E: Parameter {0} cannot be set to ''{1}'' if parameter {2} is set to ''{3}''.
- Explanation: The specified combination of parameter values is not valid.
- User Action: Run the command again with correct parameter values.
- CWWBZ0039E: Execution of script ''{0}'' failed. See ''{1}'' for more details.
- Explanation: The script could not be run.
- User Action: Fix the problems reported in the log file, then run the command again.
- CWWBZ0040E: The message engine ''{0}'' on the server or cluster ''{1}'' uses a data store or file store that cannot be accessed remotely.
- Explanation: In a cluster of messaging engines, all cluster members need access to the data store or file store.
- User Action: Ensure that all cluster members have access to the data store or file store, for example, use a shared network file system as the file store location.
- CWWBZ0041E: The development mode is not supported in a Network Deployment environment. Cannot federate server ''{0}'' on node ''{1}''.
- Explanation: To federate a stand-alone Business Process Choreographer server into a cell, do not enable the development mode on the stand-alone server.
- User Action: Use the administrative console to disable the development mode.
- CWWBZ0042E: An error occurred while exporting the WSDL files for the application ''{0}''.
- Explanation: The administrative command encountered an exception while exporting the WSDL files for a Web service.
- User Action: See the nested exception message for additional information about the cause of the problem.
- CWWBZ0043E: The application ''{0}'' is deployed to more than one application server or cluster.
- Explanation: The application is mapped to multiple deployment targets. However, applications in the Business Process Choreographer infrastructure must not be deployed to more than one deployment target.
- User Action: Remove the target mapping for all of the application servers or clusters except the server or cluster where Business Process Choreographer is configured.
- CWWBZ0044E: Business Process Choreographer is not configured on the deployment target ''{0}''.
- Explanation: To perform the specified operation, Business Process Choreographer must be configured.
- User Action: Configure Business Process Choreographer on the deployment target.
- CWWBZ0045E: Multiple applications with the pattern ''{0}'' were found on the scope ''{1}'': ''{2}''.
- Explanation: The administrative command found more than one application that conforms to the naming conventions for Business Process Choreographer applications.
- User Action: Ensure that you have only one application installed on this deployment target that conforms to the naming conventions.
- CWWBZ0046E: A data source was not provided for the messaging engine on the cluster ''{0}''.
- Explanation: To use a cluster as a deployment target, you must provide a data source for the messaging engine.
- User Action: Run the command again with the correct parameters.
- CWWBZ0047E: Configuration error: ''{0}''. Error parameters: {1}.
- Explanation: A general purpose message for use when the product is in service and a new message is needed.
- User Action: Check the error message for a description of the error.
- CWWBZ0048I: Configuration information: ''{0}''. Information parameters: {1}.
- Explanation: A general purpose message for use when the product is in service and a new message is needed.
- User Action: None.
- CWWBZ0049W: Configuration warning: ''{0}''. Warning parameters: {1}.
- Explanation: A general purpose message for use when the product is in service and a new message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBZ0050E: The messaging engine ''{0}'' on the deployment target ''{1}'' is using ''{2}'' as the message store, which is not supported in a Network Deployment environment.
- Explanation: In a Network Deployment environment the message store must be accessible from all of the cluster members.
- User Action: Use a remote database as the message store for the messaging engine.
- CWWBZ0051E: The data source for the messaging engine ''{0}'' with the JNDI name ''{1}'' was not found in the scope ''{2}''.
- Explanation: The data source must be in the same scope as the messaging engine.
- User Action: Change the scope of the data source used for the messaging engine.
- CWWBZ0052W: Business Process Choreographer Explorer {0} was configured to use the {1} URL to access the Representational State Transfer (REST) API of the {2} component on the {3} deployment target. Verify that this URL is correct.
- Explanation: The URL of the REST API can change if the Web module that contains the REST API is mapped to an HTTP server or if the context root or virtual host settings are changed.
- User Action: Refer to the information center (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp) for instructions on how to change the URL in case it is not correct.
- CWWBZ0053W: The Business Process Choreographer Explorer {0} was configured for the {1} component on the {2} deployment target. The URL to access the Representational State Transfer (REST) API cannot be set automatically in this environment. You must set this URL manually.
- Explanation: The URL of the REST API can change if the Web module that contains the REST API is mapped to an HTTP server or if the context root or virtual host settings are changed.
- User Action: Refer to the information center (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp) for instructions on how to change the URL.
- CWWBZ0054I: The following enterprise archive (EAR) file was used to install the predefined tasks: {0}.
- Explanation: More than one version of the EAR file that contains the predefined tasks can exist. This message indicates which version was installed.
- User Action: No action is required.
- CWWBZ0055W: No enterprise archive (EAR) file containing the predefined tasks was found using the {0} pattern.
- Explanation: More than one version of the EAR file that contains the predefined tasks can exist. This message indicates that no EAR file was found to install.
- User Action: Identify the EAR file that contains the predefined tasks and install it manually.
- CWWBZ0056W: DB2 reoptimization (once) is not enabled.
- Explanation: This problem can affect Business Process Choreographer API query performance.
- User Action: Refer to the information center (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp) for instructions on how to bind the NULLIDR1 package.
- CWWBZ0057E: Reading the version for the {0} application from the {1} enterprise archive (EAR) file failed..
- Explanation: The administrative command encountered an exception while reading the Implementation-Version for an application.
- User Action: Make sure that the EAR file exists and that it contains an Implementation-Version in the META-INF/MANIFEST.MF file. See the nested exception message for moreinformation about the cause of the problem.
- CWWBZ0058E: An error occurred while executing an instance of the ''{0}'' administrative command.
- Explanation: The AdminTask object encountered an exception while executing an instance of the specified administrative command.
- User Action: See the exception message for information about the cause of the problem.
- CWWBZ0059E: The ''{0}'' cleanup job was not found on the ''{1}'' deployment target.
- Explanation: No cleanup job is defined with the specified display name.
- User Action: Make sure that you have provided a valid display name.
- CWWBZ0060E: An error occurred while checking whether the configuration object type ''{0}'' is supported.
- 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.
- CWWBZ0061E: An error occurred while looking up the NotificationService MBean for process ''{0}''.
- Explanation: The NotificationService MBean is used to emit progress notifications for this administrative command.
- User Action: See the exception message for additional information about the cause of the problem.
- CWWBZ0062I: The enterprise application {0}, which contains the predefined tasks, is already installed.
- Explanation: The EAR file that contains the latest version of the predefined tasks is already installed.
- User Action: No action is required.
- CWWBZ0063W: Version {0} predefined tasks cannot be installed on a version {1} runtime system.
- Explanation: The DeployVersion for the predefined tasks must not be greater than the version of installation on the deployment target node.
- User Action: Migrate or update the deployment target node to a compatible level, then run the upgrade script again as described in the documentation.
- CWWBZ0064W: A version {0} deployment manager cannot install the predefined tasks on a version {1} runtime.
- Explanation: The version of the deployment manager must match the version of the deployment target.
- User Action: Migrate or update the deployment target node to the same level as the deployment manager, then run the upgrade script again as described in the documentation.