JOSSO.orgCommunity Documentation

Chapter 15. High-availability and Scalability

15.1. About High Availability
15.1.1. System Failover
15.1.2. Session Failover
15.1.3. Exploring a Reference Architecture
15.1.4. Enabling Clustering
15.1.5. Replicating the Configuration

Two key high-availability elements in a JOSSO EE implementation are system failover and session failover. These two features help to ensure that no single point of failure exists in the deployment, and that JOSSO EE service is always available to end-users.

The figure below illustrates the building blocks you need for basic system failover and session failover in a JOSSO EE deployment. Key components in this high availability deployment are:

In this example, load balancers represent the only access points to JOSSO EE servers. An access point can be any hardware or software that acts as a load balancer, and is associated with a site, that is installed in front of JOSSO EE servers. JOSSO Single Sign-On Agents interact with JOSSO EE servers through these access points.

The following figure illustrates the components required for basic system failover and session failover deployment.

By enabling clustering support as described in the previous section, you are enabling application state replication. Whereas, this does not encompass replicating configuration data, such as identity appliances. Replicating identity appliances is cornerstone, since they represent the blueprint of the identity services that will be exposed to users.

There are three fundamental approaches you can use to synchronize configuration data : manual, managed automatic and non-managed automatic.

This approach is built on top of Apache Derby's failover capabilities.

In order to enable data failover using Apache Derby replication for a JOSSO EE server refer to the descriptor located at $JOSSO2_HOME/etc/com.atricore.idbus.console.db.cfg.

For more information on setting Apache Derby database replication see : Replicating databases