TOPICA Report ReportReportingService |
[This is preliminary documentation and is subject to change.]
The ReportReportingService element is used to start Reporting Services Reports. I.e. it is used for integrating Reporting Services reports into a TOPICA application.
The ReportDefinition element (= the root in the TOPICA Reports XML format) can contain at most one ReportReportingService element.
When the ReportDefinition element contains a ReportReportingService element, all the
Attribute | Type | Description |
---|---|---|
Parameters | Boolean | Speficies whether the Reporting Services panel for entering parameters should be displayed. NB: The value true might compromise security! |
ReportName | String | The full path to the report in the report server. |
The ReportReportingService element does NOT specify environment specific settings like reference to reporting server, username / password used, etc. This is all set up in .config files (should be in Server.config). Specifically, these keys are used:
Key | Value |
---|---|
ReportingServicesServer | Name of server hosting the Reporting Services Instance. May contain embedded TOPICA Basic. If you use a Reporting Services instance hosted on the current database server, this value should be http://{db.server}. |
ReportingServicesInstanceReports | Name of the web home containining the Report Manager for the requested Reporting Services Instance. May contain embedded TOPICA Basic. If you use the convention, that the Reporting Services instances has same name as the database, this value could be for example http://{db.name}_Reports. Normally end users are NOT allowed to access to the Report Manager - this might compromize security. This setting is only used to let users with system administrator permission access Report Manager. |
ReportingServicesInstanceReportServer | Name of the webhome containining the Report Server (the "web services" web home) for the requested Reporting Services Instance. May contain embedded TOPICA Basic. If you use the convetion, that the Reporting Services instances has same name as the database, this value could be for example http://{db.name}_ReportServer. |
ReportViewerDomain | Domain for the user used to log in to the report server. |
ReportViewerUser | Username for the user used to log in to the report server. |
ReportViewerPassword | Username for the user used to log in to the report server. |
This ensures, that report defineiton files may be deployed in different environments without alteration. All environment-specific setting are set up in Configuration Files.