DataSource Configuration
If you're using JDBC-Jobstore, you will need a DataSource for its use (or two DataSources, if you're using JobStoreCMT).
DataSources can be configured in three ways:
1. All pool properties specified in the quartz.properties file, so that Quartz can create the DataSource itself.
2. The JNDI location of an application server managed DataSource can be specified, so that Quartz can use it.
3. Custom defined org.quartz.utils.ConnectionProvider implementations .
It is recommended that your DataSource max connection size be configured to be at least the number of worker threads in the thread pool plus three. You may need additional connections if your application is also making frequent calls to the scheduler API. If you are using JobStoreCMT, the non-managed DataSource should have a max connection size of at least four.
Each DataSource you define (typically one or two) must be given a name, and the properties you define for each must contain that name. The DataSource’s "NAME" can be anything you want, and has no meaning other than being able to identify it when it is assigned to the JDBCJobStore.