Managing Serviceguard Extension for SAP Version B.05.10, December 2012
(b) Multiple Serviceguard package - continue with mdsMDM, mdisMDM, mdsMDM andmasterMDM
configuration
If the Multiple Serviceguard package option was chosen in the beginning of this chapter, continue
with the configuration of the mdsMDM, mdisMDM, mdssMDM and masterMDM packages. 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. 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
they are mds or mdis or mdss or the master component
This code logs extensive status on the script and functions being executed.The following documents
the changes for the mdsMDM package - only the variable MDM_COMPONENT=mds is changed for
the customer_defined_run_cmds and the customer_defined_halt_cmds functions.
Repeat the steps below for the other packages mdisMDM, mdssMDM and masterMDM.
vi /etc/cmcluster/MDM/mdsMDM.control.script
function customer_defined_run_cmds
{
typeset MDM_SCR="/etc/cmcluster/MDM/sapmdm.sh"
typeset MDM_ACTION="start"
typeset MDM_COMPONENT="mds"
${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="mds"
${MDM_SCR} "${MDM_ACTION}" "${MDM_COMPONENT}"
test_return 52
}
Setup Step: MDM240
Configure sap.config
File /etc/cmcluster/MDM/sap.config contains the SGeSAP specific parameters for MDM.
Table 31 (page 157) is an excerpt and explains the parameters that can be set for the MDM
configuration.
Table 31 MDM parameter descriptions
DescriptionParameter
The database type being used.MDM_DB=ORACLE
The Oracle SID of the MDM database.MDM_DB_SID=MDM
The Oracle admin user.MDM_DB_ADMIN=oramdm
The name of the Oracle listener.MDM_LISTENER_NAME="LISTENER"
The MDM admin user.MDM_USER=mdmuser
The virtual/relocatable IP address of the MDS
component. The IP address is required to run clix
MDM_MDS_RELOC=172.16.11.96
Installation and Configuration Considerations for MDM 5.5 in a Serviceguard legacy environment 157