1.0 Introduction

2.0 Requirements

3.0 Installation

4.0 Uninstalling Reporting Services Add-in

5.0 Features in This Release

6.0 Known Problems

7.0 Documentation Notes

[Top]

The Microsoft® SQL Server™ 2005 Reporting Services Add-in for SharePoint Technologies is a Web download that provides features for running a report server within a larger deployment of Microsoft Windows® SharePoint® Services 3.0 or Microsoft Office SharePoint Server 2007. The Reporting Services Add-in provides the following functionality:

• A Report Viewer Web Part that provides report viewing capability, export to other rendering formats, page navigation, search, print, and zoom.
  
  
• Web application pages so that you can create subscriptions and schedules, set model item security, and manage reports, models, and data sources.
  
  
• Support for using standard Windows SharePoint Services features including document management, collaboration, security, and deployment with report server content types. You can use alerts, versioning (check in/out), and Filter Web Parts with reports. You can add the Report Viewer Web Part to any page or dashboard on a SharePoint site and customize its appearance. You can use SharePoint permission levels and roles to control access to report server content. You can also use SharePoint forms authentication to support access over Internet connections.
  
  
• Support for additional languages. The Web application pages, Report Builder, and ReportBuilder.chm are available in the standard SQL Server languages (Chinese Simplified, Chinese Traditional, English, French, German, Italian, Japanese, Korean, Russian, and Spanish), and the following additional languages: Czech, Danish, Dutch, Finnish, Greek, Hungarian, Norwegian (Bokmal), Polish, Portuguese (Portugal), Portuguese (Brazilian), Swedish, and Turkish.
  
  

The Reporting Services Add-in works together with updated program files that are in SQL Server 2005 Service Pack 2 (SP2). SP2 is required on the report server and provides the following functionality for a report server that is configured for SharePoint integrated mode:

• Synchronization from SharePoint content databases to the report server database.
  
  
• A custom security extension that uses SharePoint permissions to control access to report server operations.
  
  
• A new delivery extension that you can use in subscriptions to deliver reports to SharePoint libraries.
  
  
• A revised Reporting Services Configuration tool that you can use to configure a report server for SharePoint integrated operations.
  
  
• Publish reports and models from Report Designer and Model Designer to a SharePoint library.
  
  
• Open reports and models in Report Builder from a SharePoint library, and save reports to SharePoint libraries across the site.
  
  
• A new SOAP endpoint for managing report server content in SharePoint integrated mode.
  
  

To install the Reporting Services Add-in, the computer must meet the following software and hardware requirements:

• Windows SharePoint Services 3.0 or Office SharePoint Server 2007. The Reporting Services Add-in is not supported on earlier versions of Windows SharePoint Services.
  
  
• Two (2) gigabytes of RAM.
  
  
• The Web sites cannot be enabled for Anonymous access.
  
  
• Microsoft Internet Explorer 6.0 with SP2 or later.
  
  

To configure integrated operations, the report server must be SQL Server 2005 SP2 Reporting Services. The report server must be configured for SharePoint integrated mode as described in SQL Server Books Online. Supported SQL Server editions include Standard, Evaluation, Developer, and Enterprise. Server integration is not supported on the Workgroup Edition of Reporting Services or SQL Server 2005 Express with Advanced Services.

For more information about requirements for SharePoint products and technologies, see Determine hardware and software requirements (Windows SharePoint Services 3.0) and Determine hardware and software requirements (Microsoft Office SharePoint Server 2007).

[Top]

To install the Reporting Services Add-in, you must have an installation of Windows SharePoint Services 3.0 or Office SharePoint Server 2007. To use the features provided by the Reporting Services Add-in, you must have a SQL Server 2005 SP2 Reporting Services report server configured to run in SharePoint integrated mode.

You must be a SharePoint farm administrator to install the Reporting Services Add-in.

If you are installing Reporting Services and the SharePoint product or technology instance on the same computer, you must ensure that the report server and the SharePoint site are accessed through unique Web sites or ports. For instructions, see SQL Server Books Online.

1. Download and run the Setup program for the Reporting Services Add-in. Setup will copy program files and create entries in the SharePoint databases. If you are integrating Reporting Services with a SharePoint farm, you must install the Reporting Services Add-in on each Web front-end in the farm.
   
   
2. In Administrator Tools, click SharePoint 3.0 Central Administration.
   
   
3. Click Application Management. You should see a new section named Reporting Services. This section has links to pages used to specify integration settings.
   
   
4. In the Reporting Services section, click Manage integration settings
   
   
   1. Specify the report server URL (for example, http://example-server-name/reportserver).
      
      
   2. In Authentication Mode, select either Windows Authentication or Trusted Account to specify whether the proxy server endpoint 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 proxy server endpoint to a report server for processing. Each request includes information in the header that determines how the request is authenticated on the report server.
      
      If the SharePoint Web application is configured for Windows Authentication and the Kerberos protocol is enabled, you can choose Windows Authentication to connect through Windows integrated security. No security token is sent in the header. Optionally, you can choose Trusted Account to impersonate the process identity of the SharePoint Web application and pass the SharePoint user identity token in the request header to the report server.
      
      If the SharePoint Web application is configured for Forms authentication, the request header will always include a SharePoint user identity, and any value you specify for Authentication mode is ignored.
      
      
   3. Click OK.
      
      
5. In the Reporting Services section, click Grant database access. During this step, the service account information is retrieved from the report server instance. A database login for each Reporting Services service account and permissions are assigned. Integrating a Reporting Services report server with a SharePoint Web application requires that the report server be able to access the SharePoint configuration and content databases. Both the Report Server Web service and Report Server Windows service must be able to connect as trusted users with read and write permissions.
   
   
   1. Specify the name of the report server. Unless you modified the registration properties, this value is the name of the computer.
      
      
   2. Specify whether the instance is the default instance or a named instance. If you are not sure, start the Reporting Services Configuration tool and connect to the report server. In the Instance Selection dialog box, expand Instance Name to view a list of the instances installed on the server. MSSQLSERVER is the name of the default instance. All other instances are named instances.
      
      
   3. Click OK. The Enter Credentials dialog box opens.
      
      
   4. In the Enter Credentials dialog box, specify the User Name and Password to connect to the report server to retrieve the Web service and Windows service accounts. Be sure to enter credentials for an account that is a member of the local Administrators group on the report server computer.
      
      
6. In the Reporting Services section, click Set server defaults to optionally set values to limit report history, enable logging, and set a report processing time-out. For more information about these options, click Help.
   
   

Uninstalling the Reporting Services Add-in requires that the Windows SharePoint Services or Office SharePoint Server 2007 installation still exists. If you uninstall the SharePoint product or technology first, you must reinstall it in order to uninstall the Reporting Services Add-in.

You can uninstall the Reporting Services Add-in by running Setup in uninstall mode. Uninstalling the add-in will remove server integration features that are used to process reports and models on a report server. Setup does not delete files that you created or uploaded to a library, nor does it delete schedules, subscriptions or report history. Consider deleting these items before uninstalling the add-in. You should also delete the SharePoint database logins that were created for the Reporting Services service accounts.

1. Remove any reports and other report server items that you no longer use. They will not run after the Add-in is removed.
   
   
2. In Control Panel, in Add and Remove Programs, select Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies.
   
   
3. Click Remove.
   
   

[Top]

This section summarizes the available features when you run a report server in SharePoint integrated mode.:

• Use the revised Reporting Services Configuration tool to create a report server database in SharePoint integrated mode.
  
  
• Use the new report server configuration pages in Central Administration to grant the service accounts access to the SharePoint configuration and content databases.
  
  
• Use SharePoint security to control access to report server content and operations.
  
  
• Add reports and models that you created in SQL Server 2005 Reporting Services design tools to a SharePoint library. You can publish reports from Report Designer, or use the Upload action on a SharePoint library to upload any report server item. If you publish the files, be sure to specify fully qualified URLs. An example URL for a file uploaded to Shared Documents on the top-level site of a SharePoint Web application might be http://example-server-name/Shared Documents/CompanySales.rdl. The URL must include a file extension. If the library is on a site, you must also include any sites and subsites before the library. For more information, see "Deploying Reports, Models, and Shared Data Sources to a SharePoint Site" in SQL Server Books Online.
  
  
• Create new shared data source (.rsds) files from a SharePoint site to use with the reports and models that you add to a library. A new file extension named .rsds is introduced in this release; it is used for shared data source files that you create and store in a library.
  
  
• Use the new Report Viewer Web Part to view reports.
  
  
• Use Report Builder from a SharePoint site. You can open or modify an existing Report Builder report definition file from a library. You can load a model in Report Builder to create new reports from report model (.smdl) files that have been uploaded or published to a SharePoint library.
  
  
• Use new Web pages and configuration options to set permissions and properties on reports (.rdl), models (.smdl), resources, and shared data sources (.rsds) you add or create on a SharePoint site. You can also use Web application pages to define schedules and subscriptions.
  
  

This section describes known issues in this release for the Reporting Services Add-in. For more information about known issues for SP2, see the SP2 readme.

This section contains updated documentation.

Currently, there are no items for this section.

[Top]