Perform the following steps to manually configure the Enqueue Replication Server for SAP WebAS:
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
You have to restart the (A)SCS instance to make the change effective. 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 HOST = sapscshost (virtual host name)
This instance (namely, the enqueue server's lock table) should be protected with an ERS instance as follows:
On one of the physical host ( host A or host B) perform the following steps as user sidadm:
Copy the following binaries from (A)SCS instance exe directory into the ERS instance exe directory:
Note: |
The binary extensions vary for different operating systems. The naming conventions followed in the above binaries are applicable to Solaris platform. |
For each binary, ensure that the access and execute permissions are correctly set for sidadm.
Create a sapcpe list file ers.lst
with the following names.
The binary extensions may vary for different operating systems
Create a new ERS instance profile in /usr/sap/PLL/SYS/profile.
SAPSYSTEMNAME = PLL
SAPSYSTEM = 11
INSTANCE_NAME = ERS11
#---------------------------------------------------------
# Special settings for this manually set up instance
#---------------------------------------------------------
SCSID = 01
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
SAPGLOBALHOST = sapscshost
SAPLOCALHOST = sapershost
SETENV_00 = PATH=$(DIR_INSTANCE)/exe:%(PATH)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_EXECUTABLE):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
_PF = $(DIR_PROFILE)/PLL_ERS11_sapershost
#----------------------------------------------------------
# Copy SAP Executables
#----------------------------------------------------------
_CPARG0 = list:$(DIR_EXECUTABLE)/ers.lst
Execute_00 = immediate $(DIR_EXECUTABLE)/sapcpe$(FT_EXE)\
$(_CPARG0) pf=$(_PF)
#----------------------------------------------------------
# Settings for enqueue monitoring tools (enqt, ensmon)
#----------------------------------------------------------
enque/process_location = REMOTESA
rdisp/enqname = $(rdisp/myname)
#----------------------------------------------------------
# standalone enqueue details from (A)SCS instance
#----------------------------------------------------------
enque/serverinst = $(SCSID)
enque/serverhost = $(SAPGLOBALHOST)
enque/serverport = 32$(SCSID)
enque/poll_interval = 0
enque/poll_timeout = 120
enque/enrep/inactive_actio = sleep
enque/table_size = 4096
#----------------------------------------------------------
# Start enqueue replication server
#----------------------------------------------------------
_ER = er.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = immediate rm -f $(_ER)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ER)
Start_Program_00 = local $(_ER) pf=$(_PF) 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.
Control the life time of Enqueue Replication Server using switchover solution.