Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Hi,
I am looking into starting to use Quartz as batch job scheduler for a project which has previously had their batch processing performed under OPC control on MVS. And have a few questions I hope someone can answer:

- does Quartz come with a Web GUI ? It is hinted it does on this site: http://onjava.com/onjava/2005/09/28/what-is-quartz.html. Where would I find it - and what are its functionalities ?

- as far as I have been able to determine, jobchaining can be established either in terms of coding ones own listeners to start one job on completion of another - or by direct triggering of the next job as the last step of the execute() method of the previous job. What about more complex dependencies, where job C depends on the completion of jobs A and B. How is this handled ? And can jobchains be "configured" rather than coded ?

- handling of jobs that end in error and needs to be rerun, potentially after correcting data or fixing the code. How can this be achieved ? For instance, if the job is in the middle of a jobchain where the first job is triggered by the scheduler and a trigger and has completed successfully with triggering the second job in the chain as the last step in its execute() method. If this second job then fails. what means exist to rerun this second job and have the rest of the jobs in the chain executed ?

Thanks and regards,
Palle

sejer wrote:

- does Quartz come with a Web GUI ? It is hinted it does on this site: http://onjava.com/onjava/2005/09/28/what-is-quartz.html. Where would I find it - and what are its functionalities ?

There was a web-based gui that was built some years ago but fell out of maintenance. It can be found in the SVN repository, and should mostly work, but it is fairly rudimentary.

Terracotta is preparing to invest in building a new maintenance Panel, but that is some time off.

With Quartz's API, it's pretty easy to create your ow web pages that provide the functions that you want (e.g. listing jobs, deleting/pausing jobs, etc.).

sejer wrote:

- as far as I have been able to determine, jobchaining can be established either in terms of coding ones own listeners to start one job on completion of another - or by direct triggering of the next job as the last step of the execute() method of the previous job. What about more complex dependencies, where job C depends on the completion of jobs A and B. How is this handled ? And can jobchains be "configured" rather than coded ?

Those are really your options. Workflow has been out-of-scope of the project up until now. There is a simple chaining listener that ships with Quartz.

Listeners can track which jobs have completed with which statuses, and issue scheduling commands based on what they see.

Some people couple various open source workflow engines with Quartz.

I've seen implementations that use a base abstract Job class that knows who to communicate with a workflow engine or state machine to decide what if anything to trigger next. The execute() method is implemented on this class to call an abstract template method such as doExecute() and then makes the workflow/state checks and moves things along. The extending Job class puts its work in the template doExecute() method.

sejer wrote:

- handling of jobs that end in error and needs to be rerun, potentially after correcting data or fixing the code. How can this be achieved ? For instance, if the job is in the middle of a jobchain where the first job is triggered by the scheduler and a trigger and has completed successfully with triggering the second job in the chain as the last step in its execute() method. If this second job then fails. what means exist to rerun this second job and have the rest of the jobs in the chain executed ?

Typically the listener (or whatever other mechanism) that handles the chaining will only trigger the next job if the current one completes successfully. If the job throws an exception, the scheduler itself may auto-ree-xecute the job (immediately) - depending upon the exception (see JobExecutionException).

Typically the best practice (even without chaining) is for the Job to catch and handle all exceptions/errors within itself. This is because it is extremely difficult for the scheduler to know what the right thing to do is. A quite common approach is to have the job log errors or send alerts in some other way, and then re-schedule itself to be triggered some time later (and exit without throwing an exception).

Thanks for sharing !

We are happy to announce an rich and intuitive GUI for Quartz Scheduler, that can manage triggers, jobs and exclusion calenders. Check out http://quartz-scheduler-gui.com.

Currently, we are running a beta program for a short duration. People willing to participate in beta and are willing to actively provide feedback would be rewarded with a free single application license absolutely free.

Karthik.
Quartz-Scheduler-GUI.com

Look at this Quartz GUI for JBoss:

http://code.google.com/p/automatic-service/

may it will be helpful.

karthikk wrote:

We are happy to announce an rich and intuitive GUI for Quartz Scheduler, that can manage triggers, jobs and exclusion calenders. Check out http://quartz-scheduler-gui.com.
Quartz-Scheduler-GUI.com

Has anyone tried this? I emailed them, but got no response. Is it stand-alone? What versions of Quartz can it manage?

I contacted Terracotta about the Quartz Manager. There's a reason they make you contact them for the price. I suspect that if I posted it here, they'd delete my post.

A simple stand-alone app to administer Quartz would be nice. Does anyone know of one that doesn't cost as much as a office full of laptops?

Hello,
If you need a decent Quartz scheduler management and monitoring GUI, then please check the QuartzDesk project that I am the founder of.

QuartzDesk is a self-hosted Java web application that provides many powerful features such as:

Support for Quartz 1.x and 2.x schedulers.

Persistent job execution history.

Support for all major databases.

Job execution log message capturing.

Notifications (email, all popular IM protocols, web-service).

Server-side JavaScript notification notification conditions.

Interactive execution statistics and charts.

REST API for job / trigger / scheduler monitoring.

QuartzAnywhere web-service to manage / monitor Quartz schedulers from applications.

and more

We offer a Lite (free) edition with limited functionality and Standard and Enterprise editions with 1 year support and free upgrades.

Best regards,
Jan Moravec

Here is an Open Source UI Quartz Manager

https://code.google.com/p/myschedule

JobServer has a robust web GUI admin for managing job schedules and overall job processing management.

Try this Web Based GUI built on Quartz API

http://ischeduler.blogspot.ae/