Skip to Content
author's profile photo
Former Member

MDM Sender Adapter issue in SAP PI7.1

Hi All,

How to schedule(there is no poll interval in Sender communication channel) MDM PI sender Adapter.

Everytime we need to start and stop the channel then only file is being picked up.

I checked port details, file is not picking up automatically

Please suggest me.

Reagrds,

Hemanth

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    author's profile photo
    Former Member
    Posted on Mar 17, 2010 at 01:14 PM

    Hi Hemanth,

    There are different versions of the MDM PI Adapter which correspond to the relevant PI version: one for PI 7.0 and the other for PI 7.1; the two are not interchangeable. Ensure that you have downloaded the correct version for your landscape i.e. PI 7.1

    Setting Up Outbound Messaging from MDM:

    Make sure that the MDM Java API (Connector) deployed on the J2EE engine matches the version of the MDM server on which the repository is mounted.

    Also, Check that there is no more than one MDM sender configured per MDM outbound port in your system landscape

    For more details, refer this below link

    http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854c94d3217cee10000000a421937/content.htm

    Also, refer SAP Note 1337471 - Help for analysis of MDM PI Adapter messaging issues

    https://websmp130.sap-ag.de/sap/support/notes/1337471

    Thanks and Regards,

    Mandeep Saini

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Hemanth,

      Message Flow from MDM to PI:

      MDM JCA Adapter catches the syndication event and uses the MDM Port functions to retrieve the data.

      It is important to understand that only MDSS is able to throw the syndication event.

      A manual syndication using the Syndicator does not throw this event, I mean that MDM 7.1 PI Adapter is unable to pick the XML message coming from the manual syndication.

      So here i assume that every file picked from MDM port is syndicated using MDSS only in your case. If it is not there i mean manual syndication too then PI will not pick this file. So for automated operation Syndication services should be always running.

      lly for PI to MDM, Event is thown by MDIS and caught by MDM JCA Adapter.

      Also, Check you need to deploy the JAVA API for MDM Adapter. The MDM-Adapter is not started until you deploy the JAVA API. You can check the status of the Adapter in the NWA -> Start & Stop Application -> Search for "MDM".

      Make sure that the MDM Java API (Connector) deployed on the J2EE engine matches the version of the MDM server on which the repository is mounted.

      Hope it helps...

      Thanks and Regards,

      Mandeep Saini

  • Posted on Mar 17, 2010 at 10:00 PM

    Hi,

    In addition to what Mandeep said, please also try this:

    1. Stop MDS, MDIS, and MDSS and then restart MDM JAVA Connector (sap.com/com.sap.mdm.tech.connector) and MDM PI Adapter Applications (sap.com/tcmdm-adaptersvc)

    2. Check the Trace to make sure that MDM Adapter has received Syndication Event. (Check SAP Note # 1342846 for details)

    Also let us know how you are creating file on Port i.e. using Syndicator or Syndication server? I think Java API and MDM connector should be deployed first and then MDM PI Adapter.

    Regards,

    Shiv

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 08, 2011 at 02:23 PM

    Hi Hemanth,

    I am having the same issue currently, could you please help me with the solution.

    Thanks in advance.

    Edited by: Sudheer on Mar 8, 2011 7:53 PM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      >> it possible for MDM Adapter to pick the files in deferent intervals

      Let Sender MDM Adapter pick the file as soon as it is syndicated, you just need to change the QoS in MDM Channel to EOIO and assign a queue ID, so that they both use same queue, this will maintain sequencing.

      In order to add a delay of 20-30 mins, you can easily do that in PI Message mapping, there is a Java function sleep(), which you can use.

      Thanks

      Aamir