Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Short overview about Orders:

Overview

  1. An order is a JobScheduler element which works as a "token". It is passed from one job chain node to the next or to multiple nodes (parallel orders) in case of parallel job chain configuration (Node 1. Job Step).
  2. Among the configuration elements an order can have are the following:
    • runtime configuration date/time/frequency,
    • parameters such as a cutoff-date, database connection information, etc.
    • target server name/ip address for job chain execution - the default is localhost.
  3. An order primarily carries parameters which can be used by one or more job nodes in a job chain.
  4. An order can also carry runtime configuration information such as date/time/frequency etc.
  5. An order can be configured to start part of job chain on a remote server i.e. Server-A and part of a job chain on a second server i.e. Server-B.
  6. An order can also be configured to start a locally configured job chain on a remote server. This means that a generic job chain can be used to create multiple orders for a job chain. In turn, an order can (optionally) contain the server name, a runtime configuration and any extra parameters required for jobs.
  7. An order is also a "stateless" object, which means that orders do not have success or error states. State is a job property.
  8. 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.
  9. 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.
  10. An order can carry parameters from one node to another: parameters can be overwritten, deleted or new parameters added to the order at each node.
  11. 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 a PL/SQL script job.
  12. JobScheduler gives each order run a unique ID. This is exposed by the SCHEDULER_ORDER_HISTORY_ID environment variable and the order.history_id read-only API property.
    FEATURE AVAILABILITY STARTING FROM RELEASE 1.9.8 FEATURE AVAILABILITY STARTING FROM RELEASE 1.10.1
    See JS-1513 - Getting issue details... STATUS

Order Example

  • No labels