Page History

...

• 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 monitor and 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.

...

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.

...

• In the JS7 - Dashboard the user performs the operation: 
  • Standby JOC Cockpit Instance action menu: Switch-over
    
    Image Added
    
    

• 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.

...