[AIX Solaris HP-UX Linux Windows]

Migrating profiles using the migration wizard

Use the migration tools to migrate WebSphere® Application Server Version 6.x, 7.x, or 8.x profiles to Version 8.5.

Before you begin

Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Migration Toolkit.

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

Read WASPreUpgrade command and WASPostUpgrade command for descriptions of the parameters related to the information that you need to collect before you begin this procedure. The Migration wizard prompts you for this information during the migration.

Before using the Migration wizard, install WebSphere Application Server Version 8.5.

Use the Profile Management tool or the manageprofiles command to create a valid new target Version 8.5 profile if one does not already exist, or you can create a target profile using the Migration wizard.

The WebSphere Application Server - Express product creates a valid Version 8.5 profile for a standalone application server during installation.

Tip: Before migrating a WebSphere Application Server Version 6.x, 7.x, or 8.0 application server profile, use the backupConfig command or your own preferred backup utility to back up your existing configuration. Note the name and location of your backup configuration. You can also choose to let the Configuration Migration Tool run the backupConfig command. You can run the backupConfig command on the source profile and the intended target profile if the Configuration Migration Tool is not creating the profile. For more information, see backupConfig command.

About this task

The wizard is the graphical user interface to the primary Version 8.5 command-line migration tools, which are the WASPreUpgrade command and the WASPostUpgrade command. After gathering all of the information that is required for the migration, use the wizard to migrate a WebSphere Application Server Version 6.x, 7.x, or Version 8.0 profile to a Version 8.5 profile.

For help, read Troubleshooting migration.

Procedure

  1. Start the migration wizard.
    Perform one of the following options to access and start the Migration wizard:
    • [Windows]Go to Start > Programs > IBM WebSphere > Application Server V8.5 > Tools. Click Configuration Migration Tool.
    • Run one of the following commands:
      • [AIX HP-UX Solaris]app_server_root/bin/migration.sh
      • [Windows]app_server_root\bin\migration.bat
  2. Define a migration source.
    On the Migration Sources panel, click New.
  3. Select the installations that you want to migrate.
    View the list of valid installations which you can migrate to Version 8.5. You can select installations from this list, or you can specify an installation which has not been detected. Click Next.
  4. Create a backup of the valid source profiles managed by the installation you selected.
    This step is optional. If you wish to make a backup of the profile, select the profile check box and specify the location for the profile backup.
    1. Select a valid source profile from the drop down list.
    2. Optionally choose to run backupConfig on the selected source profile.
    3. Click Next.
    Note: You can use the restoreConfig script to apply this backup and restore the profile.
  5. Specify the location for the migration output.
    The migration output includes log files. You can also optionally enable tracing to the appropriate level and select the location for the trace file. The trace file destination can be a different location from the Migration output location. Click Next.
  6. Create the target profile or use an existing profile from the target installation.
    If you are using an existing profile, specify the name of the profile and click Next.
    Note: Only the names of those profiles which match the type of the source profile being migrated will be displayed in the list. If you are using an existing profile, optionally choose to run backupConfig on the target profile by selecting the checkbox and specifying the location for the profile backup.
  7. Provide the required information for the profile creation process.
    If you are creating a new profile, the information required depends on the profile type that you are migrating. Click Next.
    1. If migrating a federated node, verify the Deployment Manager is running and open for connections.
  8. Select a method to use for migrating the applications.
    If you are migrating applications, specify the application installation directory. Click Next.
  9. Specify whether to use the port values from the source or target profile.
    Click Next.
  10. Select additional migration options.
    Select the appropriate settings. To proceed to the summary page, click Next.
  11. Review and verify the migration data.
    Note: You can generate a text file of the commands. You can use this text file to create a script that uses the commands.
  12. Start the migration.
    Click Next to start the migration process. The migration process consists of 2-6 sub-processes, depending on the choices you made in previous steps. Each sub-process 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. You can review any of the sub-process tabs at any time during the migration. If the process requires user input, you are automatically moved to the appropriate tab.
  13. Review the results page.
    After all sub-processes have completed, the results page is displayed. To return to the list of Migration sources, click Finish.

What to do next

You can now start the migrated standalone application server in the WebSphere Application Server Version 8.5 environment or begin a new migration scenario.