| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
General
JobChain contains 4 jobs i.e. Job01, Job02, Job03 and Job04. Job04 can only be started when Job01,Job02,Job03.
Order will start with split node first node of the chain, split node uses JobScheduler JITL job JobChainSplitter. Splitter job starts all the nodes(Jobs) configured as next node for Split node i.e. Job01, Job02 and Job03 will be started in parallel and Split node notify Sync node about Tasks(Jobs) it should wait before proceeding in the JobChain. Once all the three nodes(Jobs) finishes processing sync node will continue with processing and Job04 will be started.
JOE diagram of JobChain
...
Job Chain Dependencies
JobScheduler can handle different types of dependencies at job chain level, job level, task level and order level.
Some use cases for such dependencies are:
- JobC can only be started after JobA and JobB successfully ended.
- JobB on ServerB can only be started after JobA on ServerB finished.
- JobC should not be started if JobA is running
JobScheduler can manage complex dependencies using a variety of built-in features such as:
- Locks
- Split and Sync
- Event Handling
- API jobs
- Preprocessing
- Post-processing
Different Scenarios
- How to wait for parallel predecessor jobs to finish
- Example showing how to run a job chain with jobs that are to be run on different servers
- Can execution of a job chain depend on the previous execution status of a job?
Related Downloads
This example can be downloaded here: JobChainDependencies.zip
.