MDM71SP08_UpgradeGuide_v30

Upgrade Guide

SAP NetWeaver® Master Data Management 7.1

Document Version 3.0 – October, 2011

Material Number 50092607

© 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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. 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 Library document classification: PUBLIC Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively 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. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Terms for Included Open Source Software This SAP software also contains the third-party open source software products listed below. Please note that the following special terms and conditions apply for these third-party products.

SAP License Agreement for STLport SAP License Agreement for STLport

between

SAP Aktiengesellschaft Systems, Applications, Products in Data Processing

Neurottstrasse 16 69190 Walldorf

Germany ( hereinafter: SAP )

and

you

( hereinafter: Customer ) 1. 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 permission 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 permission 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 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. 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 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. Moscow Center for SPARC

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

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

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

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

SAP Library document classification: PUBLIC

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

October 2011 6

Document History

Version / Date Important Changes

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. For more information, see 5.4 Update Repositories on page 30.

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, as described in 5.5.14 MDM Web Dynpro Components on page 44.

2.9 / May 2011 Guide updated for MDM 7.1 SP07.

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

o Using master/slave with SSL. For more information, see Upgrading Master/Slave Environments on page 14.

o Connecting with clients to MDM server in secure mode. For more information, see Connecting with Clients to MDM Server in Secure Mode on pag 17.

o Enabling MDIS to connect to MDM server in secure mode. For more information, see 5.5.2 MDM Import Server on page 34.

o Enabling MDSS to connect to MDM server in secure mode. For more information, see 5.5.3 MDM Syndication Server on page 35.

o Enabling MDLS to connect to MDM server in secure mode. For more information, 5.5.4 MDM Publisher see on page 37.

New software components, including support for NW 7.3. For more information, see 5.5.6 MDM JAVA API Activities on page 38.

2.7 / Jan 2011 Guide updated for MDM 7.1 SP06.

Addition to preparation steps regarding installing Microsoft Visual C++ security updates for MDM 7.1 SP05 and for MDM 7.1 SP06. For more information, see 4.7 Installing Visual C++ Security Updates on page 24.

Updates regarding MDM Web Dynpro components:

o 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. For more information, see 5.5.14 MDM Web Dynpro Components on page 44.

o Starting in MDM 7.1 SP05, the name of the component 'MDM Web Dynpro Configurator' was changed to 'MDM Web Dynpro Configuration Manager' ( 'Configuration Manager').

Update regading the fact 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, MDM Import Server was changed to Master Data Import Server.

2.4 / Jul 2010 New software component added: MDM Collaborative Processes for Material. For more information, see 5.5.15 MDM Collaborative Processes for Material on page 45.

October 2011 7

Contents 1. Introduction ....................................................................................... 8

1.1 About this Document ............................................................................................ 8 1.2 Before You Start .................................................................................................... 9

2. Upgrade – Step by Step ................................................................. 10 3. Planning........................................................................................... 14 4. Preparation ...................................................................................... 19

4.1 Download MDM 7.1 Installation Package ........................................................... 21 4.2 Adapt API Calls ................................................................................................... 21 4.3 Adapt CLIX Command Scripts ............................................................................ 22 4.4 Update Maps in Test Environment ..................................................................... 22 4.5 Stop Productive Use of MDM.............................................................................. 22 4.6 Back Up the MDM Environment ......................................................................... 23 4.7 Installing Visual C++ Security Updates .............................................................. 24

5. Upgrade Process ............................................................................ 25 5.1 Install SAP NetWeaver MDM 7.1 ......................................................................... 26 5.2 Installation Folder – Content Copy .................................................................... 26 5.3 MDM 7.1 Server Start .......................................................................................... 28 5.4 Update Repositories ........................................................................................... 30

5.4.1 Import Maps ............................................................................................. 31 5.4.2 Syndication Maps ..................................................................................... 32 5.4.3 Transport Updated Import and Syndication Maps ...................................... 32 5.4.4 Synchronize Distribution Folder Content ................................................... 33 5.4.5 Limited Number of Languages on IBM DB2 Database ............................... 33

5.5 Perform Component-Specific Activities............................................................. 33 5.5.1 Master Data Server ................................................................................... 33 5.5.2 MDM Import Server .................................................................................. 34 5.5.3 MDM Syndication Server .......................................................................... 35 5.5.4 MDM Publisher ......................................................................................... 37 5.5.5 MDM COM API Activities .......................................................................... 37 5.5.6 MDM JAVA API Activities .......................................................................... 38 5.5.7 MDM ABAP API Activities ......................................................................... 38 5.5.8 MDM Monitoring and Supportability Environment ...................................... 40 5.5.9 SAP Exchange Infrastructure Activities ..................................................... 41 5.5.10 MDM Web Services ................................................................................ 41 5.5.11 Enterprise Portal Content / iViews / UWL ................................................ 41 5.5.12 Web UIs.................................................................................................. 42 5.5.13 MDM Enrichment Architecture................................................................. 43 5.5.14 MDM Web Dynpro Components .............................................................. 44 5.5.15 MDM Collaborative Processes for Material .............................................. 45

5.6 Uninstall MDM 5.5 SP05/SP06 ............................................................................ 45 6. Appendix ......................................................................................... 46

6.1 Other Information ................................................................................................ 46 6.1.1 New Log File Format................................................................................. 46 6.1.2 New CLIX Commands .............................................................................. 46

7. Reference ........................................................................................ 49

1. Introduction

October 2011 8

1. Introduction This document describes the upgrade process from MDM 5.5 SP05 or SP06 to MDM 7.1, and the upgrade process between service packs (SP) of MDM 7.1. We do not provide direct upgrades from MDM 5.5 SP03 or SP04 to MDM 7.1. To upgrade from MDM 5.5 versions before SP05, refer to the MDM 5.5 SP05 Upgrade Guide.

Before you start the upgrade activities, read the complete Upgrade Guide.

1.1 About this Document This document describes how to upgrade from MDM 5.5 SP05 or SP06 to MDM 7.1, and how to upgrade between service packs of MDM 7.1, without modifying or losing data.

It is directed at customers running MDM 5.5 SP05 or SP06 in a Productive environment, or who are close to finalizing their MDM 5.5 implementation projects and need to upgrade to MDM 7.1; and at customers who are upgrading the service pack level of their MDM 7.1 installation.

The document does not describe the new MDM 7.1 features and functionality. Refer to the MDM 7.1 Release Notes, the documentation for the new features, and the MDM Reference Guides for information about new features.

Before you start the implementation, make sure that you have the latest version of this document. You can find the latest version on SAP Service Marketplace in the SAP MDM Documentation Center: service.sap.com/installMDM71.

This document does not address direct upgrades from former MDM 5.5 Service Packs (SP03 or SP04) to MDM 7.1. To upgrade from a former SP, follow the instructions given in the MDM 5.5 SP05 Upgrade Guide.

1. Introduction

October 2011 9

1.2 Before You Start 1. Read the complete Upgrade Guide to become familiar with the different activities for the upgrade.

2. We strongly recommend saving the running MDM 5.5 environment before you start the upgrade activities. The corresponding activities are described in detail in section 4 Preparation [page 19] of this document.

The following table contains SAP Notes relevant to the upgrade process. Read these notes carefully before you start the upgrade.

Note # Title

1235338 Upgrade MDM portal content from MDM 5.5 to MDM 7.1

1283332 MDM 7.1 SP1 - Upgrade from SP0 to SP1




None No upgrade note from SP4 to SP5


None No upgrade note from SP6 to SP7


1070163 SAP NetWeaver MDM 7.1 Release

1295253 SAP NetWeaver MDM 7.1 SP01 Release








1244358 SAP NetWeaver MDM 7.1 Release Restriction Note

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

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

















2. Upgrade – Step by Step

October 2011 10

2. Upgrade – Step by Step This section includes a checklist with all the actions you have to perform. The actions are in chronological order so that you can work through them like a checklist. For more information, use the links to the descriptions of the actions.

From MDM 7.1 SP06 and up, multiple instances of MDM are supported on the same MDM host machine. Each instance must be installed separately and requires a different SID and different listening ports.

From MDM 7.1 SP07 and up, MDM can be installed 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.

More information: MDM 7.1 – Installation Guide <Platform>.

Dev/Test Environment versus Productive Environment In the typical customer environment, there is a two-tier installation that is split into:

Dev/Test environment in which implementations and upgrades can be tested

Productive environment that has to be reliable over time

In this guide we will discuss the two-tier issue when we describe the different activities.

To minimize the downtime of your Productive system, you have to perform all preparatory steps before stopping the running Productive MDM 5.5 environment. We strongly recommend that you use a Dev/Test environment in addition to the Productive MDM 5.5 environment when performing the preparatory steps. Even if you do not use a separate MDM Dev/Test environment, you should create this environment, at least for the upgrade time (refer to step 2b in the checklist below).

The following list specifies the order in which steps must be performed for a complete upgrade, starting with the Dev/Test environment and finishing with the Productive environment.

In the preparation phase you must:

1. Adapt all custom applications that use ABAP API, Java API, or CLIX. These programs can be adapted in advance.

2. Update and test import and syndication maps. This has to be done in the Dev/Test environment.

3. Delete all pre-7.1 ports and maps from the Productive environment. This must be done before any schema imports are allowed in the 7.1 Productive environment.


October 2011 11

The figure below describes the upgrade process, which focuses on the repository-specific upgrade and optimizes the effort required in the preparation phase. Note that the numbering in the diagram is not the same as the numbering of the overall step-by-step description.

Import ports and maps fromtransported schema.

MDM 5.5

ProdRep55Unarchive MDM 5.5 Productive Repository („ProdRep55“)

install MDM7.1

Update ProdRep55 to MDM 7.1

Update and test import maps (see chapter 5.4.1)

Export Schema

Stop productive use of MDM 5.5

MDM 71Updated ProdRep71

Update MDM 5.5 productiverepository to MDM 7.1

Export repository‘s ports andupdated maps in schema file (see chapter 5.4.3).

Import Schema

Productive Rep71

Start productive use of MDM 7.1

DEV / TEST Environment Productive Environment

13

1

3

4

5

6

8

10

15

Update syndication maps (see chapter 5.4.2)

Archive MDM 5.5productive repository(„ProdRep55“)

2

9 Install MDM 7.1

11 Delete all ports from repository

14

MDM 7.1

ProdRep55

Updated ProdRep71

Map-updated ProdRep71

MDM 7.1

12 Delete all maps from repository

1. Planning

Plan the upgrade process, keeping Productive use of the MDM system in mind in order to minimize system downtime during the upgrade process (section 3 Planning [page 14]).

Some advance preparation is required for external components, such as programs based on the MDM APIs or on MDM CLIX. This additional effort has to be planned. For more information, refer to section 4 Preparation [page 19] of this document.

2. Preparation of Test Environment (TE) 1

2a. Prepare Existing Dev/Test Environment (TE)

Download the new MDM 7.1 installation package.

Clean up the existing MDM 5.5 installation environment and stop its use (section 4.5 Stop Productive Use of MDM [page 22]).

Back up your existing MDM 5.5 Dev/Test installation (section 4.6 Back Up the MDM Environment [page 23]).

1 Perform either 2a (if you have an existing MDM 5.5 Dev/Test environment) or 2b.


October 2011 12

2b. Establish New Dev/Test Environment (TE)

Download the new MDM 7.1 installation package.

To use SSL, download the SAPCRYPTO.lib file. For more information, see 3. Planning on page 14.

3. Prepare Productive Environment (PE)

Verify the Productive repository.

Archive the Productive repository. Organize the Productive repository to prevent further data model changes.

4. Perform Upgrade Steps in Dev/Test Environment (TE)

Install the new MDM 7.1 software components.

If your installation includes SSL, configure the server ini files, as described in 3. Planning on page 14.

Start the MDM 7.1 Server (section 5.3 [page 28]).

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

Update the repository in MDM 7.1 TE (section 5.4 [page 30]).

Load repository with index update (section 5.4 [page 30]).

Update the repository’s import maps (section 5.4.1 [page 31]). Manually rework the import maps as necessary.

Test the import maps.

Update the repository’s syndication maps (section 5.4.2 [page 32]).

Export repository schema containing all ports and updated import and syndication maps (section 5.4 [page 30]).

Perform all MDM-component-specific activities (section 5.5 [page 33]).

Upgrade MDM environmental applications. - If SAP Enterprise 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, upgrade and test the Java programs. If you use the old Java API, you have to rewrite your Java code to the new Java API (section 4.2 [page 21]) . - If you used CLIX command scripts, rework these according to section 4.3 [page 22].

5. Upgrade Process in Productive Environment (PE)

Stop Productive use of MDM [page 22]).

Back up your existing MDM 5.5 Productive installation (section 4.5 Back Up the MDM Environment [page 23]).

Install the new MDM 7.1 software components.

If your installation includes SSL, configure the server ini files as described in 3. Planning on


October 2011 13

page 14.

Follow section 5.2 [page 26] for copying content from MDM 5.5 environment to MDM 7.1 structure.

Start MDM 7.1 Server (section 5.3 [page 28]).

Update existing repository (section 5.4 [page 30]).

Load repository with index update (section 5.4 [page 30]).

Delete all ports from repository (section 5.4 [page 30]).

Delete all import and syndication maps from repository (section 5.4 [page 30]).

Import schema containing all ports and updated maps from MDM 7.1 TE (section 5.4 [page 30]).

Perform all MDM-component-specific activities (section 5.5 [page 33]).

Upgrade MDM environmental applications based on experience in TE: - If Enterprise Portal is assigned to the test environment, upgrade 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.

6. Follow-Up Activities

Test the old MDM 5.5 SP05/SP06 functionality in MDM 7.1.

Uninstall the old MDM 5.5 SP05/SP06 components (optional).

These activities are described in detail in the next sections.

3. Planning

October 2011 14

3. Planning Your current MDM 5.5 SP05/SP06 environment can be a productive environment or a project-specific test environment. In both cases, users rely on the availability of the MDM system.

Dev/Test versus Productive 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. After completing the upgrade in the Dev/Test environment, you may have adapted the API programs and the iViews.

As described in section 2 Upgrade – Step by Step [page 10], we strongly recommend that you use a separate Dev/Test environment. The reason is to test the upgrade in a non-Productive environment, as well as to move as much upgrade activity as possible to the preparation phase in order to minimize Productive system downtime.

Upgrading Master/Slave Environments

If your MDM 5.5 SP05/SP06 environment uses MDM master/slave technology, you have to rebuild the slaves after the upgrade to MDM 7.1. You cannot upgrade the slave repositories during an upgrade.

To use master/slave with SSL, starting from MDM 7.1 SP07, you need the following entries in your master and slave mds.ini server files to refer to the remote server. This is necessary even if the master and slave repositories are on the same MDM server instance. [MDM Server\Remote Server\xx@[Slave Server Name]

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

Example [MDM Server\Remote Server\00@tlvd60200359a]


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

If you change the listening mode or port on the MDM Server where the master is located after a slave has been created, the connection between the master and slave will be invalidated and you will need to recreate the slave.

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

Deploying the New MDM ABAP API

MDM ABAP API installed on NW 7.0 also supports MDM 5.5 MDM ABAP API installed on NW PI 7.1 does NOT support MDM 5.5

3. Planning

October 2011 15

In the following table you find information about the actions that have to be performed in different situations: You need

MDM 7.1 running on NW 7.0 You need MDM 7.1 running on NW PI 7.1

You have MDM 5.5 on NW 6.40

ABAP application server installation to be upgraded to NW 7.0

ABAP application server installation to be upgraded to NW PI 7.1

You have MDM 5.5 on NW 7.0

New ABAP API deployment (SAINT)

ABAP application server installation to be upgraded to NW PI 7.1

For deployment of the updated MDM 7.1 ABAP API, refer to section 5.5.7 MDM ABAP API Activities [page 38] of this document.

With deployment of the MDM 7.1 ABAP API, all providers lower than MDM 5.5 SP06 Patch 3 are removed. Therfore an ABAP system that has the 7.1 ABAP API deployed, cannot support MDM systems with MDM 5.5 SP06 Patch 2 or lower.

Planning the Time for the Upgrade

No explicit figures can be provided for the upgrade, but you can use the estimates below as a basis for upgrade planning.

The overall time consumption depends on the number of hosts, repositories, and components installed on a host. The Back Up Repository and Update Repository steps also depend on the number of records in the respective repository.

Time consumption for the components on a host (rough estimates):

Preparation Phase

Step Duration

Clean up MDM 5.5 environment 20 minutes / repository

Back up the stopped Dev/Test environment 2 hours / host

Install MDM 7.1 Servers on a host 1 hour / host

Update repositories and maps 10 minutes / repository up to hours, dependent on amount of manual rework

Install new MDM ABAP API and check application 4 hours

Adapt CLIX command scripts if necessary 10 minutes / script

Adapt Java API (if new API was used) 4 hours

Reimplement Java API programs (if old API was used)

If iViews are implemented some time needs to be planned for upgrade

Uninstall MDM 5.5 servers and GUIs 10 minutes / host

3. Planning

October 2011 16

Productive Environment (Downtime)

Step Duration

Clean up MDM 5.5 environment 20 minutes / repository

Back up the stopped Dev/Test environment 30 min / host

Install MDM 7.1 Servers on a host 1 hour / host

Modify configuration ini files 5 minutes/ server

Transport repository ports and maps 30 minutes / repository

Perform MDM-component-specific upgrade activities

Changed Platform Support on MDM 7.1 With MDM 7.1, the MDM PAM (platform availability matrix) has changed

The following platforms are supported in MDM 7.1:

Solaris on x86

Windows 2008 from 7.1 SP06 and up

Windows 2008 R2 from 7.1 SP06 and up

Support of new operating systems for MDM rich clients from 7.1 SP06 and up:

Windows 7

The following databases are supported by MDM from 7.1 SP06 and up:

SQL 2008

SQL 2008 R2

Oracle 11

Note that the following platforms are no longer supported:

RedHat 4

Suse 9

Windows Server 2003 32bit

HP-UX on PA-RISC

For details, refer to the MDM 7.1 Product Availability Matrix (PAM) on SAP Service Marketplace at service.sap.com/pam SAP NETWEAVER SAP MDM.

There are some changes to the requirements for the patch level of some UNIX operating systems and underlying library version between MDM 5.5 SP06 and MDM 7.1. The same applies to the version of the C++ runtime environment components.

MDM Import Server on Windows 32-Bit

The Windows 32-bit version of MDM Import Server will not be released with MDM 7.1, meaning the MDM Import Server no longer supports Excel or Access files. Excel and Access files will continue to be supported on the Import GUI (MDM Import Manager).

3. Planning

October 2011 17

MDM Server Hardware Migration

If you have to migrate your MDM server environment to different hardware during the MDM 5.5 to MDM 7.1 upgrade, for example because MDM Windows 32-bit servers are no longer delivered, you may also follow the steps described in this upgrade guide.

Schedule Adaption of API Programs / CLIX Scripts

During the upgrade process, you have downtime of the different MDM servers. The servers can be released soon after the upgrade, but upgrading environmental functionalities such as scripts using MDM CLIX commands or programs calling MDM via ABAP or Java API may be time-consuming. Due to changes in the CLIX and possible changes in the APIs, you must plan software adaption before upgrading the Master Data Server, as otherwise Web access, for example, might not be immediately available.

Connecting with Clients to MDM Server in Secure Mode 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.

To connect to MDM clients in secure mode, copy 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. You need to download this from the SMP as sapcrypto.SAR.

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

To connect to an MDM Server in secure mode with the MDM Console:

1. Mount the server.

The Mount MDM Server dialog box appears.

2. Select the Secure Connection check box.

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.

3. Planning

October 2011 18

Example:

To connect to an MDM Server in secure mode with other rich clients: 1. In the Connect to MDM Repository dialog box, choose “…”.

The Choose Repository dialog appears:

2. Select the Secure Connection check box.

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

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

If you are using the Visio workflow plugin, do not use the 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, choose the repository.

7. Choose OK.

4. Preparation

October 2011 19

4. Preparation Upgrading an existing MDM landscape using MDM 5.5 SP05/SP06 requires some preparatory steps. These steps differ if you have only a Productive landscape or a two-tier installation consisting of a Dev/Test environment and a Productive environment.

In a real-life situation, you might have a development, a test and a number of Productive environments (one master and n slaves). In this case, the steps are the same as for the two-tier environment.

One-Tier Environment (Productive Environment Only) The preparatory steps are:

1. Download the new MDM 7.1 installation packages.

2. If CLIX is used, adapt the command scripts, as described in 4.3 Adapt CLIX Command Scripts on page 22.

3. If ABAP API is used, check ABAP API programs with new ABAP API deployment.

4. If Java API is used, check Java API programs. If old Java API is used, reimplement Java programs according to new MDM Java API, as described in 4.2 Adapt API Calls on page 21.

5. Clean up the existing MDM 5.5 installation environment and stop use.

6. Stop external programs feeding MDM 5.5 Productive repositories (for example XI communication channels).

7. Back up the environment.

8. Perform the upgrade process, as described in 5. Upgrade Process on page 25.

Two-Tier Environment (Dev/Test Plus Productive Environment)

A. Prepare Dev/Test Environment:

The preparatory steps are:


2. If CLIX is used, adapt the command scripts.

3. If ABAP API is used, check ABAP API programs with new ABAP API deployment.

4. If Java API is used, check Java API programs. If old Java API is used, reimplement Java programs according to new MDM Java API, as described in 4.2 Adapt API Calls on page 21.

5. Clean the Productive MDM 5.5 repository (remove Productive content as desired) in the Productive environment and archive the repository.

6. If an MDM 5.5 environment was used in the Dev/Test environment:

Stop test MDM 5.5 usage.

Stop external programs feeding MDM 5.5 test repositories (for example XI communication channels).

Back up the test environment.

Install MDM 7.1 software components.

Start MDM 7.1 Server.

Unarchive the Productive repository in the MDM 7.1 Dev/Test environment.

7. If an MDM 5.5 environment was not used in the Dev/Test environment:

Preparation can directly start with installing the MDM 7.1 software components.

Start MDM 7.1 Server.

Unarchive the repository in the MDM 7.1 Dev/Test environment.

4. Preparation

October 2011 20

B. Upgrade Dev/Test Environment:

1. Perform the upgrade process for the Dev/Test environment as described in 5. Upgrade Process on page 25.

2. Update all import and syndication maps, as described in 5.4 Update Repositories on page 30.

3. Test import map updates in the Dev/Test environment.

4. Transport all ports and updated import and syndication maps to the Productive environment.

C. Productive Environment:

Perform the preparatory steps after upgrading the tested environment. In this way you can be sure that the upgrade is performed in the shortest possible time frame.


2. Stop Productive MDM 5.5 use.

3. Back up the environment.

4. Install the new MDM 7.1 software components and perform the upgrade process as described in 5. Upgrade Process on page 25. Use adapted components that were previously upgraded in the Dev/Test environment.

5. Delete all ports from the upgraded repository.

6. Delete all maps from the upgraded repository.

7. Transport the repository’s ports and updated maps from the Dev/Test environment.

8. Transport the adapted objects, programs, and portal content from Dev/Test environment (Java, ABAP, and CLIX).

The repository-specific upgrade process for separate Dev/Test and Productive environments is described in the diagram in 2. Upgrade – Step by Step on page 10.

The steps are described in detail in the next sections.

4. Preparation

October 2011 21

4.1 Download MDM 7.1 Installation Package Get the MDM installation package from Service Marketplace and prepare it for installation.

The downloaded software should be available for both the test environment and the Productive environment.

With MDM 7.1, the MDM servers are installed in a SAP-specific installation framework using new SAPINST installers and installing per default to /usr/sap/<SID> locations (<SID> = typical 3-letter SAP System ID, for example MDX).

Use of the SAP Startup Service as a generic MDM server start/stop toolset is introduced together with the new installation framework. This allows you to handle MDM servers with the SAP Management Console (SAP MMC) and also enables the MDM Console to handle MDM servers on any OS (operating system).

More information: MDM 7.1 – Master Guide and MDM 7.1 – Installation Guide <Platform>.

4.2 Adapt API Calls COM API .Net API

The COM API is available in MDM 7.1 with a functionality setup identical to MDM 5.5. There is no functional enhancement implementing new MDM 7.1 functionality (for example tuples). Use of MDM COM API is discouraged as it will not be part of the next MDM release.

The .NET API is new in MDM 7.1 and provides the same set of functions as the MDM 7.1 Java API. Customers are encouraged to write applications using the .NET API instead of the COM API.

JAVA API

The old Java API MDM4J was deprecated in MDM 5.5 and is no longer shipped with MDM 7.1.

MDM 7.1 provides the new version of the JAVA API only. If your Java coding is based on the old Java API MDM4J, refer to the information about migrating from the old Java API to the new Java API in the document MDM 5.5 SP06 – Java API Migration Guide on the Service Marketplace.

With MDM 7.1 SP07, a new software component is 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 now in order to obtain all the information, such as signatures, needed to perform the adaptation:

The COM API package contains the following executable installation file:

mdm-com-<built>-win32.exe (COM API shipped with MDM7.1, but deprecated)

The Java API package contains the following file:

mdm-api-<built>-java1.4.2.zip (Java API replacement for the old MDM4J)

You can find details about the installation in the MDM 7.1 – Installation Guide <Platform>.

The activities differ depending on whether or not you have a test environment

One-Tier Environment

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

a. Back up all programs that use COM API or Java API in the appropriate development environment.

4. Preparation

October 2011 22

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

c. Test the adapted programs directly after the upgrade.

Two-Tier Environment First perform the adaption in your test environment:

a. Back up all programs that use COM API or Java API in the appropriate test environment.

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

c. After upgrading the test environment to MDM 7.1, test the adapted programs locally.

d. Provide the adapted programs to the Productive environment.

Perform in the production environment:

a. Back up all programs that use COM API or Java API in the appropriate development environment.

b. Replace the old programs with the ones tested in the test environment as part of the upgrade process.

4.3 Adapt CLIX Command Scripts Obsolete CLIX commands need to be replaced. To save time during the upgrade, migrate all MDM 5.5 CLIX scripts to MDM 7.1 before you start the upgrade.

The following commands are obsolete in MDM 7.1:

- mdsStart

- mdsStop

Review existing CLIX scripts (or .bat files) for mdsStart and mdsStop commands and replace them with some of the new “iC” commands. Refer to section 6.1.2 New CLIX Commands [page 46] for details regarding the new CLIX commands.

4.4 Update Maps in Test Environment 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 on 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, some import maps may need to be updated manually (section 5.4.1 [page 31]). All updated import maps should also be tested in the Dev/Test environment.

Syndicator can update syndication maps automatically (section 5.4.2 page 32).

Once all maps are updated, transport the repository’s ports and updated maps from the Dev/Test environment to the Productive environment.

4.5 Stop Productive Use of MDM Before the complete system can be backed up and upgraded, you need to stop all components of your MDM system on this host. The necessary activities are:

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 COM API, ABAP API , JAVA API or Portal).

2. From the MDM Console, 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. Go to directory structure MDM_HOME/Distribution. For all connected MDC (Master Data Clients) and all

4. Preparation

October 2011 23

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). 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 MDM 5.5 SP05/SP06 environment. Stop external applications from providing any further MDM import files to the MDM 5.5 environment, for example by stopping the SAP XI/PI communication channels.

3. Use the MDM Console to unload all active repositories.

4. All applications running on the current host are stopped (for example, Web applications calling the MDM host directly have to be stopped, while Web applications relying on a slave can continue).

5. Stop work of SAP XI/PI communication channels that are providing import data for the MDM repositories.

6. Clean up the distribution folders 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 5.5 environment or copied to the new MDM 7.1 environment.

7. Verify and repair the repositories and ensure there are no errors.

8. Archive all running repositories Perform this step directly after checking and repairing all repositories. Using MDM Console or a CLIX-based batch procedure, archive all repositories you want to reuse after the upgrade. We recommend that you copy the archives from the MDM file location to a specific backup location.

9. Stop all servers based on the current host (Master Data Server, Master Data Layout Server, Master Data Import Server and Master Data Syndication Server). In Windows Services, check if all servers, such as the Master Data Import Server, Master Data Syndication Server or Master Data Layout Server, are stopped.

4.6 Back Up the MDM Environment This step is strongly recommended for safety reasons.

To back up the MDM environment, perform the following steps:

1. Archive all repositories used. Perform this step after checking and repairing all repositories (section 4.4 Stop Productive Use [page 22]).

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 5.5; for Unix: /usr/local or /opt.

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

3. Save your 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 5.5 SP05/SP06 custom portal content and download it to a local .epa file.

We also recommend that you perform these backup tasks for your test environment.

4. Preparation

October 2011 24

4.7 Installing Visual C++ Security Updates It is necessary to install Microsoft Visual C++ security updates on your Windows server and client machines.

For MDM 7.1 SP05, you must install Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update.

Without this update, Master Data Server fails to start, and displays a failure message.

To check if you need the security update:

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

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

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

For more information, see the Microsoft Knowledge Base Article KB973544 and the SAP Note 1375494.

For MDM 7.1 SP06, you must install both Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update and Microsoft Visual C++ 2008 SP1 Redistributable Package.

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:

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

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


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

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

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

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

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

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

5. Upgrade Process

October 2011 25

5. Upgrade Process Upgrading to MDM 7.1 consists of a number of steps that depend on the MDM components you use.

After completing the preparation activities, including backup, you can now start with the upgrade activates.

1. Keep your MDM 5.5 installation during the upgrade. 2. Install MDM 7.1. 3. Update all repositories and migrate their ports and import and syndication maps. 4. Perform component-specific activities for:

Master Data Server (MDS)

Master Data Import Server (MDIS)

Master Data Syndication Server (MDSS)

MDM Publisher

MDM Import Manager

MDM COM/JAVA API

MDM ABAP API configuration

Generic upgrade specific issues

MDM supportability 5. Perform activities in MDM environment:

SAP Exchange Infrastructure

MDM portal content / URL / iViews

MDM Java UIs

5. Upgrade Process

October 2011 26

5.1 Install SAP NetWeaver MDM 7.1 The MDM 7.1 installation has the following parts:

- MDM servers MDM servers are integrated into the SAP Startup Framework, so they 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 SAPINST-based installers that also install the Startup Framework and the SAP MMC in your system. 1. Master Data Server 2. Master Data Import Server 3. Master Data Syndication Server 4. Master Data Layout Server

- MDM GUI Clients (WIN32 only) The installer setup for the MDM GUI components did not change for MDM 7.1. Install the MDM components 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): 1. MDM Console 2. Administration component (MDM CLIX) 3. MDM Data Manager 4. MDM Import Manager 5. MDM Syndicator 6. MDM Language Selector 7. MDM UoM Manager 8. MDM Image Manager 9. MDM Publisher 10. MDM Indexer 11. All publishing components (DTP plug-ins)

- Additional MDM components 12. MDM ABAP API 13. MDM .Net API 14. MDM Java API 15. MDM Connector 16. MDM Portal Content 17. MDM Enrichment Architecture 18.TREX configurator

For details about the new MDM server installation technique, refer to the MDM 7.1 – Installation Guide <Platform>.

5.2 Installation Folder – Content Copy 1. 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):

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.

5. Upgrade Process

October 2011 27

[<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>/

2. MDM Archive Files MDM55: WIN: <System Drive>:\Program Files\SAP MDM 5.5\server\archives\*.a2a UNIX: $<MDM server Work directory>\archives\*.a2a Copy the archives you want to use in MDM 7.1 to the new folder. [<System Drive>:]/usr/sap/<SID>/MDS<instance number>/mdm/archives

3. MDM GUI Clients The folder structure of the MDM GUI components on WIN32 did not change with 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

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

4. No Copy of Master/Slave Modification Data Required

Due to the fact that MDM slave repositories cannot be upgraded and have to be rebuilt after a system upgrade, you do not need to copy the synchronization data in the modification files.

5. Save MDM 5.5 Log Files

Since the log file format was changed from MDM 5.5 (xml based) to MDM 7.1 (csv based), the MDM 5.5 log files cannot be displayed with MDM 7.1 Console. If you want to keep the log files for historic reasons, we recommend that you copy them from the log and the report folder to an extra folder together with the MDM_Log.xsl file, which allows viewing of the logs from the browser. WIN: <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

6. Copy Distribution Folder Content

The content of the inbound structures in distribution folders should have been cleaned up in an earlier step. If import files are ready for import and were not yet imported, copy these data import files from the MDM 5.5 distribution folder Ready directory to the new MDM 7.1 distribution folder Ready directory.

You cannot perform this step now because the Distribution Folder structure does not exist as long as the MDM repositories are not loaded for the first time into the MDM 7.1 server environment. To maintain the chronological order, we will refer to this step in a later section.

The mds.ini settings allow you to modify the Distribution Folder so that a shared folder can also be used to store distribution files. If you repeat this setting in the MDM 7.1 environment, it is not necessary to copy the Ready files.

5. Upgrade Process

October 2011 28

5.3 MDM 7.1 Server Start 1. Start MDM 7.1 Master Data Server

The first step in the new MDM 7.1 environment is to start the Master Data Server. Use the MDM 7.1 Console to start the MDM 7.1 Master Data Server.

From MDM 7.1 SP07 onwards, the MDM servers must be referred to using either 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 we have instance=00

Server name=iltlvt36

Port=50051

Then the server can be mounted as:

00@iltlvt36 or iltlvt36:50051 Please see the MDM installation guide and release notes for more details on the new ports for MDM Servers.

2. Stop MDM 7.1 Import Server and MDM 7.1 Syndication Server

Make sure the MDM 7.1 Import Server and MDM 7.1 Syndication Server are stopped before performing the following steps. It might make sense to start the auxiliary servers to check the installation, but then they have to be stopped before proceeding.

To use MDM Import Server and MDM Syndication Server with SSL in MDM 7.1 SP07 and up, you need to configure the MDM Import Server and MDM Syndication Server ini files (mdis.ini and mdss.ini) to refer to the appropriate MDM Server that your repository is running on, even if they are on the same server SID:

For details, see 5.5.2 MDM Import Server on page 34 and 5.5.3 MDM Syndication Server on page 35.

3. Mount all (Test/Productive) repositories As a next step, mount all repositories that should be running in the MDM 7.1 environment again.

There are two options to bring the MDM 5.5 repositories to the new MDM 7.1 environment: a. Mount the MDM 5.5 repositories. In this case the MDM 5.5 installation no longer can use these repositories. b. Unarchive the MDM 5.5 repository archives and rename the repositories.

Note: New feature: Operating system independent start/stop

With the new MDM 7.1 installation structure, MDM servers are handled on all platforms in the same way: using the SAP infrastructure framework (SAP Startup Framework).

On Windows, the server applications (mds, mdis, mdss, and mdls) now run as applications launched by instances of the SAPStartSrv executable, which runs as a service. A user account that is associated with the server applications is created during installation; the credentials of this user are required when the server applications are stopped or started. On UNIX the MDM server executables are started by a demon called SAPStartSrv.

5. Upgrade Process

October 2011 29

This is a change in handling; for detailed information refer to the MDM 7.1 – Installation Guide <Platform> or MDM 7.1 Console Reference Guide.

MDM systems are now installed with a common system ID (SAP: <SID>). A system instance is created for each of the servers that belong to a system (see example: MDM system name is MDB and consists of three instances: MDS00 – Master Data Server, MDIS01 – MDM Import Server, MDSS02 – MDM Syndication Server).

Note that both MDM 7.1 CLIX and MDM 7.1 Console can now start and stop mds, mdis, mdss, and mdls on any platform (not just Windows anymore, and not just mds!).

To start and stop the MDM 7.1 servers you can also use the SAP MC (SAP Management Console – available on all OS versions), for example the SAPMMC for Windows OS.

The Win32 Console GUI has also been adapted to use the Service Framework's underlying control method. As a result, the Console can also start non-Windows MDM services.

OS Requirements for Starting/Stopping MDM Servers

To start/stop MDS servers from the Console, you must enter the OS level user name and the password (of the server host machine). For more details, refer to the MDM 7.1 – Installation Guide <Platform>.

5. Upgrade Process

October 2011 30

5.4 Update Repositories

Run Verify/Repair on all repositories before loading them in MDM 7.1 SP04.

Prior to MDM 7.1 SP04, expressions using lookup values or relationships could not be transported properly. This has been resolved in MDM 7.1 SP04. To transport these expressions, assignments, or validations, open each expression, delete the referenced lookup value, and then add it again to the expression.

As of MDM 7.1 SP04, the Code Field for Masks and Named Searches is unique and does not allow NULL values. These requirements cannot be automatically implemented for repositories from MDM versions prior to MDM 7.1 SP04. If you run a Verify/Check in the MDM Console, a warning is displayed. In the MDM Data Manager, you need to change the entries in the Code Fields for Masks and Named Searches so that the entries adhere to the above mentioned requirements. Thereafter you can once again run a Verify/Check on your MDM repositories in the MDM Console.

Some changes made to the repository schema in MDM 7.1 require that you update the SP05/SP06 repositories from the MDM 7.1 Console. After installation of MDM, start the new Master Data Server and use MDM Console to update your repositories. All repositories that need to be updated are displayed in the MDM. Console with the icon (such as the CUSTOMER_55630_NEW repository in the example):

Perform the following steps for each repository that needs to be updated (assuming that the MDM Server is started and the corresponding repositories are mounted):

1. After installation of MDM 7.1 and having started the MDM 7.1 Server, use the MDM Console to update your repositories. Choose Update Repository from the context menu of each repository. The MDM Console then 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 in order to verify or to load it.

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

For the standard repositories templates, the default user name is Admin, and, starting in MDM 7.1 SP08, the default password is sapmdm (and can no longer be empty). Otherwise, use the user name and password that you defined in the repository.

5. Upgrade Process

October 2011 31

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 need to enter the default password in these files.

After logging on, the MDM Console shows the following icon for the repository: MDM repository is unloaded.

For a complete list of icons, see section Display and Format Conventions in the MDM Console Reference Guide.

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

4. To load the repository and update the indices, choose Load Update Indices from the context menu.

The MDM Console shows the following icon for the repository while the repository is being loaded: MDM repository is being loaded. After successfully loading the repository, the icon is: MDM repository is loaded.

We recommend that you update the indices for your repositories (Load 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.

5.4.1 Import Maps The Update Repository step does not automatically update import maps for use with MDM 7.1.

To update import maps for MDM 7.1, start the MDM 7.1 Import Manager and connect it to the updated repository. Import Manager asks if you would like to update the outdated import maps. Choose Yes to start the update procedure.

This dialog appears only when you connect Import Manager to a repository with outdated maps or try to import an outdated map.

Import Manager attempts to automatically update all of the outdated maps in the repository. However, some maps may require manual updating from within Import Manager. Import Manager appends [Requires Manual Update] to the names of these maps and notes the problems which prevented automatic update in the UpdateMapLog file, which is located in the Import Manager’s installation directory.

All updated maps should be tested and fixed in the Dev/Test environment before being transported to the Productive environment. Existing import files can be used to test the updated maps.

We recommend that the Inbound ports in the updated repository’s Distribution folder be clean – i.e. the Ready folder and Exception folders are empty – before import maps are updated.

5. Upgrade Process

October 2011 32

If you plan to copy import files from MDM 5.5 to the MDM 7.1 environment, update the import maps first.

If an import map of type XML Schema is not assigned to a port, Import Manager asks for the map’s associated XML Schema as part of the automatic update process. If an XML Schema has more than one possible root node, Import Manager asks which root node to use with the map as part of the automatic update process.

Import maps created or saved in MDM 5.5 SP05 or later versions can be upgraded directly to 7.1 SP01 or SP02. Import maps of type XML Schema that were created and last saved prior to MDM 5.5 SP05 must be loaded (along with their XML Schema) and resaved in an MDM 5.5 SP05 or SP06 Import Manager before they can be updated to MDM 7.1

For the MDM delivered standard object repository templates we provide notes that also contain information about the object type specific handling of the “Import Maps” during upgrade. SAP Note MDM Repository Template 1252846 Product 1255401 Material 1035773 Business Partner 1252883 Vendor 1252884 Customer 1268212 Employee

5.4.2 Syndication Maps The Update Repository step does not automatically update syndication maps for use with MDM 7.1.

To update syndication maps for MDM 7.1, start the MDM 7.1 Syndicator and connect it to the updated repository. Then, choose File Update Maps to update all syndication maps in the repository. When the update process is finished, Syndicator opens a dialog displaying the number of maps updated.

All maps should be reviewed and tested after being updated, as the update process enforces mapping rules and property behaviors that may be different than those in effect when the map was last saved. In addition to any modifications required by the update, repository schema changes made since the map's last "save" can also affect a map's item mappings and property states.

The Syndicator File Update Maps operation is available in MDM 7.1 SP2 only. When upgrading to MDM 7.1 SP1, each syndication map must be updated manually by opening it, verifying its mappings and settings, and then re-saving the map (which may require unmapping and remapping an item.

5.4.3 Transport Updated Import and Syndication Maps Map updates are treated as schema changes by MDM. Once all 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+). The main difference between the two methods is that 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.

In both cases, all outdated maps must be deleted from the Productive environment before any schema transport or migration can occur. If a map is being used by a port, that port must be deleted before the map can be deleted. The ports and maps deleted from the Productive system are then replaced with the ports and updated maps transported from the Dev/Test environment.

5. Upgrade Process

October 2011 33

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.

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.

5.4.4 Synchronize Distribution Folder Content Once all maps have been transported to the Productive environment, any import files left over from MDM 5.5 can be copied to the Productive environment (part 6 of section 5.2 Installation Folder – Content Copy [page 26]).

5.4.5 Limited Number of Languages on IBM DB2 Database If you do not use MDM 5.5 SP05 with database IBM DB2, you can skip this section

[SP05] Since MDM 5.5 SP06, it is not possible to unarchive or mount repositories containing more than six languages on database DB2. This limitation is only valid for repositories with more than six languages created or archived under SP05 or prior releases. These repositories cannot be unarchived on DB2 database with SP06. For newly-created repositories, the number of languages is limited to fourteen on DB2. As a workaround, the following procedure can be applied: Archive the repository under SP05. After upgrading Master Data Server to MDM 7.1, unarchive the repository on a different DBMS system (e.g. MaxDB) and update the repository to MDM 7.1 schema (see chapter 5.3). Duplicate the upgraded repository to DB2 database or archive it and unarchive it on DB2.

5.5 Perform Component-Specific Activities MDM 7.1 is delivered as a collection of components, some of which need upgrade activities.

5.5.1 Master Data Server This section includes upgrade activities specific for the MDM 7.1 Master Data Server.

Upgrade of MDS configuration file: mds.ini

We recommend that you do not copy the old MDM 5.5 mds.ini configuration file. A correct MDM 7.1 mds.ini file is written when you first start the new MDM 7.1 server. The MDM 7.1 configuration file is located in the following directory: [<System Drive>:]/usr/sap/<SID>/MDS<instance number>/config/mds.ini Check the MDM 5.5 mds.ini file for additional settings, for example for the monitoring environment.

Changes in mds.ini

5. Upgrade Process

October 2011 34

The mds.ini configuration file contains new parameters for the changed ABAP API connection (section [page 38]).

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

“Protocol Log Level”, “Database Log Level” are 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.

The following strategy is followed for access to all configuration files (mds.ini, mdis.ini, mdls.ini): MDM servers check environment variables to get the ini file path. If no such variables are set, the default is the current working directory.

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

SLD Registration Wily Instrumentation Wily Instrumentation Level Threshold

Changes to the MDM configuration files mds.ini / mdis.ini / mdss.ini only become effective once you have restarted the respective server.

5.5.2 MDM Import Server User credentials now maintained from the MDM 7.1 Console

You can now 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 of configuration file settings Transfer the following settings from MDM 5.5 mdis.ini to the new MDM 7.1 mdis.ini:

SLD Registration

Wily Instrumentation

Wily Instrumentation Level Threshold

After the installation, a new section ([MDM Server\Remote Server\<mdsInstance>@<ServerName>]) is created in the MDIS ini files, 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:

5. Upgrade Process

October 2011 35

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>



SSL Enabled=True

SSL Lib Path=C:\usr\sap\Q59\MDIS01\exe\sapcrypto.dll

SSL Key Path=C:\usr\sap\Q59\MDIS01\sec\Client.pse

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

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



5.5.3 MDM Syndication Server This section includes all upgrade activities for the MDM 7.1 Syndication Server.

Upgrade Syndication Server configuration file MDSS.ini New parameter

The mdss.ini [GLOBAL] section has a new parameter:

"MDM Server Check Interval (seconds)"

This parameter is used to monitor events that start/stop the repository. At the given interval, the main MDSS thread gets a list of running repositories and start or stop syndication tasks for each repository. The default value is 20 seconds.

Obsolete parameter MDM 7.1 does not support the following MDM 5.5 mdss.ini settings:

“Auto Syndication Task Enabled” with MDM 7.1, auto syndication is always enabled.

User credentials now maintained from MDM 7.1 Console

You can now specify 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 system.

5. Upgrade Process

October 2011 36

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 MDM 5.5 mds.ini to the new MDM 7.1 mds.ini:

SLD Registration Wily Instrumentation Wily Instrumentation Level Threshold

After the installation, a new section ([MDM Server\Remote Server\<mdsInstance>@<ServerName>]) is created in the MDSS ini files, 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 MDSS 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>



SSL Enabled=True

SSL Lib Path=C:\usr\sap\Q59\MDIS01\exe\sapcrypto.dll

SSL Key Path=C:\usr\sap\Q59\MDIS01\sec\Client.pse

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

Listening Mode=[Both/Unencrypted/SSL]



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



5. Upgrade Process

October 2011 37


5.5.4 MDM Publisher With MDM 7.1 SP07 it is possible to use MDLS and publishing clients in encrypted mode.

To enable MDLS 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>\MDLSxx\exe\sapcrypto.dll SSL Key Path=C:\usr\sap\<sid>\MDLSxx\sec\<clientKeyFileName>



SSL Enabled=True

SSL Lib Path=C:\usr\sap\Q59\MDLS01\exe\sapcrypto.dll

SSL Key Path=C:\usr\sap\Q59\MDLS01\sec\Client.pse

After the installation, the following parameters are added automatically to MDLS ini files:

Listening Mode=[Both/Unencrypted/SSL]



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




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

5.5.5 MDM COM API Activities There are no additional update activities regarding the MDM 7.1 COM API. If you want to use the MDM COM API, install it according to the MDM 7.1 – Installation Guide <Platform>.

5. Upgrade Process

October 2011 38

5.5.6 MDM JAVA API Activities To work with WAS applications using the MDM 7.1 JAVA API, you need to deploy both the Java API package and the MDM Connector.

To connect to the WAS with SSL, you also need to 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 Java API user 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

With MDM 7.1 SP07, separate portal content components are 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

If you want to use the MDM Java API, deploy the JAVA API package according to the MDM 7.1 SP07 – Installation Guide <Platform>.

5.5.7 MDM ABAP API Activities If you did not use the ABAP API with MDM 5.5 SP05/SP06, you can skip this section.

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

You have to perform the following steps during the upgrade.

1. Deploy the MDM 7.1-related 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

You must deploy the MDM 7.1 ABAP API add-on 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.

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 7.1 - ABAP API Guide).

5. Upgrade Process

October 2011 39

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.

With MDM 7.1 SP04, the new parameter SAP RFC Hostname is available in the mds.ini. For more information, refer to the MDM 7.1 SP04 – ABAP API Guide.

1. Define SAP gateways For each SAP gateway, enter a value in parameter SAP RFC Gateways=. Separate the entries 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 independently 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 gateway, 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 on the Master Data Server (use MDM Console to check MDS_Log), 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

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 maintained. 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 calling transaction SM59. Configuring MDM ABAP API to Use a Secure Network Connection Starting from MDM 7.1 SP07, you can configure MDM ABAP API to use a secure network connection (SNC). For more information, see the MDM ABAP API Guide on the SAP Help Portal.

5. Upgrade Process

October 2011 40

5.5.8 MDM Monitoring and Supportability Environment There are some changes regarding the monitoring and support environment, for example SLD registration, CCMS availability or SMD connectivity.

Configure System Landscape Directory (SLD) registration

With MDM 7.1 the following settings in the Master Data Server configuration files mds.ini/mdis.ini/mdss.ini are obsolete: “SLDReg Utility Path”.

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. To enable the SLD registration of an MDM server, set the following configuration parameter: “SLD Registration=True”.

No manual upgrade steps are necessary.

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

Reuse MDM 5.5 SLD registration

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

Slddest.cfg Slddest.cfg.key

Register MDM 7.1 to the SLD

If you did not use MDM SLD registration for MDM 5.5, the new MDM 7.1 SAPINST-based installer allows you to perform the SLD registration in an additional installer step. Provide the following data:

SLD Hostname SLD Username/Password SLD Port

The two files slddest.cfg and slddest.cfg.key are written to the MDM 7.1 folder <System Drive:>:\usr\sap\<SID>\SYS\global.

MDM CCMS Agent Plug-In Activities The MDM CCMS templates in MDM 5.5 and MDM 7.1 are identical Upgrading the PROCMON configuration on the MDM host Upgrading the LOGMON configuration on the MDM host

If the CCMS environment was running in MDM 5.5, the only task is to exchange the old mdm_ccms.dll with the newly delivered one. Copy the MDM CCMS plug-in mdm_ccms.dll from folder [<System Drive>:]/usr/sap/<SID>/MDS<instance number>/exe 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 necessary.

If the CCMS environment did not exist in MDM 5.5, perform the following steps using the Installer: 1. Create CCMS environment /usr/sap/prfclog. 2. Provide specific CCMS Installer. 3. Unpack CCMS agent to /usr/sap/prfclog 4. Register CCMS agent to central monitor (CEN) using shell command

sapccmsr –R –f csmconf. This creates /usr/sap/prfclog/sapccmsr and adds a file sapccmsr.ini.

5. Upgrade Process

October 2011 41

5. Stop CCMS agent. 6. Copy mdm_ccms library (OS dependent) from

[<System Drive>:]/usr/sap/<SID>/MDS<instance number>/exe to [<System Drive>:]/usr/sap/prfclog/sapccmsr Modify sapccmsr.ini to add the plug-in command.

7. Start the ccms agent again.

SMD integration / Wily Introscope

If SMD integration has been 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.

5.5.9 SAP Exchange Infrastructure Activities XI content MDM BUSINESS

The XI content contains objects and preconfigured settings for SP03 and SP04 as well as for SP05 and SP06 repositories. Uploading the XI content for MDM 7.1 does not influence a running XI configuration.

XI communication channels

Using the new MDM 7.1 installation structure you have to adapt the folder definitions in the XI communication channel definitions. This is valid for MDM inbound and outbound channels.

5.5.10 MDM Web Services MDM 5.5 Web services are no longer delivered. If you are using MDM 5.5 Web services, you should now use the Web Service Generator to generate new Web services. Then adapt the Web service consumer code to use the generated MDM Web services instead of the MDM 5.5 Web services.

Deploy the new Web Service Generator as described in the corresponding MDM 7.1 – Installation Guide <Platform>.

5.5.11 Enterprise Portal Content / iViews / UWL If you are using neither MDM iViews nor Universal Worklist (UWL) with your current MDM 5.5 installation, you can skip this section.

With MDM 7.1 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 and is also valid for the upgrade from MDM 5.5 SP05 to MDM 7.1

More information: SAP Note https://service.sap.com/sap/support/notes/1235338.

MDM iViews The upgrade description in SAP Note 1235338 also includes the upgrade of the delivered MDM iViews. Before you start, note the following recommendations: One-Tier Environment

We recommend that you prepare the iView adaption before performing the upgrade activities.

a. Back up all MDM iViews in the appropriate development environment.

b. Adapt the iViews according to the guidelines described below.


5. Upgrade Process

October 2011 42

c. Test the iViews directly after the upgrade.

Two-Tier Environment First perform the adaption in your test environment:

a. Back up all MDM iViews in the appropriate test environment.

b. Adapt the iViews according to the guidelines described below.

c. After upgrading the test environment to MDM 7.1, test the adapted iViews locally.

d. Provide the adapted iViews to the Productive environment.

In the production environment:

a. Back up all MDM iViews in the appropriate development environment.

b. Replace the old iViews with the ones tested in the test environment as part of the upgrade process. Note: You should upgrade your custom developments based on MDM deliveries so that they run again after

the MDM upgrade. You can develop your own iViews based on iView templates delivered with MDM (you may not change the delivered iViews themselves), t as follows: a. The new iView references the MDM iView template. b. The new iView copies the MDM iView template.

5.5.12 Web UIs Change Tracking UI

You should deploy the MDM 7.1 Change Tracking UI according to the corresponding installation guide.

5. Upgrade Process

October 2011 43

5.5.13 MDM Enrichment Architecture You should deploy the MDM 7.1 Enrichment Controller according the corresponding installation and deployment information described under Installing and Deploying the Enrichment Controller in the MDM 7.1 Enrichment Architecture Guide.

When upgrading MDM Enrichment Architecture from MDM 5.5 to MDM 7.1, perform the following steps to enable the whole enrichment process. Further details of MDM configuration are provided in the relevant guides of MDM 7.1.

Update repository

Use MDM 7.1 Console to update the repository from MDM 5.5 to MDM 7.1.

Repository schema

Use the Enrichment Controller Administration tool to update the repository schema.

Workflow

Start the Data Manager and modify the “Autolaunch” option of the enrichment workflow as required. Note that the “Immediate” option is set to the default when the repository is updated from MDM 5.5. to MDM 7.1. You therefore have to reset this option after the update.

Import Map

1. Open the Import Manager for the updated repository.

The Import Manager displays a message that the maps are outdated and should be updated.

2. Approve the map update process and review results.

You can manually update a map which could not be updated automatically by choosing File -> Save update.

3. Load the import map used for the enrichment process. Note that you must provide the import file that was generated by the Enrichment Adapter.

4. Add a new field to the record source hierarchy and name it “Completed”.

5. Map the “Completed” field to the Enrichment_Status.Completed destination field.

6. Map the completed “Null” value to the “True” destination value and save the map.

Syndication Map

1. Open the Syndicator and load the map used for the enrichment process.

2. Go to the Map Properties tab and correct the parameter “Output Remote Systems”.

3. Save the map.

5. Upgrade Process

October 2011 44

5.5.14 MDM Web Dynpro Components 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, 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

SAP NetWeaver 7.3

For more information about creating an MDM destination for MDM 7.1 SP08, see SAP Service Marketplace at http://service.sap.com/installmdm71 How to Create MDM Connections with the MDM Destinations Administration Tool.

MDM Web Dynpro Configuration Manager

As of MDM 7.1 SP04, the MDM Web Dynpro Configurator provides a user interface for configuring MDM Web Dynpro components. The following components are provided: Result Set, Item Details and Search.

As of MDM 7.1 SP05, the MDM Web Dynpro Configurator was renamed to MDM Web Dynpro Configuration Manager. The following components were added: Merge, Compare and Match.

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, the actions, and the functions of the 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 consumed (as used components), 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 http://service.sap.com/installmdm71 MDM Web Dynpro Components Reference Guide.

To upgrade MDM Web Dynpro Components:

The steps below must be performed when upgrading from MDM 7.1 SP04 to MDM 7.1 SP05. However, we recommend to perform these steps when upgrading all versions.

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

For more information, see http://service.sap.com/installmdm71 MDM Web Dynpro Components Reference Guide -> The MDM Web Dynpro Configuration Manager -> Configuring a Project in the MDM WD Configuration Manager -> Transporting.

2. Save the exported configuration file.

3. Deploy the latest version of the MDM Web Dynpro components.

You can download them from: 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 Java WebDynpro for NW 7.11 MDM JAVA WD FRAMEWORK 7.1 7.11

4. Run the Configuration Manager.

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

http://service.sap.com/installmdm71

5. Upgrade Process

October 2011 45

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 will be 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 will be deleted. You must reassign these actions to the role after deploying the new security DC.

For more information, see MDM Web Dynpro Components Reference Guide -> Installing the MDM Web Dynpro Environment.

5.5.15 MDM Collaborative Processes for Material Available as of MDM 7.1 SP05. MDM Collaborative Processes for Material is a preconfigured, packaged solution to create a master data creation process. MDM customers can rapidly deploy and implement a working master data scenario based on MDM and BPM by using the content of the packaged solution as a starting point and then tailoring it to suit their own business scenario. In this collaborative process, MDM‘s functionality is exposed as Web services and Web-based data governance user interfaces which are combined in a logical process flow using BPM.

The deployment of the MDM Collaborative Processes for Material package does not require any update or upgrade activities.

For more information, see http://service.sap.com/installmdm71 MDM Business Content Extensions Collaborative Processes for Material Master Data Creation.

5.6 Uninstall MDM 5.5 SP05/SP06 We recommend that you keep the installation of the MDM 5.5 environment during the upgrade from MDM 5.5 SP05/SP06 to MDM 7.1.

If you want to uninstall MDM components, choose Add or Remove Programs from the Windows control panel. If you encounter problems, go to the specific directories (such as C:\program files\SAP MDM 5.5\server) and start the UNWISE32.EXE executable to uninstall the component.

Uninstall the MDM 5.5 Servers on all OS and in addition the MDM 5.5 GUI components on Windows OS.

6. Appendix

October 2011 46

6. Appendix 6.1 Other Information This chapter handles other changes to the MDM 7.1 environment that are not component-specific.

6.1.1 New Log File Format With MDM 7.1, log and trace files are no longer written in .xml format. MDM 7.1 logs are saved in two formats:

.csv format – Comma-separated format, can easily be viewed in spreadsheet applications like Microsoft Excel

.lv format – A SAP internal log viewer format that can be used directly in SAP monitoring tools like Solution Manager Diagnostics (for example for End2End Analysis).

MDM 7.1 cannot read the MDM 5.5 log file format, so MDM 5.5 logs should not be copied to the MDM 7.1 Logs folder.

6.1.2 New CLIX Commands Because MDM 7.1 uses the SAP Service Infrastructure, several server instance control commands have been added to the CLIX utility.

CLIX is able to start and stop any of the MDM services from any operating system listed in the PAM. This was not possible with the old mdsStart and mdsStop commands.

In addition, the Service Framework gives users the means to control MDM service authorization based on standard operating system user accounts. The new CLIX commands are collected in the CLIX i command section and start with “ic”.

Command Description CLIX icInfo Returns information about accessible service instances

CLIX icGo, CLIX icStart Starts one or more service instances

CLIX icHalt, CLIX icStop Stops one or more service instances by sending a SIGQUIT (or SIGINT if timeout has elapsed)

CLIX icShutdown Stops one or more service instances by sending a SIGQUIT

CLIX icSight Stops one or more service instances with kill signal (win) and SIGINT to the target server

For more information about how the use these new CLIX commands, run the following command line: CLIX i

These new commands effectively replace the following CLIX commands: CLIX mdsStart, CLIX mdsStop.

To use SSL, you must first update the clix.ini file, which is located in the same location as the clix.exe: \usr\sap\<SAPSID>\<Instance Folder>\exe

If you do not have a clix.ini file, you must create one before installation and add the following parameters to it:

Add the path to the sapcrypto.dll and the Service Control Security Enabled parameter to the clix.ini file as follows:

6. Appendix

October 2011 47

SSL Lib Path=C:\usr\sap\<SAPSID>\<Instance Folder>\exe\sapcrypto.dll


When executing CLIX commands, a new parameter, –Y, is available.

After adding MdsHostSpec, add: –Y <the path to the client.pse> -# <Server SSL port number>

For example:

CLIX mdsVersion <MdsHostSpec> -Y \usr\sap\<SAPSID>\<Instance Folder>\sec\client.pse -# <MDS SSL port number>

Hard Shutdown (SIGINT)

A hard shutdown shuts down the server immediately, regardless of what the process is doing. Do not use this option unless the process is hung and you want it to exit immediately or you do not care if any data being processed is lost. The commands icTerminate and icSigInt actually send a SIGINT to the target server on UNIX.

Syntax clix [it||icSigInt||icTerminate] <hostname> <domain name(if server is on windows)\username> <password> <target server process name>...

Example

This command sends a hard shutdown signal to mds and mdis on host <host>:

clix it <host> <host>\myUser myPassword mds mdis

Soft Shutdown with Timeout (SIGQUIT/SIGINT)

A soft shutdown with timeout shuts down the server gracefully, but once the timeout period elapses it forces a "hard shutdown" and any data being processed at that time is lost. The commands icHalt, icStop and icShupdown actually send a SIGQUIT to the target server on UNIX (or SIGINT for icHalt/isStop if timeout has elapsed).

Syntax

clix [ih||icHalt||icStop] <hostname> <domain name(if server is on windows)\username> <password> <target server process name>... [-T <timeout value in secs.>]

Example

This command sends a soft shutdown signal with 1000 second timeout to mds and mdis on host <host>:

clix ih <host> <host>\myUser myPassword mds mdis -T 1000

Soft Shutdown without Timeout (SIGQUIT)

A soft shutdown without timeout shuts down the server gracefully with no timeout and consequently no data loss.

Syntax

clix [is||icShutdown] <hostname> <domain name(if server is on windows)\username> <password> <target server process name>...

6. Appendix

October 2011 48

Example

Example to send a soft shutdown signal without a timeout to mds and mdis on host <host>:

clix is <host> <host>\myUser myPassword mds mdis

For complete details about the new CLIX commands, refer to section CLIX Command Line Interface in the MDM 7.1 Console Reference Guide.

7. Reference

October 2011 49

7. Reference The related documentation about MDM is located on SAP Service Marketplace at http://service.sap.com/installMDM71:

MDM 7.1 – Master Guide

MDM 7.1 – Configuration Guide

MDM 7.1 – Installation Guide <Platform>

MDM 7.1 – Solution Operation Guide

MDM Reference Documentation

MDM 7.1 - Console Reference Guide

MDM 7.1 - Data Manager Reference Guide

MDM 7.1 - Import Manager Reference Guide

MDM 7.1 - Syndicator Reference Guide

MDM 7.1 - Publisher Reference Guide

http://service.sap.com/installMDM71

Date post:	24-Oct-2015
Category:	Documents
Upload:	srinivas-rentala
View:	30 times
Download:	6 times

MDM71SP08_UpgradeGuide_v30

Documents