Execution Agent Machines

The Execution Agents/Machines view provides a list of Execution AgentClosed 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. machines and their associated Execution Queues. This can be helpful to see at a glance the machine that has been configured in the "machine" property of each Execution QueueClosed An Execution Queue identifies the system where a Job will run. The system is specified in the Execution Queue's Machine property. The system entered in this property must have an ActiveBatch Execution Agent installed on it. When a Job is associated to an Execution Queue, it will always run on the system specified in Machine property, unless a manual override is performed (for example, using an instance's "requeue" operation). The Machine property identifies the system where an Execution Agent has been installed, which is where jobs will run.

 

The Execution Queue's machine property supports entering a hostname, IP address, or published name (if using a Directory Service to publish Execution Agents). When using a published name, there is a checkbox on the Execution Queue's Properties sheet indicating as such (Active Directory Published Name). In addition, there is also a checkbox to indicate if a VM-aware Host License is being used. If using a Directory Service and/or VM-aware Host Licensing, the machine name in the Execution Agents/Machines view will append an "ad" and/or "vm" to the system identified in the queue's machine property (e.g. ad://10.70.1.20).

 

In the image below, you see the name of the Execution Agent systems, as identified in the Execution Queue's machine property. In this example, that includes Eng-FeatureTest, Localhost (2x) and 10.70.1.20. Beneath the machine name is the Execution Queue using the machine name, and its full path. It is possible to have more than one Execution Queue using the same machine. Lastly, this view provides you with the state of the queue, depicted in the icon to the left of the queue name (in this example, all the queues are started).