AS2 Async mdn issue in seeburger monitor

Hi PI Experts,
My scenario is B2B Inbound Interface.
Partner(AS2)------->PI(7.31)--------->SAP.
MDN:Async
While Partner sending data from Third Party to PI getting below error in Seeburger Monitor.
Error : Could not send ansynchrone MDN to partner!
for Inbound interfaces from Partner side they did the MDN:Aync settings .But PI not able to receive the data from Partner ,getting the above error in seeburger monitor.
Could you please help me on this issue ,this is very urgent.
Thanks,
Aadi

Hi,
Have you had a look at these links?
Error in Seeburger Message Monitoring
AS2 Seeburger error troubleshooting
Regards,
Jannus Botha

Similar Messages

AS2 Adapter MDN option and Seeburger FTP adapter

Hi Experts,
I configured the a scenario AS2 to File, it takes all the signals from customer and placed in a particular folder, later by using some other scenario it goes to the seeburger workbench and process further.
Now I sent one outbound (810) signal to customer, then we will receive the MDN back, so we receive MDN also in the specific folder (by using the above AS2 to File configuration)? or we need to create separate CC and Sender Agreement by using the sender party?
One more Question about Seeburger FTP adapter
I configured the sender side FTP adapter to pick the functional acknowledgement (997), in the component monitoring it is displaying the below error
"Cannot create reservation, reason: Resource not available for reservation!; affected object : Resource (type:LOGICAL/id:ABCFTP/name:Logical resource name for abc to access the FTP mailbox)", I have deleted the old reservation in seeburger work bench resource management, still no luck.
Could you please guide me.
Thanks
Ramesh

Hi Experts,
I configured the a scenario AS2 to File, it takes all the signals from customer and placed in a particular folder, later by using some other scenario it goes to the seeburger workbench and process further.
Now I sent one outbound (810) signal to customer, then we will receive the MDN back, so we receive MDN also in the specific folder (by using the above AS2 to File configuration)? or we need to create separate CC and Sender Agreement by using the sender party?
One more Question about Seeburger FTP adapter
I configured the sender side FTP adapter to pick the functional acknowledgement (997), in the component monitoring it is displaying the below error
"Cannot create reservation, reason: Resource not available for reservation!; affected object : Resource (type:LOGICAL/id:ABCFTP/name:Logical resource name for abc to access the FTP mailbox)", I have deleted the old reservation in seeburger work bench resource management, still no luck.
Could you please guide me.
Thanks
Ramesh

Issues with Seeburger AS2 alerts

Hello All,
I am trying to setup an alert rule for any failures in the AS2 adapters.
I have created an alert rule in the RWB, with the adapter type as AS2.I have created the alert category as well.
When the AS2 message is unable to reach the destination system, the communication channel errors out with the description about the connection issue. But for some reasons, the alert rule is not called. I could see in the "SXMSALERT_LOGREADER" report that No active rule for this Adapter Framework exception. I have selected a * for all the filter criteria in the alert rule except for the adapter type (which is filtered as AS2).
Are my basis guys missing any alert enablement functionality while deploying the AS2?
Pls note that I am able to receive email alerts if the adapter type is selected as File or JMS instead of AS2.
Pls help me.
Edited by: Senthilnathan Natarajan on Oct 4, 2011 5:53 PM

I'm resending this since I did not have any luck with it the first time.
We also have an oss note waiting to be responded on this subject.
When I send messages using Seebuger FTP adapter, I see the following information in the SAP message monitor -
"Message entered module processor exit bean and will be transferred to JCA adapter".
But does not get to IBM VAN mailbox. How do I trace from this point onwards.
Should I use Seeburger monitoring tool for this? If so, I don't see anything in Seeburger monitoring (used all criteria).
Please let me know if you have any information on this subject.
Thanks,
Parimala

AS2 asnyc MDN not working

Hi,
I have setup my config in SeeBurger AS2 adapter in SAP PI 7.11 to send a file to our trading partner via AS2-HTTPS with async MDN requested. I got the an error in seeburger message monitoring : "Sent AS2 message successfully to partner - waiting now for asynchrone MDN"
We are still not able to received the async MDN from our partner. Wonder if anyone of here had encountered similar problem before? Please share your experience.
My config:
1. HTTPS-AS2
2. Signed Msg
3. Encrypted Msg
4. Request async MDN (Not signed) by provided our HTTPS AS2 URL in receipt delivery address, no MDN time out.
5. Create virtual sender aggrement for MDN report with accepting same message title with AS2 receiver aggrement message titile.
*Tested the same receiver agreement config with No MDN and Synchronous MDN. All successfully.
Thanks!
SP

Hi,
We are also facing the same problem. But I want to tell you few points which you need to make sure....
virtual party and communication component that you've used in Sender agreement of Reports channel shouldbe same as that of party & component used in Header mapping of actual receiver agreement. And, there should not be more than two sender agreements for MDN reports channel for same set of sender and receiver party.
One request from my side is... please let me know if your issue got resolved so that it'll be helpful for me too.
Regards
Priyanka

Error in AS2 RCV adapter.. SEEBURGER AS2: 307 Temporary Redirect #

Hi all,
Iam just doing File to File scenario and passing the resultant file to Partner system through AS2 adapter.
I gave the following details in AS2 RCV adapter..
SND>XI->Webdispatcher--->Partner.
My message will be reached to webdispatcher.. from there it will route to Partner Url.
So i will be giving my webdispatcher URL in my AS2 RCV adapter.
TP : HTTP
MP : AS2
Server : vvvvvv.com.NZ
Port : 50000
Url : /as2gs1/partnera
Message is processed succesfully but its failing in AS2 RCV adapter with following error.
Success      SEEBURGER/AS2: Received order from system.
Error      Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
Error      Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #.
Error      The message status set to NDLV.
Kindly let me know if anyone know th solution.
Regards
Seema.

Hi Peter,
>> a, what do you mean with the Web Dispatcher?
We are not using the partner URL directly.We will be using Webdispatcher URL .. from there they have written the rule to goto Partner URL.
>> b, you receive a HTTP code 307, which means that the target AS2 location has been moved. Try to connect the target AS2 server on the URL and check, if it is really there and if it is working.
Looks like this is working.. its showed success state for a while and after few minutes.. its showing the below error in communication channel monitoring.
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address #.
This is the error it is showing in Seeburger Monitoring.
State                          : Error on send, will be retried
Status Description : Could not deliver as2 message to partner: java.net.SocketException: Connection timed out:could be due to invalid address # null
What is this error?
Do u think there is no problem with AS2 adapter.. its the problem wit webdispatcher.??
Waiting for your reply.
-Seema.

Issues with Seeburger FTP adapter

Can one of you with Seeburger FTP adapter experience share some information on these issues I'm facing
1. Do I need to setup resource management in Seeburger workbench. If so, do I need to configure, resource, server and reservations. Do you have more information and what parameters I need here.
2. In the Seebuger FTP adapter, I have
Module Key - exit
Parameter Name - JNDIName
Paramter Valu - deployedAdapters/SeeXIFTP/shareable/SeeXIFTP
JNDIName, should I be replacing this with some other name. I'm trying to get Seeburger FTP to work and in the messaging monitor, I see the message as passed to Module Processor but it does go anywhere from there.
Can one you throw some light on this subject...what to expect from this definition.
Thank you for all your replies,
Parimala

I'm resending this since I did not have any luck with it the first time.
We also have an oss note waiting to be responded on this subject.
When I send messages using Seebuger FTP adapter, I see the following information in the SAP message monitor -
"Message entered module processor exit bean and will be transferred to JCA adapter".
But does not get to IBM VAN mailbox. How do I trace from this point onwards.
Should I use Seeburger monitoring tool for this? If so, I don't see anything in Seeburger monitoring (used all criteria).
Please let me know if you have any information on this subject.
Thanks,
Parimala

How to configure Integration B2B to request and process AS2 Sync MDN

Hi,
Is it possible to configure B2B to request and process sync MDN in Custom Document Over Internet scenario?
I have set up the TP Delivery Channel's Acknowledgement mode to Sync but It does not work for outgoing documents. Our trading partner sends back MDN over the same https connection but it only results in an error. The business message status of is Wait Ack for few minutes and then changes to Error:
Business Message Details
Collaboration
Revision
Business Action PROCESS
Revision 1
Process Protocol
Exchange Protocol AS2 - 1.1
B2B Message Id 1036
Protocol Message Id <1036@as2test>
Protocol Collaboration Id
Receive Time Stamp April 21, 2009 2:37:43 PM
Send Time Stamp April 21, 2009 2:37:43 PM
Acknowledge Mode Sync
Reply Mode Async
Agreement TP_TEST_AGR
Message Date Time April 21, 2009 2:37:43 PM
Error Code AIP-50079
Message Type
State Error
Remaining Retry 0
Acknowledge Type Document Exchange
Direction Outbound
Time To Acknowledge
Sending Trading Partner HOST_TEST
Wire Message View
Correlated Message
Payload Payload
Transport error: [IPT_HttpSendError] HTTP encounters send error :.
Premature EOF encountered
Also our trading partner reports that he gets the message six times during the time between Wait Ack and Error status and each time send Ack. Nothing is visible in b2b.log in that time.
When we switch to Async Ack, B2B also sends message six times and each time receives Async MDN. This time however, each MDN is received and processed correctly. Our request has status Complete, until the 6th Ack is received, then it changes to the same error as above.
Have any of you experienced above error? Is it at all possible to process AS2 MDN's correctly especially in Sync mode?
Thank you in advance.

Just consider your BPM is receiver, and sender:
Src --> BPM (BPM is Receiver)
==========
Sender Agreement (If it is IDOC or HTTP, then you do not have to create)
Commnunication Channel
Receiver Determination
Interface Determination
BPM --> Target (BPM is sender)
============
Receiver Determination
Interface Determination
Communication Channel
Receiver Agreement
If your BPM interact with other systems, you will have more Receiver Determination and Interface determination, possible Receiver agreement
Hope this clear your doubts
Liang

Enabling alerts for Seeburger Monitor

Hello,
I would like to know if there is any way to enable alerts for errors in Seeburger Monitor?
There is a checkbox "Enable alerts" in AS2 adapter communication channel,I tried to check it,but it doesn't seem to be working.
Currently,we have to manually monitor Seeburger Workbench by scrolling down the screen having 100s of messages which is not convenient.Can this be automated?
Please let me know.
Thanks.
Regards,
Shweta

According to this thread: How to generate Alerts for Seeburger Workbench failed messages (and also according to the reference given therein) it is not possible to raise alerts in Seeburger Monitor.
Regards,
Abhsihek.

MDN Issue in AS2 adapter.. Seeburger experts., Need help

Hi All,
Iam doing a scenario EDI-->Idoc for purchase order(ORDERS) by using AS2 adapter.
We are expected to send the technical acknowledgment once we receive the Orders from sender.
I think When we use the MDN (Message disposition notification), i will be getting the system generated acknowledge like below.
 <TransmissionReport>
<from>SAP</from>
<to>BIS</to>
<transmissionMsgID>43cc21a0-f752-11d8-c8ca-00c09f19e074</transmissionMsgID>
<sentAt>2004-08-26T132252+0200</sentAt>
<info/><adapterName>AS2</adapterName>
</TransmissionReport>
But my requirement is to send the ackowledgement with few more details like POnumber along with the standard details like below.
<TransmissionReport>
<from>SAP</from>
<to>BIS</to>
<transmissionMsgID>43cc21a0-f752-11d8-c8ca-00c09f19e074</transmissionMsgID>
<POnumber>6529833</POnumber>
<sentAt>2004-08-26T132252+0200</sentAt>
<info/><adapterName>AS2</adapterName>
</TransmissionReport>
1. Is there any option where i can modify the MDN acknowledgement file by adding few more fields??
2. If not please suggest me how i can proceed with this.
Note: We should not use by creating one more msgtype in SAP and send back the acknowledgement like Orders response(ORDRSP). They just want the file from XI itself.(But not from SAP Side).
Regards
Seema.
Edited by: Mike Pokraka on Jul 24, 2008 1:43 PM

Hi Reddy,
If ur problem is solved can u plz help me?
I have one question related to the MDN .
My scenario is like AS2 adapter is on the receiver side means its converting XML to EDI format. When the payload along with MDN is sent from the XI side EDI partner , the EDI partner sends back the MDN acknowledgment back to XI.
The problem is that XI is not able to accept the MDN acknowledgment.
Could you please suggest what all steps need to be configured to receive that MDN acknowledgment on XI side.
e.g 1)AS2 Communication channel with message protocol REPORTS
2)Sender agreement for accepting the acknowledgment
3) What type of message interface is to be used which is required in the configuration step for sender agreements(MDN specific format??)
4) Any other configuaration required ??
Please reply as soon as possible.
With regards,
Simran

Seeburger AS2 Adapter: "MDN not signed"

Dear all,
we just updated our test system from XI 3.0 to PI 7.1. Now we are facing a problem with our Seeburger AS2 Adapter.
I sent out a message via AS2 and get the follwing error message in Seeburger AS2 Monitor:
"MDN not signed"
In the Receiver Communication Channel I checked the Option "Sign MDN". In XI 3.0 this Scenario was working perfectly. So I contacted our communication partner and asked them if our AS2 message really contained a request for a signed MDN. Our commnucation partner confirmed and sent the MDN as text file to me. This text file shows that the MDN is signed. So it seems that the Seeburger AS2 adapter does not notice that the received MDN is a signed one. But why? Do you have an idea?
Just for testing purposes I unchecked the "Signe MDN" option. In this case the transmission finished successfully.
Who can help?
Thanks
Michael

Dear Vikrant,
many thanks for your reply. But I am not sure if we are really facing the same issue as you described it in your article.
Currently we have this situation:
When I send out a message the Seeburge Workbench provides only the following error message:
"MDN not signed"
Via the Recovery Monitor I can check the received MDN. Here I can see that the MDN is signed and positive.
In the Runtime Workbench I checked the following:
1. In the Message Monitor (Adapter engine) the message is in status "System Error". Here are the details:
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received..
2. The Communication Channel Monitor shows the following error messages:
Error type: REPORT_ERROR >> Error date: 12/14/10 12:02 PM >> Description: MDN not signed [12/14/10 12:02 PM]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
I do not understand why the MDN is recognized as negative and unsigned even if the plain text version of the MDN shows that it is signed and positive.
In your article you recommend to create a sender communication channel for MDN and a corresponding sender agreement. We already did that in XI 3.0 to forward the MDN as STATUS IDOC to SAP ECC.
Maybe you have an additional idea?
Thanks
Michaek

Information on AS2 Seeburger monitoring

Hi All,
Recently a Seeburger interface got introduced in our production,could any one please share their experience or documents for monitoring AS2 .
2)In As2 scenarios ,how to correlate the MDN number with XI Message Ids.
Regards,
Vidya

Hi look at this Thread
Re: Mapping and Monitoring in B2B(Seeburger adapters) scenarios
AS2 Seeburger error troubleshooting
Regards
Abhishek
Edited by: Abhishek Agrahari on Jun 1, 2009 7:02 AM

Seeburger AS2 - Negative MDN response.

Hi ,
I created a self-signed certificate (signing & encryption) in cyclone and uploaded it in XI. I passed some messages via cyclone to Seeburger AS2 adapter which is being configured in SAP XI.
The payload was delivered from cyclone end but the receipt (MDN) obtained was a negative response.
Error Message: Receipt response: Receiver reported that the signing certificate is not trusted
is it possible in XI (configuration) to make the certificate trusted?
Help needed!

Hi,
To avoid this error you need to follow the below steps.
1. Upload the Cyclone certificate in the Visual Admin. Path of the certificate is TRUSTED\XXX
2. If SAP XI is also encrypting messages with any certificate then you need to upload the same in Visual Admin in path TRUSTED\service_ssl\XXX
3. Provide the same path in Security Settings of the Sender/ Receiver Aggrement
Cheers!
Ram

AS2 seeburger monitor

Hi All,
I have a requirement to create alert in AS2 seeburger adpter.Once the message fail in Seeburger Workbench , need to send some alert mail to the appropriate recipient.
Could it be possible to monitor messages of seeburger in XI (SXMB_MONI or Runtimework bench) means what we monitor in Seeburger work bench, can we monitor same in Xi, in that case we can use XI alerts .
Please suggest some solution.
-Rahul

But its possible that few errors at workbench are visible as stucked messages in RWB. From there u may raise the alert.
Hi Prateek,
What r those few types of error visible in workbench....could you please throw some more light on that.
I am seeking for the solution for alert mechanism in seeburger...... so once the message failed in seeburger it report the error to the some specific recipient.
Does seeburger provide such facility???
Any other possible solution??
-Rahul

Seeburger Adapter: Party for AS2 - Synchronous MDN

Hello, I have to AS2 related questions:
1. We send a message via sender proxy which then has to be sent to an AS2 receiver. According to the documentation that I have a Party has to be created for applying AS2 IDs.
I have created a party for the external AS2 receiver, but should I also configure a Party for the internal SAP system, that sends the message via proxy? We already have a business system with communication channel configured for the proxy sender, so I am wondering whether I have to set up an additional party and use a business service for the SAP system? Any advice on that_
2. In between I also use an integration process, because apart from MDN we get two more AS2 messages used as acknowledgment that have to be correlated to the original message.
Now I am wondering how I can correlate a MDN in the integration process? I request the MDN synchronously however I doubt that I can use a synchronous interface as I have to set up a separate MDN sender even though the MDN is requested synchronously. Do you have any experience in dealing with such scenarios?
Thank you very much.
Regards,
Florian

Hi,
>>1. We send a message via sender proxy which then has to be sent to an AS2 receiver. According to the documentation that I have a Party has to be created for applying AS2 IDs.
I have created a party for the external AS2 receiver, but should I also configure a Party for the internal SAP system, that sends the message via proxy? We already have a business system with communication channel configured for the proxy sender, so I am wondering whether I have to set up an additional party and use a business service for the SAP system? Any advice on that_
No you don't need sender Party. But while creating the receiver Agreement overwrite the Sender Party with you company Identifier (so that receiver can identify teh source of the message)
>>In between I also use an integration process, because apart from MDN we get two more AS2 messages used as acknowledgment that have to be correlated to the original message.
Now I am wondering how I can correlate a MDN in the integration process? I request the MDN synchronously however I doubt that I can use a synchronous interface as I have to set up a separate MDN sender even though the MDN is requested synchronously. Do you have any experience in dealing with such scenarios?
Sorry never worked on this. But will MDN have any detail for you to correlate!!!!?
Regards
Suraj

IDoc to AS2 scenario connection issue

Hi Experts,
IDoc to AS2 scenario.
i am geeting below connection error while sending data from PI to Third Party Partner.Please help me on this issue i will appriciate you .
MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: java.net.SocketException: Connection reset # , SEEBURGER AS2: java.net.SocketException: Connection reset #
Thanks,
Aadi

Hi Srini,
Thanks for your reply.
after changing the timeout also i am getting same error
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: java.net.SocketException: Connection reset # , SEEBURGER AS2: java.net.SocketException: Connection reset # .
Please help me on this issue.

AS2 Async mdn issue in seeburger monitor

Similar Messages

Maybe you are looking for