Skip to main content

Overview of PerformancePoint Services architecture

PerformancePoint Services topology

The following is a farm topology that uses three servers for implementing PerformancePoint Services in Microsoft SharePoint Server 2010.

Architecture for three-server farm

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.

PerformancePoint Services as a service application

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.

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.