Managing Serviceguard Extension for SAP, December 2007

SAP Master Data Management (MDM)
Installation and Configuration Considerations
Chapter 5 247
Multiple MDM Serviceguard packages (FOUR+ONE)
• In the case of "Multiple" MDM Serviceguard packages each of the four
MDM component (mdb, mds, mdis and mdss) is configured and run in a
separate (mdbMDM, mdsMDM, mdssMDM, mdisMDM) Serviceguard package.
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: mdbMDM -
the string mdb stands for mdm database components and is required;
the string MDM is used as a placeholder for a System ID and can be set
to any value. 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.
• A “fifth” Serviceguard package called masterMDM must also be
configured for this configuration type. It will be used to ensure that
cluster-wide the four MDM Serviceguard packages are started in the
correct order: mdbMDM -> mdsMDM -> mdisMDM -> mdssMDM regardless of
on which cluster node they are started. The same is true for stopping
the packages – the reverse order will be used.
• 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.