Managing Serviceguard Extension for SAP Version B.05.10, December 2012

The MDM server components that are relevant for the installation and configuration of the SGeSAP
scripts are: MDS, MDIS, MDSS and MDB.
NOTE: Go to http://service.sap.com/installmdm to access the SAP Service Marketplace
web site, where you can then access the required SAP documentation needed for this installation.
You must be a SAP registered user to access these documents.
MDM 5.5 SP05 - Master Guide
MDM 5.5 SP05 - Console Reference Guide
MDM 5.5 SP05 - Release Notes
MDM 5.5 SP05 - Installation Guide
MDM 5.5 SP05 - Solution Operation Guide
As of the writing of this document, the following SAP notes contain the most recent information on
the MDM installation as well as corrections to the installation:
1025897 - MDM 5.5 SP05 Release Note
822018 - MDM 5.5 Release Restriction Note
Prerequisites
You must having the following installed and already configured:
• HP-UX and Serviceguard
• A Serviceguard cluster with at least two nodes attached to the network. (Node names:
clunode1 and clunode2)
• Any shared storage supported by Serviceguard. The shared storage used for this configuration
is based on (Enterprise Virtual Array) EVA - a fibre channel based storage solution.
NOTE: Refer to the latest Managing Serviceguard manual for Serviceguard installation instructions
at www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard —> User guide.
The MDM SGeSAP File System Layout
The following file system layout will be used for the MDM Server components.
/oracle/MDM
For performance reasons, the MDM database (MDB) file systems will be based on local and
relocatable storage (the physical storage volume / file system can relocate between the cluster
nodes, but only ONE node in the cluster will mount the file system). The file system will be mounted
by the cluster node on which the database instance is started/running. The directory mount point
is /oracle/MDM. All I/O is local to the cluster node.
/home/mdmuser
/export/home/mdmuser
These are the file systems for the MDM server components (These are MDS, MDSS and MDIS) that
are of dynamic in nature - e.g. configuration files, log files, import files, export files). These file
systems will be based on NFS. One cluster node mounts the physical storage volume and runs as
a NFS server, exporting the file systems to NFS clients. Mount point for the NFS server file system
is /export/home/mdmuser.
All nodes in the cluster mount the NFS exported files systems as NFS clients. Mount point for the
NFS client file system is /home/mdmuser. Each of the MDM server (mds, mdss and mdis)
components will use it's own directory (e.g.: /home/mdmuser/mds, /home/mdmuser/mdss,
/home/mdmuser/mdis) within /home/mdmuser.
Should the NFS server node fail - then the storage volume will be relocated to another cluster node,
which then will take over the NFS server part.
Installation and Configuration Considerations for MDM 5.5 in a Serviceguard legacy environment 139