The primary purpose of the Scheduler is automatic non-interactive execution of actions according to a user-defined time schedule.
To run, a scheduled job requires the following:
| • | Context mask that matches the contexts from which the action will be executed |
| • | Name of an action to execute |
| • | Any input parameter(s) required for the action |
| • | At least one trigger to determine when the action is executed |
The scheduler stores its internal state persistently. This means that when the server is restarted, the scheduler can detect if any scheduled jobs were missed (not launched) while the server was down.
The Scheduler executes actions in headless (non-interactive) mode. Actions that don't support non-interactive execution cannot be scheduled.
Basic properties of a scheduled job are described here.
|
Every user has his own set of Scheduled Jobs. |
|
Related tutorials: |
Administering Scheduler
Two contexts are used to administer scheduled jobs: One is the general Scheduled Jobs context, which serves as a container. The other is the Scheduled Job context, which holds the information for one scheduled action. |
|
Built-In Scheduled Jobs
Several scheduled jobs are built into AggreGate Server and appear under default administrator's user account:
| • | Check Incoming Mail. This scheduled job is used by AggreGate Server to fetch mail from incoming mail server. It is necessary for acknowledging alerts by email. |
| • | Remove Expired Events. This scheduled job is responsible for periodic removal of expired events from event history. It's not recommended to delete or reconfigure it. |