Follow

Overcoming the Historical Performance Reporting limit of top (or bottom) 200

Question:
How do I overcome the Historical Performance Reporting limit of top (or bottom) 200

Limitation:

The main reason for limiting the number of rows on custom reports is to avoid a performance bottleneck on the DGE database(es) and how it would affect overall performance. This can manifest in either delays on the Web Application as users drill-down into summary pages, historical data, etc and/or a backlog of collected results waiting to be written to the DGE database

Limitation:
You will need to re-apply these changes after installing a newer version of Traverse

Answer:

In order to enable up to 500 rows, please edit TRAVERSE_HOME\webapp\user\performanceReportInput.jsp and TRAVERSE_HOME\webapp\admin\performanceReportInput.jsp on the BVE server (TRAVERSE_HOME is the Traverse installation directory). Open the file in notepad/vi or your editor of choice and locate the following section:

<html:select name="performanceReportForm" property="numItems">
<html:option value="10">10</html:option>
<html:option value="25">25</html:option>
<html:option value="50">50</html:option>
<html:option value="100">100</html:option>
<html:option value="200">200</html:option>
</html:select>

You can insert additional selection options before the </html:select> tag like this:

<html:select name="performanceReportForm" property="numItems">
<html:option value="10">10</html:option>
<html:option value="25">25</html:option>
<html:option value="50">50</html:option>
<html:option value="100">100</html:option>
<html:option value="200">200</html:option>
<html:option value="500">500</html:option>
</html:select>

Once you save the files and navigate to Reports -> Custom -> Performance Reports, you should see the new options in the drop-down list.

No components need be restarted.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.