Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 107
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>:
#-----------------------------------------------------------------------
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = D<INSTNR_2>
#-----------------------------------------------------------------------
# start SCSA
#-----------------------------------------------------------------------
Execute_00 = local $(DIR_EXECUTABLE)/sapmscsa -n\
pf=$(DIR_PROFILE)/<SID>_D<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------
# start application server
#-----------------------------------------------------------------------
_DW = dw.sap<SID>_D<DRELOC>
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>_D<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------
_SE = se.sapRA1_D51
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>_D<INSTNR_2>_<DRELOC>
#-----------------------------------------------------------------------