2.5.2.4 Approach

There are many ways to devise the HA architecture based on the requirements, but the following is the recommended approach (to be used as reference) to devise any further changes or modifications to the architecture as per the use cases. The following figure shows the OFSAA deployment architecture for HA configuration as the end state.

Figure 2-4 High-Availability

In this illustration, the HA setup is proposed to be ACTIVE-ACTIVE configuration at the HTTP Server, Web Application Server, and Database or HDFS layers. The OFSAA layer is configured for ACTIVE- PASSIVE configuration.

Note:

Access to OFSAA applications is provided using the Global Load Balancer IP or hostname (Virtual IP). In the event of a primary node failure, the access to the secondary node is seamless, requiring no changes to the configuration information across all tiers.

Session Affinity or Sticky Session is configured at the HTTP Server level.

At any time, OFSAA patch installations should be performed only on an active node. Promotions of patches to a passive node are taken care of as part of the sync-up process for File System components.