Queues

This section discusses the Queue object, which includes the Execution and Generic Queues. Every Job must be associated with a Queue. The Queue determines which Execution Agent The Execution Agent ("Agent") is the component that runs ActiveBatch jobs. It must be installed and configured on a system that is specified in the Machine property of an Execution Queue object. The Job Scheduler uses the Queue's Machine property to determine what system to connect to in order to dispatch jobs. Most ActiveBatch environments have more than one system with an Agent installation. Which Agent to send the Job to is based on the Submission Queue that is assigned (associated) to each Job, a required Job property. system the job will run on. At least one Execution Queue is required so you can run jobs on the machine represented by that queue.

 

To create a Queue you must have “Create Queues” permission granted. This is a Scheduler-level security permission. You must also be granted "Create objects" permission on whatever container object you are adding the Queue to (Folder, Plan or Scheduler root). To Modify a queue you need “Read/Write/Modify” access permission for the Queue object. One property you cannot change is the Queue’s type (Execution or Generic).

 

In addition to user-created Execution and Generic Queues, this section also describes two built-in queues - OnDemand and RuntimeQueue.