Engine Mode

Each adTempus installation can operate in one of three Engine Modes: Primary, Agent + Standalone, or Agent-Only.

If you are not using the Distributed Scheduling features of adTempus, you will use Primary mode. If you are using Distributed Scheduling, you will have one Primary computer and one or more Agent computers.

The Engine Mode is selected during installation but can also be changed after installing using the Engine Mode editor.

In adTempus 4, there were separate Standalone and Master modes. These have been combined into Primary mode, and "Master" has been renamed "Controller."

Primary (Standalone / Controller)

In Primary mode, the server manages its own jobs. It can operate on its own (standalone) and can optionally function as a Controller for instances running in Agent mode when using Distributed Scheduling.

You can create links between jobs on different Primary instances using the Job Control Action , Job Execution Task, Job Condition, and Job Trigger.

Agent with Local Jobs

In Agent with Local Jobs mode, adTempus can run jobs sent to it by a Controller computer and can also be used just like a standalone adTempus installation: you can connect to it with the Console and define jobs that are managed locally and not controlled by the Controller.

When you connect to an Agent using the Console, you can view distributed jobs, but you cannot modify them. All changes to these jobs must be made on the Controller.

An Agent can only be the Agent for one Controller. Once a Controller has connected to an Agent, that Controller owns the Agent, and no other Controller can connect to it.

An adTempus that uses this mode requires a full adTempus license, not an agent license.

Agent Only

In Agent Only mode, all jobs are managed by the Controller. You cannot define local jobs.

An Agent can only be the Agent for one Controller. Once a Controller has connected to an Agent, that Controller owns the Agent, and no other Controller can connect to it.