HP Serviceguard Extension for SAP (SGeSAP) manual HA NFS Toolkit Configuration, JMSSERVBASE=3600

#

#Request 25 shares per dialog job.

slo s_dialog { pri = 1;

entity = PRM group dialog

cpushares = 25 shares total per metric m_dialog; }

#

#Report the number of active processes in the dialog workload group.

tune m_dialog {

coll_argv = glance_prm APP_ACTIVE_PROC dialog; }

Optional Step: OS795

Non-default SAP parameters that can be defined include EXEDIR for the SAP access path to the SAP kernel executables (default: /usr/sap/<SID>/SYS/exe/run) and JMSSERV_BASE (default:3900) for the offset from which the message server port of JAVA SCS instances will be calculated as JMSSERV_BASE+<INSTNR>.

For example:

EXEDIR for a Unicode system:

EXEDIR= /usr/sap/<SID>/SYS/exe/runU

JMSSERV_BASE for most XI add-in installations:

JMSSERV_BASE=3600

HA NFS Toolkit Configuration

The cross-mounted file systems need to be added to a package that provides HA NFS services. This is usually the (j)db(j)ci package, the (j)db package or the standalone sapnfs package. Logon as root to the primary host:

NOTE: This installation section does not need to be performed when using the HP Serviceguard Storage Management Suite with CFS and shared access Option 3 (Chapter 2 - Planning the Storage Layout)

Installation Step: LS530

If it is intended to use a standalone HA NFS package, create a directory for the sapnfs Serviceguard package for the configuration and control files similar to the Installation Steps as mentioned in chapter Serviceguard Configuration.

Refer to the documentation Managing High Available NFS for detailed instructions and configuration steps.

The naming convention for a sapnfs package is:

PACKAGE_NAME sapnfs

Installation Step: LS530

If the HA NFS functionality is intended to be integrated into a SGeSAP package, copy the HA NFS toolkit scripts into the package directory.

Since the SGeSAP package directory can have entries for both, a database and a Central Instance package, it is required to add a package type suffix 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 needs NFS server functionality.

In a package directory, only one package of any of these package types should exist. Renaming is mandatory when using multiple package types. The monitoring script nfs.mon does not need to be renamed.

The following is an example of copy operations, whereas <pkg_type> can be db, dbci or sapnfs:

cp /opt/cmcluster/nfs/hanfs.sh /etc/cmcluster/<SID>/hanfs.<pkg_type>

In the package control script <pkg_type>.control.script, specify :

80 Step-by-Step Cluster Conversion