Managing Serviceguard Extension for SAP Version B.05.10, December 2012

A couple of required SAP executables should be copied from the central executable directory
/sapmnt/<SID>/exe to the instance executable
directory/usr/sap/<SID>/ERS<INSTNR>/exe.
For SAP kernel 6.40, the list includes:
enqt, enrepserver, ensmon, libicudata.so.30, libicui18n.so.30,
libicuuc.so.30, libsapu16_mt.so, libsapu16.so, librfcum.so, sapcpe, and
sapstart.
For some releases, the shared library file extension .so is replaced by .sl. Apart from this, the
procedure remains the same. Copy these files and add a file named ers.lst in the instance
executable directory. The ers.lst should include the following lines:
enqt
enrepserver
ensmon
libicudata.so.30
libicui18n.so.30
libicuuc.so.30
libsapu16_mt.so
libsapu16.so
librfcum.so
sapcpe
sapstart
ers.lst
For SAP kernel 7.00 or higher, in addition, the following executables need to be copied:
sapstartsrv
sapcontrol
servicehttp/sapmc/sapmc.jar
servicehttp/sapmc/sapmc.html
servicehttp/sapmc/frog.jar
servicehttp/sapmc/soapclient.jar
For SAP kernel 7.00 or higher, in addition, the ers.lst file needs the following lines:
sapstartsrv
sapcontrol
servicehttp
The following script example cperinit.sh performs this step for 7.00 kernels.
for i in enqt enrepserver ensmon libicudata.so.30 libicui18n.so.30 libicuuc.so.30 libsapu16_mt.so libsapu16.so
librfcum.so sapcpe sapstart sapstartsrv sapcontrol
do
cp /sapmnt/$1/exe/$1 /usr/sap/$1/$2/exe
echo $i >> /usr/sap/$1/$2/exe/ers.lst
done
echo servicehttp >> /usr/sap/$1/$2/exe/ers.lst
echo ers.lst >> /usr/sap/$1/$2/exe/ers.lst
for i in sapmc.jar sapmc.html frog.jar soapclient.jar
do
cp /sapmnt/$1/exe/servicehttp/sapmc/$i /usr/sap/$1/$2/exe/servicehttp/sapmc/$i
done
The script needs to be called providing a SAP SID and the instance.
Example: ./cperinit.sh C11 ERS00
Replicated Enqueue Conversion: RE100
Create instance profile and startup profile for the ERS Instance .
These profiles get created as <sid>adm in the instance profile directory—
/usr/sap/<SID>/ERS<INSTNR>/profile.
Even though this is a different instance, the instance number is identical to the instance number of
the [A]SCS. The virtual IP address used needs to be different in any case.
Here is an example template for the instance profile <SID>_ERS<INSTNR>_<[A]REPRELOC>:
#--------------------------------------------------------------------
# system settings
#--------------------------------------------------------------------
SAP Preparation 55