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 1 33
Package Directory Content for the One-Package
Model
In the one package model, the SAP functionality-database and central
instance-along with the highly available NFS server are all been placed
in one Serviceguard package.
The SGeSAP/LX IPF scripts of the one package concept are organized as
follows:
• ${SGCONF}/sg.conf - cluster configuration file of Serviceguard.
• ${SGCONF}/<SID>/dbci.config - Serviceguard generic package
configuration 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 -s. This file
configures an optional application server package. 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>/dbci.sh - Serviceguard package control file as
created with cmmakepkg -p. It needs to be customized.
• ${SGCONF}/<SID>/d<INSTNR><SID>.sh - Serviceguard SAP
application server package control file as created with cmmakepkg
-p. It needs to be customized. This file is optional.
• ${SGCONF}/<SID>/dbcihanfs.sh - contains NFS specific runtime
logic used during package startup or shutdown. It needs to be
customized. The file is optional, if a central HA NFS package is used.
• ${SGCONF}/<SID>/sapdbci.sh - contains database and SAP specific
flowlogic for package startup and package shutdown. This file is
valid for one 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.