Mec as2 with SAP XI/Seeburger
guycrets,
thank you very much for these tests.
Mec AS2 --> SAP XI/Seeburger : async MDN give ERROR
---------------------------------------------------
Mesg signature : SHA1
Mesg encryption: none
MDN : async, signed
--> ERROR (RED)
Although the status is RED and the message is copied to the error folder, no real errors are reported in the log.
I think the problem is the HTTP 202 that is returned by the remote server in this case. m-e-c as2 expects a HTTP 200. Does there exist a way to change the return code at the remote system?
Anyway I think it is a good point, we will add the possiblity to accept more than HTTP 200 as positive answer.
The problem with async MDN also occurs if
- unsigned MDN is requested
- 3DES message encryption is used
SAP XI/Seeburger --> Mec AS2
----------------------------
Mesg signature : none
Mesg encryption: none
MDN : sync, unsigned
Seeburger reports an error:
AS2 message parsing failed: com.seeburger.ediint.mdn.MDNException: com.seeburger.ediint.mdn.MDNException: failed to parse MDN: javax.mail.MessagingException: Missing start boundary
This looks like a problem on the remote system side: unsigned AS2 messages are not send in MIME format and have therefore no boundaries. That means it is not possible to parse them using the java mail API (the exception shows that this has been tried). It would be great if you could send me an unsigned messages (unencrypted) that has been created by the remote system.
All the other errors that you have reported with unsigned messages seems to have the same source, these missing boundaries. Even if the raw message transport is really uncommon it would be good to have full compatibility to the Seeburger AS2.
Mesg signature : SHA1
Mesg encryption: with or without encryption
MDN : sync, signed
The message is received, no real error is reported, but message is not processed.
Mec AS2 also put the value "Unknown" in the column "signature for the incoming message.
[3:05:36 PM] AS2ServerRemoteImpl: 1 >= 1
This looks like an encoding problem or something similar in the m-e-c as2 server. "1 >= 1" is the error output of an OutOfBoundaryException in java. It looks like the number of body parts in a MIME multipart could not determined correctly. It would be great to investigate this issue more detailed.
m-e-c as2 will write "Unknown" into the encryption and signature state of the transaction until the message parsing is complete, that is why you find it there.
Other tests - with async MDN - go fine
Mesg signature : SHA1
Mesg encryption: 3DES
MDN : async, signed
--> OK
This is good to know because these are (as far as I have seen) the most common cases.
Again, thank you for the tests. It would be great if you would contact me to see on how to fix the problems that occured.
Regards
Heller
sh at mendelson dot de
Hello,
Were you ever able to test XI - MecAS2 with Client Auth turned on?
I have turned on the Client Auth in MECAS2 but when I try to post the message from XI - Seeburger AS2 adapter the message errors with error " SSL Handshake failed - Bad Certificate ".
I have loaded the Public Cert of my XI Server SSL in MEC's Keystore and am using the same as the private key in the Seeburger AS2 field, Private Key for Client Authentication.
Did you ever try this? Did it ever work?
I can provide more info if you need.
Regards,
Bhavesh
© 1999-2008 mendelson-e-commerce GmbH. All right reserved.
All,
For testing the Seeburger AS2 adapter running within SAP XI 3.0, I have used the mec as2 server. While doing my initial tests, I've written down the scenario's that work and don't work.
Please find attached the test results.
Kind regards, Guy Crets