Configuring Services and Scheduled Tasks

Issuetrak uses a combination of Windows services and scheduled tasks to continuously provide features and functionality:

Feature Name Service or Task?
Automatic Asset Updates Scheduled Task
Issue Escalations Scheduled Task
Scheduled Issues Scheduled Task
Scheduled AD Imports Scheduled Task
Scheduled Reports Scheduled Task
SLA Notifications Scheduled Task
Incoming Email Scheduled Task
Outgoing Email Service

This article applies to the current version of Issuetrak. If you have an older version, please see the below table for a comparison of previous versions or contact Issuetrak Support for more information.

To see how these features have evolved over time, click here
Feature Name 9.5.5 - 9.9.6 9.10 - 10.3.12 11.0 - 11.5.1 11.6+
Automatic Asset Updates SQL Job SQL Job Scheduled Task Scheduled Task
Escalation Rules SQL Job SQL Job Scheduled Task Scheduled Task
Incoming Email Scheduled Task Service Service Scheduled Task
Outgoing Email SQL Job Service Service Service
Recurring Issues SQL Job SQL Job Scheduled Task Scheduled Task
Scheduled AD Imports Scheduled Task Scheduled Task Scheduled Task Scheduled Task
Scheduled Reports Scheduled Task Scheduled Task Scheduled Task Scheduled Task
Service Level Agreements (SLAs) SQL Job SQL Job Scheduled Task Scheduled Task

Each service and task is version-specific. That is, it will only target and process Issuetrak instances matching its own version.

Additionally, it is possible to choose which tasks or services need to run against your site.  In order to make these changes, it is necessary to review and modify the underlying configuration.  

In On-Premises deployments, these tasks are deployed:

Incoming Email Scheduled Task

  • To begin at 12:12 AM
  • With an offset between 0-120 seconds
  • With a frequency of every 2 minutes

Scheduled Reports Task

  • To begin at 12:03 AM
  • With a frequency of every hour

Scheduled Issues Task

  • To begin at 12:06 AM
  • With a frequency of every hour

 

EmailConfiguration.xml

Configuration information concerning these services and tasks is located on the Web server in a single file named EmailConfiguration.xml located here:

C:\Program Files (x86)\Issuetrak\Common\Configuration\Services

An entry for each site determines whether scheduled tasks and services should target the site when they begin their work, what communication information should be used, and other information necessary to process the site.  Services and tasks can be disabled by changing their respective value to False.  For example, if you don't make use of SLAs in one site, you can simply set the relevant setting "SLANotificationsActive" to False to disable the SLA scheduled task for that site.  

For reference, here is an example of a site's entry within the file:

Example Code
<Site
      Name="MySite"
      Version="11.8"
      OutgoingActive="False"
      WebRootPath="c:\inetpub\wwwroot\MySite"
      SiteProcessingMaxDegreeOfParallelism="2"
      CountOfOutgoingMessagesToProcessPerIterationForSite="0"
      ConfigurationFilePath="C:\Program Files (x86)\Issuetrak\Common\Configuration\Services\Issuetrak.Services.Global.xml"
      ConnectionStringName="7797F20CD78A70D14067FAFF3F321EDC"
      AdImportActive="False"
      ScheduledReportsActive="False"
      RecurringIssuesActive="False"
      AssetAuditActive="False"
      IssueEscalationActive="False"
      SLANotificationsActive="False" />

An explanation of each entry follows below: 

Entry Name Setting Explanation
Name Name of the Issuetrak site
Version Version of the Issuetrak site
IncomingActive Deprecated.  Possible values:  True or False.  If 'True', tells the matching-version Incoming Email Service to process the site. 
OutgoingActive Possible values:  True or False.  If 'True', tells the matching-version Outgoing Email Service to process the site.
WebRootPath Path to the Issuetrak site's web folder. 
SiteProcessingMaxDegreeOfParallelism Default value is '2'. Should not be changed.
CountOfOutgoingMessagesToProcessPerIterationForSite Default value is '0', and is interpreted as 'infinite'.  Tells the matching-version Outgoing Email Service to limit the number of outgoing emails sent to the value specified each time this site is processed.
ConfigurationFilePath Default value is 'C:\Program Files (x86)\Issuetrak\Common\Configuration\Services\Issuetrak.Services.Global.xml'.  
This provides the path to the Issuetrak.Services.Global.xml file that contains connection string information for the various Issuetrak services to communicate with the Issuetrak sites.
ConnectionStringName This is a hex string that is auto-generated when a site is deployed. This is a unique identifier for each site, and it is used to differentiate between sites in the Issuetrak.Services.Global.xml file.
AdImportActive Possible values:  True or False.  Tells the AD Scheduled Import task (if present) whether to process this site.
ScheduledReportsActive Possible values:  True or False.  Tells the Scheduled Reports task (if present) whether to process this site.
RecurringIssuesActive Possible values:  True or False.  Tells the Recurring Issues task (if present) whether to process this site.
AssetAuditActive Possible values:  True or False.  Tells the Asset Audit task (if present) whether to process this site.
IssueEscalationActive Possible values:  True or False.  Tells the Issue Escalation task (if present) whether to process this site.
SLANotificationsActive Possible values:  True or False.  Tells the SLA Notification task (if present) whether to process this site.

 

Issuetrak.Services.Global.xml

Issuetrak.Services.Global.xml contains the "other half" of the configuration information referenced in EmailConfiguration.xml.  Issuetrak.Services.Global.xml is located on the Web server at the following location:  

C:\Program Files (x86)\Issuetrak\Common\Configuration\Services

The configuration information in this file is divided into three discrete sections:  

  • Secure Storage Keys:  A table cross-referencing the unique identifier for each site with the Secure Storage Key that is used to authenticate the services and tasks.
  • Site Versions:  A table cross-referencing the unique identifier for each site with the version of the site and its services.
  • Connection Strings:  An encrypted block of text that cross-references the unique identifier for each site with its own connection string information.  Each entry, when decrypted, consists of: 
    • Site Unique Identifier
    • SQL server hostname
    • Database name
    • The site-specific SQL username that communicates with the MVC application.  This is usually a variation on "IssuetrakMvcUser".
    • The password for the site's MVC SQL user account. 

If you require any assistance with modifying the settings outlined above, please contact Issuetrak Support at 757-213-1351 or support@issuetrak.com