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

Understanding Serviceguard Extension for SAP on Linux
Serviceguard Extension for SAP on Linux File structure
Chapter 132
• ${SGCONF}/<SID>/customer.functions - contains all functions
which can be modified for special setups. This file may also contain
your own additional functions. If there is a need to do a hotfix to
functions in ${SGCONF}/sap.functions, copy them over to
${SGCONF}/<SID>/customer.functions and modify them there.
Never modify ${SGCONF}/sap.functions itself. Any function
provided in customer.functions overrides its equivalent in
sap.functions.
• ${SGCONF}/<SID>/dbhanfs.sh - contains NFS specific runtime logic
used during database package startup or shutdown. It needs to be
customized. The file is optional, if a central Highly Available NFS
package is used.
• ${SGCONF}/<SID>/dbtoolkit.sh - contains NFS specific flowlogic
for package startup and package shutdown. It is optional, if a central
HA NFS package is used.
• ${SGCONF}/<SID>/nfs.mon - NFS service monitoring functions. This
file is optional.
• ${SGCONF}/<SID>/sapms.mon - SAP service monitoring functions.
This file is optional.
• ${SGCONF}/sap.functions - contains all standard runtime logic
used by one package and two package configurations. Do not modify
this file!
• ${SGCONF}/<SID>/sapwas.sh provides the basic control flow for
starting or stopping a SAP instance through a set of function calls.
These function calls themselves are defined in file
${SGCONF}/sap.functions.
Use the one package concept for all configurations where you can put the
database and central instance on one node and have an equally sized
node as a backup. During normal operation, backup nodes can be used as
an idle standby, application server host, or test system. If you are
planning to distribute the database and central instance on two nodes in
the near future apply the two package concept.