Login | Register   
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

PerformancePoint 2007: Installing Planning Server : Page 5

Building more intelligent dashboards for businesses is a great idea; however, getting the software installed can be a showstopper. Find out how to install Planning Server, one of several installations required to get PerformancePoint working.


advertisement
Planning Server Administration
I open IIS Manager and note that there are two new Web sites, "PPSPlanningWebServices" and "PPSPlanningAdminConsole."
  1. I open Internet Explorer and try to access port 41000 (enter http:abcsql01:41000) and 42000 (http://abcsql01:42000). The second URL opens up the "Planning Administration Console" (see Figure 17), and I click on the Connect button after the location field, which conveniently displays the path to the other Web site (http://abcsql01:41000) in it. The status changes from red to green and the message indicates that I am now connected to the computer in question (also shown in Figure 17).
 
Figure 17. Planning Administration Console: This screen lets you specify the path to the server running Planning Server.

So far, this is encouraging, but there are still more pieces to install. The next step in the installation process is called "Creating file shares," and the corresponding "Creating File Shares" documentation page indicates the following:

"Microsoft Office PerformancePoint Server 2007 uses a network file share for templates and data files that are created by and for Planning Server users. This shared folder name should match the application name for each application, and each application should have its own share. If a shared folder is created, it must be in a Universal Naming Convention (UNC) location available to users. In addition, the Planning Server service identity (SI) account and all users of PerformancePoint Add-in for Excel must have access to the location. Permissions must include read, write, and modify.

These are the recommended subfolders for each file share location:

  • Form templates
  • Report storage
  • Assignment forms
  • Assignment master forms"
    1. That sounds pretty straightforward, so I create this structure on my Windows Server 2003 domain controller (ABCDC01). I give the abc\administrator and abc\SQLPlan accounts full control, and allow Everyone to change and read in this share.
     
    Figure 18. Create an Application Window: Follow the instructions in the article for a sample configuration.
    The next step on TechNet is "Creating an Application" which requires the following steps:
    1. Click "Applications" in the navigation pane of the window, and then click "Create."
    2. The "Create an Application" window pops up, and it is quite intimidating (see Figure 18) but I'm guessing I can get through it.
    3. So I'll keep the name simple and call it "Application1," and the label "Application1Label," give it a quick description, and plug in the SQL Server name. I enter a new database name, with the assumption that the application gets its own database (That may be wrong, but TechNet doesn't provide much information on this topic; my reasoning is that there would probably be a lookup or browse button if I needed to pick an existing database).
    4. Then I enter the locations of the files—the share and subfolders I created a little while ago. See Figure 19 for the details.
    5.  
      Figure 19. Create an Application Window: Here's how the sample configuration looks for the first ten fields.

       
      Figure 20. Create an Application Window: The figure shows the sample configuration for the Advanced Options, Application Scripts and Default Model Site fields and options.
    6. After perusing the TechNet information, I decide to leave the Advanced Options and the Application Scripts option checked.
    7. Under Default Model Site I enter a site name, App1RootSite, give the label the same name, and tell it that ABCSQL01 is the Analysis Services computer (see Figure 20). I click OK to continue.
    Voila, that seems to have worked, as shown in Figure 21. It did create a new database, titled PlanningApp1. Out of curiosity I check the settings for this database, and SQLPlan is the owner, Full Recovery model is selected, and the size of the database is about 43 MB. Back in the Planning Administrator Console, I notice that under the Model Sites link my App1RootSite now shows up (see Figure 22).


     
    Figure 21. New Application: The figure shows the results of a successful application creation process.
     
    Figure 22. Planning Administrator Console: The new Application Name now appears in the Model Sites page.

    Almost done. I go back to the Install Screen for PerformancePoint 2007. The next item listed is Planning Business Modeler, so I'll install this next, even though the TechNet instructions don't seem to specifically refer to it.


    Comment and Contribute

     

     

     

     

     


    (Maximum characters: 1200). You have 1200 characters left.

     

     

    Sitemap