Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Figure 3-2 Package creation dialog with selections for a single package SGeSAP solution
4. In the Select package type window, enter a package name. The Failover package type is
pre-selected and Multi-Node is disabled. SGeSAP doesn't support Multi-Node. Then click
Next>>.
5. The modules in the Required Modules window are selected by default and can not be
changed. In the Select Core Modules window, you can select additional modules (or deselect
the default recommended selections) by clicking on the check box next to each module that
you want to add (or remove) from the package, then click Next>>. The first of several
consecutive Configure a Modular Package screens will appear. The exact sequence depends
on the previous selections. Each Serviceguard or Serviceguard toolkit module adds one or
more screens to the dialog. Additional information on the SGeSAP specific screens are
described below.
GI020 Select the SAP system that is to be clustered (sgesap/sap_global module)
Most SGeSAP packages are associated with a single SAP system. There is a dialog screen that
allows to select that system as well as a couple of package configuration settings that have impact
on all SGeSAP modules in the package.
1. In many situations, Serviceguard Manager Auto-Discovery can discover the SAP systems
in the cluster. If Serviceguard Manager can discover the SAP systems, you can select a SAP
system ID from a drop-down list. It is always possible to enter one manually.
2. Many SGeSAP package activities depend on system resources that are provided via
mechanisms that are not directly handled by the package. If these resources are not available,
a package operation could fail. Sometimes the resources are just temporarily unavailable
and the package activity would succeed if delayed long enough. To allow that kind of
synchronization, SGeSAP enters loops that poll missing resources regularly and delays or
retries activities that depend on these resources. The package activity continues after the
64 Step-by-Step Cluster Conversion