Installing the HCL Workload Automation Agent

This chapter describes how to perform a first-time installation of the current version of HCL Workload Automation Agent (also known as z-centric agent).

You install this agent to run workload from the mainframe to distributed systems with a low cost of ownership.

Using this agent you can run your workload:
Statically
To run existing job types, for example scripts, on a specific HCL Workload Automation Agent. In this case, you install the HCL Workload Automation Agent on the distributed systems and connect it to the z/OS system through the HCL Workload Automation for Z controller.
Statically including job types with advanced options
In this case, you install the HCL Workload Automation Agent on the distributed systems adding the Java run time, and connect it to the z/OS system through the HCL Workload Automation for Z controller.
Dynamically
To run existing job types allowing the product to assign them to the workstation that best meets both the hardware and software requirements needed to run them. In this case, you install the HCL Workload Automation Agent on the distributed systems adding the dynamic capabilities, and connect it to the dynamic domain manager. For a detailed description about how to install a dynamic domain manager for a Z controller, see the HCL Workload Automation: Planning and Installation.

During the installation of the dynamic domain manager for a Z controller, you must provide the master domain manager and the HCL Workload Automation Netman port values, even if these values are not used in a z/OS lightweight end-to-end configuration because the fault-tolerant agent is not needed.

Dynamically including job types with advanced options
To run existing job types and job types with advanced options allowing the product to assign them to the workstation that best meets both the hardware and software requirements needed to run them. In this case, you install the HCL Workload Automation Agent on the distributed systems adding the dynamic capabilities and the Java run time, then connecting it to the dynamic domain manager. For a detailed description about how to install a dynamic domain manager for a Z controller, see the HCL Workload Automation: Planning and Installation.

During the installation of the dynamic domain manager for a Z controller, you must provide the master domain manager and the HCL Workload Automation Netman port values, even if these values are not used in a z/OS lightweight end-to-end configuration because the fault-tolerant agent is not needed.

For information how to use it, see Scheduling End-to-end with z-centric Capabilities.