WebSphere Process Server messages     Operating Systems: All supported
CWSTM0001E: The installation of the application failed. An error occurred while running the dynamic artifact repository application install task.
Explanation: An error occurred while installing an application that contains a business rule group or a selector component. The application was not installed correctly. See the logged exception for more information.
User Action: Correct the error reported in the logged exception and try again.

 

CWSTM0002E: An error occurred while registering the dynamic artifact repository application install task provider with the server runtime.
Explanation: An error occurred while registering the task provider with the server runtime. See the logged exception for more information.
User Action: Correct the error reported in the logged exception. The server may need to be restarted.

 

CWSTM0003I: The business rules and selector auditing service has started.
Explanation: This is an informational message. The business rules and selector auditing service has successfully started and auditing is now available for business rules and selectors.
User Action: No action is required.

 

CWSTM0004E: The connection to the data source with a JNDI name of jdbc/WPSDB that is used to hold business rules and selectors failed as it may not have been created or it is unreachable.
Explanation: Possible causes of the problem are, if the database is local, the database has not been started, or if the database is remote, network connectivity is not established.
User Action: If the database is local to the system where the server is running, make sure that the database has been started. If the database is on a remote system, make sure that the network connectivity to the remote system and the database are active. You can also use the test connection option in the administrative console to test general connectivity to the database. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0008E: An error occurred while processing a business rules or selector artifact during startup.
Explanation: During server or application startup, business rules or selector artifacts that are in the application are stored in the repository. If a business rule or selector is not valid XML, the storage operation fails.
User Action: Validate the XML for the application business rules or selector artifacts.

 

CWSTM0010E: An error occurred while parsing the {0} tag.
Explanation: While parsing the customization-timestamp.xml file an unknown tag or an invalid value for the tag was found. The customization-timestamp.xml file is system generated and contains the timestamp for the business rule or selector selection data.
User Action: In the customization-timestamp.xml, correct the problem manually or redeploy and reinstall the application to have a new customization-timestamp.xml file generated.

 

CWSTM0011E: The business rule class {0} cannot be found.
Explanation: The specified class could not be found using the classpath. Either the class is not included in the classpath or the class was deleted.
User Action: If the class has been deleted, try to reconstruct it by exporting the component back to the development environment and then redeploying.

 

CWSTM0012E: The business rule class {0} cannot be constructed.
Explanation: The specified class cannot be constructed using the default constructor. This is a system generated class that was replaced with a customized version.
User Action: If the expected class was replaced with another version, try to reconstruct it by exporting the component back to the development environment and then redeploying.

 

CWSTM0013E: The business rule class {0} does not implement the system provided BusinessRule interface.
Explanation: The specified class must implement the system provided BusinessRule interface. This is a system generated class that was replaced with a customized version.
User Action: If the expected class was replaced with another version, try to reconstruct the class by exporting the component back to the development environment and then redeploying.

 

CWSTM0014E: The following Service Component Architecture target cannot be found: Component name: {0}, Import name: {1}, Module name: {2}, Export name: {3}.
Explanation: The selection table includes a target that is not known to the server. The most likely reason is that the target is either not installed or does not have an export binding. If the target is not packaged with the selector component in the same module then the target must be installed through its own module and include an export binding.
User Action: Install the specified component.

 

CWSTM0015E: The selection target {0} is not supported.
Explanation: The business rule selection table or the selector selection table contains a selection target entry of a type that is not supported. Business rule components support selection targets of type BusinessRuleSelectionData. Selector components support selection targets of type SCAInternalComponent, SCAImportedComponent or SCAExportedComponent.
User Action: In the business rule selection table or the selector selection table remove the unsupported target entry.

 

CWSTM0016E: An error occurred while performing a dynamic artifact repository operation.
Explanation: An error occurred while reading or writing data from the dynamic artifact repository. This error most likely occurred as a result of the data not existing in the database on a read or a duplicate key exception on a write. See the logged exception for more information.
User Action: Correct the problem as described in the details of the logged exception and retry the operation.

 

CWSTM0017E: The business rule class {0} cannot be created.
Explanation: An attempt to reflectively create an instance of the business rule class failed with an IllegalAccessException. The BusinessRuleInvocationTarget runtime class does not have access to the definition of the specified class. The backing class may have been deleted from the business rule application.
User Action: If the business rule class was deleted, try to reconstruct the class by exporting the component back to the development environment and then redeploying.

 

CWSTM0018E: An exception was encountered while performing artifact export: {0}
Explanation: While exporting business rule or selector components from the server, an unexpected exception occurred. This exception occurred during the invocation to the system to retrieve the component artifacts or while writing the artifacts to the zip file. For example, the server may not be running or the user may not have authority to the write to the file system.
User Action: Analyze the logged exception and correct the problem. For debug information, edit the exportSelectorArtifacts script file for selector components or the exportBusinessRuleArtifacts script file for business rules and set debugOutFlag=1. The script files are located in the bin directory of the server installation.

 

CWSTM0019E: The artifacts cannot be exported due to the following error: {0}
Explanation: The business rule or selector component that was specified to be exported is not known to the server.
User Action: Verify that the script is executed on the server that has the component installed. Use the administration console for viewing the installed selector components or use the business rule manager for viewing the installed business rule components. For debug information, edit the exportSelectorArtifacts script file for selector components or the exportBusinessRuleArtifacts script file for business rules and set debugOutFlag=1. The script files are located in the bin directory of the server installation.

 

CWSTM0020E: The script invocation includes incorrect parameters. The correct use is {0}.
Explanation: Incorrect parameters were given on the script invocation.
User Action: For the script usage instructions, invoke the script with the no parameters.

 

CWSTM0021E: The dynamic artifact repository configuration stopped. The error is {0}.
Explanation: While installing and configuring the dynamic artifact repository an unexpected exception occurred. Possible causes may be that the specified database in the property file is not supported or the datasource is not installed.
User Action: For the proper script usage instructions invoke the script with no parameters. For debug information, edit the configureArtifactRepository script file and set debugOutFlag=1. The script file is located in the bin directory of the server installation.

 

CWSTM0022E: The artifact repository configuration stopped. The error is {0}.
Explanation: The installation and configuration of the dynamic artifact repository failed. Possible causes are that the specified property file cannot be read, cannot create the JDBC provider, cannot create the security object for the database connection or cannot create the datasource.
User Action: For the proper script usage instructions invoke the script with no parameters. For debug information, edit the configureArtifactRepository script file and set debugOutFlag=1. The script file is located in the bin directory of the server installation.

 

CWSTM0023W: A new artifact replaced an artifact in the repository. The new artifact has the type {0}, the target namespace {1}, and the name {2}, and it is associated with the application {3}.
Explanation: A new application has been installed that contains the specified artifact. This new artifact is stored in the repository. However, an artifact exists with the same type, target, namespace, and name. The existing artifact is associated with another application. The new artifact will replace the existing one.
User Action: This is not necessarily an error. However, it indicates that two applications exist, each containing an artifact with the same type, target namespace, and name. The artifact from the most recently installed application is the only one present in the repository. If the two applications are unrelated and have artifacts that have the same type, target namespace, and name, this is likely a problem. If each application has a copy of the same artifact, this may not be a problem.

 

CWSTM0024E: An exception was encountered while performing artifact import: {0}
Explanation: While importing business rule or selector components to the server, an unexpected exception occurred. This exception occurred during the invocation to the system to import the component artifacts or while reading the artifacts from the zip file. For example, the server may not be running or the exported zip file to import is the wrong version. The import can only use zip files that were exported using the exportSelectorArtifacts.jacl script or through the administration console. Exported files created using a WPS version prior to v6.0.2 are not supported.
User Action: If the exported zip file is not the right version export the component using a supported version. For debug information, edit the importSelectorArtifacts script file for selector components or the importBusinessRuleArtifacts script file for business rules and set debugOutFlag=1. The script files are located in the bin directory of the server installation.

 

CWSTM0025E: Artifacts cannot be imported due to the following error: {0}
Explanation: The export file that was specified to be imported cannot be found.
User Action: Correct the name and path of the export file to point to the right zip file. For debug information, edit the importSelectorArtifacts script file for selector components or the importBusinessRuleArtifacts script file for business rules and set debugOutFlag=1. The script files are located in the bin directory of the server installation.

 

CWSTM0026I: The application {0}, which has business rules or selectors, is being replaced.
Explanation: This is an informational message. The information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0027I: An attempt was made to update one or more {0} from the {1}.
Explanation: This is an informational message. An attempt was made to update a business rules group, business rules rule set, or business rules decision table from the business rules manager or the business rule management APIs. This audit message is generated when an attempt is made to update one of these artifacts through the business rules manager or the business rule management APIs. It is generated before the business rules item is committed to the repository. This information is recorded for auditing purposes only. The details of what is changing are recorded in the audit destinations.
User Action: No action is required.

 

CWSTM0028I: One or more {0} from the {1} were updated successfully.
Explanation: This is an informational message. The attempt to update a business rules group from the business rules manager or through the business rule management APIs was successful. This information is recorded for auditing purposes only. The details of what is changing are recorded in the audit destinations.
User Action: No action is required.

 

CWSTM0029I: The update of a {0} from the {1} failed.
Explanation: The attempt to update a business rules group, business rules rule set, or business rules decision table from the business rules manager or through the business rule management APIs failed. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0030I: An attempt was made to update the {0} named {1}.
Explanation: This is an informational message. An attempt was made to update a business rules group, business rules rule set, business rules decision table, or selector artifact. This audit message is generated when an attempt is made to update one of these artifacts through the administrative console. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0031I: The {0} named {1} was updated successfully.
Explanation: This is an informational message. The attempt was successful to update the business rules group, business rules rule set, business rules decision table or the selector artifact through the administrative console. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0032I: The update of the {0} named {1} failed
Explanation: The attempt to update the business rules group, business rules rule set, business rules decision table or the selector artifact through the administrative console failed. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0033I: An attempt to import a {0} component named {1}.
Explanation: This is an informational message. An attempt was made to import a business rules group or selector component. This audit message is generated when an attempt is made to import one of these artifacts through the administrative console or the command line. The information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0034I: The {0} component named {1} was imported successfully.
Explanation: This is an informational message. The attempt to import a business rules group or selector component was successful. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0035I: The attempt to import {0} component named {1} failed.
Explanation: This is an informational message. The attempt to import a business rule group or selector component failed. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0036I: An attempt was made to export a {0} component named {1}.
Explanation: This is an informational message. An attempt was made to export a business rules group or selector component. This audit message is generated when an attempt is made to export one of these artifacts through the administrative console or the command line. The information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0037I: The {0} component named {1} was exported successfully.
Explanation: This is an informational message. The attempt to export a business rule group or selector component was successful. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0038I: The export of the {0} component named {1} failed.
Explanation: This is an informational message. The attempt to export a business rule group or selector component failed. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0039I: An attempt was made to start an application with a {0} artifact named {1}.
Explanation: This is an informational message. An attempt was made to start an application containing a business rule or selector artifact. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0040I: The attempt to start an application with a {0} artifact named {1} failed.
Explanation: This is an informational message. An attempt to start an application containing a business rule or selector artifact failed. This information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0041I: An application with business rules or selectors is starting, and the {0} has been stored.
Explanation: This is an informational message. The information is recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0042E: An attempt to connect or interact with a datasource failed during migration of an application containing business rules or selectors.
Explanation: The installed application containing business rules or selectors was using a datastore on Cloudscape, Informix or SQL Server. Migration of this application will copy the data from the existing datastore to a datastore with a datasource named jdbc/WPSDB. An attempt to obtain a connection or to interact with the originating datasource or the new datasource failed. The datasource has a name of jdbc/WPSDB or jdbc/wbiserver/DynamicArtifactRepository.
User Action: If the database is local to the system where the server is running, make sure that the database has been started. If the database is on a remote system, make sure that the network connectivity to the remote system and the database are active. You can also use the test connection option in the administrative console to test general connectivity to the database. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0043E: An attempt to connect with a datasource failed during migration of an application containing business rules or selectors.
Explanation: The installed application containing business rules or selectors was using a datastore on Cloudscape, Informix or SQL Server. Migration of this application will copy the data from the existing datastore to a datastore with a datasource named jdbc/WPSDB. An attempt to obtain a connection to the originating datasource or the new datasource failed. The datasource has a name of jdbc/WPSDB or jdbc/wbiserver/DynamicArtifactRepository.
User Action: If the database is local to the system where the server is running, make sure that the database has been started. If the database is on a remote system, make sure that the network connectivity to the remote system and the database are active. You can also use the test connection option in the administrative console to test general connectivity to the database. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0044I: The migration of an application with business rules or selectors was successful.
Explanation: This is an informational message. The migration of the application with business rules or selectors was successfully migrated from the original datastore to the new datastore. The data in the original datastore was left intact to assist in possible future recovery of the original data. The migrated application will use the data in the new datastore. This information is being recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0045I: Migration of business rules or selectors was not necessary.
Explanation: This is an informational message. During server migration no applications containing business rules or selectors were found. This information is being recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0046E: The attempt to migrate an application containing business rules or selectors failed.
Explanation: Problems were encountered during migration of an application containing business rules or selectors when copying the data from the datasource named jdbc/wbiserver/DynamicArtifactRepository to the datasource named jdbc/WPSDB. One possible cause of the error is that the data in the datasource named jdbc/wbiserver/DynamicArtifactRepository is corrupted and cannot be read or written to the datasource named jdbc/WPSDB.
User Action: If the database is local to the system where the server is running, make sure that the database has been started. If the database is on a remote system, make sure that the network connectivity to the remote system and the database are active. You can also use the test connection option in the administrative console to test general connectivity to the database. If Derby is the JDBC provider for the datasource named jdbc/wbiserver/DynamicArtifactRepository use the provided ij.bat or ij.sh tool to connect to the database. If the JDBC provider is DB2 use a DB2 command prompt or the DB2 Control Center to connect to the database. Once connected select content from the rep.bytestore, rep.bytestoreoverflow, and rep.apptimestamp tables (SELECT * FROM REP.BYTESTORE) to test successful retrieval of the data. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0047I: The datasource named jdbc/wbiserver/DynamicArtifactRepository was removed during business rules and selector migration.
Explanation: During business rules and selector migration a datasource named jdbc/wbiserver/DynamicArtifactRepository was found. The data was copied from this datastore to the new datastore named jdbc/WPSDB and the datastore was removed. Business rule and selector applications will use the new datastore. This information is being recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0048I: The JDBC provider that has a datasource name of jdbc/wbiserver/DynamicArtifactRepository was removed during business rules and selector migration.
Explanation: During business rules and selector migration a datasource named jdbc/wbiserver/DynamicArtifactRepository was found. The data was copied from this datastore to the new datastore named jdbc/WPSDB. The jdbc/wbiserver/DynamicArtifactRepository was the only datasource under the JDBC provider and the JDBC provider was removed. This information is being recorded for auditing purposes only.
User Action: No action is required.

 

CWSTM0049E: An attempt to remove the JDBC provider that has a datasource name of jdbc/wbiserver/DynamicArtifactRepository during business rules and selector migration failed.
Explanation: During business rules and selector migration a datasource named jdbc/wbiserver/DynamicArtifactRepository was found. The data was copied from this datastore to the new datastore named jdbc/WPSDB. The jdbc/wbiserver/DynamicArtifactRepository was the only datasource under the JDBC provider and an attempt was made to remove the JDBC provider. An error was encountered while retrieving the datasource or the JDBC provider.
User Action: Using the administrative console, check for a datasource with a JNDI name of jdbc/wbiserver/DynamicArtifactRepository and if it exists remove the datasource. If this is the only datasource associated with the JDBC provider then remove the JDBC provider. If the datasource and JDBC provider do not exist then restart the server. Make a backup before configuration of these changes using the manageprofiles script.

 

CWSTM0050E: An attempt to connect to the admin service during business rules and selector migration failed.
Explanation: An error occurred when connecting to the admin service while attempting to remove the datasource named jdbc/wbiserver/DynamicArtifactRepository and the JDBC provider during business rules and selector migration.
User Action: Using the administrative console, check for a datasource with a JNDI name of jdbc/wbiserver/DynamicArtifactRepository and if it exists remove the datasource. If this is the only datasource associated with the JDBC provider then remove the JDBC provider. If the datasource and JDBC provider do not exist then restart the server. Make a backup before configuration of these changes using the manageprofiles script.

 

CWSTM0051E: An attempt to find a datasource during business rules and selector migration failed.
Explanation: During business rules and selector migration a datasource named jdbc/wbiserver/DynamicArtifactRepository was found and the data was copied from this datastore to the new datastore named jdbc/WPSDB. An attempt to find the datasource through the admin service failed and the datasource was not removed.
User Action: Using the administrative console, check for a datasource with a JNDI name of jdbc/wbiserver/DynamicArtifactRepository and if it exists remove the datasource. If this is the only datasource associated with the JDBC provider then remove the JDBC provider. If the datasource and JDBC provider do not exist then restart the server. Make a backup before configuration of these changes using the manageprofiles script.

 

CWSTM0052E: An attempt to migrate an application containing business rules or selectors failed.
Explanation: An error occurred when attempting to connect to the admin service to retrieve the datasources named jdbc/wbiserver/DynamicArtifactRepository and jdbc/WPSDB. The migration of the business rules or selector data was not migrated from the datasource named jdbc/wbiserver/DynamicArtifactRepository to the datasource named jdbc/WPSDB.
User Action: Using the administrative console, check for datasources named jdbc/wbiserver/DynamicArtifactRepository and jdbc/WPSDB. Use the test connection option in the administrative console to test general connectivity to the database. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0053W: An attempt to retrieve a business rule artifact of type {2} and with a name of {0} and a target namespace of {1} that is of a version that is not supported on this server. A shell business rule group containing the artifact has been returned in place of the full business rule group and artifact.
Explanation: In an network deployment environment, it is possible for to have nodes and servers at different product levels. These different servers can support different business rule capability. If a business rule group component is installed into the system that is using capabilities that are not supported by a server when accessed, a shell business rule group is returned instead of throwing an exception. The shell business rule group contains the name and the namespace and is treated as a read-only object. A client application can be checked if a business rule group is a shell business rule group by checking for the property with a name of IBMSYSTEMShell. If the property exists with any type of value, the business rule group is a shell. Any access to any other attributes besides the business rule group name and target namesapce will result in an exception. The intent of the shell business rule group is to allow for servers which are running older versions of their business rule management clients to continue to support older artifacts without needing to move up to the latest server version. To have full management capabilities however, business rule management clients and the server they run on, should be upgraded to the latest version of WebSphere Process Server. If you are using the Business Rule Managager Web application and perform an upgrade, the Business Rule Manager will be updated to the correct level.
User Action: To obtain the full information for the shell business rule group, the server should be upgrade to the version which contains the appropriate support for the business rule groups that are being retrieved. The business rule management clients should also be updated with the correct support as well. For more information on migration, refer to the Migration on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/ or contact the server administrator.

 

CWSTM0054E: An attempt to reach the database tables for business rules and selectors failed because the database did not contain the APPTIMESTAMP, BYTESTORE, BYTESTOREOVERFLOW, and CUSTPROPERTIES tables as the tables were not created correctly at installation or migration time.
Explanation: An error occurred when attempting to connect to database tables that are used for busienss rules and selectors. These tables, APPTIMESTAMP, BYTESTORE, BYTESTOREOVERFLOW, and CUSTPROPERTIES, are created as part of the installation process. They can be created as part of profile creation or they can be created after a profile has been created. At migration time, they will be updated when the server first starts. The absence of these tables indicates that the profile was not created successfully, the database creation scripts were not run after the profile was created, or the migration of the server from a previous version was not successful in updating the database tables.
User Action: Using the appropriate database administrative client, check the database associated with the datasource jdbc/WPSDB and verify the APPTIMESTAMP, BYTESTORE, BYTESTOREOVERFLOW, and CUSTPROPERTIES tables have been created. If they do not exist, follow the instructions in the Information Center for creating the database tables after a profile has been created.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009