Migrating cell configurations to new host machines using the command-line tool

Before you begin

Supported configurations Supported configurations:

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

sptcfg

Review the migration planning information. See Knowledge Collection: Migration planning for WebSphere® Application Server.

This information describes migrating cells to a different machine. For information on migrating cells on the same machine, see Migrating cells using the command line tools.

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 8.5 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. The source and target host machines do not need to run the same operating system.

If WebSphere Application Server Version 8.5 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 8.5 WASPreUpgrade tool, which you use to create the migration backup directory for the profile.

This procedure assumes that the previous configuration is running and that you are migrating all profiles to a different host machine.

Avoid trouble Avoid trouble: Ensure that your setting for the maximum number of open files is 10000 or greater. If the number of open files is too low, this can cause a variety of migration failures.gotcha
Restriction: Remote migration on IBM® i is NOT supported.

Procedure

  1. Back up the deployment manager and all old nodes
  2. Install WebSphere Application Server Version 8.5
  3. Create the remote migration .jar file
  4. Create the target deployment manager profile
  5. Save the current deployment manager configuration to the migration backup directory
  6. Archive the backup directory created by the WASPreUpgrade command
  7. Restore the previous deployment manager configuration
  8. Save the Version 8.5 migrated deployment manager configuration to a file
  9. Stop and disable the deployment manager on the old host
  10. Start the Version 8.5 deployment manager
  11. Manually synchronize all nodes
  12. Migrate plug-ins for web servers
  13. Migrate application client installations
  14. Migrate nodes

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 8.5.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 10:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=tmig_migrate_remote_commandline
File name: tmig_migrate_remote_commandline.html