Home
HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
Scheduling End-to-end with z-centric Capabilities
Customizing the HTTP connections
The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
Customizing the http timeout on the Dynamic Workload Console
You can increase the length of the HTTP connection timeout in the Dynamic Workload Console to allow more time for retrieving objects related to the z-centric environment.

HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
- Customization and Tuning
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
  - About this publication
  - Configuring
  - Customizing the HTTP connections
    The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
    - Customizing HTTP connection with HTTPOPTS statement
      HTTPOPTS statement to customize HTTP connection.
    - Customizing the http timeout on the Dynamic Workload Console
      You can increase the length of the HTTP connection timeout in the Dynamic Workload Console to allow more time for retrieving objects related to the z-centric environment.
    - Configuring the heartbeat checking interval for z-centric agents and dynamic domain managers
    - Configuring the connection between the z-centric agent and controller through a proxy
      You can configure that one or more z-centric agents connect with the controller through a proxy server, by defining the proxy properties in the ROUTOPTS statement and JobManager.ini file.
    - Starting and stopping HTTP subtasks
      An HTTP Server subtask and an HTTP Client subtask run the transmission of data between the scheduler and the HCL Workload Automation Agents on the distributed side. These subtasks automatically start at controller startup.
  - Defining user IDs and passwords with the USRREC statement
    Use the USRREC initialization statement to define the passwords for the users who need to schedule jobs to run on Windows™ workstations. You do not need to do this if you run native job types on non-Windows workstations.
  - Defining variables and passwords for local resolution
  - Defining and managing HCL Workload Automation Agent workstations in the database
    After defining the destinations of your HCL Workload Automation Agents, you need to define the HCL Workload Automation Agents as HCL Workload Automation for Z computer automatic workstations.
  - Defining and managing dynamic workstations
    When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
  - Setting the security features
  - Defining and managing jobs
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Monitoring and recovering jobs
  - Running a script when a job completes
  - Viewing the job logs from the host
    An overview on how to view or retrieve the job logs issued in the z-centric environment and how to attach a header with job run information on top of each log.
  - Troubleshooting
    Troubleshooting agent problems
  - Configuring to schedule J2EE jobs
  - Security order of precedence used for the execution of J2EE tasks
  - Configure to schedule job types with advanced options
  - Managing return codes
  - Collecting job metrics
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Customizing the HTTP timeout on the Dynamic Workload Console

You can increase the length of the HTTP connection timeout in the Dynamic Workload Console to allow more time for retrieving objects related to the z-centric environment.

If you find that you get message errors, such as:

AWSJZC019E A communication error has occurred with HCL Workload Automation for Z.
The connection wait has exceeded the timeout of  "30,000" milliseconds...

when you try to retrieve z-centric objects from the z/OS engine on the Dynamic Workload Console, this implies that the HTTP/HTTPS connections within your z-centric environment might be suffering or that some of your plug-in applications require longer than expected.

To mitigate this problem you can increase the timeout allowed on the Dynamic Workload Console when receiving data from the HCL Workload Automation for Z controller.

To do so, set the zosHttpTimeout option of the TdwcGlobalSettings.xml file that configures the global settings of the Dynamic Workload Console.

If the option is not set, it takes the default value of 30,000 milliseconds (ms), which is probably not enough to fulfill your requirements. In this case, add the option in TdwcGlobalSettings.xml and set a value larger than 30,000 ms (for example, 90,0000 ms).

For additional information, see the Dynamic Workload Console User's Guide.