Configure Essbase Servers in a Failover Cluster
Active-passive failover solutions are common in Essbase 11g On-Premise deployments. Users migrating to Essbase 21c can also implement active-passive failover clusters for Essbase Agent using WebLogic and a load balancer.
- Set up failover mode (or active-passive mode) for the Essbase Agent.
- Set up active-active mode for Essbase web interface, REST endpoints and Provider Services. These always connect to the single active Essbase node.
An active-passive Essbase cluster consists of two or more Essbase instances, one on each node, that share a common storage for configuration and data. Storage is shared across two or more servers (for example, using a SAN), removing the need for the administrator to synchronize storage, as well as the constraint of read-only support. Essbase uses database tables to ensure that only one agent and its associated servers are active, to avoid data corruption on writes. During installation and configuration, a table is created to hold information on configuration and application data in the cluster.
Compared to Essbase 11g On-Premise, where Essbase failover is managed by an external agent (OPMN), in Essbase 21c, the WebLogic architecture supports Essbase failover with a central request leasing system. The Essbase instance that acquires the lease becomes the active node. Other nodes are waiting in a loop, trying to acquire the lease.
Installation Type | Component | Essbase 11.1.2.4 | Essbase 21c |
---|---|---|---|
Single Node | Provider Services |
|
Same as 11.1.2.4 |
- | Essbase Agent |
|
|
- | Essbase application server. | If the Essbase application server fails, the Essbase agent restarts it on the next server request. | Same as 11.1.2.4. |
Multi-Node (Active/Passive) | Provider Services |
|
Same as 11.1.2.4. |
- | Essbase Agent |
|
|
- | Essbase Application Server |
|
Same as 11.1.2.4, except for server-level leasing. |