Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3 133
export SGCONF
export SGROOT
export SAPSTAGE
Variables ${SGCONF} and ${SGROOT} can also be set with the following
command:
. /etc/cmcluster.conf
IS400 Installation Step:
Logon as root on the primary host.
Create a SGeSAP/LX package directory. This directory will be used by all
packages that belong to the SAP System with a specific SAP System ID
<SID>.
mkdir -p ${SGCONF}/<SID>
IS410 Installation Step:
In a previous installation step, the command:
rpm -Uhv \
sgesap-toolkit-<version>.product.<linux-os>.<platform>.rpm
has copied all relevant SGeSAP/LX files in the ${SAPSTAGE} staging
area.
The following files need to be copied from the ${SAPSTAGE} staging to the
SGeSAP/LX package directory:
cp ${SAPSTAGE}/sap.functions ${SGCONF}/sap.functions
cp ${SAPSTAGE}/SID/sap.config ${SGCONF}/<SID>/sap.config
cp ${SAPSTAGE}/SID/customer.functions \
${SGCONF}/<SID>/customer.functions
cp ${SAPSTAGE}/SID/sapwas.sh ${SGCONF}/<SID>/sapwas.sh
Enter the package directory ${SGCONF}/<SID>. For each Serviceguard
package that will be configured create:
• a Serviceguard configuration template (xxx.config)
• a Serviceguard control script template (xxx.control.script)
For example for a three package SAP configuration with one database
instance (db) and one central instance (ci) and one dialog instance (d01).