JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 7

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 8

changes.mady.by.user Alan Amos

Saved on

Key

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

...

  • An outage of JOC Cockpit in most situations does not affect execution of workflows and jobs. Due to a the resilient architecture the JS7 components work autonomously.
  • The JOC Cockpit is used to manage the inventory of objects and to monitor the execution of workflows by Controllers and Agents. This means that in case of an outage users are blind, but it doesn't mean that jobs are not running.
  • If JOC Cockpit is not available then then:
    • users cannot login to the JOC Cockpit and cannot check the status of workflow execution by orders. Users cannot check the logs of workflows and jobs.

    • users cannot manage the inventory, modify and deploy workflows and related objects. No orders can Orders cannot be submitted.

  • Testing by SOS includes to performed performing tests for the scenario when the JOC Cockpit is not available for 24 hours and the Agent executes all scheduled orders. When the JOC Cockpit is started again then job execution results are updated to the JOC Cockpit History will be updated with the results of job executions and this information will become visible with in the GUI.

Controller Behavior

  • The Controller forwards workflows execution results of workflows to the JOC Cockpit. This information is stored with in the Controller's journal. If no connection to the JOC Cockpit is available then
    • the Controller's journal will grow. Depending on the workflow load of workflows the journal files that which are stored with in the ./state directory can grow to some Gigabytes. There is no harm about in this as long as sufficient storage is available.
    • this does not affect the communication between Controller and Agents. Agents will report back order state transitions and execution results to the Controller.
  • When the JOC Cockpit outage is resolved then JOC Cockpit will re-establish the connection to the Controller. At this point in time the information about execution results will become available for to the JS7 - History Service that which stores the information with in the JS7 - Database.
    • Depending on the workflow load of workflows and the duration of the outage it can take some time to update the JOC Cockpit history. However, no information is will be lost.
    • With The Controller's journal will shrink once execution results being have been added to the JOC Cockpit database the Controller's journal will shrink .

Agent Behavior

  • Workflows are deployed to Agents just once - at design-time. At run-time, when an Agent receives has received orders for workflows some time in advance, e.g. by , for example, from the JS7 - Daily Plan Service, then it can execute them autonomously.
  • Agents will continue to execute workflows for the at their scheduled timetimes. When the connection between Controller and Agent the JOC Cockpit becomes available then , the Agent Controller will report back execution results and order state transitions to the ControllerJOC Cockpit.