Migrating products from Version 6.1.0.5 to Version 6.1.1

You can migrate WebSphere® Virtual Enterprise for z/OS® and WebSphere Extended Deployment Compute Grid for z/OS from Version 6.1.0.5 to Version 6.1.1.

Before you begin

About this task

The process of migrating Virtual Enterprise and Compute Grid from Version 6.1.0.5 to Version 6.1.1 while maintaining the same version of WebSphere Application Server Network Deployment is known as an upgrade. To complete the following procedure successfully, upgrade your deployment manager first. Next, upgrade each on demand router (ODR) before you migrate your application servers.
Note: If WebSphere eXtreme Scale Version 6.1.0.x is configured in your environment, you must complete the steps to remove the product for the deployment manager and all other nodes in the cell. eXtreme Scale cannot remain in a node if you removed it from the deployment manager, because you would then not be able to synchronize the node with the deployment manager.

Procedure

  1. Mount the new product HFS for Version 6.1.1 in the /usr/lpp/zWebSphereXD/V6R1M1 directory.
  2. Enable access to the new Version 6.1.1 file system. Edit the server.policy file. You can use the policytool in the WAS_HOME/java/jre/bin directory to edit the policy file, or you can manually edit the policy file. If you choose to manually edit the file, set permissions for the deployment manager and all of the application server nodes.
    To set permissions for the deployment manager, add the following two lines to the server.policy file in the /WAS_config_root/DeploymentManager/profiles/default/properties directory:
    grant codeBase "file:/usr/lpp/zWebSphereXD/V6R1M1/lib/-" { permission java.security.AllPermission; };
    grant codeBase "file:/usr/lpp/zWebSphereXD/V6R1M1/-" { permission java.security.AllPermission; };
    To set permissions for each application server node, add the following two lines to the server.policy file in the /WAS_config_root/AppServer/profiles/default/properties directory:
    grant codeBase "file:/usr/lpp/zWebSphereXD/V6R1M1/lib/-" { permission java.security.AllPermission; };
    grant codeBase "file:/usr/lpp/zWebSphereXD/V6R1M1/-" { permission java.security.AllPermission; };
  3. Optional: Unaugment WebSphere eXtreme Scale Version 6.1.0.x from your current cell if the product already exists in your environment.
    1. Run the manageprofiles command individually for the deployment manager and each application server node as shown in the following examples:
      WAS_install_root/DeploymentManager/bin ./manageprofiles.sh -unaugment -profileName default -templatePath WAS_install_root/DeploymentManager/profileTemplates/wxddg_augment -ignoreStack
      WAS_install_root/AppServer/bin ./manageprofiles.sh -unaugment -profileName default -templatePath WAS_install_root/AppServer/profileTemplates/wxddg_augment -ignoreStack
      WAS_install_root/AppServer2/bin ./manageprofiles.sh -unaugment -profileName default -templatePath WAS_install_root/AppServer2/profileTemplates/wxddg_augment -ignoreStack
    2. Start the deployment manager.
    3. Run the syncNode command to synchronize each node as shown in the following examples:
      WAS_install_root/AppServer/bin ./syncNode.sh dmgrSystem dmgrPport -conntype soap -username user_name -password user_password
      WAS_install_root/AppServer2/bin ./syncNode.sh dmgrSystem dmgrPport -conntype soap -username user_name -password user_password
    4. Stop the deployment manager.
  4. Optional: Remove the eXtreme Scale links and directories from your current cell if the product already exists in your environment.
    1. Run the removeOG610 command for the deployment manager from the Version 6.1.1 install_root/bin directory as shown in the following example. If you customized Version 6.1.1 with intermediate links, the value of the install_root variable is the intermediate link directory string and not the actual installation root directory string.
      install_root/bin ./removeOG610.sh install_root /WAS_install_root/DeploymentManager user_name user_password
    2. Start the deployment manager.
    3. Run the removeOG610 command for each application server node from the Version 6.1.1 install_root/bin directory as shown in the following examples. If you customized Version 6.1.1 with intermediate links, the value of the install_root variable is the intermediate link directory string and not the actual installation root directory string.
      install_root/bin ./removeOG610.sh install_root /WAS_install_root/AppServer user_name user_password
      install_root/bin ./removeOG610.sh install_root /WAS_install_root/AppServer2 user_name user_password 
    4. Stop the deployment manager.
  5. Optional: If you are using intermediate links, run the following command to point an intermediate link to the Version 6.1.1 installation root.
    ln -s $installRoot $symlinkName
    Specify the Version 6.1.1 installation root as the value of the $installRoot variable, and specify the name of a new and unique directory as the value of the $symlinkName variable.
  6. Link Virtual Enterprise and Compute Grid and upgrade the products to Version 6.1.1.
    1. Run the upgradeVECG611 command for the deployment manager from the Version 6.1.1 install_root/bin directory as shown in the following example. If you customized Version 6.1.1 with intermediate links, the value of the install_root variable is the intermediate link directory string and not the actual installation root directory string.
      install_root/bin ./upgradeVECG611.sh install_root /WAS_install_root/DeploymentManager user_name user_password  
      Note: The values for the user_name and user_password parameters are passed directly.
    2. Start the deployment manager.
    3. Run the upgradeVECG611 command for each application server node from the Version 6.1.1 install_root/bin directory as shown in the following examples. If you customized Version 6.1.1 with intermediate links, the value of the install_root variable is the intermediate link directory string and not the actual installation root directory string.
      install_root/bin ./upgradeVECG611.sh install_root /WAS_install_root/AppServer user_name user_password  
      install_root/bin ./upgradeVECG611.sh install_root /WAS_install_root/AppServer2 user_name user_password  
      Note: The values for the user_name and user_password parameters are passed directly.
    4. Stop the deployment manager.
  7. Start your new Version 6.1.1 cell.