SSRS Resource Configuration
Source System Properties
This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI > Connections > Reporting & BI > SSRS > specific connection. New connection can also be created via Manta Orchestration API General Walkthrough Example.
One IBM Automatic Data Lineage connection for SSRS corresponds to one SSRS server and the filter of its reports that will be analyzed.
This automatic extraction requires either a connection to the SSRS Web Service or to the Microsoft SQL server used by the SSRS server for storing report definitions.
Common Source System Properties
|
Property name |
Description |
Example |
|---|---|---|
|
ssrs.extractor.server |
Name of a resource representing this SSRS server also known as the dictionary ID, used as an output subdirectory name for extracted definition files for reports and other objects |
DWHBI |
|
ssrs.extractor.mode |
Determines how to extract SSRS metadata (through a REST API of the SSRS server or directly from the MS SQL database)—see below for details |
REST DATABASE |
|
ssrs.extractor.include |
Regular expression used to include reports (or other objects) in the extraction. It is matched up with the full path of the item, including directories on the SSRS server in the form of a directory/report. It is ignored if left blank. (Check SSRS Include/Exclude Options for more info) |
|
|
ssrs.extractor.exclude |
Regular expression used to exclude reports (or other objects) from extraction. It is matched up with the full path of the item, including directories on the SSRS server in the form of a directory/report. It is ignored if left blank. (Check SSRS Include/Exclude Options for more info) |
|
|
ssrs.input.encoding |
Encoding of automatically extracted SSRS reports and other object definitions. See Encodings for applicable values. |
UTF-8 |
|
ssrs.extractor.ssl.enable |
Enable encrypted communication (TLS) with the server |
true false |
|
ssrs.extractor.ssl.hostNameInServerCertificate |
JDBC extraction only Use an arbitrary host name (instead of serverName) for server certificate validation |
myserver.mydomain.com |
|
ssrs.extractor.ssl.trustServerCertificate |
When set to true, skips validation of the server certificate For JDBC extraction: Automatically trust server certificate, skip all validations For REST extraction: Skip hostname validation |
true false |
|
ssrs.extraction.method |
Set to Agent:default when the desired extraction method is the default Manta Extractor Agent, set to Agent:{remote_agent_name} when a remote Agent is the desired extraction method, set to Git:{git.dictionary.id} when the Git ingest method is the desired extraction method. For more information on setting up a remote extractor Agent please refer to the Manta Flow Agent Configuration for Extraction documentation. For additional details on configuring a Git ingest method, please refer to the Manta Flow Agent Configuration for Extraction:Git Source documentation. |
default Git agent |
In REST Extraction Mode
This is the preferred approach, available for SSRS version 2017 and newer.
Applicable properties:
| Property name | Description | Example |
|---|---|---|
| ssrs.extractor.mode | Set to REST to use the REST extraction mode |
REST |
| ssrs.extractor.address | Address of the SSRS Web Service to extract metadata from | 192.168.0.16 |
| ssrs.extractor.port | Port where SSRS Web Service listens for connections | 80 |
| ssrs.extractor.scheme | Scheme used to connect to the SSRS Web Service | http |
| ssrs.extractor.user | Name of the SSRS Web Service user | ssrs_user |
| ssrs.extractor.password | Password of the SSRS Web Service user | ssrs_password |
Using DATABASE Extraction Mode
Automatic Data Lineage can connect directly to the MS SQL database used by SSRS to store published reports. However, this approach may download out-of-date information for data source definitions if they were modified using SSRS Web GUI after publication.
The underlying database must be accessible from the computer where Automatic Data Lineage is running.
Applicable properties:
|
Property name |
Description |
Example |
|---|---|---|
|
ssrs.extractor.mode |
Set to |
DATABASE |
|
ssrs.dbExtractor.url |
JDBC connection string for the underlying database |
jdbc:sqlserver://192.168.0.16:1433 |
|
ssrs.dbExtractor.authenticationType |
Authentication type to use; see MS SQL Server Authentication Types for a description of the options |
SQL Server |
|
ssrs.dbExtractor.domain |
The Windows domain to authenticate to when using NTLM authentication |
example.com |
|
ssrs.dbExtractor.user |
Name of the database user |
ssrs_user |
|
ssrs.dbExtractor.password |
Password of the user |
ssrs_password |
|
ssrs.dbExtractor.defaultCatalog |
Name of the catalog where SSRS reports are stored |
ReportServer |
Common Scanner Properties
This configuration is common for all SSRS source systems and for all SSRS scenarios, and is configure in Admin UI > Configuration > CLI > SSRS > SSRS Common. It can be overridden on individual connection level.
|
Property name |
Description |
Example |
|---|---|---|
|
ssrs.input.dir |
Directory with files extracted from the SSRS server |
${manta.dir.temp}/ssrs/${ssrs.extractor.server} |
|
filepath.lowercase |
Whether paths to files should be lowercase (false for case-sensitive file systems, true otherwise) |
false |