Monitoring the report query queue and configuring queue processing

This topic discusses how you can manage the queue of report queries in real time.

To view the running queue

1. In Remedy Smart Reporting(Smart Reporting), select Administration > Background Execution.
   The Running queue lists all the queries that are currently running against their respective data sources. The possible states are:
   • Initializing
   • Query
   • Cross tab
   • Chart

1. To cancel a running query, click Cancel.

   Note

   The date and time for the Started Running time are based on the Smart Reporting server time, not the user time.

To view the waiting queue

1. In Smart Reporting, select Administration > Background Execution.
   The Waiting queue lists all the queries that are currently waiting to be run. The queries move to the Running queue when a report completes or times out.
2. To push a query out of the waiting queue and into the running queue, regardless of queue limit, click Add.

3. To cancel a query, select the query and click Cancel.

   Note

   The date and time for the Enqueued Time are based on the Smart Reporting server time, not the user time.

To control how the background execution queue works

1. In the RemedySmartReportingInstallDir\appserver\webapps\ROOT\WEB-INF directory, open the web.xml file and uncomment the following parameters:

   <!-- Execution queue values -->
   <!-- Uncomment these values  to customize the behavior of the background execution queue.
        
       ExecutionQueueConcurrentTasks:      The number of reports that can be run concurrently.
                                           Default: 5 times the number of CPU cores available on the server.
       ExecutionQueueInitialWaitTime:      How long the server will wait (in seconds) to finish a report before
                                           the client shows the delivery popup and start polling.
                                           Default: 5 seconds
       ExecutionQueueMaximumExecutionTime: The maximum time (in minutes) the reports can be running in the
                                           execution queue before they are killed.
                                           Default: 240 minutes (4 hours)
   <init-param>
    <param-name>ExecutionQueueConcurrentTasks</param-name>
    <param-value>10</param-value>
   </init-param>
   <init-param>
    <param-name>ExecutionQueueInitialWaitTime</param-name>
    <param-value>5</param-value>
   </init-param>
   <init-param>
    <param-name>ExecutionQueueMaximumExecutionTime</param-name>
    <param-value>240</param-value>
   </init-param>
   -->
2. To configure the number of reports that can be in the Running queue concurrently, change the ExecutionQueueConcurrentTasks parameter, which changes number of CPU cores available on the server.
   The default value is 5.
3. To configure how long the server will wait (in seconds) to finish a report before the client shows the delivery dialog box and starts polling, change the ExecutionQueueInitialWaitTime parameter. 
   The default value is 5 seconds.
4. To configure the maximum time (in minutes) a report can be in the Running queue before it is stopped and removed, change the ExecutionQueueMaximumExecutionTime parameter.
   The default value is 240 minutes (4 hours).

Where to go from here

Monitoring-and-managing-user-licenses