Skip to main content

Configuring PerformancePoint Services in SharePoint 2010

PerformancePoint Service (PPS) is used to create content rich dashboards that aggregate data and content throwing light in to how business is performing.

PPS was not part of MOSS 2007 but with SharePoint 2010 Microsoft has integrated PPS as a service within. Dashboard Designer is the tool using which we can author KPIs, Scorecards, reports, etc.

Lets take a look at the steps involved in configuring PPS on a SharePoint 2010 Server farm.

1. Select Start -> All Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Central Administration. Click "Manage Service Applications" under Application Management. On the ribbon, Click on the Arrow below "New" and select "PerformancePoint Service Application".



2. Enter a name for this service application, select/create an application pool, and associate a managed account.



3. We get a confirmation screen on the service application successfully created. I had used the name "Performance_App" for this service application



4. Next we have to create a secure store service and turn the PerformancePoint service on. Without configuring Secure Store you cannot use PerformancePoint’s unattended service account to connect to data sources. The unattended account cannot use the application pool identity to connect to data sources which used to be the case in previous version. It must use a domain account, whose password is stored in the secure store.

To create Secure Store navigate to Managed Service Application and click New and select Secure Store Service.



5. After filling in the details and clicking on Ok throws an error; I have to create a new key for this Secure Store application.



6. Click on Generate New Key on the ribbon and enter the Pass Phrase



7. Click on Refresh Key, this would propagate encryption key to all application servers.






8. PPS web application is created now



9. Next we have to configure PPS, to do this Click on the newly created PPS application - click Manage - Click on "PerformancePoint Service Application Settings"



10. Configure unattended account



11. Final step, we need to associate the our web application to PPS service application. To do so, navigate to Central Administration - Application Management - under Service Applications - click configure service application associations



12. I configure it for my default web application



13. Select the PPS service application and click Ok



The PerformancePoint service application is configured.

Comments

Anonymous said…
Well, don't you have to configure and set your PPS database and cubes in SQL as mention in this article.
http://ekhichdi.com/e/SharePoint-2010-Performance-Point-Service-Configuration-With-SSAS-472.html
Anonymous said…
In the article you have mentioned they are using Analysis Service Template, hence configuring cubes.

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er