Release 2.0 - Job Net

Scope

• The JobScheduler 1.x branch allows standalone jobs and job chains to be configured.
  • Jobs can be configured to execute successor jobs based on return code evaluation.
  • Job Chains are a simple means to chain the execution of successor jobs.
  • More complex dependency patterns are implemented by JITL Jobs e.g. 
    • split & join orders within a job chain,
    • split  & sync order across job chains.
• While JobScheduler branch 1.x includes strong capabilities for Forward Dependencies it lacks ease of use for Backward Dependencies.
  • Backward Dependencies have to be implemented by pre- and post-processing scripts.
  • Backward Dependencies cannot be visualized as they are not formalized but buried in scripting.
• The JOE job editor is discontinued and the functionality to manage jobs and to design job dependencies is migrated to the JOC Cockpit. This move is intended to drop the remaining standalone Java component of the JobScheduler product and to move all components with user interaction to a browser-based GUI for better cloud readiness.

Feature

• A job net is based on the concept of a directed acyclic graph.
• The basic functionality of a job net is oriented towards the BPMN specification.
  • BPMN terminlogy is used with JobScheduler branch 2.x.
  • Most implications of a BPMN job net will be considered, however
• Job nets are instantiated individually for each business date by use of the Daily Plan Management.
  • Changes to a job net can be limited to specific dates and date ranges.
  • Job nets will consider the new Calendar Management.
• Dependency patterns such as split & join, split & sync etc. are configured at job net level. No additional jobs have to be added to implement such dependencies as e.g. with existing JITL jobs to split, join, and sync orders.
• A graphical editor is available that allows to design a job net including drag & drop capabilities.

Delimitations

• Most implications of a BPMN job net will be considered, however we do not intend to implement a 100% BPMN syntax-compatible workflow configuration. Instead, JobScheduler will dispose of its individual job configuration language (JSON) that can be transformed to BPMN. 
• JobScheduler 2.x will not be fully compatible to the 1.x branch. SOS will provide migration tools, however, some configuration items might require individual effort for migration.