Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


  • Use Case:
    • Consider the situation where a number of orders are added in an arbitrary sequence and at arbitrary points in time to a job chain - either from a file order source watching incoming files , from or from an external source such as JOC that adds ad hoc orders or from permanent orders. The orders should then be processed serially according to predefined criteria.
    • Each order comes either:
      • with a parameter that specifies a numeric sequence,
      • with a parameter that specifies a business date, e.g. for data files that are referenced by the order and that should be loaded to a data warehouse in sequence of the business dates,
      • without parameters and should be processed in alphabetical or numerical sequence according to its order ID.
    • Orders should be processed strictly in the required sequence - either ascending or descending. If an incoming order does not provide the expected value then it should be suspended and the job chain waits for an order with the expected value to arrive. After arrival of an order with the expected value all suspended orders should then be checked to see if they provide the expected value required for the successor order. 
  • Solution Outline:
    • A single job is added at the start beginning of a job chain. This job:
      • checks for exepected values and suspends incoming orders until an order with the expected value arrives,
      • moves orders that match expected values to the next job node in the job chain and rechecks the expected value of any suspended orders.
  • References