Installing and Upgrading Reports

The iService Reports Publisher Script automates deployment of iService reports to a SQL Server Reporting Services (SSRS) server.  Since it depends on the RS utility to function, this script package requires Reporting Services to be installed on the local computer.

To check if the RS utility is installed, type this at the command prompt:

where rs.exe

If a path is output similar to below, the script can be run.  Otherwise, SSRS must be installed first:

C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\rs.exe

Requirements:

SQL Server Reporting Services 2008 R2, 2012, or 2014.

NOTE: Please see the addendum for specific requirements before running the "Topic Service Level for Operating Hours" reports.

Setup Instructions:

1. If necessary, setup and configure your SSRS server.  For more information, refer to Microsoft’s SSRS documentation.

2. Extract contents of the iService Reports zip file to a computer with SSRS installed (the zip is obtained from the iService Software Download page).

3. Configure the parameters in the deployreports.bat for your deployment environment.

4. Run deployreports.bat

Configuration Parameters:

The following configuration parameters can be set in the deployreports.bat script file.

TargetURL: The location of the Web Services for your SSRS server.  For more information on configuring SSRS Web Service locations, please refer to the Microsoft documentation.

Example 1 (Script run on report server): http://localhost/ReportServer

Example 2 (Script run on external server): https://www.mydomain.com/ReportServer

TargetFolder : The folder on the report server where the script will create the child folder (ReportFolderName).   Generally this will be the root folder on the report server.

Example:  /

 

ReportFolderName: The folder name on the report server where reports will be published to, and the name of the folder on the local computer where the reports that will be published currently reside.  By default, this is ‘iServiceCRM’.  If this is changed, you will also need to change the local folder name for the script to find it. If this folder doesn’t exist on the server, it will be created by this script. The full path of the published report will be TargetFolder + ReportFolderName + Report

Example:  iServiceCRM

 

DataSourceFolder: The data source folder on the report server.

Example: /Data Sources

 

DataSourceFolderName: The folder name on the report server where data sources are published.

Example: Data Sources

UserName: The username to authenticate to the report server to publish reports.  This username should have appropriate access rights to the TargetFolder.

Password: Password to authenticate to the report server.

ReportFolder: The name of the folder on the local computer where the ReportFolderName resides.  Generally this is the same location as the script and won’t need to be modified.

Example (for current script folder – extra backslash necessary for escaping): .\\

------ The following parameters define the data source that is generated for the reports -----

DataSourceName:  The name of the data source connection for all reports.  This will be created in the DataSourceFolder folder on the report server.

ServerName: The name of the SQL server instance that the reports will run against.

DataBaseName: The name of the database on the SQL server that the reports will run against.

dsUserName: The user to authenticate as on the SQL server when running reports.

dsUserName: The password to authenticate with.

© 2019 One-to-One Service.com, Inc.