[z/OS]

Starting deployment managers on a different MVS image

This describes steps you must follow to start your deployment manager on an MVS™ image different from the one on which it was originally configured.

About this task

The ability to start your deployment manager on an MVS image different from the one on which it was originally configured is handy if your original system becomes unavailable, either through a planned outage or a system failure. This way, you can still start and stop applications, make configuration updates, utilize monitors that use the PMI interface, perform other control functions, and so on. Perform the following steps to start your deployment manager on a different MVS image and ensure that client requests will successfully find the deployment manager at its new location.

Note: This works only if the deployment manager on the original MVS image is down. WebSphere® Application Server for z/OS® allows only one copy of the deployment manager to run at one time for any given cell.

Procedure

  1. Ensure that the MVS image to which you are moving the deployment manager contains a node that is already part of the cell of the deployment manager you want to move.
  2. Ensure that the location service daemon on the MVS image to which you are moving the deployment manager is up and running before you move the deployment manager.
  3. Using the Profile Management Tool or zpmt command, set your host names and ports appropriately:
    • Ensure that the host names and ports for the deployment manager are not specific to a particular system.
    • Ensure that you use a DVIPA generic host name, rather than a system-specific host name, for the node host name and an asterisk ("*") for both the ORB listener IP address and HTTP transport IP address.
    • Consider configuring a secondary DVIPA in case the system with the primary VIPA is down.
  4. Ensure that Sysplex Distributor is enabled so that, regardless of where the DVIPA has moved, it automatically routes any inbound traffic to the deployment manager.
  5. Ensure that access to the PROCLIB is the same for both the original MVS image and the MVS image to which you want to move the deployment manager.
  6. Start the deployment manager on the new system.

    There are three ways to accomplish this, depending on the configuration of your HFSs. Follow the scenario that matches your configuration.

    • Scenario 1: Root HFS is shared among all processors, deployment manager's configuration is in a configuration HFS on a system-generic mount point.
      Issue the start command for the deployment manager on the system on which you want it to reside:
      • To start the server in 31-bit mode:
        S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
      • To start the server in 64-bit mode:
        S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>,AMODE=64
    • Scenario 2: Root HFS is shared among all processors, deployment manager's configuration HFS is mounted under a system-specific directory.
      Note: This is an undesirable scenario that you should try to avoid from the start of your system configuration. If you find yourself with this setup, however, follow these steps for the workaround.
      1. Create a symbolic link at the equivalent system-specific location on the target MVS image. The contents of the symbolic link should point back to the actual mount point, which means you should not use $SYSNAME anywhere.
      2. Issue the start command for the deployment manager on the system on which you want it to reside:
        • To start the server in 31-bit mode:
          S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
        • To start the server in 64-bit mode:
          S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>,AMODE=64
    • Scenario 3: Root HFS is not shared among any processors, deployment manager's configuration HFS is mounted and accessible to only one system at a time.
      1. Unmount the configuration HFS from the original MVS image and remount it (at a mount point with the same name) on the new MVS image.
      2. Issue the start command for the deployment manager on the system on which you want it to reside:
        • To start the server in 31-bit mode:
          S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
        • To start the server in 64-bit mode:
          S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>,AMODE=64

Results

You know you are done when your deployment manager is up and running on a different MVS image and you are able to use it to make configuration updates to your environment.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-zos&topic=tins_dmstartdiff
File name: tins_dmstartdiff.html