This article is about methods that can be used with the JobScheduler for synchronizing the execution of jobs in different Job Chains.
See the How to Execute Jobs in a Job Chain in Parallel article for methods about executing parallel jobs within a job chain.
Using JITL Jobs for the Synchronization of Jobs in different Job Chains
Two JITL Jobs are available for configuring the parallel execution of Jobs in a Job Chain:
- The Splitter Job is used to divide processing of a main Job Chain into a number of child Job Chains. These child Job Chains are then processed in parallel.
- A Sync Job may be defined later in the main Job Chain to bring processing of these child Job Chains back to a single thread.
- The Splitter Job generates separate Orders for each of the parallel child Job Chains. The Splitter Job will then move processing of the main Job Chain to the Sync Job, if such a Job is defined later in the main Job Chain. The Sync Job will then wait for the Orders processing the parallel child Job Chains to be completed before continuing processing of the main Job Chain. See the Job Chains article for more information about the patterns that can be executed with the Splitter Job.
- The Sync Job is used to start or continue processing of a main Job Chain after one or more Jobs in different Job Chains have been executed.
- The following links provide further information and example download files demonstrating the use of the JITL Split and Sync jobs:
Alternative Methods for Configuring Dependencies Across Job Chains
Complex dependencies between jobs and orders across job chains can also be configured using:
- Backward dependencies:
- Event handlers to implement dependencies between job chains:
- For more information about configuring workflow dependencies see:
Examples in Detail