WebSphere Extended Deployment Compute Grid, Version 6.1.1
             Operating Systems: z/OS


This topic applies only on the z/OS operating system.

Migrating the WebSphere Extended Deployment Compute Grid parallel job manager

You can migrate the parallel job manager from WebSphere® Extended Deployment Compute Grid Version 6.1.0.5 to WebSphere Extended Deployment Compute Grid Version 6.1.1.

Before you begin

Before you can migrate the parallel job manager from Version 6.1.0.5 to Version 6.1.1, ensure that you meet the following prerequisites:
  1. The steps for the upgrade scenario or the standard migration scenario have been completed.
  2. TheCompute Grid Version 6.1.0.5 parallel job manager application is installed and configured.

Procedure

  1. Update the parallel job manager DB2 tables by using MIGPJM as the SPUFI input. The SPUFI input you need is in the /usr/lpp/zWebSphereXD/V6R1M1/longRunning/MIGPJM directory.
    Note: Updates for other databases, for example Derby, are not currently available.
  2. Uninstall the Compute Grid Version 6.1.0.5 parallel job manager. Run the parallelJobManager.py script from the WAS_install_root/DeploymentManager/bin directory. For example, to remove a parallel job manager application, run the following command:
    ./wsadmin.sh -lang jython -f parallelJobManager.py -remove 
    -cluster clustername_of_endpoint -user user_id 
    -password user_password
    See the parallelJobManager.py script topic in the Reference section of the Information Center for additional script information.
  3. Install a Compute Grid Version 6.1.1 parallel job manager application. Run the parallelJobManager.py script from the WAS_install_root/DeploymentManager/bin directory. For example, to install a schema named PJSCHEMA, run the following command:
    ./wsadmin.sh -lang jython -f parallelJobManager.py -install 
    -cluster clustername_of_endpoint -backend db2_back_end 
    -schema PJSCHEMA -user user_id -password user_password
    See the parallelJobManager.py script topic in the Reference section of the Information Center for additional script information.
  4. Verify in the parallel job manager datasource for DB2 that the currentSQLID custom property is set to the schema name you chose for the parallel job manager tables.
  5. Restart the servers on the clusters where you installed the parallel job manager.

Results

The parallel job manager is upgraded to Version 6.1.1.

What to do next

You can submit verification jobs.




Related information
Migrating to a Version 6.1.1 and Version 7.0.x cell
Migrating products from Version 6.1.0.5 to Version 6.1.1
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 1:36:22 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp?topic=/com.ibm.websphere.gridmgr.doc/info/migration/tzmigcgpjm.html