Setting up a High Availability configuration to work with
multiple IBM Workload Scheduler for z/OS servers.
About this task
To set up a High Availability in a z/OS environment and distribute
the workload across multiple
Dynamic Workload Consoles
and multiple
IBM Workload Scheduler for z/OS servers,
perform the following procedure.
Procedure
- Install a IBM Workload Scheduler for z/OS connector sharing WebSphere Application Server with
an already installed Dynamic Workload Console.
Note: During the installation, use the same ports and the same
user names on each node.
- Create an engine on each IBM Workload Scheduler for z/OS connector,
using the same names (for example, ZCL1) and hostnames for all the
engines, but specifying different port numbers, to define connections
pointing to different IBM Workload Scheduler for z/OS servers
for the same controller.
- Open the TWA_home\wastools folder
and run the createZosEngine.sh (createZosEnginebat on
Windows) script to create the connection. For example, ./createZosEngine.sh
-name ZCL1 -hostName x.xxx.xxx.xx -portNumber 3446
- If you want to connect to multiple controllers,
repeat this operation using a different engine name to create additional
connections. As a result, the same set of engines is defined on each
connector, and all the engines use the same name and point to the
same controller, through a different server.
- From one of the Dynamic Workload Console instances,
create an engine connection specifying the Remote Server Name defined
in the IBM Workload Scheduler for z/OS connector (for
example, ZCL1), and the Host Name as local host, to
use the IBM Workload Scheduler for z/OS connector locally
installed with the Dynamic Workload Console.
Define an engine connection for each engine name defined in the step 4.
Results
As a result, the High Availability configuration will route
users to different
Dynamic Workload Console server,
while each
Dynamic Workload Console uses
the
IBM Workload Scheduler for z/OS connector locally
installed on the same
WebSphere Application Server and
a different
IBM Workload Scheduler for z/OS server.