HCL Workload Automation, Version 9.4

A sample business scenario

To avoid unexpected slowing down in the workload processing, the analyst of a big company needs weekly reports collecting historical information about the processed workload to determine and analyze any workload peaks that might occur.

To satisfy this request, the TWSWEBUIDeveloper creates Workload Workstation Summary Reports (WWS) and Workload Workstation Runtimes Reports (WWR).

To accomplish his task, he runs the following steps:
  1. He customizes the property files related to the Workload Workstation Summary and Workload Workstation Runtimes reports, specifying the format and content of the report output.
  2. He schedules jobs to obtain WWS and WWR reports:
    • The first job generates a WWS report to be saved locally.
    • The second job runs a WWR report overnight on expected workload peaks time frames. The report output is sent using an mail to the analyst. The information collected are used to optimize the workload balance on the systems.
  3. He adds the two jobs to a job stream scheduled to run weekly and generates the plan.