Installing Reporting Services SharePoint Mode Report Server for Power View and Data Alerting
The Microsoft SQL Server Reporting Services add-in for SharePoint 2010 products.
The add-in installs the Reporting Services user interface (UI) pages and features on a SharePoint web front-end server. The UI features include Power View, administration pages in SharePoint Central Administration, feature pages used within SharePoint document libraries, and Reporting Services Data Alerting pages.
The Microsoft SQL Server Reporting Services report server installed in SharePoint Mode
The report server handles the data and report processing and rendering as well subscription and Data Alert processing. The SharePoint mode report server is architected and installed as a SharePoint Shared Service.
The following steps assume that an administrator is installing and configuring the server. The Setup user in SharePoint is also a farm administrator and often the primary site administrator for the default site collection. If you are dividing the following steps among several people, additional permissions might be required in order for the following steps to work.
Run the SharePoint 2010 Products Preparation Tool
You must have the SharePoint 2010 installation media. The preparation tool is PrerequisiteInstaller.exe on the installation media.
Install SharePoint Server 2010 enterprise or enterprise evaluation edition.
When installing SharePoint, you can choose to configure the farm later by not running the SharePoint 2010 Product Configuration Wizard after Setup is finished. Waiting to configure the farm will allow you to use a SQL Server 2012 Database Engine instance, which is installed in a later step, as the farm’s database server. To configure the farm, you will use the PowerPivot Configuration Tool. It includes actions for provisioning the farm if the farm is not yet configured.
Install SharePoint Server 2010 SP1.
Download SP1 from http://support.microsoft.com/kb/2460045.
Run SQL Server 2012 Setup to install the Database Engine and PowerPivot for SharePoint.
Install PowerPivot for SharePoint
Step 1 explains how to install PowerPivot for SharePoint. In this step, be sure to click the checkbox on the Setup Role page that adds the Database Engine to the role. Doing so adds the Database Engine to your installation so that you can use it as the farm’s database server when you configure the farm in the next step. However, if the farm is already configured, you can skip this step.
Step 2 asks you to configure the server. For this step, choose the PowerPivot Configuration tool. Although several approaches are available, using the configuration tool is the most efficient approach for a standalone installation.
If SharePoint 2010 is installed but not configured, the tool pre-selects actions that will create the farm, a default web application, and a root site collection. Be sure to leave these options selected so that the farm will be created. If you already configured the farm, the tool will omit these actions, and offer just the actions that are necessary for configuring PowerPivot for SharePoint.
Step 3 instructs you to install the SQL Server 2008 R2 version of the Analysis Services OLE DB Provider. This step is important for supporting versions of a workbook that were created in the 2008 R2 version of PowerPivot for Excel.
Verify the farm is operational.
First, start Central Administration and confirm that it is available. Next, open the team site by entering http://localhost. You should see a SharePoint team site.
Verify that PowerPivot for SharePoint is operational.
Verify a PowerPivot for SharePoint Installation
This task confirms PowerPivot data access using a sample workbook that you upload.
Run SQL Server 2012 Setup to install and configure Reporting Services and the Reporting Services Add-in.
Install Reporting Services SharePoint Mode as a Single Server Farm
Optionally, while installing Reporting Services, you can add an additional Analysis Services instance to the Setup feature tree if you want a second resource for hosting tabular data. The additional Analysis Services instance would be used to host tabular model databases that you create in SQL Server Data Tools (SSDT). Tabular databases are a valid data source for Power View reports.
Install Analysis Services in Tabular Mode
Verify that Reporting Services is operational.
Verify a Reporting Services Installation
(Site Administrators) Configure SharePoint permissions.
Contribute permissions are required to add, edit, or delete items in SharePoint libraries. View permission level is sufficient for read-only access to reports and PowerPivot workbooks that present embedded data.
PowerPivot workbooks that are accessed as external data sources (where the workbook URL is a connection string in another workbook or report) require Read permissions, which is higher than View permissions.
BI semantic model connections also required Read permissions. You might need to create new permission levels or SharePoint groups to get the correct permissions in place.
(Site Administrators) Extend document libraries
Extend document libraries to use BI content types: BI semantic model connections, Reporting Services Shared Data Sources, Report Builder reports:
Enable content type management. In Shared Documents or another document library, in the Library tab, click Library Settings. Under General Settings click Advanced settings. In Content Types, select Yes to allow management of content types, and then click OK.
Select the BI content types. In the Library tab, click Library Settings. Under Content Types, click Add from existing site content types. From the Business Intelligence content type group, add BI Semantic Model Connection File and Report Data Source. Optionally, you can also add other Reporting Services content types, such as Report Model, to enable additional report building scenarios.
For more information, see Add a BI Semantic Model Connection Content Type to a Library (PowerPivot for SharePoint) and Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode).
(Site Administrators) Create data connection files that are used to launch Power View.
You must create a BI semantic model connection (.bism) or a Reporting Services shared data source (.rsds) as a data source for Power View. After you create a data connection file, you can launch Power View using the data connection as its data source.
Create a BI Semantic Model Connection to a PowerPivot Workbook
Create a BI Semantic Model Connection to a Tabular Model Database
Create a Shared Data Source for a Data Model (SSRS)
Note: Power View is available because you installed the SQL Server 2012 version of Reporting Services and configured the server as a shared service. If you installed Reporting Services and configured it for the SQL Server 2008 level of integration, Power View is not available.
The diagram shows a typical three tier environment and the numbered items in the diagram are described in the following list:
(1) Multiple web front-end (WFE) servers. The WFE servers require the Reporting Services add-in for SharePoint 2010. The following steps add a second application server to this tier.
(2) Two application servers running Reporting Services and web sites, for example Central Administration.
(3) Two SQL Server database servers.
(4) Represents a software or hardware network load balancing solution (NLB)
Verify the server was added to the SharePoint farm.
Install the SQL Server 2012 Reporting Services add-in for SharePoint 2010 products.
Create or identify the accounts used in a report server deployment. You must have a service account for the Report Server service, and credentials for connecting to the report server database
Decide on an instance of SQL Server to host the report server database. You can use a local or remote instance of SQL Server. You should choose an instance that is on a computer that has the storage capacity to accommodate your reports.
4.Start the SharePoint ‘Claims to Windows Token Service’: Start the Claims to Windows Token Service through SharePoint Central Administration on the Manage Services on Server page. The service should be started on the server that will be performing the action. For example if you have a server that is a WFE and another server that is an Application Server that has the Reporting Services shared service running, you only need to start C2WTS on the Application Server. C2WTS is not needed on the WFE.
Installation and initial configuration
Install the SharePoint add-in on all Web front-end (WFE) computers.
Add an Additional Reporting Services Web Front-end to a Farm
Install SQL Server SQL Server 2012 Reporting Services and the Database engine.
Install Reporting Services SharePoint Mode as a Single Server Farm
Create at least one SSRS service application and configure service app association.
See the ‘Service Application’ section in Install Reporting Services SharePoint Mode as a Single Server Farm
Add SSRS content types to your document library.
Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode)
Provision SQL Server Agent
Provision Subscriptions and Alerts for SSRS Service Applications
Configure e-mail settings for your Service application
Configure E-mail for a Reporting Services Service Application
Configure Claims to Windows Token Service (c2WTS)
Claims to Windows Token Service (C2WTS)
Reporting Services can be installed from the command line using the input settings for the SQL Server setup program.
setup.exe /q /ACTION=”Install” /IACCEPTSQLSERVERLICENSETERMS /FEATURES=”RS_SHP” /INSTANCEDIR=”C:\Program Files\Microsoft SQL Server” /INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server” /INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server” /INSTALLSQLDATADIR=”C:\Program Files\Microsoft SQL Server” /SECURITYMODE=”SQL” /SAPWD=”*****” /PID=”[Your PID Value]” /SQLSYSADMINACCOUNTS=”[Account Name]” “AutoSql Admin Group” /ASSYSADMINACCOUNTS=”[Account Name]” /UPDATEENABLED=”False”
A distributed server deployment uses multiple computers, where each computer hosts a single server component. You might use this deployment configuration if you want better performance for processing complex reports or large datasets for a small organization or workgroup.
The following illustration shows components for a three-computer deployment.
The first computer hosts an instance of a SharePoint product or technology. The second computer hosts SQL Server Reporting Services. The third computer hosts an instance of the Database Engine.
In the illustration, notice that the Database Engine does not require a local installation of a report server or an instance of a SharePoint product or technology.
To use a remote database server with a deployment of a SharePoint product or technology, choose the Advanced installation option when installing an instance of a SharePoint product or technology, or use Central Administration to modify the database server setting. To select a remote database server for Reporting Services, use the Reporting Services Configuration tool. For more information about edition and connection requirements for a report server database, see Creating a Report Server Database and How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration).