Outbound Seeburger AS2 setup problem

Hello,
I am trying to setup Seeburger AS2 adapter in the way that I can post documents from our SAP system to the external server that is sitting in the internet. I was following the SAPXI30_AS2Adapter.pdf guide but it is still not working. When I initiate the posting in SAP it goes correctly to XI, XI correctly process the IDOC and maps it to XML document and pass it to AS2 adapter. But here it fails. In adapter monitoring I can see this error message:
Description: AS2 Adapter failure
Details: Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..[8/31/06 9:23 AM]
ConnectionId: null-allianceTestingServer_Party >> PartnerAddressId: allianceTestingServer_Party >> Transferred: 0/0 >> Error type: pre plugin call failed >> Error date: 1157030604769 >> Description: [8/31/06 9:23 AM]
2006/08/31 - 09:28:28:40
Retryable fault in 'Channel:allianceTestingServer_AS2_outbound'.
I think I've setup everything correctly so no idea where can be the problem. It is saying that I probably do not have AS2ID setup but it is either not true or I do not know how to do it.
Any help would be very much appreciated.
Thank you.
Martin
Solved on my own:
I really didn't have sender configuration completed. I've created new Party, configured it as AS2, created AS2ID for it etc. and then forced it as a sender in the Receiver Agreement.

Hi Anoop!
Yes, we use it on receiver side.
ModuleProcessorExitbean exists, so it should be ok.
What I'm not sure about is the thing with identifiers..
In Party (let's call it X) - Identifiers, we have default agency http://sap.com/xi/XI, scheme XIParty and name X.
What values should be there for Seeburger?
We have Agency: Seeburger, Scheme: AS2ID; Name: X.
Is it correct?
We also received some 9 char long number - probably some ID to adapter(?). Any idea, if it is necessary and where to use it?
Is it necessary to configure identifier seeburger also in Identifiers tab of Receiver communication channel? Or we can leave it empty (both- sender, receiver)?
We use this in B2B scenario, of course: Target system is party, but we use our R/3 as Business System w/o party. Is it ok, or do we laso have to "be" as Party in our configuration scenario?
A lot of questions, but points will be awarded 4 sure
Thanx!
Peter

Similar Messages

Seeburger AS2 comm channel problem (B2B) - "perhaps AS2ID missing"

Hi guys!
We try to configure B2B scenario using Seeburger AS2, but communication channel monitor returns error:
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 9/25/07 10:05 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321) [9/25/07 10:05 AM]
We're not sure about the scenario configuration and using identifiers (cos' this is probably the problem).
Did someone of u already configured Seeburger AS2?
We have configured in receiver party alternative identifier Seeburger - AS2ID, however, the message sent to target has always agency XI and scheme XIParty. It should be probably Seeburger and AS2ID (the alternative one).
<SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">XXXX</SAP:Party>
<SAP:Service>BS_3RD_XXXXX</SAP:Service>
<SAP:Interface
How to achieve it?
Thanx a lot!
Peter

Hi Anoop!
Yes, we use it on receiver side.
ModuleProcessorExitbean exists, so it should be ok.
What I'm not sure about is the thing with identifiers..
In Party (let's call it X) - Identifiers, we have default agency http://sap.com/xi/XI, scheme XIParty and name X.
What values should be there for Seeburger?
We have Agency: Seeburger, Scheme: AS2ID; Name: X.
Is it correct?
We also received some 9 char long number - probably some ID to adapter(?). Any idea, if it is necessary and where to use it?
Is it necessary to configure identifier seeburger also in Identifiers tab of Receiver communication channel? Or we can leave it empty (both- sender, receiver)?
We use this in B2B scenario, of course: Target system is party, but we use our R/3 as Business System w/o party. Is it ok, or do we laso have to "be" as Party in our configuration scenario?
A lot of questions, but points will be awarded 4 sure
Thanx!
Peter

Seeburger AS2 Communication Channel Error

Hello,
when trying to send a test message to the AS2 receiver communication channel I get the following error in communication channel monitoring:
javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: ResourceException caused by com.seeburger.xi.api.cci.SeeXIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., ResourceException caused by com.seeburger.xi.api.cci.SeeXIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE..
Have you ever got a similar error? Seems to be a configuration error of the adapter installation itself rather than a problem with configuration objects or the receiver channel.
Do you have any idea?

Hi Florian,
Please provide info if there is a need for any Sender agreement in case we select "Synchronous" mode for MDN and Handle Received MDn as "NoAction".
I am also getting the below error for my scenario (IDOC --> XI --> AS2)
Description: AS2 Adapter failure Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.. com.seeburger.as2.AS2Plugin.execute
Thanks and regards
Ajay Garg

Client Auth and SSL with Seeburger AS2 adapter

Hello All,
We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.
and I hope that you will be able to help me out.
1. Server SSL on Receiver AS2 adapter
I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.
This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.
The issue here is :
Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.
Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.
I am using a Decentral Adapter Engine with LoadBalancer.
2. Client Auth on Receiver AS2 Adapter
I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.
XI error's with the error "SSL handshake failed - Bad Certificate" .
I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,
Server Certificate ( Keystore) and Private Key for Client Authentication.
Has anyone tried this? If further details are needed, I will be able to furnish the same.
Regards,
Bhavesh

Hello Jens,
Thanks for your reply.
1. The Encryption and Signature part of the Interface is working absolutely fine and I use the same concept highlighted by you - The Sender always signs the message with his private key and encrypts with message with the partner's public key in the corresponding agreement.
2. Server SSL is also working perfectly fine, i.e, when XI initiates the connection the SSL connection is established to the partner.
3. Mutual Auth was the issue where I was getting the bad certificate issue.
To investigate further I moved the same setup to my Central Adapter Engine and all the issues I had described above seem to have vanished and things work exactly as I was expecting, ie.
The field : Server Certificate (Keystore) is used to provide the Target System's Server SSL's public Certificate.
The field : Private Key for Client Authentication is used where XI provides its own Server SSL's private key for Mutual / Client Authentication.
The problem seems to be with my Decentral Adapter engine and not my central adapter engine and so I guess,
1. I either have the incorrect certificates on my Decentral Adapter Engine.
2. I also have 2 instances of a Decentral Adapter Engine with a Webdispatcher and so maybe the 2 Visual Admin's of the 2 Decentral AE are inconsistent.
3. Maybe it was just a long day and I did something wrong
Will investigate further for the root cause but I am glad that my concepts remain intact and things do work as I expected them to work.
A blog on all this is on the cards sometime soon.
Cheers,
Bhavesh

Seeburger AS2 Adapter failure

Hi ,
Iam trying to test the Outbound AS2 connection though the receiver is not yet ready with the setup but i want to make sure at my side . While testing i got this error message ..
"Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no certificate with such alias, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Th"
and 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: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no certificate with such alias, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.
Can anyone help me to identify the issue here ?

The certificate of your client must be maintained in AS2 keystore. Make sure that in the receiver agreement, you have given the same name. If certificate name is test.crt, then receiver agreement should have entry AS2keystore\test.
Regards,
Prateek

Seeburger AS2: Authentication_error after upgrade

Hello all,
We've recently upgraded our XI 3.0 system to PI 7.1EHP1, and since this upgrade we're having problems with the Seeburger AS2 adapter (2.1.3). The outbound message (signed and encrypted) to our other party is fine, but the acknowledgment gives an error in the message overview:
Error while parsing AS2 message: AUTHENTICATION_ERROR #
We've checked the certificates in the NWA store, and they are all fine. We've also checked the user for the AS2 adapter in the connection factory, and these settings are also fine. The sender agreement contains a reference to the right certificates in the store.
Has anybody run into the same problem, and does anybody know how to fix it? There are some posts on SDN about this, but they all point towards the certificates (which seem to be fine) and don't offer any further explanation of the problem and a possible solution.
Kind regards, Wilbert

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

Com.seeburger.ksm.cryptoapi.exception.CryptoApiException in Seeburger AS2

Hi Experts ,
I am facing some very weird issue of getting below error whenever I try to enable the Encryption in my Receiver AS2 Seeburger Adapter :
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
But the moment I send data without signing and encryption it goes well. We have tried placing certificates in receiver agreement and in key store.
Thanks
Abhishek

Prateek ,
Thanks we were able to identify the user to be mentioned but now we are facing below error while using certificates with SH1withRSA Encryption and in receiver channel Encryption algorithm as 3DES :
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm.
The problem doesnt ends here ... while our partner trying to send us data to the URL we have provided its getting 403 Forbidden Error. We have tried resolving the steps which were given in manual but again the sxase is same.
URL : http://server:port/SeeburgerAS2/AS2Server
Any inputs if you can provide on the above 2 errors .
Thanks
Abhishek

Seeburger AS2: MD5WithRSAEncryption NoSuchAlgorithmException

Hello,
we use a AS2 receiver communication channel with SSL encryption. However when sending out a message we get the following error.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption), SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption)
We already checked that all Java Policy Files have been deployed. We have also tested the adapter successfully.
Any ideas on this?
Thank you!

Hi Florian,
have you checked the following:
-Installation of the Java Cryptography Extension?
-Did you deploy SeeCryptoSourceBridgeLibXI.sda? (Seeburger Certificate Service)
-The Exception "java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation" could also point to a problem in the Keystore:
--> Did you create an Adapter User to access the Keystore?
--> Check if you have set the view_creator role of the keystore you are using to EVERYONE.
--> Maybe your certificate is corrupt?
regards,
Daniel

Seeburger As2 Receiver channel exception for large files

Hello Folks,
We have JMS to seeburger AS2 interface we are facing follwing issue in As2 reciver channel for files larger than 20 MB.But In Production it is wokring fine for even 40 MB also.
Delivering the message to the application usingconnection 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: org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated. # , SEEBURGER AS2:org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosingrequest can not be repeated. # .
Please through some light on the issue .
Regards
Praveen Reddy

Hi Praveen,
The problem would be related to server size. genrally test system do not have same sizing as production server due to that you can not process large files in test system.
check the sizing of the system.
regards,
Harish

How to deal Inhouse files using Seeburger AS2 adapter...!!!

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 deals with EDI files) 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.
I have few custom Inhouse files where i need to recieve through AS2 adapter.
I need to differentiate the messages hitting to my communication channel.
ex:
1st message will be having
HDR PICKS
2nd message will be having
HDR PURCH
so based on the second field which has "PICKS" or "PURCH" , i need to pass the message to run the corresponding map.
How i need to configure to acheive these kind of custom Inhouse files through AS2 adapter??
Do i need to use splitter for these as well?? If yes how i need to use?
Is there any setting we can make at Sender AS2 adapter to differentiate each message??
Waiting for the answers.
Kindly reply if anyone knows.
Thanks&Regards
Seema.

Hi,
i have setup a scenario with edifact (different message types) using as2.
first i had to create a mapping using bic.
edifact_xxxx
in: edifact_service
out: functional acknowledgement.
in the mapping code i adjusted the called mapping, standard it will use see* changed it to e2x* (custom mapping)
in your case using flatfiles maybe you should take a look at the VDA structure, these files are also defined under inhouse.
when you define a input file adapter are you getting a classifier message?
like
<classifier><type>Edifact</type><classifierMappingID>XXXX</classifierMappingID><encoding>US-ASCII</encoding><additionalIdentifier></additionalIdentifier></classifier>

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

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.

SEEBURGER AS2 adapter test

Hi
I am trying to test AS2 adapter. I configured sender file channel and Receiver AS2 channel. i also configured the mdn report channels. But my AS2 receiver channel is failing saying mdn report channels are missing.
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. MDN requested, but appropriate report channel is missing. Missing inbound relation between AS2From: 'XXXX_Qx2' and AS2To: 'XYZ_QX1'., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. MDN requested, but appropriate report channel is missing. Missing inbound relation between AS2From: 'XXXX_Qx2' and AS2To: 'XXXX_Qx1'.

Hi,
Please check following thread
Re: File ->AS2 error?
Regards,
Deepak.

Content based receiver determination with Seeburger AS2 adapter

We are planning to use the Seeburger AS2 adapter on our XI 3.0 installation to post custom XML documents to XI from external business partners. The problem we have is to do the receiver and interface determination based on the xml message type that is submitted. How can we identify what is the name of the root xml node (which is representing the message type that was submitted to us) during the receiver determination and specify conditions for the receiver determination based on this? We can not use the Seeburger Classifier module here as this is only determining the mapping name to be used for an EDI conversion but can not handle any type of XML message.

Rudy,
I think the easiest way would still be the ReceiverDetermination and creating an XSD that contains the main important TAGs from the different messages.
That should allow you to test for the existing of certain important TAGs or check the value of some TAGS.
I don´t know about aedaptive-adapters, but I don´t think that they are Drummond-Certified. Check out...
http://www.drummondgroup.com/html-v2/as2-companies.html
Without this certification, a lot of your partners might not allow you to use this adapter if you wanna make AS2 with them.
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

Outbound Seeburger AS2 setup problem

Similar Messages

Maybe you are looking for