Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

Package Directory Content for the Two-Package Model
NOTE: In this document, references to ${SGCONF} can be replaced by the definition of the variable that
is found in this file /etc/cmcluster.config. The default values are:
• SGCONF=/opt/cmcluster/conf - for SUSE Linux
• SGCONF=/usr/local/cmcluster/conf - for Redhat Linux
In the two package model, the SAP functionality is separated into two Serviceguard packages. One for the
database (DB) and the other for the SAP central instance (CI). The database package contains the file systems
for the NFS mount points. The Serviceguard Extension for SAP on Linux scripts of the two package concept
(db<SID>, ci<SID>) and one additional SAP dialog instance (d<INSTNR><SID) are organized as
follows:
NOTE: All the following files reside in ${SGCONF}/<SID>/ except for ${SGCONF}/sap.functions
• ${SGCONF}/<SID>/db<SID>.config- Serviceguard generic package configuration file as created
with cmmakepkg -p. This file configures the database package. It needs to be customized.
• ${SGCONF}/<SID>/db<SID>.control.script- Serviceguard database package control file for
as created with cmmakepkg -s. It needs to be customized.
• ${SGCONF}/<SID>/ci<SID>.config - Serviceguard generic package configuration file as created
with cmmakepkg -p. This file configures the central instance package. It needs to be customized.
• ${SGCONF}/<SID>/ci<SID>.control.script - Serviceguard SAP central instance package
control file as created with cmmakepkg -s. It needs to be customized.
• ${SGCONF}/<SID>/d<INSTNR><SID>.config - Serviceguard generic package configuration file
as created with cmmakepkg -p. This file configures an optional application server package. It needs
to be customized. This file is optional.
• ${SGCONF}/<SID>/d<INSTNR><SID>.control.script - Serviceguard SAP application server
package control file as created with cmmakepkg -s. It needs to be customized. This file is optional.
• ${SGCONF}/<SID>/sap.config - SAP specific package configuration file. It needs to be customized.
• ${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>/nfs.mon - NFS service monitoring functions. This file is optional.
• ${SGCONF}/<SID>/sapms.mon - SAP message service monitoring functions. This file is optional.
• ${SGCONF}/<SID>/sapdisp.mon - SAP dispatcher monitoring functions. This file is optional.
• ${SGCONF}/<SID>/sapenq.mon - SAP enqueue 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.
• ${SGCONF}/sap.functions - contains all standard runtime logic used by one package and two
package configurations. Do not modify this file.
Figure 1-7 illustrates the required configuration files, and the questions they answer, for an Serviceguard
Extension for SAP on Linux application package in Serviceguard.
Enqueue Replication 27