Map Scenario 2: Migrating cell configurations to new host machines using the command-line tool

Before you begin

Supported configurations Supported configurations:

This topic 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 Scenario 1: Migrating a cell 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 across operating systems or to WebSphere Application Server Version 8.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. The source and target host machines do not need to run the same operating system.

If WebSphere Application Server Version 8.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 8.0 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: [Updated in September 2012] Remote migration on iSeries® is NOT supported. [Updated in September 2012]
sep2012

Procedure

  1. Run the backupConfig command on the deployment manager and all old nodes
  2. Install WebSphere Application Server Version 8.0
  3. Create the remote migration .jar file
  4. Create the target deployment manager profile
  5. Run the WASPreUpgrade command.
  6. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure
  7. Archive the backup directory created by the WASPreUpgrade command
  8. Run the WASPostUpgrade command from the new deployment manager profile bin directory
  9. Verify the logs for success
  10. Run the backupConfig command on the Version 8.0 deployment manager
  11. Stop and disable the deployment manager on the old host
  12. Start the Version 8.0 deployment manager
  13. Manually synchronize all nodes
  14. Migrate plug-ins for web servers
  15. Run a migration on application client installations
  16. Migrate nodes
  17. Troubleshoot

Results

You have migrated from a previous version to WebSphere Application Server Version 8.0 or later using the migration tools.




In this information ...


(Index)

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.



Terms and conditions for information centers | Feedback

Last updated: Feb 6, 2014 11:50:09 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-dist&topic=tmig_migrate_remote_commandline
File name: tmig_migrate_remote_commandline.html