mdm import and syndication server & port concept · 2019-11-12 · content overview mdm 5.5...

SAP NetWeaver MDMMDM Import and Syndication Server& Port Concept

Michael ReilSAP NetWeaver Product Management

Welcome to your RKT Live Expert Session

Please note that we are recording this session!

© SAP AG 2005, SAP NetWeaver MDM / 2

Your Instructor

Michael ReilSAP NetWeaver MDM Product Management

MDM Import and Syndication Server& Port Concept

SAP NetWeaver MDM


Content Overview

MDM 5.5 SP03Port ConceptEncapsulates all of the configuration and logistical information associated with inbound and outbound processing

MDM Import Server Load master data records periodically from various sources

MDM Syndication Server Distribute master data records periodically to defined destinations


New Components in the Architecture

Import ServerParsingStructural MappingValue MappingRecord MatchingKey Mapping

Thin ClientSearch / ViewData MaintenanceOCI

User InterfaceRich Client

Data ManagerImport ManagerSyndicator

Master Data ServerCore ServicesMemory CacheDatabase AbstractionRepository Management

Syndication ServerExtractionStructural MappingValue MappingNumber AssignmentKey Mapping

SAP NetWeaver XI SAP NetWeaver Application ServerInbound Processing Outbound ProcessingAPI / Monitoring

SAP NetWeaver XI

Image ManagerPublisher

Major Building Blocks

Import ServerCore Services

Value Mapping

Key Matching

Transformation

Parsing

Inbound Ports

Raw Object Data

Loading

Syndication ServerCore Services

Key Mapping

Structural Transformation

Outbound Ports

Messages

Extraction

Scheduling


MDM Syndication Server

Central Master-Data Management

MDM Import Server

Master-Data Consolidation

Master-Data Harmonization

In the context of MDM IT Scenarios

Load Master Data Consolidate Master Data

Load Master Data Consolidate Master Data Distribute Master Data

Distribute Master DataCreate Master Data


Port Concept – Overview

Key Information encapsulated by a PortName Display NameCode Technical Name (name of the folder)Type Direction (inbound or outbound)Format File Format (e.g. Excel, XML Schema)

XML Schema XML Schema file (e.g. DEBMDM06.xsd)Client System Client SystemMap Map File

Features

Ports are designed to eliminate inbound and outbound processing complexity

By eliminating manual selections, ports reduce the likelihood of errors, which could lead to incorrect or incomplete processing

Benefits

Basis for automated Imports & Exports

DBMS ServerRepositoryDirectionClient SystemPort

Program Files SAP MDM 5.5 Server Distributions

* For further details see MDM Console User Guide

What is a Port*?

A port represents the logical point of contact between MDM and the outside world (e.g. SAP XI or a user of the MDM Import Manager). It represents the physical staging location of data and a logical handle by which to identify all of the encapsulated information.


Port Concept – Configuration

Configure PortsFive Steps to configure Ports

Step 1 to 3 are prerequisites to be able to create ports. If Client Systems with assigned maps are already exist only step 4 and 5 is relevant.

1 Create a New Client SystemAny logical system that can supply data to or receive data from MDM is known as a client system.

2 Assign Import MapTo transfer maps among client systems they can be exported into a map file in the file system. These map files can be import into another client system.

3 Assign Syndication Map(see 2)

4 Create Inbound PortHow to create a port for inbound processing

5 Create Outbound PortHow to create a port for outbound processing

Click to start screen cam


Port Concept – Configuration (cont.)

Configure PortsFive Steps to configure Ports (cont.)

Automatically created Folder StructureThe files associated with ports are stored in a shared file system location with a fixed directory structure beneath a configurable root. Its location is specified in the mds.ini file:

[MDM Server]…Distribution Root Dir=C:\Program Files\SAP MDM 5.5\Server\Distributions\…

The following folder structure was automatically created as result of the described port configuration:

DBMS ServerRepositoryDirection

Client SystemPort



MDM Import Server*– Overview U

se

Cas

e

Load master data records periodically from various sources based on the extended port concept.

This new component separates the core processing of source data import to a background process (service), from the front-end processing (import map generation).

Can be utilized in addition to MDM Import Manager or Import Mgr Batch.

Repository

MDM Import Server

MDM Server

MDM Import Manager(GUI)

Create an import map once, and re-use of the map for future source dataimport without any operator intervention

Once the data is delivered by SAP XI on a specific port, it will automaticallyget picked within a configurable time interval and queued up for import processing

The outcome of the import processing are updated or new master data records in the repository and log files of the entire load process

Features

Master data imports can be easily automated and run in the background

No user interaction required

Provides monitoring capabilities for data import

Enables scalability and load balancing for data imports

Benefits

* Currently available for Windows platform

Automated Import


MDM Import Server – Further Information

Technical DetailsService*

MDM Import Server run-time configuration can be specified in mdis.ini file, which is located in the install directory oft MDM Import Server.

Ports**Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from client systems. Extended port folder structure to store log files.

RuntimeSince by definition a service does not have a UI, the MDM Import Server functionality may be checked using the tools available on the platform that the service is deployed on.MDM Import Server connects to each repositoryin order, then retrieves inbound distribution portinfo and imports the data.

Monitoring CapabilitiesStep-by-step audit trail of the import and a status indicating whether the import succeeded or not. These log files are accessible via MDM Console.

Availability monitoring integrated into CCMS * Currently available for Windows platform** For further details see MDM Console User Guide

DBMS ServerRepositoryDirectionClient SystemPort

Source Files Log Files

Status Files


new

Log Files

ExportImport


MDM Import Server – Configuration

Configurationmdis.ini file

Server

Interval

Automap Unmapped Value

Unmapped Value Handling

Always Use Unmapped Value Handling

[Customers*]

Specifies the computer name of the MDM Server which MDM Import Server connects to

Specifies the time interval between import cycles

Determine if unmapped values should be mapped automatically if possible

If set to true the following Unmapped Value Handling is activated

IgnoreNewValue = 0 or AddNewValue = 1 (see images at the bottom)

This section is created for each loaded repository and supplies the connection parameters for that repository

All other configuration is kept in the import maps!


MDM Import Server – Example

Load Customer RecordsThis example shows an automated import

1 Start MDM Import Server serviceThe MDM Import Server will be started manually in this case. To automatically start the MDM Import Server change the start type to Automatic.

2 Deliver data file to portThe data file (XML message) will be copied into the port folder Ready. In a real business environment the data would be delivered by SAP XI.

3 Monitor import processing resultsLog files (stored in the port folder Log) are accessible via MDM Console.

4 Review master data records and key mappingUse the MDM Data Manager to review the newly imported master data records and corresponding key mapping.



MDM Syndication Server*– Overview

Distribute master data records periodically to defined destinations based on the extended port concept.

This new component separates the core processing of master data export to a background process (service), from the front-end processing (syndication generation).

Can be utilized in addition to MDM Syndicator or Syndicator Batch.

Create a syndication once, and re-use of the syndication for future master data export without any operator intervention

Delivers master data records as data files (e.g. XML messages) to outbound ports triggered by a simple scheduling mechanism

The outcome of the export are data files (e.g. XML messages) for further processing by SAP XI and log files of the entire syndication process

Features

Master data exports can be easily automated and run in the background

No user interaction required

Provides monitoring capabilities for data export

Enables scalability and load balancing for data exports

Benefits

Repository

MDM Syndication Server

MDM Server

MDM Syndicator(GUI)

Use

Cas

e

Automated Export

* Currently available for Windows platform


MDM Syndication Server – Further Information

Technical DetailsService*

MDM Syndication Server run-time configuration can be specified in mdss.ini file, which is located in the install directory oft MDM Syndication Server.

Ports**Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from client systems. Extended port folder structure to store log files.

RuntimeSince by definition a service does not have a UI, the MDM Syndication Server functionality may be checked using the tools available on the platform that the service is deployed on.MDM Import Server connects to each repositoryin order, retrieves outbound distribution portinfo and exports the data.

Monitoring CapabilitiesStep-by-step audit trail of the export and a status indicating whether the export succeeded or not. These log files are accessible via MDM Console.

Availability monitoring integrated into CCMS

DBMS ServerRepository

DirectionClient SystemPort

Data Files Log Files

new


Log Files ExportImport

* Currently available for Windows platform** For further details see MDM Console User Guide


MDM Syndication Server – Configuration

Configurationmdss.ini file

MDM Server Name

Auto Syndication Task Enabled

Auto Syndication Task Delay

String Resource Dir

Default Interface Language Code& Default Interface Country Code

[Customers*]

Specifies the computer name of the MDM Server which MDM Syndication Server connects to

Boolean parameter tells whether the MDM Syndication Server should start upon startup: true … start / false … do not start

Specifies the time interval between auto export cycles. Zero means starting next cycle right away (continuous execution). Delay parameter is read in the end of each cycle

Specifies the location of language files

Parameters are not relevant at the moment

This section is created for each loaded repository and supplies the connection parameters for that repository

All other configuration is kept in the syndication maps!


MDM Syndication Server – Example


Distribute Master DataThis example shows an automated export

1 Review Port ConfigurationIn this case there are three outbound ports defined. One of them (NCS2) is configured to generate new keys for records sent to this client system.

2 Start MDM Syndication Server serviceThe MDM Syndication Server will also be started manually. To automatically start the MDM Import Server change the start type to Automatic.

3 Examine data in the port folder structureThe data files (here XML messages) are stored in the port folder Ready. In a real business environment the data files would picked-up by SAP XI for further processing.

4 Monitor import processing resultsLog files (stored in the port folder Log) are accessible via MDM Console.

5 Export ResultsData and Log files have been created for all defined outbound ports. Key mapping was updated accordingly.


MDM Syndication Server – Export Results

Situation before the first MDM Syndication Server run

1

Updated data will be sent to client system NCS1

2 New data will be sent to NCS2 with a new targetsystem specific key

3

Key mapping information will be updated accordingly

4Exemplary key mapping information for a BI system

5


Hints and Troubleshooting

HintsA port is locked for the duration of import, meaning no other import with MDM Import Manager can be done using this port The same applies for MDM Syndication Server

MDM Import Server can not trigger workflows on import(planned enhancement for next release)

Batch files can be used to start or stop MDM Import Serverand MDM Syndication Server instead of navigating through the Windows menus

If an MDM Import Server run failed the according inbound port will be locked. To unlock the port do the following steps:

Check log file to find out if the issue is related to the data and/or map

If caused by an incorrect map stop MDM Import Server

Connect to port using MDM Import Manager and check Import Status

Repair and save map (do not execute import!)

Leave MDM Import Manager and start MDM Import Server again

Verify if data now has been processed successfully

The same applies for MDM Syndication Server

Troubleshooting

Grayed out No data available or port is locked

To stop use option stop instead of start


Thank you for your kind interest

Questions ??

Please do not hesitate to ask them now…


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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Copyright 2005 SAP AG. All Rights Reserved

mdm import and syndication server & port concept · 2019-11-12 · content overview mdm 5.5...

Documents