Keeping the "original" filenames during sending process
nabster,
we had this issue several times so far but I am not fully aware of the actual state of the discussion. As far as I know there is no way in the as2 standard to ensure that the filename is kept over the transmission. It mainly depends on how the receiver handles the attachment filename header (and if the senders as2 systems even sends it).
It is already implemented to keep the filename on sending as2 messages from m-e-c as2 but the receipt has not been implemented so far.
I will add an option to keep the filename if messages are received by m-e-c as2. It is already parsed out of the incoming message and sent to the log (you can see it in the transaction overview)
But again, it is not ensured that this feature works using different as2 systems on receiver and sender side.
Regards
Heller
nabster,
you will find the file name in outgoing AS2 messages from m-e-c as2 in the following header, this has to be parsed by the receiver system.
Content-Type: application/EDI-Consent
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename=abc123456.abc
Regards
Heller
heller,
right, I found out about that. So this is the problem of the receiver now ;-)
But there is another question I have about "launching mecAS2 as a service". I have posted my comments to the corresponding topic: http://www.mec-community.com/node/176
Could you please have a look at this and also add your comments/experience there (maybe interesting for others, too)?
Thanks,
nabster
© 1999-2008 mendelson-e-commerce GmbH. All right reserved.
Hi,
i have prepared 2 mecAS2 servers for test scenarios to validate if the mendelson AS2 solution satisfies our requirements. The requirements are quite easy:
Somewhere some files are created that need to be sent to a partner. The filenames include a unique ID, for example "abc123456.abc". Exactly this file has to be sent to a partner, which is done by moving it to the corresponding outbox. From there the mecAS2 takes the file and sends it to the corresponding partner (and writes logfiles etc...). In our szenarios it is required that the filenames do not change. That means that the file in the inbox of the receiver has to be named "abc123456.abc" in our example instead of something like "mec_as2-1200499801187-10@leopoldAS2_nabiAS2". The reason for this is that the receiver (process) uses the id retrieved from the original filename for further processing. Besides that the fileending (in our example ".abc") should has to be kept!
Does anyone know if mecAS2 supports all this? If not, where do I have to change the source code to make it fit our requirements?
any help is welcome!
Thanks