Distributed Scheduling Setup and Administration

Once the adTempus software is installed and running on the Controller and Agent computers (see the Distributed Scheduling Installation topic), you are ready to begin configuring and managing Distributed Scheduling jobs.

All Distributed Scheduling configuration is performed through the Controller computer, so you should start the adTempus Console and connect to the Controller.

Defining Agents

The first step in Distributed Scheduling setup is to tell the Controller about the Agents that you want it to manage. Before you proceed, make sure the adTempus software is installed on the Agent computers.

Next, go to the Remote Agents folder in the Console and add a new Remote Agent definition for each of the Agent computers you want to manage from this Controller.

Note that a Controller can control any number of Agents, but each Agent can belong to only one Controller. Once a Controller has connected to an Agent, the Agent will not accept connections from any other Controllers unless you reset the agent's Controller using the Engine Mode editor.

Configuring Queues

Once you have defined your Remote Agents, you can begin assigning them to Queues. See the Distributed Scheduling Page of the Queue properties for more information on configuring Queues for Distributed Scheduling, and the Mirror jobs to Remote Agents topic for a setup example.

Configuring Jobs

Once a Queue is configured for Distributed Scheduling, any Job assigned to that Queue is executed according to the Queue's Distributed Scheduling settings. You do not need to change any settings in the job itself to make it use Distributed Scheduling.

All changes you make to the job will be sent to the Agents as necessary.

However, you should review each Distributed Job's settings to make sure that the job will execute properly on all computers assigned to the Queue.

• Any programs, batch files, etc., run by the Job must be installed and configured on each computer.
• The user account used for the job must be valid on each computer.
• Any file paths must be the same on all computers, or you must use Job Variables to ensure that the correct path is used for each Agent. See the discussion in the Remote Agent Job Variables topic for more information.

Administering Distributed Jobs

The following tools in the Jobs View of the Console will help you administer distributed jobs.

• When you select a job, an "Agents" tab is available at the bottom of the view. This tab shows the job's status for each agent that it targets. From this agent list you can also manually run a job on a specific agent only.
• The History and Job Log tabs for a job list instances and events for all agents, and indicate which computer each instance is executing on.
• If you want to manually start a job on the Controller or on all Agents, select the job from the Job List and use the Run command from the pop-up menu.
• If you want to manually start a job only on one particular Agent, select the job, then go to the Agents tab and select the desired Agent. Right-click the agent name and select theRuncommand from the pop-up menu.