Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Understanding Serviceguard Extension for SAP on Integrity Linux
Planning the LVM Layout for Clustered SAP Environments
Chapter 136
• ${SGCONF}/<SID>/sapci.sh - contains SAP specific flowlogic for
central instance package startup and shutdown. This file is valid for
two package configurations only. It depends on <SID>/sap.config,
<SID>/customer.functions, and sap.functions.
• ${SGCONF}/<SID>/sapapp.sh - contains flowlogic for a SAP
application server package startup and shutdown. It depends on
<SID>/sap.config, <SID>/customer.functions, and
sap.functions. This file is optional.
• ${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}/sap.functions - contains all standard runtime logic
used by one package and two package configurations. Do not modify
this file!
• ${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 /opt/cmcluster/conf/sap.functions itself. Any
function provided in customer.functions overrides its equivalent in
sap.functions.
• ${SGCONF}/<SID>/nfs.mon - NFS service monitoring functions. This
file is optional.
• ${SGCONF}/<SID>/sapms.mon - SAP service monitoring functions.
This file is optional.