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 1 31
Package Directory Content for the One-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 one package model, the SAP functionality-database and central
instance-along with the highly available NFS server have all been placed
in one Serviceguard package. The following convention was used for the
postfix name:
• “.config” for the Serviceguard / SGeSAP/LX package configuration
file
• “.control.script" for the Serviceguard / SGeSAP/LX package control
script
The Serviceguard Extension for SAP on Linux scripts of the one package
concept are organized as follows:
• ${SGCONF}/<SID>/dbci<SID>.config - Serviceguard generic
package configuration file as created with cmmakepkg -p. It needs to
be customized.
• ${SGCONF}/<SID>/dbci<SID>.control.script - Serviceguard
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.