Configuring PerformancePoint Monitoring Server Component Connectivity
When I installed PerformancePoint Monitoring, I got stuck because I couldn't figure out why I was not able to connect to some underlying data sources. I figured it out after reading Nick Barclay's BI Blog.
A new article, published on The Microsoft PerformancePoint Team Blog, describes how different PerformancePoint Monitoring Sever components authenticate and connect to each other and to data sources in order to create and render reports. Click here to download the article.
The following common problems were considered:
- Why can’t I see any Analysis Services Databases when creating a data source using the Dashboard Designer?
- What configuration files are referenced when deciding how to perform authentication and where are they located?
- What are the default settings for IIS Application Pools used by various PerformancePoint Monitoring Server components?
- Why do I receive an error message indicating that a dashboard is unavailable after publishing the dashboard to a SharePoint Server site?
The following “how do I” solutions are addressed:
- Locating and modifying Web.Config files.
- Determining the correct setting for the Bpm.ServerConnectionPerUser property.
- Configuring PerformancePoint Monitoring Server authentication to ensure that dimensional security by user and/or group enforced by Analysis Services roles will be honored.
- Granting PerformancePoint Monitoring Server permissions by user and/or group.
If that's not enough, the following are some pre-released bits of security/role content written by one of PeformancePoint's Information Worker technical writers, Denise. Thank you Denise for this content!
-------------
How do user roles and permissions affect dashboard elements?
Roles and permissions are interconnected in that permissions are typically granted to users through their assigned roles. For example, some users may be assigned roles that enable them to edit elements, such as data source connections, reports, or scorecards. Other users may be assigned roles that enable them to only view elements.
Roles are assigned in various software applications, such as Monitoring Server, Dashboard Designer, Windows SharePoint Services, and other servers, including Reporting Services, Analysis Services, ProClarity Analytics Server.
Norm's note: There is a difference between Monitoring Server roles and Monitoring Server element roles. Additionally, you may need access to several other servers. Consider the following (from Denise's topic).
Servers host data used by dashboard elements, such as reports, scorecards, or filters. Examples of possible dashboard data sources include:
- SQL Server 2005 Analysis Services
- SQL Server 2005 Reporting Services
- ProClarity Analytics Server
- Microsoft Office SharePoint Server 2007
- Excel Services
Example: Using roles in multiple servers to create dashboard elements
Suppose that you have the Creator role in Monitoring Server and you deploy dashboards in your organization. Suppose further that you want to include a ProClarity report in your dashboard. In order for you to do this, you must also have a role in ProClarity Server that enables you to view and use ProClarity reports. This is necessary because your Creator role only applies to Monitoring Server; the Creator role does not automatically extend to other servers that host reports or data you want to use.
-----------
Well, in conclusion, here are a few great links for servers that are likely to host data used by dashboard elements.
Monitoring Server roles and security
Security Considerations for SQL Server
Reporting Services Security Model
Plan site and content security (Windows SharePoint Services)
Plan Excel Services security
