Managing Serviceguard Extension for SAP Version B.05.10, December 2012

In addition to standard Serviceguard package dependencies, SGeSAP packages keep track of
SAP enqueue replication relationships.
• Click on the Dependencies tab on the Serviceguard Manager Main page to bring up the
Dependencies screen. The enqueue replication relationships are displayed using dashed
arrows, while standard package dependencies are given in solid lines.
Figure 8 SAP replication relationship
To update (edit) a SGeSAP toolkit package configuration:
• From the View window on the right hand side of the Serviceguard Manager Main page, right
click on a package icon to bring up the Operations Menu, then click Edit a Package to bring
up the first in a series of screens where you can make edits to package properties.
• A package can also be edited by clicking the Packages tab on the Serviceguard Manager
Main page to bring up the Packages screen, then click on the package you want to update
in the Package Name column to bring up the Package Properties screen. Click Edit This Package
in the upper left-hand corner of the Package Properties screen to bring up the first in a series
of screens where you can make edits to package properties.
Performing standard tasks with SAP's startup framework
Consider an SGeSAP package with one or more SAP instances. These instances are monitored
for health with the corresponding SGeSAP monitors.
With previous releases, if one of these instances is manually stopped with commands external to
SGeSAP (for example, the command sapcontrol -nr xx -function Stop was executed)
, the SGeSAP monitors detect a failing instance. This results in failover of the package to another
node.
Starting with SGeSAP version B.05.10 system administrators have the option to (externally to
SGeSAP) start and stop NetWeaver instances for maintenance reasons. This will not trigger a
Performing standard tasks with SAP's startup framework 21