Shulou(Shulou.com)06/03 Report--

This article mainly shows you the "sample analysis of Quartz.Net scheduling framework configuration", which is easy to understand and clear. I hope it can help you solve your doubts. Let the editor lead you to study and learn the article "sample Analysis of Quartz.Net scheduling Framework configuration".

File-based configuration

Take a look at the simple implementation code first.

Using System;using System.Collections.Generic;using System.Linq;using System.Text;using System.Threading;using Quartz;using Quartz.Impl;using Common.Logging;namespace Demo {class Program {static void Main (string [] args) {/ / First we must get a reference to a scheduler ISchedulerFactory sf = new StdSchedulerFactory (); IScheduler sched = sf.GetScheduler (); sched.Start (); sched.Shutdown (true);}

The code is simple, the basic quartz configuration in the configuration file, and how is the job,trigger information loaded? This process is the occurrence of IScheduler sched = sf.GetScheduler (); process, mainly reflected in the source code section

Public void Initialize () {/ / short-circuit if already initialized if (cfg! = null) {return;} if (initException! = null) {throw initException;} NameValueCollection props = (NameValueCollection) ConfigurationManager.GetSection ("quartz"); string requestedFile = Environment.GetEnvironmentVariable (PropertiesFile); string propFileName = requestedFile! = null & & requestedFile.Trim (). Length > 0? RequestedFile: "~ / quartz.config"; / / check for specials propFileName = FileUtil.ResolveFile (propFileName); if (props = = null & & File.Exists (propFileName)) {/ / file system try {PropertiesParser pp = PropertiesParser.ReadFromFileResource (propFileName); props = pp.UnderlyingProperties; Log.Info (string.Format ("Quartz.NET properties loaded from configuration file'{0}'", propFileName)) } catch (Exception ex) {Log.Error ("Could not load properties for Quartz from file {0}: {1}" .FormatInformations (propFileName, ex.Message), ex);} if (props = = null) {/ / read from assembly try {PropertiesParser pp = PropertiesParser.ReadFromEmbeddedAssemblyResource ("Quartz.quartz.config"); props = pp.UnderlyingProperties; Log.Info ("Default Quartz.NET properties loaded from embedded resource file") } catch (Exception ex) {Log.Error ("Could not load default properties for Quartz from Quartz assembly: {0}" .FormatInformations (ex.Message), ex);} if (props = = null) {throw new SchedulerConfigException (@ "Could not find configuration section from your application config or load default configuration from assembly.Please add configuration to your application config file to correctly initialize Quartz.");} Initialize (OverrideWithSysProps (props));}

According to the analysis of the above code, initialization first checks whether there is a configuration section node (app.config,web.config refers to config) in the system config, and if the system config has a quartz node, the configuration information here is loaded directly. If the system config does not have the basic configuration information of quartz, it will continue to look for the existence of the two configuration files quartz.config/Quartz.quartz.config, if so, load the configuration information, and if not, throw an initialization configuration exception.

And jobs.xml (scheduled tasks and triggers plugin node profile)

Plugin configuration in app.config/web.config

Point to plugin configuration in quartz.config (quartz.plugin.xml.type / quartz.plugin.xml.fileNames)

# You can configure your scheduler in either configuration section# or in quartz properties file# Configuration section has precedencequartz.scheduler.instanceName = ServerScheduler# configure thread pool infoquartz.threadPool.type = Quartz.Simpl.SimpleThreadPool Quartzquartz.threadPool.threadCount = 10quartz.threadPool.threadPriority = Normal#--*plugin configuration-- # job initialization plugin handles our xml reading, without it defaults are usedquartz.plugin.xml.type = Quartz.Plugin.Xml.XMLSchedulingDataProcessorPlugin Quartzquartz.plugin.xml.fileNames = ~ / quartz_jobs.xml# export this server to remoting contextquartz.scheduler.exporter.type = Quartz.Simpl.RemotingSchedulerExporter, Quartzquartz.scheduler.exporter.port = 555quartz.scheduler.exporter.bindName = QuartzSchedulerquartz.scheduler.exporter.channelType = tcpquartz.scheduler.exporter.channelName = httpQuartz

II. Code-based approach

This situation is achieved directly through code, as is the case with many official DEMO. Let's give an example.

Using System;using System.Collections.Generic;using System.Linq;using System.Text; using Quartz;using Quartz.Impl;using System.Threading;using Common.Logging;namespace Demo {class Program {static void Main (string [] args) {ILog log = LogManager.GetLogger (typeof (Demo.HelloJob)); log.Info ("- Initializing -") / / First we must get a reference to a scheduler ISchedulerFactory sf = new StdSchedulerFactory (); IScheduler sched = sf.GetScheduler (); log.Info ("- Initialization Complete -") / /-- add job and trigger / / computer a time that is on the next round minute DateTimeOffset runTime = DateBuilder.EvenMinuteDate (DateTimeOffset.UtcNow); log.Info ("- Scheduling Job -") / / define the job and tie it to our HelloJob class IJobDetail job = JobBuilder.Create () .WithIdentity ("job1", "group1") .build (); / / Trigger the job to run on the next round minute ITrigger trigger = TriggerBuilder.Create () .WithIdentity ("trigger1", "group1") .StartAt (runTime) .build (); / / Tell quartz to schedule the job using our trigger sched.ScheduleJob (job, trigger) Log.Info (string.Format ("{0} will run at: {1}", job.Key, runTime.ToString ("r")); / / Start up the scheduler (nothing can actually run until the / / scheduler has been started) sched.Start (); log.Info ("- Started Scheduler -"); / / wait long enough so that the scheduler as an opportunity to / / run the job! Log.Info ("- Waiting 65 seconds... -"); / / wait 65 seconds to show jobs Thread.Sleep (TimeSpan.FromSeconds (65)); / / shut down the scheduler log.Info ("-Shutting Down-"); sched.Shutdown (true); log.Info ("-Shutdown Complete-") }}}

In fact, the code way has been implemented with the configuration file mashup way. But this alignment is to load the job and trigger configuration through configuration association, and we have a third way to load the job and trigger configuration files ourselves.

Loading configuration files manually

Using System;using System.Collections.Generic;using System.Linq;using System.Text; using Quartz;using Quartz.Xml;using Quartz.Impl;using Quartz.Simpl;using System.Threading;using Common.Logging;using System.IO;namespace Demo {class Program {static void Main (string [] args) {XMLSchedulingDataProcessor processor = new XMLSchedulingDataProcessor (new SimpleTypeLoadHelper ()); ISchedulerFactory sf = new StdSchedulerFactory (); IScheduler scheduler = sf.GetScheduler (); Stream s = new StreamReader ("~ / quartz.xml"). BaseStream Processor.ProcessStream (s, null); processor.ScheduleJobs (scheduler); scheduler.Start (); scheduler.Shutdown ();}

Or like this.

Using System.Text; using Quartz;using Quartz.Xml;using Quartz.Impl;using Quartz.Simpl;using System.Threading;using Common.Logging;using System.IO;namespace Demo {class Program {static void Main (string [] args) {XMLSchedulingDataProcessor processor = new XMLSchedulingDataProcessor (new SimpleTypeLoadHelper ()); ISchedulerFactory sf = new StdSchedulerFactory (); IScheduler scheduler = sf.GetScheduler (); processor.ProcessFileAndScheduleJobs ("~ / quartz.xml", scheduler); scheduler.Start (); scheduler.Shutdown ();}

At present, according to the source code analysis, there are roughly these configuration methods, which are very flexible and can be combined arbitrarily. About the use of quartz source code is very detailed, and the garden has a large number of learning articles.

Remember that the configuration of quartz is read first by app.config/web.config-> quartz.config/Quartz.quartz.config-> quartz_jobs.xml.

By coding, we can change the direction of quartz_jobs.xml, that is, our newly named xml file.

(the default quartz_jobs.xml is specified when XMLSchedulingDataProcessor.QuartzXmlFileName = "quartz_jobs.xml")

Method one is to point to the specified jobs.xml through the quartz node / quartz.config.

Second, load the specified jobs.xml through XMLSchedulingDataProcessor

The above is all the contents of the article "sample Analysis of Quartz.Net scheduling Framework configuration". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.