Seeburger AS2: dynamic message subject
Hi guys,
I'm using and developing an AS2 scenario with the Seeburger Adapter.
I've read Deepthi Thread relating having the AS2 subject build dynamically but there is no suggestion, and the manual is not clear about this.
In the situation of getting one message sent by an external partner, we need to have the message subject placed as * and then replace the * by a field sent on the message or even by a static text.
Have you guys faced this kind of problem?
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
Similar Messages
-
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 -
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 adapterHi,
> 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 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 -
Howto configure Seeburger AS2 Sender Adapter without using subject
Hello Experts,
we're going to implement AS2 Communication with a partner who isn't able to send the XML message with a subject in AS2 HTTTP headerfield but a different dtAS2FileName per message.
We have configured the scenario and it works as long as the partner only sends one message type (e.g. ORDER-XML). But of course there will be more than ORDERS and I don't know how to configure the scenario because I have to use only one Sender agreement with the same PARTNER-IDs (as mentioned in Seeburger AS2 Adapter Configuration Guide)
Can you please provide me the required configuration to deal with different Message-Interfaces from the same Partner.
We are an NW 7.0, Seeburger is on 1.8.1
Thanks in advance
Christian SperlichChristian Sperlich wrote:
Hi Suresh
>
> thanks for your answer. Exactly this scenario cames to our mind and was also suggested by another SAP Consultant. I'm sure this will work but (sorry!) this can't be the solution. Not only the additional configuration but also the monitoring of the EDI-Messages is more difficult if there were more than 1000 messages per day.
>
> Any other possibility / configurations?
>
> Kind regards
>
> Christian
Hi
You dont need to create another file channel to poll the files from a folder. This will be a additinal overhead to the system.
You can directly route the file on the fly based on dtAS2FileName to different receivers as well as interfaces.
You need to use condition in receiver/interface detyermination.
Your condition type shound be context object(not XPATH).
Then search for context object dtAS2FileName. -
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 MHi,
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 -
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,
JasonHello ,
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. -
Seeburger AS2 message signatures
Hi,
I have deployed the Seeburger AS2 adapter and it seems to work fin.
I would like to get a hold on the original signed messages both outgoing and ingoing direction. I have configured the dump parameter for seeburger, which gives 5-6 messages pr message send. The problem is I cannot find any of the IDs in XI, since XI uses a new GUID for the messages.
Have anybody found a way to store the Signatures in a meaningful way, which can be used in a dispute.
/regards
Daniel GraversenI have not found a solution
-
Seeburger AS2 - message does not arrive when "Athentication required" is ON
Hi guys!
If somebody of you is using the Seeburger Adapter:
I have an inbound scenario and everything works fine. But when I set "Authentication Required" flag to be ON, messages are refused. This is strange, because incoming messages are signed.
Any ideas, what could be wrong? There are several settings for certificates and maybe I have some wrong setting.. Does anybody have experience with this?
Thank you, PeterSai, you probably don't have experience with Seeburger AS2, do you? It works in a special way - that's why I'm asking people, who have experience with this..
But for clarification: My inbound Seeburger AS2 channel receives message scorrectly, but when I enable uthentication on it, AS2 messages are refused - so they are not in the AE, they are not in the IE.
Peter
p.s. I will not reward your answer, sorry
Message was edited by:
Peter Jarunek -
Seeburger AS2 receiver adapter conf PI 7.1
Dear All,
I have seen a changed AS2 adapter on PI 7.1,the options are totally different than what we have in previous version of AS2 adapter.
I am looking for seeburger AS2 adapter documents and configuration steps for PI7.1 version.
Any inputs...
chirag
Edited by: Chirag Gohil on Sep 8, 2010 5:03 AMAS2Receiver:
ModuleName: localejbs/ModuleProcessorExitBean
Type: Local Enterprise Bean
Module Key: Exit
-_Module Parameter_-
Module Key: Exit
Parameter Name: JNDIName
Parameter Value: deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
-_Parameters Tab_-
HTTP
Server - Computer with listening AS2 Server
Port - Port of the endpoint with listening AS2 Server
URL Path - Path to the endpoint with listening AS2 server
HTTP Timeout - Timeout in seconds for waiting for server's response
HTTP Keep Alive - If enabled, the HTTP session is re-used. This optimizes the performance.
Basic Authentication
User - User for basic authentication
Password - Password for basic authentication
Realm - Realm for basic authentication
Proxy
Proxy Server - Your proxy server
Proxy Port - The port of the proxy server
Proxy User - User for optional authentication
Proxy Password - Password for optional authentication
Proxy Protocol - Select either - HTTP 1.0 or -HTTP 1.1
AS2
Compress - Select this option if the payload is to be compressed
Sign - Select this if the payload is to be signed
Signing Algorithm - Select an algorithm which is applied for signing the payload; we recommend "SHA-12"
Encrypt - Select this, if the payload is to be encrypted
Encryption Algorithm - Select an algorithm that is used for encrypting the payload; we recommend "RC2/128" or "3DES"
MDN Mode - SYNC to request a synchronous MDN; ASYNC to request an asynchronous MDN; NONE if no MDN is required
Receipt Delivery Address - Enter the URL of the Asynchronous MDNs that are to be delivered (i.e. the URL of your own AS2 server)
MDN Timeout - Enter a time period (in min), after which an outstanding asynchronous MDN will be interpreted as an error. The value "0" means no timeout
Sign MDN - Select this option, if the MDN is to be signed
Message Subject - This text is sent to the server within the optional HTTP header "subject"
Content Type - The content type should be set. A random content type can be set, but we recommend one of the following
= "application/edifact" for EDIFACT files
= "application/edi-x12" for ANSI X.12 files
= "application/xml" for XML files
= "text/plain" for plain text files
= "application/octet-stream" for arbitrary binary files
Delivery transmission report - A special transmission report is delivered to the report channel -
Seeburger AS2 Adapter Error :AUTHENTICATION_ERROR
i am doing the scenario for Purchase Order -> XI ->File
custumer is posting the purchase order
and XI Receives the PO using AS2 Adapter (Seeburger) and sends the output as File
i have done all the AS2 Adapter configurations as mentioned below but still i am getting the error in Seeburger Monitoring, the Error is Authentication_Error
1. Communication chennel
Adapter Type : AS2
Direction : Sender
Transport protocol : HTTP
Message Protocol : AS2
AS2 : Authentication Required is Enabled
Message Subject : Filled which is in Seeburger Monitor
2. Sender Agreement
Sender Communicational chennel which is created above
Security Setting
AS2 Sender Config :
Authentication Certificate : Customer public key
AS2 Receiver Config :
Decryption Key : Private key
3. in Party Identifiers
Party Name
AS2 ID
is there any settings missing to rectify the error "AUTHENTICATION_ERROR"Hi
Check with PIAPPLUSER authentication
With this Check the following content on AS2 may be you get more clue.
http://www.customware.net/repository/display/WMFAQ/AS2-authenticationfailureinreceivingEDIINT+MDN
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bpxproj/edi%2bwith%2bpi
Handling EDI interfaces using Seeburger BIC modules
Thanks
Gaurav -
Seeburger AS2: Proxy Error 502
Hi guys,
I'm facing a problem using AS2 Seeburger Adapter.
When sending the message I'm getting the following error:
Could not deliver as2 message to partner: 502 Proxy Error
( The HTTP message includes an unsupported header or an unsupported combination of headers. ) # null
I've checked the AS2 Header message and I've got the following content:
POST /as2/HttpReceiver Connection: Keep-Alive
content-disposition: attachment; filename=1208788092268
Message-ID: <[email protected]1>
Subject: AS2 Message
Disposition-Notification-To: testcompanyAS2
AS2-To: receivertestAS2
Date: Mon, 21 Apr 2008 14:28:12 GMT
AS2-From: testcompanyAS2
AS2-Version: 1.1
content-type: application/octet-stream
begin test
1
end test
One of the things which is odd is why doesn't the AS2 adapter place the http://<server_used>:<port_used> before the "/as2/HttpReceiver".
Another thing is, shouldn't we have a line break after the POST?
It seems to me that this two problems may be raising the 502 exception...
Have you guys faced something similar?Hi,
no, there shouldn't be any line break and the path is correct too..
First thing I'd check is the proxy settings. Is your partner's AS2 server in the same network? Or are you sending messages outside your network? Ask the network guys for a information about the proxy. Is this configured in your adapter properly (there is a proxy configuration parameter)? Because I think there is network issue now..
Peter -
As2 receiver channel, SEEBURGER AS2: 500 Internal Server Error
Hi,
There is one scenario in our landscape, its running in production, Proxy to As2. The interface working fine for last 2 weeks, today its showing error in As2 receiver channel saying
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: 500 Internal Server Error # , SEEBURGER AS2: 500 Internal Server Error #
I have searched in forum, but couldnt get much idea on why this error encounters and how can we resolve it.
Kindly provide your inputs to help me resolve this.
Thanks,
RuchiHi Ruchi,
500 means the requested server does not understand the request (the requested service is unknown). The reason is obvisiously outside of PI. You have to contact the 3rd party owner and ask why the system is refusing the request instead of responsing like before.
Regards,
Udo -
There is no key entry with such alias in keystore seeburger AS2
Hi,
Error message in RWB shows the following
Message entered module processor exit bean and will be transferred to JCA adapter
2011-04-06 06:19:29 Success SEEBURGER/AS2: Received order from system.
2011-04-06 06:19:29 Error 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 key entry with such alias in keystore, 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.CryptoApiExc
2011-04-06 06:19:29 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: 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 key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.
2011-04-06 06:19:29 Error The message status set to NDLV.
2011-04-06 06:19:29 Error MP: Exception caught with cause javax.resource.ResourceException: 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 key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ks
unable to send / receiver messages through AS2. Please let us know what could be the error. How/ where to resolve it.Please check the SDN thread below
AS2 Adapter Configuration to Customer / no signature certificate
Also, check the help page below
http://help.sap.com/saphelp_sm40/helpdata/DE/84/be18d66b2a47f6b4adc704a7c0e23e/content.htm
for instructions on how to get the "SEEBURGER EDIINT AS2 Adapter for SAP Exchange Infrastructure Configuration Guide" from the Service Marketplace. Then, on this guide, please check the configuration according to your sender or receiver communication channel regarding the Security (certificates) parameters.
Are the key Store entries imported correctly? Please check if the certificates were imported in the right order and none of the certificates on the chain are expired. -
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!
PeterHi 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
Maybe you are looking for
-
I usually save downloads to the root of F:\ and have that set in my options. Since version 27.0.1 came along, Firefox ignores my setting and defaults to MyDocuments\Downloads. Reverting to version 26 or earlier corrects the problem and my downloads g
-
Hi..All, We are doing JDBC-RFC synchronous scenario using BPM, we are getting (Req & Res) data in to SXMB_MONI perfectly, the data is not updating into the Database Table, client wants to see the data in the DB only. how can i get the data in to DB T
-
Help wk through av comp.to watch movies From tab.to tv
Ell walk me through hook up f av compon. Rom iPad tablet2 to tv for watching movies
-
Error:maintain out going EDI Connection for Partner 1000
Dear Gurus, I have output master record for vendor 1000 and i have done edi settings namely fileport, partner prifile. My problem is 1While creating PO, the settings are not reflected ( i checked them in Path Goto->mesages.) When i try to give them m
-
Page Not Found error trying to import a large application into ApEx XE DB
I have an ApEx application that I'm trying to import from a Standard DB into Express Edition. I have 2 separate installs of ApEx both on XE and I'm getting the same problem on both. PROBLEM: After I import the application I get the error: PAGE NOT FO