Installing and Configuring PerformancePoint Server 2007 in a Distributed Environment (Part 3)

This post is part of a series focussing on installing and configuring PerformancePoint Monitoring Server across multiple servers e.g. SharePoint Farm.  Other parts can be found here:


In this part, I will step through configuring the ‘Dashboard Viewer for SharePoint Services’ – AKA PerformancePoint Web Part.

This step will be carried out on our SharePoint WFE. In this case, we only have one WFE, but this step will need to be repeated for all WFE’s in the farm.


I cannot stress the importance of making sure you have all your pre-reqs installed, PRIOR to installing PPS Monitoring Server and SP3 on this WFE.  If you haven’t, or not sure, go back a check the list on Part 1.

Configuring the PerformancePoint WebPart / MasterPage

Right, now we’re set, run the Monitoring Server Config Wizard, and you should be presented with the pre-req check screen, which should all light up green except the SSRS components (unless you have SSRS installed on your WFE). Click Next.


On the next screen, ensure that ‘Distributed Configuration’ is selected, and ensure that the only component selected is ‘Dashboard Viewer for SharePoint Services’ (remember we configured the Monitoring database and Web Service in Part 2). Click Next.


Next, you’ll be asked for the SQL Server and Database Name. This is so the Web Part can locate the published dashboards and dashboard items for display.  Enter these details and click Next.


The final piece of information is a Site Collection URL on which to deploy this component.  Now this is actually a bit misleading.

There are essentially two components deployed here:

1. The PerformancePoint Dashboard WebPart will be added to the GAC and deployed as a solution to the Web Application containing the selected Site Collection above.

2. A dashboard master page will be deployed to the chosen Site Collection. This will be used by default when deploying an entire dashboard to that SharePoint Site Collection. If you’re like me and just add the Web Part to your existing Master Page, you wont be too fussed which Site Collection you select.

So taking all that in, select an appropriate Site Collection and click Next.


You should see confirmation that we are ready to proceed, click Next.


Finally, double check your settings and click ‘Configure’.


Fingers crossed, this component will be installed successfully!


Most issues arise from the following causes:

– The pre-requisites haven’t been installed successfully prior to installing PPS 2007 Monitoring Server and SP3 (prior to installing PPS, not prior to configuring).

– The user account running the Configuration Wizard doesn’t have permissions to add assemblies to the GAC or solutions to the SharePoint Central Admin solution store.

– The user account running the Configuration Wizard doesn’t have Site Collection Admin rights on the Site Collection selected in the Config Wizard.

Next, we shall look at setting up Dashboard Designer ready to begin creating some BI Dashboards!

Installing and Configuring PerformancePoint Server 2007 in a Distributed Environment (Part 2)

This post is part of a series focussing on installing and configuring PerformancePoint Monitoring Server across multiple servers e.g. SharePoint Farm.  Other parts can be found here:


Configure the PPS Monitoring Web Service and Database

As discussed, I have decided to installed this on my MOSS App Server.  After making sure all pre-reqs are installed, run the Monitoring Server Configuration Wizard.  On the pre-reqs screen, all items should be ticked, with the exception of the SSRS components as these are not required for the PPS Monitoring Web Service.  Click Next.


On the ‘Installation Options’ page, ensure that a ‘distributed configuration’ option is selected, and choose ‘Monitoring System Database’ and ‘Monitoring Server’.  It is recommended best practise to install these components first (and together).  Click Next.


On the ‘Database’ screen, enter the name of your Database Server and required name for the Monitoring Database. 

If the user you are currently running the configuration wizard as, has the following permissions on your Database Server, you can select the option to ‘Create Monitoring System Database’:

Server Log In

dbcreate rights on the server

Alternatively your SQL DBAs can create a new database, and this wizard can overlay the required schema.  For this, select the ‘Provision..’ option.

Click Next.


Now you need to configure the IIS Web Site which will house the PPS Monitoring Web Service.  Decide if SSL is required, and the desired port to use.


On the next screen you must provide the credentials of a domain account to be the identity of the Application Pool for the Web Service and the Dashboard Designer Preview site.  A straightforward domain account will suffice, and the configuration wizard will set any required permissions.  Enter the details and click Next.


If everything has been configured successfully and the account you are running the configuration wizard as has suitable permissions, you should get a set of green lights.  Click Next.


At the review screen, double check all your settings and click ‘Configure’.  Now, the configuration wizard will attempt to create the IIS Web Site, Monitoring Database etc.  At the end of this you should see a ‘Configuration completed successfully’ message on the final screen.  Close the wizard, and you are done configuring the Database and Web Service.

If you take a look in IIS, you should see the new IIS Web Site created, and the 3 virtual directories to house the PPS Dashboard Designer install, Dashboard Preview Site, and of course the Monitoring Web Service itself.


Also, you can see the three Application Pools also set up in IIS to manage the 3 virtual directories listed above.


Look out for Part 3, where we’ll configure the Dashboard Item Web Part for SharePoint.

Installing and Configuring PerformancePoint Server 2007 in a Distributed Environment (Part 1)

Welcome to a multi-part blog on installing and configuring PerformancePoint Server 2007 on a multi-server SharePoint farm. Other parts can be found here:


I’ve been meaning to blog this for a while, but a recent task to install and configure PPS in a 3 server MOSS Farm has prompted me to finally do it.

This will be a multi-part blog, beginning with the scenario and general approach.


We have a 3 server MOSS Farm (WFE, APP Server and Database Server) and the requirement is to install and configure MS PerformancePoint Server 2007 (Monitoring and Analytics) onto this environment.  We do not have the luxury in this case of having a separate server to host PPS.


PPS Monitoring Components Overview

PPS Monitoring Server contains multiple parts:

Monitoring System Database

This will reside on your SQL Server and will contain all the published dashboards, dashboard items and data sources, in addition to security info.

Pre-reqs: SQL Server (2005/2008/2008 R2)

Monitoring Web Server

This comprises of a new IIS Web Site and three virtual directories to support the main Monitoring Web Service, Dashboard Preview and Dashboard Designer Installation Site (Monitoring Central). This component obviously needs to be configured on a server which has the Web Server role (IIS).

Pre-reqs: IIS, SQL Server Native Client 9.0 (SP2), ADOMD.NET 9.0 (SP2), ASP.NET 2.0 AJAX Extensions

Scorecard Viewer for SSRS

This is an interface for deploying scorecards to SSRS in RDL format.  This component will need configuring on your SSRS server and requires SSRS to be installed and configured ready.

Pre-reqs: SSRS

Dashboard Viewer for SharePoint Services

This is effectively a Web Part for connecting to and rendering PPS Dashboard Items.  Obviously this piece requires WSS but seeing as AJAX is used, the ASP.NET 2.0 AJAX Extensions are required on the server too.

Pre-reqs: WSS 3.0, ASP.NET 2.0 AJAX Extensions v1.0

Monitoring Plug-In for Visual Studio (BIDS)

This allows for the customisation of RDL Scorecards from within a developers BIDS/Visual Studio environment.  Obviously this is only required on a developer machine.

Pre-Reqs: Visual Studio Report Designer (BIDS)

Pre-Requisite Software Required

Just to clarify, the following table lists the pre-requisite software you require on each server, appropriate to the component you wish to configure.  PPS 2007 is very fussy about this, and even though the installation will not complain, I have seen many configuration issues arise due to the pre-requisites NOT being installed prior to PPS Installation (not configuration).

Ensure these are 64-Bit if your server and PPS install is 64-bit

PPS Component Pre-Requisites
Monitoring Database None (aside from SQL Server obviously)
If wishing to install the PPS Monitoring Database (as opposed to overlaying the schema only) ensure the user running the config wizard has a SQL Login with dbcreate rights.
Monitoring Web Service ASP.NET 2.0 AJAX Extensions v1.0
SQL 2005 SP2 CU9 Client (sqlncli.msi)
SQL 2005 SP2 CU9 Analysis Services ADOMD
SQL 2005 SP2 CU9 Analysis Services OLEDB Provider (ASOLEDB9.msi)
Dashboard Viewer for SharePoint (Web Part/Master Page) ASP.NET 2.0 AJAX Extensions v1.0
SQL 2005 SP2 CU9 Client (sqlncli.msi)
SQL 2005 SP2 CU9 Analysis Services ADOMD
SQL 2005 SP2 CU9 Analysis Services OLEDB Provider (ASOLEDB9.msi)

PPS Monitoring Installation & Configuration Approach

The general approach will be as follows:

Before beginning to install PPS 2007, ensure your SharePoint Farm is all configured correctly and working. 

1. Ensure al the pre-requisite software is installed on each server appropriate to the PPS Monitoring components you wish to configure on there (see the components overview above).

NOTE: Even if SQL Server 2008/2008 R2 is being used as your database server, there is still a requirement to install component from the SQL 2005 SP2 CU9 Package (  PPS Monitoring components will only communicate with SQL Server via these interfaces. Also, a minimum of PPS 2007 SP2 is required in this case (prior to SP2, PPS 2007 wasn’t supported on SQL 2008).

2. Install PerformancePoint Monitoring Server 2007 (RTM) (PSCSrv.msi) on each server BUT DO NOT RUN THE CONFIG WIZARD (yet)

3. Install the service pack you desire on each server (the final service pack released by Microsoft was SP3 in September 2009) (PSCSrv.msp).  DO NOT RUN THE CONFIG WIZARD (yet)

4. Consider the best place to host the main Monitoring Web Server component

My personal preference is usually to host this component on your MOSS Application server.  Essentially the Monitoring Server is a service which will be requested by MOSS WFEs, in addition to clients connecting directly via Dashboard Designer.  If we think about SharePoint 2010, PerformancePoint is now a managed service application within the service tier of the product, and that is the desired model I aim to achieve in 2007 deployments. 

In addition to this, the Monitoring Server adds an additional IIS Web Site and 3 Application Pools to manage – something which you don’t necessarily want adding to your WFEs, even if this provides resilience via Load Balancing.

Finally, the PPS Monitoring Web Service is designed to be used internally within your organisation (via SharePoint or Dashboard Designer).  Therefore even if you have an Extranet environment it is unlikely you would wish to expose this outside your corporate walls.

5. Configure the PPS Monitoring Web Service (see Part 2)

6. Configure the Dashboard Viewer for SharePoint (Web Part) (see Part 3)

7. Configure the SSRS components if required. (see Part 3)

8. Finally set up and test authoring, publishing and deploying a PPS Dashboard to Monitoring Server and ultimately SharePoint. (see Part 4)

Now see how to configure the PPS Monitoring Web Service in

SPEvo Football Tournament Team News

…news just in from the managers, I now have the team selections for the SharePoint Evolutions Football Tournament, to be held in London on Sunday 18th April (4-6pm).:

England (White Shirts)

– M. Macrae (@m_macrae), A. Pearce (@Alex_Pearce), A. Woodward (@Andrew_Woody), C. O’Brien (@chriso_brien), N. Swan (@nickswan), S. Smith (@stevesmithck), N. Hodgkinson (@nellymo), Y. Ranpura


USA (Blue Shirts)

– R. Foster (@lespaulrob), L. Rodgers (@wonderlaura), S. Windhorst (@sharepointsara), B. Lonsdale (@brettlonsdale), C. Wheeler (@cwheeler76), P. Duffy, S. Pike, T. Penhall, I. Raphael (@ilohraphael)


Rest of the World (Black Shirts)

-  D. Pyett (@dpyett), M. Hughes (@mattmoo2), J. Fisk (@draken), M. Iveson, S. Nesbitt, L. Blackwell, G. Clough (@GlynClough), R. Norton, P. Sledz (@psledz)


With WAGS and celebrities such as Mr Bob Fox and Shaun O Callaghan watching from the sides swilling beer, it promises for a very entertaining afternoon.  Hell, even Joel Oleson is rumoured to make an appearance…

The press will be there Matt Groves and Combined Knowledge, so look pretty!