Managing Serviceguard Extension for SAP, December 2007

SAP Master Data Management (MDM)
Installation and Configuration Considerations
Chapter 5294
MDM254 Setup Step:
(b) Multiple - Starting and Stopping the masterMDM package
The masterMDM package is responsible for starting other Serviceguard
packages (mdmDB, mdsMDM, mdisMDM and mdssMDM) in a cluster in the
required order as specified in file sap.config. With this information, the
masterMDM will run the appropriate cmrunpkg commands to start the
packages. Before executing cmrunpkg make sure that the MDM server
packages (mdmDB, mdsMDM, mdisMDM and mdssMDM) are halted from the
previous installation tasks.
The command cmhaltpkg masterMDM will stop all MDM Serviceguard
packages in the reverse order as they were started.
NOTE Since the masterMDM package uses standard cmrunpkg commands to
start other packages – the node on which to run the underlying
Serviceguard packages on - is obtained from the variable NODE_NAME
as specified in files mdmMDM.config, mdsMDM.config, mdisMDM.config
and mdssMDM.config.
cmrunpkg masterMDM
cmrunpkg : Completed successfully on all packages
specified.
cmhaltpkg masterMDM
MDM256 Setup Step:
Serviceguard and MDM package log files
The log files for Serviceguard packages and the command executed can
be found in the following directories:
nfsMDM log files:
/etc/cmcluster/MDMNFS/nfsMDM.control.script.log
mgroupMDM log files:
/etc/cmcluster/MDM/mgroupMDM.control.script.log