Background execution
This page is designed to allow you to manage the queue of report queries in real time.
Note
This information is applicable only for BMC Remedy Smart Reporting version 9.1.03 and later.
Running Queue
This list displays all the queries that are currently running against their respective data sources. The following information is available in the list:
| Item | Description |
|---|---|
| Name | Displays the name of the report associated with the running query. |
| Requester | Displays the name of the user that is running the report. |
| Started Running | Displays the date and time the query started running. Note: This is based on the BMC Smart Reporting server time and not the user time. |
| Running Time | Displays the length of time the report query has been running. |
| State | Displays the state of the query. Possible values are:
|
| (Cancel) | Cancels the selected query and removes it from the queue. |
Waiting Queue
This list displays all the queries that are currently waiting to be run. The queries progress to the Running queue when a report completes or times out.
| Item | Description |
|---|---|
| Name | Displays the name of the report associated with the running query. |
| Requester | Displays the name of the user that is running the report. |
| Enqueued Time | Displays the date and time the user started running the report. Note: This is based on the BMC Smart Reporting server time and not the user time. |
| Waiting Time | Displays the length of time the report query has been in this queue. |
| (Add) | Pushes the query out of the waiting queue and into the running queue, regardless of queue limit. |
| (Cancel) | Cancels the selected query and removes it from the queue. |
Settings
To control how the background execution queue works, uncomment the following parameters from the web.xml file located in the BMC Remedy Smart Reporting\appserver\webapps\ROOT\WEB-INF directory:
<!-- Execution queue values -->
<!-- Uncomment these values if you want to customise the behaviour 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>
-->Concurrent Tasks
This option allows you to configure the number of reports that can be in the Running queue at the same time. You can change the number of CPU cores available on the server. The default value is is 5 x.
<init-param>
<param-name>ExecutionQueueConcurrentTasks</param-name>
<param-value>10</param-value>
</init-param>Initial Wait Time
This option allows you to configure how long the server will wait (in seconds) to finish a report before the client shows the delivery popup and starts polling. The default value is 5 seconds.
<init-param>
<param-name>ExecutionQueueInitialWaitTime</param-name>
<param-value>5</param-value>
</init-param>Maximum Execution Time
This option allows you to configure the maximum time (in minutes) a report can be in the Running queue before it is stopped and removed. The default value is 240 minutes (4 hours)
<init-param>
<param-name>ExecutionQueueMaximumExecutionTime</param-name>
<param-value>240</param-value>
</init-param>
Comments