Hi all,
I wish I could prevent XI from consuming a file in the outbound directory before it is time.
There are two business aspects :
<b>1</b>- a new file with the same name could be sent in the outbound directory and the old file should be erased by the new one
<b>2</b>- the message(s) extracted from the file should be sent to the receiver only during a certain period when the receiving application is ready for it.
As this problem is common to many scenarii, I am looking for some reusable solution.
I thought of (or was proposed) the following solutions :
- <b>event-driven messages</b> : the condition 2 is OK, but the file is consumed, so if a new file arrives, it is also consumed and both sets of data are sent to the receiver. Therefore, condition 1 is not correct.
- <b>BPM</b> : I am not yet familiar with this part of XI, and I wonder whether it could work.
- <b>module adapter</b> : as a Java developer, it was nearly piece of cake to say whether it was time or not to send the message(s) . But the module is executed after the file was processed, so condition 1 isn't fulfilled because the incoming file has been moved to archive directory before the authorized period. I tried to change the Processing mode from "archive" to "test" in order to avoid the file being moved and it works fine, except I'm not keen doing that in a production environment.
Moreover, when it is not time, how to cleanly" stop the process? I figured out I could sweep all data from xmlpayload so the process would carry one, but with no data. I don't know why, but it produces some mapping error and a red flag in monitoring. I also thought about throwing Exceptions, but I have no monitoring.
It's quite a long blog, but I wanted to explain what the problem was and what ways I tried.
Has anybody some advice to give me (except suicide, my boss wants his problem solved first ) ?
Regards
Yann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.