Scheduler

Overview

The scheduler is responsible for initiating execution of all operation lists as they are due. When the scheduler is disabled, operation lists will not run. Once the scheduler is enabled, operation lists that are marked as enabled will once again be able to run.

TIP: Note that in order to configure operation lists, operation lists must be disabled. This means that while the scheduler is off, all operation lists can be configured.

Toggling the scheduler

The scheduler can be enabled or disabled from the home page:

TIP: Operation lists that were meant to run during a time when the scheduler was off will not be run. It is important that operators keep note of any downtime of the scheduler, especially if it occurs when infrequent operation lists are due to run.


TIP: The scheduler defaults to "On" following a restart of the Event Broker service.

Scheduler states

The scheduler has three separate states:

State Purpose
Stopped The scheduler is off. In this state operation lists will not run.
Starting An intermediate step between stopped and started. In this state, only start-up Operation Lists will run. If a start-up operation fails the scheduler will not start.
Started The scheduler is on. Operation lists are able to be run by the scheduler.
ALERT: The scheduler will not move to the started state if a start-up operation fails.

Maintaining MIM Integrity

The starting state primarily serves as a means by which to prevent the target MIM instance(s) from becoming compromised by baselining before any delta processing or core MIM Event Broker functionality being performed.


A start-up operation list of used for baselining would generally contain a Full Import / Full Sync or Full Sync management agent operation.

Is this article helpful for you?