Cisco Cisco Workload Automation 6.3 User Guide
132
Jobs and Job Groups
Overview
Job Hierarchy
Jobs are built on a hierarchy of job and job group ownership. A job group is a container for a set of jobs, usually part of
a common application or department. The job group has its own name and set of runtime instructions.
a common application or department. The job group has its own name and set of runtime instructions.
You can use job groups to submit jobs that either depend on each other, or should run together. For example, all the jobs
in payroll can belong to a group called Payroll. The job group can provide default settings to all the child jobs that belong
to it. Jobs and job groups are displayed in the Jobs pane. Job groups can save you the time it takes to set up job
definitions because each job in the job group can inherit the characteristics of that job group. When you want to create
several jobs with similar scheduling characteristics, you can define those jobs within a job group and set the scheduling
characteristics in the job group definition. It is also possible to change scheduling characteristics at the job level even
though the job belongs to a group.
in payroll can belong to a group called Payroll. The job group can provide default settings to all the child jobs that belong
to it. Jobs and job groups are displayed in the Jobs pane. Job groups can save you the time it takes to set up job
definitions because each job in the job group can inherit the characteristics of that job group. When you want to create
several jobs with similar scheduling characteristics, you can define those jobs within a job group and set the scheduling
characteristics in the job group definition. It is also possible to change scheduling characteristics at the job level even
though the job belongs to a group.
For example, if a job group is defined to run every Friday, then every job in that job group is automatically defined to run
on Friday. If one job in the job group must run on Saturday, then that one job can be changed to the proper run day without
affecting the other jobs — as long as you disinherit the job group calendar and change the calendar from within that job.
on Friday. If one job in the job group must run on Saturday, then that one job can be changed to the proper run day without
affecting the other jobs — as long as you disinherit the job group calendar and change the calendar from within that job.
The ultimate ownership of a job or job group belongs to either the user or a workgroup. A workgroup is a collection of
users who can share access to the same jobs. Workgroups are displayed in the Workgroups pane.
users who can share access to the same jobs. Workgroups are displayed in the Workgroups pane.
Job Groups and Inheritance
You can organize related jobs into groups. Using job group inheritance saves you time and reduces the possibility for
error by having jobs automatically inherit properties from the job group to which they belong. You need only change the
job properties that are unique to each job. For example, if a job group is defined to run every Friday, then each job that
belongs to the job group can inherit the job group’s calendar to run on Fridays as well. Note that when you schedule a
job group, every job in the group is scheduled as well, unless you choose not to inherit the calendar property.
error by having jobs automatically inherit properties from the job group to which they belong. You need only change the
job properties that are unique to each job. For example, if a job group is defined to run every Friday, then each job that
belongs to the job group can inherit the job group’s calendar to run on Fridays as well. Note that when you schedule a
job group, every job in the group is scheduled as well, unless you choose not to inherit the calendar property.
Note: If a job within a job group does not inherit the parent group’s calendar (the Inherited option on the job’s Schedule
tab is not selected), then the calendar assigned to the job must be a subset of the dates within the job group’s calendar.
In other words, the job’s calendar cannot contain any dates that are not part of the job group’s calendar.
tab is not selected), then the calendar assigned to the job must be a subset of the dates within the job group’s calendar.
In other words, the job’s calendar cannot contain any dates that are not part of the job group’s calendar.
Job Commands
Each job is assigned one command or script file. The command can be an executable file, a shell script, a batch file, a
command file or any other executable file available to the agent that will run the job. You can also specify parameters to
be passed to the command. This allows you to create different variations of a definition, based on the parameters that
you pass to it. You can even use system or user variables in the command name or parameters.
command file or any other executable file available to the agent that will run the job. You can also specify parameters to
be passed to the command. This allows you to create different variations of a definition, based on the parameters that
you pass to it. You can even use system or user variables in the command name or parameters.
Agents
You can choose which agent will run your job. You can run your job on a specific agent in your network or you can have
CWA pick an agent based on a list of agents called an agent list. By running jobs using an agent list, you can take
advantage of workload balancing, broadcasting and dynamic rerouting.
CWA pick an agent based on a list of agents called an agent list. By running jobs using an agent list, you can take
advantage of workload balancing, broadcasting and dynamic rerouting.