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

Step-by-Step Cluster Conversion
Serviceguard Extension for SAP on Linux Configuration – sap.config
Chapter 3 163
Global Defaults
The fourth section of sap.config is rarely needed. It mainly provides
various variables that allow overriding commonly used default
parameters.
OS770 Optional Step:
If there is a special demand to use values different from the default, it is
possible to redefine some global parameters. Depending on your need for
special high availability setups and configurations have a look at those
parameters and their description in the SAP specific configuration file
sap.config.
NW04S780 Optional Step for Netweaver 2004s:
This installation step only applies if Netweaver 2004s with SAP WAS 7.0
is installed.
SAP introduced a control framework with Netweaver 2004s and SAP
WAS 7.0 that enables the management of SAP instances from third party
products using a defined application interface. This control framework is
implemented using a daemon process that is either started by:
• the operating system during boot time or
• the SAP startup script when the instance is started.
During the installation of a SAP Netweaver 2004s Web AS, the SAPIinst
installer edits a file in /etc/sysconfig/sapr3 and adds a line for each
sapstartservice instance. During boot time a init script is executed
located in:
/etc/init.d/sapinit
referenced by
/etc/rc3.d/S<###>sapinit
The sapinit script reads the content in file /etc/sysconfig/sapr3 and
starts a sapstartsrv for each instance during OS boot time. This can
lead to error output in the boot messages logfile as file systems for
exclusive shared storage is not available at that time.
If the use of the SAP control framework is not required, then remove the
reference link from the sapinit script. Furthermore, any running
sapstartsrv processes can be killed from the process list. For example:
# rm /etc/rc3.d/S<###>sapinit