Page History

...

• Connection Status
  • JOC Cockpit instances are connected
    • to a Database,
    • to Controller instances, e.g. to a Standalone Controller or to a Controller Cluster with a Primary and Secondary Controller instance.
  • Controller instances in a cluster are connected to each other.
  • The connection status, i.e. the lines between components are displayed in with the following colors:
    • The connected status indicates a working connection.
    • The unstable status indicates that the connection works but had errors during the last 30 minutes.
    • The unknown status indicates that the connection could not be established. This does not indicate that the component is not running as e.g. network issues can prevent a connection from being established.
• Component Status
  • The component status is indicated with the colored square in the left upper corner of each component.
  • The green component status signals availability, the red square signals an unknown component status as the component is not connected.
• Cluster Node State
  • The cluster node state is displayed for
    • a number of JOC Cockpit instances running in parallel.
    • a Primary Controller instance and Secondary Controller instance in a Controller cluster.
  • JOC Cockpit
    • JOC Cockpit can be implemented as an active-passive cluster with any number of instances.
      • The active JOC Cockpit instance displays the active cluster node state.
      • Additional JOC Cockpit instances display a standby or unknown cluster node state.
    • The currently used JOC Cockpit instances is displayed with a thick border and offers a context menu
      • to restart the JOC Cockpit cluster,
      • to restart individual JS7 - Services,
      • to download the JOC Cockpit main log file, see JS7 - Log Files and Locations.
    • Standby JOC Cockpit instances offer a switch-over function with their context menu that causes the standby instance to become the active instance in a cluster. Switch-over typically is performed within 60s as this is not considered an emergency fail-over but normal operation that leaves running background services enough time to complete their tasks.
  • Controller
    • A Controller can be implemented as an active-passive cluster with two instances.
    • Cluster Node State
      • The active Controller instance and the standby Controller instance cluster node states are displayed. Controller instances with an unknown component status are not connected to a JOC Cockpit instance and their cluster node state cannot be determined.
    • Cluster Status
      
      • The Coupled cluster status indicates a working cluster with Controller instances being synchronized.
      • The ClusterNodesAppointed and PreparedToBeCoupled cluster status indicate that the cluster currently is connecting and respectively is synchronizing past events which occurs after a restart of one or both Controller instances. This is a temporary status until the synchronization is completed
      • The PassiveLost cluster status indicates that the standby Controller instance is not connected to the active Controller instance. The active Controller instance will continue to execute workflows and jobs, however, this cluster status indicates loss of high-availability.

...

• The widget displays Agents in the order of frequency of parallel jobs. The length of the bar indicates the number of jobs running in parallel.
• Users can modify the widget size to display for example the 30 Agents with the highest number of parallel jobs.

...