转自： http://blog.csdn.net/hailongge/article/details/4930884
配置主要调度设置
These properties configure the identification of the scheduler, and various other 'top level' settings.这些属性配置调度程序确定，以及其他各种'顶级'的设置。
| Property Name属性名称 | Required必需的 | Type类型 | Default Value默认值 |
| org.quartz.scheduler.instanceNameorg.quartz.scheduler.instanceName | no否 | string字符串 | 'QuartzScheduler' 'QuartzScheduler' |
| org.quartz.scheduler.instanceId org.quartz.scheduler.instanceId | no否 | string字符串 | 'NON_CLUSTERED' 'NON_CLUSTERED' |
| org.quartz.scheduler.instanceIdGenerator.classorg.quartz.scheduler.instanceIdGenerator.class | no否 | string (class name)字符串（类名） | org.quartz.simpl.SimpleInstanceIdGeneratororg.quartz.simpl.SimpleInstanceIdGenerator |
| org.quartz.scheduler.threadNameorg.quartz.scheduler.threadName | no否 | string字符串 | instanceName + '_QuartzSchedulerThread'实例名+'_QuartzSchedulerThread' |
| org.quartz.scheduler.makeSchedulerThreadDaemonorg.quartz.scheduler.makeSchedulerThreadDaemon | no否 | boolean布尔 | false假 |
| org.quartz.scheduler.threadsInheritContextClassLoaderOfInitializerorg.quartz.scheduler.threadsInheritContextClassLoaderOfInitializer | no否 | boolean布尔 | false假 |
| org.quartz.scheduler.idleWaitTimeorg.quartz.scheduler.idleWaitTime | no否 | long长的 | 30000 30000 |
| org.quartz.scheduler.dbFailureRetryIntervalorg.quartz.scheduler.dbFailureRetryInterval | no否 | long长的 | 15000 15000 |
| org.quartz.scheduler.classLoadHelper.classorg.quartz.scheduler.classLoadHelper.class | no否 | string (class name)字符串（类名） | org.quartz.simpl.CascadingClassLoadHelperorg.quartz.simpl.CascadingClassLoadHelper |
| org.quartz.scheduler.jobFactory.classorg.quartz.scheduler.jobFactory.class | no否 | string (class name)字符串（类名） | org.quartz.simpl.SimpleJobFactoryorg.quartz.simpl.SimpleJobFactory |
| org.quartz.context.key.SOME_KEYorg.quartz.context.key.SOME_KEY | no否 | string字符串 | none毫无 |
| org.quartz.scheduler.userTransactionURLorg.quartz.scheduler.userTransactionURL | no否 | string (url)字符串（网址） | 'java:comp/UserTransaction'的Java：比较/ UserTransaction的' |
| org.quartz.scheduler.wrapJobExecutionInUserTransactionorg.quartz.scheduler.wrapJobExecutionInUserTransaction | no否 | booelanbooelan | false假 |
org.quartz.scheduler.instanceName org.quartz.scheduler.instanceName
Can be any string, and the value has no meaning to the scheduler itself - but rather serves as a mechanism for client code to distinguish schedulers when multiple instances are used within the same program.可以是任何字符串，值没有任何意义的调度本身-而是作为一个客户端代码机制，可分辨的多个实例在同一程序中使用的调度。 If you are using the clustering features, you must use the same name for every instance in the cluster that is 'logically' the same Scheduler.如果您使用的是集群功能，您必须使用每个群集'逻辑'同一调度实例相同的名称。
org.quartz.scheduler.instanceId org.quartz.scheduler.instanceId
Can be any string, but must be unique for all schedulers working as if they are the same 'logical' Scheduler within a cluster.可以是任何字符串，但必须是唯一的所有工作组内，好像他们是一样的'逻辑'调度调度。 You may use the value "AUTO" as the instanceId if you wish the Id to be generated for you.您可以使用作为instanceId的值为“自动”如果你希望ID来为您生成。
org.quartz.scheduler.instanceIdGenerator.class org.quartz.scheduler.instanceIdGenerator.class
Only used if org.quartz.scheduler.instanceId is set to "AUTO".如果只使用org.quartz.scheduler.instanceId设置为“自动”。 Defaults to "org.quartz.simpl.SimpleInstanceIdGenerator", which generates an instance id based upon host name and time stamp.以“org.quartz.simpl.SimpleInstanceIdGenerator”默认，生成一个实例ID基于主机名称和时间戳。
org.quartz.scheduler.threadName org.quartz.scheduler.threadName
Can be any String that is a valid name for a java thread.可以是任何字符串这是一个Java线程有效的名称。 If this property is not specified, the thread will receive the scheduler's name ("org.quartz.scheduler.instanceName") plus an the appended string '_QuartzSchedulerThread'.如果这个属性没有指定，该线程将收到调度的名称（“org.quartz.scheduler.instanceName”）加一的附加字符串'_QuartzSchedulerThread'。
org.quartz.scheduler.makeSchedulerThreadDaemonorg.quartz.scheduler.makeSchedulerThreadDaemon
A boolean value ('true' or 'false') that specifies whether the main thread of the scheduler should be a daemon thread or not.一个布尔值（'真正的'或'假'），指定是否调度主线应该是一个守护线程与否。 See also theorg.quartz.scheduler.makeSchedulerThreadDaemon property for tuning the SimpleThreadPool if that is the thread pool implementation you are using (which is most likely the case).见也是微调SimpleThreadPool如果这是执行的线程池所使用org.quartz.scheduler.makeSchedulerThreadDaemon财产（这是最有可能的情况）。
org.quartz.scheduler.threadsInheritContextClassLoaderOfInitializerorg.quartz.scheduler.threadsInheritContextClassLoaderOfInitializer
A boolean value ('true' or 'false') that specifies whether the threads spawned by Quartz will inherit the context ClassLoader of the initializing thread (thread that initializes the Quartz instance).一个布尔值（'真正的'或'假'），指定由石英产生的线程将继承范围内的初始化线程的ClassLoader（线程初始化石英实例）。 This will affect Quartz main scheduling thread, JDBCJobStore's misfire handling thread (if JDBCJobStore is used), cluster recovery thread (if clustering is used), and threads in SimpleThreadPool (if SimpleThreadPool is used).这将影响到石英主要调度线程，JDBCJobStore的失火处理线程（如果JDBCJobStore使用），集群恢复线程（如果使用群集），并在SimpleThreadPool线程（如果SimpleThreadPool使用）。 Setting this value to 'true' may help with class loading, JNDI look-ups, and other issues related to using Quartz within an application server.将此值设置为'真正的'可以帮助类加载，JNDI的查找窗口，并在应用服务器与使用石英其他问题。
org.quartz.scheduler.idleWaitTime org.quartz.scheduler.idleWaitTime
Is the amount of time in milliseconds that the scheduler will wait before re-queries for available triggers when the scheduler is otherwise idle.就是时间以毫秒为单位的调度会等待重新可用时，查询触发调度闲置。 Normally you should not have to 'tune' this parameter, unless you're using XA transactions, and are having problems with delayed firings of triggers that should fire immediately.通常你不应该'调整'这个参数，除非你使用XA事务，并同时与触发延迟发射的问题，应立即火。
org.quartz.scheduler.dbFailureRetryInterval org.quartz.scheduler.dbFailureRetryInterval
Is the amount of time in milliseconds that the scheduler will wait between re-tries when it has detected a loss of connectivity within the JobStore (eg to the database).就是时间以毫秒为单位的调度会等待重新之间的数额时，它试图发现一个连接在JobStore损失（如数据库）。 This parameter is obviously not very meaningful when using RamJobStore.这个参数是非常有意义的显然不是在使用RamJobStore。
org.quartz.scheduler.classLoadHelper.class org.quartz.scheduler.classLoadHelper.class
Defaults to the most robust approach, which is to use the "org.quartz.simpl.CascadingClassLoadHelper" class - which in turn uses every other ClassLoadHelper class until one works.最有力的做法，即使用“org.quartz.simpl.CascadingClassLoadHelper”类-这反过来使用作品之一，直到所有其他ClassLoadHelper类默认值。 You should probably not find the need to specify any other class for this property, though strange things seem to happen within application servers.你也许应该找不到需要指定此属性的任何其他类，但奇怪的事情发生，似乎在应用服务器。 All of the current possible ClassLoadHelper implementation can be found in theorg.quartz.simpl package.目前可能ClassLoadHelper执行情况的所有可以找到的org.quartz.simpl包。
org.quartz.scheduler.jobFactory.class org.quartz.scheduler.jobFactory.class
The class name of the JobFactory to use.该JobFactory类的名称。 The default is 'org.quartz.simpl.SimpleJobFactory', you may like to try 'org.quartz.simpl.PropertySettingJobFactory'.默认值为'org.quartz.simpl.SimpleJobFactory'，你可以尝试'org.quartz.simpl.PropertySettingJobFactory'。 A JobFatcory is responsible for producing instances of JobClasses. SimpleJobFactory simply calls newInstance() on the class.阿JobFatcory负责生产JobClasses实例。SimpleJobFactory只需调用newInstance（）方法的类。PropertySettingJobFactory does as well, but also reflectively sets the job's bean properties using the contents of the JobDataMap. PropertySettingJobFactory不为好，但也沉思设置作业的bean属性使用该JobDataMap的内容。
org.quartz.context.key.SOME_KEY org.quartz.context.key.SOME_KEY
Represent a name-value pair that will be placed into the "scheduler context" as strings.代表1名值对将被放入“调度范围内为字符串”。 (see Scheduler.getContext()). So for example, the setting "org.quartz.context.key.MyKey = MyValue" would perform the equivalent of scheduler.getContext().put("MyKey", "MyValue"). （见Scheduler.getContext（））。因此，例如，设置“org.quartz.context.key.MyKey = MyValue”将执行的scheduler.getContext当量（）。放（“MyKey”，“MyValue”）。
The Transaction-Related properties should be left out of the config file unless you are using JTA transactions.该交易相关的属性应被排除在配置文件，除非您正在使用JTA事务。
org.quartz.scheduler.userTransactionURL org.quartz.scheduler.userTransactionURL
Should be set to the JNDI URL at which Quartz can locate the Application Server's UserTransaction manager.应设置为JNDI的网址上可以找到的石英应用服务器的UserTransaction的经理。 The default value (if not specified) is "java:comp/UserTransaction" - which works for almost all Application Servers.默认值（如果未指定）是“爪哇：比较/ UserTransaction的” -这几乎所有的应用服务器工程。 Websphere users may need to set this property to "jta/usertransaction". WebSphere用户可能需要将该属性设置为“犹太电讯/ UserTransaction的”。 This is only used if Quartz is configured to use JobStoreCMT, andorg.quartz.scheduler.wrapJobExecutionInUserTransaction is set to true.这仅仅是如果使用石英配置为使用JobStoreCMT，并org.quartz.scheduler.wrapJobExecutionInUserTransaction设置为true。
org.quartz.scheduler.wrapJobExecutionInUserTransactionorg.quartz.scheduler.wrapJobExecutionInUserTransaction
Should be set to "true" if you want Quartz to start a UserTransaction before calling execute on your job.应设置为“true”如果你想石英开始执行之前调用在你的工作一个UserTransaction。 The Tx will commit after the job's execute method completes, and after the JobDataMap is updated (if it is a StatefulJob).在得克萨斯州后，将提交作业的执行方法完成，并经JobDataMap更新（如果它是一个StatefulJob）。 The default value is "false".默认值为“false”。
配置线程池设置
| Property Name属性名称 | Required必需的 | Type类型 | Default Value默认值 |
| org.quartz.threadPool.classorg.quartz.threadPool.class | yes是 | string (clas name)字符串（clas名称） | null空 |
| org.quartz.threadPool.threadCountorg.quartz.threadPool.threadCount | yes是 | int廉政 | -1 -1 |
| org.quartz.threadPool.threadPriorityorg.quartz.threadPool.threadPriority | no否 | int廉政 | Thread.NORM_PRIORITY (5)Thread.NORM_PRIORITY（5） |
org.quartz.threadPool.class org.quartz.threadPool.class
Is the name of the ThreadPool implementation you wish to use.是执行的线程池您希望使用的名称。 The threadpool that ships with Quartz is "org.quartz.simpl.SimpleThreadPool", and should meet the needs of nearly every user. ThreadPool中与石英船只是“org.quartz.simpl.SimpleThreadPool”，并应符合几乎所有用户的需求。It has very simple behavior and is very well tested.这是一个非常简单的行为，是非常行之有效的制度。 It provides a fixed-size pool of threads that 'live' the lifetime of the Scheduler.它提供了一个线程固定大小的池'活'的一生全部的调度。
org.quartz.threadPool.threadCount org.quartz.threadPool.threadCount
Can be any positive integer, although you should realize that only numbers between 1 and 100 are very practical.可以是任何正整数，虽然你应该明白，1到100之间只有数字，是很实际。 This is the number of threads that are available for concurrent execution of jobs.这是为线程并发执行的职位数目。 If you only have a few jobs that fire a few times a day, then 1 thread is plenty!如果你只有一个火警的一天数次，然后一线程数是很多的工作！ If you have tens of thousands of jobs, with many firing every minute, then you probably want a thread count more like 50 or 100 (this highly depends on the nature of the work that your jobs perform, and your systems resources!).如果你有数以万计的就业机会，许多射击每分钟，那么你可能一个线程数更象50年或100希望（这个高度取决于你的工作性质，工作表现，和你的系统资源！）。
org.quartz.threadPool.threadPriority org.quartz.threadPool.threadPriority
Can be any int between Thread.MIN_PRIORITY (which is 1) and Thread.MAX_PRIORITY (which is 10).可以是任何廉政之间Thread.MIN_PRIORITY（这是1）和Thread.MAX_PRIORITY（即10）。 The default isThread.NORM_PRIORITY (5).默认值为Thread.NORM_PRIORITY（5）。
SimpleThreadPool-Specific Properties SimpleThreadPool特定的属性
| Property Name属性名称 | Required必需的 | Type类型 | Default Value默认值 |
| org.quartz.threadPool.makeThreadsDaemonsorg.quartz.threadPool.makeThreadsDaemons | no否 | boolean布尔 | false假 |
| org.quartz.threadPool.threadsInheritGroupOfInitializingThreadorg.quartz.threadPool.threadsInheritGroupOfInitializingThread | no否 | boolean布尔 | true正确的 |
| org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThreadorg.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread | no否 | boolean布尔 | false假 |
org.quartz.threadPool.makeThreadsDaemons org.quartz.threadPool.makeThreadsDaemons
Can be set to "true" to have the threads in the pool created as daemon threads.可以设置为“true”将在为守护线程池中创建的线程。 Default is "false".默认是“假”。 See also theorg.quartz.scheduler.makeSchedulerThreadDaemon property.另见org.quartz.scheduler.makeSchedulerThreadDaemon财产。
org.quartz.threadPool.threadsInheritGroupOfInitializingThreadorg.quartz.threadPool.threadsInheritGroupOfInitializingThread
Can be "true" or "false", and defaults to true.可以是“真”或“假”，并默认为true。
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThreadorg.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread
Can be "true" or "false", and defaults to false.可以是“真”或“假”，并默认为false。
Custom ThreadPools自定义ThreadPools
If you use your own implementation of a thread pool, you can have properties set on it reflectively simply by naming the property as thus:如果您使用的线程池的实现，您可以设置它沉思来命名的财产，因此根本属性：
Setting Properties on a Custom ThreadPool设置属性自定义线程池
org.quartz.threadPool.class = com.mycompany.goo.FooThreadPool org.quartz.threadPool.class = com.mycompany.goo.FooThreadPool org.quartz.threadPool.somePropOfFooThreadPool = someValueorg.quartz.threadPool.somePropOfFooThreadPool = someValue
配置全球听众
Global listeners can be instantiated and configured by StdSchedulerFactory, or your application can do it itself at runtime, and then register the listeners with the scheduler.全球听众可以实例化和StdSchedulerFactory，或者您的应用程序配置在运行时可以做它自己，然后注册与调度的听众。 "Global" listeners listen to the events of every job/trigger rather than just the jobs/triggers that directly reference them. “环球”听众听取每个作业的事件/触发，而不仅仅是职位/触发器直接引用它们。
Configuring listeners through the configuration file consists of giving then a name, and then specifying the class name, and any other properties to be set on the instance.通过配置文件配置听众将包括在实例上设置然后给予一个名称，然后指定类名，以及任何其他属性。 The class must have a no-arg constructor, and the properties are set reflectively.这个类必须有一个无参数的构造函数，以及属性设置沉思。 Only primitive data type values (including Strings) are supported.只有原始数据类型的值（包括弦乐）的支持。
Thus, the general pattern for defining a "global" TriggerListener is:因此，界定“全球”TriggerListener普遍的模式：
Configuring a Global TriggerListener配置全球TriggerListener
org.quartz.triggerListener.NAME.class = com.foo.MyListenerClassorg.quartz.triggerListener.NAME.class = com.foo.MyListenerClassorg.quartz.triggerListener.NAME.propName = propValue org.quartz.triggerListener.NAME.propName = propValue org.quartz.triggerListener.NAME.prop2Name = prop2Valueorg.quartz.triggerListener.NAME.prop2Name = prop2Value
And the general pattern for defining a "global" JobListener is:和界定“全球”JobListener普遍的模式：
Configuring a Global JobListener配置全球JobListener
org.quartz.jobListener.NAME.class = com.foo.MyListenerClass org.quartz.jobListener.NAME.propName = propValue org.quartz.jobListener.NAME.prop2Name = prop2Value org.quartz.jobListener.NAME.class = com.foo.MyListenerClass org.quartz.jobListener.NAME.propName = propValue org.quartz.jobListener.NAME.prop2Name = prop2Value
配置调度插件
Like listeners configuring plugins through the configuration file consists of giving then a name, and then specifying the class name, and any other properties to be set on the instance.配置一样，通过配置文件插件听众将包括在实例上设置然后给予一个名称，然后指定类名，以及任何其他属性。 The class must have a no-arg constructor, and the properties are set reflectively.这个类必须有一个无参数的构造函数，以及属性设置沉思。Only primitive data type values (including Strings) are supported.只有原始数据类型的值（包括弦乐）的支持。
Thus, the general pattern for defining a plug-in is:因此，定义在插件的一般模式是：
Configuring a Plugin配置插件
org.quartz.plugin.NAME.class = com.foo.MyPluginClass org.quartz.plugin.NAME.class = com.foo.MyPluginClass org.quartz.plugin.NAME.propName = propValue org.quartz.plugin.NAME.propName = propValue org.quartz.plugin.NAME.prop2Name = prop2Value org.quartz.plugin.NAME.prop2Name = prop2Value
There are several Plugins that come with Quartz, that can be found in the org.quartz.plugins package (and subpackages).有几个插件，与石英来，可以在org.quartz.plugins包（及其子包中）。 Example of configuring a few of them are as follows:配置一个其中一些例子如下：
Sample configuration of Logging Trigger History Plugin样品配置的历史记录插件触发
The logging trigger history plugin catches trigger events (it is also a trigger listener) and logs then with Jakarta Commons-Logging.历史的记录插件触发捕捉触发事件（这也是触发侦听器），并记录与雅加达风景当时的记录。 See the class's JavaDoc for a list of all the possible parameters.见所有可能的参数的列表类的Javadoc。
Sample configuration of Logging Trigger History Plugin样品配置的历史记录插件触发
org.quartz.plugin.triggHistory.class = / org.quartz.plugin.triggHistory.class = /org.quartz.plugins.history.LoggingTriggerHistoryPluginorg.quartz.plugins.history.LoggingTriggerHistoryPluginorg.quartz.plugin.triggHistory.triggerFiredMessage = /org.quartz.plugin.triggHistory.triggerFiredMessage = / Trigger /{1/}./{0/} fired job /{6/}./{5/} at: /{4, date, HH:mm:ss MM/dd/yyyy}触发/（1 /）。/（0 /）发射工作/（6 /）。/（5 /）在：/（4，日期，小时：mm：ss的月/日/年） org.quartz.plugin.triggHistory.triggerCompleteMessage = /org.quartz.plugin.triggHistory.triggerCompleteMessage = / Trigger /{1/}./{0/} completed firing job /{6/}./{5/} at /{4, date, HH:mm:ss MM/dd/yyyy/}.触发/（1 /）。/（0 /）完成发射工作/（6 /）。/（5 /）在/（4，日期，小时：mm：ss的月/日/年/）。
Sample configuration of Job Initialization Plugin样本配置插件的初始化工作
Job initialization plugin reads a set of jobs and triggers from an XML file, and adds them to the scheduler during initialization.插件读取初始化工作的职位设置和从XML文件触发，并增加他们在初始化期间的调度。 See the class's JavaDoc for more details.有关详细信息，请参阅类的Javadoc。
Sample configuration of JobInitializationPlugin 样品配置JobInitializationPlugin
org.quartz.plugin.jobInitializer.class = / org.quartz.plugin.jobInitializer.class = /org.quartz.plugins.xml.JobInitializationPlugin org.quartz.plugins.xml.JobInitializationPluginorg.quartz.plugin.jobInitializer.fileName = / org.quartz.plugin.jobInitializer.fileName = /data/my_job_data.xml数据/ my_job_data.xml org.quartz.plugin.jobInitializer.overWriteExistingJobs =false org.quartz.plugin.jobInitializer.overWriteExistingJobs = 假org.quartz.plugin.jobInitializer.failOnFileNotFound = trueorg.quartz.plugin.jobInitializer.failOnFileNotFound = 真
Sample configuration of Shutdown Hook Plugin样品配置关闭挂钩插件
The shutdown-hook plugin catches the event of the JVM terminating, and calls shutdown on the scheduler.关机钩插件抓住了JVM的活动结束，并呼吁调度关机。
Sample configuration of ShutdownHookPlugin 样品配置ShutdownHookPlugin
org.quartz.plugin.shutdownhook.class = / org.quartz.plugin.shutdownhook.class = /org.quartz.plugins.management.ShutdownHookPlugin org.quartz.plugins.management.ShutdownHookPluginorg.quartz.plugin.shutdownhook.cleanShutdown = true org.quartz.plugin.shutdownhook.cleanShutdown =真
配置调度RMI的设置
None of the primary properties are required, and all have 'reasonable' defaults.主属性都不是必需的，都有合理的'默认值。 When using Quartz via RMI, you need to start an instance of Quartz with it configured to "export" its services via RMI.当通过RMI使用石英，你需要开始使用它的石英实例配置为“出口”通过RMI的服务。 You then create clients to the server by configuring a Quartz scheduler to "proxy" its work to the server.然后，创建客户端的服务器配置石英调度“代理”，其工作的服务器。
Some users experience problems with class availability (namely Job classes) between the client and server.一些一流的可用性（即就业班之间的客户端和服务器）的用户遇到问题。 To work through these problems you'll need an understanding of RMI's "codebase" and RMI security managers.若要通过这些问题，你需要一个RMI公司的“代码库”和RMI安全管理的认识。 You may find these resources to be useful:您可能会发现这些资源是有用的：
An excellent description of RMI and codebase: http://www.kedwards.com/jini/codebase.html . RMI和一个代码库很好的描述：http://www.kedwards.com/jini/codebase.html。 One of the important points is to realize that "codebase" is used by the client!重要的一点是要认识到“代码库”是由客户端使用的！
Quick info about security managers:http://gethelp.devx.com/techtips/java_pro/10MinuteSolutions/10min0500.asp快速信息有关安全管理人员：http://gethelp.devx.com/techtips/java_pro/10MinuteSolutions/10min0500.asp
And finally from the java API docs, read the docs for the RMISecurityManager并宣读终于从Java API文档，为RMISecurityManager的文档
http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/RMISecurityManager.htmlhttp://java.sun.com/j2se/1.4.2/docs/api/java/rmi/RMISecurityManager.html
| Property Name属性名称 | Required必需的 | Default Value默认值 |
| org.quartz.scheduler.rmi.export org.quartz.scheduler.rmi.export | no否 | false假 |
| org.quartz.scheduler.rmi.registryHostorg.quartz.scheduler.rmi.registryHost | no否 | 'localhost' '本地主机' |
| org.quartz.scheduler.rmi.registryPortorg.quartz.scheduler.rmi.registryPort | no否 | 1099 1099 |
| org.quartz.scheduler.rmi.createRegistryorg.quartz.scheduler.rmi.createRegistry | no否 | 'never' '没有' |
| org.quartz.scheduler.rmi.serverPort org.quartz.scheduler.rmi.serverPort | no否 | random随机 |
| org.quartz.scheduler.rmi.proxy org.quartz.scheduler.rmi.proxy | no否 | false假 |
org.quartz.scheduler.rmi.export org.quartz.scheduler.rmi.export
If you want the Quartz Scheduler to export itself via RMI as a server then set the 'rmi.export' flag to true.如果您希望石英调度通过RMI出口作为服务器，然后把'rmi.export'标志真实本身。
org.quartz.scheduler.rmi.registryHost org.quartz.scheduler.rmi.registryHost
The host at which the RMI Registry can be found (often 'localhost').在该RMI注册可以找到主机（通常'本地主机'）。
org.quartz.scheduler.rmi.registryPort org.quartz.scheduler.rmi.registryPort
The port on which the RMI Registry is listening (usually 1099).的端口RMI注册是听（通常是1099）。
org.quartz.scheduler.rmi.createRegistry org.quartz.scheduler.rmi.createRegistry
Set the 'rmi.createRegistry' flag according to how you want Quartz to cause the creation of an RMI Registry.设置'rmi.createRegistry'标志根据您要如何石英造成一个RMI注册成立。 Use "false" or "never" if you don't want Quartz to create a registry (eg if you already have an external registry running).使用“假”或“从不”，如果你不想石英创建注册表（例如，如果您已经有一个外部的注册表运行）。 Use "true" or "as_needed" if you want Quartz to first attempt to use an existing registry, and then fall back to creating one.使用“true”或“as_needed”如果你想石英首先尝试使用现有的注册表，然后回落到创建一个。 Use "always" if you want Quartz to attempt creating a Registry, and then fall back to using an existing one.使用“总是”如果你想石英试图建立一个注册表，然后回落至使用现有的1。 If a registry is created, it will be bound to port number in the given 'org.quartz.scheduler.rmi.registryPort' property, and 'org.quartz.rmi.registryHost' should be "localhost".如果创建一个注册表，它必将给定'org.quartz.scheduler.rmi.registryPort'属性的端口号，和'org.quartz.rmi.registryHost'应该是“本地主机”。
org.quartz.scheduler.rmi.serverPort org.quartz.scheduler.rmi.serverPort
The port on which the the Quartz Scheduler service will bind and listen for connections.在该端口的石英计划程序服务将绑定和侦听连接。 By default, the RMI service will 'randomly' select a port as the scheduler is bound to the RMI Registry.默认情况下，RMI服务的'随机选取一个调度端口绑定到RMI注册。
org.quartz.scheduler.rmi.proxy org.quartz.scheduler.rmi.proxy
If you want to connect to (use) a remotely served scheduler, then set the 'org.quartz.scheduler.rmi.proxy' flag to true. You must also then specify a host and port for the RMI Registry process - which is typically 'localhost' port 1099.如果你想连接到（使用）的远程服务调度程序，然后设置'org.quartz.scheduler.rmi.proxy'标志为true。然后，您还必须指定主机和RMI注册过程中的港口-通常是'本地主机'端口1099。
It does not make sense to specify a 'true' value for both 'org.quartz.scheduler.rmi.export' and 'org.quartz.scheduler.rmi.proxy' in the same config file - if you do, the 'export' option will be ignored.它没有意义的，同时指定'org.quartz.scheduler.rmi.export'和'org.quartz.scheduler.rmi.proxy在同一配置文件中'一'真正的'价值-如果你的'出口'选项将被忽略。 A value of 'false' for both 'export' and 'proxy' properties is of course valid, if you're not using Quartz via RMI.值为'假为'出口'和'代理'属性'，当然是有效的，如果你不通过RMI使用石英。
配置RAMJobStore
RAMJobStore is used to store scheduling information (job, triggers and calendars) within memory.RAMJobStore是用来存储调度信息（工作，触发器和日历在内存）。 RAMJobStore is fast and lightweight, but all scheduling information is lost when the process terminates. RAMJobStore速度快，重量轻，但所有的调度信息将丢失当进程终止。