Introduction
Every process needs a trigger to start the process. In JobStream Events are created with Out Conditions and can be used as In Conditions to trigger the next process. But is some scope for Events through which process can be executed.
Period for Event
The Events are available for 24 hours and periods start from 00:00:00 to 24:00:00 in UTC. After midnight the Events are automatically deleted from the JobStream.
FEATURE AVAILABILITY STARTING FROM RELEASE 1.13.4
The 24 hour period is configurable according to the needs and the working hours requirements. User can select the begin-time for the period.
Edit the scheduler.xml add the sos.jobstream_period_begin parameter for the start time of the period.
The syntax for parameter:
<param name="sos.jobstream_period_begin" value="09:00"/>
From the above parameter, the JobStream period begins from 09:00:00 to next-day 09:00:00.
Use-Cases
Within same JobStreams
The scope of events within the same JobStream exists until the period exists. The job creates an event when its Out Condition validates to true and this event can be used as an expression in the In Condition of other jobs within the same Job Streams for further execution. These events can be created and deleted from the Out Condition of any job within the same Job Stream. Once the event created, it gets consumed.
Example
Below is the example of events within the same JobStream:
Job Streams: jobstream1
No. | Job Name | Condition | Expression | Command / Event |
|---|---|---|---|---|
1. | job1 | In Condition | - | - |
Out Condition | rc:0 | job1 | ||
2. | job2 | In Condition | job1 | startjob: now |
Out Condition | rc:0 | job2 | ||
3. | job3 | In Condition | job2 | startjob: now |
Out Condition | rc:0 | job3 |
Within different JobStreams
The scope of events within different JobStreams also exists until the period exists. The job creates an event when its Out Condition validates to true and this event can be used as an expression in the In Condition of jobs from different Job Streams for further execution of jobs. These events can be created and deleted from the Out Condition of any job from the same or different Job Streams. Once the event created, it gets consumed.
Example
Below is the example of events within different Job Streams:
Job Streams: jobstream1 and jobstream2
No. | Job Stream | Job Name | Condition | Expression | Command / Event |
|---|---|---|---|---|---|
1. | jobstream1 | job1 | In Condition | - | - |
Out Condition | rc:0 | job1 | |||
2. | jobstream1 | job2 | In Condition | job1 | startjob: now |
Out Condition | rc:0 | job2 | |||
3. | jobstream2 | job1 | In Condition | jobstream1.job2 | startjob: now |
Out Condition | rc:0 | job1 |
Among different Masters
The scope of events among the different master is also called as Global events. The events are accessible in multiple JobScheduler within 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. To automatically start one JobScheduler's Workflow(JobStream) with the conditions of another JobScheduler master then we can use Global Events as an In and Out Conditions.
For Details review the Global Events article.
Within different Sessions
Feature availability from JobScheduler release 1.13.4.