Configuration of Quartz is typically done through the use of a properties file, in conjunction with the use of
StdSchedulerFactory (which consumes the configuration file and instantiates a scheduler).
By default, StdSchedulerFactory load a properties file named "quartz.properties" from the 'current working directory'.
If that fails, then the "quartz.properties" file located (as a resource) in the org/quartz package is loaded. If you
wish to use a file other than these defaults, you must define the system property 'org.quartz.properties' to point to
the file you want.
Alternatively, you can explicitly initialize the factory by calling one of the initialize(xx) methods before
calling getScheduler() on the StdSchedulerFactory.
Instances of the specified JobStore, ThreadPool, and other SPI classes will be created by name, and then any
additional properties specified for them in the config file will be set on the instance by calling an equivalent 'set'
method. For example if the properties file contains the property 'org.quartz.jobStore.myProp = 10' then after the
JobStore class has been instantiated, the method 'setMyProp()' will be called on it. Type conversion to primitive
Java types (int, long, float, double, boolean, and String) are performed before calling the property's setter
One property can reference another property's value by specifying a value following the convention of
"$@other.property.name", for example, to reference the scheduler's instance name as the value for some other property,
you would use "$@org.quartz.scheduler.instanceName".
The properties for configuring various aspect of a scheduler are described in these sub-documents: