In this article

Project Server 2013 integrates the SharePoint Server 2013 Business Intelligence Center site template into each instance of Project Web App, which provides a central point for hosting the reports, dashboards, and report connections that can be auto-created or manually authored to provide access to reporting data in a given instance of Project Web App. The Business Intelligence Center can be used to host content created with Excel Services in SharePoint Server 2013, Visio Services in SharePoint, PerformancePoint Services in SharePoint, Power Pivot and SQL Server Reporting Services (SSRS).

Video demonstration

This video shows the steps involved in configuring reporting in Project Web App, as described in this article.

Video: Configure reporting for Project Web App

Configure prerequisites

The procedures in this article require Excel Services and Secure Store. If you have not already deployed these services on SharePoint Server 2013, you must do so before proceeding with the procedures in this article.

Note

Both Excel Services and Secure Store run as service applications in SharePoint Server 2013. If you have already deployed these service applications in SharePoint Server 2013, you can use them with Project Server. There is no need to create new instances of these service applications for Project Server.

For information about deploying Excel Services, see the following articles:

The Excel Services application pool account requires access to the SharePoint content database that is associated with Project Web App. If the content database was created after Excel Services was configured, you must follow the procedure in Grant content database access to the managed account to grant the proper access.

For information about deploying Secure Store, see the following articles:

Active Directory security group to which you add users who will create reports, or any other users who need to access reports in Excel. This group is given read permissions to the Project Web App database via the PSDataAccess database role. Have your domain administrator create this group before proceeding with the procedures below. NOTE - If you have multiple instances of Project Web App and you want to isolate reporting access for each, you will need a Report Authors group for each instance of Project Web App.

Report Viewers group

Active Directory security group to which you add users who will view reports. Have your domain administrator create this group before proceeding with the procedures below. NOTE - If you have multiple instances of Project Web App and you want to isolate reporting access for each, you will need a Report Viewers group for each instance of Project Web App.

Secure Store Target Application account

This account provides the credentials necessary for report viewers to view reports generated from data in the Project Web App database. This account must have read permissions on the Project Web App database via the PSDataAccess database role. TIP - We recommend that you add this account to the Report Authors Active Directory group described above to give it the necessary permissions.

Add a login for the report authors group

In order for a report author to be able to access the Project Web App database from Excel, it is necessary to configure SQL Server access and add a SQL Server logon. The logon must allow specific access to the Project Web App database to get schema information and data. Use the domain group you created for report authors.

Important

Excel does not use the Secure Store Service for data access. Only Excel Services in SharePoint Server 2013 uses Secure Store. Users working with reports in Excel require direct database access.

Perform the following procedure on the computer where your Project Web App database is located, or connect to the database engine remotely by using SQL Server Management Studio.

After installing the AMO objects, restart the Project Application Service on each application server in the farm where it is running. This service is configured in the SharePoint Central Administration website in the System Settings section, Manage services on server.

Configure Excel Services settings

You must configure trusted file locations for the Project Web App Sample Reports and Templates libraries.

Follow this procedure twice: once for each library.

To configure a trusted file location

In Central Administration, in the Application Management section, click Manage service applications.

In the Warn on Refresh section, clear the Refresh warning enabled check box.

Leave the remaining options at their default value, and then click OK.

You must configure trusted data connection libraries in order to give users access to the connectors that link the report spreadsheets to the data in the Project Server Database and OLAP databases. As part of this process, you will need the URL of the data connection library in Project Web App (PWA).

Use the following procedure to determine the URL of the data connection library in PWA.

To determine the URL for the data connection library

On the Project Web App site, in the left navigation pane, click Reports.

In the left pane, click Data Connections.

On the Data Connections page, click the Open Menu button ( ...) for the English (United States) line (or the appropriate language for your locale).

On the toolbar, click View Properties.

On the Data Connections properties page, right-click the English (United States) (or the appropriate language for your locale) link, and then choose ** Properties**.

Copy the URL in the Location text box.

To set up trusted data connection libraries

In Central Administration, in the Application Management, click Manage Service Applications.

Click the Excel Services service application.

Click Trusted Data Connection Libraries.

Click Add Trusted Data Connection Library.

In the Address box, paste the URL for the data connection library that you copied in the previous procedure. It should be in the following format:

Configure Secure Store Service settings

The sample reports included with each instance of Project Web App are configured to use a Secure Store target application called ProjectServerApplication. You must create this target application in order for the sample reports to work. Use the following procedure to create the target application.

In the Target Application Administrators box, type the name of the user who will administer this target application.

In the Members box, type the name of the domain group you created for report viewers.

Click OK.

On the Secure Store Service Application page, select the check box for the target application that you just created.

On the ribbon, in the Credentials section, click Set.

On the Set Credentials for Secure Store Target Application (Group) dialog box, type the user name and password of the account you created for the secure store target application.

Important

This account must have PSDataAccess permissions on the Project Web App database. We recommend that you add this account to the Report Authors Active Directory group to give it the required permissions.

To provide your users with the needed access to the Business Intelligence Center in Project Web App and the reports within, you must populate the Report Authors and Report Viewers Active Directory groups as follows:

Report Authors group: Add the Active Directory accounts of users who will be creating reports using Excel.

Report Viewers: Add the Active Directory accounts of Project Web App users who will be viewing reports in the Business Intelligence Center.

Note

If your report authors will also be viewing reports, you can add the Report Authors group to the Report Viewers group in Active Directory.

OLAP cube access

If you plan to use SQL Server Analysis Services OLAP cubes with Project Web App, then you must configure cube access for your users. For more information, see Configure OLAP cubes for Project Web App.

See also

The feedback system for this content will be changing soon. Old comments will not be carried over. If content within a comment thread is important to you, please save a copy. For more information on the upcoming change, we invite you to read our blog post.