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

Edit the mds.ini, mdis.ini and mdss.ini files and add the virtual IP hostname for the mds
component to the [GLOBAL] section. The mdis and mdss components use this information to
connect to the mds server.
/home/mdmuser/mds/mds.ini
[GLOBAL]
Server=mdsreloc
.
.
/home/mdmuser/mdis/mdis.ini
[GLOBAL]
Server=mdsreloc
.
.
/home/mdmuser/mdss/mdss.ini
[GLOBAL]
Server=mdsreloc
.
.
Setup Step: MDM234
Stop all MDM processes
Before continuing with the configuration of the MDM Serviceguard packages, the MDM processes
have to be stopped. Use the following kill command to accomplish this:
kill -9 `ps -ef|grep mdmuser|grep "\-r"|awk '{print $2}'
Setup Step: MDM236
(a) Single Serviceguard package - continue with mgroupMDM configuration
If the Single Serviceguard package option was chosen in the beginning of this chapter, continue
with the configuration of this package. Insert in the function customer_defined_run_cmds
and customer_defined_halt_cmds the following shell scripts. These scripts are responsible
for executing the SGeSAP specific scripts e.g. for running and halting the MDM server components
of an mgroupMDM package. The key statements for this package are in the beginning:
• MDM_SCR is the script to execute
• MDM_ACTION is start for running a package and stop for halting a package
• MDM_COMPONENT which of MDM components should be started or stopped, in this case
the mgroup component
vi /etc/cmcluster/MDM/mgroupMDM.control.script
function customer_defined_run_cmds
{
typeset MDM_SCR="/etc/cmcluster/MDM/sapmdm.sh"
typeset MDM_ACTION="start"
typeset MDM_COMPONENT="mgroup"
${MDM_SCR} "${MDM_ACTION}" "${MDM_COMPONENT}"
test_return 51
}
function customer_defined_halt_cmds
{
typeset MDM_SCR="/etc/cmcluster/MDM/sapmdm.sh"
typeset MDM_ACTION="stop"
typeset MDM_COMPONENT="mgroup"
${MDM_SCR} "${MDM_ACTION}" "${MDM_COMPONENT}"
test_return 52
}
Setup Step: MDM238
156 SAP Master Data Management (MDM)