Technics:Reporting Services Integration
Installation
The CoPlanner Reporting Services Integration (CRSI) is located in the directory execute\Reporting and consists of two components:
- A server component which must be installed on the report server.
- A client component which must be installed on the client computer (only if report creating and editing using Business Intelligence Development Studio (BIDS) will be done).
The setups for both components must be executed with administrator rights.
Server Component Setup
The server component has to be installed using ReportServerConfigurator.exe which must be executed on the report server. The setup will verify the integrity of the files located in the DataExtension-directory, recognize al locally installed report servers (using the registry) and install the extension
If there are several local report servers the default instance resp. first instance (order appearing in the registry) will be chosen. The setup will only take configured instances into account. Using command line arguments other instances can be selected. Command line arguments can start with / or
| Argument | Description |
| autoinstall | Start installation after launching setup |
| autoquit | Quit setup after successfull (!) installation |
| instance | Instance selection (the next argument must define the report server’s instance name) |
| ? | Show help |
| help | Show help |
An example for automatic installation for instance SQL2008:
ReportServerConfigurator –autoinstall –autoquit –instance SQL2008Client Component Setup
The client component hast do be installed using BiStudioConfigurator.exe, which must be executed on each PC which will be used for designing reports using BIDS. The setup will verify the integrity oft he files in the DataExtension- and QueryDesigner-directory, recognize locally installed Visual Studio versions (using the registry) and install the extension.
If several versions of Visual Studio exist, the first one with an report designer extension will be chosen (in order 2005, 2008 and 2010. Using command line arguments other versions can be selected. Command line arguments can start with / or –.
| Argument | Description |
| autoinstall | Start installation after launching setup |
| autoquit | Quit setup after successfull (!) installation |
| version | Version selection (the next argument must specify the Visual Studio version number) |
| ? | Show help |
| help | Show help |
An example for automatic installation for Visual Studio 2008 (9.0):
BiStudioConfigurator –autoinstall –autoquit –version 9.0Manuel Installation
The steps for manual installation are described in the following document and its references: http://msdn.microsoft.com/en-us/library/ms155104.aspx
You have to add following extension in file RSReportServer.config in section Data:
<Extension Name="CoPlanner" Type="Cop.Reports.DataExtension.CopConnection,Cop.Reports.DataExtension"/>
You have to create a codegroup with FullTrust-rights in file rssrvpolicy.config:
<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Name="CoPlannerCodeGroup" Description="CodeGroup for CoPlanner DataExtension"/> <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Cop.Reports.DataExtension.dll"/>
On the client computer you have to add the extendion in the Data-section and the query designer in the Designer-section in file RSReportDesigner.config:
<Extension Name="CoPlanner" Type="Cop.Reports.DataExtension.CopConnection,Cop.Reports.DataExtension"/> <Extension Name="CoPlanner" Type="Cop.Reports.QueryDesigner.CopQueryDesigner,Cop.Reports.QueryDesigner"/>
You have to create a codegroup with FullTrust-rights in file rspreviewpolicy.config:
<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Name="CoPlannerCodeGroup" Description="CodeGroup for CoPlanner DataExtension"/> <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Programme\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Cop.Reports.QueryDesigner.dll"/>
Configuration
ReportServerSettings.xml
This file contains settings for the CoPlanner Reporting Services Integration. Figure below shows all available settings and their default values. All additional elements will be ignored.
<?xml version="1.0" standalone="yes"?>
<ReportServerSettings.xml>
<ReportServerSetting>
<ReportServerUrl>http://servername/reports</ReportServerUrl>
<ReportWebServiceUrl>http://servername/reports/reportingservice2005.asmx</ReportWebServiceUrl>
<UserName></UserName>
<Password></Password>
<Domain></Domain>
<RootFolder>/CoPlanner/Reports</RootFolder>
<Parameters></Parameters>
</ReportServerSetting>
</ReportServerSettings.xml>
<ReportServerUrl>
(required) The report server’s virtual directory
<ReportWebServiceUrl>
(required) SOAP endpoint for managing objects in the report server.
<RootFolder>
(required) Root folder for reports on the reportserver.
<UserFolder>
(optional) Folder for reports which will be created using the report assistant in the BI-Center. If this folder is missing or empty the root folder will be used.
<TempFolder>
(optional) Folder for reports which will be created using the report assistant in the Analyzer. If this folder is missing or empty the root folder will be used.
<SharedDataSourceReference>
(optional)
Path and name to an existing data source on report server, which is used by the report assistent to create a nre report. Is this tag missing, the report assistant creates an embedded data source. The report builder can show no preview for reports with an embedded data source.
The path specified in <UserFolder> and <TempFolder> can contain variables. Table below shows the available variables.
| Variable | Description |
{USERNAME} |
CoPlanner-User (without domain, special characters will be replaced with _) |
The following points must be taken into account:
- If any of the required elements is missing or empty all reporting functions in the CoPlanner client will be disabled or hidden.
- The server name in the URLs must not be localhost.
- The folders on the report server won’t be created automatically.
- The variable names are case-sensitive.
Data Processing Extension (DataExtension)
You can cinfugure the data processing extension in configuration file RSReportServer.config and RSReportDesigner.config. The following figure shows all kinds of options with their default values. All elements and attributes are optional, that means if they are missing, the default value will be taken.
<Extension Name="CoPlanner" Type="...">
<Configuration>
<Connection LogLevel="ErrorWarning"/>
<Connection LogLevel="ErrorWarning" TimeOut="10000"/>
<Reader LogLevel="ErrorWarning"/>
<CopApiClientStore LogLevel="ErrorWarning" EntryLifeTime="30000"/>
<Session ConnectTimeOut="2000" ConnectMaxAttempts="5" DisConnectTimeOut="2000"/>
<Kerberos SPN=""/>
<ServerCommandLog Active="False" Path=""/>
</Configuration>
</Extension>
LogLevel=""
The attribute LogLevel defines the granularity for logging of the component. All messages are logged, with a smaller or equal granularity of the configured granularity. Following table shows the available steps.
| Level | Description |
| None | NoLogging |
| Error | Error message |
| Warning | Error message and warning |
| ErrorWarning | Compatibility to previous versions |
| Info | Additional state messages |
| Verbose | Extended Logging |
Log-file coprsint.log will be written in the temporary user folder of the report server. The report server generally use the folder C:\Windows\Temp, and for BIDS (Windows 2003 Server) the folder C:\Documents and settings\username\Lokale Einstellungen\Temp
TimeOut=""
The following table shows the available time specifications (in millisecond) and their lower and upper limits.
| Element | Attribut | Min | Max | Standard |
| Command | TimeOut | 100 | 10000 | |
| CopApiClientStore | EntryLifeTime | 100 | 120000 | 30000 |
| Session | ConnectTimeOut | 100 | 2000 | |
| Session | DisConnectTimeOut | 100 | 2000 |
The TimeOut-Attribute controls the time, within the command has to be executed by the CoPlanner server. The EntryLifeTime–Attribut defines, within which time span a connection has to be reused by the data extension.
ConnectMaxAttempts=""
This attribute defines the maximum number of connection attempts to the CoPlanner server. The minimum value is 1.
<ServerCommandLog Active="False" Path=""/>
Using this option the logging of the CoPlanner server commands can be activated. In this case each request to the CoPlanner server and its answer will create a file with the following file name pattern:
Counter-Command-anfrage.xml (for requests) bzw. Counter-Command-ergebnis.xml (for answers answers)
Counter is a consecutive numbering of the commands.By default the files will be put into the report server’s bin-directory (the clCop_ClientProxy-class’ default path is the path of the binary).
<Kerberos SPN=""/>
Defines the Service Principle Name (SPN) if Kerberos authentication must be used
