Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Quartz.Net in asp.net application
    text
    copied!<p>I've the Quartz scheduler uses AdoDataStore running as a stand alone windows service in port 555. I've an asp.net application that schedule jobs for this scheduler. What are the configurations I've to do in the ASP.NET side to schedule jobs? Any help is greatly appreciated.</p> <p>This is the service configuration,</p> <p> </p> <pre><code>&lt;!-- Configure Thread Pool --&gt; &lt;add key="quartz.threadPool.type" value="Quartz.Simpl.SimpleThreadPool, Quartz" /&gt; &lt;add key="quartz.threadPool.threadCount" value="10" /&gt; &lt;add key="quartz.threadPool.threadPriority" value="Normal" /&gt; &lt;!-- Configure Job Store --&gt; &lt;add key="quartz.jobStore.misfireThreshold" value="60000" /&gt; &lt;add key="quartz.jobStore.type" value="Quartz.Impl.AdoJobStore.JobStoreTX, Quartz" /&gt; &lt;add key="quartz.jobStore.useProperties" value="true" /&gt; &lt;add key="quartz.jobStore.dataSource" value="default" /&gt; &lt;add key="quartz.jobStore.tablePrefix" value="QRTZ_" /&gt; &lt;add key="quartz.jobStore.driverDelegateType" value="Quartz.Impl.AdoJobStore.StdAdoDelegate, Quartz" /&gt; &lt;add key="quartz.jobStore.lockHandler.type" value="Quartz.Impl.AdoJobStore.UpdateLockRowSemaphore, Quartz" /&gt; &lt;add key="quartz.dataSource.default.connectionString" value="Server=server\MSSQLEXPRESS;Database=QuartzServerDB;Trusted_Connection=True;" /&gt; &lt;add key="quartz.dataSource.default.provider" value="SqlServer-20" /&gt; &lt;!--export this server to remoting context--&gt; &lt;add key="quartz.scheduler.exporter.type" value="Quartz.Simpl.RemotingSchedulerExporter, Quartz" /&gt; &lt;add key="quartz.scheduler.exporter.port" value="555" /&gt; &lt;add key="quartz.scheduler.exporter.bindName" value="QuartzScheduler" /&gt; &lt;add key="quartz.scheduler.exporter.channelType" value="tcp" /&gt; </code></pre> <p></p> <p>So how would be the configuration in the asp.net side?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload