Short overview about Order:
Overview
- Order is a JS element which works as a "Token". Order is passed from a JobChain node to next node or to multiple next nodes (parallel Orders ) in case of parallel JobChain configuration (Nodeh1. JobStep).
- 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 JobChain execution , default is localhost
- Order primarily carry parameters which could be used by specific job node or by all the nodes of a JobChain.
- Order also carry runtime configuration i.e. date/time/frequency etc.
- Order can be configured to start part of JobChain on one server i.e. Server-A and part of JobChain on a second server i.e. Server-B.
- Order can be also configured to start a locally configured JobChain on a remote server, so one can create a generic JobChain and create multiple orders for JobChain, a order in turn can contain ( optional ) server name, runtime configuration and extra parameters required for jobs.
- Order is also a "stateless" object, which means order do not has success or error state. State is a property of a Job.
- Order can starts from any step (default is first step) in the JobChain and end at any step (default is last step/end node)or can skip part of JobChain depending upon specified conditions.
- JS can also create orders from file-watcher i.e. a JobChain can be configured to monitor any directory for incoming file(s), once a file matching with regular expression is found JS creates order to start the file processing.
- Order carry parameters from one node to another, parameters can be overloaded , deleted or new parameter can be added to the order by each node.
- All the order parameters are also available as environment variables , thus order parameter added by Java application job will be accessible to Shell script job or even to PL/SQL script job.