Click Forensics, the company I work for, has graciously allowed me to open source the code to a GUI for Quartz.net. The latest code is currently available on github. We have been using Quartz.net for over a year and we use this tool to manage our schedulers. The application is written in C#, using windows forms and is targeting .
Continue ReadingThis post will describe how to create a Quartz.Net job listener. As an example, we will write a job history listener that will log job start and end times to a database. Creating the Job ListenerTo create a job listener, we need to implement the IJobListener interface. Here is the interface: public interface IJobListener{ string Name { get; } void JobExecutionVetoed(JobExecutionContext context); void JobToBeExecuted(JobExecutionContext context); void JobWasExecuted(JobExecutionContext context, JobExecutionException jobException);}
Continue ReadingIn this post I’ll walk you through creating and configuring a Quartz.Net plug-in. It’s not very complicated, but this will depend on what you are trying to do with your plug-in. For the example we will create a plug-in that attaches a global job listener to the quartz scheduler. This will come in handy later on, since I will be posting another article describing how to create a job listener for Quartz.
Continue ReadingWe recently upgraded one of our application to .Net 4.0. As part of this upgrade, we also upgraded out Quartz.net jobs to run on the 4.0 version of the .Net framework. The process was fairly straightforward, but not without surprises, so I figured I would post it here in case it’s useful.
Continue ReadingIn Part 1 we set up our database so that we could use it as a job store for Quartz.Net. Now, we need to set up our scheduler job store properties to use said database. Here are the most common properties and values that need to be set in order to get the scheduler to use the database as its job store:
Continue ReadingQuartz.Net stores all of its job related configuration in an aptly named JobStore. There are two different kinds of job stores available out of the box: RAMJobStore and AdoJobStore. By default, Quartz.Net uses a RAMJobstore. The RAMJobStore is extremely simple to configure, but it is a volatile store, so all job configuration is lost whenever the scheduler is restarted.
Continue ReadingIf you use Quartz.Net and you want to do anything other than run a batch file, then chances are you’ll want to create a custom job. Fortunately, creating it is not hard at all. Let’s get started. Here’s a quick rundown of what you need to do. First, you’ll need to add a reference to Quartz.
Continue ReadingIf you’re considering using Quartz.Net, chances are you are using log4net as the logging framework for your application. We’ll assume that you already know how to configure log4net and that you just want to plug that configuration into Quartz.Net. So, how do we configure Quartz.Net to use log4net? It’s not terribly complicated, since Quartz.
Continue ReadingIn Part 4, we explained how to configure jobs in detail. In this final installment of the series we’ll describe how to configure two kinds of triggers: the CronTrigger and the SimpleTrigger. In keeping with the previous posts, we will configure the triggers in the quartz_jobs.xml file. Part 4 included a sample configuration of a CronTrigger, so let’s start with this.
Continue ReadingPart 3 of this series describes how to configure a job to run on Quartz.Net, but it does not go into detail about what each of the job settings does. This post will cover configuring jobs in detail and will provide some examples of job configurations. Most of the information we will be covering is available in the documentation for Quartz.
Continue Reading