- CWMCO0001I: The WBIPreUpgrade command accepts the following parameters:
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0002I: The WBIPostUpgrade command accepts the following parameters:
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0003I: A scheduler of type "{0}" has been found.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0004E: No scheduler was found for the application.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0005E: The enterprise archive (EAR) file "{0}" cannot be generated. The error is "{1}".
- Explanation: The EAR file cannot be updated because of an error. The file must be updated because it contains obsolete configurations.
- User Action: Resolve the problems in the error and try to install the EAR file again.
- CWMCO0006I: The migration process updated the EAR file: {0}
- Explanation: To ensure binary installability, migration to WebSphere Process Server requires some migration actions to be performed."
- User Action: No user action required.
- CWMCO0101I: The logger did not initialize the {0} log file and received the following exception: {1}.
- Explanation: The log file cannot be generated.
- User Action: If a log file is required for the migration process, resolve the specified error and try the migration again. 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.
- CWMCO0200I: Information is being logged to the {0} file.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0201E: No target profile exists.
- Explanation: A target profile must exist before migration can begin. In addition, the target profile type and the augmentation level must match those of the source profile.
- User Action: Create a profile in the new installation that matches the type of the profile in the existing installation, and try the migration again.
- CWMCO0202E: A profile name was not specified, and no default profile could be found. No profile registry found at: {0}
- Explanation: Because a profile name was not declared, the migration tried to find a default profile, but none was found. Either the path to the earlier product is incorrect or the profile registry does not exist.
- User Action: Ensure that the path to the prevoius product is correct and the profile registry exists.
- CWMCO0203E: The migration utility was invoked with arguments that are not valid. See the valid arguments below.
- Explanation: The migration cannot continue until valid arguments are specified.
- User Action: Run the migration utility again with the correct arguments.
- CWMCO0204E: The {0} migration backup directory is not valid. It must be the same directory that is supplied in the WBIPreUpgrade command.
- Explanation: The migration backup directory must be the same for the WBIPreUpgrade and WBIPostUpgrade commands.
- User Action: Specify the correct the migration backup directory, and run the migration again.
- CWMCO0205E: The {0} target profile does not exist. Migration cannot continue.
- Explanation: The specified profile is not in the target installation.
- User Action: Create the profile in the target installation, and then run the migration utility specifying this profile name.
- CWMCO0206E: The command-line options cannot be saved to a temporary file. The error is {0}
- Explanation: The command-line options must be saved to a temporary file because they are required by some parts of the migration that are executed by the WebSphere Application Server migration.
- User Action: Resolve the problems listed in the specified error and run the migration again. 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.
- CWMCO0208I: See the following log file for information: {0}
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0209I: The {0} WebSphere Application Server utility has been invoked.
- Explanation: This is an informational message. The WebSphere Process Server migration invokes the WebSphere Application Server migration utility as part of the process.
- User Action: No action is required.
- CWMCO0210I: The first step of the WebSphere Process Server migration is complete.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0211E: The WebSphere Application Server migration portion of the WebSphere Process Server migration did not complete, so the migration process stopped. The error is {0}
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0212E: The WebSphere Application Server migration portion of the WebSphere Process Server migration did not complete, so the migration process stopped. The error is {0}
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0213E: The WebSphere Application Server migration portion of the WebSphere Process Server migration did not complete, so the migration process stopped. The message ID MIGR0272E or MIGR0286E was detected.
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0214E: The backup directory cannot be created.
- Explanation: A backup directory is required as part of the migration process.
- User Action: Specify a backup directory that has the proper permissions, and run the WebSphere Process Server migration again.
- CWMCO0215E: An unexpected error occurred during migration. See the log for details.
- Explanation: None.
- User Action: Use the log to determine the cause of the error. Resolve the error and try the WebSphere Process Server migration again. 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.
- CWMCO0216E: The {0} source profile directory does not exist. Use the correct backup directory and source profile name.
- Explanation: The migration cannot continue because the directory of the source profile cannot be found.
- User Action: Confirm the correct backup directory and source profile name and try the migration again.
- CWMCO0217E: The WebSphere Business Integration migration process failed.
- Explanation: The problem can be caused by a failure in the prerequisites check or by a failure in the WebSphere Application Server migration portion of the process.
- User Action: Refer to the error messages in the console and in the logs to determine the cause of the failure. Correct the problems and begin the migration process again. 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.
- CWMCO0218E: The argument includeApps argument is not supported.
- Explanation: This product uses applications to enhance server functionality. Therefore, excluding applications from migration results in a nonfunctional server.
- User Action: Do not use the includeApps argument in the migration commands.
- CWMCO0219I: A target profile is not specified, so the {0} default target profile will be used.
- Explanation: Because the -profileName argument was not specified, the default profile in the new installation will be used as the target profile.
- User Action: If the default profile should not be used as the target profile of the migration, specify the correct profile with the -profileName argument.
- CWMCO0220I: A source profile is not specified, so the {0} default source profile will be used.
- Explanation: Because the -oldProfile argument was not specified, the default profile in the migration backup directory will be used as the source profile.
- User Action: If the default profile should not be used as the source profile of the migration, specify the correct profile with the -oldProfile argument.
- CWMCO0221E: A source profile name is not specified, so the migration cannot continue.
- Explanation: For migration of WebSphere Business Integration 6.1.x to 6.2, you must specify the -profileName argument.
- User Action: Restart the migration process and specify the source profile name using the -profileName argument.
- CWMCO0222E: The source profile directory that was specified is not valid, so the migration cannot continue.
- Explanation: You must pass the fully qualified path to the source profile as the first argument.
- User Action: Specify the correct fully qualified path to the source profile, and restart the migration process.
- CWMCO0223E: The profile version cannot be determined, so the migration cannot continue.
- Explanation: The source profile version must be determined for the migration to proceed.
- User Action: Verify that the wbi.product file, which is located in the WebSphere home directory, exists, and restart the migration process.
- CWMCO0224I: The WebSphere Application Server utility has completed.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0231E: The argument {0} is not supported on this platform.
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Do not use the unsupported argument in the migration commands.
- CWMCO0232E: The {0} migration backup directory is not valid. On i5/OS, you must specify the fully qualified backup directory including the profile that is to be migrated. For example: backup_root/profiles/ProcSrv01.
- Explanation: The migration backup directory must be the backup directory of the profile that is to be migrated.
- User Action: Specify the correct the migration backup directory, and run the migration again.
- CWMCO0233E: The migration utility enrountered an error while invoking enablejvm command: {0}.
- Explanation: An error occurred during the execution of the enablejvm utility. WebSphere Process Server migration cannot continue.
- User Action: Specify the correct the migration backup directory, and run the migration again.
- CWMCO0301I: The {0} object of the {1} type is already installed, so it Will not be migrated.
- Explanation: This is an informational message.
- User Action: No user action is required.
- CWMCO0302E: The {0} configuration file cannot be read.
- Explanation: The problem might be caused by a corrupted configuration or invalid file system permissions.
- User Action: Verify that the specified file can be read and that the configuration is valid.
- CWMCO0303I: The wsadmin tool is deploying the {0} application.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0304W: The {0} application cannot be deployed. Check the log for details.
- Explanation: The application has an error and cannot be deployed.
- User Action: Check the log for details. Either resolve the error and restart the migration, or install the application manually.
- CWMCO0305W: The migration of one or more applications terminated unexpectedly.
- Explanation: One or more of the applications to be migrated did not install correctly to the target installation.
- User Action: Refer to the log files for the specific failure. Resolve the error and restart the migration, or install the application manually.
- CWMCO0401I: The WebSphere Process Server {0} application will not be migrated.
- Explanation: The application is a sample or other nonfunctional application that is specific to the old product installation.
- User Action: If this application is necessary, manually install the version of it that can be found in the new product installation.
- CWMCO0402I: The WebSphere Process Server {0} application will be updated during migration.
- Explanation: This is an informational message. The application is identified as a functional application that is specific to the old product installation and must be updated.
- User Action: No user action is required.
- CWMCO0501E: The profile registry information for the {0} profile in the {1} directory cannot be found.
- Explanation: Migration cannot continue because the information about the specified profile cannot be found. Likely causes are that the incorrect backup directory or profile name was used.
- User Action: Confirm that the correct backup directory and profile names were used, and correct them if they are incorrect, then restart the migration. 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.
- CWMCO0502E: The {0} and {1} profile types do not match.
- Explanation: The profile types must match, or the migration cannot continue.
- User Action: Correct the source or target profile so that the types match (stand-alone, deployment manager, or managed node), and restart the migration.
- CWMCO0503E: The {0} and {1} cell names do not match.
- Explanation: The cell names must match, or the migration cannot continue.
- User Action: Re-create the target profile using the same cell name as that of the source profile.
- CWMCO0504E: This upgrade scenario is not supported. The profile augmentation levels must match. The source and target profile did not match with respect to the {0} augmentation level.
- Explanation: To migrate an existing profile to a new profile, the augmentation levels of the profiles must match.
- User Action: Select source and target profiles that have the same augmentation levels and restart the migration. If the problem persists, create the target profile manually so that its augmentation level matches that of the source profile.
- CWMCO0505E: The {0} and {1} node names do not match.
- Explanation: For the migration to continue, the node names must match.
- User Action: Re-create the target profile using the same node name as that of the source profile.
- CWMCO0506E: The migration stopped. The version of the current WebSphere Application Server Network Deployment installation is not supported for this migration. The installed version is {0}.
- Explanation: To perform the migration, the version of the current WebSphere Application Server Network Deployment installation must be 6.0.2 with fix pack 3 or later.
- User Action: Upgrade the system to at least version 6.0.2.3 of WebSphere Application Server Network Deployment, then try the migration again. For information on upgrading, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp.
- CWMCO0507E: The migration stopped. The version of the current WebSphere Process Server installation is not supported for this migration. The installed version is {0}.
- Explanation: To perform the migration, the version of the current WebSphere Process Server installation must be any release of 6.0.1 or 6.0.2.
- User Action: Upgrade the system to any release of 6.0.1 or 6.0.2 of WebSphere Process Server, then try the migration again. For information on upgrading, refer to http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp.
- CWMCO0508E: The profile names {0} and {1} do not match.
- Explanation: For the migration to continue, the profile names must match.
- User Action: Correct the source or target profile so that the names match, and restart the migration.
- CWMCO0601E: An unexpected error occurred while trying to load the {0} XML Metadata Interchange (XMI) file.
- Explanation: The migration uses the XMI file to determine if an update to the enterprise archive (EAR) file is needed.
- User Action: Ensure that the specified XMI file can be opened and restart the migration.
- CWMCO0602I: The WBIProfileUpgrade.ant script is upgrading the applications and the configuration for the {0} profile.
- Explanation: This is an informational message. The enterprise applications and configuration data that are part of the product must be upgraded for them to function in the new release.
- User Action: No action is required.
- CWMCO0700E: The {0} profile path already exists, so the profile cannot be created.
- Explanation: The specified profile path for a new profile must not already exist.
- User Action: Specify another path for the new profile.
- CWMCO0800W: The {0} file must be manually copied to the {1} target directory.
- Explanation: The specified file must be copied to the new installation, but the migration process cannot write to the directory.
- User Action: A user with the appropriate permissions must unlock the target directory and manually copy the specified file.
- CWMCO0801E: An error occurred while detecting the security settings of the previous installation.
- Explanation: An attempt to detect the security settings of the source profile from the backup directory failed.
- User Action: Ensure the backup directory exists and is valid. Refer to the log files for more information.
- CWMCO0802E: An administrator user name and password are required.
- Explanation: The administrator user name and password are required to migrate a profile that has administrative security enabled.
- User Action: Enter the administrator user name and password using the username and password parameters.
- CWMCO0803E: The {0} retain file cannot be updated during the restore process.
- Explanation: The migration cannot continue because the specified file contains a list of required files for migration.
- User Action: Ensure that the file exists at the indicated path and that it can be accessed by the migration run time.
- CWMCO0804E: The updated {0} retain file cannot be saved during the restore process.
- Explanation: The migration cannot continue because the specified file contains a list of required files for migration.
- User Action: Ensure that the destination folder can be accessed for saving the specified file.
- CWMCO0805E: An incorrect command was used. The {0} command is not supported.
- Explanation: The migration utility was invoked with arguments that are not valid. The migration cannot continue.
- User Action: Refer to the proper usage message, and restart the migration with the correct arguments.
- CWMCO0806E: The logs subfolder of the backup directory cannot be created.
- Explanation: A backup directory with a logs subfolder is required as part of the migration process. That directory does not have the proper permissions.
- User Action: Specify a backup directory that has the proper permissions, and restart the WebSphere Process Server migration.
- CWMCO0807E: The WebSphere Application Server home property (WAS Home) cannot be determined from the wbiserver.properties file.
- Explanation: The wbiserver.properties file is either missing or corrupted.
- User Action: Ensure that the wbiserver.properties file exists and is valid.
- CWMCO0808E: The {0} file cannot be found.
- Explanation: The specified file cannot be found.
- User Action: Ensure that the specified file exists.
- CWMCO0809E: The {0} temporary properties file cannot be found.
- Explanation: The temporary properties file was not properly created.
- User Action: If the folder that contains the specified file does not have the proper permissions, change the permissions and restart the WebSphere Process Server migration.
- CWMCO0810E: The {0} temporary properties file cannot be written to.
- Explanation: The temporary properties file does not have the correct permissions.
- User Action: Change the permissions on the specified file, and restart the WebSphere Process Server migration.
- CWMCO0811E: The {0} file cannot be serialized.
- Explanation: The specified file cannot be serialized.
- User Action: If the folder that contains the specified file does not have the proper permissions, change the permissions and restart the WebSphere Process Server migration.
- CWMCO0812E: The {0} file cannot be restored.
- Explanation: The file cannot serialized.
- User Action: If the folder that contains the specified file does not have the proper permissions, change the permissions and restart the WebSphere Process Server migration.
- CWMCO0813E: The {0} destination file cannot be opened for copying.
- Explanation: The specified file is either missing or corrupted.
- User Action: If the folder that contains the specified file does not have the proper permissions, change the permissions and restart the WebSphere Process Server migration.
- CWMCO0814E: An incorrect command was used. The {0} command is not supported.
- Explanation: The migration utility was invoked with arguments that are not valid. The migration cannot continue.
- User Action: Refer to the proper usage message, and restart the migration with the correct arguments.
- CWMCO0815E: The {0} file cannot be found.
- Explanation: The specified file is required for the migration process to continue. It is generated during the creation of the backup directory.
- User Action: Verify the successful creation of the backup directory, and restart the migration steps for this profile.
- CWMCO0816E: The {0} file cannot be found.
- Explanation: This file is required for the migration process to continue.
- User Action: Verify that the specified file exists and that it has the proper permissions.
- CWMCO0817E: The profile directory for the specified profile cannot be found.
- Explanation: The profile directory is required to continue the migration process. The profile that is specified might be incorrect, or the file system might not have the proper permissions.
- User Action: Specify the correct profile if it is incorrect, or change permissions of the file system.
- CWMCO0818E: The {0} required file cannot be found.
- Explanation: The specified file is required to continue the migration process.
- User Action: Locate the specified file and make sure the file system has the proper permissions.
- CWMCO0819I: The -traceFile parameter with the {0} value is not supported when migrating from WebSphere Process Server 6.1. The trace file will be {1}.
- Explanation: This is an informational message. The -traceFile parameter is ignored when migrating from WebSphere Process Server 6.1.x. The trace statements will be placed in the file that is specified in the message.
- User Action: No user action is required.
- CWMCO0820I: The ws_ant command is being invoked with the {0} command.
- Explanation: The ws_ant command is being invoked with the command that is specified in the message.
- User Action: No user action required.
- CWMCO0821E: A failure occurred while invoking a ws_ant command.
- Explanation: The migration process failed to invoke a ws_ant command.
- User Action: Examine the log files for information about the cause of the failure. Correct the problem and rerun the migration command.
- CWMCO0822I: The WBIPostUpgrade command finished successfully.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0823I: The WBIPreUpgrade command finished successfully.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWMCO0824W: The WBIPostUpgrade command has finished with one or more warnings.
- Explanation: The WBIPostUpgrade command has finished but encountered one or more warnings.
- User Action: See previous messages for specific warning messages.
- CWMCO0825W: The WBIPreUpgrade command has finished with one or more warnings.
- Explanation: The WBIPreUpgrade command has finished but encountered one or more warnings.
- User Action: See previous messages for specific warning messages.
- CWMCO0826E: The WBIPostUpgrade command has finished with one or more errors.
- Explanation: The WBIPostUpgrade command could not complete because it has encountered one or more errors.
- User Action: See previous messages for specific error messages.
- CWMCO0827E: The WBIPreUpgrade command has finished with one or more errors.
- Explanation: The WBIPreUpgrade command could not complete because it has encountered one or more errors.
- User Action: See previous messages for specific error messages.
- CWMCO0828E: Could not determine the node name.
- Explanation: The migration process failed to determine the node name.
- User Action: Examine the node direcotries and make sure the nodes are not missing.
- CWMCO0829E: An error occured during script execution. The message WASX7022E was detected.
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0830E: Profile creation completed with either INSTCONFPARTIALSUCCESS or INSTCONFFAILED code.
- Explanation: An error occurred during the execution of the WebSphere Application Server migration utility. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0832E: An error occured during execution of restoreConfig. The message ADMU5503E was detected.
- Explanation: An error occurred during the execution of restoreConfig. WebSphere Process Server migration cannot continue.
- User Action: Resolve the error and run the WebSphere Process Server migration utility again. 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.
- CWMCO0834I: The enablejvm command is being invoked with the {0} command.
- Explanation: The enablejvm command is being invoked with the command that is specified in the message.
- User Action: No user action required.