./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:Migrate V5.x of WAS to a V6 Application ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:Server - WAS 6.x ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

Migrate V5.x of WAS to a V6 Application ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:Server

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

The migration tools of WebSphere Application Server, V6 ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:support migrating configuration data from V5.x to V6. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

Before you begin

If your scenario includes migrating a V5.x configuration on one machine ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:to WAS V6 on another machine, use the alternate procedure ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:described in Migrating V5.x of WAS to a V6 stand-alone ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:Application Server on a remote machine. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

Overview

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

This task describes how to migrate the configuration of a V5.x ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:node to V6. This task describes how to use the V6 migration tools to perform ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:the migration. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

For federated migrations, IBM advises ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:that you run the backupConfig ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:command on each node in the cell before migrating the deployment manager. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

Procedure

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

    ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

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

    ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:stopServer.sh server1
    ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:stopServer.sh server2
    ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
    ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

    If security is enabled, specify the -user ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:and -password parameters on the stopServer command. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

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

  2. Install the V6 product. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

  3. Use the Profile Creation wizard to create ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:a V6 profile. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

  4. Use the Migration ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:wizard to migrate the node (the recommended way to access the Migration ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:wizard is through the First Steps console). ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

Result

After going through the Migration wizard, you have upgraded a Version ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:5.x node to V6. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

What to do next

Return to Migrating configuration data to continue. ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:


./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

See Also

./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
Migration tools ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

See Also

./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
The WASPreUpgrade command ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
The WASPostUpgrade command ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
The clientUpgrade command ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 


./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:
./Migrating_V5.x_of_WAS_to_a_V6_Application.html: ./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

./Migrating_V5.x_of_WAS_to_a_V6_Application.html:

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.