Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

DescriptionPossible valueParameter
Specify Oracle listener password, if setsgesap/oracledb_spec/listener_password
For db_vendor = maxdb
User key of control usercsgesap/maxdb_spec/maxdb_userkey
For db_vendor = sybase
Sybase system administration or
monitoring user
sapsasgesap/sybasedb_spec/aseuser
Password for specified aseuser
attribute
sgesap/sybasedb_spec/asepasswd
For Sybase the attribute aseuser and asepaswd are optional. When specified and that user has
system administration right, it is used for native fallback in database shutdown situations. If the
user does not have the right, it is used for monitoring purposes only.
Figure 19 Configuring SAP instances
Module sgesap/mdminstance – SAP MDM repositories
The sgesap/mdminstance module is based on sgesap/sapinstance with additional attributes for
MDM repositories, MDM access strings, and MDM credentials. Many configurations combine the
MDM instances like MDS, MDIS, and MDSS (and possibly a DB instance) into one SGeSAP
package. This is called a “MDM Central” or “MDM Central System” installation. Each instance
can also be configured into separate packages, called a “distributed MDM” installation. All MDM
repositories defined in the package configuration are automatically mounted and loaded from the
database, after the MDM server processes start successfully.
The following table contains some selected SGeSAP parameters relevant to a MDM Central System
instance. For more information, see the package configuration file.
DescriptionValueParameter
Defines the unique SAP System Identifier (SAP
SID)
MO7sgesap/sap_global/sap_system
Example for defining an MDM MDS instance
with instance number 01.
MDS01sgesap/stack/sap_instance
68 Clustering SAP using SGeSAP packages