his article takes up the installation process started in Performance Point 2007: Installing Planning Server
, and assumes you have already completed that part of the installation. However, if you don't need the Planning Server components, you can install the Monitoring Server components separately—but you won't have access to the Monitoring Server tools.
To summarize TechNet's helpful overview of Monitoring Server
Monitoring Server allows business analysts and business decision makers to:
- Measure overall performance using Key Performance Indicators (KPIs). A KPI represents an organizational goal, such as sales quotas, inventory monitoring, or customer response time.
- Monitor the performance of units or divisions within in an organization by comparing actual numbers against the KPIs.
- Based on the results, the effectiveness of a specific functional area, such as sales, professional services or retail can be evaluated.
- Ideally, the information can then be used to drill down and analyze the causes of the successes or failures.
Dashboard Designer lets business analysts and IT professionals create:
- Data sources
- Analytic reports
Embarking on what I assume will be another challenging installation, I review the prerequisites for Monitoring Server
(for a condensed list, see the sidebar "Prerequistes for Monitoring Server
From that extensive list, it's apparent that the Monitoring Server needs a combination of SQL Server and SharePoint Server 2007 (or WSS 3.0) installed, along with other bits and pieces for the client tools, including Visual Studio 2005 with Report Designer.
In my virtual environment (see the sidebar "Lab Environment"), for simplicity, I'd like to keep WSS 3.0 and/or SharePoint Server 2007 off my SQL 2005 back end server, which means fewer instances of SharePoint to support and URLs to remember. Also, that will reduce RAM requirements; I'll avoid loading an unneeded version of SharePoint and using up another hundred megabytes of RAM. Finally, I just added the PerformancePoint Planning Server module to my SQL 2005 back-end server, and like the idea of adding the Monitoring components to my SharePoint 2007 front end.
|Figure 1. PerformancePoint Installation Screen: Choose the Install Monitoring Server option.|
Due to the lengthy prerequisites list, I decide to start the installation and see what components it shows as being required on the SharePoint Server 2007 server (ABCMOSS02).
I map the MOSS server to the ISO image I downloaded for the previous article (en_office_performancepoint_server_2007_x86_cd_X14-00932.iso) and the installation screen comes up (see Figure 1).
I click on Install Monitoring Server, check the "I accept the licensing terms" checkbox, and click Next. On the following screen I accept the default location (C:\Program Files\Microsoft Office PerformancePoint Server\), click Next, and then click Install on the following screen to start the installation process.
After the "Monitoring Server Setup has completed" screen comes up (see Figure 2).
|Figure 2. Monitoring Server Setup: Here's the completion screen for the Monitoring Server setup component.||
|Figure 3. Monitoring Server Configuration Manager: The figure shows the Welcome screen with the installation steps listed.||
I check "Run the Monitoring Server Configuration Manager Wizard" box, and then click Finish. The wizard opens as shown in Figure 3
, and I click Next.
The configuration manager shows that some of the prerequisites haven't been met (see Figure 4). I click Cancel and exit the wizard.
|Figure 4. Monitoring Server Configuration Manager: The Prerequisites analysis shows that some prerequisites are missing. Analysis Results.|
As Figure 4
shows, I have four items to install: the Visual Studio 2005 Report Designer, the SQL Server Native Client 9.0 (SP2), the ASP.NET 2.0 AJAX Extensions 1.0, and SQL Server 2005 Reporting Services. I'll fulfill all these requirements, starting with the AJAX Extensions.