mdm installation guide

Installation Guide

SAP NetWeaver® Master Data Management 7.1 on UNIX

Document Version 5.0 – October, 2011

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

MDM 7.1 Installation Guide (UNIX)

October 2011 3

Document History Document Version

Description of Change

5.0 / Oct 2011 Guide updated for MDM 7.1 SP08.

The default password for the Administrator user is now sapmdm, and can no longer be empty. For more information, see 5.3 Setting Up MDM Servers on page 66.

4.9 / May 2011 Guide updated for MDM 7.1 SP07.

SSL Support:

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

o For information about setting up SSL, see 5.4 Setting Up SSL Communication for MDM Servers on page 67.

4.7 /Jan 2011 Guide updated for MDM 7.1 SP06.

Starting from MDM 7.1 SP06, running multiple instances on a single machine is supported. For more information, see 7. Maintaining Multiple MDM Servers on a Host on page 70.

Addition regarding IBM i 6.1 OS. For more information, see 7. Maintaining Multiple MDM Servers on a Host on page 70.

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

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

Update regarding installating the Oracle Database. For more information, see Install Oracle and Create a Database Instance on page 43.

Update regarding the value of file descriptors on the MDM server. For more information, see Software Requirements on page 10.

Terminology updates relating to MDM server naming. For example, MDM Server was changed to Master Data Server, MDM Import Server was changed to Master Data Import Server.

4.4 In Requirements for UNIX on page 10, the minimum version of the IBM C++ Runtime Environment Components for AIX libraries was changed from 10.1 to 10.1.0.3.

4.3 In 4.1.8 Troubleshooting with SAPinst section on page 41, added information about installation error on Solaris, including references to SAP Notes 1249364 and 966416.

Section 7. Maintaining Multiple MDM Servers on a Host on page 70 was rewritten to resolve ambiguities regarding the installation of multiple Master Data Server instances on the same host.

Links to installation processes have been provided for two additional MDM Components: MDM Web Dynpro and MDM Collaborative Processes for Material.

For more information, see Installing Additional MDM Components on page 58.

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

4.1 Document History section added

Step 6 in 4.2.4 MaxDB on page 55: When mounting an MDM repository residing in a MaxDB DBMS (using MDM Console), you specify the instance name (and database name), not the hostname (and database name) of the MaxDB DBMS.


4 October 2011

Table of Contents

Installation Guide – MDM 7.1 on UNIX .......................................................... 5 1. Introduction ..................................................................................................... 5 2. Planning ........................................................................................................... 7 3. Preparation ...................................................................................................... 9

3.1 Hardware and Software Requirements ............................................................. 9 3.2 Basic SAP System Parameters ....................................................................... 11 3.3 Users and Groups ............................................................................................ 15

3.3.1 Creating AIX Groups and Users (Optional) .....................................................................16 3.3.2 Creating Linux Groups and Users (Optional) ..................................................................17 3.3.3 Creating HP-UX Groups and Users (Optional) ................................................................18 3.3.4 Creating Solaris Groups and Users (Optional) ................................................................18

3.4 File Systems and Raw Devices ....................................................................... 19 3.4.1 SAP Directories .............................................................................................................19 3.4.2 Exporting and Mounting Global Directories .....................................................................21 3.4.3 Exporting and Mounting Directories via NFS for AIX (Optional).......................................21 3.4.4 Exporting and Mounting Directories via NFS for HP-UX (Optional) .................................22 3.4.5 Exporting and Mounting Directories via NFS for Linux (Optional) ....................................24 3.4.6 Exporting and Mounting Directories via NFS for Solaris (Optional)..................................25

3.5 Preparing the Installation Files ....................................................................... 26 4. Installation ..................................................................................................... 29

4.1 Installing MDM Servers .................................................................................... 29 4.1.1 Running SAPinst ............................................................................................................29 4.1.2 SAPinst Installation Options ...........................................................................................35 4.1.3 Interrupted Installation with SAPinst ...............................................................................36 4.1.4 Performing a Remote Installation with SAPinst (Optional) ...............................................37 4.1.5 Starting SAPinst GUI Separately (Optional) ....................................................................38 4.1.6 Silent Installation with SAPinst (Optional) .......................................................................40 4.1.7 Entries in the Services File Created by SAPinst .............................................................40 4.1.8 Troubleshooting with SAPinst.........................................................................................41

4.2 Installing and Configuring the Database ........................................................ 42 4.2.1 Oracle DBMS .................................................................................................................43 4.2.2 IBM DB2 for Linux, UNIX and Windows ..........................................................................50 4.2.3 IBM DB2 for z/OS ..........................................................................................................50 4.2.4 MaxDB ..........................................................................................................................55

4.3 Installing Additional MDM Components ......................................................... 57 5. Post-Installation ............................................................................................ 59

5.1 Environment Variables for MDS ...................................................................... 59 5.2 Starting and Stopping the MDM Servers ........................................................ 61

5.2.1 Using SAP Microsoft Management Console ...................................................................61 5.2.2 Using SAP Management Console ..................................................................................62 5.2.3 Using Scripts .................................................................................................................64 5.1.4 Using MDM Console or MDM CLIX ................................................................................65

5.3 Setting Up MDM Servers .................................................................................. 66 5.4 Setting Up SSL Communication for MDM Servers ........................................ 67

6. Updating MDM Servers ................................................................................ 69 7. Maintaining Multiple MDM Servers on a Host ............................................ 70 8. Uninstalling MDM Servers ........................................................................... 71


October 2011 5

Installation Guide – MDM 7.1 on UNIX

1. Introduction This installation guide describes all steps that are necessary to install the SAP NetWeaver Master Data Management (MDM) 7.1 server components on released UNIX platforms.

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

The installation procedure for MDM 7.1 differs significantly from the installation procedure for MDM 5.5. The MDM servers are installed as SAP systems using the SAPinst installation tool and SAP Instance Framework. The installation procedure for the MDM Windows clients and additional components has not changed. For more information about MDM client installation, see service.sap.com/installMDM71 MDM – Installation Guide on Windows.

The following MDM servers are the foundation of the MDM software. These components can be installed on supported UNIX platforms using SAPinst:

Master Data Server (MDS)

Master Data Import Server (MDIS)

Master Data Syndication Server (MDSS)

The main target groups of this guide are:

System administrators

Technology consultants


6 October 2011

Required Documentation The following sections list the documentation needed for the installation:

SAP Installation Notes

Information on SAP Service Marketplace

SAP Installation Notes It is essential that you read the following SAP Notes before starting the installation. These SAP Notes contain the most recent information about the installation as well as corrections to the installation documentation.

Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at service.sap.com/notes.

SAP Note Number

Title Description

1249503 MDM Installation Note

Most recent information and best practices about the MDM installation procedure. The MDM Installation Note complements this MDM Installation Guide.

1487853 SAP NetWeaver MDM 7.1 SP07 Release

This note contains information about the current MDM 7.1 support package.

1244358 MDM 7.1 Release Restriction Note

This note contains the restrictions of the current MDM 7.1 support package.

Information on SAP Service Marketplace Information about the following areas is available on SAP Service Marketplace:

Description Internet Address

SAP NetWeaver MDM 7.1: Documentation Center – an easy to use page that provides useful information and access to the complete MDM documentation set

service.sap.com/installMDM71

Released platforms service.sap.com/platforms

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

service.sap.com/ti

Network infrastructure service.sap.com/network

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




October 2011 7

2. Planning When planning the MDM system landscape, familiarize yourself with the following documentation at service.sap.com/installMDM71:

MDM Master Guide

MDM Sizing Guide

Introduction for this guide

Get informed about the supported platforms and databases. You can find the MDM 7.1 Product Availability Matrix (PAM) at service.sap.com/pam (search for “MDM 7.1”).

If you are planning an MDM upgrade installation (for example from release 5.5 to release 7.1), read the following guide first: service.sap.com/installMDM71 Upgrade Guide

If you are planning an MDM update installation (for example implementing MDM 7.1 patches), run SAPinst with the software lifecycle option Update MDM. For more information, see the following sections in this guide:

SAPinst Installation Options

Updating MDM Servers

Implementation Considerations An MDM system landscape is typically structured as follows:

One separate UNIX host or Windows server host with the MDM servers and the database (standard system). You can distribute the different MDM servers to several hosts (distributed system).

Several different Windows machines with multiple combinations of MDM clients for administrators, master data specialists, and end users.

More than one installation of additional MDM components for developers or portal administrators, for example on Web or SOAP servers.

If you want to install the MDM 7.1 as part of the implementation of an SAP NetWeaver scenario, it is essential that you familiarize yourself with the contents of the corresponding master guide before starting the installation.

The master guide is the central document for the implementation of SAP NetWeaver solutions and scenarios. It lists the components and third-party applications required for each scenario in an SAP NetWeaver solution, and refers to the required installation and upgrade guides. It also defines the installation sequence for the scenarios of the corresponding SAP NetWeaver solution.

You can find the MDM Master Guide and all other MDM documentation on the SAP Service Marketplace at service.sap.com/installMDM71.


8 October 2011

Central and Distributed Installation Before you install the MDM servers on UNIX, you have to decide whether you want to perform a central (on one host) or distributed installation (on different hosts), since this affects how the user account information is stored and accessed.

Distributed Installation

In a distributed installation the MDM servers are stored on several hosts. In this case we highly recommend that you store the UNIX account information in a central database like NIS or Yellow Pages.

For more information, see the Users and Groups section.

Central Installation

In a central installation, all UNIX account information is stored locally on one host and is not visible to any other hosts in the system.

If the MDM servers and the database are to run on a single machine, you can perform a central installation.

High Availability High availability (HA) is a major issue when constructing business systems in order to improve system reliability. For MDM, there are different approaches that support this objective, for example system redundancy using load and balancing tools, backup strategies and cluster management software.

If you plan to set up MDM in a landscape that grants high availability, read the following documentation first: service.sap.com/installMDM71 MDM 7.1 - Solution Operation Guide 5 High Availability

Multiple Components on One Database MDS can be installed in an MCOD environment, sharing the same database with other SAP components, such as SAP ERP ECC or SAP NetWeaver Application Server.

Generally, if several components share the same database resources this affects overall performance; this must be taken into consideration when sizing the hardware and system.

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

For MCOD on an Oracle database you need to check and adjust the temporary tablespace after MDM installation. For more information, see the Adjust Temporary Tablespace for MCOD section in this guide.

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

If you plan to use LDAP with MDM, familiarize yourself with the following documentation: service.sap.com/installMDM71 MDM Console Reference Guide, section LDAP Support.

From MDM 7.1 SP06 and higher, to use LDAP authentication for MDM users on HP-UX 11.31, you must have Mozilla LDAP C SDK 5.17 installed. For support, contact your Hewlett-Packard (HP) vendor.


October 2011 9

3. Preparation To prepare for an MDM installation you need to learn about SAP systems and make some checks and settings on your UNIX platform.

This chapter is structured as follows:

Hardware and Software Requirements Lists the requirements for running SAPinst and MDM servers.

Basic SAP System Parameters Gives you an overview of the basic parameters that make up an SAP system, like system IDs, users, and so on.

Users and Groups Explains how to create users and groups manually if you do not want SAPinst to create users and groups automatically during the installation run.

File Systems and Raw Devices Lists the directories SAPinst will create for MDM servers and explains how to export and mount global directories for a distributed installation.

Preparing the Installation Files Explains how to retrieve the installation files from the DVD or SAP Service Marketplace and how to compose installation packages for the various installation options.

3.1 Hardware and Software Requirements You check that your hosts meet the hardware and software requirements for your operating system (OS), the SAP system for MDM, and the MDM server instances.

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

Prerequisites Contact your OS vendor for the latest OS patches.

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

If you want to monitor MDM using the SAP Solution Manager make sure that the MDM host name also meets the requirements listed in SAP Note 1278029.

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

service.sap.com/pam SAP NETWEAVER SAP MDM for supported operating system releases.

2. Check the Requirements for UNIX section below.




10 October 2011

3. If you are installing a production system, the values provided by the Prerequisite Checker and the Requirements for UNIX section are not sufficient. In addition, do the following:

a. Read the MDM Sizing Guide available at http://service.sap.com/installMDM71 MDM 7.1 - Sizing Guide.

b. Contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on parameters such as: - How intensively the applications are to be used - The number of users - Data model of your MDM repositories - Number of records in the MDM repositories - Number of large binary objects (for example images and PDFs) in the repositories

Requirements for UNIX This section lists the minimum hardware and software requirements for installing and running MDM servers on released UNIX platforms. A production system must meet the minimum requirements listed in the tables below.

For more information about how to check the requirements see, the OS documentation.

Hardware Requirements Requirement Type Requirement

Minimum disk space SAP system files: 2 GB

Temporary disk space for the installation: 1 GB

Minimum RAM 5 GB

Minimum swap space 1 times RAM plus 10 GB

Software Requirements Requirement Type Requirement

UNIX operating systems for MDM servers

English international 64-bit versions of the released UNIX platforms.

MDM on AIX requires AIX service pack 5.3.0.50, which can be downloaded from the IBM Web site. Also, MDM requires the IBM C++ Runtime Environment Components for AIX version 10.1.0.3 or higher contained in the Runtime package. This package can be found at: http://www-306.ibm.com/software/awdtools/xlcpp/

Starting from MDM 7.1 SP06, the C++ runtime libraries on AIX are checked during an installation or update of the AIX server. For more information on the correct runtime libraries, see SAP Note 1430477.

Network File System (NFS)

If MDM servers are installed decentrally, Network File System (NFS) must be installed.

TCP/IP access MDIS and MDSS must have TCP/IP access to the MDS. This connection must be on a local network to be effective.

Starting from MDM 7.1 SP07, each MDM instance can use either regular TCP/IP ports, or SSL TCP/IP ports for secure communication (if this was configured).

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

Check the setup of your network, operating system, and firewalls, if the MDM servers can be accessed through their dedicated TCP/IP ports.

You set the ports during the installation.

The regular TCP/IP ports are:

http://www-306.ibm.com/software/awdtools/xlcpp/



October 2011 11

MDS: Port 59950 and three sequential ports from the range 2000 - 9999 for every loaded repository (the repository ports are configurable using the MDM Console).

MDIS: Port 59750

MDSS: Port 59850

MDLS: Port 59650

The SSL TCP/IP ports, starting from MDM 7.1 SP07, are:

MDS: Port 59951 and three sequential ports in the range 2000 - 9999 for every loaded repository. You can configure the repository ports using the MDM Console.

MDIS: Port 59751

MDSS: Port 59851

MDLS: Port 59651

If you already have an MDM Server installed on your machine and you install an additional instance of MDS, MDIS, MDSS, and/or MDLS, the default TCP/IP ports will be created in the following format, where xx is the instance number:

5xx50 for the regular TCP/IP ports

5xx51 for the SSL TCP/IP ports

Value of file descriptors on the MDM server

Use the ulimit command to verify that the value of the file descriptors' kernel parameter is set correctly on the MDM server. For more information, see SAP note 1522123.

3.2 Basic SAP System Parameters SAPinst will ask whether you want to run the installation in Typical or Custom mode. If you choose Typical, SAPinst provides automatic default settings and you only have to respond to a minimum number of prompts. However, you can still change any of the default settings on the parameter summary screen.

The tables below list the basic system parameters that you always need to specify before installing your SAP system, both in typical and in custom mode.

Parameter Description

SAP System ID <SAPSID>

The SAP system ID <SAPSID> identifies the entire SAP system. SAPinst prompts you for the <SAPSID> when you execute the first installation option to install a new SAP system.

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

Choose your SAP system ID carefully. Renaming is difficult and requires you to reinstall the SAP system.

Make sure that your SAP system ID:

Is unique throughout your organization

Consists of exactly three alphanumeric characters

Contains only uppercase letters

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1522123


12 October 2011

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 GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR

SAP System Profile Directory /<sapmnt>/<SAPSID>/profile

or

/usr/sap/<SAPSID>/SYS/profile

The installation retrieves the parameters entered earlier from the SAP system profile directory.

SAPinst prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation.

See also the description of the parameter <SAPSID>.

/usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/<SAPSID>/profile.


October 2011 13


Instance Number of the SAP System

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

The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers.

The instance number is used to specify the names of the SAP system instance directories that SAP automatically creates during the installation. For example, the directory of the MDS is called MDS<Instance_Number>.

HP-UX

Do not use 75 for the instance number because this number is already used by the operating system. For more information, see SAP Note 29972.

Virtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape in order to conceal their physical network identities from each other.

This may be useful when moving SAP servers or complete server landscapes to other new hardware within a short time frame without having to carry out a reinstallation or complicated reconfiguration.

If you want to use virtual host names for the installation, you have to specify the virtual host name before you start SAPinst.

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

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

SAP system mount directory

The SAP system mount directory /<sapmnt> is the base directory for the SAP system.

For /<sapmnt> you can use a directory of your choice. If you do not specify a directory, SAPinst creates a directory named sapmnt by default.

Do not add <SAPSID> as subdirectory because the installer adds this directory automatically.

Example

If you enter /sapmount for /<sapmnt> and MDM for <SAPSID> during the input phase of the installation, the installer creates the directory /sapmount/MDM.

For more information, see the File Systems and Raw Devices section.





14 October 2011


Master Password This password is used for all new user accounts SAPinst creates. The length has to be 8 to 14 characters.

Depending on your installation scenario there might be more restrictions.

If you do not create the operating system users manually, SAPinst creates them with the common master password. In this case, make sure that the master password meets the requirements of your operating system.

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

If you did not create user <sapsid>adm manually before the installation, SAPinst creates it automatically during the installation. SAPinst sets the master password by default, but you can overwrite it either by choosing parameter mode Custom 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 sapadm is used for central monitoring services.

The same notes apply as for user <sapsid>adm.

Password of User <sapsid>adm

SAPinst processes the passwords of the operating system user as follows:

If the operating system user does not exist, SAP creates the user <sapsid>adm. This user is the SAP system administrator user and is a member of the local Administrators group.

If the operating system user already exists, SAPinst prompts you for the existing password, unless the password of this user is the same as the master password.

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

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

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

Port Number of the MDM server

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

Starting from 7.1 SP4, this parameter is configurable during the MDM installation.

We recommend that you use ports higher than 49151. The ports between 0 and 1023 might be used by the operating system and the application may not function correctly. The ports between 1024 and 49151 might be registered for and used by other applications. Check the Internet Assigned Numbers Authority (IANA) registrations with your network administrator.


October 2011 15

3.3 Users and Groups During the installation, SAPinst checks all required accounts (users, groups) and services on the local machine. SAPinst checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.

If you do not want SAPinst to create operating systems users, groups, and services automatically, you have the option of creating them before the installation. This might be the case if you use central user management such as Network Information System (NIS).

SAPinst checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly. SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does not change NIS configurations.

For a distributed system, we recommend that you distribute account information (operating system users and groups) over the network, for example by using NIS.

All SAP system users must have identical environment settings. If you change the environment delivered by SAP, such as variables, paths, and so on, we do not assume responsibility.

If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways:

Start SAPinst and choose Software Life-Cycle Tasks Additional Preparation Tasks Operating System Users and Groups. For more information, see the Running SAPinst section.

Create operating system users and groups manually as described in the Creating <UNIX OS> Groups and Users (Optional) sections below.

Operating System Users and Groups SAPinst chooses available operating system user IDs and group IDs unless you are installing an additional MDM server instance (for example MDIS). On an additional MDS instance you have to enter the same IDs as on the host of the primary MDS instance.

Do not delete any shell initialization scripts in the home directory of the OS users. This applies even if you do not intend to use the shells that these scripts are for. The user ID (UID) and group ID (GID) of each operating system user and group must be identical for all servers belonging to the same SAP system. This does not mean that all users and groups have to be installed on all SAP servers.


16 October 2011

Users and Groups of the SAP System User Primary Group Additional Group Description Login Shell root - sapinst UNIX superuser -

<sapsid>adm sapsys sapinst SAP system administrator

Bourne-compatible shell (/bin/sh)*

sapadm sapsys sapinst Host Agent administrator

Bourne-compatible shell (/bin/sh)*

* Usually SAP systems use the C shell (csh) as the login shell for the system users. However, for running MDM a Bourne-compatible shell (/bin/sh) is mandatory. The SAPinst installation master for MDM creates the user accounts using Bourne shell. If you create these users by yourself, you must also use Bourne shell. For general information about possible login shells in an SAP system, see SAP Note 202227.

If these operating system users already exist, make sure that they are assigned to group sapinst.

If you install a distributed system and you use local operating system user accounts instead of central user management (for example, NIS), user <sapsid>adm and sapadm must have the same password on all hosts.

3.3.1 Creating AIX Groups and Users (Optional) Creating AIX Groups and Users To create AIX groups and users, use the System Management Interface Tool (SMIT):

1. Create groups as follows: a. Enter the command smitty. b. Choose Security and Users Groups Add a group.

c. Enter a group name for example, sapsys and set administration group to true. d. Press F3 until the Security & Users menu appears.

2. To create users, proceed as follows: a. Enter a user name, for example <sapsid>adm. b. Enter all required values.

3. Set the initial password using the following command: passwd <user> Example: passwd <sapsid>adm

Checking Created Users As user root check all existing users as follows:

1. Enter the command smitty.

2. Choose Security & Users Users Change/Show Characteristics of a User.

3. To get a list of users, choose F4.

4. For user root and each created user <user> perform the following steps: a. Select <user>. b. Change field Soft CPU time to -1 (this is the default value).



October 2011 17

c. Change field Soft CORE file size to –1 (this is the default value). d. Change field Soft FILE size to —1.

For more information, see SAP Note 628131.

e. Change field Soft DATA segment to -1. f. Change field Soft STACK size to -1.

You must make sure that the system-wide default HARD values are not explicitly defined to be lower than the values given above. Check the file /etc/security/limits under the default: stanza. If they are not explicitly set, the values are as shown in the table at the top of the file.

Checking the Operating System 1. Enter the command smitty.

2. Choose System Environments Change/Show Characteristics of Operating System.

3. Change Maximum number of PROCESSES allowed per user to 500.

4. To exit SMIT, choose F10.

3.3.2 Creating Linux Groups and Users (Optional) You can manage Linux users with one of the following graphical tools:

Red Hat Linux: RHEL5 and higher: system-config-users

SUSE Linux: SLES10 and higher: yast or yast2

Task Command

Creating groups groupadd

Modifying groups groupmod

Deleting groups groupdel

Creating users useradd

Modifying users usermod



18 October 2011

3.3.3 Creating HP-UX Groups and Users (Optional) Here you can find information about how to create operating system users and groups on HP-UX.

To prevent terminal query errors in the <sapsid>adm environment, change the shell template as follows: 1. Edit /etc/skel/.login. 2. Comment out (with #) the following line: #eval ‘tset -s -Q -m ’:?hp’ For more information, see SAP Note 1038842.

Procedure 1. Enter one of the following commands:

/usr/sbin/smh or http://<hostname>:<port> where <port> is either the default port 2381 or your defined port (for example 2301)

2. Choose Accounts for Users and Groups Local Users Add User Account.

3. Enter the required users.

4. Choose Accounts for Users and Groups Groups Add new Group.

5. Enter the required groups.

6. Exit SMH.

7. Verify that the TZ settings in the following are consistent: /etc/TIMEZONE /etc/profile /etc/csh.login

3.3.4 Creating Solaris Groups and Users (Optional) You can create groups and users manually by using the shell commands useradd and groupadd. If you run a graphical user interface (GUI), you can use Solaris Management Console smc.

Procedure Using useradd and groupadd:

1. To add new groups and users, use the commands groupadd and useradd as follows: groupadd <new group> useradd –g <login group> -d <homedirectory> \ -s <login shell> <new user>

2. Check the following values for the users by executing command ulimit -a in sh or bash:

Output Properties time(seconds) unlimited

file(blocks) unlimited

data(kbytes) unlimited

stack(kbytes) unlimited

coredump(blocks) unlimited

nofiles(descriptors) 8192



October 2011 19

3. If your parameter settings differ from the settings above, change these values accordingly.

Example

If you have to change the value for descriptors to 8192, proceed as follows: 1. Add the following line to the .cshrc file after the line containing the character string Sun*: limit descriptors 8192 2. Add the following line to the .profile file after the line containing Sun*): ulimit -n 8192

3.4 File Systems and Raw Devices The following sections describe the directory structures for the SAP system, how to set up SAP file systems for the SAP system and, if required, raw devices on operating system level.

The installation of any SAP system does not require a special file system setup or separate partitions.

3.4.1 SAP Directories Here we describe the directories of a typical SAP system.

SAPinst creates the following types of directories:

Physically shared directories, which reside on the global host and are shared by Network File System (NFS)

Logically shared directories, which reside on the local host(s) with symbolic links to the global host

Local directories, which reside on the local host(s)

Physically Shared Directories SAPinst creates the following directories:

The directory /<sapmnt>/<SAPSID> is created on the first installation host. Normally, the first installation host is the host on which the central services instance is to run, but you can also choose another host for /<sapmnt>/<SAPSID>. You need to manually share this directory with Network File System (NFS) and - for a distributed system - mount it from the other installation hosts.

SAPinst creates the following shared directories during the SAP system installation: a. global - contains globally shared data b. profile - contains the profiles of all instances c. exe - contains executable kernel programs d. <instance> - contains instance-specific files like MDM server configuration files (.ini), and

other directories (accelerators, archives, distributions, reports)

Logically Shared Directories SAPinst creates the directory /usr/sap/<SAPSID>/SYS on each host. The subdirectories contain symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the first installation host.

Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance.


20 October 2011

Local Directories (SAP System) The directory /usr/sap/<SAPSID> contains files for the operation of a local instance as well as symbolic links to the data for one system.

This directory is physically located on each host in the SAP system and contains the following subdirectories:

SYS

The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID>.

<INSTANCE> for each instance installed on the host The instance-specific directories have the following names: - MDS<Instance_Number> - MDIS<Instance_Number> - MDSS<Instance_Number>

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

/ (root)

SYS

global

profileexe

<codepage>

global

profile

exe

<codepage><platform>

Physically shared directories

Logically shareddirectories Local directories

configworklogmdm

exe

KeySymbolic link <codepage>: UnicodeReplication by sapcpe

config

worklog

exe

usr

sap

<SAPSID>

<sapmnt>

<SAPSID>MDS<No> MD*S<No>

AcceleratorsArchivesDistributionsReports


October 2011 21

3.4.2 Exporting and Mounting Global Directories If you install one of the auxiliary servers MDIS or MDSS on a host other than the SAP Global host (where the MDS resides), you must mount global directories from the SAP Global host.

Prerequisites If you want to install the executables locally instead of sharing them, do not mount the exe directory with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local directory (not a link) with a minimum of 1.5 GB free space.

Procedure 1. Log on to the SAP Global host as user root and export the following directories with root access

to the host where you want to install the new instance: <sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global For more information, see Exporting and Mounting Directories via NFS for <UNIX platform> sections below. Make sure that the user root of the host where you want to install the new instance can access the exported directories.

2. Log on to the host of the new instance that you want to install as user root.

3. Create the following mount points and mount them from the SAP Global host: <sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global

3.4.3 Exporting and Mounting Directories via NFS for AIX (Optional) There are two ways of mounting directories via NFS:

Manually

Using the System Management Interface Tool (SMIT)

Procedure To mount directories via NFS from the host where the directory to be mounted resides:

1. Log on as user root.

2. To start NFS services at the host where the directory to be mounted resides, use SMIT as follows: a. Enter the command smitty.

b. Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS on this System Start NFS.

c. In the line Start NFS now, on system restart or both, enter: both d. Choose ENTER.


22 October 2011

3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for the host where the additional instance runs:

a. Enter the command smitty.

b. Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory to Exports List.

c. Enter the path of the directory that you want to export (for example, <sapmnt>/<SAPSID>/exe).

d. Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS allowed root access, enter the name of the host where the additional instance runs. For security reasons, make sure that this root access is disabled after the installation.

e. In the line Export directory now, system restart or both, enter: both f. Choose ENTER.

4. Create the mount point at the host where the additional instance runs: /usr/bin/mkdir <sapmnt>/<SAPSID>/SYS/exe

5. Mount the directory on the host where the additional instance runs. a. Enter the command smitty.

b. Choose Communications Applications and Services NFS Network File System (NFS) Add a File System for Mounting.

c. Enter the path name of the mount point. d. Enter the path name of the remote directory (the directory of the primary MDS instance). e. Enter the host where the remote directory resides. f. Set Mount now, add entry to /etc/filesystems or both to both. g. Set /etc/filesystems entry will mount the directory on system RESTART to yes. h. Change Mount file system soft or hard to soft. i. Choose ENTER.

6. If you exported the directory with read-write access, check if the host where the additional instance is to run has write access to directory <sapmnt>/<SAPSID>/exe by using the following commands: cd <sapmnt>/<SAPSID>/SYS/exe touch test (create a file called test) ls -l test (check if file test is created) rm test (remove the file test)

3.4.4 Exporting and Mounting Directories via NFS for HP-UX (Optional) You can mount directories via NFS in one of the following ways:

Using SMH

Manually

Mounting Directories via NFS Using SMH Procedure on the Host Where the Main Instance Runs

1. Enter one of the following commands: /usr/sbin/smh http://<hostname>:<port> where <port> is either the default port 2381 or your defined port (for example 2301)


October 2011 23

2. Choose Tools Network Services Configuration Networked File Systems Share/Unshare File Systems (Export FS).

3. Choose Share (Export) a File system.

4. Enter the local directory to be shared, for example /sapmnt/CUS.

5. Enter your client host as the Root Access Client.

6. Select Specify UID for unknown user and enter at User ID the value 0.

7. Choose OK.

8. Exit SMH.

Procedure on the Host Where the Additional Instance Runs

1. Enter the following command: /usr/sbin/smh

2. Call http://<hostname>:2381 or your defined port, such as 2301.

3. Choose Disks and File System Tools File Systems Add NFS.

4. Enter the following values: - Mount point - Remote server of the host exporting the file system - Remote directory

5. Enable the option Mount now and save configuration in /etc/fstab.

6. Choose New NFS.

7. Exit SMH.

Mounting Directories via NFS Manually Procedure on the Host Where the Main Instance Runs

1. Add the file system that you want to export to the file /etc/exports using the option -root= <nfs_cli_hostname_1>: ... :< nfs_cli_hostname_n>,> \ access= <nfs_cli_hostname_1>:...:< nfs_cli_hostname_n> Example: share –F nfs –o root=hw5111:hw5115, access=hw511:hw5115 /sapmnt/C11/exe If you are moving from a legacy system with the /etc/exports NFS configuration file you can use /usr/contrib/bin/exp2dfs to automatically convert the legacy syntax to the new syntax. If you encounter problems with your input similar to the example above, try the following:

a. Use FQDN (Fully Qualified Domain Name) b. Check what the NFS server is exporting using the following command:

showmount –e <servername> c. Try the anon option instead of root:

share -F nfs -o anon=y, access=hw5111:hw5115 /sapmnt/C11/exe

For security reasons, only use the following option during installation: -root= <nfs_cli__hostname_1>: ... :<nfs_cli_hostname_n>

2. To make the file system available to NFS clients, enter the following command: /usr/sbin/shareall


24 October 2011

Procedure on the Host Where the Additional Instance Runs

1. Add the remote file system to /etc/fstab. Example: hwi173:/sapmnt/C11 /sapmnt/C11 nfs defaults 0 0

2. Mount the file system. Example mount -a

3.4.5 Exporting and Mounting Directories via NFS for Linux (Optional) To export directories via NFS, perform the following steps (the following assumes that the host running the primary application server instance host is the NFS server):

1. Log on as user root to the NFS server.

2. Make sure that your host is configured as NFS server as follows: a. On Red Hat Linux, make sure that the output of the command chkconfig --list nfs

looks like this: nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off

b. On SUSE Linux, enter the following command: SLES9 and higher: yast or yast2

3. You can set up your host as NFS server as follows: a. On Red Hat Linux, enter the following command:

RHEL4 and higher: system-config-users b. On SUSE Linux, enter the following command:

SLES9 and higher: yast or yast2

4. To export a directory from a local file system, you can proceed as follows: a. On Red Hat Linux, use the following tool:

RHEL4 and higher: system-config-nfs b. On SUSE Linux, use the following tool:

SLES9 and higher: yast2 c. Perform the configuration manually:

1. Add a line to the local file /etc/exports: #/etc/exports <directory> <hostname>(<options>) There must not be a blank between <hostname> and <options>. Otherwise, the directory is exported with default option (ro) (read-only) to the host specified by <hostname> and with the option specified by <options> to all other hosts. To export directories on Linux with root permissions, use the option no_root_squash. For security reasons, only use this option during installation.


October 2011 25

d. Examples: To export the directory /usr/sap/trans in read-only mode to the NFS client host.wdf.sap-ag.de: #/etc/exports /usr/sap/trans host.wdf.sap-ag.de(ro) To export the directory in read-write mode with root permissions: #/etc/exports /usr/sap/trans host.wdf.sap-ag.de(rw,no_root_squash) To export the directory to all NFS clients of the domain using a wildcard (*): #/etc/exports /usr/sap/trans *.wdf.sap-ag.de(rw) To activate the changes (that is, inform the NFS daemon about the changes performed in /etc/exports), enter the following command: exportfs -r To get a list of all currently exported directories, enter the following command: exportfs -v For further details, consult the man page by entering man exports.

5. Log on as user root to the host where the file system is to be imported.

6. To mount the file systems, enter the following command: mount <nfs_server>:<file_system> <mount_point> Example: mount <nfs_server>:/usr/sap/trans /usr/sap/trans

3.4.6 Exporting and Mounting Directories via NFS for Solaris (Optional) To mount directories via NFS from the host where the directory resides that you want to mount, log on as user root and proceed as follows.

On the Host Where the Directory to Be Mounted Resides 1. Enter the command:

/usr/sbin/share

2. To add file systems shared via NFS, edit file /etc/dfs/dfstab: vi /etc/dfs/dfstab Add the following line for each file system: share -F nfs -o root=<nfsclient1>:<nfsclient2>,anon=0 \ -d "description" <file_system_to_be_shared>

Depending on your configuration, a fully qualified name might be required for nfsclient, for example, myclient.mydomain.com.

After your SAP system has been installed successfully, in the above line you have to change -o root to -o rw (or remove anon=0) for all exported directories: share -F nfs -o rw=<nfsclient1>:<nfsclient2> \ -d "description" <file_system_to_be_shared>


26 October 2011

3. If the /etc/dfs/dfstab was empty, the NFS server is not active. Start the NFS server with the following command: svcadm enable svc:/network/nfs/server:default

4. To see if the NFS server is active and which partitions are mountable, enter the command: showmount -e <NFS-server>

On the Host Where the Additional Instance Runs 1. If you are mounting NFS disks for the first time, the NFS client software is not active.

Start the NFS client software with the following command: svcadm enable svc:/network/nfs/client:default

2. Edit the file /etc/vfstab to mount the directory: vi /etc/vfstab Add the following line for each file system: <host_name_where_directory_resides>:<file_system_to_be_shared> \ - <mount point> nfs - yes - If the mount point exists, mount <file_system_to_be_shared> with the command: mount <mount point>

3.5 Preparing the Installation Files This section describes how to prepare the installation files. The installation files can be obtained from one of the following:

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

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

Procedure 1. Create a download directory on the host where you want to the MDM installation.

2. Download to the download directory all the objects necessary for the type of MDM installation you want to 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.

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


October 2011 27

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

Entry by Component: Used to download individual components one by one. You select the target operating system for the component, and then you select the items to download. Typically, you select the latest patch of the latest service pack (SP). You repeat this process for any additional components.

Link to SP Stack Application: Used to download all the components necessary for moving to a higher SP than the one currently installed. After selecting the target SP, you select for each component the instantiation, by defining the target operating system, database, or other required information.

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

1. Select the component to download: 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 the version of the server component.

3. Select the installable software unit.

4. Select the target operating system.

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

Obtaining Installation Files from DVD 1. Identify the required files for your MDM server installation as listed below.

MDM Installation Type Installation File Archive on SMP

Central Installation MDM Installation Master

Master Data Server Installation Package: mdm-server-<build>-<UNIX platform>.<archive file extension>

Master Data Import Server Installation Package: mdm-import-server-<build>-<UNIX platform>.<archive file extension>

Master Data Syndication Server Installation Package: mdm-syndication-server-<build>-<UNIX platform>.<archive file extension>

MDM Shared Installation Content Package: mdm-shared-<build>-<UNIX platform>.<archive file extension>

On DVD, the above MDM components reside unpacked in the Server_Installation directory.

SAP Instance Framework Installation Package

Distributed Installation of Master Data Server

MDM Installation Master

Master Data Server Installation Package mdm-server-<build>-<UNIX platform>.<archive file extension>

MDM Shared Installation Content Package


28 October 2011

mdm-shared-<build>-<UNIX platform>.<archive file extension>


Distributed Installation of Master Data Import Server


Master Data Import Server Installation Package: mdm-import-server-<build>-<UNIX platform>.<archive file extension>

MDM Shared Installation Content Package mdm-shared-<build>-<UNIX platform>.<archive file extension>


Distributed Installation of Master Data Syndication Server


Master Data Syndication Server Installation Package: mdm-syndication-server-<build>-<UNIX platform>.<archive file extension>

MDM Shared Installation Content Package mdm-shared-<build>-<UNIX platform>.<archive file extension>


2. 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 copied DVD do not contain any blanks. Mount the DVD locally. We do not recommend the use of Network File System (NFS), because reading from DVD mounted with NFS might fail.


October 2011 29

4. Installation This section describes how to install the following MDM servers on released UNIX platforms using SAPinst.

MDS

MDIS

MDSS

For installation of MDM Layout Server and MDM Windows clients, see service.sap.com/installMDM71 MDM – Installation Guide on Windows.

The administration command line tool MDM CLIX is automatically installed with MDS. You only need install it manually for remote access to MDS, for example from a local Windows PC. More information: service.sap.com/installMDM71 MDM – Installation Guide on Windows, section Installing MDM Windows Clients.

4.1 Installing MDM Servers You install the SAP servers as instances of an MDM system using SAPinst. In one installation run you can install all MDM servers or a single MDM server on one host.

This section is structured as follows:

Running SAPinst Explains the prerequisites and the procedure of performing an SAP system installation with SAPinst in general.

SAPinst Installation Options Lists the MDM options you can select in SAPinst for different installation types and software lifecycle tasks.

Interrupted Installation with SAPinst Explains how to proceed if the installation run of SAPinst has been interrupted manually or by the system.

Performing a Remote Installation with SAPinst, Starting SAPinst GUI Separately, and Silent Installation with SAPinst Shows optional alternative ways of starting and running SAPinst.

Entries in the Services File Created by SAPinst and Troubleshooting with SAPinst Provides additional useful information about the usage of SAPinst.

4.1.1 Running SAPinst This procedure describes how to install MDM servers with SAPinst. SAPinst includes a SAPinst GUI and a GUI server, which both use Java.

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


30 October 2011

If you need to see the installation on a remote display, we recommend you perform a remote installation with SAPinst, where SAPinst GUI is running on a separate host from SAPinst and the GUIserver. For more information, see the Performing a Remote Installation with SAPinst (Optional) section. Alternatively you can use an X Server for Microsoft Windows or other remote desktop tools like vncviewer or nxserver/nxclient offered by various vendors (or open source) for the remote access of SAPinst GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server which we use ourselves to validate installations with SAPinst.

Note the Following Information About SAPinst SAPinst normally creates the installation directory sapinst_instdir directly below the temporary

directory. SAPinst finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, SAPinst uses /tmp as the default installation directory. If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start SAPinst.

We recommend that you keep all installation directories until the system is completely and correctly installed.

SAPinst creates a subdirectory for each installation option called <sapinst_instdir>\<installation_option_directory>.

The SAPinst Self-Extractor extracts the executables to a temporary directory. These executables are deleted after SAPinst has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs.

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

During the installation, the default ports 21200, 21212, and 4239 are used for communication between SAPinst, the GUI server, SAPinst GUI, and the 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. An error message is displayed if one of these ports is already in use by another service. In this case, execute sapinst using the following parameters: SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> GUISERVER_HTTP_PORT=<free_port_number_http_server>.

To get a list of all available SAPinst properties, start SAPinst as described above with the option -p: ./sapinst -p

If you want to terminate SAPinst and the SAPinst Self-Extractor, press Ctrl + C


October 2011 31

Using SAPinst GUI 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, but SAPinst and the GUI server continue running.

If you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see the Starting SAPinst GUI Separately section.

Menu option SAPinst Log Browser Displays the Log Viewer dialog.

This dialog enables you to access the following log files directly:

Installation log (sapinst_dev.log)

Log files from the SAPinst GUI server

These log files might help you during troubleshooting. For more information, see the Troubleshooting with SAPinst section.

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

Stop Stops the installation (SAPinst GUI, SAPinst and the GUI server) without further changing the installation files. You can restart and continue the installation later from this point.

Continue Continues the installation

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

Message button Stop Stops the installation without further changing the installation files.

You can continue the installation later from this point.

Message button Continue Continues with the option you have chosen before.


32 October 2011

Prerequisites Make sure that your operating system does not delete the contents of the temporary directory /tmp

or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry. Make sure that the temporary directory has the permissions 777.

Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the SAPinst executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the SAPinst executables. You can set values for the TEMP, TMP, or TMPDIR environment variable as follows:

Shell Used Command

Bourne shell (sh) TEMP=<directory> export TEMP

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the SAPinst GUI. You can set values for the DISPLAY environment variables as follows:

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0 export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0


October 2011 33

Make sure that you have checked the following values for user root:

In csh execute limit

Output Properties cputime unlimited

filesize unlimited

datasize unlimited

stacksize unlimited

coredumpsize unlimited

descriptors 8192

memorysize unlimited

In sh, ksh, or bash execute ulimit -a

Output Properties time(seconds) unlimited

file(blocks) unlimited

data(kbytes) unlimited

stack(kbytes) unlimited

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

If your parameter settings differ from the settings above, change these values accordingly. Example: If you have to change the value for descriptors to 8192, proceed as follows: - In csh execute limit descriptors 8192 - In sh or ksh execute ulimit -n 8192

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

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

Procedure 1. Log on to your host as user root.

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

2. If you want to install an MDS, MDIS, or MDSS instance, mount the Installation Master DVD. Mount the DVD locally. We do not recommend using Network File System (NFS), because reading from DVDs mounted with NFS might fail.


34 October 2011

3. Start SAPinst from the Installation Master DVD by entering the following commands: cd <mountpoint_of_Installation_Master_DVD>/Server_Installation/ Installation_Master/MDM_IM_<platform> ./sapinst

Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started. Make sure that your current working directory is not a directory belonging to another operating system.

4. On the Welcome screen, choose the required SAPinst installation option from the tree structure. For more information, see the SAPinst Installation Options section.

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

More information about the input parameters: Section Basic SAP System Parameters More information about MDS setup for different databases: Section Environment Variables for MDS

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that SAPinst set by default. If required, you can revise the parameters before starting the installation.

6. To start the installation, choose Start. SAPinst starts the installation and displays the progress of the installation. When the installation has been completed successfully, SAPinst shows the dialog Execution of <option_name> has been completed successfully.

7. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished. Sometimes these remain in the temporary directory.

If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log file dev_selfex.out in the temporary directory. We recommend that you keep all installation directories until you are sure that the system is completely and correctly installed.

8. We recommend that you delete all files in the directory <user_home>/.sdtgui/.

9. If you have copied installation DVDs to your hard disk, you can delete these files when the installation has been successfully completed.


October 2011 35

4.1.2 SAPinst Installation Options This section provides information about the following in SAPinst:

Installation options

Software lifecycle options

If you want to use global accounts, which are configured on separate hosts, you must run the installation option Operating System Users and Groups before you start the installation of the SAP system (see Additional Software Lifecycle 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 suitable for running MDM.

Master Data Import Server (in an existing SAP system)

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

Master Data Syndication Server (in an existing SAP system)

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

Additional Software Lifecycle Options

Operation System Users and Groups

Creates all operating system accounts for your SAP system.

In most cases this is optional. However, you have to execute this option if you want to use global accounts that are configured on a separate host or if you want to install an SAP system instance on HP-UX.

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

Use this option only for SAP NetWeaver Process Integration (PI) 7.11 and higher. In lower versions of PI (or XI) you need to register MDM manually in the SLD.

More information:

service.sap.com/installMDM71 Monitoring and Supportability: How-To Guides (ZIP) MDM 7.1 How To Register MDM in SLD (PDF)

service.sap.com/installMDM71 Scenario Configuration Guide Setting Up PI

Install and Configure CCMS Agent and MDM CCMS Plug-in

Installs the SAP CCMS Agent along with the MDM CCMS plug-in and registers the agent in a central monitoring system.

More information: service.sap.com/installMDM71 Monitoring and Supportability: How-To Guides (ZIP) How To Install and Configure MDM 7.1 CCMS Monitoring on Windows and UNIX (PDF)


36 October 2011

Update MDM Updates all MDM instances of an SAP system.

You use this option for example to implement MDM server patches.

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 of the choices listed in the table below as well as a path to a log file containing detailed information about the error.

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

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps. This is possible because SAPinst records the installation progress in the keydb.xml file.

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

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

Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

You can also terminate SAPinst by choosing Ctrl + C. However, we do not recommend that you use Ctrl + C, because this kills the process immediately.

Procedure This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation.

1. Log on to your remote host as user root. Make sure that the root user has not set any environment variables for a different SAP system.

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

3. Restart SAPinst by entering the following commands: cd <mountpoint_of_Installation Master_DVD>/MDM_IM_<OS> ./sapinst

4. From the tree structure on the Welcome screen, select the installation option that you want to continue and choose Next.


October 2011 37

5. On the What do you want to do? screen, decide between the following alternatives and confirm with OK.

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it moves the content of the old installation directory and all installation-specific files to the backup directory. Afterwards, you can no longer continue the old installation.

For the backup directory, the following naming convention is used: <log_day_month_year_hours_minutes_seconds> (for example, log_01_Oct_2008_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

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 server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI.

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools like vncviewer or nxserver/nxclient – offered by various vendors or open source – for remote access to SAPinst GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server, which we use to validate installations with SAPinst.

The behavior of SAPinst has changed compared to previous versions. The client-server mode is not active by default, because SAP is no longer 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.

Prerequisites The remote host meets the prerequisites before starting SAPinst as described in the Running

SAPinst section 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 ping <local host>. b. Log on to the local host and enter the command ping <remote host>.

Procedure 1. Log on to your remote host as user root.

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

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



38 October 2011

3. Enter the following commands: cd <mountpoint_of_Installation_Master_DVD>/MDM_IM_<OS> ./sapinst -nogui For more information, see the Running SAPinst section. SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <host_name>, port <port_number> to continue with the installation

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

4.1.5 Starting SAPinst GUI Separately (Optional) You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately in the following cases:

You have logged off from SAPinst. If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately.

You want to perform a remote installation. If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinst GUI separately.

The behavior of SAPinst for remote installations has changed compared to previous SAPinst versions. The client-server mode is not active by default, because SAP is no longer 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 Windows 1. Log on as a member of the local administrators group.

2. Insert the installation DVD into your DVD drive.

3. Change to the directory of the SAPinst executables: <DVD drive>:\MDM_IM_<OS>

If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the following directory: <Installation_Master_DVD>\SAPINSTGUI_710_WINDOWS_I386



October 2011 39

4. Start SAPinst GUI by double-clicking sapinstgui.exe. SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as the default. If SAPinst and the GUI server are running on a remote host and SAPinst GUI cannot connect to the GUI Server, then the SAP Installation GUI Connection dialog is displayed. In this case, enter the name of the host on which SAPinst is running into the Host field and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host.

You have the option of starting sapinstgui.exe with the following parameters: - host=<host name>, where <host name> is the host name of the installation host - port=<nr>, where <nr> is the port number for the connection to the GUI server - -accessible enables the Accessibility mode Example: ./sapinstgui.exe host=lsi1209 port=3000 -accessible

Starting SAPinst GUI on UNIX 1. Log on as user root.

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

2. Mount your Installation Master DVD.

Mount the DVD locally. We do not recommend using Network File System (NFS).

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

If you want to start SAPinst GUI on a Linux 32-bit operating system, change to the following directory: <mountpoint_of_Installation_Master_DVD>/SAPINSTGUI_710_LINUX_I386


40 October 2011

4. Start SAPinst GUI by executing ./sapinstgui. SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as the default. If SAPinst and the GUI server are running on a remote host and SAPinst GUI cannot connect to the GUI Server, then the SAP Installation GUI Connection dialog is displayed. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host.

You have the option of starting sapinstgui with the following parameters: - host=<host name>, where <host name> is the host name of the installation host - port=<nr>, where <nr> is the port number for the connection to the GUI server - -accessible enables accessibility mode Example: ./sapinstgui host=lsi1209 port=3000 -accessible

4.1.6 Silent Installation with SAPinst (Optional) You have the option of installing the 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 an unattended installation.

For the detailed procedure, see SAP Note 950619.

4.1.7 Entries in the Services File Created by SAPinst After the installation has finished successfully, SAPinst has created the following entries in: /etc/services

sapdpXX = 32XX/tcp

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

where XX is set from 00 to 99.

If there is more than one entry for the same port number this is not an error.



October 2011 41

4.1.8 Troubleshooting with SAPinst This section describes how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

Stops the installation

Displays a dialog informing you about the error

Procedure 1. To view the log file, choose View Logs.

2. If an error occurs during the dialog or processing phase, do one of the following: - Try to solve the problem. - Abort the installation with Exit. For more information, see the Interrupted Installation with SAPinst section. - 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_home>/.sdtgui - If either the GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current user directory. - If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as described in the Starting SAPinst GUI Separately section. - If you use an X Server for Microsoft Windows or other remote desktop tools for the remote access of SAPinst GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes, contact the vendor of the X Server that you use for information on whether this X Server supports Java Swing-based GUIs and for further requirements and restrictions. See also SAP Note 1170809.

Note:

If you perform an installation on Solaris and you receive a FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen() error message in sapinst_dev.log, follow the solution described in either of the following SAP Notes:

1249364 (Inst. SAP NetWeaver based on Kernel 7.11 - UNIX)

966416 (Inst. SAP NetWeaver based on Kernel 7.10 - UNIX)


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

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


42 October 2011

4.2 Installing and Configuring the Database Before the MDS can handle data, you must install and configure the database. Starting from MDM 7.1 SP06, you cannot install MDM without providing the installation with the configured path of the database client of at least one of the supported database servers.

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 OS and DB documentation.

DBMS client software must be installed on the machine that runs the MDS.

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

Make sure that the MDM user <sapsid>adm has the necessary rights for accessing the database client.

Check if the user <sapsid>adm is a member of the user group that the system creates for the database clients during their installation. This user group owns the client files on file system level (for example user group dba for Oracle client library). SAPinst does not add the user automatically. If the MDM user is not member of the group, add it manually. To add the MDM user proceed as follows: 1. Log in as the <sapsid>adm user. 2. Stop the MDS instance and the instance service using the following commands: sapcontrol -nr <number of MDS instance> -function Stop sapcontrol -nr <number of MDS instance> -function StopService 3. Add the user <sapsid>adm to the user group that owns the database client files. 4. Start the instance service and the MDS instance again using the following commands: sapcontrol -nr <number of MDS instance> -function StartService <SAPSID> sapcontrol -nr <number of MDS instance> -function Start


October 2011 43

4.2.1 Oracle DBMS

For information on running the MDS on HP/UX Itanium with an Oracle database, see SAP Note 1264660

Install Oracle and Create a Database Instance You need to install both DBMS and client of Oracle if you plan to host Oracle on the same machine

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

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

If MDS runs on the same host that the Oracle DB is running on, you can set LD_LIBRARY_PATH (LIBPATH for AIX; SHLIB_PATH for HP-UX) directly to the Oracle library directory.

If MDS runs on a machine where only the Oracle instant client software is installed, make sure that: - the libclntsh.a library is present on AIX - a link to libclntsh.so.10.1 library is set for HP-UX, Linux, and Solaris. To set the link, use the following command: ln -s libclntsh.so.10.1 libclntsh.so

If the MDS and the DBMS are on the same machine, use the Net Configuration Assistant to define a Listener address and local Service Name that uses the IPC protocol rather than TCP. This affects the listener.ora and tsname.ora files, which can also be edited manually. This increases repository unarchive performance.

To determine the Oracle client versions which are supported for the various DBMS versions, refer to the Oracle server/client interoperability support matrix.

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

Oracle’s performance increases when separate spindles (hard disks) are used for the main data and indexes. Rollback segments (for transactions and logging) are set at database instance creation time and can represent an opportunity to use three separate spindles. The location of the main and index files can be set before repository creation, unarchiving, or duplication using the console.

Make sure that the user account of the SAP system (<sid>adm) has the permissions to read the Oracle client libraries. Typically, the client libraries are installed under $ORACLE_HOME with permissions 755, allowing read permissions for all. In addition, if the Oracle user account (for example the account used to install the Oracle software) has been assigned to the dba group, you may wish to add the SAP system user account to the dba group as well.

The Cursor Sharing parameter is set on a session basis to be exact. This provides a small performance improvement for certain operations between MDS and the Oracle Server. For earlier versions of MDM, you have the option of globally turning this parameter on for the entire Oracle instance with the following command: ALTER SYSTEM SET cursor_sharing='EXACT' scope=BOTH



44 October 2011

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 Oracle database instance that has different character sets for MDM. To use an existing database instance, run the following queries to determine the character sets: - National Character Set: select VALUE from NLS_DATABASE_PARAMETERS where PARAMETER='NLS_NCHAR_CHARACTERSET' - Database Character Set: select VALUE from NLS_DATABASE_PARAMETERS where PARAMETER='NLS_CHARACTERSET' If the results of the above queries do not return Unicode character sets, you must create a new database instance for MDM.

Linux on PowerPC: Set the following environment variable: export MDS_PRELOAD=libheteroxa10.so

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

Set Up and Test the Connection 1. To connect to the database, create an entry in the tnsnames.ora file. On UNIX OS, it is typically

located in $ORACLE_HOME/network/admin/. The entry must use the following format: <net service name specified in the MDM Console as DBMS server> = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <fully qualified IP address or domain of the host machine running the Oracle DBMS>)(PORT=<number of the port used by DBMS host with default 1521>)) ) (CONNECT_DATA = (SERVICE_NAME = <Oracle service name specified when the Oracle DBMS was installed>) ) ) You can test the net service name by logging onto the Oracle database from the MDS host using the Oracle SQLPLUS command as follows: sqlplus <userid>/<password>@<net service name> Alternatively, you can just test the connection to the Oracle database with the following command: tnsping <net service name>

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

Connect Initially 1. Modify the temporary tablespace.

When connecting to the DBMS for the first time (DBMS initialization), the system account or an equivalent account is used to make the connection and the DBMS is queried for the temporary tablespace of that account. Normally this tablespace is named TEMP. If the site wishes to use a different tablespace, modify the temporary tablespace of the connecting account prior to DBMS initialization.



October 2011 45

2. Set the user account. The first time that the MDS connects to the database, the MDM Console asks which user account to use to connect to the DBMS. By default you use the SYSTEM account for all access. If you want to use another account or the use of the SYSTEM account is not allowed in your DBMS, you can use the SYSTEM account, or the MDM Console/CLIX feature to create an alternative account. Such account creation should be modeled according to the following template:

create user HARRY_POTTER identified by muggles default tablespace SYSTEM; grant alter user, alter system, create session, create any index, create view, dba, drop

any view, create any table, delete any table, drop any table, insert any table, update any table, select any table, alter tablespace, create tablespace, drop tablespace, unlimited tablespace, create any sequence, drop any sequence, alter any sequence, select any sequence, lock any table, alter any table, alter any type, alter database, create profile, drop profile, create database link, drop any index, create user, drop user, create any directory, create any procedure, analyze any to HARRY_POTTER;

3. Define the tablespace directories. The first time you connect the MDS to the database using MDM Console, a dialog box appears asking you where you want to store data and index tablespace files. This optional step slightly improves 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 the database host machine. Furthermore, if you choose different locations for the data tablespace and index tablespace so that they are on different hard disks (different physical spindles, not just logical drives), database performance can improve by a small, but significant, degree. The directory paths you specify must already exist on the database host machine.

b. These settings apply to repositories only as they are created. Already existing repositories will stay where they were created.

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

After a repository is created through create, unarchive, duplicate or slave operations, all tables and indexes are analyzed in the final step. We recommend that you re-analyze tables to maximize the performance of the DBMS rom time to time and especially if your repository has gained or lost a significant number of records (for example from a large import).

4. To mount an MDM repository residing in an Oracle DBMS, specify the Oracle Net Service Name as the DBMS Server in the Add DBMS Server dialog. This name should be defined using Oracle networking methodologies.

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

The first time MDS establishes a relationship with a particular Oracle instance, it queries the temporary tablespace name of the initial logon, for example SYSTEM. The retrieved value, for example TEMP, is stored in MDM in the A2i_xCat_DBs.A2i_DB_Settings table in the TempTableSpaceName field. MDM queries this table when creating more users or schemas.


46 October 2011

In an MCOD environment the temporary tablespace is set to PSAPTEMP. To adjust the temporary tablespace setting proceed in one of the following ways:

In the MDM Console choose DBMS Settings from the context menu of your MDS and set the Temp tablespace name.

Use the following CLIX command: clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> TempTableSpaceName=PSAPTEMP

Allow Flexible Tablespaces You can detach from the methods built into MDM for the creation of Oracle database storage. As an experienced database administrator you can utilize even more of the flexibility and power that the database provides.

Background

In Oracle, data elements are stored in tables. Collections of tables are grouped together into schemas. Tables (or schemas) are then assigned to logical storage entities called tablespaces. By using the logical concept of a tablespace, it allows you to manage the actual files that are used for a tablespace independent of the schemas and tables.

By default MDM applies the following data storage concept:

MDM repositories use one, two, or four schemas. MDM data divides into four types of data collections: Main, Originals, Thumbnails, and Variants. In a two partition arrangement, Main and Originals are placed in one partition, with Thumbnails and Variants being placed in the other. With four partitions, each data collection type has a separate partition (schema and tablespaces).

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

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

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

While this arrangement is convenient for the majority of use cases, it limits the full control of location and other parameters in the creation and management of tablespaces that are possible in Oracle databases. But you have the freedom to create tablespaces according to the needs of your particular installation as described below.

Tablespace Enhancement

MDS can use tablespaces that preexist in a database as an alternative to creating them. You configure such a custom tablespace on the DBMS in the following table: A2I_XCAT_DBS.A2I_DB_SETTINGS

You have to add several rows that are not automatically created through use of the MDM Console or CLIX, by manually using scripts and/or the SQL*Plus utility of Oracle. Once these rows are created they can be maintained using the MDM Console.


October 2011 47

The A2I_XCAT_DBS.A2I_DB_SETTINGS table creates the following records:

NAME column

SETTING column

Explanation

DataPath Actual path or empty

Already existing and managed by MDM Console. A single directory where data tablespaces are created.

IndexPath Actual path or empty

Already existing and managed by MDM Console. A single directory where index tablespaces are created.

tsname_m Name of tablespace you created

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

tsname_mx Name of tablespace you created

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

tsname_o Name of tablespace you created

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

tsname_ox Name of tablespace you created

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

tsname_t Name of tablespace you created

Tablespace Name for Thumbnails repository schema tables. If this record is missing or the Setting column is blank or empty, the “DataPath” record will be used to create a new tablespace.

tsname_tx Name of tablespace you created

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

tsname_v Name of tablespace you created

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

tsname_vx Name of tablespace you created

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

To initially create the A2I_XCAT_DBS schema and A2I_DB_SETTINGS table on a DBMS from the MDM Console choose DBMS Settings from the MDS Server node context menu or from the Server menu. Once created, you can insert the eight necessary records listed in the table above using the Oracle Enterprise Manager, or with a script using SQL*Plus.

The following sample script utilizes eight separate tablespaces. The password for the a2i_xcat_dbs account is the same as the one used to initially connect using the DBMS Settings dialog:

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


48 October 2011

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

connect a2i_xcat_dbs/<myPassword>@<myInstance>; insert into a2i_db_settings (name, setting) values ('tsname_m', 'MDSDATA'); insert into a2i_db_settings (name, setting) values ('tsname_o', 'MDSDATA'); insert into a2i_db_settings (name, setting) values ('tsname_t', 'MDSDATA'); insert into a2i_db_settings (name, setting) values ('tsname_v', 'MDSDATA'); insert into a2i_db_settings (name, setting) values ('tsname_mx', 'MDS_IDX'); insert into a2i_db_settings (name, setting) values ('tsname_ox', 'MDS_IDX'); insert into a2i_db_settings (name, setting) values ('tsname_tx', 'MDS_IDX'); insert into a2i_db_settings (name, setting) values ('tsname_vx', 'MDS_IDX'); commit;

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

After having created such a repository, you may want to create another repository with different tablespaces. An example might be where you regularly back up the tablespaces for a master repository, but want a slave repository to be on different tablespaces where backups are less necessary.

Prior to creating such a slave, do the following: using the DBMS Settings dialog in the MDM Console, change the setting values for the tsname_<…> setting names. Or you can use CLIX or SQLPlus scripts which would look like this:

CLIX clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_m=SLAVEDATA clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_o=SLAVEDATA clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_t=SLAVEDATA clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_v=SLAVEDATA clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_mx=SLV_IDX clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_ox=SLV_IDX clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_tx=SLV_IDX clix dbSetDBMSSetting <mdsHostSpec> <dbmsSpec> tsname_vx=SLV_IDX

Once the records have been created, as above, the CLIX method integrates easily with other CLIX commands such as create slave operations. More information: Documentation of the CLIX commands <mdsHostSpec> and <dbmsSpec> at service.sap.com/installMDM71 MDM Console Reference Guide.

SQLPlus connect a2i_xcat_dbs/<myPassword>@<myInstance>; update a2i_db_settings set setting = 'SLAVEDATA' where name = 'tsname_m'; update a2i_db_settings set setting = 'SLAVEDATA' where name = 'tsname_o'; update a2i_db_settings set setting = 'SLAVEDATA' where name = 'tsname_t'; update a2i_db_settings set setting = 'SLAVEDATA' where name = 'tsname_v'; update a2i_db_settings set setting = 'SLV_IDX' where name = 'tsname_mx'; update a2i_db_settings set setting = 'SLV_IDX' where name = 'tsname_ox'; update a2i_db_settings set setting = 'SLV_IDX' where name = 'tsname_tx'; update a2i_db_settings set setting = 'SLV_IDX' where name = 'tsname_vx'; commit;

If you want to return this DBMS to the state where MDS will automatically create tablespaces, then you must manually delete these records from the database. While this cannot be done from the MDM Console, you can use the following script:

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


October 2011 49

Notes

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

The settings in the A2I_XCAT_DBS.A2I_DB_SETTINGS table are queried when MDS performs a duplicate, unarchive, create new, or create slave operation. Afterwards these tablespace settings remain associated with that repository even if you change the settings prior to creating another repository.

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

Once you have created these eight records in the A2I_DB_SETTINGS table, you can change the setting values using the DBMS Settings dialog of the MDM Console. This dialog does not allow you to add or delete records or change the name of an existing record. So, if you make a mistake with a name or wish to remove these records, you must do so using the Oracle Enterprise Manager or SQL*Plus utilities.

The History table, which is used for auditing, does not fall under this manual tablespace management approach and will still use the settings for DataPath and IndexPath.

When you create your own tablespaces, you must monitor their growth and manage extending the size of the tablespace files.

More Sample Scripts

The following example shows a tablespace definition that is typical for the main data partition of an MDM repository where the tablespace is comprised of two files that can grow indefinitely: CREATE TABLESPACE MDSDATA DATAFILE '/usr/db/ts/mdsdata1.dbf' SIZE 1M REUSE AUTOEXTEND ON NEXT 1M MAXSIZE UNLIMITED, '/usr/db/ts/mdsdata2.dbf' SIZE 1M REUSE AUTOEXTEND ON NEXT 1M MAXSIZE UNLIMITED DEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);

The following example shows a tablespace definition similar to the previous example, except that the file system limits files to 2 GB and you allocate the entire file space immediately to avoid disk fragmentation: CREATE TABLESPACE MDSDATA DATAFILE '/usr/db/ts/mdsdata1.dbf' SIZE 2048M, '/usr/db/ts/mdsdata2.dbf' SIZE 2048M DEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);

The following example shows a tablespace definition that is typical for an MDM repository index tablespace. CREATE TABLESPACE MDS_IDX DATAFILE '/usr/db/ts/mds_idx.dbf' SIZE 128K REUSE AUTOEXTEND ON NEXT 64K MAXSIZE UNLIMITED DEFAULT STORAGE (INITIAL 16K NEXT 64K MAXEXTENTS UNLIMITED PCTINCREASE 0);


50 October 2011

4.2.2 IBM DB2 for Linux, UNIX and Windows See service.sap.com/installMDM71 MDM 7.1 - DB2 LUW Guide.

4.2.3 IBM DB2 for z/OS

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

Check the System Requirements The minimum system requirements for an SAP MDM installation are as follows:

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

IBM DB2 Driver for ODBC and CLI Version 9 FixPak 1

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

Install the CLI Driver Download and Extract the Archive

1. Create a directory into which you can install the CLI Driver. In the documentation, we call this directory <db2_cli_odbc_driver>.

2. Download the CLI Driver file.

- If you are an SAP OEM customer, you can download the file from SAP Service Marketplace at http://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, you obtain the file from IBM. In this case the top directory in the archive is clidriver.

3. Extract the file to the directory <db2_cli_odbc_driver>.

- If you downloaded the file from SAP Service Marketplace, you will need to extract it with SAPCAR to <db2_cli_odbc_driver>. For more information about SAPCAR, see SAP Note 212876.

- If you downloaded the file from the IBM site, see the following IBM documentation for information about 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 extract the file, a subdirectory clidriver will be created, provided you downloaded the file from IBM.


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

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


October 2011 51

Modify the PATH Variable Add the DB2 directory to your PATH environment variable.

For AIX: Add <db2_cli_odbc_driver>/lib to the LIBPATH variable.

For Linux: Add <db2_cli_odbc_driver>/lib to the LD_LIBRARY_PATH variable

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

In special cases, you will need to set the DB2_CLI_DRIVER_INSTALL_PATH environment variable to <db2_cli_odbc_driver>. This environment variable overwrites the library path setting.

Download the CLI Driver License The CLI Driver comes with a temporary license that will expire after 90 days: If a permanent license is already available, copy it to the license directory <db2_cli_odbc_driver>/license to avoid unnecessary downtime later on.

On UNIX, the user <SIDADM>adm must have permission to read and write to the license file directory of the IBM clidriver: <cli_driver_path>/clidriver/license

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

For SAP OEM Customers: If you purchase DB2 and DB2 Connect from SAP as an OEM customer, you need to 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, you need to do the following:

Retrieve the permanent license file for the IBM DB2 Driver for ODBC and CLI from the DB2 Connect image 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.lic.

Catalog Database Server to db2cli.ini This file is located in directory <db2_cli_odbc_driver>/cfg/db2cli.ini.

Add the following section to the db2cli.ini file (with your values):

[<DBALIAS>]

DATABASE=<LOCATION NAME>

PROTOCOL=TCPIP

HOSTNAME=<HOSTNAME>

SERVICENAME=<DDFPORT>


52 October 2011

DDF Term Definitions The following are the definitions of the terms used above.

<DBALIAS> Logical name of the database under which the database is known to the MDM Console

You need to specify the <DBALIAS> within the MDM Console when you specify the DB2 for z/OS data source for your archives.

<LOCATION NAME> DDF Location name of the DB2 Subsystem

<HOSTNAME> Name of the database host

<DDFPORT> DDF listening port of the DB2 Subsystem

The DB2 command -DISPLAY DDF displays the DDF port as TCPPORT and the DDF location name as LOCATION.

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 at https://service.sap.com/instguidesnw.

You must install the stored procedure DSNUTILS according to the instructions in the SAP DBA Guide for z/OS.

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 (AS Java) To perform a BIND and GRANT in an environment without an SAP NetWeaver AS Java system, carry out the following steps:

1. Download sapcar from 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 following environment variables: AIX: DIR_LIBRARY to location of unpacked executables and LIBPATH to location of unpacked executables. You need to set both variables to the same location. Linux: DIR_LIBRARY to location of unpacked executables



October 2011 53

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 SAP Service 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 Port> -L <DDF Location> -S <Database Name> -H <Host Name> -U <Database Connect User> -u <Admin User> -p <Admin Password>

BIND and GRANT With SAP NetWeaver Application Server (AS Java) You do not need SAP NetWeaver AS Java to install MDS and core components. However, if you have SAP NetWeaver AS Java installed you can use the following procedure to BIND and GRANT:

First you call the DBA Cockpit (or transaction DB2) on your SAP Solution Manager system and perform these steps remotely for the MDM system.

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

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

Before you begin, check that the user installing MDM has the correct permissions to BIND and GRANT, as well as the MDM user that is generated during the installation process. For details 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)

If you are performing BIND and GRANT through a remote connection from an SAP Solution Manager version 3.0 or 3.1 on an SAP Web AS ABAP 6.20 or 6.40 system, use the following procedure:

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

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

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

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

a. Database host name b. Database port number c. Database SSID 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 used to grant the necessary privileges to the MDM connect user. Therefore, ensure that this user ID has sufficient authorities.



54 October 2011

SAP Solution Manager 4.0 (SAP NetWeaver 7.00 or Higher)

If you are performing BIND and GRANT through a remote connection from an SAP Solution Manager version 4.0 on an SAP Web AS ABAP 7.00 system or higher, use the following procedure:

1. You need to apply SAP Basis Support Package 12.

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

3. Call the DBA Cockpit (or transaction DB2).

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

5. In the Configuration section, choose JCL Settings (DB2J) to specify the TSO user ID to be used to run stored procedures. You do this in Profiles. The TSO user ID needs to have sufficient privileges in the DB2 subsystem of the MDM system to grant the authorities 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 SAPMDM is created with the VCAT of STOGROUP SYSDEFLT. If you do not want this to happen, you must create the STOGROUP now.

Foreign Keys SAP MDM creates foreign keys very frequently. When a referenced table is converted, the status of the tablespace containing the table is set to CHECK PENDING. The MDS resets the CHECK PENDING status to read-write (RW) by calling the DB2 CHECK utility from the stored procedure DSNUTILS.


October 2011 55

4.2.4 MaxDB 1. Log on as user root.

You need to install MaxDB server software if you plan to host MaxDB on the same machine as MDM. If the DBMS and MDM reside on different hosts, the MDS host requires installation of MaxDB client software. Due to specific database restrictions MDM repositories can contain no more than 17 data languages when working with MAXDB.

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

The MaxDB client version must be 7.6.6.17 or higher.

a. Start SDBSETUP. b. Start installation/upgrade. c. Select component group Client. d. Edit the following independent data path:

/sapdb/data e. Edit the following independent program path:

/sapdb/programs f. Install.

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

a. Start SDBSETUP. b. 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 /sapdb and define the following:

- Database name (default: MDM) - Password of the database manager operator (default user: DBM) - Password of the database system administrator (default user: DBA)

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

h. Define the following system resource settings for the database: - Memory (default: 200 MB; increase for production environment) - CPUs (default: 1; increase for production environment) - Parallel database sessions - (default: 20; for production environment set at least 300)

i. Define the following global database settings: - 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.


56 October 2011

The installation creates the following default database user which can be used for MDM: - User name = SAPMDMDB - Password = SAP The created database instance with the default database parameters is tailored for an MDM test environment and can be extended for production use.

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

5. For a production environment, change the default value of the database parameter MAXLOCKS from 50 000 to at least 650 000.

With MaxDB 7.7.04 the name of the parameter changed to MaxSQLLocks.

6. To mount an MDM repository residing in a MaxDB DBMS (using MDM Console), specify the instance name and the database name of the MaxDB DBMS as the DBMS Server in the Add DBMS Server dialog. This name should be defined using MaxDB syntax instancename:dbname.

Use a semi-colon (;) as the delimiter when using CLIX with MaxDB.

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



October 2011 57

4.3 Installing Additional MDM Components

Component Shipped Files

Prerequisites / Remarks Installation Procedure

MDM Java API and MDM Connector

For hosted applications, you need SAP NetWeaver 2004 or 7.0.

For standalone applications, you need a Java 1.4.2 compatible Java Virtual Machine.

Deploy the components on your Java machine.

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

MDM Java and .NET API Guide.

MDM Portal Content MDM Connector and MDM Java API are deployed (see above).

Deploy the components on your EP.


Portal Business Package for Master Data Management

MDM PI Adapter The SAP NetWeaver Process Integration (PI) is installed.

MDM Connector and MDM Java API are deployed (see above).

Deploy the components and the adapter content on your PI.


MDM Process Integration (PI) Adapter Guide

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


MDM ABAP API Guide and the application help of transaction SAINT.

MDM Web Services For more information, see service.sap.com/installMDM71

MDM Web Services

MDM Enrichment Controller

SAP Web Application Server 6.40 (Java), MDS, MDIS, and MDSS are installed.

MDM Connector and MDM Java API are deployed (see above).


MDM Enrichment Architecture.


58 October 2011

Component Shipped Files

Prerequisites / Remarks Installation Procedure

MDM Web Dynpro SAP NetWeaver MDM Web Dynpro Framework 7.1 SP5 Patch 2 or higher

For more information, see service.sap.com/installmdm71 Development and Customization MDM Web Dynpro Components Guide.

Refer to the following sections:

Installing the MDM Web Dynpro Environment

Deploying the MDM Web Dynpro Components Framework

MDM Collaborative Processes for Material

MDM Collaborative Processes for Material 7.10 7.20

For more information, see

service.sap.com/installmdm71 MDM Business Content Extensions Collaborative Processes for Material Master Data Creation


October 2011 59

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

5.1 Environment Variables for MDS In the dialog-phase of the MDM installer you are prompted for necessary information about how to configure the MDS instance to connect to a certain database. The MDS needs to find and load the DB client libraries, which need to be installed on the host where MDS is running.

The paths to these libraries are added to a number of shell scripts which are created in the home folder of the <sapsid>adm user. If necessary, you can change these variables in the database configuration scripts for MDM manually.

The following table gives an overview of the script files:

Shell Script Description

.mdmdbenv_<hostname>.sh

Database configuration script for Bourne-compatible shell (/bin/sh).

This is the default script that is launched at login of user <sapsid>adm.

.mdmdbenv_<hostname>.csh

Database configuration script for C-Shell (/bin/csh)

This is the default script that is launched at login of user <sapsid>adm.

.mdmdbenv.sh

Database configuration script for Bourne-compatible shell (/bin/sh).

This script is launched when .mdmdbenv_<hostname>.sh does not exist.

.mdmdbenv.csh

Database configuration script for C-Shell (/bin/csh)

This script is launched when .mdmdbenv_<hostname>.csh does not exist.

These scripts contain a number of variables that are used to configure MDS in order to load a DB client library and connect to a DBMS.

For DB2 you can use the existing database configuration script in the mdmbenv scripts. Each DB2 database manager instance has the script file sqllib/db2profile, which you can find in the home directory of the instance. This script sets up the environment for DB2 automatically. You can simply add this script to either .mdmdbenv_<hostname>.sh or .mdmdbenv.sh. It is not compatible with the C-Shell so you cannot use it with .mdmdbenv.csh or .mdmdbenv_<hostname>.csh.


60 October 2011

Procedure 1. Open the database scripts and change the setting(s). It is sufficient only to change the settings in the

script that is used at login (see table above). However, we recommend that you keep the settings in the different script files in sync. SAPinst has set the following variables:

Variable Database Description

MAXDB_UTILITIES_HOME (sh)

MAXDB_UTILS_HOME (csh) MaxDB

MaxDB utilities, for example /sapdb/programs/bin

MAXDB_CLIENT_LIBRARY_HOME (sh)

MAXDB_CLIENT_HOME (csh)

MaxDB client library (libSQLDBC76_C.xx *)

ORACLE_HOME

Oracle

Oracle installation home

ORACLE_SQLPLUS_HOME Oracle SQLPlus utility

ORACLE_CLIENT_LIBRARY_HOME (sh)

ORACLE_CLIENT_HOME (csh)

Oracle client library

DB2_CLIENT_LIBRARY_HOME (sh)

DB2_CLIENT_HOME (csh) DB2

DB2 client library (libdb2.xx *)

* .xx is the platform-specific extension for shared libraries, for example .sl,.so, or .a.

2. Restart the MDS instance in one of the following ways: - Using SAP MMC: Right-Click the instance-node and choose Restart. - Using sapcontrol: Enter the following command: sapcontrol –nr <instance number> -function RestartInstance


October 2011 61

5.2 Starting and Stopping the MDM Servers SAPinst automatically starts the SAP system and its instances after the installation. Start and stop the MDM servers to check if the installation was successful.

When stopping and restarting MDS and the database, restart the database first.

For starting and stopping MDM servers you can use the following tools:

SAP Microsoft Management Console (SAP MMC) or SAP Management Console (SAP MC) SAP MMC and SAP MC are the generic SAP system management tools, which are installed automatically with any SAP system (SAP MMC on Windows; SAP MC on UNIX).

MDM Console or MDM CLIX The MDM Console is the MDM administration Windows client for system, authorization, repository management, and other administration tasks. MDM CLIX is a Windows command line tool that provides functions of the MDM Console.

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

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

5.2.1 Using SAP Microsoft Management Console Use this procedure to start and stop the SAP system with the SAP Microsoft Management Console (SAP MMC) to check if the installation was successful.

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

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

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

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

Management Console.

2. Right-click the SAP system node and choose Start or Stop. 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), you have the following options to start or stop your system: - You start or stop the SAP instances using the SAP MMC on each host. - You add the remote instances to the SAP MMC configuration to start or stop all instances from a single SAP MMC. For more information, see the SAP MMC system documentation.




62 October 2011

5.2.2 Using SAP Management Console You can start and stop all instances of your SAP system using the SAP Management Console (SAP MC).

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprised of systems or instances on Windows platforms, you can also start and stop it from a Windows system or instance using the Microsoft Management Console (MMC). For more information about handling the MMC, see the Using SAP Microsoft Management Console section above.

Prerequisites Make sure that the host on which you start SAP MC meets the following requirements:

Java Runtime Environment (JRE) 5.0 is installed.

The browser supports Java.

The browser’s Java plug-in is installed and activated.

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

Starting the Web-Based SAP Management Console 1. To start the SAP MC Java applet, start a Web browser and enter the following URL:

http://<hostname>:5<instance_number>13 Example: If the instance number is 53 and the host name is saphost06, you enter the following URL: http://saphost06:55313

If your browser displays a security warning message, choose the option that indicates that you trust the applet.

2. Choose Start. The SAP Management Console appears.

When you start the SAP MC for the first time for a newly installed SAP system, you have to register your system as described in Registering Systems and Instances below. Having done this, the instances installed on the host you have connected to are already added in the SAP MC when you start the SAP MC next time. By default, the instances installed on the host you have connected to are already added in the SAP MC. If you want to change the configuration to display systems and instances on other hosts, see Registering Systems and Instances below.


October 2011 63

Starting and Stopping Systems and Instances Starting an SAP System or Instance

1. In the navigation pane, open the tree structure and navigate to the system node that you want to start.

2. Select the system or instance and then, from the context menu, choose Start.

3. In the Start SAP System(s) dialog box, choose the required options.

4. Choose OK. The SAP MC starts the specified system or system instances.

The system might prompt you for the SAP system administrator credentials. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm.

Stopping an SAP System or Instance 1. Select the system or instance you want to stop and choose Stop from the context menu.

2. In the Stop SAP System(s) dialog box, choose the required options.

3. Choose OK. The SAP MC stops the specified system or system instances.

The system might prompt you for the SAP system administrator credentials. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm.

Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAP MC.

Registering Systems and Instances in the SAP Management Console You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and administer all systems and instances from a single console. You can configure the SAP MC startup view to display the set of systems and instances you want to manage.

Prerequisites The SAP MC is started.

Registering SAP Systems 1. In the SAP MC, choose File New.

2. In the New System dialog box, enter the required data.

If you have already registered systems in the SAP MC, they are stored in the history. To open the System’s History dialog box, choose the browsing button next to the Instance Nr. field. Select an instance of the system that you want to add and choose OK.

3. Choose Finish.


64 October 2011

Registering Individual Instances 1. In the SAP MC, choose File New.

2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.

3. The SAP MC displays the SAP system node and the instance node in a tree view in the navigation pane.

To view all instances of the respective SAP system, select the relevant system node and choose Add Server from the context menu.

Configuring the SAP MC View

You can choose the instances that the SAP MC displays automatically on startup:

1. In the Settings dialog box, select History.

2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup.

3. Choose the ADD << button.

4. Choose Apply and then choose OK. Similarly, you can remove instances from the startup configuration.

You can save the current configuration in a file:

1. Choose File Save Landscape.

2. In the Save dialog box, enter the required data.

3. Choose Save.

You can load a configuration from a file:

1. Choose File Load Landscape.

2. In the Open dialog box, select the configuration you want to load.

3. Choose Open.

5.2.3 Using Scripts You can start and stop the SAP system for MDM by running the sapcontrol utility.

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

Procedure Starting the SAP System

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

sapcontrol –nr <instance number> -function StartSystem

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

You can start the MDM server instances separately by entering the following command: sapcontrol –nr <instance number> -function Start

Where <instance number> is the number of the MDM server instance you want to start.


October 2011 65

Stopping the SAP System

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

sapcontrol –nr <instance number> -function StopSystem

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

You can stop the MDM server instances separately by entering the following command: sapcontrol –nr <instance number> -function Stop

<instance number> is the number of the MDM server instance you want to stop. Make sure that you always stop the MDS instance first.

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

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

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

More Information About installing MDM CLIX and MDM Console: service.sap.com/installMDM71 MDM – Installation on Windows, section Installing MDM Windows Clients

About using MDM CLIX and MDM Console: service.sap.com/installMDM71 MDM – Console Guide, the following sections:

CLIX: Master Data Server Commands

Console: Accessing MDM Servers


66 October 2011

5.3 Setting Up MDM Servers To set up the MDM servers after installation you 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.

Configuring MDM Servers When the MDM server instances (MDS, MDIS, MDSS) are installed, the following configuration files are created in the config directory of the instances: - mds.ini - mdm_list.ini - mdis.ini - mdss.ini

In the configuration (ini) files you can adapt a broad range of default server settings for your needs.

For more information about the individual settings and their effects, see the following at service.sap.com/installMDM71:

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

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

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

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

For more information, see service.sap.com/installMDM71 MDM Console Reference Guide, section MDM Server Administration.

Setting MDS and Repository Passwords By default, access to new MDS and MDM repositories is not limited. For secure productive use of MDM you have to set passwords using the MDM Console to control access:

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

When creating a new repository or unarchiving a repository, make sure that you set passwords for the predefined users, especially for the Administrator user.

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

For more information, see service.sap.com/installMDM71 MDM Console Reference Guide, section MDM System Administration.


October 2011 67

5.4 Setting Up SSL Communication for MDM Servers Starting from version 7.1 SP07, you can set up SSL (Secure Sockets Layer) communication during an installation or update of MDS, as described in the following sections.

Setting Up SSL During an Installation or an Update of MDS Prerequisites

You are using the latest MDM 7.1 SP07 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 check box.

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 MDM servers' ini files. When updating MDM servers, you need to set this parameter manually in the ini files, as described in SAP Note 1563249.

3. Specify the following strings:

Organization

Country (2 letter string)

The installer uses these strings, the Common Name, which is the fully qualified server name, and the SSL TCP Port of the MDM server, to create the server and client keys.

4. Choose Next.

5. In the SAP Cryptographic Software step, make sure the Install the SAP Cryptographic Library check box is selected, and specify the path to the SAPCRYPTO library in the Path to SAPCRYPTO.SAR field.

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

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

File Description Comments client.pse Client key of the SSL communication. The MDM clients

will need this file to connect to the MDM servers.

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

Copied also to the sec folder of the MDM servers.

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

cred_v2 For internal use.

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

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





68 October 2011

To verify that SSL is set up correctly, you need to 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 <SID>adm account.

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.ini, mdis.ini, mdss.ini), verify that the following parameters are set:

Listening Mode=Both or SSL

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

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

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

Setting MDIS and MDSS to work as clients:

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:

Service Control Security Enabled=True

Default is True.

SSL Enabled=True

Default is False.

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


October 2011 69

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

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

If you want to update single instances, be aware that updates can only be installed based on MDM server types and host types. For example, if you choose to update one MDS instance running on a Linux x86_64 host, all other MDS instances of this SAP system running on other Linux x86_64 hosts are updated as well.

Prerequisites This description assumes that you installed your SAP system with standard SAP tools according to

the installation documentation.

You are logged on as user root.

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 Update

MDM.

2. Follow the instructions in the SAPinst input dialogs.


70 October 2011

7. Maintaining Multiple MDM Servers on a Host You can install multiple instances of MDM Servers (including MDS, MDSS, MDIS, and MDLS) on a single host. The instances of MDM Servers can be from different versions of MDM (such as 5.5 and 7.1), which may be useful when upgrading from one MDM version to another, or multiple instances of MDM 7.1 SP04 and above.

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 a unique SAP System ID (SID).

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

Running multiple instances of Master Data Server, at the same time, on the same host, is supported starting from MDM 7.1 SP06. (In previous versions, you could not run the multiple instances at the same time.)

To start and stop the MDM servers on hosts with multiple MDM 7.1 Server instances, you can use the following tools: SAP Microsoft Management Console (SAP MMC), SAP Management Console (SAP MC), or scripts. Starting from MDM 7.1 SP06, you can also use MDM Console or CLIX for these tasks.

Maintaining multiple instances of MDM 5.5 Master Data Server on the same host is not supported.

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

MDM 5.5 and MDM 7.1 The default installation and target directories for MDM servers differ between MDM 5.5 and MDM 7.1. Therefore, one instance of MDM 7.1 can be installed side-by-side with an instance of MDM 5.5 without additional manual configuration. For more information about a MDM 5.5 and MDM 7.1 side-by-side scenario for upgrade purposes, see service.sap.com/installMDM71 > MDM 7.1 - Upgrade Guide


October 2011 71

8. Uninstalling MDM Servers MDM has been installed as an SAP system and the MDM servers (MDS, MDIS, MDSS) have been installed as instances of this SAP system.

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

Make sure that you stop, archive, and store the MDM repositories that you want to reuse. In the SAPinst uninstallation procedure you can keep the Archive folder and other folders (see below). You cannot delete an SAP system remotely. If you delete network-wide users, groups, or service entries in an environment with Network Information System (NIS), other SAP installations might also be affected. Make sure that the users, groups, and service entries to be deleted are no longer required.

Prerequisites This description assumes that you have installed your SAP system with standard SAP tools

according to the installation documentation.

You are logged on as user root. If the saposcol process on the host where you are working has been started from the SAP system that you want to delete, stop the process using the command saposcol -k. If there are other SAP systems on the host, log on as user <sapsid>adm of the other SAP system and start saposcol from there using the command saposcol -l.

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

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 asks you which SAP instances you want to delete. Note the difference between central and distributed systems:

If you want to delete a central system (all instances reside on the same host), you can do this in one SAPinst run.

If you want to delete a distributed system, you have to run SAPinst to delete the required instances locally on each of the hosts belonging to the SAP system.

SAPinst only stops local instances automatically. To delete system directories mounted from an NFS server, make sure that you run SAPinst on the NFS server.


72 October 2011

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

Configuration files (.ini)

Log files

Archives (MDS only)

Distribution files (MDS only)

Reports (MDS only)

If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but not as directories on the local file system, you have to remove them manually.


October 2011 73

© Copyright 2011 SAP AG. 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.

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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

Oracle is a registered trademark of Oracle Corporation.

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

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

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.


74 October 2011

Disclaimer and Legal Information

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express 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 Code Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Coding Samples Any software coding and/or code lines/strings (“code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the code given herein, and SAP shall not be liable for errors or damages 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 find supplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless such damages have been caused by SAP’s gross negligence or willful misconduct.

Accessibility The information contained in this documentation represents SAP’s current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with 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 written authorization.

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


October 2011 75

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 the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Dietmar-Hopp-Allee 16 69190 Walldorf, Germany (hereinafter: SAP) and you (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 property laws, 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 or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: 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 permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG

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 and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the 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 hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the 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 purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the 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 this software 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 a notice 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 and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

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


76 October 2011

c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-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 on the 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 the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known 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 or lost profit.

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

E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies 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 this obligation.

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

3. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.


mdm installation guide

Documents

svcadm enable svc

sap erp ecc

exe profile global

swdc support packages

regular tcp ip ports

sap management consoleyou

red hat linux

mdm ccms plug