save message payload as file

[#1]

Hello community.

Due to a customer request, I have to save a copy of the payload of every delivered message as a file in PO's filesystem, no matter the receiver adapter.

I know I can do it with receiver and/or interface split and a file receiver channel, but I was wondering if I also can achieve this with a custom adapter module or even with a java mapping class as a final step in my operation mappings. I even wonder if I can get this done with a standard adapter module.

I'm asking myself about this because I want to minimize the impact on all my integration scenario configurations, minimize the implementation effort and also minimize the amount of messages delivered in PO, which can have an impact on PO's performance and statistics.

I also know I can use the API to get the message payloads but I don't like much this option because first I need to get message IDs and then start iterating this list of IDs to get the messages. Moreover, as this messages come with a trace and the envelope, I need more effort to clean the message to get just the payload. So I prefer to write a file at mapping or delivery time.

I read a lot in blogs and the community but it seems not much people get requests as absurd as the one I got from my customer.

Thanks in advance for any input you give me regarding this thinking.

[krist0v]

If you'll be dealing with a couple of payload types, that could be feasible (bean or java mapping, though SAP does not recommend file operations in mappings AFAIR), but if you're dealing with many non XML payloads, it will be very very cumbersome, hard to maintain etc (and at what cost in terms of perfs)...

[juankinspain]

Thank you again for your insight.

I'll post here the outcome when a final solution is implemented.

[krist0v]

Silly request indeed! The only "easy" thing that comes to my mind is to create a "generic" file receiver channel for each of your receivers (no FCC or any other beans here) that will be used with a "as-is" interface (no mapping, source XML will be target XML) for EACH of your interfaces configured in each scenario

If customer wants final payload (TXT, PDF whatever), that'd be a nightmare to implement and could have huge impact on perfs or resources (scenario above might have some too).

[juankinspain]

Hello Christophe.

Thank you for your answer.

What about the custom adapter module and java mapping alternatives, do you think they are feasible?