...
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 in parallel. This method is available for JobScheduler Versions 11.4 and newer and uses significantly less resources than synchronization.
...
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 JobScheduler can use a number of methods to synchronize the execution of jobs in different job chains.
Static Configuration
- JobSchedulerJobChainSplitter
- The Splitter Job is used to divide processing of a main Job Chain into a number of child Job Chains that are then processed in parallel.
- A Sync Job may be defined later in the 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 Chain. The Splitter Job will then move processing of the main Job Chain to a Join or Sync Job, if such a Job is defined later in the main Job Chain. See the Job Chains article for more information about the patterns that can be executed with the Splitter Job.
- JobSchedulerSynchronizeJobChains
- 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.
Static Configuration
- The following links provide further information and example download files demonstrating the use of the JITL Split and Sync For the static configuration of the parallel execution of jobs:Using 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:
- Use backward Backward dependencies:
- Event handlers to implement dependencies between job chains:
See also
- For more information about configuring workflow dependencies see:
...