Serviceguard Extension for SAP Version B.05.00 Release Notes (April 2010)

Serviceguard cluster configuration. Only one central configuration has to be maintained for each
package.
• SGeSAP modular package configuration files can now be created with the cmmakepkg(1m) command.
SGeSAP package creation supports three verbosity levels.
• SGeSAP modular package configuration changes can be verified using the cmcheckconf(1m) command
before they become effective. SGeSAP detects erroneous SAP package configurations and prevents
that they get applied with cmapplyconf(1m). All SAP cluster configuration changes are performed as
atomic, consistent operations across all cluster nodes.
• SGeSAP modular packages maintain internal versioning, which allows to keep packages with different
versions within the same cluster. In particular, this allows to add new SGeSAP packages for additional
SAP instances without the requirement to upgrade any already existing SGeSAP package to the same
SGeSAP revision simultaneously.
• SGeSAP modular packages take advantage of internal queries to gather information about the clustered
SAP landscape. As a result, the number of required manual configuration steps got reduced as compared
to SGeSAP legacy packages that provide the same functionality.
• SGeSAP provides five verbosity levels for package logging information. The generic Serviceguard log
level setting is effective for all SGeSAP modules.
SAP Cluster Module Enablement's
▲ SGeSAP B.05.00 introduces the modular package specification sgesap/sapinstance. It can be
used to configure failover cluster services for:
• SAP System Central Services
• SAP Replication Instance Services
• SAP ABAP Application Services
• SAP JAVA Application Services
• combined ABAP+JAVA Application Services
• Software service monitors are provided that implement software health monitoring for one or two
message services in any of the sgesap/sapinstance packages. The Automated Enqueue Replication
feature is available with the Replication Instance Service modules and no longer requires special naming
conventions to be considered.
• SGeSAP B.05.00 introduces the modular package specification sgesap/dbinstance. It can be used
to easily realize failover cluster services for:
• SAP Oracle database services
• SAP MAXDB database services
• Modularized database packages will try to use database operations as provided by SAP. In some
cases, if the SAP provided operations fail, there is a fallback to generic database routines.
• SGeSAP B.05.00 introduces the modular package specification sgesap/livecache. It can be used
to easily realize failover or hot standby cluster services for SAP Livecache instances.
• SGeSAP B.05.00 introduces the modular package specification sgesap/sapextinstance to allow
to trigger start, stop and/or restart of non-clustered SAP application server components as part of a
package operation.
• SGeSAP B.05.00 introduces the modular package specification sgesap/sapinfra to failover
standalone SAP software infrastructure tools that provide SAP-specific monitoring and routing.
SAP Startup Framework Integration
SGeSAP B.05.00 module packages integrate into environments that use the SAP startup services and the
SAP host services. SGeSAP packages can register, start and stop the instance startup services of clustered
SAP instance as part of the package operation. Automated registration is only available with SAP software
based on SAP kernel 7.10 or higher. With these operations, the SAP landscape will always provide a
consistent view on available SAP services.
10 Serviceguard Extension for SAP Version B.05.00 Release Notes