on 02-12-2014 12:42 PM
Dear experts,
I have an AS2 Receiver Channel in a PI 7.31 single stack environment. When sending a message unencrypted, all is fine, the payload on the receiver side (mendelson as2) looks fine, it only contains the Idoc data. But when sent encrypted, the payload now starts with 3 additional lines:
Content-Type: application/edi-x12
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename="BSR_PI_BENUTZER_EW"
<Z_ORDERS04 ...
where and why are these lines added and how to remove of them?
thanks for your help!
Christian
Hi Christian,
Were you able to resolve this issue? I am having the same problem with my mail receiver adapter in PI 7.31
Thanks,
Syed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Syed,
the answer from SAP was:
Thanks for the file. One of the header coming with the edi content is:
Content-Disposition: attachment;
filename=4830bd60-9ee5-11e3-9afd-8a510a010165
The header is coming in 2 lines. This is called folded header. We
don't support folded headers in our SP01 release.
Even the folded headers are not recommended by Drummond.
Possible solution:
1) Ask 3rd party vendor not to send folded headers.
2) Upgrade SAP AS2 to SP02. Here we support incoming folded headers.
If the above solutions are not acceptable to you then please let me
know so that I can process a patch for you to accept folded headers.
I haven't tested the recommended solution yet.
cheers
Christian
Hi Harish,
thanks for your quick reply! My receiver partner complains, that its not a valid xml anymore. The xml-parser gives an error and inbound processing of the message is failing.
cheers
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Christian,
when a message is transmitted via AS2, the file content on sender side before encryption definitely needs to be the same as the content on receiver side after decryption.
So...either your software has some trouble with applying the encryption (or the lines are added beofre this step)...or your partner is doing something wrong when decrypting the data.
My suggestion would be to send the data also to another endpoint/test-partner and verify if he also has these added lines (to see if the error is on his side or on your end)
Kind Regards
Stefan
Hi Christian,
AS2 protocol adds the as2 header when you encrypt, compress or sign the message. but what is the issue when it adds the header? your receiver partner should able to extract the message and the header is required to decrypt the message.
refer the below doc
About the AS2 Protocol (Sun B2B Suite AS2 Protocol Manager User's Guide)
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.