MDM Upgrade Guide THE BEST RUN. CUSTOMER SAP NetWeaver Master Data Management 7.1 Document Version: 4.7 May 2019

(1)

CUSTOMER

SAP NetWeaver Master Data Management 7.1 Document Version: 4.7 – May 2019

MDM Upgrade Guide

(2)

Content

1 Introduction. . . .6

1.1 About this Document. . . .6

1.2 Required Documentation for Installing MDM. . . .7

SAP Notes for Previous MDM 7.1 Releases. . . 8

2 Planning the Upgrade. . . .9

2.1 Dev/Test and Productive Environments. . . 9

2.2 Preparatory Tasks. . . .11

Download the MDM 7.1 Installation Package. . . .11

Adapt API Calls. . . 12

Adapt CLIX Command Scripts (MDM 5.5 Upgrade Only). . . 13

Update Maps in Test Environment (MDM 5.5 Upgrade Only). . . .13

Stop Productive Use of MDM. . . .14

Back Up the MDM Environment. . . .15

2.3 Changes in Platform Support. . . .15

2.4 Visual C++ Security Updates. . . 16

3 Performing the Upgrade. . . .18

3.1 Install MDM 7.1. . . 18

3.2 Installation Folder - Content Copy (MDM 5.5 Upgrade Only) . . . .19

3.3 Upgrading Master / Slave Environments. . . .21

3.4 MDM 7.1 Server Start. . . .22

3.5 Connecting with Clients to MDM Server in Secure Mode (SSL). . . 23

Connect with MDM Console to MDM Server in Secure Mode (SSL). . . .23

Connect with Other Rich Clients to MDM Server in Secure Mode (SSL). . . .24

3.6 Update Repositories. . . .25

Mount all (Test/Productive) Repositories. . . .25

Upgrading from a Version Earlier than MDM 7.1 SP04. . . 26

Update Each Repository. . . .26

Transport Updated Import and Syndication Maps. . . .28

Setting the Number of Languages on an IBM DB2 Database. . . 28

3.7 Perform Component-Specific Activities. . . 29

Master Data Server (MDS). . . .29

MDM Import Server (MDIS). . . 30

MDM Syndication Server (MDSS). . . 31

MDM Publisher (MDLS). . . 33

MDM JAVA API . . . .34

(3)

MDM ABAP API . . . 34

MDM Monitoring and Supportability Environment. . . .36

Enterprise Portal Content. . . .38

MDM Web Dynpro Components. . . 38

MDM Collaborative Processes for Material. . . .40

4 Additional Post-Upgrade Activities (MDM 5.5 Upgrade Only). . . . 41

4.1 Update Import Maps from MDM 5.5. . . 41

4.2 Update Syndication Maps from MDM 5.5. . . 42

4.3 Synchronize Distribution Folder Content from MDM 5.5. . . .42

4.4 Perform Component-Specific Upgrade from MDM 5.5. . . .43

SAP Exchange Infrastructure Activities. . . 43

MDM Web Services. . . 43

MDM iViews. . . 44

Web UIs. . . 44

MDM Enrichment Architecture. . . 45

4.5 Save MDM 5.5 Log Files. . . .46

4.6 Replacing MDM 5.5 CLIX Commands. . . .46

4.7 Uninstall MDM 5.5 SP05/SP06. . . 48

(4)

Document History

Version / Date Description

4.7 / May 2019 ● Guide updated for MDM 7.1 SP20

● Changes in support for SP20. See Changes in Platform Support [page 15]

4.6 / December 2018 ● Guide updated for MDM 7.1 SP19

● Changes in support for SP19. See Changes in Platform Support [page 15]

4.5 / June 2017 ● Guide updated for MDM 7.1 SP18 to support installation with Software Provisioning Manager

4.4 / December 2016 ● Guide updated for MDM 7.1 SP17 4.3 / June 2016 ● Guide updated for MDM 7.1 SP16

● Changes in support for SP16. See Changes in Platform Support [page 15].

● Changes in support for SP15. See Changes in Platform Support [page 15].

4.1 / May 2015 ● Guide updated for MDM 7.1 SP14

● Changes in platform support for SP14. See Changes in Platform Support [page 15].

● Changes in platform support for SP13. See Changes in Platform Support [page 15].

● Added note that you cannot use Maintenance Optimizer in SAP Solution Manager (MOPZ) to upgrade MDM components - see SAP Note 1596063.

● Standardized the format of this guide.

3.5 / March 2014 ● Guide updated for MDM 7.1 SP12

● New support of databases for SP12.

● New support of OS version and databases for SP11.

3.3 / March 2013 ● Guide updated for MDM 7.1 SP11

● New support of OS version and databases for SP11.

● Configure new mds.ini file options and repository properties before starting reposito

ries.

● A new MDM ABAP API software component is available to support NetWeaver 7.31 and later.

3.2 / September 2012 ● Renamed section 2.3.1 to Changes in Platform Support. This section describes changes in platform support from the previous release and is not a complete list of supported platforms.

● Updated links to MDM 7.1 Documentation Center to http://help.sap.com/nwmdm71 .

(5)

Version / Date Description

3.1 / August 2012 ● Guide restructured to clarify the upgrade processes from previous MDM 7.1 SP re

leases and from MDM 5.5.

● Guide updated for MDM 7.1 SP09.

● Updated information about supported OS versions and MaxDB client versions for MDM 7.1 SP09.

● Updated information for server .ini configuration files to connect servers in secure mode.

● MDM applications on UNIX and Linux should not be configured to use secure connec

tions to SAPStartSrv .

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

● To connect MDM Web Dynpro components to the MDM Server, you must define an MDM destination. To define an MDM destination in MDM 7.1 SP08, you must install one of the SAP NetWeaver AS Java servers.

2.9 / May 2011 ● Guide updated for MDM 7.1 SP07.

● Updates on using SSL (Secure Sockets Layer), related to:

○ Using master/slave with SSL.

○ Connecting with clients to MDM server in secure mode.

○ Enabling MDIS to connect to MDM server in secure mode.

○ Enabling MDSS to connect to MDM server in secure mode.

○ Enabling MDLS to connect to MDM server in secure mode.

● New software components, including support for NW 7.3.

2.7 / Jan 2011 ● Guide updated for MDM 7.1 SP06.

● Addition to preparation steps for installing Microsoft Visual C++ security updates for MDM 7.1 SP05 and for MDM 7.1 SP06.

● Updates for MDM Web Dynpro components:

○ Before upgrading from MDM 7.1 SP04 to MDM 7.1 SP05 you must save configurations of MDM Web Dynpro components. This is also recommended for upgrades to other versions.

○ Starting in MDM 7.1 SP05, the name of the component 'MDM Web Dynpro Config- urator' was changed to 'MDM Web Dynpro Configuration Manager' ('Configuration Manager').

● Updated that you cannot install the MDM 7.1 Master Data Server on a server that is running other SAP programs, such as the MDM 5.5 Server, with the same SID.

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

2.4 / Jul 2010 New software component added: MDM Collaborative Processes for Material.

(6)

1 Introduction

This document should be used by customers who are:

● Upgrading the service pack level of their MDM 7.1 installation

● Upgrading from MDM 5.5 SP06 in a Productive environment



Note

This document does not cover upgrading from MDM 5.5 SP05 or earlier. To upgrade from these SP releases, first follow the instructions in the MDM 5.5 SP06 Upgrade Guide.

When planning an upgrade from MDM 5.5 SP06 (henceforth "MDM 5.5") , or from any previous MDM 7.1 support package (SP) release, refer to the MDM Upgrade Guide and the MDM Installation Guide before you begin the upgrade process. Before you start the upgrade process, make sure that you have the latest version of these documents.

This guide provides the following information:

● Preparatory and pre-installation tasks

● Post installation setup and configuration tasks required to complete the upgrade process Instructions for performing the MDM installation are in the MDM Installation Guide.

For information about new MDM 7.1 features and functionality, refer to the MDM 7.1 Release Notes.

You can find the latest version of the MDM documentation on the SAP Help Portal at help.sap.com/nwmdm71.

1.1 About this Document

This document describes the process required to upgrade to the latest SP release of MDM 7.1 from:

● Any previous support package (SP) of MDM 7.1

● MDM 5.5 SP06

The information in this guide is organized as follows:

Chapter 1 Introductory information for all upgrades.

Chapter 2 Planning and preparatory tasks for all users upgrading from an earlier MDM 7.1 SP release or from MDM 5.5 SP06.

Chapter 3 The upgrade process and post-upgrade tasks for all users upgrading from an earlier MDM 7.1 SP release or from MDM 5.5 SP06.

Chapter 4 Additional post-upgrade tasks required only when upgrading from MDM 5.5.

(7)

1.2 Required Documentation for Installing MDM

The following sections list the documentation needed for the installation:

● Information on the SAP Help Portal

● SAP Installation Notes

Information on SAP Help Portal

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

SAP Installation Notes

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

SAP Note Number Title Description

2740024 SAP NetWeaver MDM 7.1 SP20 Release This note contains information about the current MDM 7.1 support package.

2751450 SAP Systems on Windows Server 2019 This note contains information about deploying and using SAP systems on Windows Server 2019.

2367941 MDM Servers Installation Moved to

SWPM

SAP NetWeaver MDM 7.1 SP17 and above installation/update processes are now part of the Software Logistics Toolset 1.0 (Software Provisioning Man

ager 1.0 SP18 and higher when availa

ble).

1680045 MDM Servers Installation with SWPM

SP19

The SAP NetWeaver MDM 7.1 SP18 in

stallation/update processes are now part of the Software Logistics Toolset 1.0 (Software Provisioning Manager 1.0 SP19 and higher when available).

(8)

SAP Note Number Title Description

1249503 MDM Installation Note Most recent information and best prac

tices about the MDM installation proce

dure. The MDM Installation Note com

plements this MDM Installation Guide.

1244358 MDM 7.1 Release Restriction Note This note contains the restrictions of the current MDM 7.1 support package.

1.2.1 SAP Notes for Previous MDM 7.1 Releases

SAP Note Number Title

1070163 SAP NetWeaver MDM 7.1 Release (for the first MDM 7.1 release)

1295253 SAP NetWeaver MDM 7.1 SP01 Release

(9)

2 Planning the Upgrade

When planning your upgrade process, keep Productive use of the MDM system in mind to minimize system downtime during the upgrade process.

We strongly recommend that you update all applications in your MDM system to the same SP release.

If you are upgrading from an MDM 7.1 version earlier than SP06, note that multiple instances of MDM are now supported on the same MDM host machine. Each instance must be installed separately and requires a different SID and different listening ports.

If you are upgrading from an MDM 7.1 version earlier than SP07, you can now install MDM with SSL. This is configured using one of the following modes: Unencrypted , SSL or Both . The installation type is configurable in the MDM server .ini files.

The process of upgrading an existing MDM landscape differs if you have only a Productive landscape or a two- tier installation consisting of a Development or Test (Dev/Test) environment and a Productive environment. If you have a development, a test, and a number of Productive environments (one master and n slaves), the upgrade process is the same as for the two-tier environment.



Note

You cannot use Maintenance Optimizer (MOPZ) in SAP Solution Manager to upgrade MDM components.

For more information, see SAP Note 1596063 .

2.1 Dev/Test and Productive Environments

Your current MDM environment can be a Productive environment or a project-specific test environment.

If you have a Dev/Test environment, we recommend that you test the upgrade here before starting the upgrade of the Productive environment. You should provide an environment-specific upgrade plan for the Dev/Test environment first.

The complete upgrade process typically starts the Dev/Test environment and ends with the Productive environment.



Note

To minimize the downtime of your Productive system, perform all preparatory steps before stopping the running Productive MDM environment.

The following sections specify the order of the steps in a complete upgrade, starting with the Dev/Test environment and finishing with the Productive environment.

(10)

Download the Installation Package

☐

Download the new MDM 7.1 installation package.

Prepare the Test Environment (TE)

☐

If you have custom applications using ABAP API, Java API or CLIX, you might need to adapt and update these applications.

☐

Clean up the existing MDM environment and stop its use (Stop Productive Use of MDM [page 14]).

☐

Back up your existing MDM Dev/Test environment (Back Up the MDM Environment [page 15]).

Perform Upgrade Steps in the Dev/Test Environment (TE)

☐

Install the new MDM 7.1 software components.

☐

If your installation includes SSL, configure the server .ini files.

☐

Start the MDM 7.1 Server (MDM 7.1 Server Start [page 22]).

☐

Copy the PE repository archive to the MDM 7.1 TE and unarchive it there.

☐

Update the repository in MDM 7.1 TE (Update Repositories [page 25]).

☐

Start the repository with an index update (Update Each Repository [page 26]).

☐

MDM 5.5 upgrade only: Update and test import and syndication maps.

☐

Transport import and syndication maps (Transport Updated Import and Syndication Maps [page 28]).

☐

Perform all MDM-component-specific activities (Perform Component-Specific Activities [page 29]).

☐

Upgrade MDM environmental applications.

○ If SAP Netweaver Portal is part of the Test environment, upgrade the portal content.

○ If your program contains custom programs using MDM ABAP API, test the ABAP programs.

○ If your program contains custom programs using MDM Java API, update, if required, and test the Java programs (Adapt API Calls [page 12]).

○ If you used CLIX command scripts, rework these, if required (Adapt CLIX Command Scripts (MDM 5.5 Upgrade Only) [page 13]).

Perform Upgrade Steps in the Productive Environment (PE)

☐

Clean up the Productive MDM environment and stop its use (Stop Productive Use of MDM [page 14]).

☐

Back up the Productive MDM environment (Back Up the MDM Environment [page 15]).

☐

Install the new MDM 7.1 software components.

(11)

☐

If your installation includes SSL, configure the server .ini files.

☐

Start the MDM 7.1 Server (MDM 7.1 Server Start [page 22]).

☐

Update the existing repository (Update Repositories [page 25]).

☐

Start the repository with an index update (Update Each Repository [page 26]).

☐

Delete all ports from the repository (Transport Updated Import and Syndication Maps [page 28]).

☐

Delete all import and syndication maps from the repository (Transport Updated Import and Syndication Maps [page 28]).

☐

Import schema containing all ports and updated maps from MDM 7.1 TE (Transport Updated Import and Syndication Maps [page 28]).

☐

Perform all MDM-component-specific activities (Perform Component-Specific Activities [page 29]).

☐

Upgrade MDM environmental applications based on experience from the TE upgrade.

○ If Enterprise Portal is assigned to the Test environment, upgrade the portal content.

○ If you have ABAP API programs, transport upgraded ABAP programs from TE into PE if possible.

○ If you have Java API programs, transport upgraded Java programs from TE into PE if possible.

○ Copy reworked CLIX command scripts from TE.

Perform Follow-Up Activities (MDM 5.5 Upgrade Only)

☐

Test MDM 5.5 functionality in MDM 7.1.

☐

Uninstall MDM 5.5 components (optional).

2.2 Preparatory Tasks

The following sections describe preparatory tasks before you begin your upgrade.

2.2.1 Download the MDM 7.1 Installation Package

Download the MDM 7.1 installation package from SAP Software Download Center and prepare it for installation, as described in the MDM Installation Guide.

Use the downloaded installation package to install both the Test environment and the Productive environment.

For more information, see the MDM Master Guide and the MDM Installation Guide for your platform .

(12)

2.2.2 Adapt API Calls

COM API (MDM 5.5 Upgrade Only)

MDM 5.5 Upgrade only:

The COM API is available in MDM 7.1 with a functionality setup identical to that of MDM 5.5. However, we do not recommend continuing the use of MDM COM API. Instead, use the .NET API, is which is available in MDM 7.1 and provides the same set of functions as the MDM 7.1 Java API.

Java API

If you are upgrading from an MDM version earlier than MDM 7.1 SP07, a new software component is now provided together with the Java API component:

● MDM_CONNECTOR 710.700 for NetWeaver 7.0

● MDM_CONNECTOR 710.711 for NetWeaver 7.11 and up

The MDM packages are installed in a later upgrade step, but the API package must be installed before upgrading MDM to obtain all the information, such as signatures, needed to perform the adaptation:

One-Tier Environment

We recommend preparing the API caller adaption before you perform the upgrade activities.

1. Back up all programs that use the Java API in the appropriate development environment.

2. Adapt the programs following the guidelines specified in this guide.

3. Test the adapted programs directly after the upgrade.

Two-Tier Environment In your Test environment:

1. Back up all programs that use the Java API in the appropriate Test environment.

2. Adapt the programs following the guidelines specified in this guide.

3. After upgrading the Test environment, test the adapted programs locally.

4. Provide the adapted programs to the Productive environment.

In the Productive environment:

1. Back up all programs that use the Java API in the appropriate development environment.

2. Replace the old programs with the ones tested in the Test environment as part of the upgrade process.

(13)

Java API MDM4J is no longer shipped with MDM 7.1. MDM 7.1 provides the new version of the JAVA API only. For information about migrating from the previous Java API to the new Java API, refer to MDM 5.5 SP06 – Java API Migration Guide on the Service Marketplace:

http://service.sap.com/installMDM -> SAP NetWeaver MDM 5.5 -> Programming Interfaces.

2.2.3 Adapt CLIX Command Scripts (MDM 5.5 Upgrade Only)

The following commands are obsolete in MDM 7.1 and must be replaced:

● mdsStart

● mdsStop

To save time during the upgrade, migrate all MDM 5.5 CLIX scripts to MDM 7.1 before you start the upgrade. Review existing CLIX scripts (or .bat files) for mdsStart and mdsStop commands and replace them with some of the new iC com

mands. See Replacing MDM 5.5 CLIX Commands [page 46] for details regarding the new CLIX commands.

2.2.4 Update Maps in Test Environment (MDM 5.5 Upgrade Only)

All MDM 5.5 import and syndication maps must be updated for MDM 7.1 before any schema migration or transport activity can occur on the upgraded repository. Updating maps in the Dev/Test environment reduces the downtime required in the Productive environment.

Import Manager attempts to automatically update all of the import maps in a repository, but due to the complexity of the process, you might need to update some import maps manually (Update Import Maps from MDM 5.5 [page 41]). All up

dated import maps should also be tested in the Dev/Test environment.

Syndicator can update syndication maps automatically (Update Syndication Maps from MDM 5.5 [page 42]).

After all maps are updated, transport the repository ports and updated maps from the Dev/Test environment to the Pro

ductive environment.

(14)

2.2.5 Stop Productive Use of MDM

Context

Before the complete system can be backed up and upgraded, you must stop all components of your MDM system on this host.

Procedure

1. Make sure that no users are actively logged on (Data Manager, Import Manager, Syndicator, Publisher, Image Manager, Indexer, plus all components accessing MDM from ABAP API, JAVA AP I or Portal).

2. From the MDM Console:

a. Check which users are connected to a repository by choosing Admin® Connections in the hierarchy tree of the specific repository. Clean up the inbound ports in Productive scenarios.

b. Go to directory structure MDM_HOME/Distribution. For all connected MDC (Master Data Clients) and all connected repositories, check if the folders called “Ready” or “Exception” contain data files waiting for an import (Ready) or waiting for correction after an unsuccessful import (Exception).

c. Clean up the folders by importing the data or correcting the errors and then importing the data. You should perform this step to get a clean final status of the existing MDM environment.

d. Stop external applications from providing any further MDM import files to the MDM environment, for example by stopping the SAP XI/PI communication channels.

3. Use the MDM Console to stop all active repositories. All applications running on the current host are stopped (for example, Web applications calling the MDM host directly must be stopped, while Web applications relying on a slave can continue).

4. MDM 5.5 upgrade only: Close the SAP XI/PI communication channels that provide import data for the MDM repositories.

5. MDM 5.5 upgrade only: For each repository, check the Import Server distribution folders:

○ Exception folders: Check for exceptions and try to perform the import for these import files manually with Import Manager.

○ Ready folders: If import files are ready to be imported, they can be imported into the MDM 5.5 environment or copied to the new MDM 7.1 environment.

6. Verify and repair the repositories and ensure that there are no errors.

7. Use MDM Console or a CLIX-based batch procedure to archive all repositories that you want to reuse after the upgrade. Perform this step directly after checking and repairing all repositories.

We recommend that you copy the archives from the MDM file location to a specific backup location.

8. Stop all servers based on the current host (Master Data Server, Master Data Layout Server, Master Data Import Server and Master Data Syndication Server). Ensure that all these servers are stopped in Windows Services.

(15)

2.2.6 Back Up the MDM Environment

Context

Perform the following steps to back up the MDM environment.

Procedure

1. Archive all repositories used.

Perform this step after checking and repairing all repositories (Stop Productive Use of MDM [page 14]).

2. Back up the MDM installation file system

Copy the complete path for the MDM installation to the backup location.

The standard path for Windows is <System partition>:\Program Files\SAP MDM 7.1, and for Unix, /usr/local or /opt.



Note

If you made changes to the mds.ini, mdss.ini, or mdis.ini files, you may have to reapply the changes after upgrading. It is therefore important that you save copies of those files.

3. Save your Computing Center Management System (CCMS) monitoring environment.

If you used CCMS monitoring for MDM, back up the CCMS environment on your host (the common location is <System partition>:\usr\sap\prfclog).

4. Save the SMD / Wily Introscope environment

If you used the Solution Manager Diagnostics connection or the Wily Introscope performance monitoring, you might want to save the log files (/usr/sap/ncs/log).

5. Save the MDM-specific portal environment.

Export the MDM custom portal content and download it to a local .epa file.

2.3 Changes in Platform Support

This section describes the changes in platform support for MDM 7.1 SP20.

For complete platform requirements, refer to the MDM Master Guide and the MDM 7.1 Product Availability Matrix (PAM) at support.sap.com/pam .

The following support has been added:

(16)

● AIX 7.2

● Windows Server 2019

● MaxDB 7.9 for Windows Server 2019

● MSSQL 2017 for Windows Server 2019

● Oracle 12.2 for Windows Server 2019

● DB2 10.5 for AIX 7.2

● DB2 10.5 for Linux Redhat EL7.2

● MaxDB 7.9 for AIX 7.2

● MaxDB 7.9 for Linux Redhat EL7.2

● MaxDB 7.9 for Windows Server 2016

● MSSQL 2017 for Windows Server 2016

● Oracle 12.2 for AIX 7.2

● Oracle 12.2 for Linux Redhat EL7.2

● Oracle 12.2 for Linux Suse SLES12

● Oracle 12.2 for Windows Server 2016

HP-UX and IBM i are no longer supported due to lack of use. Support for other platforms and databases remains as for the previous release.

MDM 5.5 Upgrade Only:

The Windows 32-bit version of MDM Import Server is not released with MDM 7.1, meaning that MDM 7.1 Import Server does not support Excel or Access files. MDM Import Manager continues to support Excel and Access files.

2.4 Visual C++ Security Updates

The following Microsoft Visual C++ security updates must be installed on your Windows server and client machines.

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

● Microsoft Visual C++ 2008 SP1 Redistributable Package

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

To check whether you need to install the security update:

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

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

If the version is 8.0.50727.4053, or greater, you already have the update.

For more information, see the Microsoft Knowledge Base Article KB973544 and SAP Note 1375494 . To install Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update:

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

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

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

(17)

● On a Win32 server, download the package from: http://www.microsoft.com/downloads/details.aspx?

familyid=a5c84275-3b97-4ab7-a40d-3802b2af5fc2&displaylang=en .

● On a Win64 server, download the package from: http://www.microsoft.com/downloads/details.aspx?

familyid=ba9257ca-337f-4b40-8c14-157cfdffee4e&displaylang=en

(18)

3 Performing the Upgrade

The steps required for upgrading MDM depend on the MDM components you use.

1. Install MDM 7.1 using the Update option of SWPM.

2. Update all repositories.

3. Perform component-specific activities for:

○ Master Data Server (MDS)

○ Master Data Import Server (MDIS)

○ Master Data Syndication Server (MDSS)

○ MDM Publisher

○ MDM COM/JAVA API

○ MDM ABAP API configuration

○ Generic upgrade specific issues

○ MDM supportability

○ MDM portal content / URL / iViews

○ MDM Web Dynpro components

3.1 Install MDM 7.1

Use the Update option of SWPM to implement new support packages or patches for upgrading MDM servers.

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 on which you installed the first MDM instance.

For details about MDM server installation using the Update option, refer to the MDM Installation Guide for your platform.



Note

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 Windows x86_64 host, all other MDS instances of this SAP system running on other Windows x86_64 hosts are updated as well.

The MDM 7.1 installation has the following parts:

● MDM servers

○ Master Data Server

○ Master Data Import Server

○ Master Data Syndication Server

○ Master Data Layout Server

(19)

MDM servers are integrated into the SAP Startup Framework, and can be handled with the standard SAP server administration applications, for example the SAP Management Console (SAP MMC). To install the MDM 7.1 servers, SAP provides new SWPM-based installers that also install the Startup Framework and the SAP MMC in your system.

● MDM GUI Clients (WIN32 only)

The installer setup for the MDM GUI components has not changed for MDM 7.1. Install the MDM

components that you need on your host in the following order (see the MDM 7.1 Master Guide for the list of components needed for your scenario):

○ MDM Console

○ Administration component (MDM CLIX)

○ MDM Data Manager

○ MDM Import Manager

○ MDM Syndicator

○ MDM Language Selector

○ MDM UoM Manager

○ MDM Image Manager

○ MDM Publisher

○ MDM Indexer

○ MDM InDesign Plug-In for publishing (according to the version of InDesign that is installed)

● Additional MDM components

○ MDM ABAP API

○ MDM .Net API

○ MDM Java API

○ MDM Connector

○ MDM Portal Content

○ MDM Enrichment Architecture

○ TREX configurator

○ MDM Web Dynpro

○ MDM Web Services

○ MDM Collaborative Processes for Material

○ MDM PI Adapter

3.2 Installation Folder - Content Copy (MDM 5.5 Upgrade Only)

MDM Servers

With the new MDM 7.1 server installation procedures, the MDM 7.1 servers are installed in a different directory structure than with MDM 5.5 (<SID> is a three-letter system ID signature).

(20)



Caution

You cannot install the MDM 7.1 Master Data Server on a server that is running other SAP programs, such as the MDM 5.5 Server, with the same SID.

[<System Drive>:]/usr/sap/<SID>/MDS<instance number>/

[<System Drive>:]/usr/sap/<SID>/MDIS<instance number>/

[<System Drive>:]/usr/sap/<SID>/MDSS<instance number>/

[<System Drive>:]/usr/sap/<SID>/MDLS<instance number>/

MDM Archive Files

MDM 5.5:

Windows: <System Drive>:\Program Files\SAP MDM 5.5\server\archives\*.a2a UNIX: $<MDM server Work directory>\archives\*.a2a

Copy the archives that you want to use in MDM 7.1 to the new folder.

[<System Drive>:]/usr/sap/<SID>/MDS<instance number>/mdm/archives

MDM GUI Clients

The folder structure of the MDM GUI components on WIN32 has not changed in MDM 7.1. The only difference is the default installation directory:

MDM 5.5: <System Drive>:\Program Files\SAP MDM 5.5 MDM 7.1: <System Drive>:\Program Files\SAP MDM 7.1



Note

In MDM 7.1, the GUI clients are installed in parallel and must be removed manually when the upgrade is finished. (In MDM 5.5 SP-specific upgrades, the GUI clients were overwritten by default).

Master/Slave Modification Data

No copy of Master/Slave modification data is required. You do not need to copy the synchronization data in the modification files because MDM slave repositories cannot be upgraded and must be rebuilt after a system upgrade.

(21)

MDM 5.5 Log Files

Save MDM 5.5 log files. MDM 5.5 log files cannot be displayed using MDM 7.1 Console because the log file format was changed from xml based in MDM 5.5 to csv based in MDM 7.1.

To keep the log files for historic reasons, we recommend that you copy them from the log folder and from the report folder to an extra folder together with the MDM_Log.xsl file, which allows you to view the logs from the browser.

Windows:

● <System Drive>:\Program Files\SAP MDM 5.5\Server\Logs

● <System Drive>:\Program Files\SAP MDM 5.5\Server\Reports UNIX:

● $<MDM server Work directory>\logs

● $<MDM server Work directory>\reports

3.3 Upgrading Master / Slave Environments

If your MDM environment uses MDM master/slave technology, you must rebuild the slaves after upgrading. You cannot upgrade the slave repositories during an upgrade.

To use master/slave with SSL, the following entries in your master and slave mds.ini server files must refer to the remote server. This is necessary even if the master and slave repositories are on the same MDM server instance.

On Windows:

[MDM Server]\[Remote Server]\[Master Server Name]:[SSL Listening Port]

Service Control Security Enabled=True SSL Enabled=True

SSL Lib Path=…\usr\sap\[SID]\MDSxx\exe\sapcrypto.dll SSL Key Path=…\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse



Sample Code

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

SSL Enabled=True

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



Note

● If you change the listening mode or port on the MDM Server that contains the master after a slave has been created, the connection between the master and slave is invalidated and you must recreate the slave.

(22)

● When the listening mode is Both , the slave synchronization is via a secure connection only. Therefore, when using master/slave where the listening mode on the MDM server is Both, configure the MDM Server\Remote Server setting in the mds.ini as described above .

On UNIX and Linux:

MDM applications on UNIX and Linux should not be configured to use secure connections to SAPStartSrv.

The .ini file setting Service Control Security Enabled should be set to False.

[MDM Server]\[Remote Server]\[Master Server Name]:[SSL Listening Port]Service Control

Security Enabled=False SSL Enabled=True

SSL Lib Path=…\usr\sap\[SID]\MDSxx\exe\sapcrypto.dll SSL Key Path=…\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

3.4 MDM 7.1 Server Start

Use the MDM 7.1 Console to start the MDM 7.1 Master Data Server.

Refer to the MDM servers using one of the following syntaxes:

xx@[Server Name] where xx is the 2 digit instance number of the server or

[Server Name]:[Port]

For example, if:

● Instance=00

● Server name=srvr36

● Port=50051

The server can be mounted as:

00@srvr36 or srvr36:50051

For more information about ports of MDM Servers, see the MDM Installation Guide and MDM Release Notes.



Caution

Make sure that the MDM 7.1 Import Server and MDM 7.1 Syndication Server are stopped before performing the following upgrade tasks.

(23)

With the new MDM 7.1 installation structure, operating system independent start and stop is available. MDM servers are handled on all platforms in the same way: using the SAP infrastructure framework (SAP Startup Framework).

This is a change in handling; for detailed information refer to the MDM Installation Guide for your platform or MDM Console Reference Guide.

3.5 Connecting with Clients to MDM Server in Secure Mode (SSL)

When MDM Server is installed with SSL as the listening mode, you can only connect to the MDM servers with clients in secure mode.

When MDM Server is installed with Both as the listening mode, you can connect to the MDM servers with clients either in secure mode or in unencrypted mode.

When MDM Server is installed with Unencrypted as the listening mode, you can only connect to the MDM servers with clients in unencrypted mode.

If you are upgrading from an MDM version earlier than SP07, connect to MDM clients in secure mode by copying all the following files to the same folder in an accessible location:

● client.pse file for your MDM Server Instance that is located in ..\usr\sap\SID\SYS\exe\uc

\NTAMD64

● sapcrypto.dll for Win32. If you do not have this file, download the file from the SMP as sapcrypto.SAR.

● ticket file for your MDM Server Instance that is located in ..\usr\sap\SID\SYS\exe\uc\NTAMD64

3.5.1 Connect with MDM Console to MDM Server in Secure Mode (SSL)

Context

You can connect to an MDM Server in secure mode with the MDM Console.

(24)

Procedure

1. Mount the server.

The Mount MDM Server dialog box appears.

2. Select the Secure Connection checkbox.

3. Specify the MDM server name using one of the following options:

○ [instance number]@[server]

○ [server]:[listening port]

○ Server name only – this option can only be used for a default instance that is on the default port.

4. In the Key File field, specify the path to the client.pse file.

5. In the SSL Library field, specify the path to the sapcrypto.dll file.



Example

3.5.2 Connect with Other Rich Clients to MDM Server in Secure Mode (SSL)

Context

You can connect to an MDM Server in secure mode with rich clients other than the MDM Console.

Procedure

1. In the Connect to MDM Repository dialog box, click ....

The Choose Repository dialog box appears.

(25)

2. Select the Secure Connection checkbox.

3. In the Key File field, specify the full path to the client.pse file.

4. In the SSL Library field, specify the full path to the sapcrypto.dll file.

If you are using the Visio workflow plugin, do not use the Browse button (…) to select the files. Instead, enter the full path to the files.

5. Specify the MDM server name using one of the following options:

○ [instance number]@[server]

○ [server]:[listening port]

○ Server name only – this option can only be used for a default instance that is on the default port.

6. In the Repository dropdown list, choose the repository.

7. Choose OK.

3.6 Update Repositories

MDM 7.1 SP10 includes new mds.ini file options for strong passwords and for other parameters, and new repository property options. Before starting your repositories, set all mds.ini file options and repository property options that you require. See Master Data Server (MDS) [page 29] for information about updating mds.ini file options.

For more information about these mds.ini file options, see the MDM Security Guide at help.sap.com/

nwmdm71.

3.6.1 Mount all (Test/Productive) Repositories

Mount all repositories that should be running in the upgraded MDM 7.1 environment.

(26)

MDM 5.5 Upgrade Only

:Do one of the following to use the MDM 5.5 repositories with the new MDM 7.1 environment:

● Mount the MDM 5.5 repositories. In this case the MDM 5.5 installation can no longer use these repositories.

● Unarchive the MDM 5.5 repository archives and rename the repositories.

3.6.2 Upgrading from a Version Earlier than MDM 7.1 SP04

Context

If you are upgrading from a version that is earlier than MDM 7.1 SP04, perform the following steps.

Procedure

1. In the MDM Console, choose Verify Repair for each repository before starting them in the upgraded MDM 7.1 version.

2. Transport expressions, assignments, or validations that use lookup values or relationships:

a. Open each expression.

b. Delete the referenced lookup value.

c. Add it again to the expression.

3. As of MDM 7.1 SP04, the Code Field for Masks and Named Searches is unique and does not allow NULL values. Perform the following operations manually in the Data Manager :

a. Reenter the lookup values used in any validations, expressions or assignments.

b. Add codes for named searches and masks, and assign main tables to the masks.

4. In the MDM Console, choose Verify Check for each repository.

3.6.3 Update Each Repository

Context

After upgrading MDM, start the new Master Data Server (MDS) and use MDM Console to update your repositories. All repositories that require updating are displayed in the MDM Console with the icon.

(27)

Perform the following steps for each repository that needs to be updated. Before you begin, ensure that the MDM Server is started and the corresponding repositories are mounted:

Procedure

1. Choose Update Repository from the context menu of each repository.

The MDM Console updates the repository so that it can be used with the latest builds. The data in the repository is automatically upgraded.

When the update is finished, the icon in front of the repository name indicates that you can connect to the repository to verify or to start it.

2. Choose Connect to Repository from the context menu and enter a user name and password.

For the standard repository templates, the default user name is Admin, and the default password is sapmdm (the password cannot be empty). Otherwise, use the user name and password that you defined in the repository.



Note

For a new repository, MDS sets the default Administrator user password to sapmdm. However, when updating an existing repository, MDS does not update the empty password values in mdis.ini and in mdss.ini. You must enter the default password in these files.

After you log on, the MDM Console displays the icon for the repository, which indicates that theMDM repository is stopped.

3. To verify the repository, choose Verify Check from the context menu. If the verification indicates errors in your repository, choose Verify Repair from the context menu.

4. To start the repository and update the indices, choose Start Update Indices from the context menu.

The MDM Console displays the icon for the repository, which indicates that the MDM repository is being started .

After successfully starting the repository, the MDM Console displays the icon, which indicates that the MDM repository is started.



Note

We recommend that you update the indices for your repositories ( Start Update Indices from the context menu) every time you upgrade the MDM components (including an upgrade at patch level).

5. Connect to the updated repositories with the MDM 7.1 Data Manager and verify that they work correctly.



Note

For a complete list of icons, see the MDM Console Reference Guide.

(28)

3.6.4 Transport Updated Import and Syndication Maps

Map updates are treated as schema changes by MDM. After all the import and syndication maps have been updated in the Dev/Test environment, use MDM Console to create a schema file for transporting all repository ports and all updated maps to the Productive environment.

MDM Console provides two methods for transporting ports and maps: schema migration and change transport (CTS+):

● With schema migration, the choice of which schema changes to add to the Productive repository is made at the time of import into the Productive repository.

● With change transport (CTS+), the choice of which schema changes to add to the Productive repository is made at the time of export from the Dev/Test environment.

When transporting ports and maps:

● All maps must be updated before they can be transported. A single outdated map will cause the entire transport operation to fail.

● All ports and maps must be deleted from the Productive repository before any schema migration or transport can occur on the Productive repository.

● If a map is being used by a port, the port must be deleted before the map can be deleted.

The ports and maps that are deleted from the Productive system are replaced with the ports and updated maps transported from the Dev/Test environment.



Note

● Change transport (CTS+) has additional requirements not covered in this document.

● SAP does not support the use of *.map files as a means of transporting maps between repositories.

For information about updating import and syndication maps from MDM 5.5, see Update Import Maps from MDM 5.5 [page 41] and Update Syndication Maps from MDM 5.5 [page 42].

3.6.5 Setting the Number of Languages on an IBM DB2 Database

If you use MDM with an IBM DB2 database, the default number of languages you can use is 17. If you have a repository with more languages, you can increase the number of languages by changing the IBMDB2 Use Long Varchar For Languages=True setting in the .ini file.

This setting is only for the IBM DB2 database. For MaxDB the limit remains 17 languages.

(29)

3.7 Perform Component-Specific Activities

MDM 7.1 is delivered as a collection of components, some of which require upgrading.

3.7.1 Master Data Server (MDS)

Upgrade the MDS configuration file: mds.ini

We recommend that you do not copy the old MDM mds.ini configuration file. When you first start the upgraded MDM 7.1 server, a new MDM mds.ini file is written in the following directory:

[<System Drive>:]/usr/sap/<SID>/MDS<instance number>/config/mds.ini Add any required changes from the old mds.ini file to the new file.



Note

Changes to the MDM configuration files mds.ini, mdis.ini, and mdss.ini become effective only after you restart the respective server.

MDM 7.1 SP10 includes new mds.ini file options for strong passwords and for other parameters. For more information about these parameters, see the What's New in MDM 7.1 SP10 document and the MDM Console Reference Guide.



Note

When upgrading from versions prior to SP07 that do not use SSL, the following line must be added to the mds.ini file:

SSL Enabled=False

The SSL key path option should be left empty.

(30)

The mds.ini configuration file in MDM 7.1 contains new parameters for the changed ABAP API connection, as described in MDM ABAP API [page 34].

MDM 7.1 does not support the following MDM 5.5 mds.ini settings:

● Protocol Log Level and Database Log Levelare replaced by Tracing Level

● ROLLING_LOG_HI is replaced by MDM Log Watermark

● Master Slave Port is obsolete

● CPU Count is replaced by Max Threads Per Operation. This setting defines the maximum number of threads used by a single operation, and not the total number of threads used by MDS. For details, refer to the MDM reference documentation.

Transfer the following settings from the MDM 5.5 mds.ini to the new MDM 7.1 mds.ini:

● SLD Registration

● Wily Instrumentation

● Wily Instrumentation Level Threshold

3.7.2 MDM Import Server (MDIS)

If you are upgrading from an MDM version earlier than SP07, the section [MDM Server]\[Remote Server]

\[Master Server Name]:[SSL Listening Port] is created in the mdis.ini file, with the following new parameters:

● Service Control Security Enabled=True (default value)

● SSL Enabled=False (default value)

In addition, the installer creates a client key file under \\<server name>\c$\usr\sap\<sid>\SYS\exe\uc

\<OS>

To enable MDIS to connect with MDS in secure mode, perform the following:

1. Change the SSL Enabled value to true. (When set to false, the connection is insecure.)

2. Copy the client key and ticket files from ...\usr\sap\<sid>\SYS\exe\uc\<OS> to C:\usr\sap

\<sid>\<MDIS Instance Folder>\sec\ .

3. Under the [MDM Server\Remote Server\<mdsInstance>@<server name>] section, add the following parameters:

SSL Lib Path=C:\usr\sap\<sid>\MDSSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\<sid>\MDISxx\sec\<clientKeyFileName>



Note

MDM applications on UNIX and Linux should not be configured to use secure connections to SAPStartSrv. Change the Service Control Security Enabled value to False.

After the installation, the following parameters are added automatically to the mdis.ini file:

Listening Mode=[Both/Unencrypted/SSL]

SSL Lib Path=C:\usr\sap\[SID]\MDSxx\exe\sapcrypto.dll

(31)

SSL Key Path=C:\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

Before starting to work with MDIS, verify that these parameters exist and are configured correctly.



Example

Listening Mode=SSL

In MDM 7.1, you can define the user name and password for mdis.ini repository sections from the MDM Console. The Password= entry is no longer used. The MDM Console can connect to MDIS, create or remove repository sections, and modify the user credentials

Transfer the following settings from the MDM 5.5 mdis.ini to the new MDM 7.1 mdis.ini:

3.7.3 MDM Syndication Server (MDSS)

\[Master Server Name]:[SSL Listening Port] is created in the mdss.ini file, with the following new parameters:

\<OS>

To enable MDIS to connect with MDS in secure mode, perform the following:

\<sid>\<MDSS Instance Folder>\sec\ .

SSL Lib Path=C:\usr\sap\<sid>\MDSSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\<sid>\MDISxx\sec\<clientKeyFileName>



Note

(32)

After the installation, the following parameters are added automatically to the mdss.ini file:

SSL Lib Path=C:\usr\sap\[SID]\MDSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

Before starting to work with MDSS, verify that these parameters exist and are configured correctly.



Example

Listening Mode=SSL

In MDM 7.1 auto syndication is always enabled; therefore the MDM 5.5 mdss.ini setting, Auto Syndication Task Enabled is now obsolete.

User credentials now maintained from MDM 7.1 Console

In MDM 7.1, you can define the user name and password for mdss.ini repository sections from the MDM Console. The Password= entry is no longer used. The MDM Console can connect to MDSS, create or remove repository sections, and modify the user credentials

Multi-tasking: Multiple concurrent tasks within each repository

MDSS can run multiple concurrent tasks within each repository by launching up to three tasks for each remote output sys

tem.

● One task is for continuous ports. After the last port has been processed, the task waits for Auto Syndication Task Delay (seconds), and then processes the ports again from the beginning.

● Another task is for manual ports (jobs requested by Workflow or Java API). Its delay is defined by the Manual Syndication Task Delay (seconds) parameter.

You can specify both settings in the global or repository-specific section. In this way the global setting can be overridden for a specific repository.

Periodic ports are processed by another task within each remote system. They do not use a mdss.ini parameter. Rather, the task has a sorted list of the next syndication times and is idle until the next port is due to be executed.

Transfer of configuration file settings

Transfer the following settings from the MDM 5.5 mdss.ini to the new MDM 7.1 mdss.ini:

(33)

3.7.4 MDM Publisher (MDLS)

\[Master Server Name]:[SSL Listening Port] is created in the mdls.ini file, with the following new parameters:

\<OS>

To enable MDLS to connect with MDS in secure mode, perform the following:

\<sid>\<MDIS Instance Folder>\sec\ .

SSL Lib Path=C:\usr\sap\<sid>\MDLSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\<sid>\MDLSxx\sec\<clientKeyFileName>



Note

After the installation, the following parameters are added automatically to the mdls.ini file:

SSL Lib Path=C:\usr\sap\[SID]\MDSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\[SID]\MDSxx\sec\SAPSSLS.pse

Before starting to work with MDLS, verify that these parameters exist and are configured correctly.



Example

Listening Mode=SSL

In MDM 7.1, color swatches are introduced to MDM Publisher, causing the following upgrade issues:

● Previous local color declarations in non-family text and geometry have been eliminated, defaulting to black or none where appropriate.

● Color declarations in publication level styles and node level properties are transformed and preserved in an upgrade step.

● The table properties in the subsection Wrap Text Around Images have been eliminated. The functionality has been moved to the new Object Properties pane.

(34)

3.7.5 MDM JAVA API

If you are upgrading from an MDM version earlier than SP07, to work with Web Application Server (WAS) applications using the MDM JAVA API, you must deploy both the Java API package and the MDM Connector.

To connect to the WAS with SSL, you must also import the MDM Server cert.crt file into the MDMKeystore view of WAS, using the NetWeaver Administrator service Keys and Certificates.

The cert.crt file is located in …usr\sap\[SID]\sys\exe\uc\[OS Type]\cert.crt.

For example:

\\abc60200359\c$\usr\sap\Q59\SYS\exe\uc\NTAMD64\cert.crt

The Java API components should be deployed according to the instructions in the MDM Java and .NET API Guide:

● MDM JAVA API 7.1

● MDM JAVA API DOC 7.1

● MDM_CONNECTOR 710.700 is to be used for connections to NW 7.0

● MDM_CONNECTOR 710.711 is to be used for connections to NW 7.1 and up

If you are upgrading from an MDM version earlier than SP07, separate portal content components are now provided to support NW 7.3:

● MDM EP 7.1 7.11

● BP MDM TECHNOLOGY 7.1

● BP MDM TECHNOLOGY 7.1 7.3

● BP MDM APPLICATION 7.1

● BP MDM APPLICATION 7.1 7.3

To use the MDM Java API, deploy the JAVA API package according to the Getting Started with Java API Guide for your platform.

3.7.6 MDM ABAP API

● If you are upgrading from an MDM version earlier than SP04, the new parameter SAP RFC Hostname is now available in the mds.ini file.

● If you are upgrading from an MDM version earlier than SP07:

○ You can now configure MDM ABAP API to use a secure network connection (SNC).

○ The MDM ABAP API (MDM TECHNOLOGY 7.10 710 software component) is supported on NetWeaver 7.3.

● Starting from MDM 7.1 SP10, a new MDM ABAP API (MDM TECHNOLOGY 7.10 731) software component is available to support NetWeaver 7.31 and later.

For more information, see the MDM ABAP API Guide.

(35)

With MDM 7.1, the MDM ABAP API has replaced the physical data communication from the ABAP system to the Master Data Server. Instead of the former direct socket communication using the MDM network protocol, the SAP RFC (Remote Function Call) technology now is used.

The ABAP interface layer is kept consistent, so there is no need to rewrite the ABAP code.

Perform the following steps during the upgrade.

1. Deploy the MDM 7.1 ABAP API package to the ABAP client.

2. Upgrade the Master Data Server configuration to the new RFC-based communication technology.

Deploy the new MDM ABAP API

Deploy the MDM 7.1 ABAP API package to your ABAP system using the transaction SAINT (apply the most recent patch of the following installation packages):

● MDM TECHNOLOGY 7.10 700

● MDM TECHNOLOGY 7.10 710

When the MDM 7.1 ABAP API is deployed, all providers for MDM 5.5 SP06 Patch 3 and lower are removed.

More information: Application help for transaction SAINT.

Change the ABAP API configuration on Master Data Server

Adapt the configuration of the ABAP API on the Master Data Server to the new concept. For more information see the MDM ABAP API Guide.

With MDM 7.1 the configuration files allow.ip and deny.ip become obsolete for the MDM ABAP API only – they are still used by other MDM components. For more information, refer to the documentation of the MDM component you are using.

1. Define SAP gateways.

For each SAP gateway, set a value in the SAP RFC Gateways parameter. Separate the values with a comma (,).

GWHOST=<GW Host> GWSERV=<GW Service> [, ...]

Example:

SAP RFC Gateways= GWHOST=host1 GWSERV=sapgw21 , GWHOST=host3.yourdomain GWSERV=3345

Using only a numeric value for mapping <GW Service> (TCP port to which the SAP Gateway listens), works inde

pendently from port mappings maintained in file services on the local system (for example, using a value of 3321 instead of sapgw21). Refer to the SAP Gateway documentation for details on the numbering scheme of ports used by SAP NetWeaver. In parallel, you can use the ABAP transaction SMGW to find details about the parameters of the gate

way, especially values for Gateway Host and Gateway Service. To check whether the Master Data Server is properly registered, choose Goto Logged on clients and verify that the Master Data Server host appears on the list. If not, check the logs for the Master Data Server through the MDM Console to see whether gateway registration was successful, and if not, which errors occurred.

2. Define trusted systems.

For each SAP trusted system, enter a value in parameter Trusted SAP Systems=: Trusted SAP Systems= [<sysId>[:<partnerHostname>]] [,

<sysId>[:<partnerHostname>]]

Example

Trusted SAP Systems= SID:host4, XYZ , X01 , Y02, AAA

(36)

If an MDM ABAP API function returns the exception CX_MDM_USAGE_ERROR with a message text like The system with ID <sysID> (partner host <partnerHostname>) is not trusted, the parameter

Trusted SAP Systems= is not yet properly configured. Use the <sysId> and <partnerHostname> of the error message and append it to the mds.ini entry as mentioned above. Keep in mind that <partnerHostname>

is optional and is used only for special purposes like limiting the trusted connection on dedicated application servers.

Especially when setting up connections to ABAP systems, it is appropriate to start with simply trusting the <sysId>. Configure the RFC connections

With transaction MDMAPIC you can create the connections to the RFC servers. You check the created connections by call

ing transaction SM59.

3.7.7 MDM Monitoring and Supportability Environment

System Landscape Directory (SLD) Registration

To enable the SLD registration of an MDM server, in the server configuration file, set the SLD Registration=True configuration parameter.

If you did not use the SLD registration for a previous MDM version, you can perform SLD registration when you upgrade in an additional installer step. Provide the following data:

● SLD Hostname

● SLD Username/Password

● SLD Port

The files slddest.cfg and slddest.cfg.key are created in the MDM 7.1 folder, <System Drive:>:\usr

\sap\<SID>\SYS\global.



Note

To use the MDM 7.1 SLD registration you must implement version 1.5.32 of the SMD CIM model.

(37)

If you registered the MDM 5.5 servers to the SLD, you can copy the following two files from their MDM 5.5 folder to the MDM 7.1 folder, (<System Drive:>:\usr\sap\<SID>\SYS\global ):

Slddest.cfg Slddest.cfg.key

In MDM 7.1, the SLDReg Utility Path setting in the Master Data Server configuration files mds.ini, mdis.ini, and mdss.ini is obsolete.

The MDM servers retrieve all path information from environment settings defined during installation by SAP Start Service Framework. These settings are part of the server configuration files.

MDM CCMS Agent Plug-In Activities

If the SAP Computing Center Management System (CCMS) environment did not exist in the previous MDM setup, perform the following steps using the Installer:

1. Create the CCMS environment /usr/sap/prfclog.

2. Provide the specific CCMS Installer.

3. Unpack the CCMS agent to /usr/sap/prfclog. Register the CCMS agent to central monitor (CEN) using the shell command: sapccmsr –R –f csmconf. This creates /usr/sap/prfclog/sapccmsr and adds a file sapccmsr.ini.

4. Stop the CCMS agent.

5. Copy the mdm_ccms library (OS dependent) from [<System Drive>:]/usr/sap/<SID>/

MDS<instance number>/exe to [<System Drive>:]/usr/sap/prfclog/sapccmsr 6. Modify sapccmsr.ini to add the command to start the plugin mdm_ccms.dll.

7. Start the CCMS agent again.

If the CCMS environment was running in MDM 5.5, the only task is to replace the old mdm_ccms.dll with the newly deliv

ered one. Copy the MDM CCMS plug-in mdm_ccms.dll from the

[<System Drive>:]/usr/sap/<SID>/MDS<instance number>/exe folder to the installed CCMS agent (can be kept from MDM 5.5 installation: [<System Drive>:]/usr/sap/prfclog/sapccmsr ). The old

mdm_ccms.ini file is no longer required.

(38)

SMD integration / Wily Introscope (MDM 5.5 Upgrade Only)

If SMD integration was set up in MDM 5.5, no manual upgrade step is necessary in MDM. The new MDM 7.1 installation structure sets up all necessary path information, so Wily Introscope integration is running if the parameter is set in the server configuration .ini file.

3.7.8 Enterprise Portal Content

If you are upgrading from an MDM version earlier than SP07, separate portal content components are provided to support NW 7.3:

● MDM Enterprise Portal 7.1 7.11

● BP TECHNOLOGY 7.1 7.3 / iViews

● BP APPLICATION 7.1 7.3 / iViews

SAP Note 1235338 (Upgrade portal content from MDM 5.5 SP06 to MDM 7.1) provides detailed instructions on how to upgrade MDM portal content to MDM 7.1.

3.7.9 MDM Web Dynpro Components

The MDM Web Dynpro components are reusable units of code that can be used as building blocks for

developing modular Web applications, and they can also be extended with Java coding. These components are used by custom-developed Web Dynpro wrapper applications, and can be used for customizing or applying different type of business logic to suit a variety of business scenarios, such as Business Process Management (BPM).

For more information about MDM Web Dynpro components, see the MDM Web Dynpro Components Reference Guide at help.sap.com/nwmdm71.

MDM Destination for MDM Web Dynpro Components

If you are upgrading from an MDM version earlier than SP08, to connect MDM Web Dynpro components to the MDM Server you must define an MDM destination. To define an MDM destination, ensure that you have installed one of the following SAP NetWeaver AS Java servers:

● SAP enhancement package 1 SP05 (or higher ) for SAP NetWeaver Composition Environment (CE) 7.1

● SAP NetWeaver Composition Environment (CE) 7.2

(39)

● SAP NetWeaver 7.3

For more information about creating an MDM destination for MDM 7.1 SP08, see the How to Create MDM Connections with the MDM Destinations Administration Tool on the SAP Help Portal at help.sap.com/nwmdm71.

MDM Web Dynpro Configuration Manager

If you are upgrading from an MDM version earlier than SP05, the MDM Web Dynpro Configuration Manager is now available with the following components: Result Set, Item Details, Search, Merge, Compare, and Match.

(In MDM 7.1 SP04, this feature was introduced as MDM Web Dynpro Configurator and provided only the following components: Result Set, Item Details, and Search.)

The MDM Web Dynpro Configuration Manager (Configuration Manager) is a wizard-based, graphical tool that exposes MDM repository metadata and is used for configuring MDM Web Dynpro components. For example, you can configure the layout, actions, and functions of the components.



Note

The steps below must be performed if you are upgrading from an MDM version earlier than SP05.

However, we recommend performing these steps when upgrading all versions.

To upgrade MDM Web Dynpro Components:

1. In the MDM Web Dynpro Configuration Manager, export all your configured projects.

2. Save the exported configuration file.

3. Deploy the latest version of the MDM Web Dynpro components.You can download them from

service.sap.com/swdc . Choose SAP NetWeaver and complementary products SAP NETWEAVER MDM 7.1 Entry by Component Java WebDynpro for NW

4. Run the Configuration Manager.

5. Import the saved configuration file and choose Replace existing projects as the Import Action.



Note

● If you undeploy the tc/mdm/wdcomps/config/dictionary development component (DC), all the project configurations from the database of the specified Application Server Java are deleted.

In general, there is no need to remove this DC, but if you do, you must export your project configurations as explained above and re-import them after deploying the new dictionary.

● If you undeploy the tc/mdm/wdcomps/security DC the MDM_WD_CONFIGURATOR and

MDM_WD_TEST_APPLICATION, actions are deleted. You must reassign these actions to the role after deploying the new security DC.

For more information, see the MDM Web Dynpro Components Reference Guide on the SAP Help Portal at help.sap.com/nwmdm71.

(40)

3.7.10 MDM Collaborative Processes for Material

If you are upgrading from an MDM version earlier than SP05, the MDM Collaborative Processes for Material is now available. MDM Collaborative Processes for Material is a preconfigured, packaged solution to deploy a master data creation process.

You do not need to perform any update or upgrade activities.

For more information, see the Collaborative Processes for Material Master Data Creation Guide at help.sap.com/

nwmdm71.