Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Execute_06 = local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)
Start_Program_03 = local $(_EN) pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------
SE =se.sap<SID>_ASCS<INSTNR>
Execute_07 =local rm -f $(_SE)
Execute_08 =local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_04 =local $(_SE) -F pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
Replicated Enqueue Conversion: RE060
Adopt instance profile and startup profile for the DVEBMGS<INSTNR> instance.
The goal of this step is to strip the Enqueue and Message Server entries away and create a standard
Dialog Instance. A second alteration is the replacement of the Instance Number of the Central
Instance that now belongs to ASCS and AREP.
The new Dialog Instance profile <SID>_DVEBMGS<INSTNR_2>_<DRELOC> differs from the
original <SID>_DVEBMGS<INSTNR>_<ip_address> profile in several ways:
All configuration entries for Message and Enqueue Service need to be deleted, for example,
rdisp/wp_no_enq=1
must be removed. Several logical names and address references need to reflect a different
relocatable address and a different Instance Number.
Example:
SAPSYSTEM=<INSTNR_2>
rdisp/vbname = <DRELOC>_<SID>_<INSTNR_2>
SAPLOCALHOST=<DRELOC>
SAPLOCALHOSTFULL=<DRELOC>.domain
The exact changes depend on the individual appearance of the file for each installation. The
startup profile is also individual, but usually can be created similar to the default startup profile
of any Dialog Instance. Here is an example template for a startup profile
START_D<INSTNR_2>_<DRELOC>:
Scan the old <SID>_DVEBMGS<INSTNR>_<local_ip> profile for additional parameters that
apply to the Enqueue Service or the Message Service. Individual decisions need to be made
whether they should be moved to the new profile.
Here is an example template for the startup profile START_DVEBMGS<INSTNR>_<DRELOC>:
#-----------------------------------------------------------------------
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = DVEBMGS<INSTNR_2>
#-----------------------------------------------------------------------
# start SCSA
#-----------------------------------------------------------------------
Execute_00 = local $(DIR_EXECUTABLE)/sapmscsa -n
pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------
# start application server
#-----------------------------------------------------------------------
_DW = dw.sap<SID>_DVEBMGS<INSTNR_2>
Execute_01 = local rm -f $(_DW)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/disp+work $(_DW)
Start_Program_01 = local $(_DW) pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------
_SE = se.sap<SID>_<INSTNR_2>
Execute_03 = local rm -f $(_SE)
Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_02 = local $(_SE) -F pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------
46 Step-by-Step Cluster Conversion