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.
Before you begin
To start your deployment manager on a different system, your system must be running at the W502000 service level.Why and when to perform 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.
Steps for this task
Note: After initial configuration, if necessary, you can change the "Node host name," "ORB Listener host name" and "HTTP Transport host name" values in the Administrative Console.
Note: If you use "static" WLM ApplEnvs instead of Dynamic WLM Application Environments, do not specify the symbolic "&SYSNAME" for the node component of the ENV= string (<node_shortname> in the steps below).
Scenario 1: Root HFS is shared among all processors, deployment manager's configuration is in a configuration HFS on a system-generic mount point.
S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
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.
S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
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.
S <controller_procname>,JOBNAME=<jobname>, ENV=<cell_shortname>.<node_shortname>.<server_shortname>
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.