Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 29

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 30

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Title change to 'example' form

Table of Contents
outlinh1. true
outlinh1. true
1printablefalse
2stylh1. none
3indent20px

Introduction to events

  • My JobChainA starts at morning 08:00 AM and should finish processing within 2 hours.
  • My JobChainB starts at morning 10:15 AM , but JobChainB can only be started when JobChainA has successfully ended processing.

...

  1. JobChainA contains 3 job nodes, i.e. TaskA1,TaskA2,TaskA3
  2. JobChainA contains 1 job node, i.e. Submit_End_Event, which will send an EVENT notification to JobScheduler that job has finished.
  3. JobChainB also contains 3 job nodes i.e. TaskB1,TaskB2,TaskB3
    • JobChainB contains 1 job node i.e. Check_End_Event, which will check if required EVENT notification is present in the JobScheduler databae and contains 1 job node i.e. Remove_End_Event which will remove the events from JobScheduler database.
    • JobChainB will wait for JobChainA to complete successfully.

Requirements

  • The JobScheduler must run using a database.
  • Events are stored permanently in the table SCHEDULER_EVENTS.
  • The JobScheduler must be installed with the Event Service (job Chain sos/events/scheduler_event_service)

Instructions

  • Unzip all files of DEP_EVENTS.zip - job configuration files into the ./confi/live folder of your active instance of the Event Service JobScheduler installation. After unzipping you will have all the objects needed to run the example in the live/DEP_EVENTS subfolder.
  • Open JOC for the Workload JobScheduler in your browser using http://scheduler_host:scheduler_port
  • Find the DEP_EVENTS/JobChainB/JobChainB job chain and click on it.
  • There is an order assigned to the JobChainB. In the order menu press Start order now
  • You see the order will start, but since the JobChainA is not yet started, thus JOB_CHAINA_END event does not exist, the order will wait for 10s and then check again.
  • Find the DEP_EVENTS/JobChainA/JobChainA job chain and click on it.
  • There is an order assigned to the JobChainA. In the order menu press Start order now
  • JobChainA will start and after successful completion will submit JOB_CHAINA_END event to the JobScheduler.
  • JobChainB node CheckEvent is checking periodically, as soon as it finds the matching event, JobChainB will also start processing.
  • JobChainB has a node RemoveEvent to remove the event from the database once JobChainB successfully completed processing.

How it works

The DEP_EVENTS/JobChainA/JobChainA/Submit_End_Event job is a JobScheduler job to check if the required event exists in the JobScheduler database.

...

  • The DEP_EVENTS/JobChainB/JobChainB/Remove_End_Event RemoveEvents step node will only be executed if all the successor job node are executed succesfully. If JobChainB needs to be restarted due to an error, then the prerequisite event will be present there This step executes the DEP_EVENTS/JobChainB/JobChainB/Remove_End_Event job to delete desired event.
  • If the event is not raised, the order executes a setback. The wait time between two checks is configured in the delay_order_after_setback definition of the job (and the job chain node).
  • After adding the event, the order will proceed with the next step and the event will be removed.

Related Downloads