Serviceguard Extension for SAP Release Notes Version B.05.10, December 2012

Additional enhancements
• All SGeSAP service monitors now support the Serviceguard package maintenance mode for
modular packages. While a package runs in maintenance mode, it is possible to manually
start, stop, and manipulate the SAP software components in the package without risking any
service monitor to fail. Monitoring will continue to operate automatically as soon as the package
leaves maintenance mode.
• For modular packages, now there is failback to traditional SAP startup, shutdown, and
monitoring operations, in case the SAP startup framework is either not configured correctly
or fails to work.
A new package parameter sapcontrol_usage specifies whether the SAP Netweaver 7
SAPcontrol Web Service Interface and the SAP startup agent framework commands (for
example, sapcontrol ) are to be used to startup, shutdown, and monitor SAP software
components.
The SGeSAP service monitors for central services (sapms.mon, sapenq.mon, and
sapenqr.mon) restarts the SAP instance startup agent software locally, if it is required for
the monitoring and became unavailable due to software failure or shutdown.
• For SAP kernel versions below 7.10, the startup framework will no longer be used at all, if it
is not configured for a given instance. Starting with kernel version 7.10, SGeSAP will
(un-)register the instances of a package in the startup framework as part of the package start
and stop operations.
• cmcheckconf(1m) command can now be used to verify a combination of HA NFS and
SGeSAP in a single package.
• If system specific ORACLE SPFILE of PFILE exists—the configuration parameters are now read
and set from this instead of a generic init.ora. The SPFILE has preference.
• Localizations of SGeSAP GUI functionality is included with the localizations available for the
HP Serviceguard Manager plug-in to System Management Homepage.
• The sgesap/sapinstance module now supports SAP Gateway instances. You can configure
an optional service monitor sapgw.mon in the package to check the health of running Gateway
instance. Gateway instances are discovered by the guided package configuration method in
Serviceguard Manager.
HP Serviceguard Manager configuration procedure for sgesap/sapinstance provides an option
to include Gateway instances in the packages.
• The sgesap/sapextinstance module now supports SAP Diagnostic Agents.
• The sgesap/sapinstance module now supports SAP Web Dispatcher instances installed with
sapinst. The sgesap/sapinfra module supports the SAP Web Dispatcher executeable, imported
and bootstrapped in a separate directory. In both the cases, an optional service monitor
sapwebdisp.mon can be configured in the package to check Web Dispatcher health during
operation. Web Dispatcher instances are discovered by the guided package configuration.
They get offered for inclusion in packages as part of the sgesap/sapinstance HP Serviceguard
Manager configuration step.
• The hot standby liveCache functionality now supports cluster device special files and links to
devspaces.
When creating MaxDB devspaces, the path defined in the location parameter within the
database configuration of the devspace can reference a link.
• It is no longer required to allow remote root access via remsh or ssh to all servers configured
with sgesap/sapextinstance. Remote operations are triggered as SAP system administrator (a
regular UNIX user).
What's In this Version 9