Migrating a Version 5.x deployment manager to Version 6.0.x with the Migration wizard

Use the Migration wizard to migrate from a WebSphere Application Server Version 5.x deployment manager to Version 6.0.x.

Before you begin

Collect the following information about your Version 5.x 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 must have access to the existing Version 5.x deployment manager. You must also have a valid Version 6.0.x deployment manager profile to serve as the target of the migration.

You should have installed Version 6.0.x already. Use the Profile creation wizard to create a new target profile if the deployment manager target for the migration does not yet exist. After verifying that a valid Version 6.0.x target exists, you can start the procedure.

The Network Deployment product does not create a deployment manager profile during installation because there are three profile types that you might require on any machine.

The Installation wizard prompts you to use the Profile creation wizard at the end of installing the core product files. However, using the Profile creation wizard at that time is optional.

Create a deployment manager profile if you have not already created one.

About this task

This article describes using the Migration wizard to migrate a Version 5.x deployment manager to a Version 6.0.x deployment manager.

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

After gathering all of the information that is required during the migration, use the wizard to migrate a Version 5.x deployment manager to the Version 6.0.x deployment manager.

Procedure

  1. Start the First steps console.
    Use the First steps console to start the deployment manager. The command to start the First steps console for the deployment manager profile is at this location:
    • [Linux] ./profile_root/firststeps/firststeps.sh
    • [Windows] profile_root\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 Version 5.x previous version is valid, the wizard displays the Target profile selection panel.

  5. Specify a backup directory, then click Next to continue.

    If the Version 6.0.x profile is valid, the wizard displays the Target profile selection panel.

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

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

    Installing the Network Deployment product does not automatically create a profile.

    The Version 6.0.x deployment manager must be running whenever you migrate a Version 5.x deployment manager to it.

    Use the First steps console to start the deployment manager. The command to start the First steps console for the deployment manager profile is at this location:
    • [Linux] ./profile_root/firststeps/firststeps.sh
    • [Windows] profile_root\firststeps\firststeps.bat
    You can also use the startManager command to start the deployment manager node directly:
    • ./profile_root/bin/startManager.sh
    • profile_root\bin\startManager.bat

    The Version 6.0.x deployment manager must have the same cell name as the Version 5.x cell.

    After migrating a Version 5.x deployment manager, you can migrate a Version 5.x managed node to a Version 6.0.x managed node. If you are migrating a Version 5.x managed node to a Version 6.0.x managed node, the node names must match. When you create the profile, use the node name of the Version 5.x managed node that you intend to migrate. See Migrating a Version 5.x managed node to a Version 6.0.x managed node for more information.

    If the cell name does not match, the wizard displays a warning panel.

    The wizard displays the Port value assignment panel.

  7. Choose whether to use port values assigned to the previous installation, or to generate new Version 6.0.x port values that are already assigned to the deployment manager profile, then click Next.

    The wizard displays the Deployment manager verification panel that warns you to verify that the deployment manager is running.

  8. Verify that the Version 6.0.x deployment manager is running, 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.

  9. 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.

  10. Click Finish to exit the Migration wizard.

What to do next

See Migrating a Version 5.x managed node to a Version 6.0.x managed node to get started migrating individual managed node to Version 6.0.x.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tins_helpmigw5dm
File name: tins_helpmigw5dm.html