Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Chapter 380
liveCache packages require package type lc. Refer to chapter 4 for lc
package types, and Chapter 5 for MDM package types.
In order to ensure a consistent naming scheme in the following
installation and configuration steps, the SGeSAP package names are
assembled from the package type and SAP System ID:
<pkg_name> = <pkg_type><SID> or, in case of ambiguous results
<pg_name> = <pkg_type><INSTNR><SID>
Examples: dbC11, ciC11, dbciC11, dbcijciC11, jdbC11, jciC11, jdbjciC11,
d01C11, d02C11, ers03C11
There is one exception in the naming convention, which concerns the
dedicated NFS package sapnfs that might serve more than one SAP SID.
For a detailed description and combination restrictions on those
packages, refer to chapter 1 - Designing SGeSAP Cluster Scenarios.
The installation steps cover HP-UX 11i v1, HP-UX 11i v2 and HP-UX 11i
v3 using Serviceguard 11.16 or higher.
NOTE Starting with Serviceguard A.11.18, a new package type was introduced,
called modular packages. Existing packages are now referred to as
legacy packages, which you can still create and use with Serviceguard
A.11.18. However, this version of SGeSAP does not support modular
packages, only legacy packages are supported.
HP Serviceguard 11.18 modular package types are not covered.
The process is split into the following logical tasks:
• SAP Preparation
• HP-UX Configuration
• Cluster Configuration
• Database Configuration
• SAP Application Server Configuration