Migrating profiles by using the migration wizard

Use the migration tools to migrate WebSphere® Application Server profiles to Version 9.0.

Before you begin

Supported configurations:

This topic is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit.

Review the following resources:

Install WebSphere Application Server Version 9.0. You must migrate your Version 7.0 or later profiles by using the Version 9.0 migration wizard.

If a valid Version 9.0 target profile does not exist, you can create one before you start the migration process by using the Profile Management tool or the manageprofiles command, or you can create one during migration by using the migration wizard.

Tip: Before you migrate a WebSphere 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 9.0 command-line migration tools, which are the WASPreUpgrade and WASPostUpgrade commands. After you gather all of the information that is required for the migration, use the wizard to migrate a WebSphere Application Server Version 7.0 or later profile to a Version 9.0 profile.

The migration wizard transfers applications and configuration information for the Version 7.0 or later server resources, security, variables, and virtual hosts to the Version 9.0 profile. All information is stored in XML files in the app_server_root/config/cells directory of each product.

Supported configurations: 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 Troubleshooting migration.


  1. If you have embedded Derby databases or messaging engine file stores that might be locked by any running servers, stop the servers that are defined by the WebSphere Application Server Version 7.0 or later profile that you want to migrate.

    The server must be stopped to unlock any in-use files that need to be migrated.

    The command that you use 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
  2. Start the Version 9.0 migration wizard.
    Perform one of the following options to access and start the migration wizard:
    • [Windows]Go to Start > Programs > IBM WebSphere > IBM WebSphere Application Server V9.0 > 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
  3. Define a migration source.
    On the Migration Sources tab, click New.
  4. Select the installations that you want to migrate, and click Next.

    Detected valid installations that you can migrate to Version 9.0 are listed. You can select installations from this list, or you can specify an installation was not detected.

  5. Select the source profile that you want to migrate.
    1. Select a valid source profile from the drop-down list.
    2. 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.
      Note: You can use the restoreConfig command to apply this backup and restore the profile.
    3. Click Next.
  6. 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. You 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.

  7. Create the target profile or use an existing profile from the target installation.
    • If you are creating a new profile, provide the required information for the profile creation process, and click Next.

      The required information depends on the profile type that you are migrating.

      If you are migrating a federated node, verify that the deployment manager is running and open for connections.

    • If you are using an existing profile, specify the name of the profile and click Next.
      Note: Only the names of those profiles that match the type of the source profile that you are migrating are displayed in the list. If you 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.
  8. Select whether to migrate your applications, and click Next.
    If you are migrating applications, you can specify a different application installation directory.
  9. Select how to migrate port values, and click Next.
  10. Select additional migration options, and click Next.
  11. Review and verify the migration summary data.
    Note: To generate a text file of the commands to be used for this migration, click Generate Commands. You can use this text file to create a script that uses the commands.
  12. To start the migration, click Migrate.

    The migration process consists of 2-6 subprocesses, depending on the choices you 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. You can review any of the subprocess tabs at any time during the migration. If the process requires user input, you are automatically moved to the appropriate tab.

    You can start any stopped servers in your source installation after the WASPreUpgradesubprocess completes.

  13. After all subprocesses complete, review the results page.
  14. To return to the list of migration sources, click Finish.

What to do next

You can now start the migrated stand-alone application server in the WebSphere Application Server Version 9.0 environment or begin a new migration scenario.