Migrate profiles using the migration wizard
Use the migration tools, such as the Configuration Migration Tool, to migrate WebSphere Application Server profiles to v9.0.
The tool allows you to clone the source profile.
Review the following resources:
- Read Overview of migration, coexistence, and interoperability and Migration considerations for general migration information.
- For resources to help us plan and perform our migration, visit Knowledge Collection: Migration planning for WAS.
- Read WASPreUpgrade command and WASPostUpgrade command for descriptions of the parameters related to the information needed to collect before you begin this procedure. The Migration wizard prompts you for this information during the migration.
Install WAS v9.0. We must migrate our v7.0 or later profiles using the v9.0 migration wizard.
If a valid v9.0 target profile does not exist, we can create one before starting the migration process using the Profile Management tool or the manageprofiles command, or we can create one during migration using the migration wizard.
Tip: Before migrating a WAS profile, use the backupConfig command or our own preferred backup utility to back up our existing configuration. Note the name and location of our backup configuration. We can also choose to let the Configuration Migration Tool run the backupConfig command. We can run the backupConfig command on the source profile and the intended target profile if the Configuration Migration Tool is not creating the profile. See backupConfig command.
The wizard is the graphical user interface to the primary v9.0 command-line migration tools, which are the WASPreUpgrade and WASPostUpgrade commands. After you gather all of the information required for the migration, use the wizard to migrate a WAS v7.0 or later profile to a v9.0 profile.
The migration wizard transfers applications and configuration information for the v7.0 or later server resources, security, variables, and virtual hosts to the v9.0 profile. All information is stored in XML files in the app_server_root/config/cells directory of each product.
This tool is supported only on AIX, Linux, and Windows. On other platforms, use a combination of the WASPreUpgrade, manageprofiles, and WASPostUpgrade commands.
For help, read Troubleshoot migration.
Tasks
- If we have embedded Derby databases or messaging engine file stores that might be locked by any running servers, stop the servers defined by the WAS v7.0 or later profile to migrate.
The server must be stopped to unlock any in-use files to be migrated.
The command used to stop the servers depends on the server type:
- Application server, administrative agent, and job manager: stopServer command
- Node agent: stopNode command
- Deployment manager: stopManager command
(Linux) For example, issue the following commands to stop server1 and server2:
./stopServer.sh server1
./stopServer.sh server2- Start the v9.0 migration wizard. Perform one of the following options to access and start the migration wizard:
- (Windows) Go to...
Start > Programs > IBM WebSphere > IBM WAS V9.0 > Tools > Configuration Migration Tool
- Run one of the following commands:
- (UNIX) app_server_root/bin/migration.sh
- (Windows) app_server_root\bin\migration.bat
- Define a migration source. On the Migration Sources tab, click New.
- Select the installations to migrate, and click Next.
Detected valid installations that we can migrate to v9.0 are listed. We can select installations from this list, or we can specify an installation was not detected.
- Select the source profile to migrate.
- Select a valid source profile from the drop-down list.
- To make a backup of the profile, select the profile check box and specify the location for the profile backup. Selecting this option runs the backupConfig command on the selected source profile.
Use the restoreConfig command to apply this backup and restore the profile.
- Click Next.
- Specify the location for the migration output and trace options, and click Next. The migration output includes log files and files saved from the source profiles.
By default, the tracing level is set to Fine. We can change this selection or specify a different location for the trace file. The trace file destination can be a different location from the migration output location.
- Create the target profile or use an existing profile from the target installation.
- For a new profile, provide the required information for the profile creation process, and click Next.
The required information depends on the profile type that we are migrating.
If we are migrating a federated node, verify that the deployment manager is running and open for connections.
- If we are using an existing profile, specify the name of the profile and click Next.
Only the names of those profiles that match the type of the source profile that we are migrating are displayed in the list. If we are using an existing profile, optionally choose to run backupConfig on the target profile by selecting the check box and specifying the location for the profile backup.
- Select whether to migrate the applications, and click Next. If we are migrating applications, we can specify a different application installation directory.
- Select how to migrate port values, and click Next.
- Select additional migration options, and click Next.
- Review and verify the migration summary data.
To generate a text file of the commands to be used for this migration, click Generate Commands. Use this text file to create a script that uses the commands.
- To start the migration, click Migrate.
The migration process consists of 2-6 subprocesses, depending on the choices we made in previous steps. Each subprocess has a tab where its progress can be monitored. Controls are in place to allow the process to flow continuously upon each success, or the user can control when to stop or continue the migration process as a whole. The Stop button brings up a confirmation dialog box. We can review any of the subprocess tabs at any time during the migration. If the process requires user input, we are automatically moved to the appropriate tab.
We can start any stopped servers in your source installation after the WASPreUpgradesubprocess completes.
- After all subprocesses complete, review the results page.
- To return to the list of migration sources, click Finish.
What to do next
We can now start the migrated stand-alone application server in the WAS v9.0 environment or begin a new migration scenario.
Related:
Overview of migration, coexistence, and interoperability Migration considerations Troubleshoot migration WASPreUpgrade command WASPostUpgrade command manageprofiles command backupConfig command restoreConfig command Migration Toolkit on WASdev