Short overview about Orders:
Overview
- An order is a JobScheduler element which works as a "Token". It is passed from a job chain node to the next node or to multiple nodes (parallel orders) in case of parallel job chain configuration (Nodeh1. Job Step).
- An order can have following configuration elements:
- runtime configuration date/time/frequency
- parameters i.e. cutoff-date, database connection information etc.
- target server name/ip address for job chain execution, the default is localhost
- An order primarily carries parameters which can be used by specific job nodes or by all the nodes of the job chain.
- An order can also carry runtime configuration i.e. date/time/frequency etc.
- An order can be configured to start part of job chain on one server i.e. Server-A and part of job chain on a second server i.e. Server-B.
- An order can be also configured to start a locally configured job chain on a remote server. This means that a generic job chain can be used along with create multiple orders for that job chain. In turn, an order can (optionally) contain the server name, a runtime configuration and any extra parameters required for jobs.
- An order is also a "stateless" object, which means that orders do not have success or error states. State is a job property.
- An order can start from any step (default is first step) in a job chain and end at any step (default is last step/end node). It can also skip part of the job chain according to specified conditions.
- JobScheduler can also create orders from a file-watcher i.e. a job chain can be configured to monitor any directory for incoming file(s). Once a file is matched with a regular expression, JobScheduler will create an order to start processing of the file.
- An order can carry parameters from one node to another: parameters can be overwritten, deleted or new parameters can be added to the order at each node.
- All the order parameters are also available as environment variables, thus an order parameter added by a Java application job will be accessible to a shell script job or even to PL/SQL script job.
Order Example