| Table of Contents |
|---|
Introduction
...
Fail-over is handled by a load balancer, which is placed 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 the HTTPS protocol to be used for communication between the user's browser and the load balancer.
Note that the load balancer has to be configured to forward session cookies when requests are forwarded from one JOC cockpit instance to another.
Cluster Configuration
Clustering is configured as follows:
- Install two or more instances of the JOC Cockpit on separate servers.
- All JOC Cockpit servers must use the same reporting database.
Add the following two lines of configuration items to the
[main]section of the Shiro configuration for one of the instances:Code Block language xml sessionDAO = com.sos.auth.shiro.SOSDistributedSessionDAO securityManager.sessionManager.sessionDAO = $sessionDAO
This can be done most easily with a User Account that has the necessary permissions and using the Enable JOC Cluster button in the Manage Accounts / Main Section tab of the JOC Cockpit interface. See the Authentication and Authorization - Configuration article for more information about the Shiro configuration.
- Connect a load balancer to all JOC Cockpit instances.
...