Page History

...

• Consider that loss of a Controller's journal means that:
  • any scheduling objects such as workflows have to be re-deployed,
  • any orders of the Daily Plan have to be re-submitted,
  • any currently running orders are lost and no information about orders and the execution status of jobs is available.
• See also the JS7 - FAQ - What happens to workflows in case of outage of a Controller? article.
• The use of a Controller cluster will leverage such a situation as the standby Controller instance operates a synchronized copy of the journal. The standby Controller instance will pick up operations immediately during fail-over after 3-5s. The failed Controller instance can then be started later on and will automatically synchronize with the then active Controller instance.

...

• Problem: If initial operation is has been successfully completed for a Controller and due to some weird reason the Controller instance's journal is deleted later on then this requires the Controller has to be registered once again from the JOC Cockpit. 
• Solution: This problem can be resolved by restarting the Controller. The Controller will start a new journal. In the JOC Cockpit "Manage Controllers/Agents" page use the "Edit" action menu of the Controller and submit the same settings as before. This operation will connect the JOC Cockpit to the Controller. Registration of existing Agents is automatically repeated. Then redeploy any scheduling objects to the Controller from the JOC Cockpit Configuration view.
• Implication: This operation does not recover information about past job executions which have not yet been added to the JOC Cockpit history.

...