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

The migration tools of WebSphere Application Server, V6 support migrating V5.x managed nodes to V6 managed nodes.

 

Before you begin

Migrating a V5 managed node to a V6 managed node requires that you first migrate the V5 deployment manager node to a V6 deployment manager node. Migrating Network Deployment V5.x to V6 is described in Migrating Network Deployment, V5.x to a V6 deployment manager.

Before starting the migration of a managed node from V5 to V6, create a V6 profile for either a stand-alone Application Server or a managed node. If you create a V6 managed node profile, do not federate the node before migration. The migration tools federate the V6 node during migration.

The migration procedure is the same for either type of V6 profile. The end result can vary slightly. Each stand-alone Application Server has a server1 Application Server process. A V5 managed node might not have a server1 process. This task describes migrating to a V6 managed node that has not been federated.

 

Overview

After migrating a V5 deployment manager to a V6 deployment manager, the V6 deployment manager runs in compatibility mode by default, where it can manage both V5 nodes and V6 nodes. The managed nodes of the V5 deployment manager are now running as V5 managed nodes in the V6 deployment manager.

Over time, migrate each V5 managed node in the V6 cell to a V6 managed node. After migrating all V5 managed nodes, use the compatibility script, convertScriptCompatibility, to change the deployment manager from a node that supports backward compatibility of V5.x administration scripts to a node that supports only V6.

 

Procedure

  1. Perform a typical or custom V6 installation, as described in Installing the product and additional software.

  2. Migrate the V5 deployment manager node to V6, as described in Migrating Network Deployment, V5.x to a V6 deployment manager.

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

    • Replace port values for virtual hosts and Web containers?

      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.

  4. Use the V6 Profile creation wizard to create a managed node, but do not federate the node.

    The V6 node must have the same node name as the V5 node.

    Note: We can migrate a V5.x node without stopping it, but it is not necessary for it to be running for you to migrate its configuration. The migration tools can retrieve all the configuration data while the node is either running or stopped. However, stop the V5.x node before one can start the V6 node that you are installing, so it makes sense to stop it now.

  5. Use the Migration wizard to migrate the V5 managed node to the V6 managed node profile, as described in Migrating a V5 Application Server to a V6 Stand-alone Application Server with the Migration wizard.

    The Migration wizard copies the configuration and applications from the V5 managed node to the V6 managed node. After migrating all of the data, the Migration wizard federates the V6 managed node into the deployment manager cell.

  6. Migrate as many V5 managed nodes as you intend to migrate by using the following procedure.

    1. Determine the node name of the V5 managed node.

    2. Use the Profile creation wizard to create a V6 managed node, but do not federate the node.

    3. Use the Migration wizard to migrate the V5 managed node to the V6 managed node.

    Note: For migration to be successful, use the same node names and cell names for each node from V5 to V6.

  7. If you chose the compatibility option (which is the default), and if all of your nodes are completely migrated to V6, run the convertScriptCompatibility script to remove backward compatibility from the V6 deployment manager.

    1. Issue the following command from the bin directory.

      • ./install_root/bin/convertScriptCompatibility.sh

      • install_root\bin\convertScriptCompatibility.bat

 

What to do next

Occasionally (e.g., after rebooting an Application Server machine), restart the nodeagent server on the Application Server node by running the startNode command from the profile/bin directory. To keep your Application Server nodes running, without having to access the bin directory of each one, use the operating system to monitor and restart the nodeagent process on each Application Server node. (We can also set up the dmgr server as a managed process on the deployment manager node.) For more information, see Automatically restarting server processes.

Adding a node automatically issues the startNode command for the node.

 

Related Tasks


Using the Migration wizard