Serviceguard Extension for SAP Version A.06.00 Release Notes for Linux

HP SGeSAP/LX software monitors provide local software restart capabilities in accordance to the
SAP HA certification requirements. The enqueue replication monitor is enabled to perform up to
three local restart attempts for the failing replication software before switching the package. The
message server monitor cooperates with the SAP startup framework to implement similar behavior.
The Central Service monitors and the replication monitor also attempt to locally restart failed or
stopped components of the SAP startup framework.
SAP HA interface support
The SAP Netweaver startup framework supports a programming interface that allows making it
cluster-aware. HP SGeSAP/LX delivers a shared library that implements this interface.
SAP administrators can start and stop clustered SAP instances with any standard SAP method that
uses the SAP startup framework (for example, MC, MMC, sapcontrol etc.) without the requirement
that operating system administrators prepare the cluster for this operation upfront.
Software health monitoring detects these triggered stops and visualize them as alerts in the
Serviceguard Manager GUI. The software health monitoring part of the cluster package is suspended
while the software is manually halted. Health monitoring automatically continues to operate after
restart of the instance with standard SAP methods.
Optionally, cluster administrators can configure SGeSAP to block any administrator-triggered
instance halt attempt. Only cluster operations will then be able to stop instances. This minimizes
the risk that happens with the SAP startup framework that generally enables SAP administrators to
trigger instance stops on remote servers.
The stop block can be removed and added anytime while the package is up.
The HA interface implementation is tested with the SAP Rolling Kernel Switch technology. HP
SGeSAP/LX can also be configured to avoid using the SAP startup framework or to use conventional
SAP startup, shutdown, and monitoring methods as a fallback if the startup framework is not working
properly.
Guided package configuration
HP SGeSAP/LX can detect SAP installations on cluster nodes. It can parse the instance configurations
and converts them into cluster configuration input.
All HP SGeSAP/LX modules can be configured as part of HP Serviceguard Manager GUI dialogs.
The dialog screen forms get pre-populated with recommended settings based on the detected
instance configurations. This significantly reduces keyboard-time required to configure packages
and avoids misconfigurations.
For standard clusters that follow the SAP recommendations, it is only required to specify which
instances are to be clustered and not how to cluster them. The recommended settings can be
reviewed and changed before they become applied.
The command deploysappkgs(1) is further more able to automatically create configurations
for all mandatory packages to a pre-installed SAP system in a single step. The created cluster
configuration files can be reviewed and changed and subsequently applied.
deploysappkgs(1) can also be used as part of ongoing change management operations to
verify how existing cluster package configurations must be altered to reflect recent changes to the
application configuration.
SAP-specific node-local cluster verification
SGeSAP maintains a list of rules that specify local configuration requirements on potential secondary
nodes. These requirements are checked with every execution of the cmcheckconf(1m) or
cmapplyconf(1m) commands on a modular-style SGeSAP package. Use of cmcheckconf(1m)
command for a SGeSAP package that is in a running condition helps to detect erroneous local
configurations that negatively impacts the capability to failover a SGeSAP package to a certain
node.
SAP-specific node-local cluster verification 7