Page History

...

• The Controller forwards execution results of workflows to JOC Cockpit. This information is stored with the Controller's journal. If no connection to JOC Cockpit is available then
  • the Controller's journal will grow. Depending on the load of workflows the journal files that are stored with the ./state directory can grow to some Gigabytes. There is no harm about this as long as sufficient disk space 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 the JOC Cockpit the JS7 - History Service that  that stores the information with the database JS7 - Database.
  • Depending on the load of workflows and the duration of the outage it can take some time to update the JOC Cockpit Historyhistory. However, no information is lost.
  • With execution results being added to the JOC Cockpit database the Controller's journal will shrink.

...

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

...