Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 272
HA NFS Toolkit Configuration
The cross-mounted filesystems need to be added to a package that
provides HA NFS services. This is usually the dbci package, the db
package or the SAPNFS package. Logon as root to the primary host:
IS750 Installation Step:
Copy the HA NFS toolkit scripts into the package directory. Since the
SGeSAP/LX IPF package directory can have entries for both, a database
and a Central Instance package, it is required to add a package type
prefix to the NFS toolkit files during the copy operation. Otherwise, all
packages of the package directory would act as NFS server. This is
usually not intended. In standard setups, only the combined dbci
package or the dedicated SAPNFS package or the DB package need NFS
server functionality.
In a package directory, only one package of any of these package types
should exist. For the one package concept, renaming is not really
necessary as of today, but it is still recommended to do so to allow future
SGeSAP/LX IPF versions to run without customization of the existing
configuration. Renaming is mandatory for the two package concept. The
monitoring script nfs.mon does not need to be renamed. The following is
an example of copy operations for one package concept:
For SuSE:
cp /opt/cmcluster/nfstoolkit/hanfs.sh \
${SGCONF}/<SID>/dbcihanfs.sh
cp /opt/cmcluster/nfstoolkit/toolkit.sh \
${SGCONF}/<SID>/dbcitoolkit.sh
cp /opt/cmcluster/nfstoolkit/nfs.mon \
${SGCONF}/<SID>
Example copy operations for two package concept:
cp /opt/cmcluster/nfstoolkit/hanfs.sh \
${SGCONF}/<SID>/dbhanfs.sh
cp /opt/cmcluster/nfstoolkit/toolkit.sh \
${SGCONF}/<SID>/dbtoolkit.sh
cp /opt/cmcluster/nfstoolkit/nfs.mon \
${SGCONF}/<SID>