Time to Retain Page Data in Cache (CACHEREPORT4)
By default, information about an active ControlPoint operation is kept in a server memory cache for 20 minutes. Within this time period, a user can:
·initiate and run a ControlPoint action or analysis
·return to results of an analysis from which the user has drilled down
·download search or analysis results.
After this time period has expired, the cache is cleared and the operation must be re-initiated.
ControlPoint Application Administrators can change the number of minutes that analysis data is held in server memory cache by modifying the Value of the ControlPoint Setting Time to Retain Page Data in Cache.
NOTE: This is an Advanced Setting.
If you increase this value, a ControlPoint operation will remain "active" for a longer period of time. Keep in mind, however, that the higher the value is set the longer information about the operation will consume memory, which may be a burden on server resources (specifically, the size of the application pool process supporting the Web application that hosts the ControlPoint Configuration Site collection).
If you decrease this value and the server cache is cleared before a ControlPoint operation (such as a Copy/Move) has completed, the Task Audit that is generated at the conclusion of the operation will contain no data. (However, a completed Task Audit for the operation can still be invoked from the Manage ControlPoint panel).
Time to Retain Temporary UI Objects in Cache (UICACHEDURATION)
By default, ControlPoint retains temporary UI-related objects in server memory for 10 minutes. ControlPoint Application Administrators can, however, change the number of minutes that analysis data is held in server memory cache by modifying the Value of the ControlPoint Setting Time to Retain Temporary UI Objects in Cache.
NOTE: This is an Advanced Setting.
This setting is designed to be used in conjunction withand set to a lower value thanTime to Retain Page Data in Cache (CACHEREPORT4) to enable the cache to be cleared more quickly.
Number of Reports to Keep in Memory After Drill-Down (RVSESSIONSKEPT)
By default, if a ControlPoint user has checked the Open drill-downs in new window parameter for a ControlPoint analysis, the Report Viewer will keep information for up to 10 of these analyses for each user in server memory before the window containing the results of the original analysis expires. ControlPoint Application Administrators can change this limit, however, by changing the Value of the ControlPoint Setting Number of Reports to Keep in Memory After Drill-Down.
NOTE: This is an Advanced Setting.
NOTE: This setting applies only when a user drills down in a new window.
If you increase this value, a user will be allowed to open more drill-down windows before having to re-initiate the original analysis. Keep in mind, however, that the higher the value is set the more information will consume memory, which may place a burden on server resources (specifically, the size of the application pool process supporting the Web application that hosts the ControlPoint Configuration Site collection).
Exclude Web Application(s) from Statistics List (DASHBOARDWAPEXCLUDE)
By default, the site collection statistics list that is created for use by dashboards includes all site collections in the farm.
ControlPoint Application Administrations can, however, exclude all of the site collections within one or more Web applications (up to a maximum of 6) from the Site Collection Statistics list. For example, you may choose not to monitor statistics for a large number of MySites.
To exclude a Web application from the Site Collection Statistics list, enter the Web application's GUID as the Value of the ControlPoint Setting Exclude Web Application(s) from Statistics List. Use the following guidelines:
1To locate a Web application's GUID, select the Web application in the ControlPoint Farm Hierarchy, right-click and choose Properties.
2Copy the Id's Property Value and paste it directly into the Value field.
3Repeat steps 1 and 2 for each Web application you want to exclude (up to a maximum of 6). Use a comma (,) to separate each GUID in the list.