Disclaimer
Your use of this download is governed by Stonebranch’s Terms of Use, which are available at https://www.stonebranch.com/integration-hub/Terms-and-Privacy/Terms-of-Use/.
Overview
This document provides a documentation how to install and use the Universal Tasks for SQL Server Reporting Services.
The here described Universal Task calls a script to deploy a report on the Reporting Services Webserver.
This Universal Task is based on the SQL Server Reporting Services RS.EXE utility. RS.EXE is a command line utility that can perform many
scripted operations related to SQL Server Reporting Services (SSRS). It can be used to complete various administrative tasks including
publishing reports and moving reports from one server to another server. The RS.exe utility requires an input file to tell the RS.EXE
"what to do". The list of actual tasks that can be performed is includes among others:
- Deploying / Publishing reports
- Moving reports
- Exporting reports to a file
- Adjust security
- Cancel a running job
- Configure SSRS system properties
The here described Universal Task calls a script to deploy a report (#1 in the list above). Points 2-6 in the list above can also be implemented via a script called by the Universal task.
Note: Further details on the RS.exe utility can be found in the referenced document [1].
System Set-up
Universal Task name: Run SAP Data Service Job Related UAC XML Files for template and task: [2]
Software used:
- MS SQLSERVER 2016
- Report Builder in SQL Server 2016
- Windows Server 2012R2
- UAC 6.4 Build 40 (beta-release)
- UA 6.3.0.1 installed on the SAP Data Services Server
Proposed enhancements
A) A script for all possible RS.EXE scenarios should be generated:
- Deploying / Publishing reports (done)
- Moving reports
- Exporting reports to a file
- Adjust security
- Cancel a running job
- Configure SSRS system properties
B) Deploy reports using a SOAP Webservice
In the referenced document [1] the command to deploy a report via a SOAP webservice is described. This solution has the advantage that no Universal Agent would have to be deployed on the SQLSERVER.
Solution Description
The following describes how the Universal Task can be demonstrated, once it is set-up on the Stonebranch demo system.
1. Configure a new Report using Report Builder in SQL Server 2016
The report configuration is written to the file system as *rdl file e.g.: rechnunsdaten.rdl
2. Test the Report in Report Builder in SQL Server 2016
Once it is tested in Report Builder in SQL Server 2016, you can deploy the report to the Reporting Server using Universal Task.
3. Configure the universal task deploy a Reporting to the Reporting Server
Universal Task template
Reporting Service Script to deploy a report:
Universal Template fields:
Universal Task
Dscription:
- REPORTNAME for the actual name of the report (=report file) to be deployed
- REPORTSERVER_FOLDER which describes the folder where the file should be deployed to (reportingserver webfolder)
- FILEPATH denotes the location of the rdl file.
4. Verify job execution in SAP Data Service Management Console
Log-On to the Reporting Webserver and check that the report has been deployed (see Universal Task Parameter reportserver): WALLDORF.
e.g. http://walldorf/Reports/browse/ (user:admin/Porsche944)
Browse to the folder, where the report should be deployed (see Universal Task Parameter: REPORTSERVER_FOLDER): /myreports
Document References
This document references the following documents: