| Table of Contents |
|---|
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. Whenever an event is using an event handler.
Event service
created an entry is made in the scheduler_events database table. The event handler contains the conditions that define whether an order is to be started for a job chain when 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.
The events can be monitored with the JOC Cockpit web interface, which replaces the JID - JobScheduler Information Dashboard interface, which is deprecated as of JobScheduler Release 1.12.0.
Event Service
The Before events can be used the event service has to be installed . It before events can be used. The event service is part of the JobScheduler installation if ordered within it has been configured 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 The job chain scheduler_event_service job chain is running in run at predetermined intervals or whenever an event is created and . The event service checks all .xml data files in folder the $SCHEDULER_DATA//config/events folder for information matching the active events which are stored in the data base table . scheduler_events database table . All job chains within the actual live folder may be concerned.
Event handler
The event handler is 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:
- Events ("if-clause")
- Command ("then-clause")
An event is uniquely defined by event class and event ID. Together with and/or/not the events of a group are combined to the condition.
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 add event command to create new events.
Every event which is used in the condition has to be deleted from the database with the remove event command .
Handling events in jobs / job chains
As part of the JobScheduler installation there are some Java classes to handle events:
- JobSchedulerSubmitEventTaskAfterMonitor
- JobSchedulerSubmitEventMonitor can be configured as a monitor for (not shell-) jobs to submit an event.
- JobSchedulerSubmitEventMonitor can be configured as a monitor for (not shell-) jobs to submit an event.
- JobSchedulerSubmitEventJob
- JobSchedulerSubmitEventJob can be configured to submit an event.
- JobSchedulerSubmitEventJob can be configured to submit an event.
- JobSchedulerDequeueEventsJob
- Dequeues Events. This job is triggered by orders or by standard job starts.
- Dequeues Events. This job is triggered by orders or by standard job starts.
- JobSchedulerExistsEventJob
- This job checks if certain event exists. The job processes orders which are configured with an event specification. Depending on whether these events exist or not the order will be put into the next_state or into the error_state.
- This job checks if certain event exists. The job processes orders which are configured with an event specification. Depending on whether these events exist or not the order will be put into the next_state or into the error_state.
- JobSchedulerCheckEvents
- Check if events exist. This job is executed order driven.
- Check if events exist. This job is executed order driven.
- JobSchedulerEventJob
- Process events. This job is executed order driven
Documentation
For more information about eventing see the reference guide JobScheduler Events, Definition and Processing