...

• Any workflows and jobs are executed with the Controller and Agents only. Orders are started and executed independently from JOC Cockpit once they are submitted by the JS7 - Daily Plan.
• In case that JOC Cockpit becomes unavailable
  • users cannot control the status of Controllers and Agents,
  • users cannot deploy scheduling objects to Controllers and Agents,
  • users cannot access the JS7 - History for execution results and log output of orders and tasks.

For command line references see the JS7 - JOC Cockpit - Command Line Operation article.

...

Cluster operations include an automated fail-over and a manual switch-over of the Active JOC Cockpit Instance.

Fail-over

Fail-over occurs when the Active JOC Cockpit Instance is terminated abnormally. 

Fail-over can be invoked by the following actions:

• The Active JOC Cockpit Instance is killed, for example
  • for Unix with a SIGKILL signal corresponding to the command: kill -9
  • for Windows with the command: taskkill /F
• The operating system crashes.

Fail-over happens within a period of time that depends on the number of orders that started but that did not yet complete. The minimum duration of a fail-over is 30s and can last for 2-3 minutes if thousands of active orders are in place.

Switch-over

Switch-over occurs exclusively when invoked by user intervention.

Switch-over can be invoked by the following actions:

...

• the Active JOC Cockpit Instance is stopped normally from the command line:
  • jetty.sh | .cmd stop
• the operating system is shut down and systemd / init.d or a Windows Service are in place to stop the JOC Cockpit normally.

Switch-over happens within a similar period of time as fail-over.

Further Resources

• JS7 - JOC Cockpit Cluster
• JS7 - Initial Operation for JOC Cockpit Cluster
• JS7 - JOC Cockpit - Command Line Operation

...