Overview of PerformancePoint Services architecture (SharePoint Server 2010)
Applies to: SharePoint Server 2010
Topic Last Modified: 2009-12-10
Microsoft SharePoint Server 2010 provides the flexibility to meet many different deployment solution goals. For more information about designing server farms and physical topologies, see the model called "Services in SharePoint 2010 Products" in Technical diagrams (SharePoint Server 2010).
The following is a farm topology that uses three servers for implementing PerformancePoint Services in Microsoft SharePoint Server 2010.
The front-end Web server runs on Internet Information Services (IIS) and hosts the PerformancePoint Services Web Parts, Web services, and proxy that are required for communication between the client and the PerformancePoint Services service application.
The service application is a wrapper for the middle-tier business logic for an instance of PerformancePoint Services.
In SharePoint Server 2010 services are no longer contained within a Shared Service Provider (SSP). Instead, the infrastructure for hosting services becomes part of SharePoint Server 2010, and the configuration of service offerings is more flexible. The service applications framework is a common service model that provides the following benefits.
A consistent management experience and shared infrastructure for all services. As one of those services, PerformancePoint Services can provide the ability to perform bulk security operations for service applications in a farm from the SharePoint Central Administration Web site.
Backup and recovery benefits also include restoring a site collection, site, or list content to a previous version or point-in-time.
Services are installed by default, so there is no SSP setup or configuration.
Sites can be configured to use only the services that are needed, rather than the entire list of services.
Deploying services across sites and farms is more flexible. Similar to previous versions, a single set of services can be shared by all Web sites in a farm.