How to: Install Data Providers for Filters

To install a data provider for a filter, you must add your DLL to the global assembly cache and then modify three web.config files. Two files are located on the computer that is running PerformancePoint Monitoring Server, and one file is located on the computer that is running Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007 where Dashboard Viewer for SharePoint Services is installed. The following table lists the default location of each web.config file.

On Computer RunningDefault Location

Monitoring Server

drive:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\PPSMonitoring_1\WebService

Monitoring Server

drive:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\PPSMonitoring_1\Preview

Windows SharePoint Services or Office SharePoint Server 2007

The web.config file is in the SharePoint Web site directory.

To install a data provider for a filter

  1. On the computer that is running Monitoring Server, add your DLL and any assembly that it references to the global assembly cache.

  2. In each web.config file, add a key for the extension by using the following format:

    <add key="[class name]" value="[namespace name.class name], [DLL name], Version=[version number], Culture=[culture type], PublicKeyToken=[public key token]" />

    For example, if your data provider is defined in the SqlQueryFilterDataProvider class, which is in the Extensions.Dashboard namespace in DashboardFilter.dll, add the following entry to the <CustomParameterDataProviders> section. Replace the version, culture, and public key token in the example with the correct information for your own signed DLL.

    <add key="SqlQueryFilterDataProvider" value="Extensions.Dashboard.SqlQueryFilterDataProvider,    DashboardFilter, Version=, Culture=neutral, PublicKeyToken=c4b493225b1eafa7" />
  3. Save and then close the file.


When you build your DLL, sign it with a strong name. In addition, ensure that all assemblies referenced by your DLL have strong names. For information about how to sign an assembly with a strong name and how to create a public/private key pair, see How to: Create a Public/Private Key Pair.

See Also

Community Additions