Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Dependencies of job chains implemented by events

 

One of the methods to implement dependencies between  job chains is using an event handlerhandlers. 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.

Events are processed by a Job Scheduler Supervisor Instance.  If the JobScheduler is not registered with a supervisor,  the current JobScheduler is used.

 

Notice that the event service will not work with data base H2.

...

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

...

Handling events within job chains

Within 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-) to submit an event.The event is then submitted to the supervisor. If the JobScheduler is not registered with a supervisor, the event is submitted to the current JobScheduler. The event can be configured using job and/or order parameters. All other parameters are treated as event parameters. For shell jobs the bin/jobscheduler_event.sh script has to be used instead of the monitor.   

       

  • JobSchedulerSubmitEventJob
    • JobSchedulerSubmitEventJob can be configured  to submit an event.The event is then submitted to the Job Scheduler configured with scheduler_event_handler_host and scheduler_event_handler_port or else to the supervisor. If the Job Scheduler is not registered with a supervisor, the event is submitted to the current Job Scheduler. The event can be configured using job and/or order parameters  All other parameters are treated as event parameters.

  • JobSchedulerDequeueEventsJob
    • During job execution in a Job Scheduler Workload instance events could be created that should be processed by a Job Scheduler Supervisor Instance. Therefore event handlers are configured in the Supervisor that implement individual conditions  that state to which events should be reacted, e.g. by starting other jobs and job chains. 
         
  • JobSchedulerExistsEventJob
    • During job execution in a JobScheduler Workload instance events could be created that should be processed by a JobScheduler Supervisor Instance. This job checks if certain events 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.   

  • JobSchedulerEventJob
    • During job execution in a Job Scheduler Workload instance events could be created that should be processed by a Job Scheduler Supervisor Instance. Therefore event handlers are configured in the Supervisor that implement individual conditions that state to which events should be reacted, e.g. by starting other jobs and job chains.     

  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

...