Managing HP Serviceguard Extension for SAP for Linux, December 2013

DescriptionValueParameter
User credential for executing MDM CLIX
commands
Adminsgesap/mdm_spec/mdm_credentialspec_user
Password credential for executing MDM CLIX
commands
sgesap/mdm_spec/mdm_credentialspec_password
The following contains some selected SGeSAP parameters relevant to MDM repository configuration.
For more information, see package configuration file.
DescriptionValueParameter
MDM repository namePRODUCT_HA_REPsgesap/mdm_spec/mdm_repositoryspec_repname
DBMS instance nameMO7sgesap/mdm_spec/mdm_repositoryspec_dbsid
DBMS instance type: "o" stands for Oracleosgesap/mdm_spec/mdm_repositoryspec_dbtype
DBMS user namemo7admsgesap/mdm_spec/mdm_repositoryspec_dbuser
DBMS passwordabcxyzsgesap/mdm_spec/mdm_repositoryspec_dbpasswd
5.5.7 Module sg/services – SGeSAP monitors
Depending on the instance type configured in the package, SGeSAP monitors can be configured
with this module to check the health of the instance. Also, a monitor for the DB used can also be
configured.
Table 23 Module sg/services – SGeSAP monitors parameter
DescriptionValueParameter
Unique name. A combination of package name
and monitor type is recommend
CM2CIdispservice_name
Path to monitor script$SGCONF/monitors/sgesap/sapdisp.monservice_cmd
Usually, no restarts must be configured for a
SGeSAP monitor to have an immediate failover if
the instance fails.
0service_restart
No fast fail configuredNoservice_fast_fail
> 0 to give monitor some time to cleanup after it
received the TERM signal.
5service_halt_timeout
Serviceguard Manager guided package setup pre-populates the services screen with the monitors
appropriate for the instance if the service module has been selected to be included in the package.
Configure a database monitor with:
service_name <pkg>datab
service_cmd $SGCONF/monitors/sgesap/sapdatab.mon
All other values are set up as described in the Table 23 (page 78) table.
5.5.8 Module sg/generic_resource – SGeSAP enqor resource
A generic resources has to be setup for SCS and ERS packages, if the SGeSAP enqueue
follow-and-push mechanism is used. There is a common resource for each SCS/ERS pair. The
naming schema of the resource follows the below convention:
sgesap.enqor<SID>_<ERS>
For example:
78 Clustering SAP Netweaver using SGeSAP packages