Migrating product configurations

Use the WebSphere Application Server V6.1.x migration tools to migrate your product configurations. These migration tools support migration from WebSphere Application Server V5.x and V6.0.x.

See Overview of migration, coexistence, and interoperability and Premigration considerations. The following configuration upgrades of WebSphere Application Server versions and offerings are directly supported.

Table 1. Directly Supported Configuration Upgrades

Migration Source	WebSphere Application Server Network Deployment V6.1.x Target
Standalone and Custom Profiles	Deployment Manager Profile
WebSphere Application Server V5.x or 6.0.x base standalone application server	Supported	Â
WebSphere Application Server V5.x or 6.0.x Network Deployment standalone application server	Supported	Â
WebSphere Application Server V5.x or 6.0.x Network Deployment federated application server	Supported	Â
WebSphere Application Server V5.x or 6.0.x Network Deployment deployment manager	Â	Supported
WebSphere Application Server V5.x or 6.0.x Express standalone application server	Supported	Â

You can migrate your product configurations using the WebSphere Application Server V6.1.x command-line migration tools.

Before using the migration tools, consult the WebSphere Application Server Version 6.1.x Release Notes document to understand what fixes apply to earlier versions. Applying fixes to an earlier version might also apply fixes to files that have a role in the migration. Apply any fixes to ensure the most effective migration of configurations and applications.

Overview

1. Install the WebSphere Application Server V6.1.x product.

   See Task overview: installing.

2. Use the WebSphere Application Server V6.1.x manageprofiles command to create one or more profiles for a deployment manager, a managed node, or a standalone application server.

   See manageprofiles command.

3. Use the migration tools to migrate the previous release to the WebSphere Application Server V6.1.x product.

   See Using the migration tools to migrate product configurations.

The WASPreUpgrade command saves the configuration and applications of the previously installed version of WebSphere Application Server into a migration-specific backup directory. The WASPostUpgrade command uses the backupConfig command to save the existing V6.1.x configuration before performing migration, and the results are stored in the profile_name/temp directory. You can use the restoreConfig command to restore the backup if required. See restoreConfig command.

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

Procedure

1. Migrate the deployment cell. Select one of the following migration scenarios for information about how to migrate configuration data to a WebSphere Application Server Version 6.1.x Network Deployment node:

   • Migrating from Network Deployment to Network Deployment V6.1

   • Migrating a standalone application server to a V6.1 federated node

   Notes:

   • The V6.1.x deployment manager must be running whenever you migrate a V5.x or 6.0.x deployment manager to it.

   • If you are migrating a V5.x or 6.0.x deployment manager, the Version 6.1.x deployment manager must have the same cell name.

   • If you are migrating a V5.x or 6.0.x managed node to a Version 6.1.x managed profile, the node names must match.

   • See Coexistence support for information on restrictions on using mixed-release cells.

2. Migrate your Web server plug-ins to work with WebSphere Application Server V6.1.x.

   See Migrating Web server configurations.

3. Migrate the WebSphere Application Server V5.x and Version 6.0.x standalone application server nodes. Select one of the following migration scenarios for information about how to migrate configuration data to a V6.1.x standalone application server:

   • Migrating to a V6.1 standalone application server profile

   • Migrating the V5.x or 6.0.x default instance to the default V6.1 standalone application server profile

4. After migrating each base node, start each node.

   Use the startNode script from the app_server_root/bin directory to start the node agent process. See startNode command.

   Occasionally, for example after rebooting an application server machine, restart the node agent server on the application server node by running the startNode command from the app_server_root/bin directory. To keep your application server nodes running, use the operating system to monitor and restart the node agent process on each application server node. (You can also set up the dmgr server as a managed process on the deployment manager node.)

5. You might want to do some things that are not done automatically by the migration tools.

   • Perform any of the following non-automated tasks:

     • Migrating to V3 of the UDDI registry

     • Migrating a complete gateway configuration

     • Migrating servers from multi-broker replication domains to data replication domains

     • Migrating from V5 embedded messaging

   • Examine any Lightweight Third Party Authentication (LTPA) security settings that you might have used in WebSphere Application Server V5.x or 6.0.x, and make sure that V6.1.x security is set appropriately.

     See Lightweight Third Party Authentication.

   • Check the WASPostUpgrade.log file in the logs directory for details about any JSP objects that the migration tools did not migrate.

     If V6.1.x does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.

   • Configure WebSphere Application Server to use a database.

     For example, you can configure WebSphere Application Server to use DB2.

6. Use Configuration mapping during product-configuration migration to verify the results of the migration.

   The article has a detailed description of how the migration tools migrate objects and what you should verify.