Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 276
IS830 Installation Step:
The control file(s) created in IS800 need to be edited. Refer to the
document Managing Serviceguard for Linux for general information
about the file content.
Define volume groups, MD RAID devices and logical volumes, IP
addresses and subnets in the package control scripts dbci.sh or db.sh
and ci.sh as appropriate. For more detail information on the LVM
specifications, refer to the section “Planning the LVM layout for
Clustered SAP Environments.” This time enter all filesystems, the
shared and NFS shared ones.
OS835 Optional Step:
The service name and command referencing the SAP message server
monitory must be specified in dbci.sh or ci.sh in order to use the
service defined in the config files dbci.config or ci.config.
Example entries in dbci.sh or ci.sh:
SERVICE_NAME[0]=”dbciCIms”
SERVICE_CMD[0]=”${SGCONF}/CI/sapms.mon”
SERVICE_RESTART[0]=””
IS840 Installation Step:
To enable the HA NFS portion of a database package or a dbci package,
open the package control file and replace the line
HA_APP_SCRIPT=”${0%/*}/toolkit.sh”
with
HA_APP_SCRIPT=”${0%/*}/<pkgtype>toolkit.sh”
Also make sure that the entry HA_APP_SERVER=”pre-IP” gets
uncommented.
IS850 Installation Step:
To enable the SGeSAP/LX IPF portion of a db, dbci or ci package change
the customer_defined_commands sections of the package control script:
For the one package concept the SGeSAP/LX IPF package type control
flow sapdbci.sh is called:
function customer_defined_run_cmds
{
${SGCONF}/<SID>/sapdbci.sh startDBCI <SID> 2>/dev/null