WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate stand-alone application servers

Migrate to a v8.0 stand-alone application server

Use the migration tools to migrate from a WAS Application Server Version 6.x or 7.x stand-alone application server profile to a v8.0 stand-alone application server.

Supported configurations:

This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

For help, read Troubleshoot migration.

If your scenario includes migrating a WAS Application Server Version 6.x or 7.x configuration on one machine to v8.0 on another machine, use the alternate procedure described in Migrate to a v8.0 stand-alone application server on a remote machine.

Tip: Before migrating a WAS v6.x or 7.x stand-alone application server, use the backupConfig command or your own preferred backup utility to back up your existing configuration if to be able to restore it to its previous state after migration. Read the "backupConfig command" article in the information center for more information. Make sure that you note the exact name and location of this backed-up configuration.

Decide whether to migrate from WAS Application Server Version 6.x or 7.x to v8.0 using the Migration wizard or using the command-line migration tools.

Procedure

• Migrate from WAS Application Server Version 6.x or 7.x to v8.0 using the Migration wizard.
  1. Stop all of the WAS v6.x or 7.x application servers that are running on the node.

     Use the stopServer command from the WAS_HOME/bin directory. Read the "stopServer command" article in the information center for more information.

     For example, issue the following commands to stop server1 and server2 on the Linux operating system:

     ./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 Application Server v6.x or 7.x node without stopping it; however, stop the node before you can start the v8.0 node that you are installing. 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.

  2. Install WAS v8.0.

     Read the "Installing the product and additional software" article in the information center for more information.

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

     Restriction: We cannot use the Profile Management Tool to create profiles for WAS installations on 64-bit architectures except on the Linux for zSeries platform. However, you can use the Profile Management Tool on other 64–bit architectures if you use a WAS 32–bit installation.

     Read the "Creating profiles using the graphical user interface" article or the "manageprofiles command" article in the information center for more information.

  4. Use the Migration wizard to transfer configuration settings from v6.x or 7.x to the v8.0 stand-alone application server.

     Read Migrate to stand-alone application servers using the Migration wizard for more information.

     Perform one of the following actions to access the Migration wizard:

     • Go to Start > Programs > IBM WAS v8.0, and click Migration wizard.
     • Run the following command:
       WAS_HOME/bin/migration.sh

     This step transfers applications and configuration information for the v6.x or 7.x server resources, security, variables, and virtual hosts to the v8.0 stand-alone application server. All stored information is in XML files in...

     WAS_HOME/config/cells

     of each product.

     The Migration wizard uses the WASPreUpgrade command and WASPostUpgrade command to migrate the data and applications from v6.x or 7.x to Version 8.

     The WASPreUpgrade tool saves selected files from the /bin directory to a backup directory that 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 copy the environment in the backup directory to the v8.0 stand-alone application server installation.

• Migrate from WAS Version 6.x or 7.x to v8.0 using the command-line migration tools.
  1. Stop all of the WAS v6.x or 7.x application servers that are running on the node.

     ./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 Application Server v6.x or 7.x node without stopping it; however, stop the node before you can start the v8.0 node that you are installing. 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.

  2. Install WAS v8.0.

  3. Use the Profile Management tool or the manageprofiles command to create a WAS Application Server v8.0 profile.
  4. Run the WASPreUpgrade command, specifying the migration backup directory name and the existing WAS Application Server directory name.

     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.

     Read WASPostUpgrade command for more information.

     The WASPostUpgrade tool copies the environment in the backup directory to the WAS Application Server v8.0 stand-alone application server installation.

     When migrating a stand-alone application server from v6.x or 7.x to v8.0, you can choose a stand-alone application server node that has already been registered with an admin agent as the target of the migration.

Migrate product configurations
Migrate to a v8.0 stand-alone application server on a remote machine
Migrate product configurations with migration tools

Related

WASPreUpgrade command
WASPostUpgrade command

+

Search Tips   |   Advanced Search