Managing HP Serviceguard Extension for SAP for Linux (May 2013)

Module sg/dependency – SGeSAP enqor MNP dependency
SCS and ERS packages taking part in the SGeSAP follow-and-push mechanism must have
same-node/up dependency with the enqor MNP. The attributes have to be set as follows:
dependency_name enqor_dep
dependency_location same_node
dependency_condition enqor = UP
Servicegurad Manager guided configuration offers the correct values preselected for the dependency
screen only if a SGeSAP enqor MNP is already setup.
The deploysappkgs script supports the dependency module for enqor.
Module sgesap/enqor – SGeSAP enqor MNP template
This module is used to setup the SGeSAP enqor MNP. It has no attributes to be configured. A
SGeSAP enqor MNP is only mandatory in the SCS/ERS follow-and-push context.
The sgesap/enqor module must not be combined with any other SGeSAP module. A configured
enqor MNP is a prerequisite for the correct function of the sg/dependency and sg/generic_resource
attributes configured into a sapinstance package.
For the configuration of the sg/dependency and sg/generic_resource modules described above
the enqor MNP is a prerequisite.
On command line a enqor MNP can be created with:
cmmakepkg –n enqor –m sgesap/enqor enqor.config
The resulting enqor.config can be applied without editing.
The Serviceguard Manager offers SAP Netweaver Operations Resource in the Select the SAP
Components in the Package screen for configuring the enqor MNP.
deploysappkgs creates the enqor.config file when the follow-and-push mechanism is the
recommended way of operation for the creates SCS/ERS packages (and no enqor MNP is not
configured yet). In such a situation deploysappkgs will also extend existing SCS/ERS package
with the requires generic_resource and dependency module and their attributes.
Verification of Phase 3:
• Start and stop packages on each configured node. When testing SGeSAP follow-and-push
mechanism the enqor MNP package must be up. This will restrict the possible nodes for SCS
and ERS package startup.
• Make sure client applications (dialog instances) can connect
Configuring sgesap/sapextinstance, sgesap/sapinfra and sgesap/livecache
This section describes configuring SGeSAP toolkit with sgesap/sapextinstance, sgesap/sapinfra
and sgesap/livecache parameters.
Remote access between cluster nodes and to external application servers
For external applications servers configured in a package, remote access between the cluster nodes
and between external hosts needs to be enabled. Root access between cluster hosts must be enabled
and the users <sid>adm and root from the cluster (in this case also a cluster host can assume the
role of an external appserver) must be allowed to run as <sid>adm on the from external
application servers. It is recommended to use ssh(1). Usage of rsh is discouraged.
To accomplish this, the following steps are necessary:
• Create ssh keys for root and <sid>adm
• Distribute those keys to allow access
To generate the keys as root user and as <sid>adm user run the ssh-keygen –t rsa command
on each host.
72 Clustering SAP using SGeSAP packages