Note | ||
---|---|---|
| ||
This site is in the process of being reviewed and updated. |
Introduction
There is a need to schedule events and tasks within the server. We will use Quartz to do this.
...
Note |
---|
Don't forget to parameterize access to start and stop times for cron based triggers. |
Note | ||
---|---|---|
| ||
Quartz internally stores a lot more information related to the created jobs and triggers. One way to achieve LDAP store for quartz is to expose the minimal and required information as entries from the custom store which holds the original data-structures used by quartz in some sort of serialized form. This frees us from representing and maintaining all the relational aspects of quartz schema in LDAP at the same time allowing to edit the job/trigger configuration through LDAP entries. One other feature that may be feasible is to create a new job/trigger on the fly by including a beanshell script submitted through the client. |
Adding New Job Entries to Scheduler
...
The currently running jobs should also be displayed under the configuration entry for the scheduler within the ou=system area of the server.
Quartz RDBMS Schema
All tables' description - quartz-jdbcstore-tables-with-allcolumns.pdf
ER diagram of the quartz's RDBS schema - quartz-jdbcstore-er-diagram.pdf
Quartz Schema
See Quartz Schema