Monitoring Server best practices
Updated: 2009-04-09
The following are best practices for Monitoring Server.
Note
Either Office SharePoint Server 2007 or Windows SharePoint Services must be installed in order to successfully install and use Monitoring Server. The terms Windows SharePoint Services and SharePoint Services are used collectively in PerformancePoint Server documentation to refer to Office SharePoint Server 2007 and Windows SharePoint Services 3.0.
Monitoring Server application pool identity account
We recommend that the Monitoring Server application pool identity account is a domain user account and has the identity of the SharePoint site on which Dashboard Viewer for SharePoint Services is installed. This account must be assigned read permissions to any of the external data sources that are monitored through dashboards that are deployed to this SharePoint site.
Configuration of external data sources
Monitoring Server can be used to monitor various types of data sources. To read data from these data sources, appropriate permissions need to be granted to these data sources.
To create these data sources or preview the data in Monitoring Server using Dashboard Designer, the application pool identity account of the Monitoring Server Web Service and Dashboard Web Preview must be granted login and read permissions to each of the data sources.
To view dashboards that pull data from the data sources, the application pool identity account must be granted login and read permissions to each of the data sources.
Minimum version for Internet Explorer
Monitoring Server requires Internet Explorer 6.00.2600.0000 or later. We recommend that you install the most recent version with all current updates.
Memory management
When running multiple Monitoring Server application pools on a single server, the ASP.NET cache should be limited to prevent performance degradation. The following lines should be added to the <system.web> section of the Web.config file for the SharePoint, WebService, and Preview Web applications:
<caching>
<cache percentagePhysicalMemoryUsedLimit="30" />
</caching>
The WebService and Preview Web applications typically share the same application pool. On a stand-alone server, there are typically two application pools that can have large ASP.NET caches: SharePoint and WebService/Prevew. On a server with only one large-cache Web application, this action is unnecessary because the default ASP.NET cache sizing will be correct — that is, approximately 60 percent of the available physical memory.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.