An Application consists of workload objects. Workload objects represent the work to be scheduled. Workload objects include jobs that execute programs such as Windows commands, UNIX scripts, and SAP ABAPs, objects that monitor for conditions such as file activity and triggering of SAP events, and objects that run on CA Workload Automation DE such as links and tasks.
To define a workload object, you need to identify the following:
The parameters (job details) of a workload object are the required and optional properties of that workload object. For example, Windows jobs require a command file, and UNIX jobs require a script name or command name.
Optional parameters may include user IDs, arguments, and environment variables. Most workload objects can contain time dependencies, notifications, resource requirements, and other options.
You specify when a workload object runs (or does not run) using schedule criteria. When an Application is generated, the run frequency determines whether the job is selected to run.
You can add a single run-frequency condition or create a list of conditions specifying when the workload object runs or does not run.
A workload object may have predecessors and successors. By default, a workload object does not run until its predecessors complete successfully and its other dependencies (time and resources) are met. When a workload object completes successfully, it releases its successors, which run after all their dependencies are met.
You specify a workload object's relationship with other workload objects using predecessor dependencies. You can create predecessor dependencies between jobs in the same Application or jobs in different Applications.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|