Versions Compared

Key

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

...

  • Users do not receive up-to-date information:
    • The JOC Cockpit will not receive updated information about the state of orders and of workflow execution results.
    • The GUI will report the Controller being unreachable and will have no information about the status of Agents.
  • Any interaction with a Controller such as deploying workflows and cancelling/suspending orders will be delayed.
    • This means that such requests are held in memory with the JOC Cockpit Proxy Service which will try to forward the requests when the Controller becomes available.
    • It is not recommended that the JOC Cockpit is restarted in this situation as pending requests would be lost and deployments would have to be repeated.
  • The JOC Cockpit Proxy Service will try to re-establish the connection to the Controller. When this is successful the GUI will automatically updates the update the status of the Controller in its Dashboard.

...

  • Workflows are deployed to Agents just once - at design-time. At run-time, the Agent will have received orders for workflows some time, such as a week, in advance. These orders come from the JS7 - Daily Plan Service, and the agent Agent can execute them autonomously.
  • In case of a Controller outage:
    • Agents will continue to execute workflows at the scheduled date and time. 
    • the Agent's journal will grow. The journal holds execution results for workflows and order state transitions.
  • Depending on the workflow load, the journal files that are stored with the ./state directory can grow to some Gigabytes. There is no harm in this as long as sufficient storage is available.
  • When the connection between Controller and Agent becomes available then the Agent will report back order state transitions and execution results to the Controller and the Agent's journal will shrink.

...