Müller [mailto:christian.muel...@gmail.com]
Sent: Wednesday, October 31, 2012 10:13 PM
To: users@camel.apache.org
Subject: Re: external scheduler integration
The difficult things for us are:
- track each exchange until the end so that we know when we finished
processing a file and we
- can stop
> christian.mueller@
> ]
> Sent: Wednesday, October 31, 2012 4:29 AM
> To:
> users@.apache
> Subject: Re: external scheduler integration
>
> We have similar requirements.
> An external scheduler (Tivoli) is used to trigger some batch processing
> (reading and p
to run the
> above on cluster as most jobs were decoupled among themselves and acted on
> computing values on read only data?
>
> -Original Message-
> From: Christian Müller [mailto:christian.muel...@gmail.com]
> Sent: Wednesday, October 31, 2012 4:29 AM
> To: users
JCR (java content repositories).
>
> -Original Message-
> From: Raul Kripalani [mailto:r...@evosent.com]
> Sent: Wednesday, October 31, 2012 7:13 AM
> To: users@camel.apache.org
> Subject: Re: external scheduler integration
>
> Another possibility is to use the came
]
Sent: Wednesday, October 31, 2012 7:13 AM
To: users@camel.apache.org
Subject: Re: external scheduler integration
Another possibility is to use the camel-stream component to tail a file
that serves as the "common interface", to which the scheduler writes to in
order to trigger an executio
Another possibility is to use the camel-stream component to tail a file
that serves as the "common interface", to which the scheduler writes to in
order to trigger an execution.
It can write the filename it wants to process, and that would be fed into
your route. It's kind of like running a tail -
as
intelligent state parser (but should not maintain state) as well as router.
-Original Message-
From: Iyer, Ramkumar (Cognizant)
Sent: Wednesday, October 31, 2012 6:19 AM
To: users@camel.apache.org
Subject: RE: external scheduler integration
I am familiar only with Quartz for scheduling
: users@camel.apache.org
Subject: Re: external scheduler integration
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
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
que
On Sun, Oct 28, 2012 at 5:26 PM, bung_ho wrote:
> Thanks for the reply. The message queue is a good idea but obviously it will
> take a little more work on the scheduler side to implement, not sure if I
> can get the help from that side in order to do it. I will consider this as
> the "proper" app
Thanks for the reply. The message queue is a good idea but obviously it will
take a little more work on the scheduler side to implement, not sure if I
can get the help from that side in order to do it. I will consider this as
the "proper" approach to be implemented in the future :)
But also, many
11 matches
Mail list logo
