...
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 user sessions being stored in the database instead of in the JOC Cockpit installationinstance. In addition the Shiro authentication and authorization information is shared between installations.
Fail-over is handled by a load balancer, which is placed "before" in front of 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.
...
Installation of redundant JOC Cockpit instances follows standard installation procedure procedures described in the JOC Cockpit - Installation article.
...