Skip to end of metadata
Go to start of metadata

Introduction

  • An outage of JOC Cockpit in most situations does not affect execution of workflows and jobs. Due to the resilient architecture JS7 components work autonomously.
  • The JOC Cockpit is used to manage the inventory of objects and 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:
    • 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. Orders cannot be submitted.

  • Testing by SOS includes 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 the JOC Cockpit History will be updated with the results of job executions and this information will become visible in the GUI.

Controller Behavior

  • The Controller forwards workflows execution results to the JOC Cockpit. This information is stored 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 the journal files which are stored in the ./state directory can grow to some Gigabytes. There is no harm 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 to the JS7 - History Service which stores the information in the JS7 - Database.
    • Depending on the workflow load and the duration of the outage it can take some time to update the JOC Cockpit history. However, no information will be lost.
    • The Controller's journal will shrink once execution results have been added to the JOC Cockpit database .

Agent Behavior

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



  • No labels