Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
Planning and Installation
Planning
Network planning
Network planning on HCL Workload Automation.
Planning the environment
Typical installation scenarios for products and components.

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
- Planning and Installation
  - Planning
    - Network planning
      Network planning on HCL Workload Automation.
      - HCL Workload Automation environment
        An HCL Workload Automation network consists of a set of linked workstations on which you perform job processing. A network is composed of one or more domains, each having a domain manager workstation acting as a management hub, and one or more agent workstations.
      - Planning the environment
        Typical installation scenarios for products and components.
        Distributed workload environment with static scheduling capabilities
        Configuration to run workload statically across your distributed network.
        Distributed workload environment with dynamic scheduling capabilities
        Use this configuration to run workload dynamically across your distributed network.
        Distributed workload environment with static and dynamic scheduling capabilities
        Use this configuration to run workload both statically and dynamically across your distributed network.
        End-to-end workload environment
        In an end-to-end workload environment (agent connected to the z/OS® system), you can define different types of configurations.
        Workload environment integrated with external systems
        Configuration to extend HCL Workload Automation capabilities for scheduling on external applications.
        Distributed-driven workload environment for z/OS®
        Configuration used when submitting from the HCL Workload Automation.
        Dockerized environment
        Use this configuration to implement a Dockerized environment.
      - Planning domains
        A HCL Workload Automation network contains at least one master domain manager that acts as a management hub for the product. Additional domains can be used to divide a widely-distributed network into locally-managed groups of workstations.
      - Workstation classes
        Workstations are organized into domains to make your network management easier and more efficient. However, the domain name is not one of the selection criteria when choosing where to run a job or job stream.
      - Time zone considerations
        Time zone support is an optional feature that is enabled by default.
    - Installation considerations
      Some considerations that need to be taken into account before installation.
  - Installing HCL Workload Automation
    Available installation methods
  - Configuring
    Configuring HCL Workload Automation components after installation.
  - Upgrading
    How to upgrade HCL Workload Automation to the current version.
  - Moving from on-premises to cloud
    A quick procedure to move your workload from an on-premises to a cloud environment
  - Troubleshooting installation, migration, and uninstallation
    An overview on troubleshooting installation, migration, and uninstallation of the HCL Workload Automation.
  - Uninstalling
    An overview on how to uninstall the product.
  - Reference
- User's Guide and Reference
- Administration Guide
- Scheduling with the Agent for z/OS
- Database Views
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

Planning the environment

Typical installation scenarios for products and components.

These typical scenarios for HCL Workload Automation show how to deploy specific solutions on the minimum possible system resources.