| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
General
JobScheduler JobChain contains 4 jobs i.e. Job01, Job02, Job03 and Job04. Job04 can only be started when Job01,Job02,Job03
Example of ini file with profiles: copy files from local host to target host using SFTP
...
| language | html/xml |
|---|
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
.
To execute this profile on the command line type:
...