Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Create the SGeSAP package configuration file. The file might already exist, if the SAP System got
installed onto virtual IP addresses .
The SGeSAP configuration file is usually created with one of the following commands:
cmmakepkg -m sgesap/all > ./sap.config — for a configuration file that covers all
available SGeSAP module functionality and combines all SGeSAP modules in a single package.
cmmakepkg -m sgesap/sapinstance > ./sap.config — for a configuration file that is
meant to create a package that clusters one or more SAP instances of a single SAP system.
cmmakepkg -m sgesap/dbinstance > ./sap.config — for a configuration file that is
meant to create a package that clusters the database service underlying a single SAP system.
cmmakepkg -m sgesap/sapinstance –m sgesap/dbinstance > ./sap.config —
for a configuration file that is meant to create a package that clusters a central system consisting
of the database and one or more SAP instances of a single SAP system. All parts run on the same
node at the same time.
NOTE: The System Central Service instances can be referred to by using SAP instance type
naming conventions.
cmmakepkg -m sgesap/scs >./scs.config and cmmakepkg -m sgesap/ers
>./ers.config — separates System Central Service and Enqueue Replication into two packages.
cmmakepkg -m sgesap/scs -m sgesap/ers > ./sap.config — would immediately
issue an error message, because System Central Services and Enqueue Replication cannot share
the same package.
NOTE: SGeSAP modules can be referred to by using SGeSAP legacy package types.
cmmakepkg -m sgesap/db -m sgesap/ci > ./sap.config — creates a single package
configuration file for database and SAP instance(s) (one package concept).
cmmakepkg -m sgesap/db > ./db.config and cmmakepkg -m sgesap/ci >
./sap.config — separates database and SAP instances into two package configuration files
(two package concept).
Optional Step: OS610
SGeSAP performs activities specific to the database you use. Specify the underlying database
vendor using the DB parameter.
Possible options include oracle, maxdb, db2, and sybase. Refer to the SGeSAP release notes
to see whether the required vendor is available for the SAP application component.
Example:
db_vendor=oracle
In the subsection for the DB component there is an optional paragraph for Oracle and
SAPDB/MaxDB database parameters. Depending on your need for special HA setups and
configurations have a look at those parameters and their description.
Preparation Step: MS405
If you want to use SGeSAP's capability to perform Netweaver software health monitoring:
Activate monitoring rights for the <sid>adm user in the cluster configuration file with the following
settings:
<sid>admUSER_NAME
ANY_SERVICEGUARD_NODEUSER_HOST
monitorUSER_ROLE
Run the cmapplyconf -C command to apply the setting.
80 Step-by-Step Cluster Conversion