Configure Report Server Integration in SharePoint Central Administration

If you are configuring a report server to run within a deployment of a SharePoint product, you must specify integration settings that determine the connection between the SharePoint technology instance and a Reporting Services report server:

·        You must be an administrator on the SharePoint farm to configure report server integration:

·        You must have installed the Reporting Services Add-in for SharePoint products, which provides the configuration pages and general integration.

·        You must also have a target report server that is already connected to a report server database that was created for SharePoint integrated.

·        If you are configuring Reporting Services to run within a SharePoint server farm, you must also have a SharePoint Web front-end installed on the report server computer.

The settings that you specify are stored in the configuration database. If you are configuring integration for a farm that includes several virtual servers, the settings will be used by all Web front-ends that are enabled in a SharePoint farm and that have an installation of the Reporting Services Add-in.

To integrate a report server with SharePoint

1.      From SharePoint Central Administration, click General Application Settings.

In the Reporting Services section, you should see the following links:

1.      Reporting services integration

2.      Add a report server to the integration

3.      Set server defaults

If you do not see the section or the links, the Reporting Services Add-in for SharePoint is not installed on the computer or the feature is not activated. For more information, see How to: Activate the Report Server Feature in Site Settings.

2.      Click Reporting services integration.

3.      In Report Server Web Service URL, specify the report server site that you want to use with the current SharePoint site or farm. The URL can point to a single report server instance, or it can be the virtual server name for a set of load-balanced report servers that run in a scale-out deployment.

To get the URL, open the Reporting Services Configuration manager, connect to the report server, and click Web Service URL. Click the URL to open a browser and verify it works. It is by design that you may see a configuration error message, if you have not yet completed integration with SharePoint.

Copy the URL and paste it into Report Server Web Service URL.

The report server URL includes a server name and a virtual directory that you specified in the Reporting Services Configuration Manager. The following examples illustrate how a report server URL might be constructed:

o    http://your-server-name/reportserver (this example might be used if the report server is on a different computer).

o    https://your-server-name:443/reportserver.

Do not specify http://localhost for a report server URL that is used throughout a SharePoint farm. A URL address that specifies http://localhost will not be valid for SharePoint Web front-ends that are installed on remote servers.

If you installed the report server and the SharePoint technology instance side-by-side, check for virtual directory name conflicts. For more information about interoperability issues, see Deploying Reporting Services and Internet Information Services Side-by-Side in SQL Server Books Online.

4.      In Authentication mode, select either Windows Authentication or Trusted Account to specify whether the report server endpoint installed on the SharePoint server sends a header with a security token for an impersonated connection on the report server.

All requests that originate from a user action on a Reporting Services application page are forwarded by the report server endpoint on the SharePoint Web application to a report server for processing. Depending on the authentication mode, the request may or may not include a SharePoint user identity token in the header.

If the SharePoint Web application is configured for Windows Authentication and the Kerberos protocol is enabled, you can select Windows Authentication to connect through Windows integrated security. In this case, no user identity token is sent. Optionally, you can select Trusted Account to impersonate the trusted account and pass the SharePoint user information in the request header to the report server.

For more information about server connections, see Security Overview for Reporting Services in SharePoint Integrated Mode in SQL Server Books Online.

5.      In Credentials, specify credentials which represent a member of the Administrator group on the computer that hosts the report server.

6.      In Activate the Reporting Services Feature, choose what scope you want to activate the reporting services integration feature for, either all site collections or only those you select.

7.      Click OK.

8.      The Integration Summary page is then displayed. The summary shows the results of database access, Windows group membership, and feature activation. If the Web service URL you specified is part of a Reporting Services scale-out deployment, you will see the Reporting Services Scale-out Integration section in the summary page. The scale-out section lists all the Reporting Services instances that were detected in the scale-out deployment. The list does not indicate if each instance has or has not already been integrated with SharePoint. The list is provided as a reminder of the instances you need to verify are integrated by either one of the following methods:

o    Click the Add Instance link next to the instance name.

o    On the Reporting Services Integration page click Add a Report Server to the Integration.

Click Close when you are finished reviewing the integration summary.

To specify server defaults

1.      In the Reporting Services section, click Set server defaults.

2.      In Report History Snapshots, set a site-wide default value for the number of copies of report history to retain. The default value provides an initial setting that establishes the number of snapshots that can be stored for each report. You can specify different limits in property pages for specific reports.

3.      In Report Processing Timeout, specify whether report processing times out on the report server after a certain number of seconds. This value applies to report processing on a report server. It does not affect data processing on the database server that provides the data for your report. The report processing timer clock begins when the report is selected and ends when the report opens. The value that you specify must be sufficient to complete both data processing and report processing.

4.      In Report Processing Log, specify whether the report server generates trace logs and the number of days the log is kept. . The logs are stored on the report server computer in the folder Program Files\Microsoft SQL Server\MSSQL.n\ReportServer\Log folder. A new log file is started each time the service is restarted. For more information about log files, see Report Server Service Trace Log.

5.      In Enable Windows Integrated Security, specify whether a connection to a report data source can be made using the Windows security token of the user who requested the report.

6.      In Enable running Ad Hoc Reporting, specify whether users can perform ad hoc queries from a Report Builder report. Setting this option sets the EnableLoadReportDefinition property on the report server. If you clear this option, the report server will not generate click through reports for reports that use a report model as a data source.

7.      In Enable RsClientPrint ActiveX control download, specify whether users can download the client side control, which provides printing options.

8.      In Enable Report Builder Download, specify whether clients are able to see the button for downloading the report builder application.

9.      In Custom Report Builder Launch URL, Specify a custom URL when the report server does not use the default Report Builder URL. This setting is optional. If you do not specify a value, the default URL will be used, which launches Report Builder 3.0. To launch Report Builder 1.0 as a Click-Once application, enter the following value: http://<computername>/ReportServer/ReportBuilder/ReportBuilder_1_0_0_0.application.

10.  Click OK.

11.  If you are installing a single server, review the post integration information in How to: Install and Configure SharePoint Integration on a Stand-alone Server.

Configure the Reporting Services Configuration Manager >> SQL Server 2012

To do the initial configuration of SSRS, or to change the configuration of an existing installation, you need to start the Reporting Services Configuration Manager (Start menu >> Programs >> Microsoft SQL Server 2012 >> Configuration Tools >> Reporting Services Configuration Manager);

The Configuration Manager can largely be treated as a wizard as you move down the tabs on the left side of the window. The first step is to set the Service Account. Once you’ve made you selection and entered logon details click the Apply button;

 

Move to the Web Service URL and either accept the default or change the Virtual Directory and Web Service Site identification details (make sure you make a note of the Report Server Web Service URL as you will need this when configuring SSRS within Microsoft SharePoint);

After you’ve clicked Apply, the Results section will confirm the Virtual Directory has been created and the URL reserved.

Click the Database Tab to select, or create a new, database for use with SSRS;

 Click the Change Database to open the Report Server Database Configuration Wizard. I’m leaving the default option of Create a new report server database and click Next;

Enter the Server Name and connection details for the SQL server which will hold the SSRS database and click Next;

Enter the Database and Temp Database Names, pick your language (unfortunately we’re restricted to only English (United States) without an option for English and pick whether SSRS should be in Native or SharePoint Integration Mode. For simplicity I have chosen Native Mode;

 Enter the log on credentials. Again I have chosen Service Credentials but would recommend a Domain User account for a production environment;

Click Next and you’ll be presented with a summary of your selections. Review them and click Previous to make any changes or click Next to proceed;

The Wizard will verify the configuration and present confirmation where you need to click Next;

The Database tab of the main Reporting Services Configuration Manager window will be updated with the database details. Review them and click Apply;
 

Move to the Report Manager URL tab and enter the Virtual Directory you want to use (I left this at the default option but in hindsight I’d rather have changed this to ReportManager_SQL2012);

After clicking Apply, as with the Web Service URL tab, you’ll be presented with confirmation that the virtual directory has been created and the URL reserved;

Click E-mail Settings and configure the SMTP settings if you want to use Report Server e-mail and click Apply;

On the Execution Account tab enter the details for accessing remote servers that store external images (make sure you use a domain user account with minimal read-only permissions) and click Apply;

Click onto the Encryption Keys tab. Whenever I see a Backup button I feel the need to do so. In the case of a demo system this isn’t especially important, but on a production environment I’d recommend you back up the Encryption Key in case of a need to recover or move the SSRS database;

 


The final step is to scale out the Deployment should you wish;
 

When done click close and SSRS will be available for use within SharePoint.



Hope you enjoyed reading this. Your comments, votes and suggestions motivates us for writing more stuffs like this.