Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt

Use this file to discover all available pages before exploring further.

In this section, we provide guides and references to use the SSRS connector. Configure and schedule SSRS metadata workflows from the OpenMetadata UI:

​
How to Run the Connector Externally

To run the Ingestion via the UI you’ll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment. If, instead, you want to manage your workflows externally on your preferred orchestrator, you can check the following docs to run the Ingestion Framework anywhere.

External Schedulers

Get more information about running the Ingestion Framework Externally

​
Requirements

The SSRS connector uses the SSRS REST API (v2.0) and authenticates via Windows Authentication (NTLM). The account used must have at minimum Browser role on the SSRS Report Server to list folders and reports.
The SSRS REST API (v2.0) requires SQL Server Reporting Services 2017 or later. Older SSRS versions using SOAP-based web services are not supported.
To grant the required role:
  1. Open the SSRS Web Portal.
  2. Navigate to Site Settings → Security → New Role Assignment.
  3. Add the service account and assign the Browser role.

​
Python Requirements

We have support for Python versions 3.9-3.11
To run the SSRS ingestion, you will need to install: 
pip3 install "openmetadata-ingestion[ssrs]"

​
Metadata Ingestion

All connectors are defined as JSON Schemas. Here you can find the structure to create a connection to SSRS. In order to create and run a Metadata Ingestion workflow, we will follow the steps to create a YAML configuration able to connect to the source, process the Entities if needed, and reach the OpenMetadata server. The workflow is modeled around the following JSON Schema

​
1. Define the YAML Config

​
2. Run with the CLI

First, we will need to save the YAML file. Afterward, and with all requirements installed, we can run: 
metadata ingest -c <path-to-yaml>
Note that from connector to connector, this recipe will always be the same. By updating the YAML configuration, you will be able to extract metadata from different sources.