HP Serviceguard Extension for SAP (SGeSAP) manual SAPROUTERSTART0=1 SAPROUTERPORT0=-S3299

of the package script execution. Therefore it is not necessary and also not allowed to change the sap.functions.

In the following there is a summary of the function hooks in chronological order:

Table 3-7 Optional Parameters and Customizable Functions List

Command:	Description:
start_addons_predb	additional startup steps on database host after all low level resources are made available
	after the system has been cleaned up for db start before start of database instance
start_addons_postdb	additional startup steps on database host after start of the database instance
start_addons_preci	additional startup steps on Central Instance host after start of the database instance
start_addons_postci	additional startup steps on Central Instance host after start of the Central Instance before
	start of any Application Server Instance
start_addons_postciapp	additional startup steps that are performed on the Central Instance host after startup of all
	Application Server Instances

Equally, there are hooks for the stop procedure of packages:

stop_addons_preciapp	usually this function contains actions that relate to what has been added to
	start_addons_postciapp
stop_addons_preci	relates to start_addons_postci
stop_addons_postci	relates to start_addons_preci
stop_addons_predb	relates to start_addons_postdb
stop_addons_postdb	relates to start_addons_predb

The customer.functions template that is delivered with SGeSAP 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 fashions.

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[*]-arrayspecifies 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,

For Example, 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

Legacy Package Configuration 77