On Thursday 14 June 2001 12:05, Aaron Smuts wrote:
> I have multiple background processes that primarily send and receive data
> for the web app ( including those that parse xml for insertion, generate
> xml for remote acounting sytems, take in data on transactions, push out
> bank deposit files, send information to ach providers, listen to mesaging
> sytems, generate reports, make graphs, convert images, . . . -- [most of
> which then deliver cache updates] ).
>
> I need some framework for centralizing the control.  They are currently
> running as chron jobs or just manually initialed.  I'd like to be able to
> monitor, start, and restart the from a control center.  

This sounds very similar to the Turbine Scheduler Service.  Have you looked 
at it? (http://jakarta.apache.org/turbine/services/scheduler-service.html)

>
> Some service could start the rmi activation daemon on a machine and then
> the control could call and spawn each process in its own vm.  It could then
> send monitoring requests and issue shutdown and restart commands.  Would
> this be an ad hoc use of the framework?
>

This is exactly the type of thing that I was looking at creating for my 
application (Tambora).  It currently uses a lot of Turbine scheduled jobs to 
move information around the application, kind of like what you are doing.  
These jobs can run under different JVM/Turbine applications.  

I also need the ability to stop and start my jobs remotely to so I was 
thinking of creating an XML-RPC handler for Turbine's XML-RPC service that 
will allow authenticated calls to a remote Turbine application to 
shutdown/startup/restart the Turbine Scheduler Service and also allow the 
adding/removing of jobs in a job queue.

Would this fullfill your needs? I do not have a time frame for getting 
something like this done yet but it is on my list :-)

John
-- 
********************************
** John Thorhauer
** [EMAIL PROTECTED]
** take a look at:
**  http://tambora.zenplex.org
**  http://www.zenplex.org
**  http://www.zenplex.com
********************************


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to