The painful part of the process is the infrastructure, not the basics of the code.
Such a tool needs to deal with file systems in a relatively transactional manner - and most file systems are not inherently transactional. Some file systems (Windows for example) will also make a file available for reading before the creator has finished writing it. So you have to jump through some hoops to make sure you don't delete an incomplete file or pass an incomplete file. And make sure that the files you are writing out are not grabbed too soon.
Such a tool usually needs a configuration that is available to at least a certain class of business user/operator, if not to "end-users". This may end up requiring a database and a set of webscreens to maintain that database. And then, if you've got a database, you may need two-phase commit with your MQ!
Such a tool certainly needs monitoring - both to ensure that it is running, and for the inevitable case when the user puts a file with the wrong permissions in the input directory. _________________ I am *not* the model of the modern major general.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum