Cluster Server 7.3.1 Configuration Guide for SAP Web Application Server - Windows

To manually configure the Enqueue Replication Server for SAP Web Application Server

1. Enable replication in the (A)SCS instance by adding the following parameter to the instance profile of (A)SCS instance:

   (SAPSID_InstName_VirtualHostname).

   enque/server/replication = true

   Restart the (A)SCS instance to make the change effective.

   Let us assume a two-node software failover cluster, running on the physical hosts - host A and host B, and a clustered (A) SCS instance with the following parameters.

   • SCS SAPSID = PLL

   • SCS INSTNO = 01

   • SCS HOST = sapscshost (virtual host name)

   This instance (that is, the Enqueue Server's lock table) must be protected with an ERS instance as follows:

   • ERS SAPSID = PLL

   • ERS INSTNO = 11 (a free instance number)

   • ERS HOST = sapershost (virtual hostname)

2. On one of the physical hosts ( host A or host B) perform the following steps as user sidadm or domain administrator:

   Create the directory structure as follows:

   drive:\usr\sap\PLL\ERS11\exe

   drive:\usr\sap\PLL\ERS11\log

   drive:\usr\sap\PLL\ERS11\data

   drive:\usr\sap\PLL\ERS11\work

3. Copy all the binaries from (A)SCS instance exe directory into the ERS instance exe directory.
4. Create a new ERS instance profile in drive:\usr\sap\PLL\SYS\profile.

   SAPSYSTEMNAME = PLL
   SAPSYSTEM = 11
   INSTANCE_NAME = ERS11
   
   DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
   DIR_INSTANCE = <drive>:\usr\sap\$(SAPSYSTEMNAME)\$(INSTANCE_NAME)
   DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
   DIR_PROFILE = $(DIR_INSTALL)/profile
   _PF = $(DIR_PROFILE)\PLL_ERS11_sapershost
   
   SAPGLOBALHOST = sapscshost
   SAPLOCALHOST = sapershost
   
   #----------------------------------------------------------------
   # Copy SAP Executables
   #----------------------------------------------------------------
   _CPARG0 = list:$(DIR_CT_RUN)/scs.lst
   Start_Program_01 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
   $(_CPARG0)
   #-----------------------------------------------------------------
   # Settings for enqueue monitoring tools (enqt, ensmon)
   #-----------------------------------------------------------------
   enque/process_location = REMOTESA
   rdisp/enqname = $(rdisp/myname)
   
   #-----------------------------------------------------------------
   # standalone enqueue details from (A)SCS instance
   #-----------------------------------------------------------------
   SCSID = 01
   SCSHOST = sapscshost
   enque/serverinst = $(SCSID)
   enque/serverhost = $(SCSHOST)
   enque/serverport = 32$(SCSID)
   
   enque/enrep/poll_interval = 0
   enque/enrep/poll_timeout = 120
   enque/enrep/inactive_action = sleep
   
   #-----------------------------------------------------------------
   # Start enqueue replication server
   #-----------------------------------------------------------------
   _ER = $(DIR_EXECUTABLE)\enrepserver$(FT_EXE)
   Start_Program_02 = local $(_ER) pf=$(_PFL) NR=$(SCSID)
   

   For DIR_CT_RUN in this ERS profile, take the value DIR_CT_RUN from the (A)SCS instance profile. If the (A)SCS instance has not configured DIR_CT_RUN in its profiles, take the value specified for DIR_EXECUTABLE from the (A)SCS instance profile.

   It is essential that the binaries from (A)SCS and ERS instance are from the same binary set.

5. Use the sapstartsrv.exe command to create an SAP Windows Service for the Enqueue Replication Server instance.
6. Start the SAP instance for the Enqueue Replication Server. Ensure that the instance starts successfully.

   The SAP instance is now ready for clustering and to control the life time of Enqueue Replication Server using VCS.