WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Migrating product configurations

This topic shows you the steps to take for migrating WebSphere Extended Deployment Version 5.1 configuration settings to WebSphere Extended Deployment Version 6.0.1.

Before you begin

For migration to succeed, cell and node names must match for both WebSphere Application Server Version 5.1 / WebSphere Extended Deployment Version 5.1 and WebSphere Application Server Version 6.0.2 / WebSphere Extended Deployment Version 6.0.1. Since WebSphere Extended Deployment Version 6.0.1 does not support a mixed WebSphere Extended Deployment Version 5.1 and WebSphere Extended Deployment Version 6.0.1 environment, all WebSphere Extended Deployment nodes must be migrated together. Therefore, the runtime must be upgraded to WebSphere Application Server Version 6.0.2 and WebSphere Extended Deployment Version 6.0.1 on all nodes. The WebSphere Application Server migration process must be performed on the deployment manager and all WebSphere Extended Deployment application server nodes. Finally, the WebSphere Extended Deployment migration process is performed on the deployment manager.

The WebSphere Application Server migration process must be performed on the deployment manager and all WebSphere Extended Deployment application server nodes. Finally, the WebSphere Extended Deployment migration process is performed on the deployment manager.

  • Type PK43942 in the Search Support field. This is the specific APAR number for the interim fix.
  • Select Download (Fixes, Utilities, APARs) to limit the returned results, and click Search.

About this task

Complete the following steps to migrate to WebSphere Extended Deployment Version 6.0.1.

Procedure

  1. Install WebSphere Application Server Version 6.0.2 on machine hosting deployment manager.
  2. Create a Version 6.0.2 deployment manager profile.
  3. Perform Version 6.0.2 migration on deployment manager. That is, use the WASPreUpgrade/WASPostUpgrade utilities. See the WebSphere Application Server Version 6.0 migration tools topic in the WebSphere Application Server Infocenter.
  4. Install WebSphere Extended Deployment Version 6.0.1 on the machine hosting the Version 5.1 deployment manager. See Installing the product.
  5. Run WebSphere Extended Deployment Version 6.0.1 augmentation against the WebSphere Application Server Version 6.0.2 deployment manager profile.
  6. Install WebSphere Application Server Version 6.0.2 on machine hosting the first WebSphere Extended Deployment 5.1 application server node.
  7. Create a WebSphere Application Server Version 6.0.2 custom profile.
  8. Migrate application server node base configuration to WebSphere Application Server Version 6.0.2 custom profile using the WASPreUpgrade/WASPostUpgrade utilities.
  9. Install WebSphere Extended Deployment Version 6.0.1 on machine hosting the first WebSphere Extended Deployment 5.1 application server node.
  10. Run WebSphere Extended Deployment Version 6.0.1 augmentation against the WebSphere Application Server Version 6.0.2 managed profile, created in step 7.
  11. Repeat steps 6-10 for each WebSphere Extended Deployment 5.1 application server node.
  12. Stop all WebSphere processes in the cell, and perform WebSphere Extended Deployment migration on the deployment manager. You can use either the XDUpgrade command or the Migration wizard.
  13. Start remaining servers.
  14. This step is comprised of manual tasks to perform to complete the migration. Perform these manual steps if necessary.
    1. You might need to migrate the Autonomic Request Flow Manager (ARFM) manual settings file. See the Migrating the ARFM manual settings file for migration instructions.
    2. The WebSphere Extended Deployment Version 6.0.1 migration component will migrate node groups and dynamic clusters for the existing WebSphere Extended Deployment Version 5.1 configuration. However, custom configuration of resources and variables applied to the dynamic cluster members will not be migrated. The configuration of resources and variables has moved to the cluster level in Version 6.0.1. Therefore, you must manually reconfigure any custom settings in the Version 6.0.1 environment.
    3. Routing rules for generic server clusters. These routing rules are not compatible between WebSphere Extended Deployment Version 5.1 and WebSphere Extended Deployment Version 6.0.1, so the WebSphere Extended Deployment Version 5.1 settings are not migrated to WebSphere Extended Deployment Version 6.0.1. These settings must be manually entered in the WebSphere Extended Deployment Version 6.0.1 deployment manager.

Results

All WebSphere Extended Deployment Version 5.1 configuration information is transferred to your WebSphere Extended Deployment Version 6.0.1 environment with two exceptions:
  1. Routing rules for generic servers - The WebSphere Extended Deployment Version 5.1 and WebSphere Extended Deployment Version 6.0.1 generic server routing rules are incompatible. If you have routing rules in your WebSphere Extended Deployment Version 5.1 configuration, review them and define new WebSphere Extended Deployment Version 6.0.1 routing rules in accordance with your requirements. See the Routing requests to external nodes with generic server clusters article for instructions.
  2. ARFM manual settings - The WebSphere Extended Deployment Version 5.1 and WebSphere Extended Deployment Version 6.0.1 ARFM manual settings are incompatible. If you have WebSphere Extended Deployment Version 5.1 ARFM manual settings, review them and define new ARFM manual settings in accordance with your requirements. See the Migrating the ARFM manual settings file topic for further instructions.
  3. The WebSphere Extended Deployment Version 6.0.1 migration component will migrate node groups and dynamic clusters for the existing WebSphere Extended Deployment Version 5.1 configuration. However, custom configuration of resources and variables applied to the dynamic cluster members will not be migrated. The configuration of resources and variables has moved to the cluster level in Version 6.0.1. Therefore, you must manually reconfigure any custom settings in the Version 6.0.1 environment.



Subtopics
Using the Migration wizard
XDUpgrade command
Related concepts
Where migration tasks are performed
Related tasks
Installing the product
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 3:56:54 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/migration/txdmigsteps.html