Amine wrote:
> > when you redesign a legacy system with J2EE you use EJB for interactive
> > programs.
> > What do you use for batch ones?
You can use a job scheduler. A job scheduler can schedule and queue the
non-interactive (batch) tasks that you want to execute. And when it
comes time to execute each non-interactive task, that task could be
fired as an EJBean, a JMS message, or whatever J2EE mechanism that is
appropriate.
<vendor>
Flux is a job scheduler that fully integrates into J2EE and Java
applications. You can schedule and queue all your non-interactive tasks.
As Flux fires each job, it can notify your session beans or JMS message
listeners. In turn, these beans and message listeners can perform the
appropriate batch work.
Flux persists jobs in a database, you can pause/resume/interrupt jobs.
You can schedule jobs using simple strings to denote when a job should
run. For example, Mon-Fri at 9 am at 4 pm, the first business day of the
month, every Friday unless that day is a holiday in which case run it on
the previous business day, the last Friday of the month, every 90
minutes, every 125 milliseconds, etc.
Flux is at http://www.simscomputing.com/
</vendor>
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
