Migrating product configurations

Use the WebSphere Application Server Version 6.1.x migration tools to migrate your product configurations. These migration tools support migration from WebSphere Application Server Version 5.x and Version 6.0.x.

Before you begin

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 Version 6.1.x Target
Standalone and Custom Profiles Deployment Manager Profile
WebSphere Application Server Version 5.x or 6.0.x base standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment federated application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment deployment manager   Supported
WebSphere Application Server Version 5.x or 6.0.x Express standalone application server Supported  

You can migrate your product configurations using the WebSphere Application Server Version 6.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 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.

Best practice Best practice: The deployment manager maintains the master configuration data for all of the nodes that it manages. This configuration data is updated through the configuration manager. When the configuration manager detects that the updates to the configuration data were not made against the latest saved copy, it reject the updates and creates an exception. To avoid this situation, following these best practices:
  • Migrate each node independently. For example, let the first node complete the migration process before starting the process for the second node, and so on.
  • Ensure that the administrative console for the deployment manager is not running when the migration process is in progress.
If you need to migrate federated nodes concurrently, use the following steps to minimize the potential failures:
  1. Run the backupConfig command for the deployment manager and each federated node before you begin. For more information, see the documentation about the backupConfig command.
  2. Stagger the start of the migration process for each node by 3 to 5 minutes.
  3. Run the restoreConfig command on that node and rerun the migration process if a failure occurs. For more information, see the documentation about the restoreConfig command.
bprac

About this task

When you use the migration tools, the overall migration process includes these steps:
  1. Install the WebSphere Application Server Version 6.1.x product.
  2. Use the WebSphere Application Server Version 6.1.x manageprofiles command to create one or more profiles for a deployment manager, a managed node, or a standalone application server.
  3. Use the migration tools to migrate the previous release to the WebSphere Application Server Version 6.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 Version 6.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 WebSphere Application Server Version 6.1.x Network Deployment node:
    Notes:
    • The Version 6.1.x deployment manager must be running whenever you migrate a Version 5.x or 6.0.x deployment manager to it.
    • If you are migrating a Version 5.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 Version 5.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 Version 6.1.x.

    See Migrating Web server configurations.

  3. Migrate the WebSphere Application Server Version 5.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 Version 6.1.x standalone application server:
  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.

    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 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 a complete gateway configuration
      • Migrating from Version 5 embedded messaging
    • Examine any Lightweight Third Party Authentication (LTPA) security settings that you might have used in WebSphere Application Server Version 5.x or 6.0.x, and make sure that Version 6.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 Version 6.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.




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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=tmig_admin
File name: tmig_admin.html