Extending Reporting Services - Professional SQL Server 2005 Reporting Services - page 576

The directory that you will install the extension into is the bin directory of the report server: InstallPath\
MSSQL.3\Reporting Services\ReportServer\bin . Copy your custom data processing extension
assembly into this directory. The extension is now in the correct location, but you need to inform Reporting
Services of its presence. This is done by editing the configuration file that Reporting Services uses for its set-
tings. This file is called RSReportServer.config and is located in the parent directory. Open this file and
look for the <Data> section. Within this section, you should see entries similar to the following:
<Data>
<Permissions>
<PermissionSet class=”System.Security.NamedPermissionSet” version=”1”
Unrestricted=”true” Name=”FullTrust”
Description=”Allows full access to all resources”/>
</Permissions>
<Extension Name=”SQL”
Type=”Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapper,
Microsoft.ReportingServices.DataExtensions”/>
<Extension Name=”OLEDB”
Type=”Microsoft.ReportingServices.DataExtensions.OleDbConnectionWrapper,
Microsoft.ReportingServices.DataExtensions”/>
<Extension Name=”ORACLE”
Type=”Microsoft.ReportingServices.DataExtensions.OracleClient
ConnectionWrapper,Microsoft.ReportingServices.DataExtensions”/>
<Extension Name=”ODBC”
Type=”Microsoft.ReportingServices.DataExtensions.OdbcConnection
Wrapper,Microsoft.ReportingServices.DataExtensions”/>
<Extension Name=”DATASET”
Type=”Wrox.ReportingServices.DataSetDataExtension.DataSetConnection,Wrox.ReportingS
ervices.DataSetDataExtension”/>
</Data>
Add the DataSet entry that you see in the highlighted code snippet. The Name tag is the unique name you
want users to see when they select your extension. The Type element contains the entry point for your
extension (the first object created and the one that is required to implement the IExtension interface),
followed by the fully qualified name of your extension. Save the file. Reporting Services will now recognize
your extension, but you must change the security policy to give the extension the permissions that it needs
to do its job.
Server Security configuration
The security policy file is located in the same directory as the server configuration file. Simply locate the
file called rssrvpolicy.config . This file contains the security policy information for SSRS, and an
entry should be made that looks similar to the following:
</CodeGroup>
<CodeGroup class=”UnionCodeGroup” version=”1” PermissionSetName=”FullTrust”
Name=”WroxSRS” Description=”Code group for my DataSet data processing
extension”>
<IMembershipCondition class=”UrlMembershipCondition”
version=”1”Url=”C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\Wrox.ReportingServices.DataSetDataExtension.dll” />
</CodeGroup>