Dependencies of job chains implemented by events
One Event handlers are one of the methods to implement dependencies between available for implementing dependencies between JobScheduler job chains is using event handlers. Whenever an event is created an entry is made into in the data base table scheduler_events database table. In the The event handler contains the conditions are defined to add that define whether an order is to be started for the a job chain to be startedwhen an event is detected.
Events are processed by a JobScheduler Instance. This could be a Supervisor JobScheduler if a Workload JobScheduler is registered with that instance otherwise the Workload JobScheduler is used.
Before events can be used the The event service has to be installed . It before events can be used. The event service is part of the JobScheduler installation if it has been configured within during the installation procedure.
The Event Service can also be installed in an existing JobScheduler instance. For more information see How to install the Event Service feature in JobScheduler.
The job chain scheduler_event_service job chain is running in run at predetermined intervals or whenever an event is created. The event service checks all
.xml data files in the
$SCHEDULER_DATA/config/events folder for information matching the active events which are stored in the scheduler_events database table . All job chains within the actual live folder may be concerned.
The event handler is a an
.xml data file which contains the definitions of the events and the commands which are to be triggered .
For each job chain started by events we need an action to be defined in the event handler. An action has the two parts:
In the command part the Order is defined to start the Job Chain as soon as the condition becomes
true. It is also possible to use the the add event command to create new events.