Posted: Fri Mar 05, 2010 12:22 am Post subject: Scheduling Message Broker Flow - Design Challange
Newbie
Joined: 05 Feb 2010 Posts: 9
I have a requirement for scheduling a message broker flow which reads the XML messages from MQ Queue and Writes into a file in a Shared FTP location. There is another java Batch process which consume these files for further processing and removes these files from the FTP location.
I want to schedule this message broker flow to run every 2 hrs interval daily and wait (stop) between say 3:00 PM to 4:00 PM daily for Java batch process to consume the files from FTP location.
Queries:
1. what should be the nodes structure and how can I achieve this?
2. Is it good to use some external scheduling tools like crontab or CA7 for such requirements.
I will greatly appreciate your help. Thanks!!
I searched through this forum for similar issues related to Timernotification and TImerControl nodes. Not exactly answers my question.
Posted: Fri Mar 05, 2010 7:50 am Post subject: Re: Scheduling Message Broker Flow - Design Challange
Grand Master
Joined: 25 Jun 2008 Posts: 17447
[quote="yps_sengar"I searched through this forum for similar issues related to Timernotification and TImerControl nodes. Not exactly answers my question.[/quote]
Why not?
These and an MQGet and a FileOutput node are what I'd use.
Thanks for replies. Yes I am using MQInput/MQGet --> FileOutput.
I want to know which is a better approach between using TimerNotification and TimerControl or external scheduler. I am little confused. The below article recomends Timer node over external scheduler.
It's a fine article from a worthy associate on this forum. I would agree with him wholeheartedly that if you have a flow with an inbuilt timeout or other self contained timing issue then these node provide an ideal way to handle them.
I am less convinced that for a simple batch process such as you describe maintaining crontab is as much of an issue as he claims. I've also never seen a Unix site that didn't have cron installed. But it is an issue (insofar as it's a point to consider when planning) and you must make your own mind up given the particular requirements under which you're working.
Bottom line - I said cron might be easier. You might decide I'm wrong. You might be correct in that. _________________ Honesty is the best policy.
Insanity is the best defence.
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