It is important to know that the scheduler uses this database for storing and running tasks. The performance of schedulers is ultimately limited by the performance of the database. If you need more tasks per second, you can run the scheduler daemons on larger systems or you can use clusters for the session beans used by the tasks. Eventually, however, the task database becomes saturated and you then need a larger or better-tuned database system.
Multiple applications can share a scheduler database. This sharing can lower the cost of administering scheduler databases.
The scheduler requires a database, a JDBC provider, and a data source.