Reporting Services configuration. If your
MOSS Web application uses the default port 80,
which is the case for a default MOSS configuration,
you must reassign the Web site that's hosting
the Report Server Virtual Directory to an unused
port, such as 8080, and be sure that Web site is
started in IIS. To reassign the report server's Web
site port, open Internet Information Services
(IIS) Manager in the Administrative Tools program
group, expand the server hosting SSRS, and
expand the Web Sites folder. Right-click the Default
Web Site (or the Web site you've assigned
the SSRS virtual directories to), and click Properties. In the Default Web Site Properties dialog
box, on the Web Site tab, type the number of the
unused port in the TCP port box. Keep the dialog
box open for subsequent steps.
Next, verify authentication on the Web site
to ensure that anonymous access is disabled
and that integrated Windows authentication is
enabled. In the Default Web Site Properties dialog
box, click the Directory Security tab. In the
Authentication and access control section, click
the Edit button. In the Authentication Methods
dialog box, clear the Enable anonymous access
check box and select the Integrated Windows authentication
check box.
Last, revise the RSReportServer.config file
(which you can find at Program Files\Microsoft
SQL Server\MSSQL.n\Reporting Services\ReportServer)
by changing the URLRoot property
to include the port number (e.g., http://your_server:8080/reportserver); this provides the correct
link to reports in email subscriptions. Before continuing,
restart IIS, and then test the URL in your
browser to make sure SSRS works correctly.
Setting Up Integrated Mode
You're now ready to prepare the report server for
integrated mode. First, use the Reporting Services
Configuration Tool to change the Windows
Service Identity and Web Service Identity to use
a domain user account if the MOSS databases
are on the same machine as the report server in
a remote SQL Server deployment. Start the Reporting
Services Configuration Tool by clicking
Start, pointing to All Programs, Microsoft SQL
Server 2005, Configuration Tools, and clicking
Reporting Services Configuration. Select the correct
SSRS instance by specifying the report server
name and selecting the SSRS instance when
prompted, then click Connect. Click Windows
Service Identity in the left pane of the configuration
tool's window, then select Windows account,
provide the domain username and password created
as explained in the earlier Installation Prerequisities
section, and click Apply.
To change the Web Service Identity, you
use IIS Manager, but first confirm the application
pool that SSRS is using. Click Web Service
Identity in the left pane of the Reporting Services
Configuration Tool, and in the drop-down
list next to Report Server, note the name of the
application pool. Don't worry about the Report
Manager application pool's identity because you
won't use it after you switch the report server to
integrated mode. Keep the configuration tool
open, and switch to IIS Manager. Expand the
server hosting SSRS, expand the Application
Pools folder, right-click the application pool you
identified for Report Server in the configuration
tool, click Properties, and click the Identity tab.
Select Configurable, provide the domain username
and password, and click OK. Remember
that this step is necessary only for a remote SQL
Server deployment.
To convert the report server to integrated
mode, switch back to the Reporting Services
Configuration Tool, click Database Setup in the
left pane, connect to the database server, then
click Change. Click Yes to confirm the request
to change the report server mode. In the resulting
SQL Server Connection dialog box, provide
a new report server database name, confirm that
the Create the report server database in Share
Point Integrated mode check box is selected, as Figure 2 shows, and click OK. At the bottom of
the Database Setup
page, click Apply,
and then click OK
to confirm the credentials
used to finalize
the database.
The Report Manager
Virtual Directory
page in the
Reporting Services
Configuration Tool
is now disabled because
the report
server is in integrated
mode. Also notice
the red status icon
next to the Share-
Point Integration link in the left pane. This icon
means SharePoint Integration is not configured.
The status will change to Configured (a green
icon) after you configure the MOSS server for integration,
which I cover next.
Before closing the Reporting Services Configuration
Tool, make sure you back up the encryption
key. You'll need the encryption key backup
if you ever need to restore the report server databases.
Without this backup, after restoring the
report server databases, you must delete encrypted
data such as data sources or user information
because there would be no way to decrypt it. To
create the backup, click Encryption Keys in the
left pane, click Backup, and type a password.
Click the ellipsis button to the right of the Key
File box, and then in the Save As dialog box,
navigate to a secure folder or removable media
location, provide a file name, and click Save.
A common question from report server administrators
planning to convert an existing SSRS server from native to integrated mode is
how to migrate the existing report server contents.
Unfortunately, there's no migration utility
to transfer the contents of the native mode
report server database to the integrated mode
version of the database. Instead, you have to redeploy
existing reports to the MOSS server and
reconfigure execution and security settings of
each report in MOSS.
Installing and Configuring the
SSRS Add-in on the MOSS Server
Now, you're ready to install the SSRS add-in on
the MOSS server. If you have a MOSS farm, you
must install the add-in on all Web front-end servers
in the farm except the report server. When
you've updated all the servers, you can configure
SSRS integration in MOSS. Remember from Table
2 that you must use a domain user account that has MOSS farm administrator and site collection
administrator privileges to perform this task. To
begin the SSRS configuration, click Start, point
to All Programs, point to Microsoft Office Server,
and click SharePoint 3.0 Central Administration. Click the Application Management tab. The addin
has updated this page to include a Reporting
Services section. Click Manage integration settings
to specify the URL for the report server
(e.g., http://your_server:8080/reportserver) and
set the authentication mode, as Figure 3 shows.
Click OK when finished. (For information about
which authentication mode to use, see the Web
sidebar "The Differences Between Authentication
Modes," InstantDoc ID 96842.)
On the Application Management page, click
Grant database access. Provide the report server
name and instance in preparation for granting
permissions to the SSRS Windows and Web
services to access the MOSS databases. After
you click OK, you're prompted for report server
administrator credentials. If you have trouble
here, you might need to reapply the settings on
the Windows Service Identity and Web Service
Identity pages of the Reporting Services Configuration
Tool. After you properly configure the
service accounts, the status of SharePoint Integration
in the Reporting Services Configuration
Tool should be Configured (green).
Optionally on the Application Management
page, you can click Set server defaults to provide
default settings for report history and logging in
the Reporting Services Server Defaults page, as Figure 4 shows. If an error displays when you
try to open this page, make sure you've created a
Web application and site collection. Also be sure
you're logged in using a site collection administrator
account. Finally, be aware that sometimes
the configuration changes you make in the Reporting Services section require a restart of
IIS before you can open the Reporting Services
Server Defaults page.
Your next step is to configure Component
Services with the correct permissions for the
SSRS Web Service Identity to activate MOSS.
On the MOSS server, click Start, point to Administrative
Tools, click Component Services,
and then expand Computers, My Computer,
DCOM Config. Right-click IIS WAMREG
Admin Service, and click Properties. On the
Security tab, click the Edit button for Launch
and Activate Permissions. Click Add and type
the built-in account or domain user account you
assigned to the Report Server application pool.
Alternatively, you can click the Advanced button
to search for and select the account. After
you add the account, highlight it in the Group or
user names list in the Launch Permission dialog
box, then select the Local Activation check box
in the Allow column. Click OK twice to close all
dialog boxes and save the permission changes.
Last, update the document libraries in the
MOSS Web application to use the SSRS content
types. You can make these changes to any document
library in your MOSS Web application, but
I limit my explanation to the Reports and Data
Connections libraries that are part of the standard
Report Center site. In Internet Explorer
(IE), navigate to the Reports document library
in your MOSS Web application. For example, if
the URL you assigned to the Web application
is http://your_server/sites/Reports, go to http://your_server/sites/Reports/ReportsLibrary to open
the Reports library. On the Settings menu, click
Document Library Settings. In the Content Types
section, click Add from existing site content types.
In the Available Site Content Types list, select Report
Builder Report, click Add, and click OK.
Report Center includes the Data Connections
library to restrict access to data source files and
related management tasks. To add the SSRS content
types for data sources, open the library, and
repeat the steps you followed to add report content
types, except select Report Data Source.
You can add the Report Builder Model content
type to either the Reports library or the Data
Connections library. I find it easier for users to
use a report model if it's in the same library as the
Report Builder Report content type; the Report
Builder application displays a list of all models
in the same library in which the user creates the
new Report Builder Report. If the model is in a
different library, the user must click the default
library link in the Getting Started pane of Report
Builder, must know which MOSS library
contains the desired model, and must navigate
to that location.
Successful Configuration
By following these steps, you have successfully
installed and configured the components required
to integrate SSRS with MOSS Enterprise
Edition. (For more information about these
steps, see the Microsoft resources listed in the
Learning Path at InstantDoc ID 96840.) In the
second article in this series, I'll show you how
to perform familiar SSRS tasks, such as deployment,
security implementation, and property
management, in the new MOSS environment.
I'll also show you how to take advantage of new
features enabled by MOSS, such as versioning,
workflow, alerts, information management policies,
and how to achieve BI information integration
with SSRS and MOSS.
End of Article
Prev. page
1
2
[3]
next page -->
