- CWMBP0001I: The BPCPostUpgrade migration utility is starting. See the BPCPostUpgrade.<date and time>.log file under the target profile's 'logs' folder for more details.
- CWMBP0002I: The BPCPostUpgrade migration utility has completed successfully.
- CWMBP0003I: The BPCPostUpgrade migration utility did not complete successfully due to the following error; resolve the error, restore the previous WebSphere environment, and try the WebSphere Process Server migration again: {0}.
- CWMBP0004W: An installed .FAR module in archive {0} has been detected. This application will be skipped; migration is continuing.
- CWMBP0005E: The WebSphere Process Server migration failed. An installed .FAR module in archive {0} has been detected, and the -warnFARFiles option was not specified.
- CWMBP0006E: When run, the Business Process Choreographer upgrade script encountered an error: {0}.
- CWMBP0007W: Migration is continuing; run the following command manually after the problem has been fixed: {0}.
- CWMBP0008I: The business process container or business process Web client will now be migrated on the following node: {0}.
- CWMBP0009I: The business process container or business process Web Client will now be migrated on the following cluster: {0}.
- CWMBP0010I: The business process container will now be migrated on a stand-alone server on node {0}.
- CWMBP0011I: The following application will not be migrated, because it is a sample application: {0}.
- CWMBP0012I: Migrating application {0}.
- CWMBP0013I: Attempting to execute the wsadmin call: {0}.
- CWMBP0014I: The wsadmin call {0} has been successfully executed.
- CWMBP0015I: The federated node {0} base application server version is being restored to 5 in its node-metadata.properties.
- CWMBP0016I: The federated node {0} base application server version is being updated to 6 in its node-metadata.properties so that the BPEWebClient can be upgraded to the J2EE 1.4 level during migration.
- CWMBP0017I: The base application server version for node {0} has been modified.
- CWMBP0018I: The application {0} was not installed; the -includeApps attribute was set to false.
- CWMBP0019I: Migration has detected a federated node.
- CWMBP0020I: Migration has detected a deployment manager node.
- CWMBP0021I: Migration has detected a stand-alone node.
- CWMBP0023I: The EAR file has been regenerated to location {0}.
- CWMBP0024I: The target EAR file to install is {0}.
- CWMBP0025I: The deployment file is being migrated from folder {0} to folder {1}.
- CWMBP0026I: The BPCPreUpgrade migration utility completed successfully.
- CWMBP0027I: The BPCPreUpgrade migration utility did not complete successfully due to the following error; resolve the error, restore the previous WebSphere environment, and try the WebSphere Process Server migration again: {0}.
- CWMBP0028I: The BPCPreUpgrade migration utility is starting. See the BPCPreUpgrade.<date and time>.log file in the backup directory for more details.
- CWMBP0029I: See the log file for more details: {0}.
- CWMBP0030I: See the log file for more details: {0}.
- CWMBP0031E: An unexpected error has occurred: {0}.
- CWMBP0032W: Configuration file {0} cannot be read.
- CWMBP0033I: The normalized EAR file name is {0}.
- CWMBP0034W: Object {0} of type {1} cannot be located.
- CWMBP0035I: The metadata has been updated in EAR file {0}.
- CWMBP0036I: The EAR file has been saved to {0}.
- CWMBP0037I: The attribute useMetaDataFromBinaries is set to {0}.
- CWMBP0038I: The new application file name is ''{0}''.
- CWMBP0039W: The application has already been deployed on the migration target: {0}.
- CWMBP0040W: The application ''{0}'' cannot be deployed.
- CWMBP0041I: See the log file for more details: {0}.
- CWMBP0041W: The application ''{0}'' cannot be migrated.
- CWMBP0042I: Attempting to migrate WebSphere Process Server application. The command is: ''{0}''.
- CWMBP0043I: The migration .jacl script has been created: {0}\n\t{1}\n\t{2}\n\t{3}