HP Serviceguard Extension for SAP (SGeSAP) Legacy Package Configuration, Package Name dbciC11

Legacy Package Configuration

This section describes the cluster software configuration with the following topics:

•Serviceguard Configuration

•SGeSAP Configuration

•Global Default Settings

Serviceguard Configuration

Refer to the standard Serviceguard manual Managing Serviceguard to learn about creating and editing a cluster configuration file and how to apply it to initialize a cluster with cmquerycl(1m) and cmapplyconf(1m). The following section assumes that a cluster is up and running on the intended primary node and all failover nodes.

Logon as root on the primary host.

Installation Step: LS400

Create a Serviceguard 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 /etc/cmcluster/<SID>

Installation Step: LS410

The swinstall process copied relevant files to a staging area at /opt/cmcluster/sap for reference.

The following files need to be copied from the repository to the SAP package directory:

cp /opt/cmcluster/sap/sap.functions/etc/cmcluster/sap.functions

cp /opt/cmcluster/sap/SID/sap.config/etc/cmcluster/<SID>/sap.config

cp /opt/cmcluster/sap/SID/customer.functions\

/etc/cmcluster/<SID>/customer.functions

SGeSAP automatically detects the package setup with the desired SAP component configured.

cp /opt/cmcluster/sap/SID/sapwas.cntl/etc/cmcluster/<SID>/sapwas.cntl

Installation Step: LS420

Enter the package directory /etc/cmcluster/<SID>. Create standard package configuration and control files for each package. The files might already exist, if the SAP System got installed onto virtual IP addresses.

Decide which package types are needed in the high availability environment depending on the installed SAP System generate a control and configuration file for each package. These files should always be created using the standard Serviceguard commands. The package types are recommended to be named <pkg_name>.control.script for a control file and <pkg_name>.config for a configuration file.

For any kind of package (substitute <pkg_type> with your package type):

cmmakepkg -s/etc/cmcluster/<SID>/<pkg_name>.control.script

cmmakepkg -p/etc/cmcluster/<SID>/<pkg_name>.config

Installation Step: LS430

The created configuration file(s) need to be edited.

Refer to the Managing Serviceguard User's Guide for general information about the file content. The naming convention <pkg_name> should be used for the PACKAGE_NAME parameter.

For example:

PACKAGE NAME dbciC11

Specify NODE_NAME entries for all hosts on which the package should be able to run.

Specify the package control script names in the package configuration files:

Specify in /etc/cmcluster/<SID>/<pkg_name>.config:

RUN_SCRIPT /etc/cmcluster/<SID>/<pkg_name>.control.script

HALT_SCRIPT /etc/cmcluster/ <SID>/<pkg_name>.control.script

Legacy Package Configuration 65