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

• 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
Add MDM virtual IP addresses and hostnames to /etc/hosts.
Virtual IP addresses will be enabled on the cluster node where the corresponding Serviceguard
package is started and disabled when the package is stopped. The MO7 NFS files systems will
be accessible under 172.16.11.95/nfsMO7reloc for both (a) = ONE as well as for (b) =
FOUR configurations as described above.
For the (a) ONE package configuration the database will be accessible under the
172.16.11.96/mdbreloc virtual IP address/hostname, all the MDM components under the
172.16.11.97/mdsreloc virtual IP address/hostname.
For the (a) FOUR package configuration the database will be accessible under the
172.16.11.96/mdbreloc virtual IP address/hostname, the MDS component will use the
172.16.11.97/mdsreloc virtual IP address/hostname, 172.16.11.98/mdisreloc will be
used for MDIS and 172.16.11.99/mdssreloc will be used for MDSS.
/etc/hosts
----------
172.16.11.93 clunode1 # cluster node 1
172.16.11.94 clunode2 # cluster node 2
172.16.11.95 nfsMO7reloc # MDM reloc address for NFS
172.16.11.96 mdbreloc # MDM reloc address for DB
172.16.11.97 mdsreloc # MDM reloc address for MDS
172.16.11.98 mdisreloc # MDM reloc address for MDIS
172.16.11.99 mdssreloc # MDM reloc address for MDSS
Setup Step: MDM020
Scan for new disk devices on the first cluster node (clunode1). Run ioscan and insf to
probe/install the disk devices. These will be used for the following relocateable file systems:
/usr/sap/MO7/MDIS01, /usr/sap/MO7/MDIS02, /usr/sap/MO7/MDSS03,
164 SAP Master Data Management (MDM)