Migrating cells to new host machines using the command-line tool
You can migrate cell configurations from a previous version of WebSphere® Application Server that is hosted on one machine to an instance of WebSphere Application Server Version 9.0 that is hosted on a different machine. The source and target host machines do not need to run the same operating system.
Before you begin
This topic is about profile configuration migration, specifically migrating cells to a different host.
- To clone migrate cells to a different host, see Clone migrating cells to new host machines using the command-line tools. In a clone migration, you can continue to use a source profile after you migrate it to a Version 9.0 environment.
- To migrate cells on the same host, see Migrating cells using the command-line tools.
- To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit.
For resources to help you plan and perform your migration, see Knowledge Collection: Migration planning for WebSphere Application Server.
For videos about migrating cells to
a different machine, see the WebSphere Administration - Migrating cells
REMOTELY using the command-line tools videos in the WebSphere Migration - Using the CMD line playlist. The steps in this topic
are not for a clone migration. The videos mention clone migration steps. To not do a clone
migration, do not set the -clone optional parameter to true
in
a WASPostUpgrade migration command.
About this task
This task describes how to migrate each profile in a cell configuration from a previous version of WebSphere Application Server to WebSphere Application Server Version 9.0 hosted on a different machine. The cell configuration consists of a deployment manager with one or more nodes, a web server, and an application client. All ports are migrated forward into the new configuration.
To migrate a cell configuration, you run WASPreUpgrade, WASPostUpgrade, manageprofiles, and other migration commands that are described in Using the migration tools. You can specify individual parameters on migration commands, or specify the -properties file_name.properties parameter to input a properties file.
If WebSphere Application Server Version 9.0 is not installed on the source host machine, you must generate a remote migration .jar file on the target host machine that matches the operating system of the source machine. The remote migration .jar file provides the source host with the Version 9.0 WASPreUpgrade tool, which you use to create the migration backup directory for the profile.
- OPTION 1: Install the target product version on the source machine.
- OPTION 2: Create the remote migration .jar file. The .jar file has the WASPreUpgrade command and files that are needed to support its running, including Java, collected from the target installation.
When the multiple source machines all have the same operating system architectures but different from the target machine, then only one source machine needs to have the target release installed. From that one source machine, the remote migration .jar can be created and used on the other source machines.
This procedure assumes that the previous configuration is running and that you are migrating all profiles to a different host machine.
Procedure
Results
You used the migration tools to migrate the cell configurations from a previous version of WebSphere Application Server to new host machines that run WebSphere Application Server Version 9.0.