Exclusive updates on:

Quartz 2.0 Supports Fluent Configuration API and Monitoring of Job Scheduling

by Srini Penchikala on Apr 23, 2011 |

The latest version of open source job scheduler Quartz supports fluent configuration API and monitoring and management of job scheduling actions. Terracotta recently announced the release of version 2.0 of the scheduler framework.

The new version also offers two commercial modules - Quartz Manager which provides a GUI for monitoring and management, and Quartz Where which can be used to control where jobs are executed based on machine name or resources. The new features in the latest version fall into three categories:

Quartz Scheduler:
The new version of the open source Quartz library features a feature-rich API and new DSL/builder-based API for construction of Jobs and Triggers. It also comes with some performance improvements that speed up the job processing.

Quartz Manager:
Quartz Manager offers real-time monitoring and management for the Quartz scheduler product. Its user interface can be used to:

Gain visibility into job schedules, status and activity
Add or modify scheduling information
Manage multiple instances of Quartz Scheduler through a single interface
Perform ongoing management of job scheduling and execution tasks

Quartz Where:
Quartz Where is part of the commercial Quartz Scheduler. Built on the Terracotta platform, it allows users to direct jobs to specific machines, or to any machine with specific available resources which helps in distributed, heterogeneous clusters with large numbers of mission critical jobs. This enables the management of increasing workloads in traditional data center to control where jobs are executed based on machine name (user-defined node or node group) or machine resources (RAM, CPU or OS).

Terracotta also released back in February, an extension to Ehcache product called Ehcache Search that can be used to query, search and analyze in-memory data. The enterprise version of this feature, which requires Enterprise Ehcache EX or FX, is used to search across a distributed cache.