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

This article mainly explains "what are the functions of QuartzNet". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the functions of QuartzNet"?

Other features of Quartz.Net

Quartz is built in a modular manner, so to make it work, several components need to be "spliced" together. Fortunately, there are some assistants who can achieve this goal.

The main components that need to be configured before Quartz can complete its work are:

1), ThreadPool

2), JobStore

3), data source (if necessary)

4), the scheduler itself

The thread pool has changed a lot since the introduction of task-based jobs. More TODO documentation

JobStores and DataSrouces are discussed in lesson 9 of this tutorial. It's worth noting that all JobStores implement the IJobStore interface-if one of the bundled JobStore doesn't meet your needs, you can create your own.

Finally, you need to create an instance of Scheduler. You need to specify a name for the Scheduler itself and give it to the instances of JobStore and ThreadPool.

1 、 StdSchedulerFactory

StdSchedulerFactory is the implementation of the ISchedulerFactory interface. It uses a set of properties (NameValueCollection) to create and initialize the Quartz Scheduler. These properties are usually stored in and loaded from the file, but can also be created by the program and passed directly to the factory. Simply call getScheduler () on the factory class instance to generate the scheduler, initialize it (and its ThreadPool,JobStore and DataSources), and return a handle to its public interface.

There are some sample configurations (including descriptions of properties) in the "docs / config" directory of the Quartz distribution. You can find the complete documentation in the configuration manual under the reference section of the Quartz documentation.

2 、 DirectSchedulerFactory

DirectSchedulerFactory is another SchedulerFactory implementation. It is very useful for those who want to create Scheduler instances in a more programmatic manner. It is generally discouraged for the following reasons: (1) it requires users to better understand what they are doing, and (2) it does not allow declarative configuration-or, in other words, you end up hardcoding all settings for the scheduler.

3 、 Logging

Quartz.NET uses the LibLob library to meet all its logging needs. Quartz doesn't generate a lot of log information-- it usually just generates some information during initialization, and then only messages about serious problems during Jobs execution. In order to "optimize" logging settings (such as output volume and output location), you need to actually configure the logging framework of your choice, because LibLog mainly delegates work to more mature logging frameworks, such as log4net, serilog, and so on.

4. Advanced (enterprise) functions

Clustering: clusters are currently only available for AdoJobstore (JobStoreTX). Features include load balancing and job failover (if the JobDetail request recovery flag is set to true).

Enable clustering by setting the quartz.jobStore.clustered property to true. Each instance in the cluster should use the same copy of the quartz property. The exception is to use the same property, with the following allowed exceptions: different thread pool sizes, and different values for the "quartz.scheduler.instanceId" property. Each node in the cluster must have a unique instanceId, which can be easily done by placing "AUTO" as the value of this attribute (no different properties files are required).

Never run clusters on different machines unless their clocks are synchronized using some form of time synchronization service (daemon), which runs regularly (clocks must be within each other's seconds). If you are not familiar with how to do this, visit http://www.boulder.nist.gov/timefreq/service/its.htm.

Never start a non-clustered instance against the same set of tables running any other instance. You may receive serious data corruption and will definitely experience abnormal behavior.

5. Other functions of Quartz.Net

1), Plug-Ins (plug-in)

Quartz provides an interface (ISchedulerPlugin) for inserting additional functionality.

Plug-ins that come with Quartz can be found in the Quartz.Plugins namespace to provide a variety of practical functions. The functions they provide include automatically scheduling jobs when the scheduler starts, recording job history and triggering events, and ensuring that the scheduler closes cleanly when the virtual machine exits.

2), JobFactory

When a trigger is triggered, the Job associated with it is instantiated through the JobFactory configured on the Scheduler. The default JobFactory simply activates a new instance of the job class. You may want to create your own JobFactory implementation to accomplish things such as having your application's IoC or DI container generate / initialize job instances.

3), 'Factory-Shipped' Jobs (some useful tasks pre-installed in the factory)

Quartz also provides a number of utilities that you can use in your applications to perform operations such as sending e-mail and calling remote objects. You can find these jobs out of the box in the Quartz.Jobs namespace.

Thank you for your reading, these are the contents of "what are the functions of QuartzNet". After the study of this article, I believe you have a deeper understanding of what the functions of QuartzNet are, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.