Table 5-3 MDM parameter descriptions

Parameter

Description

MDM_DB=ORACLE

The database type being used.

MDM_DB_SID=MDM

The Oracle SID of the MDM database.

MDM_DB_ADMIN=oramdm

The Oracle admin user.

MDM_LISTENER_NAME="LISTENER"

The name of the Oracle listener.

MDM_USER=mdmuser

The MDM admin user.

MDM_MDS_RELOC=172.16.11.96

The virtual/relocatable IP address of the MDS component.

 

The IP address is required to run clix commands. Note:

 

MDSS and MDIS do not require a virtual IP address.

MDM_PASSWORD=""

The password used to access MDM.

MDM_REPOSITORY_SPEC=" PRODUCT_HA:MDM:o:mdm:sap \

The following a brief description of the values:

PRODUCT_HA_INI:MDM:o:mdm:sap \"

Repository= PRODUCT_HADBMS instance=

 

MDMDatabase type= o (Oracle)Username=

 

mdmPassword= sap

MDM_CRED="Admin: "

Clix Repository Credentials: the password used for

 

repository related commands. Note: the space in the string

 

is required.

MDM_MONITOR_INTERVAL=60

How often the check/monitor gets executed.

MDM can be configured to run as "SINGLE" or "ONE" Serviceguard package OR as "MULTIPLE" or "FOUR+ONE" Serviceguard packages.

In the case of a "SINGLE" package all MDM components (mdb mds mdis mdss) are always started and stopped on the same cluster node which the Serviceguard package itself is started on. In this case variable MDM_MGROUP_DEPEND will be used by the Serviceguard package called (mgroupMDM) to start these in order.In the case of "MULTIPLE" Serviceguard packages each MDM component (mdb or mds or mdis or mdss) is configured as a separate Serviceguard package (mdbMDM mdsMDM mdisMDM mdssMDM) and can be started independent of the location of the other MDM Serviceguard packages. Variable MDM_MASTER_DEPEND controls this configuration and is used by a "FIFTH" Serviceguard package called (masterMDM) to start these in order.

The following table details the MDM_MGROUPand MDM_MASTER dependencies.

Table 5-4 MDM_MGROUP and MDM_MASTER dependencies

Dependency

Description

MDM_MGROUP_DEPEND="\ mdb mds mdis mdss" The elements (mdb mds...) of variable MDM_MGROUP_DEPEND are the names of the MDM components that are started from a single Serviceguard package. The order of the MDM components is important.

MDM_MASTER_DEPEND="\ mdbMDM mdsMDM mdisMDM\

Each element (mdbMDM mdsMDM...) of variable

mdssMDM"

MDM_MASTER_DEPEND is the name of a Serviceguard package to

 

start. The position of the element determines the start order.

Setup Step: MDM242

(a) Single Serviceguard package - configure sap.config

Edit sap.config and add the following parameters for a Single Serviceguard package configuration. This is for the mgroupMDM package. The key variable for this configuration is MDM_MGROUP_DEPEND="mdb mds mdis mdss".

vi/etc/cmcluster/MDM/sap.config

MDM_DB=ORACLE MDM_DB_SID=MDM MDM_DB_ADMIN=oramdm

MDM_LISTENER_NAME="LISTENER"

MDM_USER=mdmuser

Installation and Configuration Considerations 133

Page 133
Image 133
HP Serviceguard Extension for SAP (SGeSAP) Single Serviceguard package configure sap.config, Mdmlistenername=Listener