Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SGeSAP Configuration
Chapter 3166
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.
OS740 Optional Step:
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).
stop_addons_predb relates to start_addons_postdb
stop_addons_postdb relates to start_addons_predb
Table 3-7
Optional Parameters and Customizable Functions
List (Continued)
Command: Description: