mdm instalacion

7/16/2019 MDM Instalacion

http://slidepdf.com/reader/full/mdm-instalacion 1/66

Typographic Conventions

Type Style Represents

Example Text Words or characters that appearon the screen. These includefield names, screen titles,pushbuttons as well as menunames, paths and options.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, titles of graphics andtables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, table names,and individual key words of aprogramming language, whensurrounded by body text, forexample, SELECT andINCLUDE.

Example text Screen output. This includes fileand directory names and theirpaths, messages, names of variables and parameters,source code as well as names of installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in the

documentation.<Example text> Variable user entry. Pointed

brackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (such asF2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



MDM 7.1 Installation Guide (Windows)

March 2013 3

Document History

DocumentVersion

Descript ion of Change

5.2 /

March2013

· Guide updated for MDM 7.1 SP10.

· Updated links to MDM 7.1 Documentation Center to htt p: / / hel p. sap. com/ nwmdm71.

5.1 /August2012


· Added description of usage for installation and upgrade guides. See1.3 Using theInstallation and Upgrade Guides on page 9.

· Added information about installing Microsoft Security Updates. See 3.2 Visual C++ SecurityUpdates on page 14.

· Updated supported MaxDB client versions in the section, 4.4.5 MaxDB on page 51.

· Added section, 6.3.2 Running Multiple MDM Server Components on a Single Machine.

5.0 / Oct2011


·

The default password for the Administrator

user is now sapmdm, and can no longer beempty. See 5.2 Setting up MDM Servers on page 56.

4.9 / May2011


· SSL Support:

o For information about SSL TCP/IP ports, see Software Requirements on page 13.

o For information about setting up SSL, see 5.3 Setting Up SSL Communication for MDMServers on page 57.

4.6 / Jan2011


· Starting from MDM 7.1 SP06, running multiple instances on a single machine is supported.See 6.3 Maintaining Multiple MDM Servers on a Host on page 60.

· Addition regarding IBM i 6.1 OS. See 6.3 Maintaining Multiple MDM Servers on a Host onpage 60.

· Updated path for downloading files from SAP Software Download Center on SMP.

o Updated following documentation: 3.5 Preparing the Installation Files on page 23.

· Update regarding installating the Oracle Database. See Install Oracle and Create aDatabase Instance on page 41.

· Terminology updates relating to MDM server naming - MDM Server was changed to MasterData Server, MDM Import Server was changed to Master Data Import Server.

4.3 · Two additional MDM Components were added: MDM Web Dynpro and MDM CollaborativeProcesses for Material. See section1.1 MDM Component Overview on page 7.

· Links to installation process for the MDM Web Dynpro and the MDM Collaborative

Processes for Material has been provided. See 4.3 Installing Additional MDM Componentson page 38.

· Section 6.3 Maintaining Multiple MDM Servers on a Host on page 60 was rewritten toclarify the installation of multiple Master Data Server instances on the same host.

4.2 · In 4.1.2 SAPinst Installation Options section on page 29, under Configure SLD Generation,a reference to the MDM 7.1 How To Register MDM in SLD guide was added.

· In the Software Requirements section on page 13, information about updated NW RFCSDK Libraries as of MDM 7.1 SP05 was added. This requires the installation of MicrosoftVisual C++2005 Service Pack 1 Redistributable Package ATL Security.

· In the 1.1 MDM Component Overview section on page 6, a note about installing the COMAPI of the same build as the Master Data Server (MDS) for using the MDM UOM Managerwas added.

4.1 · Document History section added




4 March 2013

· Step 7 in 4.4.5 MaxDB on page 51: When mounting an MDM repository residing in aMaxDB DBMS (using MDM Console), you specify the instance name (and databasename), not the hostname (and database name) of the MaxDB DBMS.




March 2013 5

Table of Contents

1. Int roduction ................................................................................................ 71.1 MDM Component Overview .................................................................................... 7

1.2 Required Documentation ........................................................................................ 81.2.1 Information on SAP Help Portal................................................................................. 81.2.2 SAP Installation Notes .............................................................................................. 81.2.3 Information on SAP Service Marketplace .................................................................. 9

1.3 Using the Installation and Upgrade Guides .......................................................... 9

2. Planning .................................................................................................... 102.1 Implementation Considerations ........................................................................... 10

2.1.1 MDM System Landscapes ...................................................................................... 102.1.2 Windows Domain or Local Installation ..................................................................... 10

2.2 High Availabil it y ..................................................................................................... 112.3 Multiple Components on One Database .............................................................. 11

2.4 Lightweight Directory Access Protocol ............................................................... 11

3. Preparation ............................................................................................... 123.1 Hardware and Software Requi rements ................................................................ 12

3.1.1 Process Flow .......................................................................................................... 123.1.2 Requirements for Windows ..................................................................................... 13

3.2 Visual C++ Securi ty Updates ................................................................................ 14

3.3 Basic SAP System Parameters............................................................................. 15

3.4 Preparation Steps .................................................................................................. 173.4.1 Checking the File System........................................................................................ 173.4.2 Checking the Domain Structure............................................................................... 183.4.3 Checking Required User Authorizations .................................................................. 183.4.4 Performing a Domain Installation Without Being a Domain Administrator ................ 19

3.5 SAP Directories...................................................................................................... 213.5.1 SAP System Directories .......................................................................................... 213.5.2 MDM Windows Client Directories ............................................................................ 23

3.6 Preparing the Installat ion Fi les............................................................................. 233.6.1 Downloading Installation Files from SMP ................................................................ 243.6.2 Obtaining Installation Files from DVD ...................................................................... 24

4. Instal lation ................................................................................................ 264.1 Install ing MDM Servers ......................................................................................... 26

4.1.1 Running SAPinst ..................................................................................................... 264.1.2 SAPinst Installation Options .................................................................................... 294.1.3 Interrupted Installation with SAPinst ........................................................................ 304.1.4 Performing a Remote Installation with SAPinst (Optional) ....................................... 314.1.5 Starting SAPinst GUI Separately (Optional) ............................................................ 314.1.6 Silent Installation with SAPinst (Optional) ................................................................ 334.1.7 Entries in the Services File Created by SAPinst ...................................................... 33

4.1.8 Avoiding Automatic Logoff by SAPinst .................................................................... 334.1.9 Troubleshooting with SAPinst.................................................................................. 34




6 March 2013

4.2 Installing MDM Windows Clients .......................................................................... 344.2.1 Installation Modes ................................................................................................... 354.2.2 MDM Windows Clients in Detail .............................................................................. 36

4.3 Instal ling Addit ional MDM Components .............................................................. 38

4.4 Instal ling and Configuring the Database ............................................................. 40

4.4.1 Microsoft SQL Server .............................................................................................. 404.4.2 Oracle DBMS .......................................................................................................... 414.4.3 IBM DB2 for Linux, UNIX and Windows .................................................................. 474.4.4 IBM DB2 for z/OS.................................................................................................... 484.4.5 MaxDB .................................................................................................................... 51

5. Post-Installation ....................................................................................... 545.1 Start ing and Stopping the MDM Servers ............................................................. 54

5.1.1 Using SAP Microsoft Management Console ............................................................ 545.1.2 Using MDM Console or MDM CLIX ......................................................................... 55

5.1.3 Using Scripts ........................................................................................................... 555.2 Setting up MDM Servers ....................................................................................... 56

5.2.1 Configuring MDM Servers ....................................................................................... 565.2.2 Mounting MDS and Connecting the Database ......................................................... 565.2.3 Setting MDS and Repository Authentications .......................................................... 56

5.3 Setting Up SSL Communication for MDM Servers ............................................. 575.3.1 Setting Up SSL During an Installation or an Update of MDS ................................... 575.3.2 Post Installation/Update Tasks ................................................................................ 57

6. Additi onal Information ............................................................................. 59

6.1 SAP System Secur ity ............................................................................................ 596.1.1 User Accounts......................................................................................................... 596.1.2 Groups .................................................................................................................... 596.1.3 SAP Directories ....................................................................................................... 59

6.2 Updating MDM Servers ......................................................................................... 60

6.3 Maintaining Multiple MDM Servers on a Host ..................................................... 606.3.1 Installing Different Versions of MDM Clients............................................................ 616.3.2 Running Multiple MDM Server Components on a Single Machine ........................... 616.3.3 Unarchiving and Updating MDM Repositories ......................................................... 61

6.4 Uninstalling MDM Servers .................................................................................... 61

6.5 Uninstall ing MDM Windows Clients ..................................................................... 62




March 2013 7

MDM 7.1 Installation Guide for Windows

1. Introduction This installation guide describes how to install the SAP NetWeaver Master Data Management (MDM) 7.1components on supported Windows platforms.

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

The installation procedure for MDM 7.1 differs significantly from the installation procedure forMDM 5.5. The MDM servers are installed as SAP systems using the SAPinst installation tooland SAP Instance Framework.

The installation procedure for the MDM Windows clients and additional components has notchanged. The procedure is described in this Windows installation guide.

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 onsupported Windows 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 componentscan be installed on Windows using a simple MDM-specific installation routine:

· MDM Console

· MDM CLIX

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.· MDM Data Manager (including MDM Workflow)

· MDM Import Manager

· MDM Syndicator

· MDM Language Selector

· MDM UOM Manager (requires the COM API of the same build as the Master Data Server)

From MDM 7.1 SP09, we recommend that you manage Units of Measurement from the MDMConsole.

· MDM Image Manager

· MDM Publisher

· MDM Indexer




8 March 2013

· InDesign®Plug-In

Addi tional MDM Components

The following additional MDM components enable you to connect MDM to other applications. Thesecomponents can be deployed on their respective platforms:

· MDM J ava API and MDM Connector· MDM Portal Content

· MDM PI Adapter

· MDM ABAP API

· MDM Web Services

· MDM .NET API

· MDM COM API

· MDM Enrichment Controller

· MDM TREX Client

· MDM Web Dynpro

· MDM Collaborative Processes for Material

1.2 Required Documentation The following sections list the documentation needed for the installation.

· Information on the SAP Help Portal

· SAP Installation Notes

· Information on the SAP Service Marketplace

1.2.1 Information on SAP Help Portal The SAP NetWeaver MDM 7.1 Documentation Center on the SAP Help Portal athelp.sap.com/nwmdm71provides useful information and access to the complete MDM documentation set, including all the MDMinstallation and planning guides.

1.2.2 SAP Installation NotesIt is essential that you read the following SAP Notes before starting the installation. These SAP Notescontain the most recent information about the installation as well as corrections to the installationdocumentation.

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

Marketplace atservice.sap.com/notes.

SAP NoteNumber

Title Description

1249503 MDM Installation Note Most recent information and best practices about theMDM installation procedure.

The MDM Installation Note complements this MDMInstallation Guide.

1754181 SAP NetWeaver MDM 7.1SP10 Release

This note contains information about the current MDM7.1 support package.

1244358 MDM 7.1 ReleaseRestriction Note

This note contains the restrictions of the current MDM7.1 support package.

https://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1249503

https://service.sap.com/sap/support/notes/1754181








March 2013 9

1.2.3 Information on SAP Service MarketplaceInformation on the following areas is available on SAP Service Marketplace:

Description Internet Address

Released platforms service.sap.com/platforms

Technical infrastructure – configuration scenarios andrelated aspects, such as security, load balancing,availability, and caching

service.sap.com/ti

Network infrastructure service.sap.com/network

1.3 Using the Installation and Upgrade Guides

When planning a new MDM installation, follow the instructions in the MDM Installation Guides.

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 before you begin the upgrade process.

The Upgrade Guide provides the following information:

· Preparatory and pre-installation tasks

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




10 March 2013

2. PlanningWhen planning the MDM system landscape, familiarize yourself with the following documentation athelp.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 atservice.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 guide first (available athelp.sap.com/nwmdm71).

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

· SAPinst Installation Options

· Updating MDM Servers

2.1 Implementation Considerations

2.1.1 MDM System LandscapesAn MDM system landscape is typically structured as follows:

· One separate UNIX host or Windows server host with the MDM servers and the database (standardsystem).

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 andscenarios. This document lists the components and third-party applications that are required for eachscenario in an SAP NetWeaver solution, and refers to the required installation and upgrade guides. It alsodefines 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 athelp.sap.com/nwmdm71 .

2.1.2 Windows Domain or Local InstallationBefore 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.

Domain Installation

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

You must perform a domain installation if you install a distributed system with MDM servers and thedatabase 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 anyother hosts in the system.

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




March 2013 11

2.2 High AvailabilityHigh availability (HA) is a major consideration when planning business systems that require systemreliability. For MDM, there are different approaches that support this objective, for example, systemredundancy 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, read the following documentation:help.sap.com/nwmdm71 ® Solution Operation Guide ® High Availability

2.3 Multiple Components on One DatabaseMDS 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 mustbe taken into consideration when sizing the hardware and system.

For more information, see service.sap.com/mcod .

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

For more information, see the section Adjust Temporary Tablespace for MCOD in this guide.

2.4 Lightweight Directory Access ProtocolMDM supports the Lightweight Directory Access Protocol (LDAP) for user authorization management.

If you plan to use LDAP with MDM, read the following documentation:help.sap.com/nwmdm71 ® MDM Security Guide, section LDAP Support.




12 March 2013

3. Preparation To prepare for an MDM installation, learn about SAP systems and make some checks and settings on yourWindows platform.

The chapter is structured as follows:

· Hardware and Software RequirementsLists the requirements for running SAPinst and MDM servers and describes how to check theserequirements.

· Basic SAP System Parameters

Provides an overview of the basic parameters that make up an SAP system, like system IDs, users,and so on.

· Preparation StepsLists the Windows-specific steps to prepare a local or domain installation.

· SAP Directories

Lists the directories that SAPinst and the MDM Windows client installation executables create forMDM servers and clients.

· Preparing the Installation Files

Describes how to retrieve the installation files from the DVD or SAP Service Marketplace and howto create installation packages for the various installation options.

3.1 Hardware and Software RequirementsCheck that your hosts meet the hardware and software requirements for your operating system (OS), theMDM server instances, and the MDM clients.

If your hosts do not fully meet these requirements, you might experience problems when workingwith 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.

To monitor MDM using the SAP Solution Manager, the MDM host name must also meet therequirements listed in SAP Note 1278029.

3.1.1 Process Flow1. Check the Product Availability Matrix (PAM) on SAP Service Marketplace at

service.sap.com/pam ® SAP NETWEAVER ® SAP MDM for supported operating systemreleases.

2. Check the Requirements for Windows section below.

3. If you are installing a production system, the values provided by the Prerequisite Checker and theRequirements for Windows section in this guide are not sufficient. In addition, do the following:

a. Read the MDM Sizing Guide available athelp.sap.com/nwmdm71 ®MDM 7.1 - Sizing

Guide.

b. Contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing depending on parameters such as:- How intensively the applications are to be used

- Number of users- Data Model of your MDM repositories








March 2013 13

- 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

This section lists the minimum hardware and software requirements for installing and running MDM serverson released Windows platforms.

Your system must meet the minimum requirements listed in the following tables.

Hardware Requirements

Requirement Type Requirement How to Check

Minimum disk space SAP system files (not includingpaging file): 2 GB

Temporary disk space for theinstallation: 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. Choose Start ® Control Panel ® System.

2. Choose Advanced.

3. Select Performance Settings Advanced.

4. In section Virtual memory, choose Change.

Software Requirements


Windows operatingsystem for MDMservers

English international 64-bitversion of one of the releasedWindows Server Editions.

For any version of WindowsServer, you need the latestsupported service pack.

To check your Windows version:

1. Choose Start ® All Programs ®

Accessories® Command Prompt.

2. Enter the command wi nver .

TCP/IP access MDIS, MDSS, and MDLS must

have TCP/IP access to the MDS. This connection must be on alocal network to be effective.

Starting from MDM 7.1 SP07,each MDM instance can useeither regular TCP/IP ports, orSSL TCP/IP ports for securecommunication (if this wasconfigured).

For more information on the TCP/IP ports, see SAP Note1487853.

Check the setup of your network, operating

system, and firewalls, to verify that the MDMservers can be accessed through theirdedicated TCP/IP ports.

You set the ports during the installation.

The regular TCP/IP ports are:

· MDSPort59950 and three sequential portsin the range 2000 - 9999 for everyloaded repository. Configure therepository ports using the MDMConsole.

· MDIS

Port59750· MDSS






14 March 2013


Port59850

· MDLSPort59650

The SSL TCP/IP ports, starting from MDM 7.1

SP07, are:

· MDSPort59951 and three sequential portsin the range 2000 - 9999 for everyloaded repository. Configure therepository ports using the MDMConsole.

· MDISPort59751

· MDSSPort59851

· MDLS:Por t 59651

If an MDM Server is already installed on yourmachine and you install an additional instanceof MDS, MDIS, MDSS, and/or MDLS, thedefault TCP/IP ports will be created in thefollowing format, where xx is the instancenumber:

· 5xx50 for the regular TCP/IP ports

· 5xx51 for the SSL TCP/IP ports

3.2 Visual C++ Security Updates The following Microsoft Visual C++security updates must be installed on your Windows server and clientmachines.

· Microsoft Visual C++2005 Service Pack 1 Redistributable Package ATL Security Update

· Microsoft Visual C++2008 SP1 Redistributable Package

Without these updates, Master Data Server fails to start, and displays a failure message.

To check if you need the security update:

1. In the Windows Control Panel, select Add or Remove Programs.

2. Check the version of Microsoft Visual C++2005 SP1 Redistributable Package.

If the version is 8.0.50727.4053, or greater, you already have the update.For more information, see the Microsoft Knowledge Base Article KB973544 and the SAP Note1375494.

To install Microsoft Visual C++2005 Service Pack 1 Redistributable Package ATL Security Update:

1. Navigate to: http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en

2. In theFiles in This Download section, select the file to download according to the type of yourmachine: x86 for Win32 or x64 for Win64.

To install Microsoft Visual C++2008 SP1 Redistributable Package:

· To install on a Win32 server, download the package from:http://www.microsoft.com/downloads/details.aspx?familyid=a5c84275-3b97-4ab7-a40d-3802b2af5fc2&displaylang=en.


http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en


http://www.microsoft.com/downloads/details.aspx?familyid=a5c84275-3b97-4ab7-a40d-3802b2af5fc2&displaylang=en








March 2013 15

· To install on a Win64 server, download the package from:http://www.microsoft.com/downloads/details.aspx?familyid=ba9257ca-337f-4b40-8c14-157cfdffee4e&displaylang=en.

3.3 Basic SAP System ParametersSAPinst asks whether to run the installation in Typical orCustom mode. If you choose Typical, SAPinstprovides automatic default settings and you only respond to a minimum number of prompts. However, youcan still change any of the default settings on the parameter summary screen.

The following tables list the basic system parameters that you must specify before installing your SAPsystem in typical and in custom mode.

For all other SAP system parameters, use the F1 help in the SAPinst dialogs.

Parameter Description

SAP System ID<SAPSI D>

The SAP system ID <SAPSI D>identifies the entire SAP system. SAPinst

prompts you for the <SAPSI D>if you run the first installation option to install anew SAP system.

If there are further installation options to be executed, SAPinst prompts you forthe profile directory. For more information, see the description of the parameterSAP System Profile Directory.

Choose your SAP system ID carefully. Choosing a new ID isdifficult 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 reserved IDs:ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GI DI BM I NT KEY LOG LPT MON NI X NOT NUL OFF OMS PRN RAWROW SAP SET SGA SHG SI D SQL SYS TMP UI D USR VAR

SAP System ProfileDirectory

\ \ <SAPGLOBALHOST>\sapmnt \ <SAPSI D>\

SYS\ prof i l e

The installation retrieves the parameters entered earlier from the SAP systempr of i l e directory.

SAPinst prompts you to enter the location of the pr of i l e directory if theinstallation option that you run is not the first one belonging to your SAP

system installation.

For more details, read the description of the parameter <SAPSI D>.

Instance Number of theSAP System

Technical identifier that is required for every instance of an SAP system,consisting of a two-digit number from00 to 97.

The instance number must be unique on the host. If more than one SAPinstance is running on the same host, these instances must be assigneddifferent numbers.

The instance number specifies the names of the SAP system instancedirectories that SAP automatically creates during the installation. For example,the directory of the MDS is called MDS.

Do not use 89 for the instance number because it is used by

http://www.microsoft.com/downloads/details.aspx?familyid=ba9257ca-337f-4b40-8c14-157cfdffee4e&displaylang=en

16 March 2013


Windows Terminal Server.

Virtual Host Name Use one or more virtual TCP/IP host names for SAP servers in an SAP serverlandscape to conceal their physical network identities from each other.

This may be useful for moving SAP servers or complete server landscapes to

other new hardware within a short time frame, without reinstalling or performinga complicated reconfiguration.

To use virtual host names for the installation, specify the virtual host namebefore you start SAPinst.

For more information about the use of virtual TCP/IP host names, see SAPNote 962955.

The host name must not exceed 12 characters. For more information about theallowed host name length and characters, see SAP Note 611361.

Destination Drive Base directory for the SAP system.

If you install an additional SAP system, you cannot select theinstallation drive because the sapmnt share already exists.SAPinst uses the installation drive that the sapmnt share pointsto.

Master Password Common password for all users that are created during the installation:

Operating system users (for example <sapsi d>adm, SAPServi ce<SAPSI D>)

If you did not create the operating system users manually beforethe installation, SAPinst creates them with the default masterpassword. In this case, make sure that the master password meets

the requirements of your operating system.

If a user already exists, you are prompted to confirm the password for thisuser.

User <sapsi d>adm User <sapsi d>admis the system administrator user and is a member of thelocal Admi ni st r at or s group.

If you do not create the user <sapsi d>admmanually before the installation,SAPinst creates it automatically during the installation. SAPinst sets the MasterPassword by default, but you can overwrite it by choosing the parameter modeCustom or by changing it on the parameter summary screen.

Make sure that the user ID and group ID of this operating system user are

unique and the same on each MDM server instance host.User sapadm User sapadmis used for central monitoring services.

The same notes apply as in user <sapsi d>adm.

User SAPSer vi ce<SAPSI D>

This user is the Windows account to run the SAP system. It is not a member of the local Admi ni st r at or s group and direct login to this user is not possible.

Password of OperatingSystem Users

SAPinst processes the passwords of operating system users as follows:

If the operating system users do not exist, SAP creates the users listed in thistable.

If the operating system users already exist, SAPinst prompts you for theexisting password, unless the password of these users is the same as the

master password.




March 2013 17


Make sure that you have the required user authorization for theseaccounts before you start the installation.

Password of sapadm The administration user sapadmis created to use central monitoring services.

If this user does not already exist, SAPinst automatically creates it. SAPinstprompts you to enter either the password of the existing user or a newpassword for the user to be created.

Port Number of theMDM server

The TCP/IP port number of the respective MDM server (MDS, MDIS, MDSS,MDLS) makes the server accessible through the network.

As of SAP NetWeaver MDM 7.1 SP04, this parameter is configurable duringthe MDM installation.

We recommend that you use ports higher than 49151.

The ports between 0 and 1023 might be used by the operatingsystem and the application may not function correctly.

The ports between 1024 and 49151 might be registered for andused by other applications. Check the Internet Assigned NumbersAuthority (IANA) registrations with your network administrator.

3.4 Preparation Steps This chapter explains the following Windows-specific preparation steps that you must perform before starting

SAPinst:· Checking the File System

· Checking the Domain Structure (Windows domain installation only)

· Reducing the Size of the File Cache

· Checking Required User Authorizations

· Performing a Domain Installation Without Being a Domain Administrator (Windows domaininstallation only)

3.4.1 Checking the File System

Check that you are using the Windows file system NTFS on the hosts where you want to install the SAPsystem. NTFS supports full Windows security and long file names.

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

1. Open the Windows Explorer.

2. Select the relevant disk.

3. Choose Properties ® General. The system displays the type of file system in use.

4. Check that the file system is NTFS.

18 March 2013

3.4.2 Checking the Domain Structure

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 domainIn this model, the SAP system is embedded in its own domain, which is specially defined for SAP. Asecond 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 theroot domain.

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

Prerequisites

· You are performing a domain installation.· You are familiar with checking Windows domain structures. For more information, see the Windows

OS documentation.

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 istherefore not supported.

Procedure

For a domain installation, we recommend that you check that all SAP system and database hosts aremembers of a single Windows domain. We recommend this for all SAP system setups.

3.4.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 installationaborts.

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

Do not use the user <sapsi d>admfor the installation of the SAP system.

Domain InstallationFor a domain installation, the account used to run the installation must be a member of the localAdmi ni st r at or s and the domain Admi ns group must be a member of the relevant domain. All hosts in thesystem must belong to the same domain. In a domain installation, the SAP system user information is storedcentrally 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 youperform a domain installation to avoid authorization problems.

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

for the operating system users <sapsi d>admand SAPServi ce<SAPSI D>. Therefore, we donot support a local installation for a distributed system. We recommend that you install adistributed system as a domain installation.

March 2013 19

If you must perform a local installation for a distributed system, make sure that:- You use the same password for the <sapsi d>admor the SAPServi ce<SAPSI D>user on allhosts. The password for the <sapsi d>admand SAPSer vi ce<SAPSI D>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 Admi nsgroup, you can perform the installation with a domain user who is a member of the localAdmi ni st r at or s group. However, the domain administrator has to prepare the system for you.For more information, see section Performing a Domain Installation without being a Domain Administrator below.

For a domain installation:

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

2. If required, obtain these rights by asking the system administrator to enter the account as a memberof the domain Admi ns group.

Local InstallationFor a local installation, the account used for the installation must be a member of the localAdmi ni st r at or s group of the machine involved. In a local installation, all Windows account information isstored locally on one host and is not visible to any other hosts in the system.

For a local installation:

1. Check that the account used for the installation is a member of the local Admi ni st r at or s group.

2. If required, obtain these rights by asking the system administrator to enter the account as a memberof the local Admi ni st r at or s group.

3.4.4 Performing a Domain Installation Without Being aDomain Administrator

You normally perform a domain installation of the SAP system with a user who is a member of the domainAdmi ns group, as described in section Checking Required User Authorizations above. If for any reason, theaccount used for the installation is not a member of the domain Admi ns group, you can perform theinstallation with a domain user who is a member of the local Admi ni st r at or s group.

In this case, the domain administrator has to prepare the system appropriately for you. The domainadministrator can perform the following steps manually or by using SAPinst:

1. Create the new global group SAP_<SAPSI D>_Gl obal Admi n.

2. Create the two new SAP system users <sapsi d>admand SAPSer vi ce<SAPSI D>.3. Add the users <sapsi d>admand SAPSer vi ce<SAPSI D>to the newly created group

SAP_<SAPSI D>_Gl obal Admi n.

Prerequisites

You must be domain administrator to perform the required steps.

Creating the Required Users and Groups Using SAPinstOn 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.

20 March 2013

Creating the Required Users and Groups ManuallyCreating the New Global Group SAP_<SAPSID>_GlobalAdmin

1. Log on as domain administrator.

2. To start the Active Directory Users and Computers Console, choose Start ® Control Panel

Administrative Tools ® Active Directory Users and Computers.

3. Right-click Users inTree, and choose New Group.

4. Enter the following:Group name: SAP_<SAPSI D>_Gl obal Admi n

Enter the SAP_<SAPSI D>_Gl obal Admi n group exactly as specified in the correct uppercaseand lowercase.

5. Select the following:Group scope: GlobalGroup type: Security

6. Choose OK.

Creating the New SAP System Users <sapsid>adm and SAPService<SAPSID>

1. In Active Directory Users and Computers Console, right-click Users inTree and choose New User .

2. Enter the following:

Field Input for <sapsid>adm Input for SAPService<SAPSID>

First name: None None

Initials: None None

Last name: None None

Full name: <sapsi d>adm SAPSer vi ce<SAPSI D>

User logon name: <sapsi d>adm SAPSer vi ce<SAPSI D>

Enter the <sapsi d>admand SAPSer vi ce<SAPSI D>user exactly as specified in the correctuppercase and lowercase.

3. Choose Next and enter the following:Password: <passwor d>Confirm password: <passwor d>

4. Select Password never expires.

Make sure that no other options are selected.

5. Choose Next ® Finish.

Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group

1. In the Users folder, double-click the newly created user account <sapsi d>admin the list on theright.

2. Choose Member Add.

3. Select the newSAP_<SAPSI D>_Gl obal Admi n group and choose Add to add it to the list.

March 2013 21

By default, the user is also a member of the Domai n User s group.

4. Choose OK twice.

Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group

1. In theUsers folder, double-click the newly created user account SAPServi ce<SAPSI D>in the liston the right.

2. Choose Member Add.

3. Select the newSAP_<SAPSI D>_Gl obal Admi n gr oup.

4. Choose Add to add it to the list, and then OK.

5. Choose OK to close SAPSer vi ce<SAPSI D>Properties.

6. Close the Active Directory Users and Computers Management Console.

3.5 SAP Directories This section describes the directories that the system creates during the installation of MDM servers andMDM Windows clients.

3.5.1 SAP System Directories This section describes the SAP system-specific and MDM servers-specific directories that SAPinst createsduring 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\ <SAPSI D>\ SYS. There is exactly one physicaldirectory for each SAP system. It consists of the following subdirectories:- gl obal – contains globally shared data- pr of i l e – contains the profiles for all instances- exe – contains the executable replication directory for all instances

· Local host and shared with the name sapl oc.On local hosts, the \ usr \ sap\ <SAPSI D>\ directory contains copies of theSAP software and local (instance-specific) data.

Under \ usr \ sap\ <SAPSI D>\ \ conf i g, for example, you find the MDM-specific configuration files for MDM servers:- mds. i ni- mdi s. i ni- mdss. i niIn the MDS instance folder under mdm, you find the following MDS-specific sub-folders:- accel er at or s- ar chi ves- di str i but i ons- reports

As SAP traces for the instance are created in \ usr\ sap, make sure there is sufficient spaceavailable in this directory. Changes to SAP profiles can also affect the disk space.

22 March 2013

The executables on the local host are replicated from the executables on the global hostevery time the local instance is started. The SAP copy program sapcpe compares thebinaries in the<pl at f orm>directory on the global host and the binaries in the exedirectory on the MDS. If the binaries in the exe directory are older than those in the<pl at f orm>directory, sapcpe replaces them with the newer version of the global host.

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 theUNC path \ \ <SAPLOCALHOST>\ sapl oc. If the UNC path points to a local directory, the local path (and notthe 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:

profile

global

exe

<platform>

work

config

exe

log

SYS MD*S<No>

<drive>

usr

sap

<SAPSID>

config

work

log

exe

MDS<No>

uc

Key:

\\<SAPLOCALHOST>\saploc(UNC path)

\\<SAPGLOBALHOST>\sapmnt(UNC path)

r e f e r st o

r e f e r s t o

Replication by sapcpe uc =Unicode

mdm

Accelerato rs

Archi ves

Reports

Distributions

March 2013 23

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

LocalLocal Instance(sInstance(s) (Auxiliary Server)) (Auxiliary Server)Global Host with MDS InstanceGlobal Host with MDS Instance

<SID>

Access to

global directories

<drive>

usr

sap

<SAPSID>

profile

global

exe

<platform>

SYS

uc

r e f e r s t o

\\<SAPLOCALHOST>\saploc(UNC path)

<drive>

usr

sap

<SAPSID>

r e f e r s t o

Access to

local instancedirectories

config

work

log

exe

MD*S<No>

\\<SAPGLOBALHOST>\sapmnt(UNC path)

\\SAPLOCALHOST>\saploc

(UNC path)

log

work

exe

mdm

MDS<No>

Key:

Replication bysapcpe

uc: Unicode

On global host:

SAPGLOBALHOST =SAPLOCALHOST

Accelerato rs

Archi ves

Distributions

Reports

config

3.5.2 MDM Windows Client Directories This section describes the MDM Windows client-specific directories that the MDM client installers createduring 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 \ Pr ogr am Fi l es\ SAP MDM 7. 1 directory contains, for example executables, logs, and the languagefiles for the client UIs.

3.6 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 wantto perform.

a. Downloading Installation Files from SMP

b. Obtaining Installation Files from DVD

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.

24 March 2013

If you download an installation DVD, the DVD might be split into several files. In this case, youmust reassemble the required files after the download.

3.6.1 Downloading Installation Files from SMP You can download installation files from the SAP Software Download Center on SMP. The SAP SoftwareDownload Center enables you to download individual components one by one, or download an entire stackof components at once, by using one of the following options:

· Entry by Component: Used to download individual components one by one. You select the targetoperating system for the component, and then you select the items to download. Typically, you select thelatest 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 SPthan the one currently installed. After selecting the target SP, you select for each component theinstantiation, 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: http://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 theversion 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.

3.6.2 Obtaining Installation Files from DVD1. Identify the files required to install your MDM servers from the following list.

MDM Installation Type Installation File Archive on SMP

Central Installation MDM Installation Master

Master Data Server Installation Packagemdm-server-<build>-<Windows platform>.zip

MDM Import Server Installation Packagemdm-import-server-<build>-< Windows platform>.zip

MDM Syndication Server Installation Packagemdm-syndication-server-<build>-< Windows platform>.zip

MDM Shared Installation Content Packagemdm-shared-<build>-< Windows platform>.zip

On DVD, the above MDM components reside unpacked inthe Ser ver_I nstal l at i on directory.

SAP Instance Framework Installation Package

Distributed Installation of Master Data Server

MDM Installation Master

Master Data Server Installation Packagemdm-server-<build>-<Windows platform>.zip

MDM Shared Installation Content Package

March 2013 25

mdm-shared-<build>-< Windows platform>.zip


Distributed Installation of MDM Import Server


MDM Import Server Installation Packagemdm-import-server-<build>-< Windows platform>.zip



Distributed Installation of MDM Syndication Server


MDM Syndication Server Installation Packagemdm-syndication-server-<build>-< Windows platform>.zip



Distributed Installation of MDM Layout Server


MDM Layout Server Installation Packagemdm-layout-server-<build>-< Windows platform>.zip



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

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

If you copy the DVD to disk, make sure that the paths to the destination location of the copiedDVD do not contain any blanks.

If you perform a domain installation using the network drives for mapping the installation DVD,make sure that the <sapsi d>admuser has access to the UNC paths of the network drives.

26 March 2013

4. Installation This section describes how to install the following components:

· MDM servers (MDS, MDIS, MDSS, MDLS) on released Windows platforms 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 Installing MDM ServersInstall the MDM servers as instances of an SAP system using SAPinst. In a single installation run, you caninstall all MDM servers or a single MDM server on one host.

This section is structured as follows:

· Running SAPinstExplains the prerequisites and the general procedure for performing an SAP system installation with

SAPinst.· SAPinst Installation Options

Lists the MDM options that you can select in SAPinst for different installation types and softwarelifecycle tasks.

· Interrupted Installation with SAPinst

Explains how to proceed if the installation run of SAPinst has been interrupted manually or by thesystem.

· Performing a Remote Installation with SAPinst, Starting SAPinst GUI Separately, and SilentInstallation with SAPinst

Describes optional alternative ways of starting and running SAPinst.

· Entries in the Services File Created by SAPinst, How to Avoid Automatic Logoff by SAPinst,Troubleshooting with SAPinst

Provides additional useful information about the usage of SAPinst.

4.1.1 Running SAPinstSAPinst includes a SAPinst GUI and a GUI server, which both use J ava.

This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on thesame host: When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via asecure SSL connection to the GUI server and the GUI server connects to SAPinst.

· SAPinst normally creates the installation directory sapi nst_i nstdi r , where it stored its log files. This directory is located directly in the Pr ogr am Fi l es directory.If SAPinst is not able to create sapi nst_i nstdi r in this location, it tries to create

sapi nst_i nstdi r in the directory defined by the environment variable TEMP.

· We recommend that you keep all installation directories until you are certain that the system hasbeen completely and correctly installed.

· SAPinst creates a subdirectory for each installation option called<sapi nst _i nst di r >\ .

· The SAPinst Self-Extractor extracts the executables to a temporary directory. These executables aredeleted after SAPinst has stopped running.Directories called sapi nst _exe. xxxxxx. xxxx sometimes remain in the temporary directory. Youcan safely delete them.

The temporary directory also contains the SAPinst Self-Extractor log file dev_sel f ex. out , whichmight be useful if an error occurs.

March 2013 27

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 communicationbetween 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:cd <DVD dr i ve>: \ I M_WI NDOWS_<pl at f or m>Enter the following command in a single line:sapi nst . exe SAPI NST_DI ALOG_PORT=<f r ee_port _number_sapi nst _t o_gui _server >GUI SERVER_DI ALOG_PORT=<f r ee_por t _number _gui _ser ver_t o_sapi nst _gui >GUI SERVER_HTTP_PORT=<f r ee_port _number _ht t p_server>

To get a list of all available SAPinst properties, go to the directory(%TEMP%\ sapi nst _exe. xxxxxx. xxxx), after you have started SAPinst, and enter the commandsapi nst . 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.

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

Input Type Label Description

Menu option File® Exit Stops the SAPinst GUI. SAPinst and the GUI servercontinue running.

During the installation, if you log off from thehost where you control the installation withSAPinst GUI, the installation continues.

You can reconnect to the same SAPinstinstallation from the same host or a differenthost later on. For more information, seesection Starting SAPinst GUI Separately.

Menu option SAPinst ® Log Browser Displays the Log Viewer dialog box in which you canaccess the following log files:

· Installation log (sapi nst _dev. l og)

· Log files from the SAPinst GUI server

These log files might help you during troubleshooting. Formore information, see section Troubleshooting withSAPinst.

Menu option SAPinst ® Cancel Cancels the installation with the following options:

· Stop

Stops the installation (SAPinst GUI, SAPinst and

the GUI server) without making any furtherchanges to the installation files.

28 March 2013

Input Type Label Description

You can restart and continue the installation fromthis point later on.

· ContinueContinues the installation

Message button Retry Performs the installation step again (if an error occurred)

Message button Stop Stops the installation without making any further changesto the installation files

You can continue the installation from this point later on.

Message button Continue Continues with the option that you chose before

Prerequisites

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

· You need at least 300 MB of free space in the installation directory for each installation option. In

addition, you need 60-200 MB free space for the SAPinst executables.

· Make sure that you have defined the most important SAP system parameters as described in thesection Basic SAP System Parameters before you start the installation.

· Check that your installation host(s) meet(s) the requirements for the installation option(s) that youwant to install. For more information, see section Hardware and Software Requirements.

Procedure

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 sapi nst . exe from thefollowing path:<DVD dr i ve>: \ Ser ver _I nst al l at i on\ I nst al l at i on_Master \ MDM_I M_<pl at f or m>

SAPinst GUI starts automatically by displaying the Welcome screen.

To use a virtual host name, start SAPinst as follows:sapi nst . exe SAPI NST_USE_HOSTNAME=<vi r t ual host name>

3. In theWelcome screen, choose the required SAPinst installation option from the tree structure. Formore information, see section SAPinst Installation Options below.

To use the installation option Software Life-Cycle Options ® Operating System Users andGroups, 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 createthem manually. Make sure that you have the required user authorization for these accountsbefore 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

6. To start the installation, choose Start.SAPinst starts the installation and displays the progress of the installation. When the installation has

March 2013 29

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

7. We recommend that you delete all the files in the directory%user pr of i l e%\ . sdt gui \ .

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

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).

Installation Option Description

Central System

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 an MDS instance.

Master Data Server (in an existing SAP system)

Adds a new MDS instance to an existing SAP system, which is suitablefor running MDM.

Master Data Import Server (in an existing SAP system)

Adds a new MDIS instance to an existing SAP system, which is suitablefor running MDM.

Master Data SyndicationServer (in an existing SAP system)

Adds a new MDSS instance to an existing SAP system, which is suitablefor running MDM.

Master Data Layout Server (in an existing SAP system)

Adds a new MDLS instance to an already existing SAP system which issuitable for MDM.

This option is only available on Windows platforms.

Addi tional Sof tware Li fecycle Opt ions

Operation System Usersand Groups

Creates all operating system accounts for your SAP system.

In most cases, this is optional. However, you must execute this option touse global accounts that are configured on separate hosts.

Configure TREX Configures MDS to connect to TREX.

More information: 4.3 Installing Additional MDM Components on page 38® TREX Client

Configure SLD Generation Configures MDM instances for registration as technical systems in theSystem Landscape Directory (SLD)

Use this option only for SAP NetWeaver Process Integration (PI) 7.11and higher. In lower versions of PI (or XI), register MDM manually in theSLD.

More information:

· help.sap.com/nwmdm71 ® Monitoring and Supportability: How-

To Guides (ZIP) ®MDM 7.1 How To Register MDM in SLD (PDF)

· service help.sap.com/nwmdm71 ® Scenario Configuration

Guide ® Setting Up PI

30 March 2013

Installation Option Description

Install and Configure CCMS Agent and MDM CCMS Plug-in

Installs the SAP CCMS Agent with the MDM CCMS plug-in and registersthe 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 Monitoring 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 MDMservers.

More information: Section Updating MDM Servers

Uninstall MDM Uninstalls all MDM instances and deletes the SAP system.

4.1.3 Interrupted Installation with SAPinst 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 thetable 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 theprevious steps. This is possible because SAPinst records the installation progressin the keydb. xml file.

We recommend that you view the entries in the log files, try to solve the problemand then choose Retry. If the same or a different error occurs again, SAPinstdisplays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUIserver. SAPinst records the installation progress in the keydb. xml file.

Therefore, you can continue the installation from the point where you stoppedwithout 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-clickingsapi nst . exe. You can also start SAPinst by entering the following commands at the Windows command prompt:cd <DVD dr i ve>: \ MDM_I M_WI NDOWS<pl at f or m>

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

5. In the What do you want to do? screen, choose one of the following options, and confirm with OK.

Alternat ive Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, itmoves the content of the old installation directory and allinstallation-specific files to the backup directory. Afterwards, you

March 2013 31

can no longer continue the old installation.

For the backup directory, the following naming convention is used:<l og_day_mont h_year _hours_mi nut es_seconds>(forexample, l og_01_Oct _2008_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point where

you stopped.

4.1.4 Performing a Remote Installation with SAPinst(Optional)Use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI serverrun on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which youcontrol the installation with SAPinst GUI.

Alternatively, use an X server for Microsoft Windows or other remote desktop tools like vncvi ewer ornxser ver / nxcl i ent – offered by various vendors or open source – for remote access to SAPinst GUI onWindows workstations. We recommend that you use the Hummingbird Exceed X Server.

The client-server mode is not active by default, because SAP is not allowed to deliver thecryptographic library that is required for the encryption of client-server communication due tolegal requirements.For more information, see SAP Note 1238121.

Prerequisites

· The remote host meets the prerequisites before starting SAPinst as described in section RunningSAPinst above.

· Both computers are in the same network and can “ping” each other.

To test this:a. Log on to your remote host and enter the command pi ng <l ocal host >.

b. Log on to the local host and enter the command pi ng <r emote host >.

Procedure

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. Enter the following commands:cd <DVD dr i ve>: \ MDM_I M_WI NDOWS_<pl at f or m>sapi nst . exe - nogui

For more information, see section Running SAPinst.SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at thecommand prompt:gui engi ne: no GUI connect ed; wai t i ng f or a connect i on on host <host _name>,por t <por t _number > t o cont i nue wi t h t he i nst al l at i on

4. Start SAPinst GUI on your local host as described in section Starting SAPinst GUI Separately below.

4.1.5 Starting SAPinst GUI Separately (Optional) 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 isstill running, start SAPinst GUI separately.

32 March 2013

· 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 GUIseparately.

With SAPinst, for remote installations, the client-server mode is not active by default, because

SAP is not allowed 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.

Starting SAPinst GUI on Windows1. 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 dr i ve>: \ MDM_I M_WI NDOWS_<pl at f or m>

To start SAPinst GUI on a Windows 32-bit operating system, change to the following directory:\ SAPI NSTGUI _710_WI NDOWS_I 386

4. Start SAPinst GUI by double-clicking sapi nst gui . exe.SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host asdefault.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears. In this case, enter the name of the host on whichSAPinst is running and choose Log on.

The first dialog of the installation appears and you can perform the remote installation from your localhost.

You can start sapi nst gui . exe with the following optional parameters:- host =<host name>, where <host name>is the host name of the installation host- por t =<nr>, where <nr >is the port number for the connection to the GUI server- - accessi bl e enables the Accessibility modeExample:. / sapi nst gui . exe host =l si 1209 por t =3000 - accessi bl e

Starting SAPinst GUI on UNIX1. Log on as user r oot .

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

2. Mount your Installation Master DVD.

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

3. Change to the directory of the SAPinst executables:<mountpoi nt_of _I nst al l at i on_Mast er_DVD>/ MDM_I M_<OS>

To start SAPinst GUI on a Linux 32-bit operating system, change to the following directory:<mount poi nt _of _I nst al l at i on_Mast er_DVD>/ SAPI NSTGUI _710_LI NUX_I 386

March 2013 33

4. Start SAPinst GUI by executing . / sapi nst gui .SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host asdefault.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP 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 localhost.

You can start sapi nst gui with the following optional parameters:- host =<host name>, where <host name>is the host name of the installation host- por t =<nr>, where <nr > is the port number for the connection to the GUI server- - accessi bl e enables accessibility modeExample:. / sapi nst gui host =l si 1209 por t =3000 - accessi bl e

4.1.6 Silent Installation with SAPinst (Optional) 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 anysubsequent unattended installation.

For the detailed procedure, see SAP Note 950619.

4.1.7 Entries in the Services File Created by SAPinstOnce the installation is complete, SAPinst creates the following entries in:<dr i ve: >\ WI NDOWS\ syst em32\ dr i ver s\ etc\ servi ces:

sapdpXX = 32XX/ t cp

sapdbXXs = 47XX/ t cpsapgwXX = 33XX/ t cp

sapgwXXs = 48XX/ t cp

where XX is set from00 to 99.

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

4.1.8 Avoiding Automatic Logoff by SAPinstWhen you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user account

used for the installation has the required privileges and authorization.For a domain installation, the account must be a member of the local Admi ni st r at or s and a member of the domain Admi ns group. For a local installation, the account must be a member of the localAdmi ni st r at or s group.

In both cases, 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 theaccount to activate them. To prevent SAPinst from logging off the account, set these rights manually beforeyou start the installation.




34 March 2013

Be aware that domain policies override locally defined policies. This means that to grant domainadministrator rights for a user who belongs to the local Admi ni st r at or s group, make sure thatyou have also defined domain administrator rights for this user on domain level.

To assign these rights to the user account used for the installation:

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 theinstallation.

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

4.1.9 Troubleshooting with SAPinstIf 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.For more information, see section Interrupted Installation with SAPinst.- 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:%user pr of i l e%\ . sdt gui \

- If GUI server or SAPinst GUI do not start, check the file sdt start . err in the current userdirectory.- If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI asdescribed in section Starting SAPinst GUI Separately.

4.2 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 managementclients (for example, the MDM Data Manager or the MDM Import Manager).

To run MDM Windows clients, a Windows user must have read/write access toHKLM/ SOFTWARE/ SAP/ MDM 7. 1 in the Windows registry.

The MDM Windows client installation procedure for MDM 7.1 is still the same as the one forMDM 5.5.

Preparation

1. Check the Product Availability Matrix (PAM) on SAP Service Marketplace at

service.sap.com/pam ® SAP NETWEAVER ® SAP MDM for supported Windows releases.2. Log on to your host as a user with administrator rights.




March 2013 35

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

4. Extract the MDM installation executables.

4.2.1 Installation Modes 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 Windowsinitialization file (extension .ini).

For more information about the installation prerequisites and dependencies of individual components, seethe table below.

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

Silent Mode To install a single component:

1. Open a Windows Command Prompt and navigate to the folder containing the extracted installationexecutable(s).

2. Launch the executable and pass the parameter / s and the path to an initialization file (for example,enter MDMI mpor t Manager I nst al l . exe / s i nst al l . i ni ).

With the optional initialization file you can override the default installation settings. You can use one.ini file for all components. We ship a sample .ini file together with the installation executables. Formore information about the file structure and the individual settings, see comments in theinitialization file.

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

To install a collection of components in one run:

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 inseparate lines. For a lean MDM client installation, the batch file might look as follows:

MDMConsol eI nst al l . EXE / s i nst al l . i niMDMDat aManager I nst al l . EXE / s i nst al l . i ni

MDMI mpor t Manager I nst al l . EXE / s i nst al l . i niMDMLanguageSel ect or I nst al l . EXE / s i nst al l . i niMDMSyndi cat or I nst al l . EXE / s i nst al l . i ni

With the optional initialization file you can override the default installation settings. You can use oneinitialization file for all components. We ship a sample .ini file together with the installationexecutables. See the initialization file for more information about the file structure and the individualsettings.

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

Check whether installation was successful using the i nst al l . l og file, which is written tothe corresponding installation directory for each component.

36 March 2013

4.2.2 MDM Windows Clients in DetailComponentShipped Files

Prerequisites Remarks

MDM Console

MDMConsoleInstall_<build>.exe

The MDM Console and CLIX must have

TCP/IP access to the MDS. The machine running the MDM Consoleand MDM CLIX must be in the samenetwork domain as the MDS.

The Console and CLIX user must knowthe user name and password for theDBMS server with read/write/createpermissions.

The Console and CLIX user must haveread/write permissions on the MDSmachine.

The administration command line

tool MDM CLIX is automaticallyinstalled with the MDS (at<syst em dr i ve>: \ usr \sap\ <SAPSI D>\ \ exe).

You only need to install the toolmanually for remote access toMDS, for example, from a localPC.

To use the Start Server commandin the Console, the logged-inWindows user must havepermission to start the MDS

service on the (remote) machine.

MDM CLIX

MDMCLIXInstall_<build>.exe

MDM Data Manager

MDMDataManagerInstall _<build>.exe

The MDM Data Manager must have TCP/IP access to the MDS. Thisconnection can be local or remote.

Install MS Visio on the machines onwhich you want to model (not run)MDM workflows.

In MS Visio, make the followingsettings for MDM Workflow:

· Under Tools ® Options ®

Advanced® File Paths...set both Add-ons andStart-up to the folderwhere MDM VSL isinstalled (C:\ProgramFiles\SAP MDM 7.1\Workflow\VSL in a standardWindows installation).

· Under Tools ® Options ®Security choose Enable Automation Events.

MDM Import Manager

MDMImportManagerInstall_<build>.exe

The MDM Import Manager and theMDM Syndicator must have TCP/IPaccess to the MDS. This connectioncan be local or remote.

To enable the MDM ImportManager to generate XMLschemas from XML files uponimport, the xsd. exe must residein the same folder as the ImportManager executable.

The xsd. exe is part of theMicrosoft .NET Framework SDK

(Software Development Kit) 2.0,which can be downloaded from thedownload center of the Micrsosoftweb site.

MDM Syndicator

MDMSyndicatorInstall_<build>.exe

MDM LanguageSelector

MDMLanguageSelectorInstall_<build>.exe

To display the MDM client component'suser interfaces correctly in East Asianlanguages, you may need to installthese languages on Windows (Settings

® Control Panel ® Regional and

Language Options ® Languages).

MDM UOM Manager

MDM_UOMManagerInst

all_<build>.exe

The client software of the underlyingdatabase must be installed on the UOM

Manager host.

March 2013 37

ComponentShipped Files

Prerequisites Remarks

MDM Image Manager

MDMImageManagerInstall_<build>.exe

You must install Adobe Photoshop®before installing the Image Manager.

The Image Manager must have TCP/IP

access to the MDS. This connectionmust be local to be effective.

MDM Publi sher

MDMPublisherInstall_<build>.exe

MDLS must be installed first.

MDM Indexer

MDMIndexerInstall_<build>.exe

MDM Publisher must be installed first.

InDesign® Plug-In

InDesignPlugin<InDesignversion>Install_<build>.exe

Adobe InDesign®must be installedfirst.

The machine on which the plug-in isinstalled must have TCP/IP access tothe MDS, MDLS, and Data Manager.

This connection must be local to beeffective.

The Plug-In for InDesign version CS3requires the Microsoft Visual C++ 2005SP1 Redistributable Package (x86),which you can download from theMicrosoft web site.

Install the MDM plug-in in theInDesign default plug-in directory.

38 March 2013

4.3 Installing Addit ional MDM ComponentsComponentShipped Files

Prerequisites / Remarks Installation Procedure

MDM Java API andMDM Connecto r For hosted applications, you needSAP NetWeaver 2004 or 7.0.

For standalone applications, youneed a J ava 1.4.2 compatible

J ava Virtual Machine.

Deploy the components on your Javamachine.

For more information, seehelp.sap.com/nwmdm71 ®MDM Java

and .NET API Guide.

MDM Portal Content MDM Connector and MDM J avaAPI are deployed (see above).

Deploy the components on your EP.

For more information, seehelp.sap.com/nwmdm71 ® Portal

Business Package for Master DataManagement

MDM PI Adapter The SAP NetWeaver Process

Integration (PI) is installed.MDM Connector and MDM J avaAPI are deployed (see above).

Deploy the components and the adapter

content on your PI.For more information, seehelp.sap.com/nwmdm71 ®MDM

Process Integration (PI) Adapter Guide

MDM ABAP API An ABAP system is installed. Deploy components on your ABAP systemas SAP Add-On.

For more information, seehelp.sap.com/nwmdm71 ®MDM ABAP

API and the application help of transactionSAINT.

MDM Web Services For more information, see

help.sap.com/nwmdm71 ®MDM WebServices

MDM DOTNET API For more information, seehelp.sap.com/nwmdm71 ®MDM Java

and .NET API

MDM COM API

MDMCOMInstall_<build>.exe

As Microsoft .NET is thetechnological successor of Microsoft COM, the MDM COMAPI is deprecated with MDM 7.1.Customers are advised not tostart any new projects based onthe MDM COM API and to

consider migration to theMicrosoft .NET framework, as theMDM COM API will not be part of the next MDM release.

See section Installing MDM WindowsClients above.

MDM EnrichmentController

SAP Web Application Server 6.40(J ava), MDS, MDIS, and MDSSare installed.

MDM Connector and MDM J avaAPI are deployed (see above).

For more information, seehelp.sap.com/nwmdm71 ®MDM

Enrichment Architecture.

March 2013 39

ComponentShipped Files

Prerequisites / Remarks Installation Procedure

TREX Client

MDMProtocolHandler.dll

The TREX server must be version7.1.

For performance reasons we

recommend that you install TREXserver and MDS on differenthosts. If you install them on thesame host, both must be 64bitversions.

When installing TREX server foruse with MDM there is no need toset a communication protocol.

The MDS host must haveincoming TCP traffic enabled onport 59950.If there is a firewall on the MDM

server, the firewall must beconfigured to permit traffic on thisport.

The MDM-TREX integrationsupports English documents only.

For more information about TREXinstallation seeservice.sap.com/

installNW70® Installation -

Standalone Engines ® SAPNetWeaver Search andClassification TREX

1. If MDS and TREX server reside ondifferent hosts, you must install a TREXinstance on the MDS host. This additional

TREX is used as a client for MDM. To use TREX as client for MDM, disablethe server aspect of the additional TREX.For more information, see SAP Note1133493.

2. On your MDS host, start SAPinst,choose Additional Software-Lifecycle

Options® TREX Configuration and followthe instructions on the screen.

3. On your TREX server host, stop the TREX server processes.

4. Copy the file MDMProtocolHandler.dll to

the TREX server executables directory (thisdirectory also containsTREXPreprocessor.exe).

5. Open the Properties dialog of the DLL.On the Security tab page, verify that the

TREX service user(SAPService<TREX_SID>) or a group the

TREX user is member of (for exampleSAP_<TREX_SID>LocalAdminsorSAP_LocalAdmin), has all permissions forthe DLL.

6. Open the TREXPreprocessor.ini filelocated on the TREX server.

7. Search for a section in theTREXPreprocessor.ini file called[ pr ot ocol ] . If this section does not exist,add it to the end of the file.

8. In the [ pr ot ocol ] section, add thefollowing line (if it does not already exist):mdm=mdswr ap

9. Save and close TREXPreprocessor.ini

and restart the TREX server processes.

MDM Web Dynpro SAP NetWeaver MDM WebDynpro Framework 7.1 SP5 Patch

2 or higher

For more information, seehelp.sap.com/nwmdm71 →

Development and Customization→ MDMWeb Dynpro Components.

Refer to the following sections:

· Installing the MDM Web DynproEnvironment

· Deploying the MDM Web DynproComponents Framework

MDM CollaborativeProcesses for Material

MDM Collaborative Processes forMaterial 7.10 7.20

For more information, seehelp.sap.com/nwmdm71 ®MDM

Business Content Extensions®Collaborative Processes for Material

Master Data Creation

40 March 2013

4.4 Installing and Configuring the DatabaseBefore the MDS can handle data, you must install and configure the database.

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

Starting from MDM 7.1 SP06, the installation for Windows asks you which database server[s] will be used byMDM. Then, for each server, the installation searches for the database client and does not continue if thedatabase client is not found on the server.

Note the following when planning the MDS and database combination:

· Make sure that your operating system meets the prerequisites for the database you want to run,including any necessary service packs, hot fixes, libraries, or dlls. For more information, see the OSand DB documentation.

· DBMS client software must be installed on the machine that runs the MDS. Make sure that theMDM user SAPSer vi ce<SI D>has the necessary rights for accessing the database client.

· The DBMS user that MDM uses to connect to a DBMS must have access rights equivalent to thesystem user. You can use the system account or create a user with equivalent rights. The built-insystem accounts are as follows:- MS SQL – sa (reserved)- Oracle – system (reserved)- DB2 – db2admin (configurable installation option)- MaxDB - dbm (configurable installation option)

4.4.1 Microsoft SQL Server

When installing Master Data Server instances on Windows Server 2008 and connecting to anSQL Server database, make sure that the SAP Instance Framework used for MDM is of SAPKernel version 710 patch 146 or higher. This instance framework patch level is delivered with theMDM 7.1 SP02 installation package.

To check the instance framework version of an MDM instance proceed as follows:- Start the SAP Microsoft Management Console (SAP MMC)- In the context menu of the instance node choose Version Info.

1. Install the SQL Server and create the appropriate database instances.

MS SQL can be installed as a Named Instance or a Default Instance. When using MS SQL as a

Named Instance, in which the fully qualified name contains a backslash (\), you must use the MSSQL Client Network Utility to create an alias for that instance. You then refer to the alias insteadof 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 onseparate machines, you might need to change the network connection between the MDS and theDBMS 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 theGeneral tab.

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




March 2013 41

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

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 justdifferent drive letters.

· When MDS creates database schemas, it does not set the recovery method. So SQL Servercreates a new database schema with the method that the "model" database uses. If you wish toexplicitly use a setting different than "model", use one of the following parameters in the top sectionof mds.ini:- SQL Ser ver Recovery Type=Ful l- SQL Ser ver Recovery Type=Si mpl e- SQL Ser ver Recovery Type=Bul k_Logged

Unarchiving mainly BLOB-based repositories (containing many PDFs, pictures and so on) runssignificantly faster when using Si mpl e orBul k_Logged. On other repositories Ful l is slightlyfaster.

· Define the storage paths. The first time you connect the MDS to the database using MDM Console, a dialog box appearsasking 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 databasehost machine. Furthermore, if you choose different locations for the Data path and Log path so thatthey are on different hard disks (different physical spindles, not just logical drives), databaseperformance may improve by a small degree. The directory paths you specify must already exist onthe 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 separatepartition (Schema and Tablespaces).Choosing two or four partitions gives you the option of performing SQL Server-based backups on adifferent schedule for the various partitions. Since Thumbnails and Variants can be recreatedthrough MDM, these can be backed up less frequently or not at all. For many use cases, Originalschange at a less frequent rate than Main data. This means they can also be backed up lessfrequently in a four partition configuration.

· With SQL Server 2005, the Full-text Indexing feature is automatically on. Since MDS does not needthis feature, it is explicitly turned off when creating repository database schemas. This slightlyimproves performance for many database operations. To override the default and enable thisfeature at repository creation, enter the following in the top section of mds.ini:SQL Server Enabl e Ful l - Text I ndexi ng=t r ue

4.4.2 Oracle DBMS

Instal l 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 Oracleclient.

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

sure you select Create and configure database (and not Install database software only).

42 March 2013

· If the MDS and the DBMS are on the same machine, use the Net Configuration Assistant to define aListener address and local Service Name that uses the IPC protocol rather than TCP. This affectsthe l i s tener . ora and t sname. ora files, which can also be edited manually. This increases therepository unarchive performance.

· To determine the Oracle client versions that are supported for the various DBMS versions, refer tothe Oracle server/client interoperability support matrix.

In earlier versions of Oracle, by default, passwords did not expire. Starting from Oracle 11, thedefault is that passwords expire in 180 days. Password expiration has a negative impact onMDS. This is due to the fact that during the days before the password expires, warningmessages about password expiration interfere with MDS operations.

· Oracle’s performance increases when separate spindles (hard disks) are used for the main dataand indices. Rollback segments (for transactions and logging) are set at database instance creationtime and can represent an opportunity to use three separate spindles. The location of the main andindex 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 sothat the MDM service can inherit the Oracle path from the system.

· The Cur sor Shar i ng parameter is set on a session basis to be exact . This provides a smallperformance improvement for certain operations between MDS and the Oracle Server. For earlierversions of MDM, you can turn this parameter on globally for the entire Oracle instance with thefollowing command:ALTER SYSTEM SET cursor _shari ng=' 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.

Unicode character sets are the only character sets that MDS supports. Do not use an Oracledatabase instance that has different character sets for MDM.

To use an existing database instance, run the following queries to determine the charactersets:

- National Character Set:sel ect VALUE f r om NLS_DATABASE_PARAMETERS wher ePARAMETER=' NLS_NCHAR_CHARACTERSET'

- Database Character Set:sel ect VALUE f r om NLS_DATABASE_PARAMETERS wher ePARAMETER=' NLS_CHARACTERSET'

If the results of the above queries do not return Unicode character sets, you must create anew database instance for MDM.

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

Set Up and Test the Connection1. To connect to the database, create an entry in the t nsnames. ora file. On Windows, the

t nsnames. ora file is typically located in \ or acl e\ . . . \ net wor k\ admi n. The entry must use the following format:<net ser vi ce name speci f i ed i n the MDM Consol e as DBMS server> =

( DESCRI PTI ON =( ADDRESS_LI ST =

( ADDRESS = ( PROTOCOL = TCP) ( HOST = <f ul l y qual i f i ed I P addressor domai n of t he host machi ne runni ng t he Or acl e DBMS>) ( PORT=<number of t he por t used by DBMS host wi t h def aul t 1521>) )

)( CONNECT_DATA =

March 2013 43

( SERVI CE_NAME = <Or acl e ser vi ce name speci f i ed when t he Or acl eDBMS was i nst al l ed>)

))

Test the net service name by logging onto the Oracle database from the MDS host using the OracleSQLPLUS command as follows:

sql pl us <user i d>/ <passwor d>@<net ser vi ce name>Alternatively, test the connection to the Oracle database with the following command:t nspi ng <net ser vi ce name>

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

Connect Initially1. Modify the temporary tablespace.

When connecting to the DBMS for the first time (DBMS initialization), the system account or anequivalent account is used to make the connection and the DBMS is queried for the temporarytablespace of that account. Normally this tablespace is named TEMP.

If the site needs to use a different tablespace, modify the temporary tablespace of the connectingaccount 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 touse to connect to the DBMS. By default you use the SYSTEMaccount for all access. To use anotheraccount or if the use of the SYSTEMaccount is not allowed in your DBMS, use the SYSTEMaccount,or the MDM Console/CLIX feature to create an alternative account.Model your account creation according to the following template:

cr eat e user HARRY_POTTER i dent i f i ed by muggl es def aul t t abl espaceSYSTEM;

gr ant al t er user , al t er system, cr eat e sessi on, cr eat e any i ndex,cr eat e vi ew, dba, dr op any vi ew, cr eat e any tabl e, del et e any tabl e,

dr op any t abl e, i nser t any tabl e, updat e any t abl e, sel ect anyt abl e, al t er t abl espace, cr eat e t abl espace, dr op t abl espace,unl i mi t ed t abl espace, cr eat e any sequence, dr op any sequence, al t erany sequence, sel ect any sequence, l ock any t abl e, al t er any t abl e,al t er any t ype, al t er dat abase, creat e pr of i l e, dr op pr of i l e, creat edat abase l i nk, dr op any i ndex, cr eat e user, dr op user, cr eate anydi r ectory, cr eat e any procedure, anal yze any t o HARRY_POTTER;

3. Define the tablespace directories. The first time that you connect the MDS to the database using MDM Console, a dialog box appearsasking you where you want to store data and index tablespace files. This optional step slightlyimproves performance:

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 thedatabase host machine. Furthermore, if you choose different locations for the datatablespace and index tablespace so that they are on different hard disks (different physicalspindles, not just logical drives), database performance can improve by a small, butsignificant, degree. The directory paths you specify must already exist on the database hostmachine.

b. These settings apply to repositories only as they are created. Existing repositories staywhere they were created.

c. To gain even more detailed control your tablespaces, or to use tablespaces that alreadyexist, see the Allow Flexible Tablespaces section below.

After a repository is created through create, unarchive, duplicate or slave operations, alltables and indexes are analyzed in the final step.

44 March 2013

We recommend that you re-analyze tables to maximize the performance of the DBMS romtime 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 asthe DBMS server in the Add DBMS Server dialog. This name should be defined using Oraclenetworking methodologies.

Adjust Temporary Tablespace for MCODFor MCOD (MDM sharing the same database with other SAP components, such as SAP ERP ECC or SAPNetWeaver Application Server), check and adjust the temporary tablespace.

The first time MDS establishes a relationship with a particular Oracle instance, it queries the temporarytablespace name of the initial login, for example SYSTEM. The retrieved value, for example TEMP, is stored inMDM in the A2i _xCat_DBs. A2i _DB_Set t i ngs table in the TempTabl eSpaceName field. MDM queriesthis table when creating more users or schemas.

In an MCOD environment where the database has been installed with SAP NetWeaver AS J ava using

SAPinst, the temporary tablespace is set to PSAPTEMP. To adjust the temporary tablespace setting, proceedin one of the following ways:

· In the MDM Console, choose DBMS Settings from context menu of your MDS and set the Temptablespace name.

· Use the following CLIX command:cl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec>

TempTabl eSpaceName=PSAPTEMP

Allow Flexible Tablespaces You can detach from the methods built into MDM for the creation of Oracle database storage. As anexperienced 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 logicalconcept of a tablespace, Oracle allows you to manage the actual files that are used for a tablespaceindependent 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 atwo partition arrangement, Main and Originals are placed in one partition, with Thumbnails andVariants being placed in the other. With four partitions, each data collection type has a separatepartition (schema and tablespaces).

Choosing two or four partitions gives you the option of performing Oracle based backups ona different schedule for the various partitions.Since Thumbnails and Variants can be recreated through MDM, these can be backed upless frequently or not at all. For many use cases, Originals change at a less frequent ratethan Main data, so they, too, can be backed up less frequently in a four partitionconfiguration.

· MDM creates two tablespaces for each schema, one for data and the other for indexes. The namesof the schemas are derived from the repository name, and in turn the tablespace names are derivedfrom the schema names.

· MDM uses a single directory location on an individual DBMS for all data tablespaces and anothersingle directory for index tablespaces. These two settings are controllable from the MDM Console.

March 2013 45

This arrangement is convenient for the majority of use cases; however, it limits the full control of location andother parameters in the creation and management of tablespaces that are possible in Oracle databases. Youcan create tablespaces according to the requirements of your particular installation as described below.

Tablespace Enhancement

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_SETTI NGS

You must add several rows that are not automatically created through use of the MDM Console or CLIX, bymanually using scripts and/or SQL*Plus utility of Oracle. Once these rows are created, they can bemaintained using the MDM Console.

The A2I _XCAT_DBS. A2I _DB_SETTI NGS table creates the following records:

NAMEcolumn

SETTINGcolumn

Explanation

DataPath Actual pathor empty

Already exists and managed by MDM Console. A single directory wheredata tablespaces are created.

I ndexPat h Actual pathor empty

Already exists and managed by MDM Console. A single directory whereindex tablespaces are created.

t sname_m Name of tablespaceyou created

Tablespace name formain repository schema tables. If this record ismissing or the Setting column is blank or empty, the DataPath record isused to create a new tablespace.

t sname_mx Name of tablespaceyou created

Tablespace name formain repository schema tables indexes. If thisrecord is missing or the Setting column is blank or empty, the IndexPath

record is used to create a new tablespace.

t sname_o Name of tablespaceyou created

Tablespace name fororiginals repository schema tables. If this recordis missing or the Setting column is blank or empty, the DataPath recordis used to create a new tablespace.

t sname_ox Name of tablespaceyou created

Tablespace name fororiginals repository schema tables indexes. If thisrecord is missing or the Setting column is blank or empty, the IndexPath

record will be used to create a new tablespace.

t sname_t Name of tablespaceyou created

Tablespace Name forThumbnails Repository Schema Tables. If thisrecord is missing or the Setting column is blank or empty, the “DataPath”record will be used to create a new tablespace.

t sname_t x Name of tablespaceyou created

Tablespace name for thumbnails repository schema tables indexes. If this record is missing or the Setting column is blank or empty, theIndexPath record will be used to create a new tablespace.

t sname_v Name of tablespace

you created

Tablespace name for image variants repository schema tables. If thisrecord is missing or the Setting column is blank or empty, the DataPath

record will be used to create a new tablespace.

t sname_vx Name of tablespaceyou created

Tablespace name for image variants repository schema tables indexes.If this record is missing or the Setting column is blank or empty, theIndexPath record will be used to create a new tablespace.

To initially create the A2I _XCAT_DBS schema and A2I _DB_SETTI NGS table on a DBMS from the MDMConsole, choose DBMS Settings from the MDS Server node context menu or from the Server menu. Oncecreated, 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 _dbsaccount is the same as the one used to initially connect using the DBMS Settings dialog:

connect a2i _xcat _dbs/ <myPasswor d>@<myI nst ance>;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_m' , ' MMM' ) ;

46 March 2013

i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_o' , ' OOO' ) ;i nser t i nt o a2i _db_set t i ngs (name, set t i ng) val ues ( ' t sname_t ' , ' TTT' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_v' , ' VVV' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_mx' , ' MMM_I X' ) ;i nser t i nt o a2i _db_set t i ngs (name, set t i ng) val ues ( ' t sname_ox' , ' OOO_I X' ) ;i nser t i nt o a2i _db_set t i ngs (name, set t i ng) val ues ( ' t sname_t x' , ' TTT_I X' ) ;

i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_vx' , ' VVV_I X' ) ;commi t ;

You must use the names of the actual, existing tablespace or tablespaces you intend to use prior to actuallycreating a repository (creating slave, unarchiving, etc). For example, if you were using a single tablespace forall data named MDSDATAand another for all indexes named MDS_I DX, your script would be as follows:

connect a2i _xcat _dbs/ <myPasswor d>@<myI nst ance>;i nsert i nt o a2i _db_set t i ngs ( name, sett i ng) val ues ( ' t sname_m' , ' MDSDATA' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_o' , ' MDSDATA' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_t ' , ' MDSDATA' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_v' , ' MDSDATA' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_mx' , ' MDS_I DX' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_ox' , ' MDS_I DX' ) ;i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_t x' , ' MDS_I DX' ) ;

i nser t i nt o a2i _db_set t i ngs ( name, set t i ng) val ues ( ' t sname_vx' , ' MDS_I DX' ) ;commi t ;

At this point, create a new repository (or unarchive, make a slave, etc.) on that particular DBMS host.

After creating this repository, you may want to create another repository with different tablespaces. Forexample you want to regularly backup the tablespaces for a master repository, but you also want a slaverepository on different tablespaces where backups are less necessary.

Prior to creating a slave, in the DBMS Settings dialog in the MDM Console, change the setting values for thet sname_<…>setting names. Alternatively use CLIX or SQLPlus scripts which would look as follows:

· CLIXcl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_m=SLAVEDATAcl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_o=SLAVEDATAcl i x dbSetDBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_t =SLAVEDATAcl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_v=SLAVEDATAcl i x dbSetDBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_mx=SLV_I DXcl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_ox=SLV_I DXcl i x dbSet DBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_t x=SLV_I DXcl i x dbSetDBMSSet t i ng <mdsHost Spec> <dbmsSpec> t sname_vx=SLV_I DX

Once the records have been created (as shows above), the CLIX method integrates easilywith other CLIX commands such as create slave operations.

More information:Documentation of the CLIX commands <mdsHost Spec>and <dbmsSpec>at

help.sap.com/nwmdm71 ®MDM Console Reference Guide.

· SQLPlusconnect a2i _xcat _dbs/ <myPasswor d>@<myI nst ance>;updat e a2i _db_set t i ngs set set t i ng = ' SLAVEDATA' wher e name = ' t sname_m' ;update a2i _db_set t i ngs set set t i ng = ' SLAVEDATA' wher e name = ' t sname_o' ;update a2i _db_set t i ngs set set t i ng = ' SLAVEDATA' wher e name = ' t sname_t ' ;update a2i _db_set t i ngs set set t i ng = ' SLAVEDATA' wher e name = ' t sname_v' ;update a2i _db_set t i ngs set set t i ng = ' SLV_I DX' wher e name = ' t sname_mx' ;update a2i _db_set t i ngs set set t i ng = ' SLV_I DX' wher e name = ' t sname_ox' ;update a2i _db_sett i ngs set set t i ng = ' SLV_I DX' wher e name = ' t sname_t x' ;update a2i _db_set t i ngs set set t i ng = ' SLV_I DX' wher e name = ' t sname_vx' ;commi t ;

To return this DBMS to the state where MDS automatically creates tablespaces, manually delete theserecords from the database. This cannot be done from the MDM Console; use the following script:

March 2013 47

connect a2i _xcat _dbs/ <myPasswor d>@<myI nst ance>;del ete a2i _db_set t i ngs where name l i ke ' t sname_%' ;commi t ;

Notes

· When you choose this alternate method of tablespace assignment, you must create the tablespacesby yourself. To test what you have done with these assignments, create a new repository by usingfour partitions and examine the results in report files, or by using the Oracle Enterprise Manager .

· The settings in A2I _XCAT_DBS. A2I _DB_SETTI NGS table are queried when MDS performs aduplicate, unarchive, create new, or create slave operation. Afterwards these tablespace settingsremain associated with that repository even if you change the settings prior to creating anotherrepository.

· The contents of the NAME column are case-sensitive. Make sure that you use t sname_o and noother spelling.

· Once you have created these eight records in the A2I _DB_SETTI NGS table, you can change thesetting values using the DBMS Settings dialog of the MDM Console. This dialog does not allow youto add or delete records or change the name of an existing record. To change the name of a recordor to delete records, use the Oracle Enterprise Manager orSQL*Plus utilities.

· The History table, which is used for auditing, does not fall under this manual tablespacemanagement approach and still uses the settings for Dat aPat h and I ndexPath.

· When you create your own tablespaces, you must monitor their growth and manage the way thatthe size of the tablespace files is extended.

More Sample Scrip ts

· The following example shows a tablespace definition that is typical for the main data partition of anMDM repository where the tablespace is comprised of two files that can grow indefinitely:

CREATE TABLESPACE MDSDATA DATAFI LE' / usr / db/ t s/ mdsdat a1. dbf ' SI ZE 1M

REUSE AUTOEXTEND ON NEXT 1M MAXSI ZE UNLI MI TED,' / usr / db/ t s/ mdsdat a2. dbf ' SI ZE 1M

REUSE AUTOEXTEND ON NEXT 1M MAXSI ZE UNLI MI TEDDEFAULT STORAGE

( I NI TI AL 16K NEXT 64K MAXEXTENTS UNLI MI TED PCTI NCREASE 0) ;

· The following example shows a tablespace definition similar to the previous example, except thatthe file system limits files to 2 GB and you allocate the entire file space immediately to avoid diskfragmentation:

CREATE TABLESPACE MDSDATA DATAFI LE' / usr / db/ t s/ mdsdata1. dbf ' SI ZE 2048M,' / usr / db/ t s/ mdsdat a2. dbf ' SI ZE 2048M

DEFAULT STORAGE( I NI TI AL 16K NEXT 64K MAXEXTENTS UNLI MI TED PCTI NCREASE 0) ;

·

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

CREATE TABLESPACE MDS_I DX DATAFI LE' / usr / db/ t s/ mds_i dx. dbf ' SI ZE 128K

REUSE AUTOEXTEND ON NEXT 64K MAXSI ZE UNLI MI TEDDEFAULT STORAGE

( I NI TI AL 16K NEXT 64K MAXEXTENTS UNLI MI TED PCTI NCREASE 0) ;

4.4.3 IBM DB2 for Linux, UNIX and WindowsSeehelp.sap.com/nwmdm71 ® Installing and Setting Up MDM with IBM DB2 for Linux, UNIX, and

Windows.

48 March 2013

4.4.4 IBM DB2 for z/OS

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 forODBC and CLI Version 9 FixPak 1

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

The following sections describe how to install the CLI driver.

Download and Extract the Archive1. Create a directory in which to install the CLI driver. In the documentation, this directory is

<db2_cl i _odbc_dr i ver >.

2. Download the CLI driver file:

- If you are an SAP OEM customer, you can download the file from the SAP Service Marketplace athttp://service.sap.com/swdc ® 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 iscl i dr i ver .

3. Extract the file to the directory <db2_cl i _odbc_dr i ver >

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

<db2_cl i _odbc_dr i ver >.For more information about SAPCAR, see SAP Note 212876.

- If you downloaded the file from the IBM site, see the following IBM documentation for informationabout file extraction:http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.apdv.cli.doc/doc/c0023378.htm.

When you download the file from IBM and extract the file, a subdirectory cl i dr i ver is created.

Modify the PATH VariableAdd the following db2 directory to your PATHenvironment variable:<db2_cl i _odbc_dri ver >\ bi n

If a DB2 Connect client is installed on the server, make sure that the CLI Driver is found prior to the DB2Connect client.

In special cases, you must set the DB2_CLI _DRI VER_I NSTALL_ PATHenvironment variable to<db2_cl i _odbc_dri ver >. This environment variable overwrites the library path setting.

Download the CLI Driver License The CLI Driver comes with a temporary license that expires after 90 days: If a permanent license is alreadyavailable, copy it to the license directory, <db2_cl i _odbc_dr i ver >/ l i cense, to avoid unnecessary

downtime later on.


http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.apdv.cli.doc/doc/c0023378.htm

March 2013 49

On Windows NT, the user SAPSer vi ce<SAPSI D>must have permission to modify and read the license filedirectory of the IBM clidriver: <cl i _dr i ver _pat h>\ cl i dr i ver\ l i cense

Depending on the way you purchase DB2 Connect, the permanent license file for the IBM DB2 Driver forODBC and CLI is available from different sources:

· For SAP OEM Customers: If you pur chase DB2 and DB2 Connect from SAP as an OEM

customer, do the following:Go to http://service.sap.com/swdc ® Download ® Database Patches (from other vendors)

® DB2 for z/OS ® License Files for IBM DB2 Driver for ODBC, CLI or JDBC V9. The site with the license file is only accessible for OEM customers.

· For IBM Customers: If you purchase DB2 and DB2 Connect from IBM, do the following:

Retrieve the permanent license file for the IBM DB2 Driver for ODBC and CLI from the DB2 Connectimage that you receive from IBM. Depending on your edition of DB2 Connect (Enterprise Edition,Unlimited Server Edition), the name of the license file varies.

In the Enterprise Edition, the license file is called db2consv_ee. l i c.

Catalog Database Server to db2cli.ini This file is located in directory <db2_cl i _odbc_dr i ver >/ cf g/ db2cl i . i ni .

Add the following section to the db2cl i . i ni file (with your values):

[ <DBALI AS>]

DATABASE=<LOCATI ON NAME>

PROTOCOL=TCPI P

HOSTNAME=<HOSTNAME>

SERVI CENAME=<DDFPORT>

Where:

· <DBALI AS> is the logical name of the database under which the database is known to the MDMConsole.

You must specify the <DBALI AS>within the MDM Console when you specify the DB2 for z/OSdata source for your archives.

· <LOCATI ON NAME> is the DDF Location name of the DB2 Subsystem

· <HOSTNAME>is the name of the database host

· <DDFPORT>is the DDF listening port of the DB2 Subsystem

The DB2 command - DI SPLAY DDF displays the DDF Port as TCPPORT and the DDF Location Name asLOCATI ON.

General DB2 Setup The DB2 z/OS setup is the same for SAP NetWeaver and SAP NetWeaver MDM.

For more information on the DB2 z/OS setup, see the SAP DBA Guide for DB2 athttps://service.sap.com/instguidesnw

You must install the stored procedure DSNUTI LS according to the instructions in the SAP DBA

Guide for z/OS.

50 March 2013

Perform the BIND and GRANT Steps

For the most recent information about BIND and GRANT with MDM, see SAP Note 1119041.

BIND and GRANT without SAP NetWeaver Application Server Java (ASJava)

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 ® 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 SAPService Marketplace at:service.sap.com/swdc ® 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 Por t > - L <DDF Locat i on> - S <Dat abase Name> - H<Host Name> - U <Dat abase Connect User > - u <Admi n User > - p <Admi n Passwor d>

BIND and GRANT with SAP NetWeaver Application Server (AS Java) You do not need SAP NetWeaver AS J ava 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 thesesteps remotely for the MDM system.

For general information about the Solution Manager, see the SAP Solution Manager documentation atservice.sap.com/solutionmanager .

The procedure for performing the BIND and GRANT steps depends on the version of your SAP NetWeaverAS J ava.

Before you begin, check that the user who is installing MDM has the correct permissions toBIND and GRANT, as well as the MDM user generated during the installation process. Fordetails on permissions, see the Security Guide for DB2 for z/OS at

service.sap.com/instguides ® <SAP release> ® 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.1on an SAP Web AS ABAP 6.20 or 6.40 system, use the following procedure:

1. Apply CCMS transportSAPK640OCO. 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 remoteMDM system:

a. Database host name

b. Database port number

c. Database SSID




March 2013 51

d. 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 usedto grant the necessary privileges to the MDM connect user. Therefore, ensure that this user ID has sufficientauthorization.

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 WebAS ABAP 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 torun 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.

Create STOGROUP (optional)

When you initialize DB2 for MDM, the STOGROUP SAPMDMis created with the VCAT of STOGROUPSYSDEFLT. If you do not want this to happen, you must create the STOGROUP now.

Foreign KeysSAP MDM creates foreign keys very frequently. When a referenced table is converted, the status of thetablespace 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 thestored procedure DSNUTILS.

4.4.5 MaxDBIf you plan to host MaxDB on the same machine as MDM, install only the MaxDB server software (whichincludes a MaxDB client).

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

Due to specific database restrictions, MDM repositories can contain no more than 17 data languages whenworking 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

52 March 2013

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\ dat a

e. Edit the following independent program path:<LW>\ sapdb\ pr ogr ams

f. Install.

3. Install the MaxDB server software and create an MDM database instance using the MaxDBInstallation Manager:

a. Start SDBSETUP.

b. Start installation/upgrade.

c. Select component groups Server + 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 LOGvolume 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.

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 MDMtest environment and can be extended for productive use.

On Windows you must reboot the system after installation.

4. Optional: Install the following MaxDB administration tools (Windows only):- Database Manager for administering databases, including remote ones- SQL Studio for sending SQL statements to the database

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

6. For a productive environment, change the default value of the database parameter MaxSQLLocksfrom 50 000 to at least 650 000.

7. To mount an MDM repository residing in a MaxDB DBMS (using MDM Console), specify theinstance name and the database name of the MaxDB DBMS as the DBMS Server in the Add DBMSServer dialog.




March 2013 53

This name should be defined using MaxDB syntax i nst ancename: dbname.

When using CLIX with MaxDB, use a semi-colon (;) as the delimiter.

More Information

· Details about MaxDB installation and operations: help.sap.com →SAP NetWeaver 7.0→SAP

NetWeaver by Key Capability → Databases →MaxDB.· Frequently asked questions (FAQ) on MaxDB: SAP Note 820824



54 March 2013

5. Post-Installation To make your installed MDM system a running system, test and set up the MDM servers and the databaseconnection. You can also set up secure communication (SSL) for the MDM servers.

If you are not planning to use SSL, ensure that the following is set in the mds. i ni file:

SSL Enabl ed=Fal se

The SSL key path option should be left empty.

5.1 Starting and Stopping the MDM ServersSAPinst automatically starts the SAP system and its instances after the installation. Start and stop the MDMservers to check if the installation was successful.

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

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

· SAP Microsoft Management Console (SAP MMC)SAP MMC is the generic SAP system management tool, which is installed automatically with anySAP system on Windows platforms.

· MDM Console or MDM CLIX The MDM Console is the MDM administration Windows client for system, authorization, repositorymanagement and other administration tasks. MDM CLIX is a Windows command line tool thatprovides functions of the MDM Console.

In a heterogeneous system landscape, you can also start and stop a UNIX system with the Windows-basedSAP MMC, MDM Console, and MDM CLIX.

If you cannot start or stop the SAP system using SAP MMC and you get an UnauthorizationError , even though you made sure that you are using valid credentials, see SAP Note 927637.

5.1.1 Using SAP Microsoft Management ConsoleUse this procedure to check that you can start and stop the SAP system with the SAP MicrosoftManagement Console (SAP MMC) after the installation.

With the newly installed SAP MMC, start or stop installed SAP instances locally on the host that you arelogged on to. If the SAP MMC is configured for central system administration, you can start or stop the entiresystem from a single host.

Prerequisites

· You have logged on to the SAP system host as user <sapsi d>adm.

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

Procedure

1. Start the SAP MMC on the SAP system host by choosing Start→ All Programs→ SAPManagement Console.

2. Right-click the SAP system node and choose Start 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 optionsto start or stop your system:

March 2013 55

- 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 singleSAP MMC. For more information, see the SAP MMC system documentation.

5.1.2 Using MDM Console or MDM CLIX You can start and stop MDM server instances on all supported platforms using the following MDMadministration clients:

· The command line tool MDM CLIXCLIX is automatically installed with any MDS instance on any platform. It can be installed separatelyon Windows platforms.

· The Windows GUI client MDM Console The MDM Console must be installed separately on Windows 32bit platforms (for example on a PC).

More Information

Installing MDM CLIX and MDM Console:Section Installing MDM Windows Clients in this guide

Using MDM CLIX and MDM Console:help.sap.com/nwmdm71 ® MDM Console Reference Guide. Read the following sections:

· CLIX: MDM Server Commands

· Console: Accessing an MDM Server

5.1.3 Using ScriptsStart and stop the SAP system for MDM by running the sapcont r ol utility.

Prerequisites

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

Starting the SAP System To start all instances on an MDM system host, enter the following command:

sapcont r ol –nr - f unct i on St art Syst em

Where is the number of one of the MDM server instances of the SAP system youwant to start.

You can start the MDM server instances separately by entering the following command:

sapcont r ol –nr - f unct i on St artWhere is the number of the MDM server instance you want to start.

Stopping the SAP System To stop all instances on an MDM system host, enter the following command:

sapcont r ol –nr - f unct i on St opSyst em

Where is the number of one of the MDM server instances of the SAP system youwant to stop.

You can stop the MDM server instances separately by entering the following command:

sapcont r ol –nr - f unct i on St op

56 March 2013

is the number of the MDM server instance you want to stop.

Make sure that you always stop the MDS instance first.

5.2 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.

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

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

are created in the config directory of the instances:- mds. i ni- mdm_l i st . i ni- mdi s. i ni- mdss. i ni- mdl s. i ni

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 athelp.sap.com/nwmdm71 :

· mds. i ni and mdm_l i st . i ni :MDM Console Reference Guide, section MDS Configuration

· mdi s. i ni :MDM Console Reference Guide, section MDIS Configuration

· mdss. i ni :MDM Console Reference Guide, section MDSS Configuration

5.2.2 Mounting MDS and Connecting the Database To check if MDM and the database are installed and configured correctly, you start the MDM Console, mountthe MDS and connect to the database.

For more information, see help.sap.com/nwmdm71 ®MDM Console Reference Guide, section MDM

Server Administration.

5.2.3 Setting MDS and Repository AuthenticationsBy 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 forthe predefined users, especially for the Administrator user.

Statring in MDM 7.1 SP08, the default password for the Administrator user is sapmdm , and can nolonger be empty.

For more information, see help.sap.com/nwmdm71 ®MDM Console Reference Guide, section MDM

System Administration.




March 2013 57

5.3 Setting Up SSL Communication for MDMServersStarting from version 7.1 SP07, you can set up SSL (Secure Sockets Layer) communication during aninstallation or update of MDS, as described in the following sections.

5.3.1 Setting Up SSL During an Installation or an Updateof MDSPrerequisites

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

Procedure

In the Install 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.

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

When you update MDM servers, set this parameter manually in the ini files, as described in SAPNote 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. Choose Next.

5. In theSAP 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 toSAPCRYPTO.SAR field.

For information about downloading the SAPCRYPTOlibrary, see SAP Note 397175.

5.3.2 Post Installation/Update TasksAfter the installation or update is complete, the following files are created in the exe folder of the global host:

File Description Comments

cl i ent . pse Client key of the SSL communication. The MDM clientswill need this file to connect to the MDM servers.

SAPSSLS. pse Server key of the SSL communication. The MDM serverswill need this file.

Copied also to the secfolder of the MDM servers.

cert . cr t Certificate files that are used to connect the MDM serverto the WAS (Web Application Server) in secure mode.

cr ed_v2 For internal use.

t i cket For internal use. Copied also to the sec

folder of the MDM servers





58 March 2013

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

To verify that SSL is set up correctly, perform the following tasks:

Verify that the framework is set to secure HTTPS mode:

For every server instance (MDS, MDIS MDSS), perform the following:

1. Log in to the MDM server using the <SI D>admaccount.

2. In the command line, type the following command:

sapcontrol.exe -nr <NR> -function GetAccessPointList

3. 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.

Verify SSL settings in the mdm ini files:

In the MDM ini files (mds. i ni , mdi s. i ni , mdss. i ni ), verify that the following parameters are set:

· Li st eni ng Mode=Bot h or SSL

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

· SSL Li b Pat h= [ Path to the servers’ sapcr ypt o library; must be located in the servers’ exefolder]

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

Sett ing MDIS and MDSS to work as cl ients:

To enable the MDM Import Server and MDM Syndication Server to work as clients with the MDM servers,you must set the following paramers manually after an MDS installation or update:

· Ser vi ce Cont r ol Secur i t y Enabl ed=True

Default is Tr ue.

· SSL Enabl ed=Tr ue

Default is Fal se.

· SSL Key pat h=[Path to the client key file cl i ent . pse, located in the exe folder of the globalhost]

March 2013 59

6. Additional Information This chapter provides additional useful information about SAP System Security on Windows, uninstallingMDM servers and Windows clients, and updating an MDM installation (for example, implementing a patch).

6.1 SAP System SecurityIn a central SAP system installation, SAPinst automatically performs all steps relevant for security. AlthoughSAPinst makes sure that the system is protected against unauthorized access, you must still check that nosecurity breaches can occur.

For central and straightforward administration of the SAP system, you must install distributed SAP systemswith multiple application servers in a Windows domain. This section describes the user accounts and groupsthat SAPinst creates during a domain installation and shows how these are related to the SAP directories.

6.1.1 User AccountsSAPinst creates the following accounts for SAP system administration:

· <sapsi d>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 Admi ni st r at or s group.

· SAPSer vi ce<SAPSI D> This is the user account that is required to start the SAP system. It has the local user right to log onas a service.

The advantage of the additional SAPServi ce<SAPSI D>account is that it does not allow aninteractive logon, which prevents abuse of the account. Therefore, you do not need to set anexpiration date for the password and you do not need to set the option user must change passwordat next logon.

6.1.2 GroupsSAPinst creates the following groups during a domain installation:

· SAP_<SAPSI D>_Gl obal Admi n This global group is a domain-level SAP administration group for organizing SAP systemadministrators.

The only function of a global group is to group users at the domain level so that they can be placedin the appropriate local groups.

· SAP_<SAPSI D>_Local Admi nOnly 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 fromthis domain.

6.1.3 SAP DirectoriesSAPinst protects the SAP directories under \ usr \ sap\ <SAPSI D>by only granting the groupSAP_<SAPSI D>_Local Admi n full control over these directories.

An access control list (ACL) controls access to SAP system objects. For maximum securityin the SAP system, only the following are members of all SAP system object ACLs:- Local group SAP_<SAPSI D>_Local Admi n

- Group Admi ni st r at or s- Account SYSTEM




60 March 2013

6.2 Updating MDM Servers This section describes how to update MDM servers with the Update option of SAPinst, for example toimplement support packages or patches.

The Update option allows you to update the complete SAP system from one host, even if the system wasinstalled on several hosts (distributed system). For performance reasons you should run the update on thehost where you installed the first MDM instance.

When updating single instances, be aware that updates can only be installed based on MDMserver types and host types. For example, if you choose to update one MDS instancerunning on a Windows x86_64 host, all other MDS instances of this SAP system running onother Windows x86_64 hosts are updated as well.

For more information about upgrading your MDM installation, see help.sap.com/nwmdm71 >MDM 7.1

Upgrade Guide.

Prerequisites

· This description assumes that you installed your SAP system with standard SAP tools according tothe installation documentation.

· You are logged on as an administration user.

· You know how to start SAPinst.More information: Section Running SAPinst

Procedure

1. Start SAPinst and on the Welcome screen, choose Additional Software Lifecycle Options® UpdateMDM.

2. Follow the instructions in the SAPinst input dialogs.

6.3 Maintaining Multiple MDM Servers on a Host You can install multiple instances of MDM Servers (including MDS, MDSS, MDIS, and MDLS) on a singlehost. The instances of MDM Servers can be from different versions of MDM (such as 5.5 and 7.1), whichmay be useful when upgrading from one MDM version to another, or multiple instances of MDM 7.1 SP04and above. For more information about a MDM 5.5 and MDM 7.1 side-by-side scenario for upgradepurposes, see help.sap.com/nwmdm71 >MDM 7.1 - Upgrade Guide

§

When installing multiple instances of MDM 7.1 Master Data Server on the same host,and each instance has a different MDM version, each MDM 7.1 instance must have aunique SAP System ID (SID).

§ When installing multiple instances of Master Data Server on the same host, and eachinstance has the same MDM version, they can all have the same SAP System ID (SID).

§ Starting from MDM 7.1 SP06, running multiple instances of Master Data Server, at thesame time, on the same host, is supported.

§ To start and stop the MDM servers on hosts with multiple MDM 7.1 Server instances, usethe SAP Microsoft Management Console (SAP MMC), SAP Management Console (SAPMC), 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.




March 2013 61

6.3.1 Installing Different Versions 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 tothe 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 DataServer.

· MDM clients connecting to a Master Data Server on a host where multiple instances of Master DataServers are maintained must provide the port number of the Master Data Server they want to connect to.

6.3.2 Running Multiple MDM Server Components on aSingle MachineStarting 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 loadingmultiple MDM repositories on a single Master Data Server (MDS) are:

· 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 towork 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 asecond machine, and a DBMS on a third machine.

· Multiple Master Data Servers and MDM Import/Syndication Servers on one machine with a remoteDBMS 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 aforementionedconfiguration options; therefore the configuring option you choose should be based solely on your preferredhardware setup.

6.3.3 Unarchiving and Updating MDM RepositoriesAll MDM repositories used with a Master Data Server must be from the same version as that Master DataServer. To avoid data problems due to schema differences among MDM versions, repositories should onlybe unarchived and updated from earlier to later versions—never the opposite.

6.4 Uninstalling MDM ServersMDM has been installed as an SAP system and the MDM servers (MDS, MDIS, MDSS, MDLS) have beeninstalled as instances of this SAP system.

This section describes how to uninstall MDM servers by deleting a single instance or a complete SAP systemwith the Uninstall option of SAPinst.

Make sure that you stop, archive, and store the MDM repositories that you want to reuse. In theSAPinst un-installation procedure, keep the Archive folder and other folders (see below).

You cannot delete an SAP system remotely.

62 March 2013

If you delete network-wide users, groups or service entries in an environment with NetworkInformation System (NIS), other SAP installations might also be affected. Make sure that theusers, groups, and service entries to be deleted are no longer required.

Prerequisites

·

It is assumed that you have installed your SAP system with standard SAP tools according to theinstallation documentation.

· You are logged on with a user account that has the required authorization to run the SAPinst tooland the SAP system.

· You know how to start SAPinst.For more information, see section Running SAPinst.

Procedure

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 distributedsystems:

· 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 thehosts belonging to the SAP system.

SAPinst only stops local instances automatically.

SAPinst asks you if you want to keep the MDM-specific folders and files located under/ usr / sap/ <SAPSI D>for reuse. You can keep the following:

· Configuration files (. i ni )

· Log files

· Archives (MDS only)

· Distribution files (MDS only)

· Reports (MDS only)

6.5 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 Windowsclients:- To remove a single client, open a Windows Command Prompt and launch the installationexecutable passing the parameter / su ( for example enter MDMSer ver I nst al l . 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 harddisk.




March 2013 63

©2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated inthe United States and other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode aretrademarks or registered trademarks of Apple Inc.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems Inc.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company.

Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater,Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android aretrademarks or registered trademarks of Google Inc.

HP is a registered trademark of the Hewlett-Packard Development Company L.P .

HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for Informatics and Mathematics (ERCIM), or Keio University.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS,OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale,PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

IOS is a registered trademark of Cisco Systems Inc.

The Klout name and logos are trademarks of Klout Inc.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.

OpenText is a registered trademark of OpenText Corporation.

Oracle and J ava are registered trademarks of Oracle and its affiliates.

QR Code is a registered trademark of Denso Wave Incorporated.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2,BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

SAVO is a registered trademark of The Savo Group Ltd.

The Skype name is a trademark of Skype or related entities.

Twitter and Tweet are trademarks or registered trademarks of Twitter.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

SAP, R/3, ABAP, BAP I, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, theBusiness Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server,Adaptive Server Enterprise, iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic EDDY,Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It's

time to love work again, SuccessFactors J am and BadAss SaaS, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.




64 March 2013

Disclaimer and Legal Information

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAPGroup”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an

additional warranty. SAP does not warrant that this document is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED,OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Java™ Source CodeSome components of this product are based on J ava™. Any code change in these components may cause unpredictable and severemalfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any J ava™ Source Code deliveredwith this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Coding SamplesAny software coding and/or code lines/strings (“code”) included in this documentation are only examples and are not intended to beused in a productive system environment. The code is only intended better explain and visualize the syntax and phrasing rules of certaincoding. SAP does not warrant the correctness and completeness of the code given herein, and SAP shall not be liable for errors ordamages caused by the usage of the code, except if such damages were caused by SAP intentionally or grossly negligent.

Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint where to findsupplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or theability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless suchdamages have been caused by SAP’s gross negligence or willful misconduct.

Accessibi lity The information contained in this documentation represents SAP’s current view of accessibility criteria as of the date of publication; it isin no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liabilitywith respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document. This document is for internal use only and may not be circulated or distributed outside your organization without SAP’s prior writtenauthorization.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with “you”, or agender-neutral noun (such as “sales person” or “working days”) is used. If when referring to members of both sexes, however, the thirdperson singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of thenoun and pronoun. This is to ensure that the documentation remains comprehensible.




March 2013 65

Legal Software Terms

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party products thefollowing special terms and conditions shall apply.

· This software was developed using ANTLR.

·

SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++library(STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual propertylaws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties orrestrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentationunchanged: Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:

· The conditions indicated in the above permissions notice are met;

· The following copyright notices are retained when present, and conditions provided in accompanying permissionnotices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology .Copyright 1999,2000 Boris Fomi tchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is herebygranted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice andthis permission notice appear in supporting documentation. Hewlett-P ackard Company makes no representations aboutthe suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is herebygranted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice andthis permission notice appear in supporting documentation. Silicon Graphics makes no representations about thesuitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is herebygranted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice andthis permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations aboutthe suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided"as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy thissoftware for any purpose is hereby granted without fee, provided the above notices are retained on all copies.Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and anotice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby

granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice andthis permission notice appear in supporting documentation. SAP makes no representations about the suitability of thissoftware for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreementdistributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referringto its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be notincluded.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions andshall be subject to a separate contract.




c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport iserror-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be

compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based onthe failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on theextent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstancesknown to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect orlost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backupcopies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery,notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing thisobligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees oragents of SAP.

· Adobe Docu ment Serv icesAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe documentservices and Adobe LiveCycle Designer, see SAP Note 854621.




mdm instalacion

Documents

mdm collaborativeprocesses

mdm server naming mdm

mdm import server

multiple mdm servers

mdm web dynpro

multiple mdm server

additional mdm components

mdm component overview