Introduction
Multiple JOC Cockpit instances can be operated as an active cluster, in conjunction with a load balancer, to achieve load balancing and high availability. Alternatively, redundancy can be achieved by installing several JOC Cockpits on separate servers "in parallel".
JOC Cockpit Clusters
FEATURE AVAILABILITY STARTING FROM RELEASE 1.12.2
With this configuration, multiple instances of the JOC Cockpit are installed on separate servers and configured to use the same reporting database. In addition, session sharing between the JOC Cockpit instances is activated with authentication tokens being stored in the database instead of in the JOC Cockpit installation. The fail-over is handled by a load balancer, which is placed "before" the JOC Cockpit servers. The load balancer handles all user requests via a single URL and ensures that the fail-over is transparent. Clustering also allows HTTPS protocol to be used for communication between the user's browser and the load balancer.
Configuration
The configuration of JOC Cockpit clusters is described in the Clustering section of the Authentication and Authorization - Configuration article.
Redundant Operation of the JOC Cockpit
FEATURE AVAILABILITY STARTING FROM RELEASE 1.12
A number of JOC Cockpit instances running on separate servers can be used to achieve a degree of operational redundancy. As with a cluster, the JOC Cockpit instances are configured to use the same reporting database. However, each instance is addressed with its own URL and "fail-over" will involve the user manually changing the URL used to access the JOC Cockpit and re-logging in.
Installation of redundant JOC Cockpit instances follows standard installation procedure described in the JOC Cockpit - Installation article.