Cisco Cisco Workload Automation 6.3 User Guide
311
Controlling Production
Resources in CWA
From the Navigator pane, select Definitions>Job Classes to display the Job Classes pane.
Resources in CWA
Jobs often require external resources to run to completion. The term, resources, can be used to refer to any physical or
virtual asset that is used during the processing of a job. This resource may be a piece of hardware such as a printer or
it may be software like a database. Agents and queues are also considered resources that are used during the processing
of a job. By officially designating an asset as a resource, the use of that resource can be quantified to limit how many
jobs can use it at once.
virtual asset that is used during the processing of a job. This resource may be a piece of hardware such as a printer or
it may be software like a database. Agents and queues are also considered resources that are used during the processing
of a job. By officially designating an asset as a resource, the use of that resource can be quantified to limit how many
jobs can use it at once.
It is important to remember that a resource can still be used in CWA even if it is not designated as a resource. Designating
something as a resource is just a more effective way to manage access to it. While multiple jobs can use the same
resource at the same time, a numerical limit is imposed on the resource during its definition to restrict access by
quantifying how much of the resource is available to each individual job.
something as a resource is just a more effective way to manage access to it. While multiple jobs can use the same
resource at the same time, a numerical limit is imposed on the resource during its definition to restrict access by
quantifying how much of the resource is available to each individual job.
While a job can still use an asset even if it is not specifically assigned to it, access management of that asset is bypassed.
The purpose of designating an asset as a resource is to prevent the resource from being overwhelmed by simultaneous
demand from multiple jobs and to impose order on the use of the resource. Once an asset is defined as a resource the
operator should ensure that the resource is assigned to all jobs that need that resource to ensure that proper
management of the resource is enforced. Jobs that use the resource without the constraints imposed by resource
management negate the benefits gained from this feature and receive the lowest priority for access.
The purpose of designating an asset as a resource is to prevent the resource from being overwhelmed by simultaneous
demand from multiple jobs and to impose order on the use of the resource. Once an asset is defined as a resource the
operator should ensure that the resource is assigned to all jobs that need that resource to ensure that proper
management of the resource is enforced. Jobs that use the resource without the constraints imposed by resource
management negate the benefits gained from this feature and receive the lowest priority for access.
If a resource is assigned to a job then that job cannot run without the resource. The resource is managed by imposing a
limit to the number of jobs that can simultaneously use it, ensuring a more efficient allocation of the resource. A job with
an assigned resource is guaranteed the use of that resource until the job completes. When the job runs, it locks up its
share of the resource so that no other job can use that portion of the resource until the job is done. When the job
completes, its share of the resource is released for other jobs to use. While a job can have multiple resources assigned
to it, the job cannot run until all of the resources assigned to it are available. None of the resources are locked up by the
job until all of the resources are available and the job can run. This “all or nothing” approach prevents resources from
being tied up needlessly if they cannot be used.
limit to the number of jobs that can simultaneously use it, ensuring a more efficient allocation of the resource. A job with
an assigned resource is guaranteed the use of that resource until the job completes. When the job runs, it locks up its
share of the resource so that no other job can use that portion of the resource until the job is done. When the job
completes, its share of the resource is released for other jobs to use. While a job can have multiple resources assigned
to it, the job cannot run until all of the resources assigned to it are available. None of the resources are locked up by the
job until all of the resources are available and the job can run. This “all or nothing” approach prevents resources from
being tied up needlessly if they cannot be used.
Note: If you assign a job class to a job group, all child jobs within that job group without an assigned job class are
automatically assigned the group’s job class.
automatically assigned the group’s job class.
System inefficiencies are created when too many jobs try to use a resource at the same time. Assigning a specific amount
of a defined quantity of a resource to each job ensures that the resource is not deluged with more work than it can handle.
Queues and dependencies can be used to control how many jobs access a resource at the same time but they are
insufficient in certain instances.
of a defined quantity of a resource to each job ensures that the resource is not deluged with more work than it can handle.
Queues and dependencies can be used to control how many jobs access a resource at the same time but they are
insufficient in certain instances.
Queues offer a way to manage access to a resource if the job does not require more than one resource to run to
completion. However, queues are ineffective at managing a job's access to a resource if the job requires more than one
resource as it processes. On the other hand, if variable dependencies are constructed to control the use of a resource
by a job, if the job rolls over to the next production day, then a situation arises where two copies of the job will be updating
the variable.
completion. However, queues are ineffective at managing a job's access to a resource if the job requires more than one
resource as it processes. On the other hand, if variable dependencies are constructed to control the use of a resource
by a job, if the job rolls over to the next production day, then a situation arises where two copies of the job will be updating
the variable.
When defining a resource, a limit or numeric quantity is specified. If the limit is one, then the resource is single-threaded
and only one job at a time can use it. If the limit is six then up to six jobs can use the resource at once. However, a job
may require multiple quantities of the resource at a time. For example, one job may require three licensed connections
to a database resource while another job needs two parts of the possible accesses to the resource. Even if a single use
is available it is possible that it may go unused even if jobs are waiting to use the resource because the other jobs may
require more than one access to the resource.
and only one job at a time can use it. If the limit is six then up to six jobs can use the resource at once. However, a job
may require multiple quantities of the resource at a time. For example, one job may require three licensed connections
to a database resource while another job needs two parts of the possible accesses to the resource. Even if a single use
is available it is possible that it may go unused even if jobs are waiting to use the resource because the other jobs may
require more than one access to the resource.
Resources Interface