Page History

...

• The JS1 knows Jobs and Job Chains that implement a sequence of jobs.
  • A job is an object that can be modified individually and that can be re-used with a number of job chains.
  • A job is defined to be operated standalone or as a node in a job chain.
  • Any changes to jobs and job chains are immediately in effect.
• The JS7 is not limited to a sequence of JS7 - Jobs but introduces a number of JS7 - Workflow Patterns which is why the term workflow replaces job chain.
  • A job is available within a workflow only. A job is not an independent object and it cannot be re-used.
    • While users might consider this a limitation, in fact it guarantees a self-contained and consistent workflow configuration. Consider the fact that a JS1 job could be modified or removed at run-time leaving the job chain in a critical status. The JobScheduler Master had to check for updated versions of a job XML file and had to apply any modifications in good time. If modifications are not consistent, e.g. if the job parameterization changed, then this breaks a current order run as any changes to jobs are immediately applied.
    • Modifications of a JS7 job force a workflow to be deployed once again.
    • The JS7 offers bulk operations for jobs to modify a single job and to apply changes to a number of jobs across workflows.
  • There are no JS1 standalone jobs in JS7, instead such jobs are considered workflows with a single job.
  • Changes to workflows take effect for newly added JS7 - Orders only. The JS7 Controller keeps track of workflow versions as long as an order is assigned the workflow.
    • At the point of time of submission an order is associated with the current version of a workflow.
    • If the workflow changes later on then this has no impact on submitted orders, but affects new orders only that are submitted after this change.
    • This feature can be used to target changes of a workflow to a future date. Existing orders can be cancelled and re-submitted to be assigned the current version of a workflow from the Daily Plan view.

Orders

The term "order" in JS1 corresponds to the term "schedule" in JS7Orders in JS1 correspond to JS7 - Schedules:

• JS1
  • The JS1 makes use of Orders that include a run-time definition. This means the order recalculates its next start time after execution. At the same time this includes that e.g. suspended orders will not calculate a next start time and will not be executed for future dates as long as they are suspended or blocked, e.g. by stopped jobs or job nodes.
  • JS7 cyclic orders are represented as a single order that recalculates its next start time after completion of the last cycle. This includes to use a relative cycle interval that counts from the completion of a previous order run to the start of the next order run.
  • JS1 orders can use Schedules that present run-time definitions shared by a number of orders and jobs
  • JS1 orders carry Parameters. If a parameter is changed then the order has to be changed, i.e. the change is valid for any future executions of an order starting from the point in time of the change.
• JS7
  • The JS7 creates individual JS7 - Orders for each execution of a workflow.
    • This allows to modify orders individually from the JS7 - Daily Plan, for example to modify the start time and parameters for individual days only.
    • Assume a daily order with a single start time: it will execute each day at the given time independently from the fact if the order for the previous day has been completed or is suspended or blocked.
  • A JS7 cyclic order is presented from the Daily Plan view as a single order, however, the cyclic order is submitted to a Controller as an individual order per cycle. This includes that each execution of an order cycle is independent from its predecessor and it includes that there cannot be a start time relative to completion of the predecessor cycle.

  • JS7 - Schedules correspond to JS1 Orders: a schedule combines a workflow reference, a run-time definition and variables (parameters). From a given schedule the Daily Plan generates individual orders for each day and start time.

  • The start time and variables of a JS7 order can be modified individually for each order from the Daily Plan view. If the start time or variables from a schedule are changed then this applies to any future orders created with the schedule, it does not apply to existing orders.
    • Note that orders can be submitted days or weeks in advance of their start time by use of the JS7 - Daily Plan Service.
    • This allows to target changes to a schedule for a specific date. Users can cancel and re-submit existing orders or re-create the Daily Plan if they want changes to a schedule to be in effect starting from a specific date.

...