Migrate product configurations

 

+

Search Tips   |   Advanced Search

 

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

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

Table 1. Directly Supported Configuration Upgrades

Migration Source	WAS V6.1.x Target
ND Standalone and Custom Profiles	ND Deployment Manager Profile
WAS V5.x or 6.0.x base standalone appserver	Supported
WAS V5.x or 6.0.x ND standalone appserver	Supported
WAS V5.x or 6.0.x ND federated appserver	Supported
WAS V5.x or 6.0.x ND deployment manager		Supported
WAS V5.x or 6.0.x Client
WAS V5.x or 6.0.x Express standalone appserver	Supported
WAS V5.0.x Enterprise base standalone appserver	Supported
WAS V5.0.x Enterprise ND standalone appserver	Supported
WAS V5.0.x Enterprise ND federated appserver	Supported
WAS V5.0.x Enterprise ND deployment manager		Supported
WBISF V5.1.x base standalone appserver	Supported *
WBISF V5.1.x ND standalone appserver	Supported *
WBISF V5.1.x ND federated appserver	Supported *
WBISF V5.1.x ND deployment manager		Supported *

WAS Version 6.1.x supports the migration of a subset of programming model extensions (PMEs) from WebSphere Business Integration Server Foundation. See Programming model extension migration for more information on this support.

You can migrate your product configurations using the WAS V6.1.x Migration wizard or the command-line migration tools.

Before using the migration tools, consult the WAS 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

When you use the migration tools, the overall migration process includes these steps:

1. Install the WAS V6.1.x product.
2. Optional: Use the WAS V6.1.x Profile Management tool to create one or more profiles for a deployment manager, a managed node, or a standalone appserver.

3. Use the migration tools to migrate the previous release to the WAS V6.1.x product.

   1. Perform one of the following actions to start the Migration wizard:

      • Go to...

        Start | Programs | IBM WebSphere | Application Server V6.1 ND | Migration wizard

      • Run the following command:
        app_server_root/bin/migration.sh

   2. Use the Migration wizard to migrate the previous release to the Version 6.1.x product.

The Migration wizard calls the WASPreUpgrade and WASPostUpgrade commands.

The WASPreUpgrade command saves the configuration and applications of the previously installed version of WAS 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.

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

 

Procedure

Perform the following actions.

1. Migrate the deployment cell. Select one of the following migration scenarios for information about how to migrate configuration data to a WAS Version 6.1.x ND node:
   • Migrating to a V6.1 deployment manager using the Migration wizard
   • Migrating to a V6.1 deployment manager
   • Migrating to a V6.1 managed appserver
   • Migrating a large ND configuration with a large number of applications

   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 WAS V6.1.x.

3. Migrate the WAS V5.x and Version 6.0.x standalone appserver nodes. Select one of the following migration scenarios for information about how to migrate configuration data to a V6.1.x standalone appserver:
   • Migrating to a V6.1 appserver using the Migration wizard
   • Migrating to a V6.1 standalone appserver
   • Migrating to a V6.1 standalone appserver on a remote machine

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

   Use the startNode script from the profile_root/bin directory of each appserver to start the node agent process. See startNode command.

   Occasionally, for example after rebooting an appserver machine, restart the node agent server on the appserver node by running the startNode command from the profile_root/bin directory. To keep your appserver nodes running without having to access the bin directory of each one, use the operating system to monitor and restart the node agent process on each appserver node. (You can also set up the dmgr server as a managed process on the deployment manager node.) For more information, see Automatically restarting server processes.

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 security settings that you might have used in WAS V5.x or 6.0.x, and make sure that V6.1.x security is set appropriately.

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

   • Review your Java virtual machine settings to verify that you are using a heap size of at least 50 for improved startup performance.

     If you have used a smaller heap size in the past, you can use the default heap size of 50.

   • Configure WAS to use a database.

     For example, you can configure WAS 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.

---

Configuration mapping during product-configuration migration
Use the migration tools to migrate product configurations
Migrate standalone appservers
Migrate ND configurations
Migrate Cloudscape databases
Migrate a previously non-root configuration to root
Roll back your environment