title: Multiple Quartz.NET scheduler services and single web-app
body: <p>I have a scenario where I can have one-to-many Quartz scheduler instances running on a single server. Basically you can envision it as each department within the company getting it's own scheduler instance. Each scheduler is backed by it's own unique quartz database and each is wrapped up in it's own unique Windows Service. To illustrate better:</p>
  
  <p><strong>Server1</strong></p>
  
  <ul>
  <li>Accounting_WindowsService --> Accounting_QuartzScheduler --> QuartzAccountingDatabase</li>
  <li>Sales_WindowsService --> Sales_QuartzScheduler --> QuartzSalesDatabase</li>
  <li>IT_WindowsService --> IT_QuartzScheduler --> QuartzITDatabase</li>
  </ul>
  
  <p><strong>Server2</strong></p>
  
  <ul>
  <li>Management_WindowsService --> Management_QuartzScheduler --> QuartzManagementDatabase</li>
  <li>HR_WindowsService --> HR_QuartzScheduler --> QuartzHRDatabase</li>
  </ul>
  
  <p>etc.</p>
  
  <p>On a completely separate server I have a single web site that is used by ALL departments within the company. But this site needs to able to route through to the correct Quartz scheduler so that the user can schedule and maintain their own jobs as well as view existing jobs and their status etc. So for example, if I login to the web app as a member of the Sales dept I only want to see the jobs scheduled to the QuartzSalesDatabase and if I wish to schedule a new job I need a mechanism to get a handle on the required Sales_QuartzScheduler to do so. How best would this be accomplished? thanks</p>