...
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 HTTPS protocol to be used for communication between the user's browser and the load balancer.
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 using the Enable JOC Cluster button in the Manage Accounts / Main Section tab.
- Connect a load balancer to all JOC Cockpit instances.
Configuration testing
You can test whether the cluster is configured correctly with the attached script following script:
...
An example call for calling the script iswould be:
./joc_cockpit_cluster_check.sh -ischeduler_id
-uhost1:4446 -rhost2:4448 -auser:pwd -t10
...