Migrate a V5 deployment manager to V6 with the Migration wizard

V6 migration always works by migrating an earlier supported version of WAS to a deployment manager 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, have access to the existing V5 deployment manager. You must also have a valid V6 deployment manager profile to serve as the target of the migration.

You should have installed Version 6 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 V6 target exists, one 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.

 

Overview

This topic describes using the Migration wizard to migrate a V5.x deployment manager to a V6 deployment manager.

The Migration wizard is new as of V6. The wizard is the graphical interface to the Version 6 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 V5 deployment manager to the V6 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:

   • ./install_root/profiles/dmgr_profile/firststeps/firststeps.sh

   • install_root\profiles\dmgr_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 V5 previous version is valid, the wizard displays the Target profile selection panel.

5. 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 V6 deployment manager must be running whenever you migrate a V5 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:

   • ./install_root/profiles/dmgr_profile/firststeps/firststeps.sh

   • install_root\profiles\dmgr_profile\firststeps\firststeps.bat

   We can also use the startManager command to start the deployment manager node directly:

   • install_root/profiles/dmgr_profile/bin/startManager.sh

   • install_root\profiles\dmgr_profile\bin\startManager.bat

   
   
   
   
   The V6 deployment manager must have the same cell name
   as the V5 cell.
   
   
   
   After migrating a V5 deployment manager, one can migrate
   a V5 managed node to a V6 managed node. If you are migrating a V5.x managed
   node to a V6 managed node, the node names must match. When you create the
   profile, use the node name of the V5 managed node that you intend to migrate.
   See Migrating a V5.x managed node to a V6 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. 
   
   
   
   
   
   Choose whether to use port values assigned to the previous installation,
   or to generate new V6 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.
   
   
   
   
   Verify that the V6 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.
   
   
   
   
   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.
   
   
   
   
   Click Finish to exit the migration wizard.
   
   

 

What to do next

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

Refer to the description of the wasprofile command to learn more about the command-line tool, and to see examples of how to use the command. See Migrating a V5.x managed node to a V6 managed node to get started migrating individual managed node to V6.

---

 

Related Tasks

Migrating a V5.x managed node to a V6 managed node

 

---