Migrating product configurations

Use the migration tools to migrate WebSphere Application Server product configurations.

Before you begin

Important: If your WebSphere Application Server environment matches either of the following two conditions, you must upgrade all the clients and servers that use the service integration technologies to Version 6.0.0.2 before you upgrade any such client or server to Version 6.0.1 or later:
  • Your WebSphere Application Server environment consists of one or more cells with multiple nodes and servers using the service integration technologies
  • Your WebSphere Application Server environment uses a topology with clients that connect to a server using service integration technology messaging

If you use an earlier version of WebSphere Application Server, the system administrator might have fine-tuned various application and server settings for your environment. It is important to have a strategy for migrating these settings with maximum efficiency and minimal loss.

Before using the migration tools, consult the Version 6.0 release notes to understand what fixes you must 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 possible.
Restriction: If you want to migrate to create a mixed cell containing Version 5.x nodes and you intend to apply maintenance to the Version 5.x nodes after the migration, your Version 6.0.x environment must be at level 6.0.2.7 or higher before starting the migration process. If you have a lower level of Version 6.0.x when you migrate, the repository and template directories will be removed from the Version 5.x nodes during the process of synchronizing with the cell's Version 6.0.x deployment manager and you will no longer be able to apply maintenance to the Version 5.x nodes.

The migration tools in WebSphere Application Server Version 6.0.x support migration from WebSphere Application Server Version 4.0.x, Version 5.0.x, and Version 5.1.x.

About this task

IBM provides a set of migration tools for migrating administrative configurations from Version 4.0.x, 5.0.x, or 5.1.x to the Version 6.0.x Network Deployment product.

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

You can perform incremental migration of Version 4.0.x or Version 5.x nodes by calling the migration tools multiple times, each time specifying a different configuration file. Various reasons exist for having multiple configuration files. Whatever the reason, migrating one configuration file at a time lets you test applications incrementally before continuing to the next configuration file.

When you use the migration tools, the overall migration process includes the following steps:
  1. Install the WebSphere Application Server Version 6.0.x product.
  2. Use the WebSphere Application Server Version 6.0.x Profile creation wizard to create one or more profiles for a deployment manager, a managed node, or a standalone application server.
  3. Start the First steps console.
  4. Select the Migration wizard on the First steps console.
  5. [AIX] [Solaris] [Version 6.0.2] Click Exit on the First steps console.
  6. Use the Migration wizard to migrate the previous release to the Version 6.0.x product.

    See Using the Migration wizard.

The Migration wizard calls the WASPostUpgrade command. The WASPostUpgrade command uses the backupConfig command to save the existing Version 6.0.x configuration before performing migration. The results are stored in the profile_name/temp directory. You can use the restoreConfig command to restore the backup if required.

Procedure

  1. Migrate the deployment manager.
    Note: The WebSphere Application Server Version 6.0.x deployment manager must be running whenever you migrate a Version 5.x deployment manager to it. Also, if you are migrating a Version 5.x deployment manager, the Version 6.0.x deployment manager must have the same cell name.
  2. Migrate WebSphere Application Server Version 5.x and 4.0.x Express and base nodes.
    Note: If you are migrating a WebSphere Application Server Version 5.x managed node to a Version 6.0.x managed profile, the node names must match.
  3. After migrating each base node, start each node.

    Use the startNode script from the profile_name/bin directory of each application server to start the node agent process.

    Occasionally, for example after rebooting an application server machine, you must restart the node agent server on the application server node, by running the startNode command from the profile_name/bin directory. To keep your application server 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 application server node. (You can also set up the dmgr server as a managed process on the deployment manager node.)

  4. Configure the WebSphere Application Server environment after migration, as described in Configuring WebSphere Application Server after migration. This is a way of verifying the results of the migration tools. You can also use Configuration mapping during 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.

Results

You can use the migration tools to migrate from one version of WebSphere Application Server to another.

What to do next

Return to Migrating and coexisting to continue.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

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

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tins_migadmin
File name: tins_migadmin.html