Java (SCS) high availability setup

Java (SCS) high availability setup

The Java (SCS) high availability setup consists of at least two SCS nodes, which run the SCS and ERS instances. Under regular conditions, the ERS is always started on the node where the SCS is not running. This failover setup has no downtime due to fast failure detection and in-memory data exchange between ES and ERS in case the SCS must be moved to the failover node. During the failover, the virtual IP address for the SCS is moved to the failover node too, so its addressing remains unchanged.

Primary and Additional AS node

The Primary AS node and the Additional AS nodes consist of Java Application Servers, which are restarted in place in case of software failures. Protection against hardware failures is done by setting up multiple Application Servers on different hardware. Therefore, the System Automation for Multiplatforms concept for SAP high availability does not consider failovers of Application Servers to other nodes because Application Server restarts take a lot of time. Other Application Servers must be sized to take the additional workload from failing servers.

Web Dispatcher and SAProuter node (optional)

The Web Dispatcher and SAP router high availability setups consists of at least two nodes, which run the instances in a failover setup. The components are key for the clients to access the Application Servers, so in case of a failure the instance failover to standby nodes includes their virtual IP addresses too.

Database high availability setup

The database high availability setup is explained in Database high availability installation setup.

NFS high availability setup

The NFS high availability setup is explained in NFS high-availability installation setup.

Set up a Java SCS SAP high availability solution with the following components.