...

• The JOC Cockpit Cluster brings high-availability through fail-over (automated) and switch-over (by user intervention) capabilities.
  • A number of JOC Cockpit instances are operated on different servers with one JOC Cockpit instance taking the active role and the other instances acting as standbys.
  • Automated fail-over guarantees high-availability and restart capabilities of a JOC Cockpit Cluster (passive cluster).
• The JOC Cockpit can be configured to act as a Cluster Watch, see JS7 - Controller Cluster. In this scenario an active JOC Cockpit instance has to be available to support Controller Cluster fail-over.
• The JOC Cockpit itself does not ´take an active part in job or workflow execution, which are performed by the Controller and Agents. Therefore unavailability of the JOC Cockpit or of the database service does not affect job or workflow execution. However, it does affect monitoring and control of jobs.
• The Use of the JOC Cockpit Cluster is subject to the agreements of the the JS7 - License.

Cluster Management

...