Migrate a V5.x Application Server configuration instance to a V6 Application Server profile

The migration tools of WebSphere Application Server, V6 support migrating a V5.x configuration instance to a V6 profile.

 

Before you begin

This task describes how to migrate the configuration of a V5.x configuration instance to a V6 profile. This task describes how to use the V6 migration tools to perform the migration.

 

Overview

If the node you are migrating is part of a deployment manager cell, migrate the V5.x deployment manager to V6 first, before continuing this procedure. The deployment manager node must always be at the highest release level within the cell.

 

Procedure

  1. Stop the V5.x deployment manager and start the V6 migrated deployment manager if the deployment manager is not already running.

    During migration the V6 deployment manager must be running for the migration tools to:

    • Update the configuration for each federated node

    • Request full synchronization

    If the V6 deployment manager is not running, failures can occur.

  2. Stop all of the V5.x Application Servers that are running on the node. Use the stopServer command from the install_root/bin directory. For example, issue the following commands to stop server1 and server2 on a Linux platform 

    stopServer.sh server1
stopServer.sh server2

    If security is enabled, specify the -user and -password parameters on the stopServer command.

    We can migrate a V5.x node without stopping it. But it is not necessary to have the node running to migrate its configuration. The migration tools can retrieve all the configuration data while the node is stopped. You must stop the node before one can start the V6 node that you are installing.

  3. Stop the node agent process. Run the stopNode command from the install_root/bin directory of the V5.x Application Server. For example, issue the following command to stop the nodeagent process on a Linux platform 

    stopNode.sh

    If security is enabled, specify the -user and -password parameters on the stopNode command.

  4. Install the V6 product.

  5. From the V6 node's <profile>/bin directory, run the following command:

    UNIX 

     ./WASPreUpgrade.sh <backupDirectory> <V5_location>

    Windows 

     WASPreUpgrade.bat <backupDirectory> <V5_location>
    where backupDirectory is the name of the directory you want the output of WASPreUpgrade to be stored, and V5_location is the location where the V5.x node is installed.

  6. From the V6 node's <profile>/bin directory, run the following command:

    UNIX 

    ./WASPostUpgrade.sh <backupDirectory> -oldProfile <host_instanceName> -profileName <ProfileName>

    Windows 

     WASPostUpgrade.bat <backupDirectory> -oldProfile <host_instanceName> -profileName <ProfileName>
    where backupDirectory is the same directory you specified in WASPreUpgrade, and ProfileName is the name of the V6 profile. (See WASPostUpgrade command for more information on WASPostUpgrade.)

  7. Start the V6 node.

  8. Optional: Uninstall the V5.x node. Perform this step only after you are certain that you have successfully migrated the configuration of the node you intend to delete.

 

Result

You have upgraded a V5.x configuration instance to a Version 6 profile.

 

What to do next

Return to Migrating configuration data to continue.

 

See Also


Migration tools

 

See Also


The WASPreUpgrade command
The WASPostUpgrade command
The clientUpgrade command
The convertScriptCompatibility command