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

Similar Messages

AS2: Synchronous MDN request but no synchronous interface possible?

Hello,
in our AS2 scenario with the Seeburger Adapter we request the MDN synchronously and we also would like to use a synchronous interface for this.
But obvisouly this is not possible as you have to create a separate sender communication channel for reports and a sender agreement (where I have to use an outbound or abs interface).
Is there really no way to use a synchronous interface for that scenario as we need to get the response back synchronously for handling in integration server.
Thank you for your advice!

So basically my idea was to use a synchronous send step in the integration process and then call a proxy when we have received the MDN.
Even when you use sync MDN with report protocol, you can send message to Integration Engine and process further. You should be able to use this message in BPM also and then it could be sent to receiver proxy.
the SAP sender wants to be notified in case there was a transmission problem and this can only be handled automatically with a synchronous interface.
If you are already using BPM in your scenario, then use of sync scenario is no longer a limitation. You can try correlating the MDN with the AS2 request message.
Regards,
Prateek

MDN in Asyn Mode: Seeburger Adapter

Hi Experts,
I am working with seeburger adapter.
Can we use MDN in asynchronous mode? If so, how??
Thanks,
Sushama

Hello Sushama,
Yes,you can use MDN in async mode.
But when you select Asynchronous,it is mandatory to provide receipt delivery address
Please let us know if you need further details.
Thanks.
Regards,
Shweta

Error in Seeburger Adapter

Hi Experts,
We are sending a message to a Partner, and i can see the message processed succesfully in the SXMB_MONI and also in the Runtime Workbench, but when i see in the seeburger adapter monitoring for the MDN's i noticed that the message was in Error MIC not verified # MIC values not verified sha1-null. At first i thought the error was related to certificate, but when the message was retried after some time it was sucessfully processed and we got positive MDN's also. Could you please let me know when exactly the Error comes? and what can be done to solve this issue.
Many Thanks.
Edited by: Ravi Kumar Nakerikanti on Aug 13, 2008 4:51 AM

Hi,
You have used the AS2 Message type MDN (Message Disposition Notification).
An MDN may optionally be signed, in which case the recipient can authenticate the sender of the MDN and check its integrity. A valid, signed MDN together with a valid MIC reported by the MDN can be used by the sender of the payload message
But here this validation is failed ...and have raised the error like
"MIC not verified # MIC algorithms not verified [LOC: com.seeburger.as2.component.MDNHandler.parseMDN]"
refer
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_AS2_Spoke_Unit_for_Trading_Partner_Integration.pdf
Thanks
Swarup

Seeburger - async receiving MDN problem- no binding found for AS2

Hi guys!
We have configured AS2 receiver adapter but during receiveing Async MDN we get following error (sending of message is successful) :
Cannot receive async MDN: com.seeburger.as2.exception.AS2PluginException: Inbound communication from 90586 to 22266 not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No binding found for: AS2, http://seeburger.com/xi, Gloria, R3
Note: Gloria & R3 are names of XI identifiers (scheme: XIParty) and 22266 & 90586 are names from AS2ID scheme - alternative identifiers.
22266 - is sender of original message
90586 - is receiver
What is wrong on the settings? Why the sending message uses alternative identifiers and incoming MDN does not?
Thanx for answers & suggestions!
Peter

Hi Peter
checkm this thread discuss the same ..... hope it will solve ur all querry
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
Thanks !!!
Questions are welcome here!!
<b>Also mark helpful answers by rewarding points</b>
Thanks,
Abhishek Agrahari

Sender AS2 adapter settings for Asynchronous MDN

Hello,
I need to configure the settings for AS2 sender adapter for Asynchronous MDN.
In order to configure the asynchrounous MDN Settings which parametrs i need to fill in the channel from below
1) Use Proxy
2) Proxy Server
3) Proxy Port
4) Proxy User
5) Proxy Password
6) Proxy Realm
7) Proxy Protocol
8) Server Certificate (Keystore)
9) Private Key for Client Authentication
Thanks
Srinivas

Hi,
The MDN asynchronous mode is for the AS2 receiver adapter and not sender.
If you want to use a proxy server, then only you would need to provide the details that you have mentioned and if you are using encryption, you would need to provide the encryption certificate in the corresponding receiver agreement where the comm channel is used.
Also, for asynchronous MDN, you would need to configure a report channel (AS2 sender adapter with message protocol reports) and sender agreement. You need this even if Refer to XI system option is disabled in the AS2 receiver adapter.
Regards

Seeburger Adapter Payload & XML Structure for AS2

Does anyone have a sample AS2 message with payload that I can use to test the Seeburger AS2 adapter for a customer in the UK?
Thanks in advance

Hi Frederic
we will be receiving Tradacoms over AS2. I understand that the Seeburger adatper uses the modules from BIC to convert to XI-SOAP ( XML ), but we need to have the schema created for us to construct the data types or to import external definitions into IR. I would like an actual AS2 message without header and signature if possible or a schema version of the tradacoms messsage format for EPOS data. Or if applicable the mapping program that the BIC module will call from the Seeburger adapter. I have the config guide for the BIC, so I know where to configure, but I need the mappping program which will create the XML prior to sending to XI.
Thanks.
I can send you a sample EDI message ( which will be the attachment ) if you give me your email address.
Cheers,
Mark

Sender / Receiver ID mapping for EDI interfaces and Type of seeburger adapt

We need to set up a interface using Seeburger adapter for Purchase order IDOC to 850 EDI mapping.. After reading from SDN,
1) We can use the standard mapping in BIC MD to do E2X and X2E mapping..
2) We can use any of the AS2, EDI generic adapter, Seeburger FTP adapter or Seeburger SFTP adapter...
How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security...
Also how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID
Also the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping.

Hi Kris,
I had worked in the somehow same scenario, It was IDOC to EDIFACT file.
I can give you few clues which might be helpful
In BIC MD you have to create your own mapping if the standard mapping is not available (First check all the standard mappings in BIC). For your reference you need X2E mapping, as your scenario is IDOC to 850 EDI.
"the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping."
In graphical mapping i created my own mapping, Seeburger has given some sample mappings you can check those for your reference (SEEBURGER_GENERIC_EDI software component). Mostly you have to create your own. You need a document from your functional consultant so that you are able to map correct fields and constants.
"how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID"
This has been generally hardcoded in message mapping (In my case i hardcoded). If any of ur IDOC field contains that data you can map that field. But better Idea is ask your functional expert.
"How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security... "
You can choose adapter according to your requirement. In my case i used File adapter as i have to create file in PI server only. My suggestion you can use SFTP for seeburger
Hope these points are helpfu for u
Regards,
Shradha

Forum for SEEBURGER Adapter

Hi ALL,
I have been posting quiet a few questions on SDN regarding SEEBURGER Adapter, But I don't seem to be getting much help in SDN. I understand there is not much information avaiable on net about SEEBURGER Adapter. Is anyone aware of any forum dedicated for SEEBURGER Adapter?
Regards,
XIer

Hi Xler
<b>pls go through these links for more information on SEEBURGER Adapter</b>
http://www.seeburger.com/fileadmin/com/pdf/SAP_Exchange_Infrastructure_Integratio_Strategy.pdf
Need Material on Seeburger Adapters.
Seeburger Adapter
Installing seeburger adapter
http://www.seeburger.com/xi-adapters/
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Please see this threads for some more information on this:
Seeburger AS2 Adapter
Seeburger
have a look also on these URl's
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
Thanks
Pls reward if useful

Integration of Seeburger Adapter in Solution Manager for Monitoring

Hi Experts ,
Can we Integrate the monitoring of Seeburger adapter into the Solution Manager dashboard under central PI Monitoring ?
We are using AS2, FTP and sSFTP seeburger adapters here.
Regards,
Kamal
Edited by: KAMAL KUMAR on Jan 11, 2012 2:33 PM

Hi,
check [this.|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/408e1501-fb8c-2e10-edba-f51f13cde64e?QuickLink=index&overridelayout=true]
Page 29 has useful information on adapter/channel monitoring.
-santosh.

SFTP Seeburger adapter - Could not find channel for report handling between

Hello Friends ,
We have R3 -> PI-> SFTP scenario . The messages are transferred successfully and the file is successfully received at the receiving end . But when we do communication channel monitoring , we see errors in Receiver CC . The Reciever CC contains SFTP adapter (Seeburger) . Recently the Seeburger adapter is upgraded and the below error has started occuring then onwards .
Error Message which we see in CC monitoring for Receiver CC (SFTP) is as below .
Initiation of Transmission Report( job id: da405030-30c6-11df-8b6e-797b8921162c milestone: 290) failed! Exception occured: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) - com.seeburger.xi.connector.fw.ConfigurationException: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) [3/16/10 8:40 AM]
Could experts help me ...
Thanks for your time .
Regards,
Laxman Nayak .

Hi,
I also have the error you mentioned but we're implementing the Seeburger SFTP adapter for the first time.
I've requested transport acknowledgements in my ABAP proxy and have checked the 'Deliver transmission report' flag in the adapter but I don't know what else I must do.
Any help would be greatly appreciated.
Thanks,
Alan

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

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

Seeburger adapter monitoring

We are running Seeburger AS2 adapter with XI3.0.
All inbound messages that the adapter can handle are passed to XI and we have access to those from XI message monitoring.
From there we have alerting setup.
Whenever an external party presents a message with a bad certificate the AS2 adapter refuses the message.
We can see trace of that in the adapter monitor. But there is no message in error passed to XI. So nothing we could get in message monitoring.
We saw we have a logfile containing those errors on the server. We could setup a logfile monitor on this file and get errors in CCMS. And from there, we could trigger alerts. But that does not look very elegant.
Is there a best way to get Seeburger adapter error generating alerts ?

Hi,
If the check is happening in the Adapter then the Alerts needs to be raised by Adapter framework.
So you have to set up Alert rule for the Adapter framework.
The message goes to message montioring only if the adapter sends the date to the Adapter engine and then you can see the message in the message monitoring.
If the rejection is at AF levelt hen you need to check in the Communication Channel if you are getting the Error?
Regards
Vijaya

Seeburger Adapter details

Hi All
What are the things that are to be kept in mind for choosing the Seeburger adapters.
For a logistics based EDIs we are planning to go for Seeburger adapters in XI, i need to know the following things that will help me to contact the seeburger guys for pricing.
1. what are the seeburger components we need to develop the interfaces,(The softwares comes with what all adapters)
2. Does any trial version is available for download?
3. What are the things that will differ from a normal interface development when we use the Seeburger adapters(any1)
steps in IR and ID.
is there any Document from SAP which gives overall picutres the things to be taken care when taking seebuger in XI?
regards
Nisar Khan

Hi Nisar,
1. what are the seeburger components we need
to develop the interfaces,(The softwares comes
with what all adapters)
2. Does any trial version is available for
download?
No trial version available.
3. What are the things that will differ from a
normal interface development when we use the
Seeburger adapters(any1)
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
4) from the followingt types of adapters:
1)BIC Adapter:
There is no BIC adapter it is the client based tool provided by seeburger which has the standard mapping program which does the conversion of EDI-XML and XML-EDI it supports many data types like INHOUSE,CSV, TRADACOM etc. So the std mappinf provided by seeburger has to be deploye first on XI and then used in adapter module tab for conversion.
Using BIC we can create our own data strucutre like we do in IR,we can create our own data type mapping program.
There are three mapping program which is provided by seeburger which is used for creating our own mapping program.
1) Create XML message
2) CreateMappingXML to EDI
3) CreateMappingEDI to XML.
You need to use this mapping program and create your own mapping program for your own structure once it is created import it in BIC.
2)Split997 adapter
The SEEBURGER message splitter module initiates new XI messages as children of a main (or parent) XI Message. A new child (or split) message will be created for each main messages attachment in the split list.
Example of when to use splitter:
1) mail adapter initiates a XI message which contains several attachments, you can use the message splitter to create a new XI Message for each attachment in the original email.
2) U have many UNH messages in one EDI file and u want to create different IDOC for every UNH message for that file that time splitter can be sued.
3)AS2 adapter.
I have provided u the details.
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
I hope I have given u better picture.
Thnx
Chirag

Seeburger Adapter: Party for AS2 - Synchronous MDN

Similar Messages

Maybe you are looking for