Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

Description:Command:
additional startup steps on Central Instance host after start of the Central Instance before
start of any Application Server Instance
start_addons_postci
additional startup steps that are performed on the Central Instance host after startup of all
Application Server Instances
start_addons_postciapp
Equally, there are hooks for the stop procedure of packages:
usually this function contains actions that relate to what has been added to
start_addons_postciapp
stop_addons_preciapp
relates to start_addons_postcistop_addons_preci
relates to start_addons_precistop_addons_postci
relates to start_addons_postdbstop_addons_predb
relates to start_addons_predbstop_addons_postdb
The customer.functions template that is delivered with Serviceguard Extension for SAP on Linux provides
several examples within the hook functions. They can be activated via additional parameters as described
in the following.
Stubs for JAVA based components work in a similar fashion.
Optional Step: OS740
SAPROUTER is an example for an additional program that always starts on the Central Instance host.
The array SAPROUTER_START[*] should be set to 1 for each saprouter that should be started with the
CI package. Make sure that multiple saprouters do not share the same SAPROUTER_PORT. The
SAPROUTER_HOST[*]-array specifies where the saprouter should be started. These parameters are
mandatory. An optional SAPROUTER_STRING may be set that will be passed to the saprouter, for example
to set the path to the saprouttab file to reside on a shared volume.
Example:
SAPROUTER_START[0]=1
SAPROUTER_PORT[0]="-S3299"
SAPROUTER_HOST[0]=hpcc006
SAPROUTER_STRING[0]="-W 20000 -R /sapmnt/SG1/profile/saprouttab3299 -T
sapmnt/SG1/profile/dev_rout3299"
The saprouter(s) get(s) started in the script customer.functions (start_addons_postciapp)
and get(s) halted sequentially during package shutdown (stop_addons_preciapp).
Optional Step: OS750
Specify RFCADAPTER_START=1 to automatically start the RFC adapter component, e.g. for some early
Exchange Infrastructure versions.
Make sure that the JVM executables can be reached via the path of SIDADM.
Example:
RFCADAPTER_START=1
RFCADAPTER_CMD="run_adapter.sh"
Optional Step: OS760
Specify SAPCCMSR_START=1 if there should be a CCMS agent started on the DB host automatically.
You should also specify a path to the profile that resides on a shared volume.
Example:
SAPCCMSR_START=1
SAPCCMSR_CMD=sapccmsr
SAPCCMSR_PFL="/usr/sap/ccms/${SAPSYSTEMNAME}_${CINR}/sapccmsr/${SAPSYSTEMNAME}.pfl"
Serviceguard Extension for SAP on Linux Configuration - sap.config 91