CWLDB

• CWLDB1001I
  Process application administration commands
• CWLDB1002I
  A group of commands that performs process application administration
• CWLDB1003I
  Command for importing a process application twix file.
• CWLDB1004I
  Command for importing a process application twix file.
• CWLDB1005I
  Command for installing a process application from process center to process server.
• CWLDB1006I
  Command for installing a process application from process center to process server.
• CWLDB1007I
  Command for uninstalling a process application.
• CWLDB1008I
  Command for uninstalling a process application.
• CWLDB1009I
  Command for starting a process application.
• CWLDB1010I
  Command for starting a process application.
• CWLDB1011I
  Command for stopping a process application.
• CWLDB1012I
  Command for activating a process application.
• CWLDB1013I
  Command for activating a process application.
• CWLDB1014I
  Command for deactivating a process application.
• CWLDB1015I
  Command for deactivating a process application.
• CWLDB1016I
  Command for archiving a process application.
• CWLDB1017I
  Command for archiving a process application.
• CWLDB1018I
  Name of the twix file to be imported.
• CWLDB1019I
  Acronym of the process application.
• CWLDB1020I
  Acronym of the snapshot.
• CWLDB1021I
  Acronym of the branch.
• CWLDB1022I
  Name of the install Package file.
• CWLDB1023I
  Desired state for the install.
• CWLDB0001I
  The Schema was updated successfully for the 0 component.
• CWLDB0002E
  The schema for the 0 component could not be updated.
• CWLDB0003I
  The version of the Process Server schema version was updated to 0 successfully.
• CWLDB0004W
  The updateSchema Admin Task command is not supported for the 0 process type.
• CWLDB0005I
  The schema was updated successfully for the following components: 0.
• CWLDB0006E
  The schema for the following components could not be updated: 0.
• CWLDB0007E
  The schema was not updated for the following components: 1.
• CWLDB0008I
  The common database schema is up to date.
• CWLDB0009E
  The schema could not be updated for the 2 component because the 0 SQL script could not be found. The system reported the following error: "1".
• CWLDB0010E
  The schema for the 0 component could not be updated to version 1. An attempt was made to run the 2 SQL script, but that attempt lead to an SQL error: "3".
• CWLDB0011E
  The schema for the 0 component could not be updated to version 1. An attempt was made to run the 2 SQL script, but that attempt lead to an input/out system error: "3".
• CWLDB0012E
  The schema for the 1 component could not be updated. The system reported the following error: "0".
• CWLDB0013E
  The schema for the 2 component could not be updated because the 0 migration configuration file is missing. The system reported the following error: "1".
• CWLDB0014E
  The schema for the 2 components could not be updated because there are syntax errors in the 0 configuration file. The system reported the following error: "1".
• CWLDB0015E
  The 0 application could not be started. The system reported the following error: "1".
• CWLDB0016E
  The common database schema update is not supported for WebSphere ESB version 0.
• CWLDB0017E
  The common database schema update is not supported for WPS version 0.
• CWLDB0018I
  The common database migration started successfully.
• CWLDB0021I
  The common database uses the default schema for the user that is configured.
• CWLDB0027I
  Common database admin commands
• CWLDB0028I
  A group of commands that invoke CommonDB utilities
• CWLDB0029I
  Process Server and WebSphere ESB admin commands for common database resources
• CWLDB0030I
  Process Server and WebSphere ESB admin commands for common database resources
• CWLDB0031I
  The update schema for the common database
• CWLDB0032I
  The update schema for the common database
• CWLDB0033I
  Retrieves the database type of the common database
• CWLDB0034I
  Retrieves the database type of the common database
• CWLDB0055I
  The schema name of the common database
• CWLDB0056I
  Retrieves the name of the common database
• CWLDB9001E
  There is more than one topology in the cell. You need to indicate the topology name to add nodes to.
• CWLDB9002W
  The Deployment manager configuration does not contain any topologies. This node cannot be added to topology.
• CWLDB9003W
  The topology in the cell is a custom topology. You cannot use Installer/PMT to configure this topology.
• CWLDB9004W
  The topology pattern does not match pattern in the cell.
• CWLDB9005W
  No topology is found in the cell.
• CWLDB9007W
  Node being added is not part of the topology.
• CWLDB9008I
  Deployment environment 0 of pattern 1 is in state 2.
• CWLDB9009I
  Creating cluster 0.
• CWLDB9010I
  Creating cluster member 0 on node 1 for cluster 2.
• CWLDB9011E
  Creating cluster 0 failed. Reason: 1.
• CWLDB9012E
  Creating cluster member 0 failed. Reason: 1.
• CWLDB9013I
  Configuring component 0 on deployment target 1.
• CWLDB9014E
  The configuration of component 0 failed. Reason 1.
• CWLDB9015I
  Deployment environment 0 is being generated.
• CWLDB9016E
  The generation for deployment environment 0 failed. Reason: 1. If in doubt, discard the changes and do not save the failed configuration to the master repository.
• CWLDB9017W
  Deployment environment 0 did not start completely. Reason: 1
• CWLDB9018E
  Deployment environment 0 failed to start. Reason: 1
• CWLDB9019W
  Deployment environment 0 did not stop completely. Reason 1
• CWLDB9020E
  Deployment environment 0 failed to stop. Reason 1
• CWLDB9021I
  Datasource 0 is configured at scope 1
• CWLDB9022I
  Creating authentication alias 0 for component 1.
• CWLDB9023E
  Importing the deployment environment from 0 failed. Reason: 1
• CWLDB9024E
  Exporting deployment environment 0 failed. Reason: 1
• CWLDB9025E
  Deployment environment 0 is invalid. Reason 1.
• CWLDB9026I
  Starting deployment environment 0.
• CWLDB9027I
  Stopping deployment environment 0.
• CWLDB9028I
  Role 0 being configured with this member 1
• CWLDB9029I
  Role member 0 is being configured with template name 1
• CWLDB9030I
  Component 0 being configured on the target 1
• CWLDB9031I
  Datasource has been configured with the following properties: 0
• CWLDB9032I
  SIBus Configuration details: name: 0, datasource: 1, authAlias: 2
• CWLDB9033I
  Topology Configuration completion with final state 0
• CWLDB9034I
  Importing node 0 into topology 1
• CWLDB9035I
  Adding node 0 to topology 1
• CWLDB9036W
  Deployment environment definition 0 is not found.
• CWLDB9037W
  Deployment environment definition 0 has already been configured. The operation 1 cannot be executed.
• CWLDB9038I
  Successfully renamed the node from 0 to 1;
• CWLDB9039I
  Successfully renamed the deployment environment definition from 0 to 1;
• CWLDB9040W
  Node 0 cannot be found in deployment environment definition 1;
• CWLDB9041I
  The CEI destination on server 0 and node 1 will be configured with Event Infrastructure emitter factory JNDI name 2.
• CWLDB9042I
  The CEI destination on cluster 0 will be configured with Event Infrastructure emitter factory JNDI name 1.
• CWLDB9043W
  The Common Event Infrastructure server deployment target is not valid. It is a single server 0 that has no node or more than one node defined.
• CWLDB9044W
  Deployment environment definition 0 cannot be created because WebSphere Business Monitor does not support multiple deployment environments in a single cell.
• CWLDB9045W
  The 0 node cannot be renamed because it cannot be found in the 1 topologyRole.
• CWLDB9046W
  The 0 node cannot be removed because it cannot be found in the 1 topologyRole.
• CWLDB9047W
  The 0 topologyRole cannot be found in the topology.
• CWLDB9048E
  The 0 deployment environment cannot be exported because the 1 directory already exists. The directory cannot be overwritten because the overwrite option is set to false.
• CWLDB9049E
  The node cannot be added to topology deployment environment, because more than one topology is in the cell.
• CWLDB9050W
  The 0 role is not synchronized with the 1 deployment target.
• CWLDB9051W
  Deployment environment 0 is successfully generated.
• CWLDB9052E
  Updating the port 0 of cluster member 1 failed. Reason: 2.
• CWLDB9100W
  The 0 component type cannot be configured for the 1 deployment environment.
• CWLDB9101E
  The 0 component type cannot be used more than once for the 1 deployment target for the 2 deployment environment.
• CWLDB9102E
  The component "0" has a dependency on component "1" that has not yet been configured for topology "2".
• CWLDB9103E
  The 0 component has not been configured for the 1 deployment environment.
• CWLDB9104E
  The 0 component configuration of the 1 type cannot be removed because it is used by the 2 component configuration in the 3 deployment environment.
• CWLDB9105E
  The 0 component configuration of the 1 type cannot be removed because it is configured in the 2 deployment environment.