Managing HP Serviceguard Extension for SAP for Linux (May 2013)
To help in decision making, you can move the cursor over the configurable parameters, and
view the tool tips that provide information about the parameter.
10. Click Next >> and another Create a Modular Package screens appears.
Step 2 of X: Configure SGeSAP parameters global to all clustered SAP software
(sgesap/sap_global) .
Fill in the required fields and accept or edit the default settings.
Click Next >>. Another Create a Modular Package screen appears with the following message
at the top of the screen:
Step 3 of X: Configure SGeSAP SAP instance parameters (sgesap/sapinstance) .
Fill in the required fields, and accept or edit the default settings.
Click Next >> until the mandatory <SID> can be entered.
Figure 16 Configuration screen: SAP System ID
11. After you are done with all the Create a Modular Package configuration screens, the Verify
and submit configuration change screen appears. Use the Check Configuration and Apply
Configuration buttons to confirm and apply your changes.
Creating the package configuration file with the CLI
NOTE: To create a package you can use either Serviceguard Manager GUI or the CLI. This
section describes CLI steps and the GUI steps are described in “Creating the package with the
Serviceguard Manager” (page 53) the section.
Invoke cmmakepkg –n <pkg> -m sgesap/sapinstance [-m ...] <pkg>.config
command.
Initially no SGeSAP attributes are enabled except for the mandatory attribute
sgesap/sap_global/sap_system, which must be set to the SAP SID designated for the
installation. All others SGeSAP related attributes must be left unspecified at this point.
For a database package, specify the module sgesap/dbinstance. An sgesap/dbinstance
does not have any mandatory attributes.
For a combined package, both sgesap/sapinstance and sgesap/dbinstance module must
be specified. Other combinations are also possible.
NOTE: Specifying the SGeSAP modules automatically adds the necessary Serviceguard modules
such as volume_group or filesystem, or package_ip required for a base package.
Infrastructure setup, pre-installation preparation (Phase 1) 55