Before you begin
Your database system must be installed and available.
It is important to realize that the scheduler uses this database for storing tasks and then executing them. The performance of the scheduler 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 the scheduler database.
Why and when to perform this task
The scheduler requires a database, a Java Database Connectivity (JDBC) provider and a data source.Steps for this task