Introduction
The JobScheduler's unique concept includes the use of jobs within job chains with dependencies. Jobs are the basic unit for the processing of executable files, job chains can be seen as an assembly line on which multiple job nodes are passed.
Jobs
- Jobs are the basic unit for the processing of executable files, shell scripts, procedures and of job implementations based on the JobScheduler internal API.
- Jobs can be executed independently from one another. However, job starts can also be made dependent on the execution result (success, failure, exit code) of preceding jobs.
- Jobs can be executed in parallel by a configurable number of tasks.
Read more on these features in the job documentation.
Job Chains
- Job Chains can be seen as an assembly line on which multiple job nodes are passed, with each job making up one step in the processing of a chain.
Read more on this feature in the order and job chain documentation.
Orders
- Workflow is regulated by orders. An order can be thought of as a directive which is processed in a chain of jobs. An order is assigned to a job chain with an identifier which is valid for that particular job chain. The order also has a status which changes after the processing of each job node and can have a payload of parameters.
- Orders are persistently stored during processing. This means that if a job is stopped during processing and then restarted, it will be continued at exactly the point where it was stopped.
Read more on this feature in the order and job chain documentation.
Resources
Feature in detail
How To ... Instructions
Frequently Asked Questions
Examples in detail