Capturing Errors in Acknowledgements in MDM adapter - PI7.11

Hi Experts
I am working on a File to MDMadapter in PI 7.11 , I am sending a request to MDM adapter and receiving the acknowledgements back to PI, but in failed status. I have configure the Alerts to capture the erros in runtime work bench.
However whenever there is a failure on the Acknowledgements the alerts are not being sent. How can I capture the errors in Acknowledgements from MDM adapter.
Thanks
PR

Hi PR,
can you tell us what exactly do you mean by receiving acknowlegdements in error status?
Do you mean you there was an ackowledgement from MDM saying that the load was un-succesful?
Or do you mean there was an acknowledgement which went into failed status, because there was no configuration done in PI to handle that acknowledgement?
If you mean 2nd point, then you should have a scenario to handle the acknowledgements and then have the alerts configured the normal way.
Best Regards,
Ravi

Similar Messages

PI MDM Adapter Error - MDM port not found

We are working on an R/3 - PI - MDM scenario using the PI MDM Adapter. We are currently encountering the following errors.
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-08 15:31:22 Error Message could not be forwarded permantely to the JCA adapter. Reason: System error: MDM port not found
2009-09-08 15:31:22 Error Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found
2009-09-08 15:31:22 Error Adapter Framework caught exception: System error: MDM port not found
2009-09-08 15:31:22 Error Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found.
Is there an issue with our receiver communication channel and the MDM Access Parameters? We are using the Port code and Remote System code provided by the MDM team.
Anyone experience this same issue?

We are no longer seeing the MDM Port Not found error, but we are still seeing the UnknownServer error. Looking at RWB Message Monitoring it appears that the message is successfully sent to the MDM server, but nothing is coming into the Ready folder. Any ideas on where the message is going, and why it is not showing up in the Ready folder?
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-11 14:04:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http: //XXXXXXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-11 14:04:15 Information Using connection MDM_http ://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.
2009-09-11 14:04:15 Information Message successfully put into the queue.
2009-09-11 14:04:15 Information The message was successfully retrieved from the receive queue.
2009-09-11 14:04:15 Information The message status was set to DLNG.
2009-09-11 14:04:15 Information Delivering to channel: MDS_TEST_CC
2009-09-11 14:04:15 Information The message was successfully delivered to the application using connection MDM_http ://sap.com/xi/MDMAdapter.
2009-09-11 14:04:15 Information The message status was set to DLVD.
I thought the implementation of the MDM Adapter was suppose to be straightforward and simple
Edited by: Chris Williar on Sep 11, 2009 9:56 PM

Error with MDM Adapter.

Dear Experts,
We are working on PI MDM adapter. We are facing below error in PI Communication Channel...
" MDM Adapter listener could not start due to: Can not create repository
session '<server=XXXX serverUser=Admin
repository=XXXX user=Admin>' caused by: Path to object does
not exist at MDM Factory, the whole lookup name is deployedAdapters/MDM
Factory/shareable/MDM Factory. "
Any one please help us to resolve the issue.
Thanking you.
Hemanth.

Hey,
Please have a look at SAP Note 1468614.
You need to apply a patch to fix this issue.
Thanks
Aamir

Error with PI MDM Adapter

Dear Experts,
We are working on PI MDM adapter. We are facing below error in PI Communication Channel...
" MDM Adapter listener could not start due to: Can not create repository
session '<server=XXXX serverUser=Admin
repository=XXXX user=Admin>' caused by: Path to object does
not exist at MDM Factory, the whole lookup name is deployedAdapters/MDM
Factory/shareable/MDM Factory. "
Any one please help us to resolve the issue.
Thanking you.
Hemanth.

Hello Hemanth
Please do not cross post the same issue on several different forums. This is against the forums etiquette :).
error with MDM Adapter.
Regards
XI/PI Moderator

Acknowledgement from MDM to PI.

Hi All,
I am new to MDM. We have a requirement ECC->ABAP Proxy->PI->MDM Adapter->MDM. And Acknowledgement has to be sent to PI from MDM.
Using MDM 7.1 and PI 7.1 versions.
The interface is working fine but no acknowledgment is received at the PI.
In SXMB_MONI of PI: Staus is Success. (But no Ack Staus.)
RWB: Message Processing started.
Message Prcessing Completed Successfully.
My question is, do we need to do any configuratiions in MDM side or PI side to receive Acknowledgement from MDM?
Referred Links:
/people/ramesh.gulipalli2/blog/2009/11/16/sap-47-to-mdm-integration-using-pi71-part1
/people/ramesh.gulipalli2/blog/2009/11/27/sap-47-to-mdm-integration-using-pi71-part2
/people/orit.prince/blog/2009/02/03/how-to-schedule-mdm-inbound-processes-with-pi-ccbpm
Thanks in advance.
Prasanna.

Hi Prasanna,
First thing, I hope that you are using MDM PI Adapter rather than File Adapter. As MDM PI Adapter delivers the message to the MDM server by using the MDM Java API ports functionality. Then The MDM PI Adapter updates the message delivery status in PI Monitoring.
Second thing, Your MDIS (MDM Import Services should be running) because it imports the message independently (MDIS). Once completed, a processed import event is triggered. Then The MDM PI Adapter captures the processed import event and updates the PI Monitoring with the message import status.
Please have a look on Statuses(No error, contain errors etc) for Acknowledgment of Messages (inbound messages to MDM):
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/986fec0e0e0e27e10000000a421937/content.htm
Also refer, Inbound Message Flow to MDM
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/cee75a6dc1581ce10000000a42189c/content.htm
Complete MDM PI Adapter Guide:
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/956cd09521062de10000000a42189d/frameset.htm
Note: Your MDIS services should be running because only this triggers import event when data successfully imported into MDM. Then this event captures by MDM PI adapter which updates PI monitoring with message import status.
Regards,
Mandeep Saini

MDM Adapter supporting PI 7.0 released with MDM 7.1

Hi,
I have imported the MDM adapter which supports PI 7.0 and is released with MDM7.1 to facilitate Syndication/Import of data from/to MDM and configured the sender channel in PI for the same to fetch the file from the outbound port of MDM server.
I observe that when file is syndicated to outbound port and is ready for PI processing, the adapter do not instantly fetch the file from outbound port even for hours but when i make a dummy change in Communication channel and again activate the same then it fetches the file and processes it in PI but after that if any other file is syndicated in the outbound port i have to again manually make a dummy change and activate it in PI and so on.
I found one Sap Note 1452509 which is relevant to this but want to know if the settings mentioned in SAP note are to be made on MDM server or PI and if there is any other setting which i have to make in channel or in MDM so that file is processed instantly/near real time manner.
I am on PI7.0
Thanks,
Amit

Hey Amit,
If you are talking about "Restart the MDM ADAPTER java component" then it will be done on PI server. MDM system does not have any java component.
This is a common error which we also faced, it happens often right after the restart of MDM server.
I have seen cases where when MDM server was restarted, we had to come to PI and restart the MDM Adapter services to make Sender MDM Adapter pick files from Ready folder.
>>if there is any other setting which i have to make in channel or in MDM
No other settings are required
Thanks
Aamir
Edited by: Aamir Suhail on Feb 7, 2011 5:44 PM

MDM Adapter doubt

Hi
what are all the advantages of using MDM adpater in PI 7.1
1.Will MDM adapter accesses directly the repository (in console or data manager or syndicator)?
2.How MDM adapter can be compared with import manager or syndicator .
3. MDM adpater enables to load the data directly to any repository ?
4. how the integration of PI7.1 with MDM 7.1 takes place ?
am bit confused, can you pls explain ?
thanks
manian

Hi Manian,
Please go through this link; it will give you a good idea about the new features of MDM 7.1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d0b0e7-f144-2b10-17a2-982103c96ac0
Some key points on MDM-PI Adapter; this will definitely answer all your questions:
1. MDM 7.1 will offer new functionality to directly push/pull data into/from MDM using the MDM JAVA API.
2. The MDM PI Adapter will support SAP Netweaver PI 7.0 and 7.1
3. The MDM PI adapter is shipped as a separate file to be deployed on the PI adapter engine.
4. Message flow between PI and MDM can be monitored end to end (e.g. show if messages have been recieved and properly imported into MDM)
5. Error handling is improved because the Communication Channel in PI is pointing to one specific Repository Port.
6. Restarting of messages if a service is unavailable is possible.
7. Configuration/System landscape setup/Integration
       (a) MDM Adapter can be used instead of the File Adapter.
       (b) Configuration of FTP is no longer needed.
       (c) MDM Adapter is easy to implement and straight forward to monitor.
       (d) Higher reliability of data transfer.
8. Message Flow PI to MDM
       (a) Data sent from any connected system to PI is stored within PI's internal database.
       (b) XML message is forwarded to the defined communication channel (MDM PI Adapter).
       (c) MDM JCA Adapter itself invokes the MDM JAVA API sends the message to MDM using MDIS Port Functions.
       (d) Store the message in XMl format in XML format into the corresponding MDIS port folder so that MDIS can import the files independently.
       (e) "Finished import event" is thrown by MDIS and caught by the MDM JCA Adapter.
        (f) The import status is used to update the PI monitoring accordingly.
9. Message flow from MDM to PI
       (a) The Syndication event is triggered by MDSS as soon as the syndication is finished.
       (b) The data is available as XML file in the corresponding port folder.
       (c) The MDM JCA Adapter catches the syndication event and uses the MDSS Port functions to retrieve the data.
       (d) PI XMl message is created and sent to the PI AF for reciever determination and further message processing.
       (e) It is important to understand that only MDSS is able to throw the syndication event.
       (f) A manual syndication using the syndicator does not throw this event, meaning that the MDM 7.1 PI adapter is unable to pick the XMl message coming from manual syndication.
All these points should give you a very clear picture of all the abilities of MDM-PI Adapter.
Hope this will answer most of your questions.
Regards,
Varun

Receiver MDM adapter not working !!! Please suggest !!!

Hi Experts ,
mine is a idoc to MDM adapter scenerio. The idoc message is successfully passing the PI integration engine , but failing in the adapter engine ( MDM communication channel ) giving the following message.
Configuration error: Can not create repository session - server=xxxxxx.XX.XXXXXX.net serverUser=Admin repository=xxxxxxxx user=Admin]' caused by: The specified MDM repository was not found on the server (xxxxxx) Configured MDM access parameters for inbound port: [ MDM Server: xxxxx.xx.xxxxxx.net , Repository: xxxxxxxxxx , Port Code: CREMMDM0XIncrementalData , Remote System Code: ECC , DBMS Server: xxxxxx.xx.xxxxxx.net , DBMS Type: ORCL
I have tried connecting to the same MDM server using a receiver file adapter and it is working absolutely fine. But dont know why the mdm adapter is giving the following error. I have cross checked the adapter parameters with the MDM guy. They are OK.
I was wondering this was a version / service error, how can I chack the service pack of MDM Comm channel .
Please suggest . Urgent
Regards,
Arnab.
Edited by: Arnab Mondal on Jan 19, 2012 12:04 PM
Anything guys??
Any feed guys??
Edited by: Arnab Mondal on Jan 20, 2012 5:37 AM

Try a reset, which is similar to a computer restart and is done by pressing and holding the home button and the sleep/wake or on/off button simultaneously until you see the Apple logo and then release.

Reg: MDM adapter in PI 7.1

Dear All,
My scenario is IDOC PI(7.1) MDM(7.1) .
In moni it is showing successful and when checked in Runtime workbench for MDM adapter (receiver communication channel) it is showing error as,
"Message processing failed. Cause: java.lang.Exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean' "
Can anyone suggest me on this.
Regards,
Lavanya.B

Hi Rajesh,
Thanks for the reply.In the Receiver MDM Adapter, we have two things,
Processing sequence
Module Name type Module key
localejbs/ModuleProcessorExitBean Local Enterprise Bean 1 (default)
Module Configuration
Module key Parameter Name Parameter Value
Could you please explain me in detail what need to filled as this is the first time I am configuring the MDM Adapter.
Regards,
Lavanya

How to send the acknowledgement via mail adapter

Hi Experts,
I have a async scenario file to webservice here we are getting an acknowledgment from the webservice side.
My requirement is - to capture the acknowledgement (application ack) which is coming to PI and then send this acknowledgment to some user mail ID using the mail adapter.
here we are not using the proxies and the acknowlodgement is application ack (not transport ack) and we are avoiding the BPM.
Please help me in this regard.
Thanks
Sugata

Hi Stefan,
Thanks for quick reply.
can you please let me know if application ack can be handled by BPM or not? if it is possible thru BPM please provide me the guidelines for the same ( blog etc.).
I am here to capture the Application Acknowledgment that is coming into PI sxmb_moni from webservice
Thanks
Sugata

CcBPM, how to capture error message in the exception branch ?

Hi,
Can I capture error message in the exception branch ? how to do that ?
because i want to raise the alert including with the error message ?
Cheers
Fernand

Hello Fernand,
I hope at the end of this you may get some knowledge on Alerts.
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step XI:Alerts step-by-step. (fundamental Basic)
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i CCMS Monitoring for XI. (CCMS monitoring for XI is enough later
we configure to Adapter Engine).
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1 Configuring scenario specific E-mail alerts in XI-CCMS: Part-1
(This is Important)
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 Configuring scenario specific E-mail alerts in XI-CCMS: Part-2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3 Configuring scenario specific E-mail alerts in XI-CCMS: Part 3
/people/federico.babelis2/blog/2006/05/03/solution-manager-cen-and-alerting-configuration-guide-for-dummies Solution Manager CEN and Alerting configuration (Advanced)
Please reward points if it is useful...
Thanks,
Satya Kumar

Acknowledgement File receiver adapter

Hi KP's,
Is there a possibility to send an acknowledgement when the file adapter has processed the file succesfully or
is there a possibility to send an error message when the file adapter has failed to process the message (when he
is not able to post the file in the file folder).
TIA

Peter
I can tell you the logic in Java code.Offcourse you would be using a filereceiver to write your file, now call this Java code from a commandline batch file by passing in the file name to be written by the adapter.You can then write within your Java code, the specific logic say checking write folder for permissions or checking specifically to see if a Zero size file is being created.
In our scenario we had explicitly checked the values in the file and generated a flag response along with correlation value which was sent back as a HTTP response to simulate an application acknowledgement.This will effectively close the S-A bridge.

MDM Adapter 7.1

Hi ,
I am trying to pick data from the MDM server using the MDM Adapter configured in PI. I am getting the below error :
MDM Adapter listener could not start due to: Can not obtain ConnectionAccessor for MDM server caused by: Connection refused: connect
can some one please help me on the same.
Thanks
Amit K

Hi Amit,
chk if ur using the right port and whether its accessible from PI server ?
also chk the below threads, they address same kind of issue :-
PI MDM Adapter Error - MDM port not found
SAP PI 7.1 MDM Adapter
Regards,
Rohit

MDM Adapter: MDM Adapter listener could not start (MdmSecureSocketFactory)

Hi there,
We are running the following versions of the PI MDM adapter:
MDM_ADAPTER 710.700 SP7 (1000.710.700.7.0.20110411174317)
MDM_JAVA_API 710 SP5 (1000.710.0.5.111.20101227095400)
com.sap.mdm.tech.apireset 710 (710.20101227094734.0000)
com.sap.mdm.tech.connector 710 (710.20101227094734.0000)
com.sap.mdm.tech.mdm4j 710 (710.20101227094734.0000)
tc/mdm/adapter/svc 710.700 (8917411)
And the following versions on the MDM Server itself:
SHARED_COMP 7.1.05.104
MDS 7.1.05.104
MDIS 7.1.05.104
MDSS 7.1.05.106
MDLS 7.1.05.99
All the MDM adapters have the same error now:
MDM Adapter listener could not start due to:
com/sap/mdm/net/MdmSecureSocketFactory
Does anyone know what this error means?
Any help would be greatly appreciated
Lynton

Was just a version issue, the MDM java API and MDM adapter had different versions.....un-deploying and re-deploying solved the issue.
Lynton

Capture error response from http receiver

Hi All !
I am using an asynchronous scenario File (sender) -> XI -> HTTP (receiver).
Please, tell me, how can I capture error response from HTTP receiver and write it in a log-file?
You can see response here [http://pic.ipicture.ru/uploads/090728/1TcDsx3777.jpg]
Regards,
Andrey

Hi,
You can make use of onewayresponsebean in sender file adapter.
Regards
suraj

Capturing Errors in Acknowledgements in MDM adapter - PI7.11

Similar Messages

Maybe you are looking for