Cisco Cisco Workload Automation 6.3 User Guide

Page of 412
321
 
Controlling Production
Queues in CWA
Successive Compounding of Child Filters
When jobs are assigned to queues, they pass through each parent filter before they reach their destination queue. The 
job in the destination queue therefore meets all the criteria of the destination queue’s filter plus each of its parent’s and 
grandparent’s queue filters. During the search for the right queue to assign to a job, each successive queue filter acts 
using AND logic, further narrowing down which queue will become its destination queue.
Assigning Jobs to Specific Queues 
You cannot directly assign a job to a queue. However, you can configure your definitions to consistently assign jobs to 
run in specific queues. CWA is designed with intelligent queue software that determines the best queue based on each 
job’s properties. Once the queue structure has been set up for your business cases, jobs will automatically enter the 
appropriate queue. For details on how to send a job to a specific queue, see 
Guidelines for Creating Queues
The following are a set of guidelines to help you create queues that meet your scheduling needs. These guidelines are 
suggestions, not requirements. The way your queue hierarchy is structured is entirely up to you.
Queue Names —Use queue names that define what the queue is used for. A queue named Manufacturing Jobs 
makes more sense than a queue named A1.
Queue Hierarchies and Queue Filters —Hierarchies, combined with queue filters let you create specific queues for 
specific types of jobs, giving you more task management control. Hierarchies also help you avoid mistakes by visually 
organizing how jobs run in the overall schedule. For example, you could have each queue parent only accept jobs of 
a particular class. You could then subdivide child queues by having each accept jobs that are owned by a particular 
workgroup or user.
Child Queue Priority Levels —Give all sibling queues under the same parent different priority levels, otherwise the 
queues are selected randomly when a job is assigned.
Job Limits and Queue Limits —The settings that control the number of jobs that run on a machine or network are 
the agent’s job limit and the queue’s queue limit. Consider these limits carefully. Though the system queue limit 
controls how many jobs can run overall at any one time, make sure it is large enough to accommodate the sum of 
all the agents’ job limit values.
You could set queues in hierarchies with limits reflecting the maximum acceptable load for the queue, and then 
regulate the entire system load by setting the system queue limit to a percentage of its maximum. 
For example, suppose the system queue has three child queues only, Queue A, Queue B, and Queue C with a queue 
limit of 10 each. Thus, the maximum possible load is 30 jobs. However, you could set the system queue with a limit 
of 20, 66% of maximum, and only 20 jobs will run at one time, but the underlying queue functionality is the same. In 
effect, you decrease (or increase) your scheduling load with one control.
Hours Available —You can submit jobs that do not need to be run immediately to a queue that is set to operate after 
hours. An example is to use this option to free up resources during the day.
When the time comes to operate, the jobs begin to run. When the queue closes, it continues to finish jobs that are 
being run, and halts all waiting jobs until the next time it is open.
Launch Immediately —Create one or two queues with the launch immediately queue option for those emergency 
situations where a user absolutely needs a job to run as fast as possible. You will be able to use this for manually 
overriding a given assignment or for queue bumping.
Queue Bumping —Add queue bumping for queues where some jobs never launch or wait too long to launch. The 
queue that is bumped to should have a higher priority than the previous queue, or the jobs may wait even longer to 
start.