Table of Contents

Dependencies of job chains implemented by events

One of the methods to implement dependencies between  job chains is using an event handler. Whenever an event is created an entry is made into the data base table scheduler_events. In the event handler the conditions are defined to add an order for the job chain to be startet.

...

The  events can be monitored with  JID - JobScheduler Information Dashboard

Event service

Before events can be used the event service has to be installed. It is part of the JobScheduler installation if ordered within the installation procedure.

...

The job chain scheduler_event_service is running in predetermined intervals or whenever an event is created and checks all .xml data files in folder $SCHEDULER_DATA/config/events for information matching the active events which are stored in the data base table .  All job chains within the actual live folder may be concerned.

Event handler

The event handler is a  .xml data file which contains the definitions of the events and the commands which are triggered .

...

Every event which is used in the condition has to be deleted from the database with the command remove event.

Add events within job chains

Within the JobScheduler installation there is the JITL job sos.scheduler.job.JobSchedulerSubmitEventJob to store the event into the data base. Whenever an event is needed in a job chain a job using this JITL class is inserted. The needed event informations are transferred by parameters. Several  events can be submitted in one job.

Documentation

For more information about eventing see JobScheduler Events, Definition and Processing

...