This could be done using a Scheduled Listener implementation. There's info about this in the docs (programmers guide).
JBossESB is great (mostly), but you might be better off with a batch processing system like CA Autosys or even just simply cron (or perhaps even quartz inside JBoss or JBoss Scheduler )
Reasons you probably shouldn't use JBoss ESB:
1.) What use does a self-contained, long-running batch process have for messaging?
2.) Your batch processes will be constrained to the threading model of the app server, as you shouldn't be starting your own threads inside JBoss.**
3.) You'll need to have hot-deploy on in production and stop an entire ESB component in order to redeploy schedule changes. I suspect that this will stop the currently running batch process. Thus, you'll be stuck with one deployment unit (.esb archive) per batch process if you need flexibility.
**The Quartz and JBoss Scheduler solutions are are susceptible to weakness #2 also.
Don't get me wrong, I'd love to have another user so this project becomes more popular and gets more attention and perhaps more paid developers (or more volunteer developers, even), but I'm not sure JBoss ESB is the way to go for you.
Thanks for the replies so far.
At the moment we've an framework for batch processes developed by ourselfs. This framework is running on production but is difficult to maintain and to extend. So the idea came for a platform where we can deploy modules "the batch processes" and each module can be indivudaly stopped and started. On the esb you could use JBoss ON and the adminstrators have a frondend to maintain the processes.
1. We can rewrite some processes to put messages on a queue or topic. But still this proces use a callback structure to retrieve data information which we need for backend processes.
2. I agree with this, but in the older documentation from ESB Rosetta they had also to deal with this problem. I was hoping that this part BatchProcess is also in the jboss esb.
3. Is the feature we want.
Any advice or ideas.