Managing Serviceguard Extension for SAP Version B.05.10, September 2010

For performance reasons, the MDM database (MDB) file systems will be based on relocateable
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/MO7.
NOTE: In this installation the non-relocatable /home/mo7adm, /usr/sap and the
/usr/sap/MO7/SID file systems are fairly small file systems. The HP-UX system disk had
adequate free capacity and therefore these file systems were created on the system disk. Should
file system space be an issue on the system disk, additional disk space will have to be allocated
and configured in installation steps described below.
Single or Multiple MDM Serviceguard Package Configurations
MDM servers with SGeSAP can be installed either as a "Single" Serviceguard package (ONE
package) OR as "Multiple" Serviceguard packages (FOUR). The MDM 7.10 installation guide
calls the one package configuration a “Central” or “Central System” installation, the multiple
package configuration is called a “Distributed” MDM installation.
Single MDM Serviceguard Package (ONE)
• In the case of "Single" MDM Serviceguard package all four MDM components (mdb mds
mdis mdss) are always started and stopped together on "one" cluster node—the node on
which the Serviceguard package itself is started or stopped on. All four MDM components
are combined or grouped together to form a “MDM Central System mcs”.
• The naming convention for the Serviceguard packages is: mcs<SID>. The string ID is used
as a placeholder for a <SID> SAP System ID and is set to MO7 for this installation.
• The mcsMO7 package contains code for dependency checks: it will ensure that the MDM
components are started and stopped in the correct order: mdb -> mds -> mdis ->
mdss—and in the reverse order for stop.
• The advantage of the Single MDM Serviceguard package is a simpler setup—less steps are
involved in setting up and running the configuration—but with the restriction that all four
MDM server components always have to run together on the same cluster node. It is assumed
the majority of MDM installations are of this type.
Multiple MDM Serviceguard packages (FOUR)
• In the case of "Multiple" MDM Serviceguard packages each of the four MDM components
(mdb, mds, mdis, and mdss) is configured and run in a separate (mdb<SID>, mds<SID>,
mdss<SID>, mdis<SID>) Serviceguard package. This is called a distributed MDM
installation. So in the case of a four node cluster each MDM Serviceguard package could be
configured to run on it's own cluster node and by this distribute load over the four cluster
nodes.
• The naming convention for the Serviceguard packages is: mdb<SID>—the string mdb stands
for MDM database components and is required; the string <SID> is used as a placeholder
for a System ID. In this guide MO7 will be used as the example SID. The name of the other
Serviceguard packages is derived from: mds stands for MDM master data server components,
mdis stands for MDM import server components and mdss stands for MDM syndication
server components.
• The advantage of Multiple MDM Serviceguard packages is flexibility: it is possible to balance
the load by distributing the MDM servers over cluster nodes—but with the cost of requiring
more steps to install and run the system.
Installation steps for MDM
Setup Step: MDM010
156 SAP Master Data Management (MDM)