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 35
Package Directory Content for the Two-Package
Model
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
filesystems for the NFS mount points. The SGeSAP/LX IPF scripts of the
two package concept are organized as follows:
• ${SGCONF}/<SID>/db.config - Serviceguard generic package
configuration file as created with cmmakepkg -s. This file configures
the database package. It needs to be customized.
• ${SGCONF}/<SID>/ci.config - Serviceguard generic package
configuration file as created with cmmakepkg -s. This file configures
the central instance package. 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>/db.sh - Serviceguard database package control
file for as created with cmmakepkg -p. It needs to be customized.
• ${SGCONF}/<SID>/ci.sh - Serviceguard SAP central instance
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>/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 HA NFS package is used.
• ${SGCONF}/<SID>/sapdb.sh - contains database specific flowlogic
for database 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.