- CWMCO0001I: The WebSphere Process Server migration is attempting to migrate the archive: {0}.
- CWMCO0002I: No WebSphere Process Server migration is needed for the EAR file {0}.
- CWMCO0003I: The following archive has BPEL content: {0}.
- CWMCO0004I: The archive {0} is being validated.
- CWMCO0005I: The following archive has WebSphere Process Server content that needs to be migrated: {0}.
- CWMCO0006E: A WebSphere Business Integration Server Foundation 5.1-level configuration format was detected in this file: {0} from archive: {1}. Message is: {2}
- CWMCO0007I: The WebSphere Process Server migration is attempting to update archive {0}.
- CWMCO0008I: The WebSphere Process Server migration is attempting to create file {0} in archive {1}.
- CWMCO0009I: There are no configuration elements within the archive {1} that should be migrated to {0}.
- CWMCO0010I: The WebSphere Process Server migration is attempting to update file {0} in archive {1}.
- CWMCO0011I: The WebSphere Process Server migration is attempting to update configuration file {0}.
- CWMCO0012I: The WebSphere Process Server migration is attempting to create configuration file {0}.
- CWMCO0013E: An error occurred when the source artifact was opened: {0}; Message is: {1}.
- CWMCO0014E: The existing WebSphere instance is not WebSphere Business Integration Server Foundation 5.1.x.
- CWMCO0015E: No profiles exist on the target.
- CWMCO0016E: Error: A default profile to migrate to could not be found, and no profile was specified.
- CWMCO0017E: Incorrect command usage: The backup directory must be specified.
- CWMCO0018I: The WebSphere Process Server migration is ready to invoke the base WebSphere migration utility: {0} \nIgnore the following messages that the base migration might give: \n\tThe <WebSphere Business Integration Server Foundation feature> is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed\n\tBPED0267E: A syntactical error was found in BPEL file\n\tADMA5014E: The installation of application <The WebSphere Business Integration Server Foundation application containing .bpel files> failed.
- CWMCO0019I: The base WebSphere migration is complete. The WebSphere Process Server migration will now continue.
- CWMCO0020E: The base WebSphere migration 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}.
- CWMCO0021I: The WBICorePostUpgrade migration utility is starting. Refer to the WBICorePostUpgrade.<date and time>.log file in the backup directory for more details.
- CWMCO0022I: The WBICorePostUpgrade migration utility completed successfully.
- CWMCO0023I: The WBICorePostUpgrade migration utility did not complete successfully due to the following error; resolve the error, restore the previous WebSphere environment, and try the WBICore migration again: {0}.
- CWMCO0024I: The CMMEJBJarExtension has been removed from the migrated ibm-ejb-jar-ext-wbi.xmi file within the application because it was generated incorrectly and contained no real content.
- CWMCO0025I: The WebSphere Process Server migration is attempting to extract the WebSphere Process Server configuration elements of {0} to {1}.
- CWMCO0026I: The WebSphere Process Server migration is saving WebSphere Process Server content to file {0}.
- CWMCO0027I: No WebSphere Process Server content was found in the configuration files {0} {1} {2}.
- CWMCO0028E: The WebSphere Process Server migration source folder name is invalid: {0}.
- CWMCO0029E: The WebSphere Process Server migration destination folder name is invalid: {0}.
- CWMCO0030E: The WebSphere Process Server migration destination folder could not be created: {0}.
- CWMCO0031E: The specified migration destination folder must not be a file: {0}.
- CWMCO0032E: Configuration file {0} could not be migrated.
- CWMCO0033W: The configuration file {0} could not be parsed because the top-level element was not {1}:{2}.
- CWMCO0034W: The configuration element {0} will not be migrated, as it is no longer supported.
- CWMCO0035W: Warning: The WebSphere Process Server migration is adding an xmi prefix to the ''{0}'' attribute for element {1} whose ''{0}'' attribute value is {2}.
- CWMCO0036E: The cell name must be specified.
- CWMCO0037E: The cell name, {0}, is invalid on the source configuration.
- CWMCO0038E: The cell name, {0}, is invalid on the target configuration.
- CWMCO0039E: The node name must be specified.
- CWMCO0040E: The node name, {0}, is invalid on the source configuration.
- CWMCO0041E: The node name, {0}, is invalid on the target configuration.
- CWMCO0042E: The server name, {0}, is invalid on the target configuration.
- CWMCO0043I: The WebSphere Process Server migration is migrating from 5.1.x node name {0} to 6.0 node name {1}.
- CWMCO0044I: The source node for this migration is {0} and the target node is {1}.
- CWMCO0045I: The WebSphere Process Server migration is migrating from 5.1.x cell name {0} to 6.0 cell name {1}.
- CWMCO0046I: The WebSphere Process Server migration is migrating from 5.1.x server name {0} to 6.0 server name {1}.
- CWMCO0047W: Warning: The WebSphere Process Server migration is migrating from source cell name {0} to the target cell name {1}.
- CWMCO0048W: Warning: The WebSphere Process Server migration is migrating from source node name {0} to the target node name: {1}.
- CWMCO0049I: The WebSphere Process Server migration has detected a federated node.
- CWMCO0050I: The WebSphere Process Server migration has detected a deployment manager node.
- CWMCO0051I: The WebSphere Process Server migration has detected a stand-alone node.
- CWMCO0052I: During the migration of this federated node, its 5.1 cell name, ''{0}'', will override its 6.0 cell name, ''{1}''.
- CWMCO0053E: Error: there are no sub-directories of {0}.
- CWMCO0054I: Migration has detected a federated node.
- CWMCO0055I: Migration has detected a deployment manager node.
- CWMCO0056I: The CEI migration completed successfully.
- CWMCO0056W: There is no 'event' folder in the backup directory, so no CEI migration will be performed.
- CWMCO0057E: The CEI migration failed because the target profile was not augmented with CEI information. Check the logs for more details.
- CWMCO0058E: The CEI migration failed. Check the logs for more details.
- CWMCO0059W: The CEI migration returned an unrecognized code. Check the logs for more details.
- CWMCO0060W: The CEI_HOME directory could not be located. There was an error trying to obtain that information from this file: {0}.
- CWMCO0061I: CEI will not be migrated because it is not at version 5.1.1 or higher.
- CWMCO0062I: CEI will not be migrated because there was an error saving the response file used to communicate with the CEI migration utility: {0}.
- CWMCO0063I: The log file: {0} was successfully initiated.
- CWMCO0064I: Logger failed to initialize log file {0} and received the following exception: {1}.
- CWMCO0065W: The security file could not be found, so global security settings could not be detected: {0}.
- CWMCO0066I: The WBICorePreUpgrade migration utility is starting. See the WBICorePreUpgrade.<date and time>.log file under the target profile's 'logs' folder for more details.
- CWMCO0067I: Incorrect command usage: The backup directory and current WebSphere directory must be specified.
- CWMCO0068I: See the log file for more details: {0}.
- CWMCO0069I: See the log file for more details: {0}.
- CWMCO0070I: See the log file for more details: {0}.
- CWMCO0071I: The Common Event Infrastructure configuration was not backed up because the following directory does not exist: {0}.
- CWMCO0072I: Backing up the Common Event Infrastructure configuration from the directory {0} to {1}.
- CWMCO0073I: The trace file {0} was successfully initialized.
- CWMCO0074W: Error Reading output of {0}: the exception was {1}
- CWMCO0075I: See the log file for more details: {0}.
- CWMCO0076E: The backup directory could not be created. Ensure that it is a valid directory with the proper permissions.
- CWMCO0077W: The source file was unable to be copied, because it does not exist: {0}.
- CWMCO0078W: Source directory {0} could not be copied.
- CWMCO0079W: Target file {0} could not be copied.
- CWMCO0080W: Directory or file ''{0}'' could not be created.
- CWMCO0081W: Directory ''{0}'' could not be created.
- CWMCO0082W: An error occurred while reading backup options from file ''{0}''. The error is: {1}.
- CWMCO0083W: An unexpected internal error occurred {0}.
- CWMCO0084W: XML file {0} could not be read. The error is {0}.
- CWMCO0085E: The base WebSphere migration 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: Return code was {0}.
- CWMCO0086E: The base WebSphere migration 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: The base migration message ID MIGR0307I or MIGR0286E was detected.
- CWMCO0087E: The backup configuration directory does not exist: ''{0}''. Retry the migration with a valid backup directory.
- CWMCO0088E: The target configuration directory does not exist: ''{0}''. Retry the migration with a valid profile.
- CWMCO0089E: No default profile exists and no profile was specified: Try the WebSphere Process Server Migration again with the '-profileName' parameter to explicitly specify the target profile.
- CWMCO0090E: No profile named ''{0}'' exists: Try the WebSphere Process Server Migration again with a valid profile name.
- CWMCO0091I: Scheduler of type {0} has been found.
- CWMCO0092E: No scheduler was found for the application.
- CWMCO0093E: The EAR file {0} could not be generated due to the following error: {1}.