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

SERVICE_NAME[0]="mgroupMDMmon"
SERVICE_CMD[0]="/etc/cmcluster/MDM/sapmdm.sh check mgroup"
SERVICE_RESTART[0]=""
To activate the changes in the configuration files run the following commands:
cmapplyconf -P /etc/cmcluster/MDM/mgroupMDM.config
cmrunpkg mgroupMDM
Setup Step: MDM248
(b) Enable SGeSAP monitoring for "Multiple" MDM packages
The SGeSAP scripts include check functions to monitor the health of MDM processes. The variable
MDM_MONITOR_INTERVAL=60 in file sap.config determines how often the monitor function is
executed. To enable monitoring it has to be configured in the Serviceguard package configuration
files. For the mdsMDM Serviceguard package - the name "mdsMDMmon" will be used as the monitor
name /SERVICE_NAME. Edit both Serviceguard package files.
vi /etc/cmcluster/MDM/mdsMDM.config
SERVICE_NAME mdsMDMmon
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 60
vi /etc/cmcluster/MDM/mdsMDM.control.script
SERVICE_NAME[0]="mdsMDMmon"
SERVICE_CMD[0]="/etc/cmcluster/MDM/sapmdm.sh check mds"
SERVICE_RESTART[0]=""
To activate the changes in the Serviceguard configuration files run the following command:
cmapplyconf -P /etc/cmcluster/MDM/mdsMDM.config
Repeat the above steps for the mdbMDM, mdisMDM and mdsMDM packages.
NOTE: The masterMDM Serviceguard package does not require a check function. The only goal
of this package is to coordinate a cluster wide start and stop of the MDM server packages and
therefore does not need a monitor.
Setup Step: MDM250
Synchronize the /etc/cmcluster/MDM contents with second node
Synchronize the contents of directory /etc/cmcluster/MDM with the second node using following
command:
clunode1:
scp –pr /etc/cmcluster/MDM clunode2:/etc/cmcluster/MDM
Setup Step: MDM252
(a) Single - Starting and Stopping the mgroupMDM package
Since everything is grouped in one package the following command will start and stop the package
and all it's MDM server components (mdb, mds, mdss and mdis) at the same time - on the
cluster node the cmrunpkg command is executed.
cmrunpkg mgroupMDM
cmhaltpkg mgroupMDM
Setup Step: MDM254
(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,
160 SAP Master Data Management (MDM)