RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX


Performance Point 2007 Installation, Part 2: Installing Monitoring Server : Page 2

Follow this detailed walkthrough and—despite the lengthy list of prerequisites—you'll find that installing Performance Point Monitoring Server is a fairly straightforward process.

Install the ASP.NET 2.0 AJAX Extensions 1.0
To get the ASP.NET 2.0 AJAX Extensions 1.0. I search Microsoft.com and immediately find the download, so I click the Download button, and then, (because the file is tiny—1.36 MB) I click Run.

Figure 5. Installing ASP.NET 2.0 AJAX Extensions: Here's the first screen for the ASP.NET 2.0 AJAX Extensions 1.0 setup.
On the install screen for the AJAX wizard, I click Next (see Figure 5).

I accept the license terms, click Next, then click Install. When the install completes, I uncheck "Display Microsoft ASP.NET 2.0 AJAX Extensions 1.0 Release notes" and click Finish.

To ensure that I've installed the correct component I restart the Configuration Manager (Start → All Programs → Microsoft Office PerformancePoint Server 2007 → Monitoring Server Configuration Manager), which verifies that the AJAX component is installed.

Install SQL Server 2005 Native Client 9.0 and Reporting Services
Next, I'll install the two SQL components that Planning Server needs: SQL Server Native Client 9.0 SP2 and Microsoft SQL Server 2005 Reporting Services. I map to the ISO for SQL Server 2005 Enterprise (en_sql_2005_ent_x86_cd1.iso).

Author's Warning: SQL DBA's probably know this already, but I first selected the SQL Native Client Installation Wizard—and got stuck, because it didn't install the Business Intelligence Developments Studio (BIDS). Then I applied SP2, and couldn't get back to a place where the install wizard would let me install the BIDS! Fortunately, I had a VMWare snapshot to roll back to, and got it right the second time around. Moral: Make sure you set a rollback point before you begin.

From the installation screen (see Figure 6), I choose the "Server components, tools, Books online and samples" item.

Figure 6. SQL Server 2005 Enterprise Edition Install Screen: Select the "Server components, tools, Books Online, and samples" option.
Figure 7. SQL Server 2005 Setup: Here's the screen that appears to install prerequisites.

I accept the licensing terms and conditions, and click Next, then click Install on the Prerequisites screen (see Figure 7).

When the Prerequisites install completes, I click Next, which brings up a welcome screen, where I again click Next (see Figure 8).

Figure 8. SQL Server 2005 Setup: The figure shows the Installation Wizard's welcome screen.
Figure 9. SQL Server 2005 Setup: This screen shows the results of the system configuration check.

When the configuration check completes, you should review the results to see if there are any show stoppers. In this case, I had one warning (see Figure 9) which turned out to be that my system doesn't meet minimum hardware requirements—but I'll keep going anyway, so I click Next.

Next, I enter a name and company information on the third screen (see Figure 10) and click Next.

Figure 10. SQL Server 2005 Setup: Enter your name and company on this screen.
Figure 11. SQL Server 2005 Setup: Select the components you want to install.

From the next screen (see Figure 11) I select the Reporting Services and "Workstation components, Books Online and development tools" options. I then click on the Advanced button to review the features that will be installed. The key thing (as I learned in a previous installation attempt) is to make sure the Business Intelligence features get installed.

As shown in Figure 12, this installation includes the Business Intelligence Development Studio (BIDS), so I click Next.

Figure 12. SQL Server 2005 Setup: Clicking the Advanced button from the screen in Figure 11 shows details about the installation.
Figure 13. SQL Server 2005 Setup: You can elect to install a default instance or a named instance.

On the next screen (see Figure 13) I keep "Default instance" selected, and click Next.

I choose to log in using a domain user account—the administrator account, as shown in Figure 14. Note that using the administrator account is not good practice. Don't do this in a real-world situation. For this test, however, I want to keep things simple, and not have to maintain too many unique accounts in my VMWare environment. I click Next to continue.

Figure 14. SQL Server 2005 Setup: You can assign a domain account for the service.
Figure 15. SQL Server 2005 Setup: Report Server Installation Options: This screen simply informs you that you'll need to configure Reporting Services after the install completes.

The screen in Figure 15 clarifies that "setup will install, but not configure, the report server software." So I'll need to use the Reporting Services Configuration tool after the setup process is complete. I click Next to continue.

You can elect to automatically send information to Microsoft on the next screen. I leave the boxes unchecked and click Next, which gets me to the Ready to Install screen (see Figure 16). I click Install.

Figure 16. SQL Server 2005 Setup: The Ready to Install screen shows the components you've elected to install.
Figure 17. SQL Server 2005 Setup: Insert Disc 2 Window.

The install begins, and eventually requests Disc 2 (see Figure 17), so I change the ISO mapping to Disc 2 to install SQLXML4, the SQL Native Client, and the Workstation Components, and complete the configuration for several other components.

When the setup completes (see Figure 18), I click Next. Finally, I click Finish on the next screen.

Figure 18. SQL Server 2005 Setup: This progress screen shows you the install results for the selected components.
Figure 19. Monitoring Server Configuration Manager: This time, the Prerequisites screen shows that only SQL Server Native Client 9.0 (SP2) is missing.

Now I'll launch the Monitoring Server Configuration Manager to see which prerequisites are still pending (Start → All Programs → Microsoft Office Performance Point Server 2007 → Monitoring Server Configuration Manager). That brings up the welcome screen, so I click Next to run the prerequisite checker again. This time, the results in Figure 19 indicate that everything's installed except the SQL Server Native Client 9.0 (SP2)—which makes sense since I haven't installed SP2 yet. I click Cancel to exit the Configuration Manager.

Close Icon
Thanks for your registration, follow us on our social networks to keep up-to-date