- 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: No action is required.
- CWWBF0008I: Creating table space {0} using {1}...
- Explanation: The system is creating the tablespace.
- User Action: No action is required.
- CWWBF0009I: Creating database schema for {0} ...
- Explanation: The system is creating the database schema.
- User Action: No action is required.
- CWWBF0010I: Database {0} has been created successfully.
- Explanation: The database has been created successfully.
- User Action: No action is required.
- 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 be installed. 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: No action is required.
- CWWBF0016I: Process module deployment of {0} completed.
- Explanation: A process module was successfully deployed.
- User Action: No action is required.
- CWWBF0017I: Process module installation of {0} completed.
- Explanation: A process module was successfully installed.
- User Action: No action is required.
- CWWBF0018E: Cannot uninstall Business Process Choreographer, because there are still applications with process modules installed: {0}
- Explanation: Business Process Choreographer 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: No action is required.
- 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 at version {1} which does not yet support BPEL applications.
- Explanation: Process Choreographer versions before 5.1 do not support BPEL applications.
- User Action: Migrate the node to Version 5.1 or later.
- CWWBF0027E: Business processes cannot be installed on the default target deployment manager.
- Explanation: The default install target is the deployment manager. This server does not support business processes.
- User Action: Specify a server or cluster that is configured for business processes as the install target.
- 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: No action is required.
- 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: Use the provided failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- 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: No action is required.
- 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: Use the provided failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- CWWBF0033E: Error during lookup of data source {0} for server or cluster {1}.
- Explanation: The configuration of the business process container for the deployment target points to a data source JNDI name that cannot be resolved. This might happen if the business process container is not configured for the deployment target or the corresponding server is not running.
- User Action: Check if a data source with the given name is registered with the name server. Make sure that the server that is specified as the deployment target is actually running.
- 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: No action is required.
- 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: No action is required.
- 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.
- CWWBF0048E: Connection necessary for installing the enterprise application is not found.
- Explanation: Connection 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 the people directory configuration JNDI name. The corresponding server might not be running.
- Explanation: A running server is needed during deployment to lookup the JNDI name of the people directory configuration.
- 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: No action is required.
- 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: No action is required.
- CWWBF0053E: Administration process is not connected to running server.
- Explanation: During deployment a connection to a running server is required. In an ND environment, this must be the deployment manager.
- User Action: Do not use the "-conntype NONE" option when installing a process application.
- CWWBF0054I: Deleted table {0} from data source {1}.
- Explanation: The tables for the process entity EJBs have been deleted from the database.
- User Action: No action is required.
- 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.
- CWWBF0060E: Cannot find a specific session EJB {0} for the process.
- Explanation: Each business process application must contain a generated specific session EJB.
- User Action: Regenerate code of application in WebSphere Integration Developer.
- 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: To be able to run business processes, you must configure Business Process Choreographer. This is a separate action that must be performed after the WebSphere Process Server has been created.
- User Action: Configure Business Process Choreographer.
- CWWBF0064E: {0} is not configured to run business process applications.
- Explanation: To be able to run business processes, you must configure Business Process Choreographer. This is a separate action that must be performed after the WebSphere Process Server has been created.
- User Action: Configure Business Process Choreographer and try to install the application again.
- CWWBF0065E: Business process applications generated with version {0} cannot be installed on deployment targets of version {1}.
- Explanation: The version of the deployment target is earlier than the version of the generator that was used to create the business process application.
- User Action: Specify a server or cluster that is the same version as, or later than, as the version of the generator that was used to create the business process application. When you install on a cluster, make sure that all of the cluster members are at the latest version.
- CWWBF0066E: Unable to access the Business Process Choreographer database tables.
- Explanation: The database tables for Business Process Choreographer must be present to install a business process application but the tables could not be accessed.
- User Action: Check the database configuration and make sure that the database tables were created successfully.
- CWWBF0067E: Unable to access the Business Flow Manager Management Bean.
- Explanation: The JMX Management Bean for Business Flow Manager must be present to uninstall business process applications but it could not be reached.
- User Action: Make sure that all the servers that the application is mapped onto are running.
- CWWBF0068E: Unable to access the temp folder.
- Explanation: The Business Flow Manager cannot access the temp folder.
- User Action: Check the access rights of the <WASHome>/wstemp folder.
- CWWBF0069E: Unable to extract the EAR file {0} to the temp folder {1}.
- Explanation: The Business Flow Manager cannot extract the contents of the EAR to the temp folder.
- User Action: Check the access rights of the <WASHome>/wstemp folder.
- CWWBF0070W: Removing invalid Business Process template {0} - validFrom: {1} from the Business Process Choreographer database.
- Explanation: The Business Flow Manager detected a business process template in the Business Process Choreographer database that is not configured in the WebSphere Configuration Repository. Therefore the business process template will be removed.
- User Action: No action is required.
- CWWBF0071W: Detected invalid Business Process template {0} - validFrom: {1} in the Business Process Choreographer database.
- Explanation: The Business Flow Manager detected a business process template in the Business Process Choreographer database that is not configured in the WebSphere Configuration Repository. This business process template still has associated instances.
- User Action: Either reinstall the application that contains the business process template to allow the remaining instances to finish, or use the deleteInvalidProcessTemplate.py script from the Process Choreographer directory to clean up the Business Process Choreographer database.
- CWWBF0072E: Unable to resolve Business Process Component implementation section of component: {0}.
- Explanation: The implementation section of the Business Process Component specifies the location of the BPEL file.
- User Action: Make sure that the implementation sections points to a valid BPEL file in the EAR file.
- CWWBF0073E: The 'CommitMessagingTransactionsLast' JVM property is not set.
- Explanation: The application 'BPEContainer' was not started to avoid the risk of long-running processes hanging in the running state. To use an Oracle database the 'CommitMessagingTransactionsLast' JVM property must be set to 'true' for this server.
- User Action: Consult the latest 6.0.2 installation instructions for additional details and instructions how to set this property.
- 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: No action is required.
- CWWBF0102E: An error occurred while attempting the requested configuration change for the application named {0}: {1}
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Check the failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- CWWBF0103E: The application cannot be installed or uninstalled, because these operations are not supported on back-level deployment targets. The version of the deployment target with the node name {0} is {1} is older than that of the deployment manager version {2}.
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Make sure that your deployment targets are on the same level as the deployment manager.
- CWWBF0104E: Cannot find the SCA EJB module jar file in the application {0}. This jar file is required for applications containing business processes.
- Explanation: The requested configuration change cannot be processed for this application, because it contains one or more business process components that require the SCA EJB module jar file within the business process application.
- User Action: Make sure that this SCA EJB module jar file is available in the application. For example, regenerate the application code in WebSphere Integration Developer.
- CWWBF0105E: The application cannot be installed, because it contains at least one business process, which contains inline human tasks that use the ''Group'' people assignment criteria. However, group work items are disabled on the deployment target {0}.
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Make sure that your deployment targets have either group work items enabled, or your human tasks do not use the 'Group' people assignment criteria.
- CWWBF0106E: The following unexpected error occurred when attempting the requested configuration change: ''{0}''.
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Use the provided failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- CWWBF0107E: The following unexpected error occurred when attempting the requested configuration change: ''{0}''.
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Use the provided failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- CWWBF0108E: An unexpected error occurred when attempting the requested configuration change for the application with the name {0}: {1}
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Use the provided failure reason to resolve the issue. If the problem still persists, check the technical information databases at www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or see www.ibm.com/software/integration/wps/support/ again for information about IBM Software Support and Services.
- CWWBF0109W: The {0} business process template - validFrom: {1} was detected in the started state during uninstallation.
- Explanation: During uninstallation of the specified process template, the Business Flow Manager detected that the process template was in the started state. Uninstallation will continue. However, generally, all process templates that belong to an application should be stopped before uninstallation.
- User Action: No action is required.
- CWWBF0110E: The following unexpected error occurred during validation of the {0} process: {1}
- Explanation: The requested configuration change cannot be processed for this application.
- User Action: Use the error text to resolve the problem. If the problem persists, check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBF0111E: The cleanup service encountered an unexpected error when attempting to delete the {0} process instance. Reason for the failure: {1}
- Explanation: The deletion cannot proceed for this process instance.
- User Action: Use the specified failure reason to resolve the problem. If the problem persists, check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBF0112E: The following unexpected error occurred when running the cleanup service for process instances: {0}
- Explanation: The cleanup service aborted processing and will run again at the next scheduled time.
- User Action: Use the specified failure reason to resolve the problem. If the problem persists, check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBF0113W: The specified value {0} for the maximum duration of one cleanup service run is not valid. The cleanup service will default to an infinite duration.
- Explanation: The maximum duration must be an integer value that specifies the maximum duration of one cleanup service run in minutes.
- User Action: In the administrative console, change the setting to a valid value.
- CWWBF0114W: The specified value {0} for the maximum slice of instances to delete during one cleanup service job run is not valid. The cleanup service will default to a slice value of 10.
- Explanation: The slice value must be an integer value.
- User Action: In the administrative console, change the setting to a valid value.
- CWWBF0115E: The cleanup service cannot process because it is not running with business process administrator privileges.
- Explanation: The cleanup service must run with business process administrator privileges.
- User Action: In the administrative console, configure a user with business process administrator privileges as CleanupUser on the business process container.
- CWWBF0116I: The cleanup service started executing cleanup job {0}.
- Explanation: All instances configured for scheduled deletion by this job will be removed during this job run. The cleanup service will stop processing, if the configured maximum cleanup service duration is reached.
- User Action: No action is required.
- CWWBF0117I: The cleanup service finished executing cleanup job {0}. It deleted {1} instances.
- Explanation: The cleanup service finished the scheduled deletion for this job. Please note, that the number of deleted instances does specify the number of top-level instances. For businesses processes, this will be only the number of parent processes, while the child processes are deleted as well.
- User Action: No action is required.