Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

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 execute runt the command ssh-keygen –t rsa as user root and <sid>adm
on each host.
This will create files for the private (id.rsa) and public key (id_rsa.pub) in the user’s .ssh directory.
The public key then needs to be distributed to the other hosts. This can be accomplished by running
the command ssh-copy-id –i id_rsa.pub user@host. This will add the user’s public key
to the authorized_keys (not authorized_keys2) on the target host.
On each cluster node this has to be executed as the root user and host being one of the other
cluster nodes in turn. On each clusternode and for each external application server
appserverinvoke the ssh-copy-id … user@host command twice, replacing the user@host
string with <sid>adm@appserver and root@appserver.
It is also recommended to pre-populate the known hosts file (/etc/ssh/ssh_known_hosts) on each
cluster node by executing
ssh-keyscan list-of-remote-hosts >> /etc/ssh/ssh_known_hosts
This avoids the first login from the remote host hanging in the fingerprint.
After finishing this section a password less login must be possible between
• root user on all cluster nodes
• root andsidadm to external appservers
Completing SGeSAP package creation (Phase 3b) 71