High Availability and Scalability

High Availability (HA) and Scalability requires planning when it comes to deployment structure and there are a number of things that needs to be considered and performed before starting to install IFS Applications if aiming for a true HA solution and/or scalable deployment.

Note: For a HA cluster to properly function even when the master node crashed, it is recommended to setup at least two slave nodes (three nodes all together).
HA may not fully function in an event of hardware failure.
Managed servers in nodes with network failures tend to shutdown themselves due to isolation from clusters.
A Manual restart may be required once the hardware is restored.

From an HA and scalability aspect there are two parts of IFS Applications that each need their separate approach, the storage tier (i.e. the Oracle database) and the middle tier (i.e. the application server).

Storage Tier / Oracle Database

Please refer to Oracle documentation for detailed information about HA and scalability aspects and instructions on how to set up an Oracle Real Application Cluster (RAC) for instance.

Middle Tier / Application Server

 

Load Balancer

A load balancer must be used in front of the cluster in order to distribute the load among the cluster nodes.