We have similar requirements. An external scheduler (Tivoli) is used to trigger some batch processing (reading and processing large files). The trigger happens via HTTP and provides the file name which should be processed. After we finished the processing (multiple routes which are decoupled by queues) we have to return the HTTP call with a status code. Like 0 == OK, 1 == Error 1, 2 == Error 2, ... And of course, we have to stop the route...
For this, we have implemented our own solution because this was not possible with a route policy (we need something like a "use case policy"). We use the Camel API to start/stop routes, to track inflight messages and whether they failed or not. Not an easy solution at this time... Best, Christian On Sun, Oct 28, 2012 at 4:48 PM, bung_ho <bung...@hotmail.com> wrote: > For various reasons it's not practical to use quartz etc to schedule my > routes, all the scheduling must be done using the corporate scheduler. I > have searched the forums and it seems all scheduler discussion is based on > the built-in quartz/cron etc. > > Anyway my idea to integrate with the external scheduler is simply to use a > <from uri="file: ..." /> that looks for a marker file that will be placed > by > the external scheduler, this will tell the route when to run. I figure > also, > the route can drop another marker file at the end to report success or > failure; the external scheduler can also be made to look for these files to > get the job status. > > Can anyone think of any drawbacks to this approach, or have any better > suggestions? > > Thanks > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/external-scheduler-integration-tp5721668.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
