MDM PI Adapter Guide

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/956ccc9521062de10000000a42189d/frameset.htm
Created on July 30, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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 and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 11
Table of content
1 MDM PI Adapter Guide
1.1 Overview
1.1.1 Integration Architecture
1.1.2 Landscape Prerequisites
1.1.3 Frequently Used Acronyms
1.1.4 Useful Links
1.2 Functionality
1.2.1 Quality of Service
1.2.2 Message Flow
1.3 Installing the MDM PI Adapter
1.3.1 Deploying the MDM PI Adapter Software
1.3.2 Importing the MDM PI Adapter Content
1.4 Setting Up Messaging
1.4.1 Setting up the PI Scenario
1.4.2 MDM Adapter Specific Configuration
1.4.2.1 Setting Up Inbound Messaging into MDM
1.4.2.2 Setting Up Outbound Messaging from MDM
1.5 Monitoring the MDM Adapter
1.5.1 Integration Monitoring - Runtime Workbench
1.5.2 Monitoring XML Messages in SAP GUI
1.5.3 PI Alert Mechanism
1.5.4 Logging and Tracing
1.6 Troubleshooting and Error Handling
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 11
1 MDM PI Adapter Guide
1.1 Overview
The transfer of data messages between MDM and other remote systems is one of MDM's core functionalities. MDM offers several tools that are able to import data
into MDM (Import Manager, Import Server) and distribute data from MDM (Syndicator, Syndication Server).
The common SAP middleware for message exchange and data distribution is SAP NetWeaver Process Integration (PI), which is used to facilitate the exchange of
information among a company's internal software and systems, and those of external parties.
In this guide, we present a general overview of the MDM PI Adapter focusing on its functionality for exchanging messages in a heterogeneous system landscape.
1.1.1 Integration Architecture
In MDM versions prior to MDM7.1, the MDM PI integration is carried out via FTP and File Network shares (File Adapter) since MDM requires a file system-based
message transfer mechanism. Data messages are stored in a physical file system for inbound and outbound processing.
As of MDM 7.1 the MDM PI Adapter is used for direct communication between MDM and the PI server. The MDM PI Adapter delivers data to and pulls data from
MDM by using the MDM Java API port functions enabling a tighter MDM PI integration as well as message monitoring.
The diagram above shows how the MDM PI Adapter facilitates direct messaging between the PI and MDM servers.
All other communication methods between SAP NetWeaver PI server and the different attached systems are already documented and are not covered in this
document.
1.1.2 Landscape Prerequisites
The following software must be installed prior to using the MDM PI Adapter
SAP NetWeaver MDM 7.1
One of the following SAP NetWeaver PI servers:
PI 7.0 (SP 15 and higher)
PI 7.1 (SP 07 and higher) or PI 7.11 (SP01 and higher)
Caution
There are different versions of the MDM PI Adapter which correspond to the relevant version of the SAP NetWeaver PI server (PI server); one for
PI 7.0 and the other for PI 7.1 and PI 7.11); the two versions are not interchangeable. Ensure that you have downloaded the correct version for your
landscape.
For detailed list of prerequisites prior to installation, see Installing the MDM PI Adapter.
1.1.3 Frequently Used Acronyms
1.1.4 Useful Links
For more information about the installation, upgrade, and operations of SAP NetWeaver MDM, see http://help.sap.com/nwmdm71.
For information about SAP NetWeaver installation, upgrade, operation, and maintenance, see http://help.sap.com/nw_platform.
For more information about network and communication security in MDM that affects the MDM PI Adapter (such as network ports, and so on), see the
Network and Communication Security section in the MDM Security Guide.
1.2 Functionality
As of MDM 7.1 you can use the MDM PI adapter to facilitate direct messaging between the PI and MDM servers.
ACK Acknowledgment
AS Application Server
MDM Master Data Management
MDS MDM Server
MDIS MDM Import Server
MDSS MDM Syndication Server
PI Process Integration (previously known as XI Exchange Infrastructure)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 11
For more information, see:
Quality of Service
Describes the mechanisms related to message delivery
Message Flow
Describes the message processing in both the sender and receiver directions
1.2.1 Quality of Service
Quality of Service (QoS) is an attribute that determines how a message is delivered.
The MDM PI Adapter guarantees the successful delivery of data to MDM and supports the following models for Quality of Service message delivery:
Exactly Once (EO)
The message is sent to the receiver only once. There is no serialization, the processing sequence of subsequent messages at the receiver cannot be
determined in advance.
Exactly-Once-In-Order (EOIO)
In some integration scenarios, the serialization of MDM messages sent to backend systems is important. In this model, the messages are delivered in the
same sequence as they were received in the PI server.
In both models, the message flow between the PI and MDM servers is asynchronous.
1.2.2 Message Flow
Message processing involves various steps in the sender and receiver direction.
The MDM PI Adapter supports the following communication:
Receiving data into MDM from the PI server
The PI server receives data from any connected system and pushes the data into a configured MDM inbound port using the MDM PI Adapter.
Sending data from MDM to the PI server
MDM triggers data distribution (syndication event). The MDM PI Adapter collects the data from the connected MDM outbound port, wraps it as a message,
and pushes it into the PI server pipeline.
Inbound Message Flow to MDM
The following process shows the message flow of the MDM PI Adapter receiver from the PI server to MDM (see diagram below):
1. A message sent from any connected system to the PI server is stored within the PI server's internal database.
2. The message is forwarded to the defined communication channel (MDM PI Adapter).
3. The MDM PI Adapter delivers the message to the MDM server by using the functionality of the MDM Java API ports.
4. The MDM PI Adapter updates the message delivery status using the PI monitoring system.
5. MDM imports the message independently using the MDM Import Server (MDIS). Once the import is completed, a processed import event is triggered.
6. The MDM PI Adapter captures the processed import event and updates the PI monitoring sytem with the message import status.
7. When the incoming message is marked with a request for an application ACK (acknowledgement), an acknowledgement message is sent back to the
sender system (for example, when the incoming message is an IDoc originating from a SAP system).
Outbound Message Flow from MDM
The following process shows the message flow of the MDM PI Adapter sender from MDM to the PI server (see diagram below):
1. A syndication processed event is triggered as soon as syndication to the corresponding outbound port is completed.
The data is available as an XML file(s) in the corresponding port folder.
2. The MDM PI Adapter captures the syndication processed event and retrieves the data by using the functionality of the MDM Java API ports.
3. For each data file, a PI message is created and then sent to the PI server for receiver determination and further message processing.
Note

The syndication event can also be triggered by manual port syndication as follows:
1. Open the MDM Syndicator.
2. From the File menu, choose New.
3. In the Type field, select port.
4. Select the relevant port.
5. Execute the syndication.
If the port is not selected, manual syndication is not possible with the MDM PI Adapter.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 11
Note
MDM uses the distribution port folders as a persistency layer for data transport. Upon request for retrieval of syndication data via the MDM API, MDM delivers
all available data to the requesting application.
1.3 Installing the MDM PI Adapter
Use
To make the MDM PI Adapter operational in a SAP NetWeaver landscape, a few deployment steps must be carried out.
Prerequisites
The PI landscape has been installed and configured.
For more information, see the SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver Exchange Infrastructure.
MDM 7.1 system landscape has been installed and configured.
For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 MDM Installation Guide.
The following components are installed on your SAP NetWeaver Application Server Java:
Prior to MDM 7.1 SP07
MDM JAVA API ( MDM _JAVA_ API .sca)
As of MDM 7.1 SP07
MDM JAVA API ( MDM _JAVA_ API .sca)
MDMCONNECTOR ( MDM _CONNECTOR.sca)
Note
Make sure that you use the MDM Connector according to the SAP NetWeaver AS Java version.
For more information about deploying the Java API library and MDM Connector, see
Getting Started with Java API
Installing and Referencing the MDM Connector Installation
service.sap.com/sltoolset . Go to Software Logistics Toolset 1.0 Documentation System Maintenance Updating SAP Systems Using
Software Update Manager .
Procedure
Deploy the MDM 7.1 Adapter software on your SAP NetWeaver Application Server Java (AS Java).
For more information, see Deploying the MDM PI Adapter Software.
Import the MDM PI Content
For more information, see Importing the MDM PI Adapter Content.
1.3.1 Deploying the MDM PI Adapter Software
The PI Adapter Engine is an AS Java-based runtime component deployed on an SAP NetWeaver Application Server Java (AS Java). The Adapter Engine hosts
resource adapters for integrating applications and systems. It is automatically installed on the Process Integration Server as the central Adapter Engine. It can also
be installed on any SAP NetWeaver AS Java. In this case, it is a non central Adapter Engine.
For more information, see SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver Exchange Infrastructure Runtime Connectivity Adapter
Engine.
The direct link is: Adapter Engine.
MDM PI Adapter supports the central as well as the non central PI Adapter server and is deployed on one of the following SAP NetWeaver servers:
SAP NetWeaver PI 7.0 SP15 and higher
SAP NetWeaver PI 7.1 SP07 and higher
SAP NetWeaver PI 7.11 SP01 and higher
Prerequisite
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 11
Prerequisite
The MDM PI adapter software component SCA file must be deployed into a PI Adapter server. To deploy the MDM_ADAPTER SCA file, use the SAP Software
Update Manager (SUM) tool.
Prior to deploying the MDM PI Adapter software, you must download the SCA file from the SAP Service Marketplace.
Procedure
Downloading the MDM PI Adapter SCA file
Any customer with a valid SAP Service Marketplace User ID (S-User) license can download the MDM_ADAPTER SCA file as follows:
1. Log on to the SAP Software Download Center (SWDC) at http://service.sap.com/swdc .
2. From the navigation panel on the left, choose Support Packages and Patches Browse our Download Catalog to open a list of SAP's downloadable
products.
3. Scroll down the main page and choose SAP NetWeaver and complementary products
4. Choose SAP MDM.
5. Choose SAP NETWEAVER MDM 7.1 Entry by Component.
6. Choose one of the following:
PI Adapter for NW 7.0
PI Adapter for NW 7.1x (where x is the Enhancement Package number)
7. Download the SCA files as follows:
For PI Adapter for NW 7.0
1. Choose MDM ADAPTER 7.1 7.0.
2. Choose # OS independent to see the available objects for download.
3. Select and download the appropriate version. For example, MDMADAPTER<SP-Number>_<Patch-Number>-10005238.SCA
For PI Adapter for NW 7.1x
1. Choose MDM ADAPTER 7.1 7.1.
2. Choose # OS independent to see the available objects for download.
3. Select and download the appropriate version. For example, MDMADAPTER<SP Number>_<Patch Number>-10005240.SCA
8. Download the archive to a folder of your choice. Always use the same folder name when you update to a new version.
Deploying the MDM PI Adapter Software
To deploy a new software component or apply a higher Support Package, use the Software Update Manager (SUM) tool. For more information, see the SUM
guide at service.sap.com/sltoolset . Go to Software Logistics Toolset 1.0 Documentation System Maintenance Updating SAP Systems Using
Software Update Manager .
Note
The Java Support Package Manager (JSPM) has been replaced by the Software Update Manager (SUM). SAP strongly recommends that you use SUM
for all Java maintenance scenarios for SAP NetWeaver -based systems. For detailed information on JSPM replacement, see SAP Note 1589311 .
1.3.2 Importing the MDM PI Adapter Content
Use
MDM PI (XI) Adapter Content must be imported into the PI repository to enable configuration of integration scenarios using the MDM PI Adapter as a
communication channel.
The PI content for the MDM PI Adapter is generic and object free as it encapsulates the MDM PI Adapter metadata only.
In addition, SAP delivers MDM Business 7.1 PI content. This PI content is object-specific as it is designed for the MDM repositories delivered with MDM
Business Content 7.1. This PI content is optional and is not required to run the MDM PI Adapter.
Procedure
For initial deployment or for updating the MDM PI Adapter Content, import the MDM PI Adapter metadata ( TPZ file) into the PI repository.
For PI 7.0, use the Integration Repository tool
For more information, see the SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver 7.0 (2004s) Installation, Configuration, Upgrade
Technology Consultant's Guide Enabling Application-to-Application Processes Application-to-Application Integration Configuration of Usage Type
Process Integration (PI Wizard-Based Basic Configuration Importing Process Integration Content.
The direct link is: Importing Process Integration Content.
For PI 7.1 use the Enterprise Services Builder tool (ESR)
For more information, see the SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver 7.1 SAP NetWeaver Process Integration 7.1
System Configuration and Administration Configuration Guide Configuration of SAP NetWeaver Configuration of SAP NetWeaver Systems PI
(Process Integration) Wizard-Based Configuration Importing ESR Content.
The direct link is: Importing ESR Content.
1.4 Setting Up Messaging
In addition to a technical infrastructure for process integration, SAP delivers process integration content to facilitate the implementation process including setting up
messaging.
For an overview of SAP process integration content for SAP NetWeaver, see SAP Help Portal at http://help.sap.com/netweaver Concepts of Process Integration
(XI).
To download process integration content for Master Data Management from the SAP Service Marketplace carry out the following procedure:
1. Log on to the SAP Software Download Center (SWDC) at http://service.sap.com/swdc .
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 11
2. From the navigation panel on the left, choose Download Support Packages and Patches Browse our Download Catalog to open a list of SAP's
downloadable products.
3. Scroll down the main page and choose SAP NetWeaver and complementary products.
4. Choose SAP MDM.
5. Choose SAP NETWEAVER MDM 7.1 Entry by Component XI Content.
6. Choose XI CONTENT MDM BUSINESS 7.1.
7. Choose # Database independent to see the available objects for download.
8. Select and download the appropriate version of the following file: MDMBUSCONT71<SP Number>_<Patch Number>-20004539.ZIP.
9. Extract the archive to a folder of your choice. Always use the same folder name when you update to a new version.
1.4.1 Setting up the PI Scenario
To set up a PI scenario, define the following configuration objects:
Business system/service
Sender agreement
Receiver determination
Interface determination
Receiver agreement
For more information on how to configure the above objects, see SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver Exchange Infrastructure
Configuration.
1.4.2 MDM Adapter Specific Configuration
You can configure the MDM PI Adapter for inbound and outbound messaging corresponding to receiver and sender communication channels.
Note
In both cases, the MDM PI Adapter is indifferent to the message type and does not change the message content during the processing or validate the
structure. The MDM PI Adapter is mainly responsible for the connectivity between the PI and MDM servers.
You can use any message type on the PI server, but to be able to import the data successfully into MDM, the message type must match the corresponding
import map configured in the inbound MDM port.
For more information, see
Setting up Inbound Messaging into MDM.
Setting up Outbound Messaging from MDM.
1.4.2.1 Setting Up Inbound Messaging into MDM
Use
Each inbound message from a backend system that is routed into PI, can be delivered to MDM using the MDM PI Adapter.
Prerequisites
Make sure that the MDM Java API Connector deployed on the AS Java engine matches the version of the MDM server on which the repository is mounted.
Procedure
1. Open the PI Integration Directory tool.
2. Create a new communication channel; enter MDM as the Adapter Type.
3. Set as Receiver.
4. Configure the following MDM access parameters (all MDM access parameter values can be found in the MDM Console tool):
MDM Server (host name or IP)
Note
If your MDM server uses a network port other than the default, you can append the port number after a colon or a semicolon, using the following
format <serverName>:<portNumber> For example, localhost:59950
Secure Connection
Select this checkbox to use a secure communication channel to the MDM server. In this case, the MDM server name must include the number of the
secured port.
Note
To use a secure connection, you must first import a certificate file (.crt) to the dedicated key store view named MDMKeystore on your
application server.
For more information about the certificate file, see the following sections in the MDM Java API and .NET API Guide:
Alternative Session Creation MethodEnabling Secure Connections
Managing Connections and Sessions
For more information about secure connections, see the Network and Communication Security section in the MDM Security Guide.
MDM Repository Name (as well as User and Password)
DBMS Server (host name or IP) and DBMS Type
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 11
Note
Important! These parameters must be entered as shown in the Repository Detail pane under the corresponding server node.
Port Code and Remote System Code of the inbound MDM port
Note
Important! These parameters must be entered as shown in the Ports and Remote Systems nodes under the Admin tree of the corresponding
repository node.
Caution
Make sure that there are no duplicated MDM receiver communication channels. Check that there is not more than one MDM receiver configured per MDM
inbound port in your system landscape (including the central adapter engine and non central adapter engines). This restriction is not enforced during runtime.
Deviating from this guideline can lead to a race condition state where different MDM receiver communication channels are monitoring the same MDM inbound
port, and only the first one receives the import acknowledgment of the message.
Non-XML Inbound Messaging
When the backend system uses the PI File Adapter sender as the communication channel to deliver messages to the PI server, and the receiving MDM channel
corresponds to an inbound MDM port of type other than XML (for example, Flat text file), then you must enable the File Adapter Specific Message Attribute
named File Name as follows:
1. Edit the corresponding File Adapter sender communication channel.
2. In the Advanced tab, choose Set Adapter Specific Message Attribute.
3. Choose the File Name.
4. Save and activate the changes.
1.4.2.2 Setting Up Outbound Messaging from MDM
Use
Data is syndicated by the MDM Syndication Server (MDSS). The MDM PI adapter is triggered and forwards each of the syndicated files as a single message
through the PI server to the receiving party.
Prerequisites
Make sure that the MDM Java API Connector deployed on the AS Java engine matches the version of the MDM server on which the repository is mounted.
Procedure
1. Open the PI Integration Directory tool.
2. Create a new communication channel and enter MDM as the Adapter Type.
3. Set as Sender.
4. Configure the following MDM access parameters (all MDM access parameter values can be found in the MDM Console tool):
MDM Server (host name or IP)
Note
If your MDM server uses a network port other than the default, you can append the port number after a colon or a semicolon, using the following
format <serverName>:<portNumber> For example, localhost:59950
Secure Connection
Select this checkbox to use a secure communication channel to the MDM server. In this case, the MDM server name must include the number of the
secured port.
Note
To use a secure connection, you must first import a certificate file (.crt) to the dedicated key store view named MDMKeystore on your
application server.
For more information about the certificate file, see the following sections in the MDM Java API and .NET API Guide:
Alternative Session Creation MethodEnabling Secure Connections
Managing Connections and Sessions
For more information about secure connections, see the Network and Communication Security section in the MDM Security Guide.
MDM Repository Name (as well as User and Password)
DBMS Server (host name or IP) and DBMS Type
Note
Important! These parameters must be entered as shown in the Repository Detail pane under the corresponding server node.
Port Code and Remote System Code of the outbound MDM port
Note
Important! These parameters must be entered as shown in the Ports and Remote Systems nodes under the Admin tree of the corresponding
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 11
repository node.
Caution
Make sure that there are no duplicated MDM sender communication channels. Check that there is no more than one MDM sender configured per
MDM outbound port in your system landscape (including the central adapter engine and non central adapter engines). This restriction is not
enforced during runtime.
Deviating from this guideline can lead to a race condition state where different MDM sender communication channels are monitoring the same
MDM outbound port, and only the first one receives the syndicated port data.
5. This is an optional step. The default setting for the Quality of Service (QoS) model is Exactly Once (EO). To change the model to Exactly-Once-In-Order
(EOIO), carry out the following steps:
1. Choose the Processing tab.
2. Choose EOIO as the Quality of Service.
3. Enter a Queue name. This value must be upper case with a length of 1-16 characters.
The Queue name defines the serialization context and all messages with the same queue name and with QoS defined as EOIO, are delivered in the
same sequence as they were received in the PI server.
1.5 Monitoring the MDM Adapter
The MDM PI Adapter supports the following monitoring possibilities:
Runtime Workbench
The Runtime Workbench is the central tool for accessing PI monitoring
For more information, see Integration Monitoring - Runtime Workbench.
Integration Engine Monitoring
Then SXMB_MONI transaction contains a monitor for processed XML messages.
For more information, see Monitoring XML Messages in SAP GUI.
PI Alert Mechanism
Enables improved reaction to process errors in the PI runtime environment. Alerts can be configured as to whether they are sent or not. If an alert is sent, it
can be used by the administrator for error analysis.
For additional information, see SAP Help Portal at http://help.sap.com/netweaver Process Integration Monitoring.
1.5.1 Integration Monitoring - Runtime Workbench
The PI Runtime Workbench provides the following tools for monitoring your integration landscape:
Component Monitoring (for example, Communication Channels Monitoring)
Message Monitoring
End-to-End Monitoring
For more information, see the SAP Help Portal at http://help.sap.com/netweaver PI Monitoring with SAP NetWeaver Administrator.
1.5.2 Monitoring XML Messages in SAP GUI
Message monitoring is used to display the processed message status using the SAP Easy Access transaction Integration Engine - Monitoring ( SXMB_MONI).
For more information, see SAP Help Portal at http://help.sap.com/netweaver Monitoring XML Messages.
The following tables explain different statuses for processed messages:
Statuses for Processed XML Messages
For more information, see Processing Status.
Statuses for Acknowledgment of Messages (inbound messages to MDM)
Icon Status Description
Message processed The message was processed by the sender channel and is
persistent in the integration server.
This does not necessarily imply successful message
delivery to the receiving party.
For further analysis, check the corresponding
communication channels involved in Integration
Monitoring - Runtime Workbench.
System error A system error occurred during message processing
Possible errors related to MDM are described in the section
Troubleshooting and Error Handling.
Icon Status Description
No errors in acknowledgment The message was successfully delivered and imported
into MDM.
Acknowledgment contains errors The message was successfully delivered to MDM but
further processing caused errors.
Note
The message cannot be restarted through monitoring.
Errors have to be checked and fixed using the
corresponding MDM tools.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 11
For more information, see Acknowledgment Messages.
Caution
In general, technical sender adapters are not able to request acknowledgments (except for industry speak adapters). Therefore, the acknowledgment is not
passed back to the sender system.
For example, a File Adapter does not support acknowledgment, therefore messages sent by the File Adapter would not have any Ack Status value in the
XML messages table (transaction SXMB_MONI).
1.5.3 PI Alert Mechanism
Alerts are used to notify users about critical situations (see examples below), so that immediate and timely action can be taken. Message-based alerting is
embedded within both the Runtime Workbench (RWB) and SAP NetWeaver Administrator (of) Process Integration (NWAPI), and is based on the Alert Framework
that is shipped by the SAP NetWeaver Application Server. By defining alerting rules, you can restrict the alerts that are triggered, depending on message header
properties or the component where the error occurs.
For more information, see How To Monitor Industry-Speak Scenarios, available on SAP Developer Network (SDN) at sdn.sap.com/irj/sdn/nw-mdm How-
to Guides SAP NetWeaver MDM7.1.
When a fatal error occurs during runtime of an MDM PI adapter channel, an alert containing an error message is generated and triggered in the PI server. If
alerting rules are defined in the PI Alert Mechanism, the administrator is immediately notified of the processing failure and is able to analyze the error and take
action.
The MDM PI adapter triggers alerts in the PI server for the following reasons:
A runtime configuration error of an MDM channel has occurred.
For a receiver channel, the corresponding inbound MDM port has an exception or is blocked.
For a sender channel, an error has occurred during processing of a syndication event of the corresponding outbound MDM port.
For more information on how to configure the PI Alert Mechanism, see the following links on the SAP Help Portal:
Alert Configuration
Configuring the CCMS Alert Monitor.
1.5.4 Logging and Tracing
Use
The MDM PI adapter uses standard logging of the SAP NetWeaver AS Java Engine to log the processing steps of XML messages. Tracing is used to analyze
these processing steps. Changing the default settings of the logging and tracing is optional and mainly used for troubleshooting.
Procedure
Log on to the corresponding administration tool on the AS Java engine where the adapter is deployed and where you can configure the logging and tracing details.
For more information, see the SAP Help Portal at http://help.sap.com/netweaver PI Process Integration Management Logging and Tracing. The direct link
is:Logging and Tracing.
1.6 Troubleshooting and Error Handling
The MDM PI Adapter uses various logging and tracing methods to display errors in the corresponding monitors.
You can view the errors and resolve the issues manually as required. In general resolvable errors related to the MDM adapter are caused by connectivity
problems between the MDM PI adapter and the MDM server.
Note
Before troubleshooting issues the MDM PI Adapter, make sure your process integration scenario is configured correctly using the Test Configuration tool
incorporated within the Integration Builder.
For more information, see the SAP Help Portal Testing the Configuration.
Possible errors are described in the section,
Troubleshooting and Error Handling.
Still waiting for acknowledgment No acknowledgment message has arrived from MDM. The
message may not have been imported into MDM.
It may also not have been delivered to MDM.
For further analysis, check the corresponding
communication channels involved in Integration
Monitoring - Runtime Workbench.
Failure Error Action to Resolve the Error
Connection to MDM failed Incorrect communication channel configuration Check the communication channel configuration on the PI
server and compare the given access parameters with the
MDM settings.
MDS is not running Check the MDM system landscape and start the MDM
server
MDM repository is not running Check the MDM server using the MDM Console. Load the
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 10 of 11
In all the above cases, the adapter allows restarting of affected messages.
Note
Only errors that occur during the import or syndication data process using the MDM tools (MDIS, MDSS) are monitored. These errors are resolved using the
corresponding MDM tool. The adapter prevents restarting of affected messages.
Related SAP Notes
For more information on troubleshooting issues, see the following notes:
1337471 Help for analysis of MDM PI Adapter messaging issues
1336552 Inbound messages are not reaching MDM Adapter receiver
1342846 How to trace received MDM events by PI Adapter
Note
Additional notes can be found at https://service.sap.com/notes
In the Application Area enter MDM-FN-PI as the component.
repository.
Incoming message delivery failed MDS is not running Check the MDM system landscape and start the MDM
server.
Not receiving MDM import acknowledgment in the process
log of the MDM receiver communication channel
Reasons for errors could be:
MDIS is not running or configured properly
Import port is blocked
Import map needs to be updated
For more information, see the MDM Import Manager
Reference Guide.
MDM communication channels are not able to connect
because a socket error or session related exception is
reported
MDM server has not been stopped correctly (process has
been killed or has crashed)
Make sure MDS, MDIS, and MDSS are not running.
In the AS Java engine that runs the Adapter Engine for the
relevant MDM communication channels, restart the
following applications:
MDM Java API Connector:
sap.com/com.sap.mdm.tech.connector
MDM PI Adapter:
sap.com/tc~mdm-adapter~svc
For more information, see the SAP Help Portal Starting
and Stopping Java Applications.
In AS Java 7.0, this can be done using the Visual
Administrator tool as follows: Server Services
Deploy Runtime Connector.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 11 of 11