Versions Compared

Key

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

Table of Contents

Scope

Global is a keyword used before the name of the event to make the event accessible throughout the multiple JobScheduler with the same database. Once the Global Event is created we can use it as an In Condition and Out Condition of the same or different JobScheduler masters. 

Earlier if the event is created in one JobScheduler master then we can't use it in another JobScheduler master, that's why Global Event is introduced. Now, if Global Event has created in one JobScheduler master then multiple JobScheduler masters with the same database use this Global Event. If you want to automatic start one JobScheduler's jobs and job chains with the conditions of another JobScheduler master then we can use Global Events as an In and Out Conditions

How to create Global Events

For creating Global Event, in the Conditions Editor write the name of the event which you want to access globally and then select the Global Event checkbox to true for making the event global. Now, the event is ready to access in another JobScheduler.

Use Case

Create Global Event in one JobScheuler master and use it in another JobScheduler master

  • Here we are using JobScheduler master_01 and another JobScheduler master_02 uses the same database.
  • Create Global Event ( global:event1 ) in master_01 and uses it in master_02.
  • In JobScheduler master_01 create a Job Stream "js1" and job  "job11". 
  • In JobScheduler master_02 create a Job Stream "js2" and job  "job21". 

Explanation

  • Login to JOC Cockpit and switch to the Job Streams tab. 
  • Select the graphical view of the Job Stream.  
  • Drag and drop jobs and edit OutCondition of JobScheduler master_01 
  • In the Condition Editor Event List under Create Event write the name of the event you want to create and enable the Global Event  checkbox for making the event global 
  • Hit the Save and Submit button to apply the changes. 

        Image Added


  • If the job11 successfully executed then a Global Event is created. 

    Image Added



  • Now, in another JobScheduler master (JobScheduler ID: master_02)  add a global event as an In Condition of Job j21.

Image Added


  • In the In Condition's Condition Editor, add the global event as an in condition

    • Either write the expression, i.e. global:name_of_event
      For example: global:event1 


      Image Added


    • Or click on the pencil icon to add the In Condition of job21 in JobScheduler master_02.

      Image Added


  • Save and hit the Submit button to apply the changes. 

    Image Added


  • Now, add Out Condition for JobScheduler master_02. A job21 will be executed only if the Expressions of its In Condition will be evaluated to true. After successfully completed of job21 event2 of JobScheduler master_02 is created.

    Image Added



S.No. JobSchedulerJob NameConditionExpressionCommand






1.master_01job11In Condition--



Out Conditionrc:0global:event1






2.master_02job21In Conditionglobal:event1startjob: now



Out Conditionrc:0event2