Migrate to a V6.1 standalone appserver

 

Use the migration tools to migrate from WAS V5.x or 6.0.x to V6.1. See Overview of migration, coexistence, and interoperability and Premigration considerations.

For help in troubleshooting problems when migrating, see Troubleshooting migration.

If your scenario includes migrating a WAS V5.x or 6.0.x configuration on one machine to V6.1 on another machine, use the alternate procedure described in Migrating to a V6.1 standalone appserver on a remote machine.

Before migrating a WAS V5.x or 6.0.x standalone appserver, use the backupConfig command or your own preferred backup utility to back up your existing configuration if you want to be able to restore it to its previous state after migration. See backupConfig command. Make sure that you note the exact name and location of this backed-up configuration.

Decide whether you want to migrate from WAS V5.x or 6.0.x to V6.1 using the Migration wizard or using the command-line migration tools.

 

Procedure

• Migrate from WAS V5.x or 6.0.x to V6.1 using the Migration wizard.

  1. Stop all of the WAS V5.x or 6.0.x appservers running on the node.

     Use the stopServer command from the app_server_root/bin directory. See stopServer command. 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.

     You can migrate a WAS V5.x or 6.0.x node without stopping it. 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 you can start the V6.1 node that you are installing.

  2. Install WAS V6.1.

     See Installing the product and additional software.

      

  3. Optional: Use the Profile Management tool or the manageprofiles command to create a WAS V6.1 profile.

     See Creating profiles through the graphical user interface or manageprofiles command.

  4. Use the Migration wizard to transfer configuration settings from V5.x or 6.0.x to the V6.1 standalone appserver.

     See Use the Migration wizard to migrate product configurations. Perform one of the following actions to access the Migration wizard:

     • Go to Start > Programs > IBM WebSphere > Application Server V6.1 Network Deployment, and click Migration wizard.

     • Run the following command:

       • app_server_root/bin/migration.sh

       • app_server_root\bin\migration.bat

     The Migration wizard uses the WASPreUpgrade command and WASPostUpgrade command to migrate the data and applications from V5.x or 6.0.x to V6.1.

     This step transfers applications and configuration information for the Version 5.x or 6.0.x server resources, security, variables, and virtual hosts to the V6.1 standalone appserver. All stored information is in XML files in the app_server_root/config/cells directory of each product. For a full description of each XML file, see Configuration documents and Configuration document descriptions. The WASPreUpgrade tool saves selected files from the /bin directory to a backup directory you specify on a wizard panel. Migration saves files from the following directories to the backup directory:

     • classes

     • config

     • installableApps

     • installedApps (or an alternate directory specified by the user)

     • properties

     Later, the Migration wizard uses the WASPostUpgrade tool to restore the environment in the backup directory into the V6.1 standalone appserver installation.

• Migrate from WAS V5.x or 6.0.x to V6.1 using the command-line migration tools.

  1. Stop all of the WAS V5.x or 6.0.x appservers running on the node.

     Use the stopServer command from the app_server_root/bin directory. See stopServer command. 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.

     You can migrate a WAS V5.x or 6.0.x node without stopping it. 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 you can start the V6.1 node that you are installing.

  2. Install WAS V6.1.

     See Installing the product and additional software.

  3. Use the Profile Management tool or the manageprofiles command to create a WAS V6.1 profile.

     See Creating profiles through the graphical user interface or manageprofiles command.

  4. Run the WASPreUpgrade command, specifying the migration backup directory name and the existing WebSphere Application Server directory name.

     See WASPreUpgrade command. The WASPreUpgrade tool saves selected files from the /bin directory to a backup directory you specify on a wizard panel. Migration saves files from the following directories to the backup directory:

     • classes

     • config

     • installableApps

     • installedApps (or an alternate directory specified by the user)

     • properties

  5. Run the WASPostUpgrade command, specifying the migration backup directory.

     See WASPostUpgrade command.

     The WASPostUpgrade tool restores the environment in the backup directory into the WebSphere Application Server V6.1 standalone appserver installation.

---

Migrating product configurations
Migrating to a V6.1 standalone appserver on a remote machine
Use the migration tools to migrate product configurations

 

Related Reference

WASPreUpgrade command
WASPostUpgrade command
clientUpgrade command