Page History

...

The documentation frequently indicates a Primary JOC Cockpit Instance and any number of Secondary JOC Cockpit Instances. The names suggest that one JOC Cockpit Instance is primarily used and other instances are used for backup purposes.

• The wording in of cluster terms suggests to indicate the Active JOC Cockpit Instance and the Standby JOC Cockpit Instances independently from the fact if the Primary or a Secondary JOC Cockpit Instance is active.
• JOC Cockpit implements an active-passive cluster, however, the term passive is misleading as the Standby JOC Cockpit Instances are not necessarily passive:
  • Users can login to a Standby JOC Cockpit Instance to perform any operations as available from the Active JOC Cockpit Instance.
  • The following limitations apply to use of Standby JOC Cockpit Instances:
    • The JS7 - Dashboard does not automatically update order states, history information and cluster status information. Such information is updated when navigating to the page.
    • No running log is available for orders and tasks that are currently executed. In addition, no access to order logs and task logs is available for the time that an order is not completed. 
• Any JOC Cockpit instances operated as a cluster use the same JS7 - Database.
  • The database is used to synchronize cluster operations. 
  • Unavailability of the database prevents the JOC Cockpit cluster from working.

...