AS2 adapter Outbound Message

Hi,
We have recently configured AS2 adapter for a party and started to test. We tried to send an outbound message to the party and found the following status in our seeburger monitor
It says "Initiaion to Backend Pending" with yellow state. Further the status description shows "AS2 Message created. Will try to send it now to partner and wait then for synchrone MDN.".
What should we do now? Is it the job of the receiving party to accept the message or do some thing at their side.
Regards
Krish

Hello all,
Note 1287778 solved the problem. Thanks for the reply.
Kind regards, Wilbert
Edited by: Wilbert Jeuken on Feb 24, 2010 9:43 AM

Similar Messages

Receiver AS2 Adapter : Empty Message Handling

Hello Experts ,
We are trying to work on following requirement .
File -> PI -> AS2 ( File) ( We are using Pranke to drop our message to the receiver system) (MDN ack too is in place )
There are times when none of the source records are valid and we have an empty payload post mapping.
In AS2 adapter we are using StrictXML2Plain.
Scenario works fine for all target messages which have data and a file is created at the receiver end. MDN ACK works fine too.
Problem is when we have empty target payloads , We get following error in communication Channel monitoring.
Information
SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted
Information
MP: processing local module localejbs/ModuleProcessorExitBean
Information
Message entered AF MP exit bean and will be passed to the JCA adapter now.
Information
SEEBURGER/AS2: Received order from system.
Error
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Error
MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Error
Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Has anyone handled such situation ? Is there any workaround at the SAP end to handle this issue ?
Or is this to be handled at the Pranke end ?
Attaching the Seeburger AS2 monitor error as well for empty messages ,
State
Error on send, will be retried
Status Description
Could not deliver as2 message to partner: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # null
Little urgent and your expertise is appreciated PI geeks
Sayalee

Hi,
here is the my requirment one source -> two target interfacess (0..1)
If u have 2 target interfaces,then this is not suffice..... u should make it as 0..unbounded both in operation mapping and message mapping.
But based on ur requirements posted above i guess u have only one inbound interface at a time based on some conditions....
But,
<messages>
<messages1>
based on condition first message type not created in mapping.
<messgaes2>
The error u r getting is because.... u want only one interface in target at a time....
Then u should not generate Message1 also in the target.
So avoid mapping to message1 if u want only message2.
If both message1 and message2 are created in target means... it is triggering for two interfaces.... so avoid one message1 or message2... based on some conditions u have..
Still nt solved do post...
Babu

Seeburger AS2 Adapter sending message error

I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor). I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ...
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Regards,
Jason

Hello ,
same issue occurred in my system
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Please advise asap.

AS2 Adapter in error

Hello,
I have got an error in AS2 adapter.
Error message is as shown below :
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated. # , SEEBURGER AS2: org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated. #
we are struggling for this error for quite few days.
Can anyone help me out what we can check in this ?? what could be a possible cause for same??
Thanks a lot in adavance !!!
Regards,
Vikrant

Hi Vikrant
Just have alook at this thread may get some clue ..
Seeburger AS2 Adapter sending message error
Re: Error in AS2 RCV adapter.. SEEBURGER AS2: 307 Temporary Redirect #
Regrds
Abhishek

Message subject in seeburger sender AS2 adapter

Hi Experts,
I read few fourms regarding message subject in seeburger and in those below forum is related to my problem
AS2 Sender adapter.. How we can receive 2 messages from same partner??
like how we can identify different message types when we receive from partner
A) using AS2 ID and message subject
If we give message subject as * it will receive all the message but how to identify them as our partner is not providing message
subject.
I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter

Hi,
> Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter
When message comes to PI, initially it goes to seeburger workbench, here based on the EDI type (ANSI X12 or EDIFACT or...), EDI Version (4010 or 4020 or...) and Signal (850 or 810 or ....) it determines the respective mapping (E2X or X2E) program, this is done by Classifier.
When we are sending outbound scenarios and using MDN option then message subject plays an important role. Once we send the outbound signal we can get the ack(997) signal, based on AS2ID and message subject it identifies the respective 997 inbouns scenario.
> I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Seeburger is used if you are handling the EDI data but here you are using XCBL so you no need to use the seeburger adapters.
Regards,
Venkata Ramesh

Seeburger inbound/outbound mapping options with AS2 adapter

Hi Gurus,
This is the first time that i am handling Seeburger adapters(AS2 adapter).
We have the following issue.
We are using AS2 adapter from Seeburger for communicating with Partners (inbound/outbound).
For some scenarios, the trading partners either sends us a flat/csv file or expects a flat/csv file from PI.
And for these scenarios, we are using the AS2 adapter (for sender or receiver channel configuration) .
Now, the main issue is that we need to convert the flat file to PI-XML format when we receive a flat file from a trading partner or we need to convert from PI-XML format to flat file format when we are sending file to a trading partner.
Since the AS2 adapter does not have a File Content Conversion (Like we have in the File/FTP adapter) mechanism, we need to rely on MessageTransformBean (under AF Modules) to do the conversion for us. However, since this module cannot handle deep structures (nested structures) what other alternatives can we look out for ?
I know we can also go for BIC Mapper which is shipped from Seeburger for EDI to XML and XML to EDI conversions. However in this project, we just need XML to flat file/CSV or Flat File/CSV to XML conversions and hence we want to abstain from buying a license for BIC mapper.
Please let me know what other options can we try in this case.
Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
Regards, Gaurav.

Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
No. Seeburger doesn't provide any such tool/option.
Please let me know what other options can we try in this case.
As per the detail you have provided, you don't have any standard option left. You have to either develop your own adapter module or you can pass the payload directly to mapping and then perform Java mapping on it. You have option of using Conversion Agent but there must be some license cost for it as well.
Regards,
Prateek

AS2 Adapter Error: Error while parsing AS2 message: AUTHENTICATION_ERROR #

Hi,
Following Scenario: Inbound.
i have been receiving messages via Seeburger AS2 Adapter with the following Error message
Error while parsing AS2 message: AUTHENTICATION_ERROR #
I have done the following in the AS2 adapter as per findings in the forum
1. Unchecked the Authentication Required Flag.
2. AS2 Certificates are fine.
3. Use Authentication: Disabled (there is no authentication)
even though every thing seems to be fine i am not able to receive messages successfully. Please let me know what could have gone wrong here.

Hi Venkatesh,
>> Everything is provided in the Sender Agreement. Partners Certificate, Self Encryption & Signing certificate
How come you are using encryption when you are receiving the message. I think it might be decryption.
1. Anyway please cross check whether you provide the following correct details in Sender agreement.
Sender Configuration
Authentication Certificate : Partner's public certificate.
AS2 Receiver Configuration
Decryption Key : Own private key.
Signing Key : Own private key.
2. Can you please check and tell in the Seeburger Monitoring for the incoming message, whether they are sending the message with encryption and signing? This you can check in the Seeburger Monitoring.

Standard Adapter Module "Message Transform Bean" in Seeburger AS2 Adapter

Hi,
    I am calling standard adapter module "Message Transform Bean" in seeburger AS2 Sender adapter where I am getting the following error :
ClassNotFoundException:com.sap.aii.messaging.adapter.Conversion . Can anybody help me on this. Appreciate for your respoinse.
Thank you,
Mallikarjuna Rao M

Hi,
Thank you for your replies I manage to get NWA dump for this issue.. Here is the log
Could not call backend system: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
[LOC: com.seeburger.as2.impl.SHCInitiatorProcessor.initiateToBackend] Caused by: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:55)
at com.seeburger.xi.connector.fw.InitiationThread.run(InitiationThread.java:101)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:259)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:353)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sap.aii.af.modules.trans.MessageTransformBean.loadClass(MessageTransformBean.java:121)
at com.sap.aii.af.modules.trans.MessageTransformBean.setup(MessageTransformBean.java:178)
at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:346)
at sun.reflect.GeneratedMethodAccessor484_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy2674_10002.process(Unknown Source)
at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:249)
at sun.reflect.GeneratedMethodAccessor311_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy102_10002.process(Unknown Source)
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:43)
Waiting for your valuable inputs on this.
Thank you,
Mallikarjuna Rao M

Seebuger AS2 adapter for XI as sender for multiple messages

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent. What is the name of the module? Is it specified in your sender AS2 adapter with parameters? Is it wrapped as an adapter? How do you configure the module to split and pass specific messages etc... Any help on this would be much appreciated.
Thx,
Pete

Hi Rudy,
the Classifier/BIC/Splitter - Solution is mainly designed for EDI-Messages that cannot be handled directly by XI.
IF you use pure XML-messages you should be able to handle it with XI-basic-functionality since this is what XI can handle itself.
Depending on how different your XML-Messages are, the effort will be very small or a little bit bigger.
In the ReceiverDetermination it should be possible for you to check whether certain XML-TAGs are existing or what the content for certain TAGs is BAsed on this information you can route the messages in a correct way.
(Of course you might have to create your own XSD for this containing the important TAGs of each message, so you can setup your Conditions)
Btw. the Seeburger BIC-Adapter can provide also this functionality, but this also needs to be customized)
Greetings
Stefan

Seeburger AS2 Adapter: Receiving multiple messages

Hi guys,
I'm having some trouble using AS2 Adapter for receiving multiple messages. The problem is really similar to Peter's problem.
Seebuger AS2 adapter for XI as sender for multiple messages
I have it configured for one scenario and it's working fine. The problem is when I'm trying to receive other messages for the same Party but different services. Meaning, I've one Party(example BMW) and several services (BMW_DE, BMW_USA, etc). I'm able to receive messages from service BMW_DE but when configuring BMW_USA I'm getting HTTP 403 Forbidden.
This error may have different reasons:
a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
b) A valid sender agreement is missing.
c) There are more then one AS2 sender agreements with the same sender AND receiver party.
d) The corresponding inbound channel is set to inactive.
And the problem is that there are two sender agreements. Although the services are different, XI is not able to find the correct sender agreement to be used. After deleting the second second agreement, I'm able to send the respective message....
Can anyone give me a hint on how to solve this problem?

Hi,
this is done by different AS2 subjects. The sender agreement is selected based on this. So create separate AS2 receiver adapters for every message you need and put there different message subjects.
So if you'll have 3 AS2 receiver channels with subjects:
MessageType1_DE
MessageType1_US
the AS2 adapter will work like following:
first it tries to find an exact message subject, if it is found, message is "assigned" to this sender agreement. If no exact message matches the subject, then wildcards are used. (this mechanism is described in the Seeburger AS2 guide).
If you are getting 403 HTTP code, there may be also problem with authentication certificates.
Another problem may be, you don't have configured AS2 receiver channel for current subject.
Does this help you? Or you meant it another way?
Peter
p.s. check the answer above my post, Vardharajan's right
Edited by: Peter Jarunek on May 19, 2008 2:11 PM

AS2 Adapter.. How i can receive the MDN messages?

Hi All,
Doing IDOC to EDI scenario.
Iam using AS2 adapter to send the messages to partner system and i need to receive the MDN from partner system.
1. what are configuration settings i need to provide in AS2 receiver adapter?
2. I need to put option as Refer MDN to XI system..?
3. Is it necessary to create one more Sender channel and sender agreement to recevie the MDN?
4. Why we have the option as Asynchronous MDN settings in AS2 sender adapter ?.
Kindly let me know if anyone knows the answers.
Thanks & Regards
Seema.

Thanks Anoop for the answer.
So if i want to do the scenario for Idoc to EDI.
then the steps will be..
1.
- AS2 rcv adapter -- to send the message to partner.
- all remaining steps like sx agreement,rx agreement,interface deter,Rx determination to send the actual msg.
2.
- Again one AS2 sender channel to receive the MDN from partner for the same scenario
- one sender agreement for MDN.
TO receive the MDN.. no need of rx agreement,interface determination,rx agrrement??
If we want to see the MDN.. how we can see it?
3.I have a scenario where, once i receive my MDN message and with the help of Data in MDN message , i need to update my custom table in SAP by inbound processing.Is it possible??
Please help me.
Regards
Seema.

Dynamically selection of Message Subject in AS2 adapter. Urgent Help..!!

Hi All,
I need to send the message to partner by using AS2 adapter.
And i need to keep the Message Subject by taking dynamically from the payload message.
ie. Iam sending the Purchase Order to Partner and i need to pass OrderNO which is coming in one field of my strcture to the message subject.
How i can select dynamically the Orderno and pass into message subject of AS2 Receiver adapter??
In the Seeburger AS2adpter manual, they provide the answer by using module parameters like
http://seeburger.com/xi/common/dtsubject   DYNSUBJECT
But i don't know how to put particular field into it.
Any idea abt this?
Regards
Deepthi.

Hi Deepthi,
I think this would help you in configuring Dynamically selection of Message Subject.
Supported dynamic attributes are:
dtSubject if the subject parameter is set in the XI message and the AS2 receiver channel is
      configured to use all non-empty or subject attribute, it will be treated as the message subject
      by the AS2 adapter;
dtAS2FileName the name of the payload. This is an attribute of the Content-Disposition
      header. With this AS2 is compatible with AS2 Filename Preservation draft.
dtAS2ContentType for Example application/xml, depending on the payload type
To enable the usage of Dynamic Attributes, there is a special dedicated section in receiver channel.
Dynamic attributes are used if the Use dynamic attributes setting is checked in the receiver channel.
If the the setting Use non-empty attributes is not selected, all known attributes are used for
configuration if the attribute is present.
Mention Check boxes for these
          Use dynamic Attributes
          Subject
Dynamically set attributes override static channel attributes. Example: the subject attrib
in receiver channels overrides the channel attribute.
Here is an example how to set them. Channel tab Module->Module Configuration:
Module Key: 1
Parameter Name: http://seeburger.com/xi/common/dtsubject
Parameter Value: DYNSUBJECT
Message Subject: This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message.
Wildcards are allowed.
Regards,
Varun Reddy.K

AS2 Adapter

Hi Experts,
I have got a special requirement, can you please suggest is this requirement is possible or not in SAP PI using seeburger AS2 adapter. We have a got probelm in Our GIS System in setting up AS2 profiles for one of our customer. So we thought of using Seeburger AS2 adapter for this requirement.
By using the Seeburger AS2 adapter I have to receive and Post EDI messages. I have to decrypt the Inbound message and need to stage on the PI Server, No need of message mapping and posting to receiver system. We have a process in GIS system to pick the file from PI Server and do the mapping and post the output data to ORD System.
For the outbound transactions like 855 and 856, GIS will generates the EDI 855 and 856 files on PI Server. Seeburger AS2 adapter need to encrypt this messages and send to partner's AS2 server.
Is the above requirement is feasilble in SAP PI using AS2 adapter?
Any other ideas on this is greatly appreciated
Thanks,
Kishore

I have to decrypt the Inbound message and need to stage on the PI Server, No need of message mapping and posting to receiver system.
For inbound cases, you may use PI as the receiver system and use NFS protocol of File adapter to put the file on PI server. If you use decryption certificate at sender, you may perform the decryption very well.
Seeburger AS2 adapter need to encrypt this messages and send to partner's AS2 server.
This can again be done by the encryption certificate shared with the third party using receiver AS2 adapter.
Is the above requirement is feasilble in SAP PI using AS2 adapter?
Yes.
Regards,
Prateek

Error in AS2 adapter. Object not found in lookup of as2.. Its urgent..!!

Hi AS2 experts,
*When i tried sending an xml to partner system using AS2 adapter.. Mapping is succesfull and message is failing in receiver AS2 adapter.
1. I used the following parameters in AS2 Module.
ModuleName                                                       Module Key
localejbs/Seeburger/solution/as2                              solutionid
localejbs/ModuleProcessorExitBean                          exit
ModuleKey    ParameterName         ParameterValue
exit                JNDIName     deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Iam getting the following error.
Success     MP: Processing local module localejbs/Seeburger/solution/as2
Error :   MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2.
Error : Exception caught by adapter framework: Object not found in lookup of as2.
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: Object not found in lookup of as2.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2..
2. When i tried by removing Modulename "localejbs/Seeburger/solution/as2"
It is showing the below error like AS2ID is missing.. but its there in party configuration.
Error :
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Can anyone has idea what might be wrong.
Kindly suggest me asap.
Thank You.
Regards
Seema.

Hi,
Plesae go through below links
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
and
Check with below configuration
Configuration for AS2 or simple file adapter.
We are using this module configuration for converting EDI D96A format to XML:
1 localejbs/CallBicXIRaBean Local Enterprise Bean bic
2 localejbs/CallSapAdapter Local Enterprise Bean 0
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic logAttID ConverterLog
bic mappingName See_E2X_ORDERS_UN_D96A
bic saveSourceMsg ORIGINAL_EDI
can someone please tell me the module configuration for reverse mapping at receiver end,i.e.,XML to EDI D96A
basically,I need mapping name for this.
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
File receiver:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_X2E_EDIFACT_ORDERS_UN_D93A
ONly the mapping program name changes from E2X to X2E. IN ur case it will be See_X2E_ORDERS_UN_D96A
Thanks
Swarup

Receiver AS2 Adapter issue.....Failed to get configuration from DATABASE. S

Hi,
Iam doing prototyping for File -AS2 adapter and ended up with below erros.
Error type: COMPONENT_ERROR >> Error date: 6/17/11 8:04 AM >> Description: AS2 Adapter failure Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:379) [6/17/11 8:04 AM]
and
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing..
The setting i have made during configation are :
1> Reciver Party with Agency,Schema and Name entered.
2>Identifiers for both Sender and reciver channel fileld with values seeburger and AS2ID.
3>Used Sender uses Virtual reciver in sender aggremnet.
4> Reciever CC have modules localejbs/Seeburger/solution/as2 and localejbs/ModuleProcessorExitBean in sequence.
Please provide solutions to overcome the issue.
As this is prototyping, i have downloaded Free As2 client and trying to send files to that client from PI.

Hi Dinesh,
make sure to also configure a report channel (refer to the sample chapter in the SEEBURGER AS2 documentation) in order to receive AS2 MDNs for your sent message. Additionally report channels are needed if the SEEBURGER specific TransmissionReports are requested.
Hope that helps
Greetings
-Sascha-

AS2 adapter Outbound Message

Similar Messages

Maybe you are looking for