Planning Server deployment topology

Updated: 2009-04-16

The following diagram shows the PerformancePoint Planning Server topology.

Planning Server Architecture

Development, test, and production environments

Due to the complexity of the product, you may choose to follow a "Development to Test to Production" large-system deployment model when deploying Planning Server to your production environment. Planning Server enables you to customize your installation and configuration based on your business requirements. This customization process can be called the development stage, and the system of computers that host this stage is often referred to as the Development environment. After customization is complete, you may move the system to a Test environment to allow users to thoroughly test and confirm that everything performs as expected. The final stage is to deploy the customized and tested system to a Production environment. You may choose to combine the Development and Test systems into one Development-Test environment.

Each of these environments can have different configurations of physical deployment. For example, your Development-Test environment could be a stand-alone configuration that you eventually migrate to your 30-server Production environment. See Migrating Planning Server data in PerformancePoint Server 2007 Operations Guide for more information.

ProClarity Analytics Server

ProClarity Analytics Server (PAS) runs only in 32-bit mode. It can be installed and run on the 64-bit versions of the Windows Server 2003 operating system, but it alters the way some components run to accommodate its 32-bit coding. PAS does not support the 64-bit versions of Windows Server 2003 directly. PAS can be installed on the 64-bit versions of Windows Server 2003, but it configures Internet Information Services (IIS) to run in 32-bit mode. This means that any other 64-bit applications that require IIS to run in 64-bit mode on a 64-bit server will conflict with PAS and will cause errors in PAS and the other 64-bit applications.

PerformancePoint Monitoring Server can be installed on either the 32-bit or 64-bit versions of Windows Server 2003 and supports each version natively. When you are installing Monitoring Server to the 64-bit versions of Windows Server 2003, PerformancePoint Monitoring Server requires that IIS be set to 64-bit mode. This means that PerformancePoint Monitoring Server and ProClarity Analytics Server cannot run on the same server that is running the 64-bit version of Windows Server 2003.

In some deployments, PAS and Monitoring Server are deployed together to aid in reporting for both PerformancePoint Server and ProClarity. In cases where only one server license is available to run both PAS and Monitoring Server, we recommend that the 32-bit version of the Windows Server 2003 operating system be used.

Sample: Three-server topology

The first sample deployment topology is a three-server topology. Server1 has SQL Server 2005 Service Pack 2 (SP2) installed. Server2 has SQL Server 2005 Analysis Services Enterprise Edition installed, and Server 3 has PerformancePoint Planning Server (Planning Process Service, Planning Web Service, and Planning Administration Console) installed and configured.

This is a basic deployment, such as for a test environment or a small organization. In this example, a file share is being used instead of SharePoint Products and Technologies (Windows SharePoint Service 3.0 or Microsoft Office SharePoint Server 2007).

three-server topology

Server1: SQL Server

Server2: Analysis Services

Server3: Planning Web Service, Planning Administration Console and Planning Process Service server.

Sample: Five-server topology

The second sample deployment topology is a five-server topology. Install SQL Server on the first computer, Analysis Services server on the second computer, Planning Web Service and Planning Administration Console on the third computer, Planning Process Service on the fourth computer, and Windows SharePoint Services 3.0 or Office SharePoint Server 2007 on the fifth computer.

three-server topology

Server1: SQL Server

Server2: Analysis Services

Server3: Planning Web Service and Planning Administration Console

Server4: Planning Process Service

Server5: Windows SharePoint Services (or Office SharePoint Server) or File Share

Sample: Ten-server topology

This sample deployment topology is an ten-server topology. This topology shows the scalability of Planning Server. Each component of a Planning Server topology can be installed. You can scale out each server to x number of computers depending on your system's load and performance requirements. For example, you can put SQL Server on five computers, with Server 1 containing PPSPlanningSystem and PPSPlanningService databases, Server2 through Server5 contains Planning application#1 to application#4.

Diagram of a ten-server topology

Server1: SQL Server

Server 2: SQL Server

Server 3: Analysis Services

Server 4: Analysis Services

Server 5: Planning Web Service

Server 6: Planning Web Service

Server 7: Planning Process Service

Server 8: Planning Process Service

Server 9: Planning Administration Console

Server 10: SharePoint Products and Technologies

Note

The terms Windows SharePoint Services and SharePoint Services are used collectively in PerformancePoint Server documentation to refer to Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0.

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.

See Also