- CWWBF0000E: Error while updating database {0}.
- Explanation: The database could not be updated.
- User Action: Determine the reason for the update failure.
- CWWBF0001E: Error while creating database {0}.
- Explanation: The database could not be created.
- User Action: Determine the reason for the creation failure.
- CWWBF0002E: Error while creating the table space for {0} in {1}.
- Explanation: A table space cannot be created.
- User Action: Determine the reason for the creation failure.
- CWWBF0003E: Configuration failed.
- Explanation: The Business Process Choreographer beans configuration cannot be created.
- User Action: Determine the reason for the creation failure.
- CWWBF0004E: Argument passed to the configuration is not valid; argument name: {0}, value: {1}.
- Explanation: The passed argument value does not correspond with the expected values.
- User Action: Refer to the command-line help to determine the correct argument values.
- CWWBF0005E: Expected to run on a Microsoft Windows platform.
- Explanation: The configuration is designed to run on Microsoft Windows operating systems but was called on a different platform.
- User Action: Run the configuration on a Microsoft Windows operating system.
- CWWBF0006E: Error while creating the data source for database {0}.
- Explanation: A data source cannot be created.
- User Action: Determine the reason for the failure.
- CWWBF0007I: Creating database {0} ...
- Explanation: The system is creating the database.
- User Action: None.
- CWWBF0008I: Creating table space {0} using {1}...
- Explanation: The system is creating the tablespace.
- User Action: None.
- CWWBF0009I: Creating database schema for {0} ...
- Explanation: The system is creating the database schema.
- User Action: None.
- CWWBF0010I: Database {0} has been created successfully.
- Explanation: The database has been created successfully.
- User Action: None.
- CWWBF0011E: The EAR file ''{0}'' cannot be opened.
- Explanation: The EAR file for installing the process module cannot be opened.
- User Action: Check the EAR file for availability.
- CWWBF0012E: The FAR file ''{0}'' cannot be deployed.
- Explanation: Error during the deployment of the process archive (FAR) file.
- User Action: Check that the FDML files for the process module are correct.
- CWWBF0013E: The process module ''{0}'' cannot be configured.
- Explanation: Error during the configuration of the process module.
- User Action: Check that the process descriptor ibm-process.xmi is correct.
- CWWBF0014E: Error during the installation of the EAR file {0}
- Explanation: Error during the installation of process modules.
- User Action: Check that the process containers are configure on the servers where you want the application to beinstalled. Check that an application server and the databases are running. Check that the process template names are unique within one application server or cluster.
- CWWBF0015I: Process module configuration of {0} completed.
- Explanation: A process module was successfully configured.
- User Action: None.
- CWWBF0016I: Process module deployment of {0} completed.
- Explanation: A process module was successfully deployed.
- User Action: None.
- CWWBF0017I: Process module installation of {0} completed.
- Explanation: A process module was successfully installed.
- User Action: None.
- CWWBF0018E: Cannot uninstall the business process container, because there are still applications with process modules installed: {0}
- Explanation: The business process container could not be uninstalled because there are still applications with process modules installed.
- User Action: First uninstall all enterprise applications with process modules then try again.
- CWWBF0019E: Application {0} with process modules cannot be uninstalled. All process templates of the application must be stopped and process instances removed from the database.
- Explanation: An enterprise application with process modules could not be uninstalled because not all process instances have been removed or some process templates have not been stopped.
- User Action: Remove all process instances and stop all process modules belonging to the enterprise application, then try again.
- CWWBF0020E: Unexpected error while removing process modules of application {0} from {1}: {2}
- Explanation: An unexpected error occurred while removing the application''s process modules. The detail error message is {2}.
- User Action: Fix error {2} then try again.
- CWWBF0021I: Uninstall of process application {0} completed.
- Explanation: The processes belonging to the application have been successfully uninstalled.
- User Action: None.
- CWWBF0022E: Unexpected error while removing the process modules belonging to application {0}: {1}
- Explanation: An unexpected error occurred while removing the application''s process modules. The detailed error message is {1}.
- User Action: Fix error {1} then try again.
- CWWBF0023E: Cannot install the process application. There is no EJB JAR or WAR file in the EAR file to be installed: {0}
- Explanation: An EAR file that contains FAR files must also contain at least one EJB JAR or WAR file.
- User Action: Make sure that the EAR file contains at least one EJB JAR or WAR file.
- CWWBF0024E: Process {0} of application {1} is not stopped. Stop the templates manually before updating or uninstalling a process application.
- Explanation: All processes belonging to an application must be stopped before you can uninstall it.
- User Action: Stop the template and retry uninstalling.
- CWWBF0025E: Process {0} of application {1} still has instances. Terminate and delete all process instances before updating or uninstalling a process application.
- Explanation: A process application cannot be uninstalled if it still has processes with instances.
- User Action: Remove the instances and retry uninstalling.
- CWWBF0026E: Node {0} is not migrated to process choreographer version 5.1. BPEL applications cannot be installed on this node.
- Explanation: Process choreographer versions before 5.1 do not support BPEL applications.
- User Action: Migrate the node to Version 5.1.
- CWWBF0028I: Process components of {0} have been successfully configured in the WebSphere configuration repository.
- Explanation: The configuration file for the process components of the application was added to configuration repository.
- User Action: None.
- CWWBF0029E: Process components of {0} cannot be configured in WebSphere configuration repository.
- Explanation: An error while generating a configuration file for the process components of the application.
- User Action: Check that the BPEL and component files are correct.
- CWWBF0030E: Error during update of Business Process Choreographer database with processes for application {0}:{1}
- Explanation: It was not possible to complete updating the Business Process Choreographer database with business processes metadata.
- User Action: None.
- CWWBF0031I: Completed updating the Business Process Choreographer databases with processes for application {0}.
- Explanation: The Business Process Choreographer database was updated successfully with business processes metadata.
- User Action: None.
- CWWBF0032E: Unexpected error during uninstall of application with process components {0}: {1}
- Explanation: The processes for the application cannot be removed from the Business Process Choreographer databases.
- User Action: None.
- CWWBF0034E: Business process {0} {1} is already registered for application {2}
- Explanation: The name of a business process and the date, from which it can be instantiated, must be unique within the Business Process Choreographer database.
- User Action: Choose a different business process name when modelling the process.
- CWWBF0035E: Cannot find matching service and port for port type {0}.
- Explanation: Referenced port types in component files must have matching port types in the target component file, otherwise an appropriate service and port cannot be found.
- User Action: Regenerate the EAR file and specify port and service for each partner link in your process definition.
- CWWBF0036I: Successfully bound service references of application {0}.
- Explanation: All referenced services or processes have been bound to the appropriate JNDI name.
- User Action: None.
- CWWBF0037E: A service name is not specified for port type {0} in the component file.
- Explanation: Each port type in the WSDL section of a component file must also have a service name specified.
- User Action: Regenerate the EAR file and specify a port and service for each partner link in your process definition.
- CWWBF0038E: A port name is not specified for port type {0} in the component file.
- Explanation: Each port type in the WSDL section of a component file must also have a port name specified.
- User Action: Regenerate the EAR file and specify a port and service for each partner link in your process definition.
- CWWBF0039E: Error loading component file {0}: {1}
- Explanation: The file content does not comply to the WCDL XSD.
- User Action: Correct the component file and deploy again.
- CWWBF0040E: Error loading BPEL file {0}: {1}
- Explanation: The BPEL file cannot be loaded.
- User Action: Correct the BPEL file references.
- CWWBF0041E: Error loading wiring file {0}: {1}
- Explanation: The BPEL file cannot be loaded. This is because either the file is not found or because the file does conform to the XSD.
- User Action: Check wiring file.
- CWWBF0042E: Wrong component file reference: {0}
- Explanation: A reference to a component file in the wiring file is not valid.
- User Action: Check references in wiring file.
- CWWBF0043E: No references to port types are found for this partner link: {0}
- Explanation: Component files contain references to port types with the name of the partner link.
- User Action: Check references in the component files.
- CWWBF0044E: Component name {0} differs from process name {1}.
- Explanation: Name attribute in the BPEL file must be the same as the name attribute in the component file.
- User Action: Correct names.
- CWWBF0045E: Cannot find environment reference for partner link {0} in the EJB JAR file {1}.
- Explanation: Each partner link must have corresponding environment references in the deployment descriptor of the EJB JAR file.
- User Action: Regenerate the EAR file.
- CWWBF0046I: Database update is skipped according to deployment option.
- Explanation: During migration the database update is skipped.
- User Action: None.
- CWWBF0047E: Data source necessary for installing the enterprise application is not found.
- Explanation: Data source for installing the business processes in the Business Process Choreographer database is not found.
- User Action: Ensure that the business process container is configured correctly.
- CWWBF0049E: Cannot resolve staff plug-in JNDI name. The corresponding server might not be running.
- Explanation: A running server is needed during deployment to lookup the JNDI name of the staff plug-in.
- User Action: Start at least one server per cluster, and try again.
- CWWBF0050W: Table.ddl file for automatic creation of tables of type {0} not found, although this option is selected. Skipping creation of tables for module {1}.
- Explanation: The tables for the process entity EJBs can only be created if there is a corresponding Table.ddl in the EJB module.
- User Action: In WebSphere Integration Developer, either generate TopDownMapping, or skip RMIC code generation for the EJB modules.
- CWWBF0051I: Created tables for module: {0}.
- Explanation: During deployment the tables for process entity EJBs are created automatically, if the corresponding option is specified.
- User Action: None.
- CWWBF0052I: Overwriting invalid application in database: {0}.
- Explanation: There are fragments of an invalid application in the database, probably from a previous deployment attempt. These fragments are being removed before the new application is written into the database.
- User Action: None.
- CWWBF0054I: Deleted table {0} from data source {1}.
- Explanation: The tables for the process entity EJBs have been deleted from the database.
- User Action: None.
- CWWBF0055W: Could not delete table {0} from data source {1}.
- Explanation: During process application uninstall, an attempt is made to delete the tables for the corresponding process entity EJBs.
- User Action: Delete the tables manually.
- CWWBF0056W: Failed to delete the tables for the container managed process entity beans.
- Explanation: During process application uninstall, an attempt is made to delete the tables for the corresponding process entity EJBs.
- User Action: Delete the tables manually.
- CWWBF0057E: The application cannot be stopped because of existing process instances.: {0}
- Explanation: An application cannot be stopped if instances of its process templates exist. The exception to this case is when the server is shut down; the application is stopped even if process instances exist.
- User Action: Delete all of the instances of the process templates that belong to the application and try again.
- CWWBF0058W: Could not check the process application for existing instances of its processes.
- Explanation: An application cannot be stopped if instances of its process templates exist. The exception to this case is when the server is shut down. The check for existing instances could not be executed. The Business Process Choreographer database might not be accessible.
- User Action: Check that the server is running and the database is connected.
- CWWBF0059E: Cannot find the configuration for the business process container application {0}.
- Explanation: A process container must be configured and the corresponding application installed on each deployment target of the business process application.
- User Action: Configure the process container on the respective server or cluster.
- CWWBF0061W: Cannot register or unregister business processes of the application {0} with the debugger.
- Explanation: The processes of an application must be registered with the process debugger when the application is started.
- User Action: Restart the business processes explicitly, for example, with the administrative console.
- CWWBF0062W: Cannot register or unregister the business process {0} {1} with the process debugger.
- Explanation: Processes are registered with the process debugger when they start and unregistered when they stop.
- User Action: Restart the business processes explicitly, for example, with the administrative console.
- CWWBF0063I: The WebSphere Process Server is not configured to run business process applications.
- Explanation: Enabeling a WebSphere Process server to run business processes requires that the Business Process Contianer be configured. Configuring the Business Process Container is a separate action that needs to be performed after the WebSphere Process Server has been created. This server has not had the Business Process Container configured.
- User Action: Configure business process container.
- CWWBF0064E: {0} is not configured to run business process applications.
- Explanation: Enabeling a WebSphere Process Server to run business processes requires that the Business Process Contianer be configured. Configuring the Business Process Container is a separate action that needs to be performed after the WebSphere Process Server has been created. This server has not had the Business Process Container configured.
- User Action: Configure business process container and try to install the application again.
- CWWBF0100E: Configuration error: ''{0}''. Error parameter(s): {1}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Make sure that all process templates that belong to the application are stopped and there are no running instances before you uninstall a process application.Check that there are no process applications on the server where you want to uninstall the process container.
- CWWBF0101I: Configuration information: ''{0}''. Information parameter(s): {1}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: None.