AS2 Adapter issues

Hi,
I have a scenario (Proxy to AS2).
Receiver channel is configured to HTTPS.
It passes successfully through MONI, but gives error in Receiver adapter.
Exact error is :
"Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake # "
Any help on this ?
Thanks,
Vikas

Looks like the other side is not configured for SSL. First check the address and port number you send the message to. If that turns out to be fine, verify that the java unlimited encryption has been deployed on your PI system (note the the default java encryption on a PI system is not the correct one!)

Similar Messages

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-

Seeburger AS2 adapter issue

Hi experts
We have migrated from XI 3.0 to PI 7.1.
The corresponding AS2 seeburger is also upgraded to a compatible version.
But after that it seems the mapping is not working. I am getting the foollowing error while using AS2 adapter at receiver side.
Runtime exception during processing target field mapping /LIST/S_ISA/D_I05_2. The message is: Exception:[java.lang.NoClassDefFoundError: com/seeburger/functions/permstore/VariableFactory] in class
A function in map uses seeburger classes(VariableFactory)
Thanks and Regards
Dhanish Joseph

As Anoop said check for property store values.
http://seeburger.com/xi/SeeFunctions provider.servlet.server ; http://localhost/50100 . check for this entry from property store from see front end.
make sure all other mapping variables and addressbook values imported properly.
Regards,

Issue with AS2 Adapter monitoring

Hi All,
I am using Seeburger AS2 Adapter in our XI project we are able to post and retrieve
messages through AS2 communication,but we are facing the problem of monitoring the messages if any incoming messages failed in the AS2 adapter only due to some network failure or some other issue we are not able to track which message is failed and what payload it contains as in Adapter Monitoring or communication channel monitoring AS2 Adapter shows the only "Failed Session"
Do we have any application to monitor it in XI.
Regards
Gaurav

Hi Gaurav,
Have you tried Tcode SXMB_MONI . In this by giving some details about your scenario, it will give you the information about all the messages which are successful or not. Here you can see the payload af successful messages and error in failed message by clicking on the perticular message.
hope this will help.
regards
HONEY

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

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

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

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 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

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

AS2 Adapter changing SSL Cert

Guys do you know how to use the AS2 Adapter ?. Our Customer is complaining that Invoices sent to them are now being rejected due to signing problem.
The Receiver Agreement has Security Settings for AS2 Sender Signing Key TRUSTED\ mycompanykeys \ mycompanykey
and AS2 Receiver Encrypt and Auth certicate TRUSTED\ mycompanykeys \ customercert
But if I have a new certificate were and how do I physically put this on the server ?

Hi,
As rightly stated it is an issue with the certificates.
To uplaod the certificates is the responsibilty of the BASIS team.However if you are suppose to do the settings than this is the procedure.
First thing you need to check is whether the SSL service is active. This youo can check in transaction SMICM>Goto> service.
Incase if you do not see the SSL service here then you need to active the service.
Please refer to the following procedure to activate the service.
http://help.sap.com/saphelp_nwpi71/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
Once this is done there are certain adapter specific settings, for this please refer to the following link.
http://help.sap.com/saphelp_nwpi71/helpdata/en/f5/799add57aeee4f889265094a04695c/frameset.htm
After finishing the above two procedures the certificates will be successfully uploaded in the system.(AS2 requires two kinds of certificate i.e.e SSL for encryping serving information i.e. host, port etc and second is the AS2 certificates to encypt the actual payload)
Once the AS2 certificates of the sender are uplaoded in the XI server then the name of this certificate is to be given in the Key trusted that you have mentioned.
regards,
Milan Thaker.

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>

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 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.

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 Adapter: "MDN not signed"

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

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

Seeburger AS2 Adapter with HTTPS transport

The AS2 adapter is generating the following error.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection., SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection.
According to documentation, the SSL Certificate (keystore) field should point to the keystore, and not a specific key. in my communication channel it does. Thep rivate key points to my key. I have verified both of these entries are correct.
Other than that, this scenario is configured the same as my previously configured scenarios that use HTTP, all working without issue.

Thank you, we had already done that.
What we found however was the entry for the "keystore" in the communication channel, we needed to fully name the key to be used, as opposed to simply the keystore.
Once we did that, we cycled the as2 adapter and were able to send a message successfully.

AS2 Adapter issues

Similar Messages

Maybe you are looking for