Inclusive and exclusive rule-based run cycles
This scenario shows how a HCL Workload Automation administrator can use subsets of run cycles in a run cycle group to achieve a specific workload schedule that, without the use of a run cycle group, would require the definition of numerous run cycles, calendars, or both. In addition, it demonstrates how you can reuse run cycle groups in different job streams and add an offset to shift a workload schedule forward by one day.
Scenario goal
In this scenario, a HCL Workload Automation administrator needs to run a process that elaborates sales projections every day except Friday, and on the first day of each month; in the latter case, it must run even if the first day of the month is a Friday. The administrator must then run a post-sales check according to the same schedule but a day later.
Business Scenario
To define the required workload schedule, the HCL Workload Automation administrator creates a run cycle group with two subsets. The first subset defines that the process must run every day except Fridays, and the second subset defines that the process must run on the first day of each month, even if the first day of the month is a Friday. The same run cycle group is reused in a different job stream to run a post-sales check, however, this job stream should follow the same schedule as the sales projections, but one day later.
Roles
This section lists the user roles needed to run the scenario:
- HCL Workload Automation Developer
- Defines the run cycle groups in a job stream.
- HCL Workload Automation Job Scheduler
- Manages HCL Workload Automation workload by submitting and monitoring jobs.
Software Requirements
- HCL Workload Automation version 9.1.
- Dynamic Workload Console version 9.1.
Setting up the environment
To run this scenario you must install or upgrade to HCL Workload Automation version 9.1.
Running the Scenario
To complete the scenario, perform the following steps: