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.
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...
More info
