1. In Administrator Tools, click SharePoint 3.0 Central Administration.

2. Click the Application Management tab.

3. In the Reporting Services section, click Manage integration settings. If the Reporting Services section is not available, the Reporting Services Add-in must be downloaded and installed.

   1. In Report Server Web Service URL, specify the report server that you are integrating with the SharePoint deployment. This URL identifies the report server site that is used 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. Examples of how a report server URL might be constructed include:
      
   • http://your-server-name/reportserver (this example might be used if the report server is on a different computer).
     
   • http://your-server-name:8080/reportserver (this example might be used if the report server is on the same computer as the SharePoint deployment that you are integrating and you mapped the default Web site to port 8080)
     
   • https://your-server-name:443/reportserver
     If you installed the report server and the SharePoint technology instance side-by-side, and the SharePoint technology instance is using default values, port 80 will be used to access the top-level SharePoint site. When you install the report server on the same Web server, you must either assign and use a different port number on the default Web site, or create the report server virtual directory under a custom Web site that is uniquely identified through a port number, IP address, or a host header. For more information about report server URLs and the virtual directory, see Configuring Report Server Virtual Directories.
     

4. 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 and permissions is created for each Reporting Services service account. 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. By default, this 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.
      

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

   1. In Report History Default, 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
      
   2. 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. When you set this value, specify enough time to complete both data processing and report processing.
      
   3. In Report Processing Log, specify whether the report server generates trace logs and the number of days the log is kept. You can specify whether the report server generates trace logs and the number of days the logs are kept. The logs are stored on the report server computer in the \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 Reporting Services Trace Logs.
      
   4. 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.
      
   5. In Enable 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 clickthrough reports for reports that use a report model as a data source.
      
   6. Click OK.
      

Concepts

Other Resources