MDM PI Adapter

Using SAP NetWeaver PI Adapter forMDM

Sam RajuSAP NetWeaver RIG AmericasSAP Labs, LLC

August 12, 2009

SAP AG 2009,KHNC – Using SAP NetWeaver PI Adapter for MDM/ Sam Raju / 081209/ 2

Disclaimer

This presentation outlines our general product direction and should not berelied on in making a purchase decision. This presentation is not subject toyour license agreement or any other agreement with SAP. SAP has noobligation to pursue any course of business outlined in this presentation or todevelop or release any functionality mentioned in this presentation. Thispresentation and SAP's strategy and possible future developments aresubject to change and may be changed by SAP at any time for any reasonwithout notice. This document is provided without a warranty of any kind,either express or implied, including but not limited to, the implied warrantiesof merchantability, fitness for a particular purpose, or non-infringement. SAPassumes no responsibility for errors or omissions in this document, except ifsuch damages were caused by SAP intentionally or grossly negligent.


1. Introduction2. Message Flow3. Configuration in the SAP NetWeaver PI4. Monitoring and Error Handling5. Usage of PI within MDM 5.5 Vs MDM 7.16. Summary

Agenda


Introduction

MDM offers components that are able to import and export data into/out of MDMImport Manager, Import ServerSyndicator, Syndication Server

SAP’ s common middleware for data distribution is SAP NetWeaver Process Integration

With SAP NetWeaver MDM5.5 the PI integration is implemented via FTP and File NetworkShares

MDM 7.1 offers new functionality to directly push/pull data into/from MDM using the MDMJava API (e.g. Port Functions)

Tighter MDM PI integration without the usage of a file system based transfer



Agenda


Message Flow PI to MDM

Data sent from any connected system to PI is stored within PI’s internal databaseXML message is forwarded to the defined communication channel (MDM PI Adapter)MDM PI Adapter itself utilize the MDM Java API for submitting the message to MDM usingthe MDM Port functionsThose store the message in XML format into the corresponding port’s ready folder so thatMDIS can import the files independentlyMDM PI Adapter updates the delivery status

in the PI Monitoring“Finished import event” is triggered by MDM

and received by the MDM PI AdapterThe import status is used to update the PI Monitoring

accordingly

CRMERP

MDM Server

IDOC/XML

MDMAdapter

SyndicationServer

ImportServer

Legacy


Message Flow MDM to PI

The syndication event is triggered by MDM as soon as the syndication is finishedThe data is available as XML file in the corresponding port folderThe MDM PI Adapter catches the syndication event and uses the MDM Port Functions toretrieve the dataPI message is created and sent to the PI server for receiver determination and furthermessage processing


ConfigurationcacheIS

MDM Message Flow in PI

AdapterSender

AdapterReceiver

Q

AdministrationSecurity

MonitoringTracingLogging

Module Processor

Backend

Channel

Messaging

Configurationcache

AdapterFramework

MappingReceiverDetermination

Queue

XI Messages

System Landscape Directory• Holds component descriptionincluding address data

Exchange Profile• Holds central connection descriptionsincluding user, passwords

RWB

IBDir

Adapter Engine in SAP J2EE

Message, Componentmonitoring et.al.

Scenario Configuration

httpIDocBPE



Agenda

SAP AG 2009,KHNC – Using SAP NetWeaver PI Adapter for MDM/ Sam Raju / 081209/ 10© SAP 2008 / Page 10

Communication Channel in PI / Inbound andOutbound / Receiver and Sender


Adapter Metadata in PI

-



Agenda


Monitoring and Error Handling

PI offers several monitoring possibilities. The MDM PI Adapter supports the technicalMessage Monitoring (transaction SXMB_MONI) as well as the Communication ChannelMonitor

The MDM PI Adapter supports the PI Adapter Framework trace and log interface. Thisenables the usage of the SAP J2EE logging and tracing which is invoked by using the TraceObject

In general resolvable errors are caused by connectivity problems between the MDM PIAdapter and MDM itself

Possible Error Action to resolve the error

Connection to MDM failed due to To resolve this error:

a) Wrong Adapter Meta Data Check the Communication Channel configuration on PI andcompare the given configuration with the settings in MDM.

b) MDM Server is not running Check the MDM system landscape and start the MDM Server.

c) MDM Repository is not running Check the MDM Server using MDM Console. Start theRepository.

Message delivery failed due to To resolve this error:

a) MDIS is not running Check the MDM system landscape and start the MDM ImportServer.

b) MDSS is not running Check the MDM system landscape and start the MDMSyndication Server.


Monitoring within PI

SXMB_MONISXMB_MONI

CommunicationChannel Monitoring

CommunicationChannel Monitoring


DEMO



Agenda


Usage of PI within MDM5.5 versus MDM7.1

MDM 5.5 MDM 7.1

Monitoring of message flow restricted to innerboundaries of MDM

High reliability due to end-to-endmonitoring of message flow between PI andMDM

High effort for file adapter / FTP setup MDM adapter shortens setup timesignificantly

Difficult error handling due to unspecific logfiles

Improved error handling for multiplerepository implementations



Agenda


Summary

MonitoringMessage flow between PI and MDM can be monitored end to end (e.g. show if messageshave been received and properly imported into MDM)Error handling is improved because the Communication Channel in PI is pointing to onespecific Repository PortRestarting of messages if a service is unavailable is possible

Configuration / System Landscape Setup / IntegrationMDM Adapter can be used instead of the File AdapterConfiguration of FTP is no longer neededMDM Adapter is easy to implement and straightforward to monitorHigher reliability of data transfer


Q&A

Questions?


Thank you!


Copyright 2009 SAP AGAll 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 changedwithout prior notice.

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

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed arethe 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 writtenpermission 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 thatthis 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 theaccuracy 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 orimplied, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen vonProdukten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertragoder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieserPublikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherigeAnkündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte,Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a.,aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialienentstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen,unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über InternetseitenDritter ab.

Alle Rechte vorbehalten.

Documents

MDM PI Adapter