MDM InstGuide

8/10/2019 MDM InstGuide

http://slidepdf.com/reader/full/mdm-instguide 1/84

Installation Guide for Windows CUSTOMER

SAP NetWeaver Master Data Manager 7.1

Document Version: 5.4 - 2014-04-02

MDM Installation Guide for Windows



Table of Contents

1 Introduction to MDM Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 MDM Component Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Required Documentation for Installing MDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 How to Use the MDM Installation and Upgrade Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Planning the MDM System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

2.1 Windows Domain or Local Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.3 Multiple Components on One Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4 Lightweight Directory Access Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

3 Preparation for MDM Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1.1 Checking Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1.2 Requirements for Windows Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1.3 Installing Visual C++ Security Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

3.2 Basic SAP System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3 Preparation for a Local or Domain Windows Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.3.1 Checking the File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.3.2 Checking the Domain Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.3.3 Checking Required User Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.3.4 Preparing Domain Installation by a Non-Domain Administrator. . . . . . . . . . . . . . . . . . . . . . . 21

3.4 SAP Directories Created During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.4.1 SAP System Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.4.2 MDM Windows Client Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.5 Preparing the Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.5.1 Downloading Installation Files from SMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.5.2 Obtaining Installation Files from DVD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 Installation of MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.1 MDM Installation Using SAPinst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.2 Starting the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.3 SAPinst Installation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.4 Restarting an Interrupted Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.5 Performing a Remote Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.6 Starting SAPinst GUI Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.6.1 Starting SAPinst GUI on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.6.2 Starting SAPinst GUI on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.7 Performing a Silent Installation of MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.8 Installation Entries in the Services File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2C U S T O M E R© 2014 SAP AG or an SAP affiliate co mpany. All rights reserved.


Table of Contents



4.9 Troubleshooting Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

5 Installing MDM Windows Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1 Using GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.2 Using Silent Mode for a Single Windows Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.3 Using Silent Mode for Multiple Windows Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.4 MDM Windows Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6 Installing Additional MDM Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7 Installing and Configuring the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.1 Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

7.1.1 Database Performance Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7.2 Oracle DBMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.2.1 Setting Up the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

7.2.2 Connecting MDS to the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

7.2.3 Adjusting Temporary Tablespace for MCOD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

7.2.4 Allowing Flexible Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

7.3 IBM DB2 for Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7.4 IBM DB2 for z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7.4.1 Downloading the Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7.4.2 Modifying the PATH Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.4.3 Downloading the CLI Driver License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.4.4 Configuring db2cli.ini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

7.4.5 Setting Up DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.4.6 Performing BIND and GRANT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.4.7 Creating the STOGROUP (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.4.8 Creating Foreign Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.5 MaxDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.6 SAP Adaptive Server Enterprise (ASE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7.6.1 Installing the SAP ASE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.6.2 Configuration of the SAP ASE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

7.6.3 Installing and Configuring the SAP ASE ODBC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

7.6.4 Configuration of MDS.INI Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

7.7 SAP HANA (For MDM-SRM Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

8 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8.1 Starting and Stopping the MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8.1.1 Using SAP Microsoft Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8.1.2 Using MDM Console or MDM CLIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

8.1.3 Using Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

8.2 Setting Up SSL Communication for MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.2.1 Setting Up SSL During MDS Installation or Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71


Table of Contents

C U S T O M E R© 2014 SAP AG or an SAP affiliate company. All rights reserved. 3



8.2.2 Post-Installation/Update Tasks for SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8.2.3 Setting Up SSL in a Master/Slave Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

8.2.4 Using CLIX with SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

8.3 Setting up MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

8.3.1 Configuring MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

8.3.2 Mounting MDS and Connecting the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

8.3.3 Setting MDS and Repository Authentications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

9 Multiple MDM Servers on a Single Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

9.1 Installing Different Version of MDM Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

9.2 Running Multiple MDM Server Components on a Single Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

9.3 Unarchiving and Updating MDM Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

10 Updating MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

11 Uninstalling MDM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

12 Uninstalling MDM Windows Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

13 SAP System Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

13.1 User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

13.2 Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

13.3 Security of SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82



Table of Contents



1 Introduction to MDM Installation

This installation guide describes how to install the SAP NetWeaver Master Data Management (MDM) 7.1

components on supported Windows platforms.

The guide also describes the installation and configuration of released databases for use with MDM.

Caution

The installation procedure for MDM 7.1 servers differs significantly from the installation procedure for MDM 5.5.

MDM 7.1 servers are installed as SAP systems using the SAPinst installation tool and SAP Instance Framework.

The installation procedure for MDM clients and additional components has not changed.

This document should be used by system administrators and technology consultants who are installing the MDM

system.

1.1 MDM Component Overview

MDM Servers

The following MDM servers are the foundation of the MDM software. These components can be installed on

supported platforms using SAPinst:

● Master Data Server (MDS)

● Master Data Import Server (MDIS)

● Master Data Syndication Server (MDSS)

● Master Data Layout Server (MDLS)

MDM Windows Clients

The following MDM clients enable you to administrate the system and manage your data. These components can

be installed on Windows using a simple MDM-specific installation routine:

● MDM Console

● MDM CLIX

Note

The administration command line tool MDM CLIX is automatically installed with the MDS. You only need to

install it manually for remote access to MDS, for example, from a local PC.


Introduction to MDM Installation






Information on SAP Help Portal

The SAP NetWeaver MDM 7.1 Documentation Center on the SAP Help Portal at help.sap.com/nwmdm71 providesuseful information and access to the complete MDM documentation set, including all the MDM installation and

planning guides.

SAP Installation Notes

It is essential that you read the following SAP Notes before starting the installation. These SAP Notes contain the

most recent information about the installation as well as corrections to the installation documentation.

Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service

Marketplace at service.sap.com/notes .

SAP Note Number Title Description

1249503MDM Installation Note Most recent information and best

practices about the MDM installa

tion procedure. The MDM Installa

tion Note complements this MDM

Installation Guide.

1938462SAP NetWeaver MDM 7.1 SP12 Re

lease

This note contains information

about the current MDM 7.1 support

package.

1244358MDM 7.1 Release Restriction Note This note contains the restrictions

of the current MDM 7.1 support

package.

1.3 How to Use the MDM Installation and Upgrade Guides

When planning a new MDM installation, follow the instructions in the relevant MDM Installation Guide for yourplatform. When planning an upgrade from MDM 5.5, or from any previous MDM 7.1 support package (SP) release,

you should also refer to the MDM Upgrade Guide for the following information before you begin the upgrade

process:

● Preparatory and pre-installation tasks

● Post installation setup and configuration tasks required to complete the upgrade process.


Introduction to MDM Installation


http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1249503




http://help.sap.com/disclaimer?site=http://service.sap.com/notes

http://help.sap.com/nwmdm71



2 Planning the MDM System Landscape

When planning the MDM system landscape, familiarize yourself with the following documentation at

help.sap.com/nwmdm71:

● MDM Master Guide

● MDM Sizing Guide

● Introduction to this guide

Get informed about the supported platforms and databases. The MDM 7.1 Product Availability Matrix (PAM) is at

service.sap.com/pam (search for MDM 7.1). If you are planning an MDM upgrade installation (from release 5.5

or from a previous SP release of 7.1), read the MDM Upgrade Guide first (available at help.sap.com/nwmdm71).

For more information, refer to the following sections in this guide:

● SAPinst Installation Options [page 33]

● Updating MDM Servers [page 78]

MDM System Landscapes

An MDM system landscape is typically structured as follows:

● One separate UNIX host or Windows server host with the MDM servers and the database (standard system).

You can distribute the different MDM servers to several hosts (distributed system).

● Several different Windows machines with multiple combinations of MDM clients for administrators, master

data specialists and end users.

● More than one installation of additional MDM components for developers and portal administrators, for

example, on Web or SOAP servers.

Before you install MDM 7.1 as part of the implementation of a SAP NetWeaver scenario, familiarize yourself with

the contents of the corresponding SAP NetWeaver Master Guide. The Master Guide is the central document for

the implementation of SAP NetWeaver solutions and scenarios. This document lists the components and third-

party applications that are required for each scenario in an SAP NetWeaver solution, and refers to the required

installation and upgrade guides. It also defines the installation sequence for the scenarios of the corresponding

SAP NetWeaver solution.

The MDM Master Guide and all other MDM documentation is on the SAP Help Portal at help.sap.com/nwmdm71.

2.1 Windows Domain or Local Installation

Before you install the MDM servers on Windows, decide whether to perform a domain or local installation. The

installation type affects how the user account information is stored and accessed.



Planning the MDM System Landscape

http://help.sap.com/disclaimer?site=http://service.sap.com/pam







Domain Installation

In a domain installation, the user account information is stored centrally in one database on the domain controllerand is accessible to all hosts in the system.

You must perform a domain installation if you install a distributed system with MDM servers and the database on

different hosts (this is strongly recommended to avoid authorization problems).

Local Installation

In a local installation, all Windows account information is stored locally on one host and is not visible to any otherhosts in the system.

To run the MDM servers and the database on a single machine, perform a local installation.

2.2 High Availability

High availability (HA) is a major consideration when planning business systems that require system reliability.

For MDM, there are different approaches that support this objective, for example, system redundancy using load

and balancing tools, backup strategies and cluster management software.

If you plan to set up MDM in a landscape that provides high availability, see the High Availability section in the

MDM Solution Operation Guide at help.sap.com/nwmdm71.

2.3 Multiple Components on One Database

MDS can be installed in an MCOD environment, sharing the same database with other SAP components, such as

SAP ERP ECC or SAP NetWeaver Application Server. Generally, several components sharing the same database

resources affect overall performance; this must be taken into consideration when sizing the hardware and

system.

Note

For MCOD on an Oracle database, check and adjust the temporary tablespace after the MDM installation. For

more information, see Adjusting Temporary Tablespace for MCOD [page 52].







2.4 Lightweight Directory Access Protocol

MDM supports the Lightweight Directory Access Protocol (LDAP) for user authorization management. If you plan

to use LDAP with MDM, see the LDAP Support section in the MDM Security Guide at help.sap.com/nwmdm71







3 Preparation for MDM Installation

To prepare for an MDM installation, learn about SAP systems and make some checks and settings on the platform

designated for MDM installation.

The chapter describes the following:

● Hardware and Software Requirements [page 11]

● Basic SAP System Parameters [page 14]

● Preparation for a Local or Domain Windows Installation [page 18]

● SAP Directories Created During Installation [page 23]

● Preparing the Installation Files [page 26]

3.1 Hardware and Software Requirements

Check that your hosts meet the hardware and software requirements for your operating system (OS), the MDM

server instances, and the MDM clients. The following topics describe the requirements for running SAPinst and

MDM servers and how to check these requirements.

Caution

If your hosts do not fully meet these requirements, you might experience problems when working with the SAP

system.

Prerequisites

● Contact your OS vendor for the latest OS patches.

● Make sure that the host name meets the requirements listed in SAP Note 611361 .

Caution

To monitor MDM using the SAP Solution Manager, the MDM host name must also meet the requirements listed

in SAP Note 1278029 .

3.1.1 Checking Requirements

1 Check the supported operating system releases in the MDM 7.1 Product Availability Matrix (PAM) at

service.sap.com/pam (search for MDM 7.1).

2 Check that your system meets the minimum requirements listed in Requirements for Windows Installation

[page 12] .


Preparation for MDM Installation










3 If you are installing a production system, the values provided by the Prerequisite Checker and the

Requirements for Windows section in this guide are not sufficient. In addition, do the following:

a) Read the MDM Sizing Guide available at help.sap.com/nwmdm71.

b) Contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing

depending on parameters such as:

○ How intensively the applications are to be used

○ Number of users

○ Data Model of your MDM repositories

○ Number of records in the MDM repositories

○ Number of large binary objects (for example, images and PDFs) in the repositories

3.1.2 Requirements for Windows Installation

This section lists the minimum hardware and software requirements for installing and running MDM servers on

released Windows platforms.

Hardware Requirements

Requirement Type Requirement How to Check

Minimum disk space SAP system files (not including pag

ing file): 2 GB

Temporary disk space for the instal

lation: 1 GB

To check disk space:

1 Choose Start All Programs

Administrative Tools

Computer Management Disk

Management.

2 Right-click the drive and choose

Properties

.

Minimum RAM 5 GB To check RAM:

In the Windows Explorer, choose

Help About Windows .

Paging file size 1 times RAM plus 10 GB To check paging file size:

1 ChooseStart Control

Panel System .

2 Choose Advanced.

3 Select Performance Settings

Advanced

.

4 In sectionVirtual memory

,

chooseChange

.







Software Requirements

Requirement Type Requirement How to Check

Windows operating system for MDM

servers

English international 64-bit version

of one of the released Windows

Server Editions. For any version of

Windows Server, you need the lat

est supported service pack.

To check your Windows version:

1 Choose Start All Programs

Accessories Command

Prompt .

2 Enter the command winver.

TCP/IP access MDIS, MDSS, and MDLS must have

TCP/IP access to the MDS. This

connection must be on a local net

work to be effective. Starting fromMDM 7.1 SP07, each MDM instance

can use either regular TCP/IP ports,

or SSL TCP/IP ports for secure

communication (if this was config

ured). For more information on the

TCP/IP ports, see SAP Note

1487853.

Check the setup of your network,

operating system, and firewalls, to

verify that the MDM servers can be

accessed through their dedicatedTCP/IP ports. You set the ports dur

ing the installation. The regular

TCP/IP ports are:

● MDS: Port 59950 and three se

quential ports in the range

2000 - 9999 for every loaded

repository. Configure the repo

sitory ports using the MDM

Console.

● MDIS: Port 59750

● MDSS: Port 59850● MDLS: Port 59650

The SSL TCP/IP ports, starting

from MDM 7.1 SP07, are:

● MDS: Port 59951 and three se

quential ports in the range

2000 - 9999 for every loaded

repository. Configure the repo

sitory ports using the MDM

Console.

●

MDIS: Port 59751● MDSS: Port 59851

● MDLS: Port 59651

If an MDM Server is already installed

on your machine and you install an

additional instance of MDS, MDIS,

MDSS, and/or MDLS, the default

TCP/IP ports will be created in the

following format, where xx is the in

stance number:








Parameter Parameter

If there are further installation options to be executed,

SAPinst prompts you for the SAP System Profile Directory, which is described below.

Caution

Choose your SAP system ID carefully. Choosing a

new ID is difficult and requires you to reinstall the

SAP system.

Make sure that your SAP system ID:

● Is unique throughout your organization

● Consists of exactly three alphanumeric characters

● Contains only uppercase letters

● Has a letter for the first character

● Does not include any of the following, which are re

served IDs:

ADD ALL AND ANY ASC AUX COM CON DBA

END EPS FOR GID IBM INT KEY LOG LPT MON

NIX NOT NUL OFF OMS PRN RAW ROW SAP SET

SGA SHG SID SQL SYS TMP UID USR VAR

SAP System Profile Directory

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\ SYS\profile

The installation retrieves the parameters entered ear

lier from the SAP system profile directory.

SAPinst prompts you to enter the location of the profile

directory if the installation option that you run is not

the first one belonging to your SAP system installation.

For more details, read the description of the parameter

<SAPSID>.

Instance Number of the SAP System Technical identifier that is required for every instance

of an SAP system, consisting of a two-digit number

from 00 to 97.

The instance number must be unique on the host. If

more than one SAP instance is running on the same

host, these instances must be assigned different num

bers.

The instance number specifies the names of the SAP

system instance directories that SAP automatically

creates during the installation. For example, the direc

tory of the MDS is calledMDS<Instance_Num-

ber>.Windows Terminal Server.

Virtual Host Name Use one or more virtual TCP/IP host names for SAP

servers in an SAP server landscape to conceal their

physical network identities from each other.






Parameter Parameter

This may be useful for moving SAP servers or complete

server landscapes to other new hardware within a shorttime frame, without reinstalling or performing a compli

cated reconfiguration.

To use virtual host names for the installation, specify

the virtual host name before you start SAPinst.

For more information about the use of virtual TCP/IP

host names, see SAP Note 962955 .

The host name must not exceed 12 characters. For

more information about the allowed host name length

and characters, see SAP Note 611361 .

Destination Drive Base directory for the SAP system.

Note

If you install an additional SAP system, you cannot

select the installation drive because the sapmnt

share already exists. SAPinst uses the installation

drive that the sapmnt share points to.

Master Password Common password for all users that are created during

the installation: Operating system users (for example<sapsid>adm, SAPService<SAPSID>)

Caution

If you did not create the operating system users

manually before the installation, SAPinst creates

them with the default master password. In this case,

make sure that the master password meets the re

quirements of your operating system.

If a user already exists, you are prompted to confirm

the password for this user.

User <sapsid>adm User <sapsid>adm is the system administrator user

and is a member of the local Administrators group.

If you do not create the user <sapsid>adm manually

before the installation, SAPinst creates it automatically

during the installation. SAPinst sets the Master Pass

word by default, but you can overwrite it by choosing

the parameter mode Custom or by changing it on the

parameter summary screen.










3.3 Preparation for a Local or Domain Windows Installation

The following topics describe the Windows-specific preparation steps that you must perform before starting a

local or domain installation:

● Checking the File System [page 18]

● Checking the Domain Structure

● Checking Required User Authorizations

● Preparing Domain Installation by a Non-Domain Administrator

3.3.1 Checking the File System

Check that you are using the Windows file system NTFS on the hosts where you want to install the SAP system.

NTFS supports full Windows security and long file names.

Note

You must use NTFS for an SAP system installation. Do not install the SAP directories on a FAT partition.

1 Open the Windows Explorer.

2 Select the relevant disk.

3 Choose Properties General

4 Check that the file system is NTFS.

3.3.2 Checking the Domain Structure

● You are performing a domain installation.

● You are familiar with checking Windows domain structures. For more information, see the Windows OS

documentation.

Note

You do not need this step for a local installation.

In Windows, you can implement either of the following domain models for the SAP system:

● Extra domain

In this model, the SAP system is embedded in its own domain, which is specially defined for SAP. A second

domain exists for the user accounts. In Windows, the SAP domain and user domain must be incorporated into

a domain tree. In this tree, the user accounts must form the root domain and the SAP domain must be a child

domain of the root domain.

● Single domain






In this model, the SAP system and the user accounts are incorporated into a single domain.

Caution

You cannot create local users and groups on the host that is used as a domain controller. Running an SAP

instance or the database on the host where the domain controller is installed is therefore not supported.

For a domain installation, check that all SAP system and database hosts are members of a single Windows

domain. We recommend this for all SAP system setups.

3.3.3 Checking Required User Authorizations

The authorization required depends on whether you intend to perform a domain or local installation. If required,

ask the system administrator to grant the necessary authorization before you start the installation. If you attempt

the installation with an account that does not have the required authorization, the installation aborts. This section

informs you about the authorization required for a domain and a local installation.

Caution

Do not use the user<sapsid>adm

for the installation of the SAP system.

3.3.3.1 Checking for Domain Installation

For a domain installation, the account used to run the installation must be a member of the local Administrators

and the domain Admins group must be a member of the relevant domain. All hosts in the system must belong to

the same domain. In a domain installation, the SAP system user information is stored centrally on the domain

controller and is accessible to all hosts in the system. If the SAP system is to be distributed across more than one

machine, SAP strongly recommends that you perform a domain installation to avoid authorization problems.

Caution

If you install a distributed system as a local installation, this can lead to authorization problems for the

operating system users<sapsid>adm

andSAPService<SAPSID>

. Therefore, we do not support a local

installation for a distributed system. We recommend that you install a distributed system as a domain

installation. If you must perform a local installation for a distributed system, make sure that:

● You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all hosts. The

password for the <sapsid>adm and SAPService<SAPSID> user can differ.

● You use the same master password on all hosts.

● All hosts belong to the same Windows work group.

For performance and security reasons, SAP does not support an SAP system installation on a domain

controller. If for any reason the account used for the installation is not a member of the domain Admins group,

you can perform the installation with a domain user who is a member of the local Administrators group.

However, the domain administrator must prepare the system for you.






1 Check that the account used for the installation is a member of the domain Admins group.

2 If required, obtain these rights by asking the system administrator to enter the account as a member of the

domain Admins group.

Related Information

Preparing Domain Installation by a Non-Domain Administrator [page 21]

3.3.3.2 Checking for Local Installation

For a local installation, the account used for the installation must be a member of the local Administrators group

of the machine involved. In a local installation, all Windows account information is stored locally on one host and is

not visible to any other hosts in the system.

1 Check that the account used for the installation is a member of the domain Admins group.

2 If required, obtain these rights by asking the system administrator to enter the account as a member of the

local Administrators group.

3.3.3.3 Avoiding Automatic Logoff by SAPinst

For both domain and local installations, the user account must be authorized to:

● Act as part of the operating system

● Adjust memory quotas for a process

● Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automatically logs off the

account to activate them. To prevent SAPinst from logging off the account, set these rights manually before you

start the installation.

Note

Domain policies override locally defined policies. This means that to grant domain administrator rights for a

user who belongs to the local Administrators group, make sure that you have also defined domain

administrator rights for this user at the domain level.

1 Choose Start Settings Control Panel Administrative Tools Local Security Policy .

2 In the Local Security Settings window, choose Local Policies User Rights Assignment .

3 Double-click the required right under Policy and choose Add User or Group.

4 In the Select Users and Groups window, choose the required user and choose Add. The selected user

appears in the box below.






5 Confirm your entry and then repeat the steps for each remaining policy that the user requires for the

installation.

6 Log off and log on again to apply the changes.

3.3.4 Preparing Domain Installation by a Non-DomainAdministrator

You must be domain administrator to perform the required steps.

You normally perform a domain installation of the SAP system with a user who is a member of the domain Admins

group. If for any reason, the account used for the installation is not a member of the domain Admins group, youcan perform the installation with a domain user who is a member of the local Administrators group. In this case,

the domain administrator has to prepare the system appropriately for you. The domain administrator can perform

the following steps manually or by using SAPinst:

1 Create the new global group SAP_<SAPSID>_GlobalAdmin.

2 Create the two new SAP system users <sapsid>adm and SAPService<SAPSID>.

3 Add the users <sapsid>adm and SAPService<SAPSID> to the newly created group

SAP_<SAPSID>_GlobalAdmin.

Related Information

Checking Required User Authorizations [page 19]

3.3.4.1 Creating Required Users and Groups Using SAPinst

On the host where the SAP system is to be installed, the domain administrator runs SAPinst and chooses

Additional Software Life-Cycle Options Operating System Users and Groups to create the group and

users automatically.

3.3.4.2 Creating the Required Users and Groups Manually

The following tasks describe the procedure to add users and groups manually.






Create the New Global Group SAP_<SAPSID>_GlobalAdmin

1 Log on as domain administrator.

2 To start the Active Directory Users and Computers Console, chooseStart Control Panel Administrative

Tools Active Directory Users and Computers .

3 Right-clickUsers in Tree

, and chooseNew Group

.

4 Enter the following:Group name: SAP_<SAPSID>_GlobalAdmin

Note

Enter the SAP_<SAPSID>_GlobalAdmin group exactly as specified in the correct uppercase and

lowercase.

5 SelectGroup scope: Global and Group type: Security

.

6 Choose OK.

Create the New SAP System Users <sapsid>adm andSAPService<SAPSID>

1 InActive Directory Users and Computers Console

, right-clickUsers in Tree

and chooseNew User

.

2 Enter the following:

Field Input for adm Input for SAPService

First name:

None None

Initials: None None

Last name: None None

Full name:

<sapsid>adm SAPService<SAPSID>

User logon name:

<sapsid>adm SAPService<SAPSID>

Note

Enter the<sapsid>adm

andSAPService<SAPSID>

user exactly as specified in the correct uppercase and

lowercase.

3 ChooseNext

and enterPassword: <password>

andConfirm password: <password>

4 Select Password never expires.

Note

Make sure that no other options are selected.

5 Choose Next Finish .






Add the <sapsid>adm User to theSAP_<SAPSID>_GlobalAdmin Group

1 In the Users folder, double-click the newly created user account <sapsid>adm in the list on the right.

2 Choose Add Member .

3 Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to the list.

Note

By default, the user is also a member of the Domain Users group.

4 ChooseOK

twice.

Add the SAPService<SAPSID> User to theSAP_<SAPSID>_GlobalAdmin Group

1 In the Users folder, double-click the newly created user account SAPService<SAPSID> in the list on the right.

2 Choose Add Member .

3 Select the new SAP_<SAPSID>_GlobalAdmin group.

4 ChooseAdd

to add it to the list, and thenOK

.

5 Choose OK to close SAPService<SAPSID> Properties.

6 Close theActive Directory Users and Computers Management Console

.

3.4 SAP Directories Created During Installation

This section describes the directories that the system creates during the installation of MDM servers and MDM

Windows clients.

3.4.1 SAP System Directories

This section describes the SAP system-specific and MDM servers-specific directories that SAPinst creates during

the installation of MDM servers. SAPinst automatically creates the following directory during the installation: \usr

\sap

This directory is created on the:

● Global host and shared with the network share sapmnt. The global host is the host where the primary MDS

instance is installed. On global hosts, the \usr\sap directory contains general SAP software, global and local

(instance-specific) data. SAPinst creates the global directory usr\sap\<SAPSID>\SYS. There is exactly one

physical directory for each SAP system. It consists of the following subdirectories:






○ global – contains globally shared data

○ profile – contains the profiles for all instances

○ exe – contains the executable replication directory for all instances

● Local host and shared with the name saploc. On local hosts, the \usr\sap\<SAPSID>\<instance_name>

directory contains copies of the SAP software and local (instance-specific) data. Under \usr\sap\<SAPSID>

\<instance_name>\config, for example, you find the MDM-specific configuration files for MDM servers:

○ mds.ini

○ mdis.ini

○ mdss.ini

In the MDS instance folder under mdm, you find the following MDS-specific sub-folders:

○ accelerators

○ archives

○ distributions

○ reports

Note

As SAP traces for the instance are created in \usr\sap, make sure there is sufficient space available in

this directory. Changes to SAP profiles can also affect the disk space.As SAP traces for the instance are

created in \usr\sap, make sure there is sufficient space available in this directory. Changes to SAP

profiles can also affect the disk space.

Other MDM servers or application servers access the global data using the Universal Naming Convention (UNC)

path \\<SAPGLOBALHOST>\sapmnt. The SAP programs access their instance-specific data with the UNC path\

\<SAPLOCALHOST>\saploc. If the UNC path points to a local directory, the local path (and not the UNC path) is

used to access the directory. The parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on

the global host.

The following graphic shows the directory structure of a central installation:






The following graphic shows the directory structure of a distributed installation:






3.4.2 MDM Windows Client Directories

This section describes the MDM Windows client-specific directories that the MDM client installers create during

the installation of each client component: \Program Files\SAP MDM 7.1.

This directory is created on the local host, where the MDM client installation executables are started. The

\Program Files\SAP MDM 7.1 directory contains, for example executables, logs, and the language files for the

client UIs.

3.5 Preparing the Installation Files

This section describes how to prepare the installation files. The installation files can be obtained from one of the

following:

● Download the installation files from SAP Service Marketplace (SMP).

● An MDM installation DVD, which is a part of the installation package.

To prepare the installation files:

1 Create a download directory on the host on which you are installing MDM.

2 Download to the download directory all the objects required for the type of MDM installation you want to

perform.






3 Extract the individual download objects directly into the download directory. During the extraction, the

structure of the installation DVD is set up in the download directory.

Related Information

Downloading Installation Files from SMP [page 27]

Obtaining Installation Files from DVD [page 28]

3.5.1 Downloading Installation Files from SMP

You can download installation files from the SAP Software Download Center on SMP. The SAP Software Download

Center enables you to download individual components one by one, or download an entire stack of components at

once, by using one of the following options:

● Entry by Component

: Used to download individual components one by one. You select the target operating

system for the component, and then you select the items to download. Typically, you select the latest patch of

the latest service pack (SP). You repeat this process for any additional components.

● Link to SP Stack Application: Used to download all the components necessary for moving to a higher SP

than the one currently installed. After selecting the target SP, you select for each component the

instantiation, by defining the target operating system, database, or other required information.

To download a single MDM component from the SAP Software Download Center (swdc):

1 Select the component to download: service.sap.com/swdc Support Packages and Patches Browse

our Download Catalog SAP NetWeaver and complementary products SAP MDM SAP

NETWEAVER MDM 7.1 Entry by Component <component>

2 When you select a server component:

a) Verify that you are using the latest version of the MDM Installation Master 7.1.

b) Verify that the version of the installed MDM Shared Install Content corresponds to the version of the

server component.

3 Select the installable software unit.

4 Select the target operating system.

5 Scroll down to view the Downloads tab, and select the items to download.




http://help.sap.com/disclaimer?site=http://service.sap.com/swdc




3.5.2 Obtaining Installation Files from DVD

Caution

If you copy the DVD to disk, make sure that the paths to the destination location of the copied DVD do not

contain any blanks. If you perform a domain installation using the network drives for mapping the installation

DVD, make sure that the <sapsid>adm user has access to the UNC paths of the network drives.

1 Identify the archive files required to install your MDM servers according to your required type of MDM

installation:

Option Description

Central Installation ○ MDM Installation Master

○ Master Data Server Installation Package mdm-

server-<build>-<Windows platform>.zip

○ MDM Import Server Installation Package mdm-

import-server-<build>-< Windows

platform>.zip

○MDM Syndication Server Installation Package mdm-syndication-server-<build>-< Windows

platform>.zip

○ MDM Shared Installation Content Package mdm-

shared-<build>-< Windows

platform>.zip

Note

On DVD, the above MDM components reside

unpacked in the Server_Installation directory.

○ SAP Instance Framework Installation Package

Distributed Installation of Master Data Server ○ MDM Installation Master

○ Master Data Server Installation Package mdm-

server-<build>-<Windows platform>.zip



platform>.zip


Distributed Installation of MDM Import Server ○ MDM Installation Master

○ MDM Import Server Installation Package mdm-

import-server-<build>-< Windows

platform>.zip






Option Description



platform>.zip


Distributed Installation of MDM Syndication Server ○ MDM Installation Master

○ MDM Syndication Server Installation Package mdm-

syndication-server-<build>-< Windows

platform>.zip



platform>.zip


Distributed Installation of MDM Layout Server

○ MDM Installation Master

○ MDM Layout Server Installation Packagemdm-

layout-server-<build>-< Windows

platform>.zip



platform>.zip


2 Identify the files required for your MDM Windows client installation. For more information, see Installing MDM

Windows Clients [page 41].

3 Make the required installation media available on each installation host.






4 Installation of MDM Servers

This section describes how to install the following components:

● MDM servers (MDS, MDIS, MDSS, MDLS) using SAPinst.

● MDM Windows clients using MDM-specific installation executables

● Additional MDM Components using deployment tools for the respective platforms

● A database using the database-specific installation routine

4.1 MDM Installation Using SAPinst

You install the MDM servers as instances of an SAP system using SAPinst. In a single installation run, you can

install all MDM servers or a single MDM server on one host. This topic explains the prerequisites and the general

procedure.

These topics describe an installation where SAPinst, SAPinst GUI, and the GUI server are running on the same

host: When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secure SSL

connection to the GUI server and the GUI server connects to SAPinst.

● SAPinst includes a SAPinst GUI and a GUI server, which both use Java.

● SAPinst normally creates the installation directory sapinst_instdir, where it stored its log files. This

directory is located directly in the Program Files directory. If SAPinst is not able to create

sapinst_instdir in this location, it tries to create sapinst_instdir in the directory defined by the

environment variable <TEMP> .

● We recommend that you keep all installation directories until you are certain that the system has been

completely and correctly installed.

● SAPinst creates a subdirectory for each installation option called <sapinst_instdir>

\<installation_option_directory>.

● The SAPinst Self-Extractor extracts the executables to a temporary directory. These executables are deleted

after SAPinst has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can

safely delete them. The temporary directory also contains the SAPinst Self-Extractor log file

dev_selfex.out, which might be useful if an error occurs.

Caution

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

● During the installation, the default ports 21200, 21212, and 4239 are used for communication between

SAPinst, GUI server, SAPinst GUI, and HTTP server.

○ SAPinst uses port 21200 to communicate with the GUI server.

○ The GUI server uses port 21212 to communicate with SAPinst GUI.

○ 4239 is the port of the HTTP server, which is part of the GUI server.

If one of these ports is already in use by another service, an error message appears. In this case, proceed as

follows: Open a command prompt and change to the required directory as follows:



Installation of MDM Servers



cd <DVD drive>:\IM_WINDOWS_<platform>

Enter the following command in a single line:

sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>GUISERVER_HTTP_PORT=<free_port_number_http_server>

To get a list of all available SAPinst properties, go to the directory %TEMP%\sapinst_exe.xxxxxx.xxxx,

after you have started SAPinst, and enter the command

sapinst.exe -p

● To terminate SAPinst and the SAPinst Self-Extractor, choose one of the following options:

○ Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit.

○ Click the icon for the SAPinst output window located in the Windows tray and choose File Exit .

SAPinst GUI Functions

The following table shows the most important functions that are available in SAPinst GUI:

Input Type Label Description

Menu optionFile Exit

Stops the SAPinst GUI. SAPinst and

the GUI server continue running.

Note

During the installation, if you log

off from the host where you con

trol the installation with SAPinst

GUI, the installation continues.

You can reconnect to the same

SAPinst installation from the

same host or a different host

later on. For more information,

see Starting SAPinst GUI Sepa

rately.

Menu optionSAPinst Log Browser

Displays theLog Viewer

dialog boxin which you can access the follow

ing log files:

● Installation log (sa-

pinst_dev.log)

● Log files from the SAPinst GUI

server

These log files might help you dur

ing troubleshooting. For more infor

mation, see Troubleshooting Server

Installation.






Input Type Label Description

Menu optionSAPinst Cancel

Cancels the installation with the fol

lowing options:

● Stop

Stops the installation (SAPinst

GUI, SAPinst and the GUI

server) without making any fur

ther changes to the installation

files. You can restart and con

tinue the installation from this

point later on.

● Continue

Continues the installation

Message buttonRetry

Performs the installation step again

(if an error occurred)

Message button Stop Stops the installation without mak

ing any further changes to the in

stallation files You can continue the

installation from this point later on.

Message buttonContinue

Continues with the option that you

chose before

4.2 Starting the Installation

● You are using an account with the required user authorization to install the SAP system with the SAPinst tool.

● You are using an account with the required user authorization to install the SAP system with the SAPinst tool.

● Make sure that you have defined the most important SAP system parameters as described in Basic SAP

System Parameters [page 14] before you start the installation.

● Check that your installation host(s) meet(s) the requirements for the installation option(s) that you want to

install. For more information, see Hardware and Software Requirements [page 11].

1 Insert the SAP Installation Master DVD into your DVD drive or mount it locally.

2 Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.exe from the following path:

<DVD drive>:\Server_Installation\Installation_Master\MDM_IM_<platform>.

To use a virtual host name, start SAPinst as follows: sapinst.exe SAPINST_USE_HOSTNAME=<virtual

host name>

SAPinst GUI starts automatically by displaying theWelcome

screen.

3 In the Welcome screen, choose the required SAPinst installation option from the tree structure. For more

information, see SAPinst Installation Options [page 33].

To use the installation option Software Life-Cycle Options Operating System Users and Groups , you

must start it before you start the installation of the SAP system. Choose this option if the operating system






users do not yet exist and you do not want to create them manually. Make sure that you have the required

user authorization for these accounts before you start the installation.

4 If SAPinst prompts you to log off from your system, log off and log on again. SAPinst restarts automatically.

5 Follow the instructions in the SAPinst dialogs and enter the required parameters.

More information about the input parameters: section Basic SAP System Parameters [page 14]

6 To start the installation, choose Start.

SAPinst starts the installation and displays the progress of the installation. When the installation has

successfully completed, SAPinst displays the message, Execution of <Option_Name> has been

completed successfully.

7 After installation completes, we recommend that you delete all the files in the directory %userprofile%

\.sdtgui\.

4.3 SAPinst Installation Options

This section provides information about the installation options and software lifecycle options in SAPinst.

Note

To use global accounts that are configured on separate hosts, run the installation optionOperating System

Users and Groups before you start the installation of the SAP system (see Additional Software Life-Cycle

Options in the table below).

Central System:

Installation Option Description

MDM Central System Creates a new SAP system for MDM and installs the

following instances on a single host: MDS, MDIS, MDSS

Distributed System:


Master Data Server Creates a new SAP system for MDM and installs anMDS instance.

Installation Options:


Master Data Server (in an existing SAP system) Adds a new MDS instance to an existing SAP system,

which is suitable for running MDM.

Master Data Import Server (in an existing SAP system) Adds a new MDIS instance to an existing SAP system,

which is suitable for running MDM.

Master Data Syndication Server (in an existing SAP

system)

Adds a new MDSS instance to an existing SAP system,

which is suitable for running MDM







Master Data Layout Server (in an existing SAP system) Adds a new MDLS instance to an already existing SAP

system which is suitable for MDM. This option is only

available on Windows platforms.

Additional Software Lifecycle Options:


Operation System Users and Groups Creates all operating system accounts for your SAP

system. In most cases, this is optional. However, you

must execute this option to use global accounts that

are configured on separate hosts.

Configure TREX Configures MDS to connect to TREX (an additional

MDM component).

Configure SLD Generation Configures MDM instances for registration as technical

systems in the System Landscape Directory (SLD) Use

this option only for SAP NetWeaver Process Integra

tion (PI) 7.11 and higher. In lower versions of PI (or XI),

register MDM manually in the SLD.

More information:

● help.sap.com/nwmdm71 Monitoring and

Supportability: How-To Guides (ZIP) MDM 7.1

How To Register MDM in SLD (PDF)

● help.sap.com/nwmdm71 Scenario Configu

ration Guide Setting Up PI

Install and Configure CCMS Agent and MDM CCMS

Plug-in

Installs the SAP CCMS Agent with the MDM CCMS

plug-in and registers the agent in a central monitoring

system.

More information: help.sap.com/nwmdm71

Monitoring and Supportability: How-To Guides (ZIP)

How To Install and Configure MDM 7.1 CCMS Mon

itoring on Windows and UNIX (PDF)

Update MDM Updates all MDM instances of an SAP system. Use this

option to implement patches and support packages for

MDM servers.

Uninstall MDM Uninstalls all MDM instances and deletes the SAP sys

tem.

Related Information

Installing Additional MDM Components [page 45]






Updating MDM Servers [page 78]

4.4 Restarting an Interrupted Installation

The SAP system installation might be interrupted for one of the following reasons:

● An error occurred during the dialog or processing phase: SAPinst does not abort the installation in error

situations. If an error occurs, the installation pauses, and a dialog box appears. The dialog box contains a

short description about the choices listed in the table below as well as a path to a log file that contains detailed

information about the error.

● You interrupted the installation by choosing Exit in the SAPinst menu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure

without repeating any of the previous steps. This is

possible because SAPinst records the installation prog

ress in the keydb.xml file.

We recommend that you view the entries in the log

files, try to solve the problem and then chooseRetry

. If

the same or a different error occurs again, SAPinst dis

plays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box,

the SAPinst GUI, and the GUI server. SAPinst records

the installation progress in the keydb.xml file.

Therefore, you can continue the installation from the

point where you stopped without repeating any of the

previous steps. See the procedure below.

Continue SAPinst continues the installation from the current

point.

To restart an installation that you stopped by choosing Stop, or to continue an interrupted installation after an

error situation, perform the following:

1 Log on to your remote host as a user who is a member of the local administrators group.

2 Insert the installation DVD in the DVD drive or mount the installation DVD.

3 Restart SAPinst by double-clickingsapinst.exe. You can also start SAPinst by entering the following

command at the Windows command prompt: cd <DVD drive>:\MDM_IM_WINDOWS<platform> .

4 From the tree structure in the Welcome screen, select the installation option to continue and choose Next.

5 In theWhat do you want to do?

screen, choose one of the following options, and confirm withOK

.








4.6 Starting SAPinst GUI Separately

You might need to start SAPinst GUI separately in the following cases:

● You have logged off from SAPinst.

If you logged off during the installation and you later want to reconnect to the installation while it is still

running, start SAPinst GUI separately.

● You want to perform a remote installation.

If SAPinst GUI runs on a different host from SAPinst and the GUI server, you must start SAPinst GUI

separately.

Caution

With SAPinst, for remote installations, the client-server mode is not active by default, because SAP is notallowed to deliver the cryptographic library that is required for the encryption of client-server

communication due to legal requirements. For more information, see SAP Note 1238121 .

4.6.1 Starting SAPinst GUI on Windows

1 Log on as a member of the local administrators group.

2 Insert the installation DVD into your DVD drive.

3 Change to the directory of the SAPinst executables: <DVD drive>:\MDM_IM_WINDOWS_<platform>

Note

To start SAPinst GUI on a Windows 32-bit operating system, change to the following directory:

<Installation_Master_DVD>\SAPINSTGUI_710_WINDOWS_I386

4 Start SAPinst GUI by double-clickingsapinstgui.exe.

Note

You can start sapinstgui.exe with the following optional parameters:

○ host=<host name> , where <host name> is the host name of the installation host

○ port=<nr> , where <nr> is the port number for the connection to the GUI server

○ -accessible enables the Accessibility mode

For example: ./sapinstgui.exe host=lsi1209 port=3000 -accessible

SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default.

If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP

Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is

running and choose Log on. The first dialog of the installation appears and you can perform the remote

installation from your local host.







4.6.2 Starting SAPinst GUI on UNIX

1 Log on as user root.

Caution

Make sure that the root user has not set any environment variables for a different SAP system or database.

2 Mount your Installation Master DVD.

Note

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

3 Change to the directory of the SAPinst executables: <mountpoint_of_Installation_Master_DVD>/MDM_IM_<OS>

Note

To start SAPinst GUI on a Linux 32-bit operating system, change to the following directory:

<mountpoint_of_Installation_Master_DVD>/SAPINSTGUI_710_LINUX_I386

4 Start SAPinst GUI by executing ./sapinstgui.

SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default. If

SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation

GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and

choose Log on. The first dialog of the installation appears and you can perform the remote installation from

your local host.

Note

You can start sapinstgui with the following optional parameters:

○ host=<host name> , where <host name> is the host name of the installation host

○ port=<nr> , where <nr> is the port number for the connection to the GUI server

○ -accessible enables accessibility mode

For example: ./sapinstgui host=lsi1209 port=3000 -accessible .

4.7 Performing a Silent Installation of MDM Servers

You can install MDM servers silently without graphical output or user interaction.

Once you have run SAPinst for the first time, you can use the initialization file created by SAPinst for any

subsequent unattended installation.

For the detailed procedure, see SAP Note 950619 .







4.8 Installation Entries in the Services File

Once the installation is complete, SAPinst creates the following entries in <drive:>\WINDOWS

\system32\drivers\etc\services:

sapdpXX = 32XX/tcp

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

where XX is set from 00 to 99.

Note

There can be more than one entry for the same port number.

4.9 Troubleshooting Server Installation

If an error occurs, SAPinst:

● Stops the installation

● Displays a dialog informing you about the error

When errors occur during the installation with SAPinst, proceed as follows:

1 To view the log file, choose View Logs.

2 If an error occurs during the dialog or processing phase, perform one of the following:

○ Try to solve the problem.

○ Abort the installation with Exit and restart.

○ Continue the installation by choosing Retry.

3 Check the log and trace files of the GUI server and SAPinst GUI in the following directory for errors:

%userprofile%\.sdtgui\

○ If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current user directory.

○ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI separately.

Related Information

Restarting an Interrupted Installation [page 35]

Starting SAPinst GUI Separately [page 37]











5 Installing MDM Windows Clients

This section explains how to install the MDM Windows clients on released Windows platforms. MDM Windows

clients are administration clients (for example, the MDM Console) and data management clients (for example, the

MDM Data Manager or the MDM Import Manager).

Note

To run MDM Windows clients, a Windows user must have read/write access to HKLM/SOFTWARE/SAP/MDM

7.1 in the Windows registry.

You can choose between the following installation modes:

● Install the components one by one making installation settings in a graphical user dialog.

● Install one component or a set of components "silently", making the settings in a Windows initialization file

(extension .ini).

1 Check the Product Availability Matrix (PAM) for supported Windows releases on SAP Service Marketplace

service.sap.com/pam . Go to SAP NETWEAVER and select SAP MDM.

2 Log on to your host as a user with administrator rights.

3 Download the MDM installation archives from SAP Service Marketplace or insert the installation DVD in your

DVD drive.

4 Extract the MDM installation executables.

5.1 Using GUI Mode

Double-click the installation executables one by one and follow the instructions on the screen.

5.2 Using Silent Mode for a Single Windows Client

Note

Check whether installation was successful using the install.log file, which is written to the corresponding

installation directory for each component.

1 Open a Windows Command Prompt and navigate to the folder containing the extracted installation

executable(s).

2 Launch the executable and pass the parameter /s and the path to an initialization file (for example, enter

MDMImportManagerInstall.exe /s install.ini). With the optional initialization file you can override


Installing MDM Windows Clients






the default installation settings. You can use one .ini file for all components. We ship a sample .ini file

together with the installation executables. For more information about the file structure and the individual

settings, see comments in the initialization file.

5.3 Using Silent Mode for Multiple Windows Clients

1 Create a Windows batch file (create a new .txt file and rename it to .bat file).

2 Open the batch file in a text editor and enter one installation command for each component in separate lines.

For a lean MDM client installation, the batch file might look as follows:

MDMConsoleInstall.EXE /s install.iniMDMDataManagerInstall.EXE /s install.iniMDMImportManagerInstall.EXE /s install.iniMDMLanguageSelectorInstall.EXE /s install.iniMDMSyndicatorInstall.EXE /s install.ini

With the optional initialization file you can override the default installation settings. You can use one

initialization file for all components. We ship a sample .ini file together with the installation executables. See

the initialization file for more information about the file structure and the individual settings.

3 Save the batch file and launch it either by double-clicking it or using a Windows Command Prompt.

Note

Check whether installation was successful using the install.log file, which is written to thecorresponding installation directory for each component.

5.4 MDM Windows Clients

Component

[Shipped Files]

Prerequisites Remarks

MDM Console

[MDMConsoleIn-

stall_<build>.exe]

MDM CLIX

[MDMCLIXInstall_<build>.exe]

The MDM Console and CLIX must

have TCP/IP access to the MDS.

The machine running the MDM Con

sole and MDM CLIX must be in the

same network domain as the MDS.

The Console and CLIX user must

know the user name and password

for the DBMS server with read/

write/create permissions.

The administration command line

tool MDM CLIX is automatically in

stalled with the MDS (at <system

drive>:\usr\ sap\<SAPSID>

\<Instance Folder>\exe ).

You only need to install the tool

manually for remote access to MDS,

for example, from a local PC.






Component

[Shipped Files]


The Console and CLIX user must

have read/write permissions on the

MDS machine.

To use the Start Server command in

the Console, the logged-in Windows

user must have permission to start

the MDS service on the (remote)

machine.

MDM Data Manager

[MDMDataManagerIn-

stall_<build>.exe]

The MDM Data Manager must have

TCP/IP access to the MDS. This

connection can be local or remote.

Install MS Visio on the machines on

which you want to model (not run)

MDM workflows.

In MS Visio, make the following set

tings for MDM Workflow:

● UnderTools Options Ad

vanced File Paths ...

set both Add-ons and Start-up

to the folder where MDM VSL is

installed (C:\Program Files

\SAP MDM 7.1\Workflow

\VSLin a standard Windows in

stallation).

● UnderTools Options

Security choose Enable Auto

mation Events

.

MDM Import Manager

[MDMImportManagerIn-stall_<build>.exe]

MDM Syndicator

[MDMSyndicatorIn-

stall_<build>.exe]

The MDM Import Manager and the

MDM Syndicator must have TCP/IP

access to the MDS. This connection

can be local or remote.

To enable the MDM Import Manager

to generate XML schemas from

XML files upon import, the xsd.exe

must reside in the same folder as

the Import Manager executable.

The xsd.exe is part of the Micro

soft .NET Framework SDK (Soft

ware Development Kit) 2.0, which

can be downloaded from the down

load center of the Micrsosoft web

site.

MDM Language Selector

[ MDMLanguageSelectorIn-

stall_<build>.exe]

To display the MDM client compo

nent's user interfaces correctly inEast Asian languages, you may need

to install these languages on Win

dows ( Settings Control Panel

Regional and Language Options

Languages

).

Languages

[MDM_UOMManagerIn-

stall_<build>.exe]

The client software of the underly

ing database must be installed on

the UOM Manager host.






Component

[Shipped Files]


MDM Image Manager

[MDMImageManagerIn-

stall_<build>.exe]

You must install Adobe Photoshop®

before installing the Image Man

ager. The Image Manager must

have TCP/IP access to the MDS.

This connection must be local to be

effective.

MDM Publisher

[MDMPublisherIn-

stall_<build>.exe]

MDLS must be installed first.

MDM Indexer

[MDMIndexerIn-

stall_<build>.exe]

MDM Publisher must be installed

first.

InDesign® Plug-In

[InDesignPlugin<InDesign

version>Install_<build>.exe]

Adobe InDesign® must be installed

first.

The machine on which the plug-in is

installed must have TCP/IP access

to the MDS, MDLS, and Data Man

ager. This connection must be local

to be effective.

The Plug-In for InDesign version

CS3 requires the Microsoft Visual C

++ 2005 SP1 Redistributable Pack

age (x86), which you can download

from the Microsoft web site.

Install the MDM plug-in in the InDe

sign default plug-in directory.






6 Installing Additional MDM Components

Component

[Shipped Files]

Prerequisites / Remarks Installation Procedure

MDM Java API and MDM Connec

tor

For hosted applications, you need

SAP NetWeaver 2004 or 7.0. For

standalone applications, you need a

Java 1.4.2 compatible Java Virtual

Machine.

Deploy the components on your

Java machine.

For more information, see MDM

Java and .NET API Guide at

help.sap.com/nwmdm71

MDM Portal Content MDM Connector and MDM Java API

are deployed (see above).

Deploy the components on your EP.

For more information, see Portal

Business Package for Master Data

Management at help.sap.com/

nwmdm71

MDM PI Adapter The SAP NetWeaver Process Inte

gration (PI) is installed. MDM Con

nector and MDM Java API are de

ployed (see above).

Deploy the components and the

adapter content on your PI. For

more information, see MDM Proc

ess Integration (PI) Adapter Guide at


MDM ABAP API An ABAP system is installed. Deploy components on your ABAP

system as SAP Add-On. For more

information, see MDM ABAP APIand the application help of transac

tion SAINT at help.sap.com/

nwmdm71.

MDM Web Services For more information, see MDM

Web Services at help.sap.com/

nwmdm71

MDM DOTNET API For more information, see MDM

Java and .NET API at help.sap.com/

nwmdm71

MDM COMAPI

[MDMCOMInstall_<build>.exe]

As Microsoft .NET is the technological successor of Microsoft COM, the

MDM COM API is deprecated with

MDM 7.1. Customers are advised

not to start any new projects based

on the MDM COM API and to con

sider migration to the Micro

soft .NET framework, as the MDM

COM API will not be part of the next

MDM release.


Installing Additional MDM Components














Component

[Shipped Files]


MDM Enrichment Controller SAP Web Application Server 6.40(Java), MDS, MDIS, and MDSS are

installed. MDM Connector and MDM

Java API are deployed (see above).

For more information, see MDM Enrichment Architecture at

help.sap.com/nwmdm71 .

TREX Client

[MDMProtocolHandler.dll]

The TREX server must be version

7.1.

For performance reasons we rec

ommend that you install TREX

server and MDS on different hosts.

If you install them on the same host,

both must be 64bit versions.

When installing TREX server for use

with MDM there is no need to set a

communication protocol.

The MDS host must have incoming

TCP traffic enabled on port 59950.

If there is a firewall on the MDM

server, the firewall must be config

ured to permit traffic on this port.

The MDM-TREX integration sup

ports English documents only. For

more information about TREX in

stallation see service.sap.com/

installNW70 . Go to Installation-

Standalone Engines

and choose

SAP NetWeaver Search and Clas

sification TREX

1 If MDS and TREX server reside

on different hosts, you must in

stall a TREX instance on the

MDS host. This additional TREX

is used as a client for MDM.

To use TREX as client for MDM,

disable the server aspect of the

additional TREX. For more infor

mation, see SAP Note 1133493

.

2 On your MDS host, start SA

Pinst, choose Additional

Software-Lifecycle Options

TREX Configuration

and fol

low the instructions on the

screen.

3 On your TREX server host, stop

the TREX server processes.

4 Copy the file MDMProtocol-

Handler.dll to the TREX

server executables directory

(this directory also contains

TREXPreprocessor.exe).

5 Open the Properties dialog of

the DLL. On theSecurity

tab

page, verify that the TREX serv

ice user (SAPSer

vice<TREX_SID>) or a group

the TREX user is member of (forexample SAP_<TREX_SID>Lo

calAdmins or SAP_LocalAd

min), has all permissions for the

DLL.

6 Open the TREXPreproces-

sor.ini file located on the

TREX server.

7 Search for a section in the

TREXPreprocessor.ini file

called [protocol]. If this section






http://help.sap.com/disclaimer?site=http://service.sap.com/installNW70

http://help.sap.com/disclaimer?site=http://service.sap.com/installNW70




Component

[Shipped Files]


does not exist, add it to the end

of the file.

8 In the [protocol] section, add

the following line (if it does not

already exist): mdm=mdswrap

9 Save and close TREXPrepro-

cessor.ini and restart the

TREX server processes.

MDM Web Dynpro SAP NetWeaver MDM Web Dynpro

Framework 7.1 SP5 Patch 2 or

higher

For more information, see

help.sap.com/nwmdm71. Go to De

velopment Information

and chooseMDM Web Dynpro Components

.

Refer to the following sections:

● Installing the MDM Web Dynpro

Environment

● Deploying the MDM Web Dyn

pro Components Framework

MDM Collaborative Processes for

Material

MDM Collaborative Processes for

Material 7.10 7.20

For more information, see

help.sap.com/nwmdm71. Go to

MDM Business Content Exten

sions

and chooseCollaborative

Processes for Material Master

Data Creation










Client Network Utility to create an alias for that instance. You then refer to the alias instead of the fully

qualified name in all MDS interactions. You can use any collation.

2 When using MDM in an environment where the SQL Server DBMS and MDS are located on separatemachines, you might need to change the network connection between the MDS and the DBMS from the

default connection.

This configuration is done using the SQL Server Network Utility:

a) To access this utility, right-click on the DBMS Server in SQL Server Enterprise Manager, choose

Properties from the context menu, and choose Network Configuration from the General tab.

b) Check if there are any features of your local system which will work better with a particular protocol.

3 Change the security settings from the default Windows Security to SQL and Windows.

7.1.1 Database Performance Tips

● SQL Server’s performance increases when the main data file (.mdf) and the transaction log file (.ldf) are

located on separate spindles. Remember that this involves using different drives and not just different drive

letters.

● When MDS creates database schemas, it does not set the recovery method. So SQL Server creates a new

database schema with the method that the "model" database uses. If you wish to explicitly use a setting

different than "model", use one of the following parameters in the top section of mds.ini:

○ SQL Server Recovery Type=Full

○ SQL Server Recovery Type=Simple

○ SQL Server Recovery Type=Bulk_Logged

Unarchiving mainly BLOB-based repositories (containing many PDFs, pictures and so on) runs significantly

faster when using Simple or Bulk_Logged. On other repositories Full is slightly faster.

● Define the storage paths.

The first time you connect the MDS to the database using MDM Console, a dialog box appears asking for Data

path and Log path. This optional step may slightly improve performance: If you leave these fields blank, MDM

creates tablespaces in the default directory of SQL Server. While this is acceptable in most cases, you may

wish to specify other locations on the database host machine. Furthermore, if you choose different locations

for the Data path and Log path so that they are on different hard disks (different physical spindles, not just

logical drives), database performance may improve by a small degree.

The directory paths you specify must already exist on the database host machine.

●MDM repositories use one, two or four schemas.MDM data is divided into four types of data collections: Main, Originals, Thumbnails, and Variants. In a two

partition arrangement, Main and Originals are placed in one partition, with Thumbnails and Variants being

placed in the other. With four partitions, each data collection type has a separate partition (Schema and

Tablespaces).

Choosing two or four partitions gives you the option of performing SQL Server-based backups on a different

schedule for the various partitions. Since Thumbnails and Variants can be recreated through MDM, these can

be backed up less frequently or not at all. For many use cases, Originals change at a less frequent rate than

Main data. This means they can also be backed up less frequently in

● With SQL Server 2005, the Full-text Indexing feature is automatically on. Since MDS does not need this

feature, it is explicitly turned off when creating repository database schemas. This slightly improves

performance for many database operations. To override the default and enable this feature at repository

creation, enter the following in the top section of mds.ini: SQL Server Enable Full-Text Indexing=true


Installing and Configuring the Database




7.2 Oracle DBMS

Install Oracle and Create a Database Instance

● Install both DBMS and client of Oracle if you plan to host Oracle on the same machine as MDS. If the DBMS

and MDM reside on different hosts, the MDS host requires the installation of the Oracle client.

Note

When installing the Oracle Database, in the step where you select the installation option, make sure youselect

Create and configure database

(and notInstall database software only

).

● If the MDS and the DBMS are on the same machine, use the Net Configuration Assistant to define a Listener

address and local Service Name that uses the IPC protocol rather than TCP. This affects the listener.ora

and tsname.ora files, which can also be edited manually. This increases the repository unarchive

performance.

● To determine the Oracle client versions that are supported for the various DBMS versions, refer to the Oracle

server/client interoperability support matrix.

Note

In earlier versions of Oracle, by default, passwords did not expire. Starting from Oracle 11, the default isthat passwords expire in 180 days. Password expiration has a negative impact on MDS. This is due to the

fact that during the days before the password expires, warning messages about password expiration

interfere with MDS operations.

● Oracle’s performance increases when separate spindles (hard disks) are used for the main data and indices.

Rollback segments (for transactions and logging) are set at database instance creation time and can

represent an opportunity to use three separate spindles. The location of the main and index files can be set

before repository creation, unarchiving, or duplication via the Console.

● Make sure that you reboot the machine after a new installation of Oracle on a Windows platform so that the

MDM service can inherit the Oracle path from the system.

● The <Cursor Sharing>

parameter is set on a session basis to be exact. This provides a small performance

improvement for certain operations between MDS and the Oracle Server. For earlier versions of MDM, you

can turn this parameter on globally for the entire Oracle instance with the following command:

ALTER SYSTEM SET cursor_sharing='EXACT' scope=BOTH

● MDM requires particular character sets:

○ National Character Set: Choose a Unicode character set, such as UTF8 or AL16UTF16.

○ Database Character Set: Choose a Unicode character set, such as UTF8 or AL32UTF8.

Caution

Unicode character sets are the only character sets that MDS supports. Do not use an Oracle database

instance that has different character sets for MDM. To use an existing database instance, run the

following queries to determine the character sets:






○ National Character Set:

select VALUE from NLS_DATABASE_PARAMETERS where

PARAMETER='NLS_NCHAR_CHARACTERSET'

○ Database Character Set:select VALUE from NLS_DATABASE_PARAMETERS where

PARAMETER='NLS_CHARACTERSET'

If the results of the above queries do not return Unicode character sets, you must create a new

database instance for MDM.

For more parameter recommendations for Oracle 10g, see SAP Note 830576 .

7.2.1 Setting Up the Database

1 To connect to the database, create an entry in the tnsnames.ora file. On Windows, the tnsnames.ora file

is typically located in \oracle\...\network\admin.

The entry must use the following format:

<net service name specified in the MDM Console as DBMS server> = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <fully qualified IP address ordomain of the host machine running the Oracle DBMS>)(PORT=<number of the portused by DBMS host with default 1521>))

) (CONNECT_DATA = (SERVICE_NAME = <Oracle service name specified when the Oracle DBMSwas installed>) ) )

Test the net service name by logging onto the Oracle database from the MDS host using the Oracle SQLPLUS

command sqlplus <userid>/<password>@<net service name>

Alternatively, test the connection to the Oracle database with the command tnsping <net service

name>

2 On the MDS host, run the Net Manager to make the DBMS known to Oracle clients. In this case, the MDS is an

Oracle client.

7.2.2 Connecting MDS to the Database

1 Modify the temporary tablespace.

When connecting to the DBMS for the first time (DBMS initialization), the system account or an equivalent

account is used to make the connection and the DBMS is queried for the temporary tablespace of that

account. Normally this tablespace is named TEMP. If the site needs to use a different tablespace, modify the

temporary tablespace of the connecting account prior to DBMS initialization.








2 Set the user account.

The first time that the MDS connects to the database, the MDM Console asks which user account to use to

connect to the DBMS. By default you use the SYSTEM account for all access. To use another account or if the

use of the SYSTEM account is not allowed in your DBMS, use the SYSTEM account, or the MDM Console/

CLIX feature to create an alternative account. Model your account creation according to the following

template:

create user HARRY_POTTER identified by muggles default tablespaceSYSTEM;grant alter user, alter system, create session, create any index,create view, dba, drop any view, create any table, delete any table,drop any table, insert any table, update any table, select any table,alter tablespace, create tablespace, drop tablespace,unlimited tablespace, create any sequence, drop any sequence, alter anysequence, selectany sequence, lock any table, alter any table,alter any type, alter database, create profile, drop profile, create

database link, drop any index, create user, drop user, create anydirectory, create any procedure, analyze any to HARRY_POTTER;

3 Define the tablespace directories.

The first time that you connect the MDS to the database using MDM Console, a dialog box appears asking you

where you want to store data and index tablespace files. These settings apply to repositories only as they are

created. Existing repositories stay where they were created.

a) If you leave these fields blank, MDM creates tablespaces in the default tablespace directory. While this is

acceptable in most cases, you may wish to specify other locations on the database host machine. If you

choose different locations for the data tablespace and index tablespace so that they are on different hard

disks (different physical spindles, not just logical drives), database performance can improve by a small,

but significant, degree. The directory paths you specify must already exist on the database host machine.

b) These settings apply to repositories only as they are created. Existing repositories stay where they were

created.

c) To gain even more detailed control your tablespaces, or to use tablespaces that already exist, see

Allowing Flexible Tablespaces [page 53].

Note

After a repository is created through create, unarchive, duplicate or slave operations, all tables and

indexes are analyzed in the final step. We recommend that you re-analyze tables to maximize the

performance of the DBMS rom time to time and especially if your repository has gained or lost a

significant number of records (for example from a large import).

4 To mount an MDM repository residing in an Oracle DBMS, specify the Oracle Net Service Name as the DBMS

server in the Add DBMS Server dialog. This name should be defined using Oracle networking methodologies.

7.2.3 Adjusting Temporary Tablespace for MCOD

For MCOD (MDM sharing the same database with other SAP components, such as SAP ERP ECC or SAP

NetWeaver Application Server), check and adjust the temporary tablespace.

The first time MDS establishes a relationship with a particular Oracle instance, it queries the temporary

tablespace name of the initial login, for example SYSTEM. The retrieved value, for example TEMP, is stored in






MDM in the A2i_xCat_DBs.A2i_DB_Settings table in the TempTableSpaceName field. MDM queries this table

when creating more users or schemas.

In an MCOD environment where the database has been installed with SAP NetWeaver AS Java using SAPinst, the

temporary tablespace is set to PSAPTEMP.

To adjust the temporary tablespace setting, proceed in one of the following ways:

○ In the MDM Console, choose DBMS Settings from context menu of your MDS and set the Temp

tablespace name.

○ Use the following CLIX command:

clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> TempTableSpaceName=PSAPTEMP

7.2.4 Allowing Flexible Tablespaces

You can detach from the methods built into MDM for the creation of Oracle database storage. As an experienced

database administrator, you can utilize even more of the flexibility and power that the database provides.

Background

In Oracle, data elements are stored in tables. Collections of tables are grouped together into schemas. Tables (or

schemas) are then assigned to logical storage entities called tablespaces. By using the logical concept of a

tablespace, Oracle allows you to manage the actual files that are used for a tablespace independent of the

schemas and tables.

By default MDM applies the following data storage concept:

● MDM repositories use one, two or four schemas.

MDM data divides into four types of data collections: Main, Originals, Thumbnails, and Variants. In a two

partition arrangement, Main and Originals are placed in one partition, with Thumbnails and Variants being

placed in the other. With four partitions, each data collection type has a separate partition (schema and

tablespaces).

Note

Choosing two or four partitions gives you the option of performing Oracle based backups on a different

schedule for the various partitions. Since Thumbnails and Variants can be recreated through MDM, these

can be backed up less frequently or not at all. For many use cases, Originals change at a less frequent rate

than Main data, so they, too, can be backed up less frequently in a four partition configuration.

● MDM creates two tablespaces for each schema, one for data and the other for indexes. The names of the

schemas are derived from the repository name, and in turn the tablespace names are derived from the

schema names.

● MDM uses a single directory location on an individual DBMS for all data tablespaces and another single

directory for index tablespaces. These two settings are controllable from the MDM Console.






This arrangement is convenient for the majority of use cases; however, it limits the full control of location and

other parameters in the creation and management of tablespaces that are possible in Oracle databases. You can

create tablespaces according to the requirements of your particular installation as described below.

7.2.4.1 Enhancing Tablespace

MDS can use tablespaces that preexist in a database as an alternative to creating them. The configuration of such

a custom tablespace is maintained on the DBMS in the following table:

A2I_XCAT_DBS.A2I_DB_SETTINGS

You must add several rows that are not automatically created through use of the MDM Console or CLIX, by

manually using scripts and/or SQL*Plus utility of Oracle. Once these rows are created, they can be maintained

using the MDM Console.

The A2I_XCAT_DBS.A2I_DB_SETTINGS table creates the following records:

NAME column SETTING column Explanation

DataPath Actual path or empty Already exists and managed by

MDM Console. A single directory

where data tablespaces are created.

IndexPath Actual path or empty Already exists and managed by

MDM Console. A single directory

where index tablespaces are cre

ated.

tsname_m Name of tablespace you created Tablespace name for main reposi

tory schema tables. If this record is

missing or the Setting column is

blank or empty, the DataPath re

cord is used to create a new table

space.

tsname_mx Name of tablespace you created Tablespace name for main reposi

tory schema tables indexes. If this

record is missing or the Setting col

umn is blank or empty, the IndexPath record is used to create a new

tablespace.

tsname_o Name of tablespace you created Tablespace name for originals repo

sitory schema tables. If this record

is missing or the Setting column is

blank or empty, the DataPath re

cord is used to create a new table

space.

tsname_ox Name of tablespace you created Tablespace name for originals repo

sitory schema tables indexes. If this







NAME column SETTING column Explanation

umn is blank or empty, the Index

Path record will be used to create a

new tablespace.

tsname_t Name of tablespace you created Tablespace Name for Thumbnails

Repository Schema Tables. If this


umn is blank or empty, the “Data

Path” record will be used to create a

new tablespace.

tsname_x Name of tablespace you created Tablespace name for thumbnails re

pository schema tables indexes. If

this record is missing or the Setting

column is blank or empty, the IndexPath record will be used to create a

new tablespace.

tsname_v Name of tablespace you created Tablespace name for image variants

repository schema tables. If this re

cord is missing or the Setting col

umn is blank or empty, the Data


new tablespace.

tsname_vx Name of tablespace you created Tablespace name for image variants

repository schema tables indexes. If

this record is missing or the Setting

column is blank or empty, the Index


new tablespace.

To initially create the A2I_XCAT_DBS schema and A2I_DB_SETTINGS table on a DBMS from the MDM Console,

choose DBMS Settings from the MDS Server node context menu or from the Server menu. Once created, insert

the eight necessary records listed in the table above by using the Oracle Enterprise Manager, or with a script using

SQL*Plus.

The following sample script utilizes eight separate tablespaces. The password for the a2i_xcat_dbs account is the

same as the one used to initially connect using the DBMS Settings dialog:

connect a2i_xcat_dbs/<myPassword>@<myInstance>;insert into a2i_db_settings (name, setting) values ('tsname_m', 'MMM');insert into a2i_db_settings (name, setting) values ('tsname_o', 'OOO');insert into a2i_db_settings (name, setting) values ('tsname_t', 'TTT');insert into a2i_db_settings (name, setting) values ('tsname_v', 'VVV');insert into a2i_db_settings (name, setting) values ('tsname_mx', 'MMM_IX');insert into a2i_db_settings (name, setting) values ('tsname_ox', 'OOO_IX');insert into a2i_db_settings (name, setting) values ('tsname_tx', 'TTT_IX');insert into a2i_db_settings (name, setting) values ('tsname_vx', 'VVV_IX');commit;








To return this DBMS to the state where MDS automatically creates tablespaces, manually delete these records

from the database. This cannot be done from the MDM Console; use the following script:

connect a2i_xcat_dbs/<myPassword>@<myInstance>;delete a2i_db_settings where name like 'tsname_%';commit;

Note

● When you choose this alternate method of tablespace assignment, you must create the tablespaces by

yourself. To test what you have done with these assignments, create a new repository by using four

partitions and examine the results in report files, or by using the Oracle Enterprise Manager.

● The settings in A2I_XCAT_DBS.A2I_DB_SETTINGS table are queried when MDS performs a duplicate,

unarchive, create new, or create slave operation. Afterwards these tablespace settings remain associated

with that repository even if you change the settings prior to creating another repository.

●

The contents of the NAME column are case-sensitive. Make sure that you use tsname_o and no otherspelling.

● Once you have created these eight records in the A2I_DB_SETTINGS table, you can change the setting

values using the DBMS Settings dialog of the MDM Console. This dialog does not allow you to add or delete

records or change the name of an existing record. To change the name of a record or to delete records, use

the Oracle Enterprise Manager or SQL*Plus utilities.

● The History table, which is used for auditing, does not fall under this manual tablespace management

approach and still uses the settings for DataPath and IndexPath.

● When you create your own tablespaces, you must monitor their growth and manage the way that the size

of the tablespace files is extended

More Sample Scripts

● The following example shows a tablespace definition that is typical for the main data partition of an MDM

repository where the tablespace is comprised of two files that can grow indefinitely:

CREATE TABLESPACE MDSDATA DATAFILE '/usr/db/ts/mdsdata1.dbf' SIZE 1M REUSE AUTOEXTEND ON NEXT 1M MAXSIZE UNLIMITED, '/usr/db/ts/mdsdata2.dbf' SIZE 1M

REUSE AUTOEXTEND ON NEXT 1M MAXSIZE UNLIMITEDDEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);

● The following example shows a tablespace definition similar to the previous example, except that the file

system limits files to 2 GB and you allocate the entire file space immediately to avoid disk fragmentation:

CREATE TABLESPACE MDSDATA DATAFILE '/usr/db/ts/mdsdata1.dbf' SIZE 2048M, '/usr/db/ts/mdsdata2.dbf' SIZE 2048MDEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);

● The following example shows a tablespace definition that is typical for an MDM repository index tablespace.

CREATE TABLESPACE MDS_IDX DATAFILE

'/usr/db/ts/mds_idx.dbf' SIZE 128K REUSE AUTOEXTEND ON NEXT 64K MAXSIZE UNLIMITED






DEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);

7.3 IBM DB2 for Linux, UNIX, and Windows

See Installing and Setting Up MDM with IBM DB2 for Linux, UNIX, and Windows at help.sap.com/nwmdm71 .

7.4 IBM DB2 for z/OS

Note

MDM repositories on IBM DB2 for z/OS are limited to 24 languages.

The minimum system requirements for an SAP MDM installation are as follows:

● IBM DB2 for z/OS Version 8 in New Function Mode

● IBM DB2 Driver for ODBC and CLI Version 9 FixPak 1

Caution

You must use this driver for connectivity between the database and your MDM server.

The following sections describe how to install the CLI driver.

7.4.1 Downloading the Archive

1 Create a directory in which to install the CLI driver. In the documentation, this directory is

<db2_cli_odbc_driver>.2 Download the CLI driver file:

If you are an SAP OEM customer, you can download the file from the SAP Service Marketplace at

service.sap.com/swdc . Go to Download Database Patches (from other vendors) DB2 for z/OS

IBM DB2 Driver for ODBC, CLI and JDBC, <version and FixPak>

. There is no top directory in this archive.

If you are an IBM customer, obtain the file from IBM. In this case, the top directory in the archive is

clidriver.

3 Extract the file to the directory <db2_cli_odbc_driver>

If you downloaded the file from the SAP Service Marketplace, extract it using SAPCAR to

<db2_cli_odbc_driver>. For more information about SAPCAR, see SAP Note 212876 .













7.4.6.1 BIND and GRANT with SAP NetWeaver AS Java

You do not need SAP NetWeaver AS Java to install MDM. However, if SAP NetWeaver AS Java is installed, you can

use the following procedure to BIND and GRANT:

First, call the DBA Cockpit (or transaction DB2) on your SAP Solution Manager system and perform these steps

remotely for the MDM system.

For general information about the Solution Manager, see the SAP Solution Manager documentation at

service.sap.com/solutionmanager .

The procedure for performing the BIND and GRANT steps depends on the version of your SAP NetWeaver AS

Java.

NoteBefore you begin, check that the user who is installing MDM and the MDM user generated during the

installation process have the correct permissions for BIND and GRANT. For details on permissions, see the

Security Guide for DB2 for z/OS at service.sap.com/instguidesnw , go to <SAP release> and choose

Operations.

SAP Solution Manager 3.0 or 3.1 (SAP Web AS ABAP 6.20 or 6.40)

To perform BIND and GRANT through a remote connection from SAP Solution Manager version 3.0 or 3.1 on an

SAP Web AS ABAP 6.20 or 6.40 system, use the following procedure:

1 Apply CCMS transport SAPK640OCO. For more information, see SAP Note 427748 .

2 Download the executable db2radm patch 9 into your kernel directory.

3 Call SAP transaction DB2 and select the Checks/Settings tab.

4 Choose MDM Configuration and enter the following parameters for the DB2 subsystem of the remote MDM

system:

a Database host name

b Database port number

c Database SSIDd Database location name

e MDM connect user

The user ID that is specified in transaction DB2J to execute stored procedures on the Profiles panel is used to

grant the necessary privileges to the MDM connect user. Therefore, ensure that this user ID has sufficient

authorization.






http://help.sap.com/disclaimer?site=http://service.sap.com/instguidesnw

http://help.sap.com/disclaimer?site=http://service.sap.com/solutionmanager



SAP Solution Manager 4.0 (SAP NetWeaver 7.00 or Higher)

To perform BIND and GRANT through a remote connection from SAP Solution Manager 4.0 on an SAP Web ASABAP 7.00 system or higher, use the following procedure:

1 Apply SAP basis support package 12.

2 Download the executable db2radm patch 4 into your kernel directory.

3 Call the DBA Cockpit (or transaction DB2).

4 Define a connection to the DB2 subsystem of the MDM system.

5 In the Configuration section, choose JCL Settings (DB2J) to specify the TSO user ID to be used to run stored

procedures. You do this in Profiles.

The TSO user ID must have sufficient privileges in the DB2 subsystem of the MDM system to grant

authorization to the MDM connect user.

6 Specify the password for this user ID on the JCL Settings panel. For more information, see Security

Considerations for Stored Procedures in the SAP DBA Guide for DB2.

7 Choose MDM Configuration in the Configuration section of the DBA Cockpit.

a Check whether the parameters for the DB2 subsystem of the MDM system are correct.

b Specify the MDM connect user.

8 Choose MDM Bind and Grant Action to perform the bind and grant task.

7.4.6.2 BIND and GRANT without SAP NetWeaver AS Java

To perform a BIND and GRANT in an environment without SAP NetWeaver AS Java, perform the following:

1 Download sapcar from the SAP Service Marketplace at service.sap.com/swdc . Go to Support

Packages and Patches Support Packages and Patches Browse our Download Catalog Additional

Components SAPCAR <SAPCAR version>

This tool enables you to unpack the files that you need to download to BIND and GRANT.

2 Unpack SAPEXEDB.SAR on your local system using SAPCAR.

3 Set the environment variable DIR_LIBRARY to location of unpacked executables.

4 Download DB2RADM and Kernel Part II (minimum Patch Level 48) to any location within the path you

specified in the environment variable. You can download the support packages from the SAP Service

Marketplace at: service.sap.com/swdc . Go to Support Packages and Patches Browse our

Download Catalog Additional Components SAP Kernel SAP KERNEL 64-BIT UNICODE <SAP

KERNEL version> <Operating System>

5 To BIND and GRANT, enter the following at the command prompt of your system:

db2radm –m mdmi –P <DDF Port> -L <DDF Location> -S <Database Name> -H <Host Name> -

U <Database Connect User> -u <Admin User> -p <Admin Password>









7.4.7 Creating the STOGROUP (Optional)

When you initialize DB2 for MDM, the STOGROUP SAPMDM is created with the VCAT of STOGROUP SYSDEFLT. If

you do not want this to happen, you must create the STOGROUP now.

7.4.8 Creating Foreign Keys

SAP MDM creates foreign keys very frequently. When a referenced table is converted, the status of the tablespace

containing the table is set to CHECK PENDING. The MDS resets the CHECK PENDING status to read-write (RW)

by calling the DB2 CHECK utility from the stored procedure DSNUTILS.

7.5 MaxDB

If you plan to host MaxDB on the same machine as MDM, install only the MaxDB server software (which includes a

MaxDB client). If the MaxDB server and MDS reside on different hosts, you must also install the MaxDB client

software on the MDS host. Due to specific database restrictions, MDM repositories can contain no more than 17

data languages when working with MaxDB. The MaxDB client version must be one of the following:

●7.7.07.41 and later

● 7.8.02.28 and later

● 7.9.08.02 and later

To install MaxDB:

1 Log on as a user with administrator rights.

2 Install the MaxDB client software using the MaxDB Installation Manager:

a) Start SDBSETUP.

b) Start installation/upgrade

c) Select component group Client.

d) Edit the following independent data path:<LW>\sapdb\data

e) Edit the following independent program path: <LW>\sapdb\programs

f) Install.

3 Install the MaxDB server software and create an MDM database instance using the MaxDB Installation

Manager:

a) Start SDBSETUP.

b) Startinstallation/upgrade

.

c) Select component groupsServer + Client

.

d) Choose Install software and create database instance.

e) Select SAP MDM.

f) Edit installation prefix <LW>\sapdb and define the following:

○ Database name (default: MDM)






○ Password of the database manager operator (default user: DBM)

○ Password of the database system administrator (default user: DBA)

g) Define the locations of the database volumes (default: 1 DATA volume with 2 GB; 1 LOG volume with 200

MB)

h) Define the following system resource settings for the database:

○ Memory (default: 200 MB; increase for productive environment)

○ CPUs (default: 1; increase for productive environment)

○ Parallel database sessions - (default:20

; for productive environment, set at least 300)

i) Define the following global database settings:

○ Automatic start on system reboot (Windows only; default: ON)

○ Automatic extension of data areas (default: OFF)

○ Automatic statistics update (default: OFF)

○ Log settings (default: No LOG backup; only recommended for a test environment)

j) Install.

Note

The installation creates the following default database user which can be used for MDM:

○ User name =SAPMDMDB

○ Password =SAP

The created database instance with the default database parameters is tailored for an MDM test

environment and can be extended for productive use. On Windows you must reboot the system after

installation.

Optional: Install the following MaxDB administration tools:

○ Database Manager for administering databases, including remote ones

○ SQL Studio for sending SQL statements to the database

4 Plan and implement a log and backup strategy for a productive environment.

5 For a productive environment, change the default value of the database parameter MaxSQLLocks from 50

000 to at least 650 000.

6 To mount an MDM repository residing in a MaxDB DBMS (using MDM Console), specify the instance name

and the database name of the MaxDB DBMS as the DBMS Server in theAdd DBMS Server

dialog.

More Information:

● Details about MaxDB installation and operations at help.sap.com: Go to SAP NetWeaver 7.0 SAP

NetWeaver by Key Capability Databases MaxDB

.

● Frequently asked questions (FAQ) on MaxDB: SAP Note 820824

7.6 SAP Adaptive Server Enterprise (ASE)

This section describes the specific configuration required to use a SAP ASE database with MDM. For general

information about creating and managing a SAP ASE database, see infocenter.sybase.com/ .




http://help.sap.com/disclaimer?site=http://infocenter.sybase.com/

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/%20820824

http://help.sap.com/





Note

You can set any name for the tempdb log device. Modify the absolute path to match the environment and

desired configuration.

2 In the Master database, add a tempdb device. For example:

disk init name = 'tempdbdev',physname = 'C:\sybase\data\tempdbdev.dat',size='512M'

3 Expand tempdb to put the log on a log device. For example:

alter database tempdbon tempdbdev = '512M'log on tempdblogdev = '512M'

4 Prevent future allocation oftempdb

on the master device. For example:

USE tempdbEXEC sp_dropsegment 'default', 'tempdb', 'master'EXEC sp_dropsegment 'system', 'tempdb', 'master'EXEC sp_dropsegment 'logsegment', 'tempdb', 'master'EXEC sp_dropsegment 'logsegment', 'tempdb', 'tempdbdev'

7.6.2.2 Optimizing Performance

After installation, to optimize performance when working with MDM, we recommend that you configure the SAP

ASE server as shown in the following example:

Example

EXEC sp_deviceattr 'tempdbdev', 'directio', 'false'EXEC sp_deviceattr 'tempdbdev', 'dsync', 'false'EXEC sp_deviceattr 'tempdblogdev', 'directio', 'false'EXEC sp_deviceattr 'tempdblogdev', 'dsync', 'false'

7.6.2.3 Additional Configuration

Ensure that the values for the following system procedures comply with the minimum required values:

System Procedure Minimum Required Value

max memory

1132156

number of open devices

500

number of open locks

250000






System Procedure Minimum Required Value

user conne

500

heap memory per user

8192

size of global fixed heap

1024

statement cache size

0, '200M'

procedure cache size

0, '512M'

allocate max shared memory

1

default data cache

'1024M'

number of open indexes

5000

number of open objects

5000

number of open partitions

5000

number of open databases

50

enable functionality group

1

enable literal autoparam

1

enable plan sharing

0

max online engines

16

kernel resource memory

8192

lock scheme

0, 'datarows'

7.6.2.4 Installing Automatic Database Expansion Procedure

Install automatic expansion using the installdbextend script, which defines defaults for automatic expansion in a

database or device.

Run isql -Uuser -Ppassword -Sserver_name <%SYBASE%/%SYBASE_ASE%/scripts/

installdbextend

7.6.2.5 Configuring the Thread Pool

Configure the thread pool setting to comply with the following minimum requirement: ALTER THREAD POOL

syb_default_pool WITH THREAD COUNT = 2






7.6.3 Installing and Configuring the SAP ASE ODBC Client

Install the SAP ASE ODBC client before installing MDM. Download the required SAP ASE ODBC drivers from

service.sap.com/swdc .

7.6.4 Configuration of MDS.INI Settings

When SAP ASE is selected as a database in the MDM installation, the following settings are available in the

mds.ini file. These settings are used when creating a new repository.

Parameter Default Value

SAP ASE main repository data device size 2048

SAP ASE main repository log device size 512

SAP ASE history repository data device

size

1024

SAP ASE history repository log device size 512

Note

● Consider size requirements for repository size and history size when deciding whether to change these

values.

● When you change the values of these parameters, current repositories are not affected.

7.7 SAP HANA (For MDM-SRM Only)

The SAP HANA database is only supported for MDM-SRM. This section describes the specific configuration

required to use a SAP HANA database with MDM-SRM. For information about installing the SAP HANA ODBC

client, see SAP HANA Client Installation Update Guide.

Install the SAP HANA ODBC client before installing MDM.

After installing MDM, add the following mds.ini settings for SAP HANA:

Parameter Default Value

HANA Repository Type COLUMN (recommended) or ROW




http://help.sap.com/hana/SAP_HANA_Client_Installation_Update_Guide_en.pdf




8 Post-Installation Tasks

To make your installed MDM system a running system, test and set up the MDM servers and the database

connection. You can also set up secure communication (SSL) for the MDM servers.

Note

If you are not planning to use SSL, ensure that the following is set in the mds.ini file: SSL Enabled=False

The SSL key path option should be left empty.

8.1 Starting and Stopping the MDM Servers

SAPinst automatically starts the SAP system and its instances after the installation. Start and stop the MDM

servers to check if the installation was successful.

Caution

After stopping MDS and the database, restart the database first.

To start and stop MDM servers, use the following tools:

●SAP Microsoft Management Console (SAP MMC)

: SAP MMC is the generic SAP system management tool,which is installed automatically with any SAP system on Windows platforms.

● MDM Console

orMDM CLIX

: The MDM Console is the MDM administration Windows client for system,

authorization, repository management and other administration tasks. MDM CLIX is a Windows command

line tool that provides functions of the MDM Console.

In a heterogeneous system landscape, you can also start and stop a UNIX system with the Windows-based SAP

MMC, MDM Console, and MDM CLIX.

Caution

If you cannot start or stop the SAP system using SAP MMC and you get an Unauthorization Error, even though

you made sure that you are using valid credentials, see SAP Note 927637 .

8.1.1 Using SAP Microsoft Management Console

● You have logged on to the SAP system host as user <sapsid>adm.

● You have checked the settings for VM parameters as described in SAP Note 723909 .

Use this procedure to check that you can start and stop the SAP system with the SAP Microsoft Management

Console (SAP MMC) after the installation.


Post-Installation Tasks







With the newly installed SAP MMC, start or stop installed SAP instances locally on the host that you are logged on

to. If the SAP MMC is configured for central system administration, you can start or stop the entire system from a

single host.

1 Start the SAP MMC on the SAP system host by choosing Start All Programs SAP Management

Console

.

2 Right-click the SAP system node and chooseStart

orStop

. All instances listed under the system node start

or stop in the correct order.

3 If the SAP system is installed on multiple hosts (distributed system), use one of the following options to start

or stop your system:

○ Start or stop the SAP instances using the SAP MMC on each host.

○ Add the remote instances to the SAP MMC configuration to start or stop all instances from a single SAP

MMC. For more information, see the SAP MMC system documentation.

8.1.2 Using MDM Console or MDM CLIX

You can start and stop MDM server instances on all supported platforms using the following MDM administration

clients:

● The command line tool MDM CLIX: CLIX is automatically installed with any MDS instance on any platform. It

can be installed separately on Windows platforms.

● The Windows GUI client MDM Console: The MDM Console must be installed separately on Windows 32-bit

platforms (for example on a PC).

More Information

● Accessing an MDM Server section in the MDM Console Reference Guide at help.sap.com/nwmdm71

● MDM Server Commands section in the MDM CLIX Command Reference Guide at help.sap.com/nwmdm71

8.1.3 Using Scripts

Start and stop the SAP system for MDM by running the sapcontrol utility.

8.1.3.1 Starting the SAP System

You have logged on to the SAP system hosts as user <sapsid>adm.

To start all instances on an MDM system host :

Enter the command sapcontrol –nr <instance number> -function StartSystem , where

<instance number> is the number of one of the MDM server instances of the SAP system you want to start.








Note

You can start the MDM server instances separately by entering the command sapcontrol –nr

<instance number> -function Start, where <instance number> is the number of the MDM serverinstance you want to start.

8.1.3.2 Stopping the SAP System

You have logged on to the SAP system hosts as user <sapsid>adm.

To stop all instances on an MDM system host:

Enter the command sapcontrol –nr <instance number> -function StopSystem , where <instance

number> is the number of one of the MDM server instances of the SAP system you want to stop.

Note

You can stop the MDM server instances separately by entering the command sapcontrol –nr

<instance number> -function Stop, where <instance number> is the number of the MDM server

instance you want to stop. Make sure that you always stop the MDS instance first.

8.2 Setting Up SSL Communication for MDM Servers

Starting from version 7.1 SP07, you can set up SSL (Secure Sockets Layer) communication during an installation

or update of MDS, as described in the following sections.

8.2.1 Setting Up SSL During MDS Installation or Update

You are using the MDM 7.1 Installation Master, which can be downloaded from SMP (Service Market Place).

In theInstall all Servers for MDM

tool:

1 In the Setup for the MDM SSL Installation step, select the Setup MDM for Secure Socket Layer

Connection

checkbox.

2 From the MDM Listening Mode dropdown, select either SLL or Both.

Note

In a new installation, the installer automatically sets the MDM listening mode in the MDM servers' ini files.

When you update MDM servers, set this parameter manually in the ini files, as described in SAP Note

1563249 .







3 Specify the following strings:

○ Organization

○ Country

(2 letter string)

The installer uses these strings, the Common Name, which is the fully qualified server name, and the SSL

TCP Port

of the MDM server, to create the server and client keys.

4 ChooseNext

.

5 In the SAP Cryptographic Software step, make sure the Install the SAP Cryptographic Library checkbox is

selected, and specify the path to the SAPCRYPTO library in the Path to SAPCRYPTO.SAR field.

For information about downloading the SAPCRYPTO library, see SAP Note 397175 .

8.2.2 Post-Installation/Update Tasks for SSL

After the installation or update is complete, the following files are created in the exe folder of the global host:

File Description Comments

client.pse Client key of the SSL communica

tion. The MDM clients will need this

file to connect to the MDM servers.

SAPSSLS.pse Server key of the SSL communica

tion. The MDM servers will need this

file.

Copied also to the sec folder of the

MDM servers.

cert.crt Certificate files that are used to con

nect the MDM server to the WAS

(Web Application Server) in secure

mode.

cred_v2 For internal use.

ticket For internal use. Copied also to the sec folder of the

MDM servers

For information about creating the client and server keys manually, see SAP Note 1562668 .

8.2.2.1 Verifying SSL Communication

To verify that SSL is set up correctly:

1 For every server instance (MDS, MDIS MDSS), verify that the framework is set to secure HTTPS mode::

a) Log in to the MDM server using the <SID>adm account.

b) In the command line, type the commandsapcontrol.exe -nr <NR> -function

GetAccessPointList

c) Verify that the HTTPS access point is available in the access point list. If HTTPS is not in the access point

list, try to restart the instance service and check again.









2 In the MDM ini files (mds.ini, mdis.ini, mdss.ini), verify that the following parameters are set:

○ Listening Mode=Both or SSL

This parameter is set by the MDM listening mode parameter in the installation.

○ SSL Lib Path= [Path to the servers’sapcrypto library; must be located in the servers’ exe folder]

○ SSL Key Path= [Path to the servers’ key file SAPSSLS.pse, located in the servers’ sec folder]

3 Enable the MDM Import Server and MDM Syndication Server to work as clients with the MDM servers by

setting the following parameters manually after an MDS installation or update:

○ Service Control Security Enabled=True

Default is True.

○ SSL Enabled=True

Default is False.

○ SSL Key path= [Path to the client key file client.pse, located in the exe folder of the global host]

8.2.3 Setting Up SSL in a Master/Slave Environment

If your MDM environment uses MDM master/slave technology, you must set up the slaves after installation.

To use master/slave with SSL, the following entries in your master and slave mds.ini server files must refer to

the remote server. This is necessary even if the master and slave repositories are on the same MDM server

instance.

Set the parameters as follows:

[MDM Server]\[Remote Server]\[Master Server Name]:[SSL Listening Port]Service Control Security Enabled=TrueSSL Enabled=TrueSSL Lib Path=…\usr\sap\[SID]\MDSxx\exe\sapcrypto.dllSSL Key Path=…\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

Example

[MDM Server]\[Remote Server]\tlvd60200359a:50051Service Control Security Enabled=TrueSSL Enabled=True

SSL Lib Path=C:\usr\sap\Q59\MDS00\exe\sapcrypto.dllSSL Key Path=C:\usr\sap\Q59\MDS00\sec\SAPSSLS.pse

Note

● If you change the listening mode or port on the MDM Server that contains the master after a slave has

been created, the connection between the master and slave is invalidated and you must recreate the

slave.

● When the listening mode is Both, the slave synchronization is via a secure connection only. Therefore,

when using master/slave where the listening mode on the MDM server isBoth

, configure theMDM

Server\Remote Server setting in the mds.ini as described above.






8.2.4 Using CLIX with SSL

To use CLIX with SSL, you must configure the clix.ini file, which is located in the same location as the

clix.exe: \usr\sap\<SAPSID>\<Instance Folder>\exe

n the clix.ini file, add the path to the sapcrypto.dll and set theSSL Lib Path

and theService Control

Security Enabled parameters as follows:

[MDM Server]\[Remote Server]\[Master Server Name]:[SSL Listening Port]Service Control Security Enabled=TrueSSL Enabled=TrueSSL Lib Path=…\usr\sap\[SID]\MDSxx\exe\sapcrypto.dllSSL Key Path=…\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

8.3 Setting up MDM Servers

To set up the MDM servers after installation, use the MDM configuration files and the MDM Console.

You configure the MDM servers and test the system by mounting the MDS and connecting to the database. In

addition, you set MDS and repository passwords for secure MDM operation.

Note

Saphostcontrol (on port 1128) is used for communication between MDM servers and MDM Console.

8.3.1 Configuring MDM Servers

When the MDM server instances (MDS, MDIS, MDSS, MDLS) are installed, the following configuration files are

created in the config directory of the instances:

● mds.ini

● mdm_list.ini

● mdis.ini

● mdss.ini

● mdls.ini

In the configuration (ini) files, you can change a broad range of default server settings as required.

For more information about the individual settings and their effects, see the following points at help.sap.com/

nwmdm71:

● mds.ini and mdm_list.ini: MDM Console Reference Guide, section MDS Configuration

● mdis.ini: MDM Console Reference Guide, section MDIS Configuration

● mdss.ini: MDM Console Reference Guide, section MDSS Configuration









8.3.2 Mounting MDS and Connecting the Database

To check if MDM and the database are installed and configured correctly:

1 Start the MDM Console.

2 Mount the MDS and connect to the database.

For more information, see MDM Console Reference Guide, section MDM Server Administration at


8.3.3 Setting MDS and Repository Authentications

By default, access to new MDS and MDM repositories is not limited. For a secure, productive use of MDM, you

must set passwords using the MDM Console to control access:

● When mounting an MDS for the first time, make sure that you set a password for the new MDS.

● When creating a new repository or unarchiving a repository, make sure that you set passwords for the

predefined users, especially for the Administrator user.

Note

Starting in MDM 7.1 SP08, the default password for theAdministrator

user issapmdm

, and can no longer

be empty.

For more information, see MDM Console Reference Guide, section MDM System Administration at help.sap.com/

nwmdm71









9 Multiple MDM Servers on a Single Host

You can install multiple instances of MDM Servers (including MDS, MDSS, MDIS, and MDLS) on a single host. The

instances of MDM Servers can be from different versions of MDM (such as 5.5 and 7.1), which may be useful when

upgrading from one MDM version to another, or multiple instances of MDM 7.1 SP04 and above.

For more information about a MDM 5.5 and MDM 7.1 side-by-side scenario for upgrade purposes, see the Upgrade

Guide at help.sap.com/nwmdm71

Caution

● When installing multiple instances of MDM 7.1 servers on the same host, each set of MDM servers must

have a unique SAP System ID (SID). Within a single set of servers, each server, MDS, MDIS, MDSS, and

MDLS, can have the same SID.

● Starting from MDM 7.1 SP06, running multiple instances of Master Data Server, at the same time, on the

same host, is supported.

● To start and stop the MDM servers on hosts with multiple MDM 7.1 Server instances, use the SAP Microsoft

Management Console (SAP MMC), SAP Management Console (SAP MC), or scripts.

Starting from MDM 7.1 SP06, you can also use MDM Console or CLIX for these tasks.

● Maintaining multiple instances of MDM 5.5 Master Data Server on the same host is not supported.

9.1 Installing Different Version of MDM Clients

You can install multiple versions of MDM Windows clients (such as MDM Console and MDM Data Manager) on one

host by selecting different target directories in the client installers.

● The installer for MDM Windows clients overwrites any existing desktop and Start menu icons to point to the

last-installed version of the client. To prevent this overwriting and avoid any potential user confusion, we

recommend labeling existing icons with their MDM version number.

● MDM clients connecting to a Master Data Server must be from the same version as the Master Data Server.

● MDM clients connecting to a Master Data Server on a host where multiple instances of Master Data Servers

are maintained must provide the port number of the Master Data Server they want to connect to.

9.2 Running Multiple MDM Server Components on a SingleMachine

Starting from MDM 7.1 SP06, you can install and run multiple MDM server components on one physical machine.

The advantages of installing multiple MDM server components on a single machine instead of loading multiple

MDM repositories on a single Master Data Server (MDS) are:



Multiple MDM Servers on a Single Host




● You can perform parallel execution of imports to, and syndications from loaded MDM repositories.

● Two repositories for separate projects on two different MDM versions can reside on the same machine, which

results in reduced TCO.

Each Master Data Import Server (MDIS) and Master Data Syndicator Server (MDSS) must be configured to work

with only one particular MDS. You can distribute the MDM server components according to the following

hardware configuration options:

● Multiple Master Data Servers on one machine with remote MDM Import/Syndication Servers on a second

machine, and a DBMS on a third machine.

● Multiple Master Data Servers and MDM Import/Syndication Servers on one machine with a remote DBMS on

a separate machine.

● Multiple Master Data Servers, MDM Import/Syndication Servers, and a DBMS all on one machine.

Test results show that hardware sizing parameters are almost identical for all the aforementioned configuration

options; therefore the configuring option you choose should be based solely on your preferred hardware setup.

9.3 Unarchiving and Updating MDM Repositories

All MDM repositories used with a Master Data Server must be from the same version as that Master Data Server.

To avoid data problems due to schema differences among MDM versions, repositories should only be unarchived

and updated from earlier to later versions—never the opposite.


Multiple MDM Servers on a Single Host




10 Updating MDM Servers

● This description assumes that you installed your SAP system with standard SAP tools according to the

installation documentation.

● You are logged on as an administration user.

● You know how to start the installation with SAPinst.

This section describes how to update MDM servers with the Update option of SAPinst, for example to implement

support packages or patches.

The Update option allows you to update the complete SAP system from one host, even if the system was installed

on several hosts (distributed system). For performance reasons, run the update on the host where you installed

the first MDM instance.

Note

When updating single instances, be aware that updates can only be installed based on MDM server types and

host types. For example, if you choose to update one MDS instance running on a Windows x86_64 host, all

other MDS instances of this SAP system running on other Windows x86_64 hosts are updated as well.

1 Start SAPinst and on the Welcome screen, choose Additional Software Lifecycle Options Update

MDM .

2 Follow the instructions in the SAPinst input dialogs.

Related Information

Starting the Installation [page 32]



Updating MDM Servers



11 Uninstalling MDM Servers

● It is assumed that you have installed your SAP system with standard SAP tools according to the installation

documentation.

● You are logged on with a user account that has the required authorization to run the SAPinst tool and the SAP

system.

● You know how to start SAPinst. For more information, see Starting the Installation [page 32]

You can uninstall MDM servers by deleting a single instance or a complete SAP system with the Uninstall option

of SAPinst.

Caution

Make sure that you stop, archive, and store the MDM repositories that you want to reuse. In the SAPinst un-

installation procedure, keep theArchive

folder and other folders (see below). You cannot delete an SAP systemremotely. If you delete network-wide users, groups or service entries in an environment with Network

Information System (NIS), other SAP installations might also be affected. Make sure that the users, groups,

and service entries to be deleted are no longer required.

1 Start SAPinst and on the Welcome screen, choose Additional Software Lifecycle Options Uninstall

MDM .

2 Follow the instructions in the SAPinst input dialogs.

SAPinst first asks you which SAP instances to delete. Note the difference between central and distributed

systems:

○ You can delete a central system (all instances reside on the same host) in one SAPinst run.

○ To delete a distributed system, run SAPinst to delete the required instances locally on each of the hosts

belonging to the SAP system.

Note

SAPinst only stops local instances automatically.

SAPinst asks you if you want to keep the MDM-specific folders and files located under/usr/sap/<SAPSID>

for reuse. You can keep the following:

○ Configuration files (.ini)

○ Log files

○ Archives (MDS only)

○ Distribution files (MDS only)

○ Reports (MDS only)


Uninstalling MDM Servers




12 Uninstalling MDM Windows Clients

You can uninstall MDM Windows clients in the following ways:

● Remove the MDM core components one by one using the corresponding Windows function, Settings

Control Panel Add or Remove Programs

● Use the installation executables to remove single MDM Windows clients or sets of MDM Windows clients:

○ To remove a single client, open a Windows Command Prompt and launch the installation executable

passing the parameter /su ( for example enter MDMServerInstall.exe /su).

○ To remove a collection of clients, create a batch file.

After uninstalling, delete the MDM Windows client folders ( Program Files SAP MDM 7.1 ) from your hard

disk.



Uninstalling MDM Windows Clients



13 SAP System Security

In a central SAP system installation, SAPinst automatically performs all steps relevant for security. Although

SAPinst makes sure that the system is protected against unauthorized access, you must still check that no

security breaches can occur.

For central and straightforward administration of the SAP system, you must install distributed SAP systems with

multiple application servers in a Windows domain. This section describes the user accounts and groups that

SAPinst creates during a domain installation and shows how these are related to the SAP directories.

13.1 User Accounts

SAPinst creates the following accounts for SAP system administration:

● <sapsid>adm

This is the SAP system administrator account that enables interactive administration of the system. Under

Windows, this account is a member of the local Administrators group.

● SAPService<SAPSID>

This is the user account that is required to start the SAP system. It has the local user right to log on as a

service.

The advantage of the additionalSAPService<SAPSID>

account is that it does not allow an interactive logon,

which prevents abuse of the account. Therefore, you do not need to set an expiration date for the password

and you do not need to set the optionuser must change password at next logon

.

13.2 Groups

SAPinst creates the following groups during a domain installation:

● SAP_<SAPSID>_GlobalAdmin

This global group is a domain-level SAP administration group for organizing SAP system administrators. The

only function of a global group is to group users at the domain level so that they can be placed in the

appropriate local groups.

● SAP_<SAPSID>_LocalAdmin

Only local groups are created and maintained on an MDM server. A local group can only be given permissions

and rights to the system where it is located. The system is part of a particular domain, and the local group can

contain users and global groups from this domain.


SAP System Security




13.3 Security of SAP Directories

SAPinst protects the SAP directories under\usr\sap\<SAPSID> by only granting the group

SAP_<SAPSID>_LocalAdmin

full control over these directories.

Note

An access control list (ACL) controls access to SAP system objects. For maximum security in the SAP system,

only the following are members of all SAP system object ACLs:

Local group SAP_<SAPSID>_LocalAdmin

Group Administrators

Account SYSTEM



SAP System Security




SAP System Security




www.sap.com/contactsap

© 2014 SAP AG or an SAP affiliate co mpany. All rights reserved.

f

http://www.sap.com/contactsap

Documents

MDM InstGuide