Page History

...

• The solution contains three job chains:
  • job_chain_A and job_chain_B represent the predecessor job chains that have no relevant dependencies with job_chain_Z.
  • job_chain_Z is the final job chain that checks if job_chain_A and job_chain_B have previously been executed successfully.
• The solution implements a job check_predecessor_job_chain_Z that has been added to the top of job_chain_Z.
  • This job is parameterized with any number of parameters that start with the prefix "check_predecessor" and use an arbitrary suffix that is required in order to create unique parameter names. The value of each parameter is the final job of the respective job chain that is checked for successful execution:
    • Example
      • check_predecessor_A = issues/final_chain/do_something_job_chain_A
      • check_predecessor_B = issues/final_chain/do_something_job_chain_B
    • Should the sample files not have been extracted to the ./config/live/issues/final_chain folder then please adjust the parameter value to point to the respective directory.
  • This job implements a spooler_process() function that reads the parameters and checks the job history for successful execution of jobs as specified by the parameters.
  • Should all checks for previous successful execution provide a positive result, then the current order is moved to the next job chain node. Otherwise the current order is set back an will repeat several times depending on the setback configuration of this job.

...