Home
Dynamic Workload Console User's Guide
HCL Workload Automation Concepts
Conceptual information about HCL Workload Automation
Engine connections
You must define an engine connection to manage and monitor objects that run on a specific workstation in the HCL Workload Automation environment in the network.

Dynamic Workload Console User's Guide
- Getting Started
  Information about the Dynamic Workload Console installation and configuration.
- Running HCL Workload Automation from a mobile device
  Use your mobile device to easily and quickly interact with your HCL Workload Automation environment.
- Managing users and repositories
  How to configure, change, and share your settings repository and change the DB2 user. How to manage the user settings.
- Configuring High Availability
  How to configure, change, and share your settings repository.
- Customizing your console
  You can customize your console to have just the tasks that you want to access.
- HCL Workload Automation Concepts
  Conceptual information about HCL Workload Automation
  - Scheduling environment
    Main concepts that help you to understand what a scheduling environment is
  - Scheduling objects
    Scheduling objects that you can view and manage using the Dynamic Workload Console.
  - Production process
    Generating the HCL Workload Automation production plan.
  - Engine connections
    You must define an engine connection to manage and monitor objects that run on a specific workstation in the HCL Workload Automation environment in the network.
  - Event management
    What the event management feature is and how to use it.
  - Reports
    How to customize and generate HCL Workload Automation reports.
  - Workload service assurance
    Basic concepts about critical jobs and the critical path, which are fundamental to take advantage of this feature.
  - HCL Workload Automation for SAP
    Use HCL Workload Automation with SAP support
- Creating and Editing Objects
- Managing Workload Security
  Managing security settings in your environment by using Dynamic Workload Console.
- Changing user password in the plan
  How you change the user password in the plan.
- Monitoring your environment
- Working with Plans
  The main tasks that involve plans.
- Submitting Workload on Request in Production
  How you can insert jobs or job streams into your workflow at any time.
- Keeping track of changes
  How to keep track of changes in your environment
- Reporting
- Scenarios
  Scenarios demonstrating practical application of HCL Workload Automation in a business environment.
- Reference
  Reference information to perform the main tasks and activities from the Dynamic Workload Console.
- Glossary

Engine connections

You must define an engine connection to manage and monitor objects that run on a specific workstation in the HCL Workload Automation environment in the network.

To manage and monitor objects you must connect the Dynamic Workload Console to HCL Workload Automation distributed environments, z/OS environments, or both. You connect them by defining engine connections, and you can create as many engine connections as you need.

When you create a new connection, you must provide an engine name, the host name, and port number of the engine you want to connect to.

If you connect to a HCL Workload Automation for z/OS environment, the plan that you access is the current plan and the engine that you connect to is the controller workstation, which is the management hub of the HCL Workload Automation for z/OS environment.

If you connect to a HCL Workload Automation distributed environment, you can connect to:

The master domain manager workstation: A workstation acting as the management hub for the network. It manages all your scheduling objects. You can define and use different engine connections to the master domain manager, each accessing a different plan.
Backup master domain manager: A workstation that can act as a backup for the master domain manager when problems occur. It is a master domain manager, waiting to be activated. Its use is optional. This workstation must be installed as a master domain manager workstation.