Export (0) Print
Expand All

Step 5: Perform post-upgrade configurations for PerformancePoint Server 2007 SP3

PerformancePoint Server 2007

Updated: 2009-10-15

 

To complete the update process, PerformancePoint Planning Server must be configured to enable client computers to connect to the server and start to use the updated system. This following procedure enables asynchronous workflow processing to start.

Perform post-update configurations

  1. Restart the following services:

    • Planning Process Service

    • Planning Web site and Application Pool

  2. Start Planning Administration Console and then click Applications. Select all applications and then click Take Online.

    While in the Planning Administration Console, click Model Sites and note all your applications in the Applications box and all of the Model Site Labels. You will need this information for the next step.

  3. From any PerformancePoint Planning Business Modeler computer that has been updated with Microsoft Office PerformancePoint Server 2007 with Service Pack 3 (SP3), perform full deployment for every model site in all applications by using the Planning Command Utility.

    Open a Command Prompt window and at the command prompt change directories to the ppscmd.exe tool (the default path is %System Drive%:\Program Files\Microsoft Office PerformancePoint Server\3.0\BizModeler\ppscmd.exe). Using the list you created in step 2 that contains all of your Application and Model Site Labels, type the following command:

    ppscmd modelsitedeploy /full /server <PlanningServer URL> /path <ApplicationLabel>.<ModelSiteLabel>

    NoteNote:

    If all model sites are not deployed in this manner, the system may produce unexpected results.

  4. Recreate all required Staging databases by using Planning Administration Console. You must recreate the Staging database in the same Application database location. If you want to use the same Staging database name as the existing one, you must first remove the existing Staging database. If you want to save the existing Staging database for archiving, first remove the database and then create the new Staging database in the Administration Console. See Create the staging database for detailed information.

  5. Recreate all required data destinations by using Planning Administration Console. The Administration Console places them on the same server as the Application database.

  6. Custom configured security settings for the staging databases which were dropped during the SP3 Upgrade process must be re-configured. If dedicated users exist which are used to move data between source and staging databases that have assigned database permissions such as db_datareader, db_datawriter roles, those user accounts must be re-configured. For additional security configurations, see the discussion of data integration Security roles.

  7. All user accounts added to the PerformancePoint Global Administrator (GA) role during the SP3 update should now be removed.

Upon completion of this procedure, the update process is finished, and Planning Server is ready to use. This step also enables asynchronous workflow processing to begin.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft