SAP Central Services high availability setup options

System Automation for Multiplatforms supports three different SAP Central Services high availability installation setups:
  • ABAP (ASCS) high availability installation
  • Java™ (SCS) high availability installation
  • Double-stack (ASCS and SCS) high availability installation
Select the high availability installation that matches your SAP installation.

Standalone Enqueue Server 2 support

The Standalone Enqueue Server 2 (ENSA2) in SAP NetWeaver Application Server for an SAP Advanced Business Application Programming (ABAP) system provides improved scalability and advanced SMENQ transaction. You can use the advanced SMENQ transaction instead of the previous SM12 transaction to monitor and administer ENSA2. The standalone ENSA2 provides a simplified high availability architecture and the Enqueue Replicator 2 (ERS2) provides an improved failover process.

From System Automation for Multiplatforms fixpack 4.1.0.5, with SAP NetWeaver policy supports Enqueue Server 2 (ENSA2) by using Enqueue Replicator Server 2(ERS2). The ENSA2 can be configured either in a two-node cluster configuration or a multi-node cluster configuration. In a two-node cluster configuration, ABAP SAP Central Services (ASCS) fails over to the node where ERS is running. In a multi-node cluster configuration, ASCS fails over to any online node in the cluster where ERS is not running.

Note: To transform your existing SAP into a highly available SAP, keep your existing SAP up and running until the newly installed SAP Central Services high availability setup is tested.