Distributed Scheduling Page

When you are using the Distributed Scheduling features of adTempus, the Distributed Scheduling settings for the Queue determine which computers the jobs assigned to the Queue will be executed on. If the server you are managing is not configured as a Distributed Scheduling Master computer, this page of the Queue's properties will not be available.

In adTempus version 2.x, Distributed Scheduling options were set individually for each job. Beginning with adTempus 3.0, these options are set at the Queue level to simplify job management.

Agent Mode

Select the mode adTempus should use when running the jobs in this Queue.

Limit the number of jobs from this queue that can run concurrently across all target computers

This option is only available if the Agent Mode is set to "Load Balance."

Use this option to limit the maximum number of jobs that can run concurrently in this Queue across all computers assigned to this Queue. For example, if the limit is set to "1," only one job at a time will run in this Queue, regardless of how many Agents are assigned to the Queue, or what limit has been set on the Queue page.

Run on Master

Check this option to run the job on the Master computer, in addition to any specified agents.

If you select the Slave or Mirror modes, the job will be run on the Master and on any specified agents. If no agents are specified, the job will run only on the Master.
If you specify the Load Balance mode, adTempus will consider the Master and all specified agents when determining which computer to run the job on.

Run on Remote Agents

Specify the Agents on which the job should run.

When you add or edit an agent, adTempus displays the Remote Execution Options window, which allows you to customize the way the job will be run on this agent.

Evaluate Conditions On

This option is only available if the Agent Mode is set to "Slave."

Use this option to specify where job-level conditions for the job should be evaluated (step-level conditions are always evaluated on the computer where the job is actually running).

Master: When the job is triggered, the Master computer evaluates the job-level conditions for the job. If the conditions are met, the execution command is sent to the Agent computers and the job is run. If the conditions are not met, the job is not run.
Slave: When the job is triggered, the Master computer sends the execution commands to the Agents. Each Agent then evaluates the conditions for the job and determines whether the run the job. Thus it is possible that the job will execute on some Agents but not on others.