Versions Compared

Key

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

...

  • 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.

License Model Changes

The JobScheduler and YADE products are available under a dual license model that gives customers the choice between open source licenses and commercial licenses.

  • JS1
    • The license model includes to run any number of parallel jobs with Masters and Agents if used with the commercial license.
    • Users of the open source license can run any number of parallel jobs with Masters and are limited to run one task at a time with Agents.
  • JS7
    • JS7 introduces a new license model, for details see JS7 - License.
    • Users of the open source license can run any number of parallel jobs with JS7 Agents.
    • The same source code and therefore the same feature functionality is available with both license models. The one exception is the operational feature to cluster the JS7 components for high availability which is a commercially available feature for enterprise customers.
  • JS1 + JS7
    • The SOS is committed to open source. Open source is about free software, in the sense of freely available source code.
    • Customers with commercial licenses benefit from additional Support Options and Services.