Migrating an application server node for z/OS

You can migrate an application server node from your current WebSphere® Application Server Network Deployment Version 6.1.0.x and WebSphere Extended Deployment Version 6.1.0.5 cell to a new WebSphere Application Server Network Deployment Version 7.0.x and WebSphere Extended Deployment Version 6.1.1 cell.

Before you begin

Migrate the deployment manager.

Procedure

  1. Create and mount a new configuration file system as the target of the migration.
  2. Mount the product HFS for WebSphere Application Server Network Deployment Version 7.0.x at /usr/lpp/zWebSphere/V7R0.
  3. Use the z/OS® Migration Management Tool or zmmt command to generate and run the Job Control Language (JCL) jobs for Version 7.0.x. See Migrating product configurations with migration tools for more information.
  4. Use the WebSphere Customization Tools to generate the Version 6.1.1 augmentation job for each node. Use the directory name you used in step 1 as the mount point of the configuration file system. See Generating customization definitions for more information.
  5. Use the WebSphere Customization Tools to upload and run the augmentation job for each node. See Uploading and running customized jobs for more information.
  6. Start the deployment manager if it is not already started.
  7. Run the XDUpgrade command to copy the existing configuration to the new Version 6.1.1 cell as shown in the following example:
    XDUpgrade.sh -userID user_name -password user_password -sourceWasHome install_root/AppServer 
    -sourceProfilePath install_root/AppServer/profiles/default -targetProfilePath configuration_root/AppServer/profiles/default
    Note: You must run the XDUpgrade command from the configuration_root/AppServer/bin directory.

    After you run the XDUpgrade command, review the XDUpgrade.log and XDUpgrade.trace files in the configuration_root/AppServer/logs directory.

  8. Start each node.

What to do next

If your environment contains Compute Grid, migrate the parallel job manager.


The URL for this topic is: