The standalone enqueue server (SAP Central Services – SCS) is used in NetWeaver Web AS Java to provide a locking service based on the enqueue function. Commands to check status of ERS/SCS instances 5. Checking the Installation (Replication Server) 4. $ClusterName = $SAPSID.This document contains steps to be performed to install, configuring and testing an ERS instance failover.Īpplies to NetWeaver Web AS Java 2004s onwards (Unix system)ĭivided the article in below sections:- 1. Run this command on one of the cluster nodes: # Hostnames of the Win cluster for SAP ASCS/SCS
Enqueue replication server install#
Install and configure Windows failover cluster Install the Windows failover cluster feature
Add the Windows VMs to the domainĪfter you assign static IP addresses to the virtual machines, add the virtual machines to the domain. To apply the changes, restart both cluster nodes. HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters The following registry entries must be changed on both cluster nodes: If using ERS1, it is also necessary to add SAP profile parameters, as described later in this article. To avoid interrupting these connections, change the TCP/IP KeepAliveTime and KeepAliveInterval values on both cluster nodes. The SAP work processes open connections to the SAP enqueue process as soon as the first enqueue/dequeue request needs to be sent. Add registry entries on both cluster nodes of the ASCS/SCS instanceĪzure Load Balancer may close connections, if the connections are idle for a period and exceed the idle timeout. Azure Internal Load Balancer will be created and configured as well.įor details - see the ARM template. The Azure ARM template will create two Windows 2019 or 2016 VMs, create Azure shared disk and attach to the VMs. With the Azure Resource Manager Template for WSFC for SAP ASCS/SCS instance with Azure Shared Disk, you can automate the infrastructure preparation, using Azure Shared Disk for one SAP SID with ERS1. The VMs were already added to the ILB backend pool.
This section only applies, if using Enqueue replication server 2 architecture. Make sure that Idle timeout (minutes) is set to max value 30, and that Floating IP (direct server return) is Enabled.Īs Enqueue Replication Server 2 (ERS2) is also clustered, ERS2 virtual IP address must be also configured on Azure ILB in addition to above SAP ASCS/SCS IP. If using Basic Load Balancer, create Load-balancing rules for the following ports If using Standard Load Balancer, select HA ports
Leave the default option for Protocol (TCP), Interval (5), Unhealthy threshold (2) In this example VMs pr1-ascs-10 and pr1-ascs-11. The configuration for both SAP ASCS and ERS2 in performed in the same Azure load balancer.Īdd all virtual machines that should be part of the (A)SCS/ERS cluster. The following list shows the configuration of the (A)SCS/ERS load balancer. If you need additional IP address for the VM, deploy a second NIC. For details see Azure Load balancer Limitations. But if your cluster is running in availability set, you need to deploy LRS for Azure premium shared disk (Premium_LRS) and if the cluster is running in availability zone deploy ZRS for Azure premium shared disk (Premium_ZRS).įloating IP is not supported on a NIC secondary IP configuration in load-balancing scenarios. The steps mentioned in the document remain same for both deployment type. SAP deployment in Azure availability zones Host name role SAP deployment in Azure availability set Host name roleĮRS cluster network name ( only for ERS2) Create Azure Internal Load Balancer for SAP ASCS /SCS instance.īased on your deployment type, the host names and the IP addresses of the scenario would be like:.Architecture guide: Cluster an SAP ASCS/SCS instance on a Windows failover cluster by using a cluster shared diskįor SAP ASCS / SCS cluster deploy two VMs in Azure availability set or Azure availability zones based on the type of your deployment.
Prerequisitesīefore you begin the installation, review this article: The documentation doesn't cover the database layer.