Serviceguard Extension for SAP on Linux Version A.02.00 Release Notes IA64 Integrity and x86_64, February 2008

What's new in this Version
Version 2.00 provides the following enhancement to the SGeSAP/LX product:
▲ Support of SAP ABAP and JAVA System Central Services
▲ Support of Replicated Enqueue for ABAP and JAVA.
▲ Generic Serviceguard SAP package templates.
Support of SAP ABAP and JAVA System Central Services
SAP Netweaver kernels get installed with a separate instance that isolates mission-critical, central software
components. One or two of these separate instances can now be included in any SGeSAP/LX package to
support SAP JAVA-only, ABAP-only, double-stack, and add-in installations.
Support of Replicated Enqueue for ABAP and JAVA
In case an SAP environment has very high demands regarding guaranteed uptime, it makes sense to activate
a Replicated Enqueue. With this additional mechanism it is possible to failover SAP Central Service Instances
without the need of resetting ongoing transactions. Each SAP Enqueue Service maintains a table of exclusive
locks that can temporarily be granted exclusively to an ongoing transaction. This mechanism avoids
inconsistencies that could be caused by parallel transactions that access the same data in the database
simultaneously. In case of a failure of the Enqueue Service, the table with all locks that have been granted
gets lost. After package failover and restart of the Enqueue Service, all Dialog Instances need to get notified
that the lock table content got lost. As a reaction they cancel ongoing transactions that still hold granted
locks. These transactions need to be restarted. The Enqueue Server has the ability to mirror its memory content
to a Replication Instance that needs to be running on a remote host. SGeSAP/LX supports one or two
Replication Instances to be configured in a package to support SAP JAVA-only, ABAP-only and add-in
installations.
NOTE: On Linux, Enqueue Replication is currently only supported in two-node configurations. It is not yet
possible to use automatically installed Enqueue Replication Service instances (ERS).
Generic Serviceguard SAP package templates
In a SAP environment each software Single Point of Failure (SPOF) defines a SGeSAP package type. SGeSAP
follows a consistent naming convention for these package types. The naming conventions were created to
be independent of SAP software release versions. This allows to use a similar approach for each SPOF,
regardless of whether it appears in the latest SAP Netweaver stack or a SAP software that was released
before the first design of SAP Web Application Server. Older SAP components sometimes only support a
subset of the available clustering options. Many of the software SPOFs can be combined in a single package
to reflect logic dependencies and avoid a high number of packages that would be hard to administer.
SGeSAP provides a high flexibility of what can be combined. The most common combinations are:
• mutual failover scenarios using a two package concept: dbSID, ciSID
• robust failover using a one package concept (ABAP-only or add-in): dbciSID, dbcijciSID
• stand-alone JAVA clusters (e.g. SAP Enterprise Portal): jdbSID, jciSID, jdbjciSID
• Replicated Enqueue packages: arepSID, repSID
• liveCache clusters: lcSID
• ABAP Dialog Instance clusters: dNRSID
Complete HP SGeSAP/LX product documentation is provided in the manual Managing HP Serviceguard
Extension for SAP on Linux (IA64 Integrity and x86_64) (T2392-90013).
10 Serviceguard Extension for SAP on Linux Version A.02.00 Release Notes