Migrate a V5 Application Server to a V6 Stand-alone Application Server with the Migration wizard

V6 migration always works by migrating an earlier supported version of WAS to an Application Server profile.

 

Before you begin

Collect the following information about your V5 installation before you begin this procedure. The Migration wizard prompts you for the information during the migration:

  • Installation root directory

    See WASPreUpgrade command for a description of the currentWebSphereDirectory parameter.

  • Use port values assigned to previous installation?

    Specifying “true” causes any ports of matching VirtualHosts to first be removed from the new configuration before adding the new values.

    Specifying “false” for this parameter will just add new port values.

    See WASPostUpgrade command for a description of the replacePorts parameter.

  • Backup directory name

    See WASPreUpgrade command for a description of the backupDirectory parameter.

  • Target profile name.

    See WASPostUpgrade command for a description of the profileName parameter.

Before using the Migration wizard, you should have installed V6 already. Use the Profile creation wizard to create a valid new Application Server profile if one does not already exist. After verifying that a valid V6 target exists, one can start the procedure.

The Network Deployment product does not create a profile during installation because there are three profile types. The Installation wizard prompts you to create a profile, but that action is optional during installation. Create a stand-alone Application Server profile if you have not already created one.

 

Overview

This topic describes using the Migration wizard to migrate a Version 5.x Application Server to a V6 stand-alone Application Server.

The Migration wizard is new as of V6. The wizard is the graphical interface to the V6 migration tools, which are the WASPreUpgrade command and the WASPostUpgrade command. The migration tools are command-line tools.

Use the wizard to migrate a V5.x Application Server to a V6 stand-alone Application Server.

 

Procedure

  1. Start the First steps console.

    • ./install_root/profiles/profile/firststeps/firststeps.sh

    • install_root\profiles\profile\firststeps\firststeps.bat

  2. Click the Migration wizard option on the First steps console.

    The First steps console starts the Migration wizard. The wizard displays its Welcome panel.

  3. Read the Welcome panel to learn about the migration, then click Next.

    The wizard displays the Detected versions of WebSphere Application Server panel.

  4. Select a previous version, then click Next to continue.

    Select the check box to specify the location of a previous installation that might not appear in the list.

    If the previous version specification is correct, the wizard displays the Target profile selection panel.

  5. Select the target profile from the list of valid V6 profiles for the installation, then click Next.

    Use the Profile creation wizard to create a target profile for the migration if one does not yet exist.

    The wizard displays the Port value assignment panel.

  6. Choose whether to use port values assigned to the previous installation, or generate new V6 port values that are already assigned to the target profile, then click Next.

    The wizard begins the premigration. The wizard displays a Migration status panel during the premigration.

    If the premigration is not successful, the wizard displays a failure panel. If the premigration is partially successful, the wizard displays a warning panel.

    Correct any problems and retry the migration.

    If the premigration is successful, the wizard displays an indication of success.

  7. Click Next to start the postmigration.

    If the postmigration is not successful, the wizard displays a failure panel. If the postmigration is partially successful, the wizard displays a warning panel.

    Correct any problems and retry the migration.

    If the postmigration is successful, the wizard displays an indication of success.

  8. Click Finish to exit the migration wizard.

 

What to do next

See Using the Profile creation wizard to learn more about creating profiles.

Refer to the description of the wasprofile command to learn more about the command, and to see examples of how to use the wasprofile command.