Upgrading from a prerelease version of Planning Server
Updated: 2009-04-30
In this article:
Security requirements
Prepare for the upgrade
Perform the binary upgrade
Perform the Planning system upgrade
Perform the Planning application upgrade
Verify the upgrade
Perform post-upgrade configurations
Planning Server upgrade allows the current Planning Server and client applications to be upgraded to the next released version. For the version 1.0 release of Microsoft Office PerformancePoint Server 2007, the upgrade process allows CTP4 versions of Planning Server deployments to be upgraded to version 1.0. Upgrading from CTP1 version is not supported.
Note
To upgrade from CTP2 version of the Planning server and client applications, you must first upgrade from CTP2 to CTP4 followed by CTP4 to version 1. Upgrade must be fully completed before applying any patches.
Do not use earlier versions of the Planning client applications, such as Planning Business Modeler, PerformancePoint Add-in for Excel, Planning Administration Console or Planning Server, with the current version of Planning client applications or Planning Server because they might cause the system to be unstable or produce unexpected results.
When upgrading Planning Server, the Staging database (StagingDB) and the Outbound database (OutboundDB) are not upgraded. Create new StagingDB and OutboundDB databases as part of the upgrade process.
This upgrade process consists of six sequential steps. Each of these steps is discussed in detail in the following sections.
Security requirements
The administrator who upgrades Planning Server from CTP4 to version 1.0 needs specific permissions, or the upgrade will not succeed.
To upgrade Planning Server to version 1.0, the administrator performing the upgrade must be a member of the global administrator role in each Planning Server application. In addition, the same person needs administrator permissions on all computers in the Planning Server environment that are running Microsoft SQL Server 2005, SQL Server 2005 Analysis Services, Internet Information Services (IIS), and Windows Server 2003. Finally, to redeploy model sites after the upgrade is complete, the administrator needs to be a member of the Modeler role, with Model Site-scope permissions, in every model site in the system.
Prepare for the upgrade
Step 1: Prepare for the upgrade
Verify that you have documentation of your deployment topology to ensure that all servers and client computers are upgraded as part of this process.
Verify that all client computers have submitted any pending assignments through PerformancePoint Add-in for Excel.
Launch the Planning Administration Console and then click Applications. Select all applications, and then click Take Async-Offline.
Back up all Planning system and application databases, including related Analysis Services cubes:
PlanningSystemdb
PlanningServicedb
Planning application database (by default <ApplicationLabel>_AppDB in SQL Server)
Planning staging area database per application (by default <ApplicationLabel>_StagingDB in SQL Server)
Registered data destinations (by default <ApplicationLabel/ModelSiteLabel>_OutboundDB in SQL Server)
Planning analysis services database (by default <ApplicationLabel_ModelSiteLabel> in Analysis Services)
Uninstall CTP4 binaries from every server computer where Planning Server was installed. In a multi-computer deployment topology, you must ensure that CTP4 binaries are uninstalled from every computer running Planning Server.
Uninstall CTP4 binaries from every client computer where Planning Server was installed. In a multi-computer deployment topology, you must ensure that CTP4 binaries are uninstalled from every computer running Planning Server. If you use offline mode, ensure that PerformancePoint Add-in for Excel offline caches are deleted from computers running PerformancePoint Add-in for Excel.
Note
Do notdrop any Analysis Services or SQL Server databases. Do not delete Analysis Services cubes generated by Planning. Do not run the Planning Server Configuration Manager in this step. Planning Server Configuration Manager will be run in a subsequent step.
Perform the binary upgrade
After the environment has been prepared and ready to receive the new version, the following steps must be performed to install the new version of Planning Server.
Step 2: Perform the binary upgrade
Run PPLSrv.msi to install Planning Server components as you did for the topology information gathered in Prepare for the upgrade.
Run PBMCli.msi to install the Planning Business Modeler components.
Run PPLXCli.msi to install the PerformancePoint Add-in for Excel.
All server components including Web servers and client computers, including Planning Business Modeler, PerformancePoint Add-in for Excel and Planning Administration Console, must be installed prior to proceeding to the next step.
Perform the Planning system upgrade
After the new Planning version binaries have been installed on all servers and client computers, the Planning system databases must be upgraded from one of the newly installed servers.
Note
All applications will be set to Offline by this step.
Step 3: Perform the Planning system upgrade
Run the Planning Server Configuration Manager and select the distributed installation option. Clear the database option.
Attach to the existing Planning Server and Planning system databases and complete other required configurations. The objects upgraded are:
The DBSchemaVersion table in PPSPlanningService and PPSPlanningSystem databases
Representation of internal structures
Representation of internal metadata
Representation of system data
Representation of process metadata and data
Note
If multiple system upgrades are performed, this process will only track the last upgrade operation.
Perform the Planning application upgrade
After the Planning Server upgrade is complete, each application must be upgraded to ensure that it is compatible with the upgraded system. This process will attempt to upgrade all applications, even if one application upgrade fails.
The upgrade process determines which applications need to be upgraded by comparing the DBSchemaVersion table in the Application databases with the DBSchemaVersion table in the PlanningSystem database.
The following objects will be upgraded:
The DBSchemaVersion table in each application database
Representation of internal structures
Representation of system generated stored procedures
Representation of system metadata
Representation of user defined metadata definitions
Representation of process metadata and data
Note
If you did not install the new client components during Perform the binary upgrade, you will not be able to move forward in this process, because the installed version of Planning Command Utility (PPSCmd.exe) is also verified during this process. Planning Command Utility is installed in the same location as Planning Business Modeler.
Do not use any client applications until the upgrade is complete.
Step 4: Perform the Planning application upgrade
Upgrade all application databases by using Planning Command Utility as follows:
ppscmd upgrade /server < PlanningServer URL >
This step generates console output for all operations performed while upgrading the applications.
Verify the upgrade
It is important to verify the upgrade on both the server and client side. To ensure that the upgrade process is completed successfully, perform each of the following verification actions.
Step 5: Verify the upgrade
View the console output after the execution of Planning Command Utility from Perform the Planning application upgrade.
Verify the DBSchemaVersion table in the PPSPlanningSystem and PPSPlanningService databases.
Verify the DBSchemaVersion table in each application database.
Verify the About dialog box in Planning Business Modeler and PerformancePoint Add-in for Excel.
Verify that Planning Administration Console can connect to the upgraded Planning Server.
Perform post-upgrade configurations
To complete the upgrade process, the Planning Server must be configured to enable client computers to connect to the server and start to use the upgraded system. This step enables asynchronous workflow processing to start.
Step 6: Perform post-upgrade configurations
Launch the Planning Administration Console, and then click Applications. Select all applications, and then click Take Online.
Verify and manage any security configurations for upgraded applications. For example, if the Service Identity user account has been changed during the upgrade, then additional security configurations might be required.
Perform full deployment for every model site in all applications by using Planning Command Utility as follows:
ppscmd modelsitedeploy /full /server <PlanningServer URL> /path <ApplicationLabel>.<ModelSiteLabel>
Note
If all model sites are not deployed in this manner, the system might produce unexpected results.
Re-create all required Staging databases by using Planning Administration Console.
Configure the security settings for the newly created Staging databases by adding each Data Administrator user to Data Reader and Data Writer roles in SQL Server. For additional security configurations, refer to Data Integration Security roles.
Re-create all required data destinations by using Planning Administration Console.
Configure the security settings for the newly created data destination databases by adding each Data Administrator user to the dbowner role in SQL Server. For additional security configurations, refer to Data Integration Security roles.
Upon completion of this step, the upgrade process is complete and Planning Server is ready to be used. This step also enables asynchronous workflow processing to start.
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 Planning Server.