SSRS-PBRS integration preflight checks

To ensure successful metadata ingestion and lineage generation, complete the following preflight checks.

In your SQL Server Reporting Services and Power BI Report Server environments

Collibra Data Lineage uses REST API version 2.0 to ingest SQL Server Reporting Services (SSRS) and Power BI Report Server (PBRS) metadata. You need at least the minimum permissions in SSRS-PBRS to enable Collibra Data Lineage to access the SSRS-PBRS metadata and ingest it in Data Catalog.

Important There are known limitations to the metadata returned by the API when integrating PBRS. For example, Power BI reports in PBRS are ingested as Power BI Report assets in Data Catalog, but there is no technical lineage for the reports.

Use SQL Server 2019 Reporting Services or newer. We can't guarantee that older versions will work.

Minimum roles and permissions

  • You need the following roles, with user access to the server from which you want to ingest:
    • A system-level role that is at least a System user role.
    • An item-level role that is at least a Content Manager role.
      If your SSRS environment does not use permission inheritance, assign the item-level role to each folder in the folder hierarchy that you want to ingest. Otherwise, folders without explicit permissions are not returned by the API and are not ingested.
  • The following item-level roles in SSRS provide the required access to content in SSRS-PBRS.
    Item-level roleSupported content
    Content ManagerAll supported SSRS content.

    Publisher

    All supported SSRS content.

    Report Builder

    Only the content contained in your paginated reports.

    My Reports

    Only the content in the My Reports folders that you own.

  • For full access to the Report Server and its content, assign both a system-level role, such as System Administrator, and an item-level role, such as Content Manager.

In your Collibra environment

Lineage enablement

  • Technical lineage via Edge is enabled in your Collibra environment.

Edge

  • You either created and installed an Edge site or were granted a Collibra Cloud site.
    Important If you're using a Collibra Cloud site, go the Collibra Cloud site documentation to check if your data source is supported.
  • The Edge site status must be Healthy.

Network and proxy configuration

  • Edge can connect to all Collibra Data Lineage service instances in your geographic location.
  • Optionally, you've connected to a proxy server.
  • Optionally, use a custom certificate to allow the Edge capability to connect to your data source. In this case, you've saved the certificate as "ca.pem" in the same directory as the Edge site installer. If you've saved the certificate in another directory, use the --ca argument in the Edge site installation command.

Collibra permissions

You can connect to Collibra Data Lineage by using the basic or OAuth authentication method. The following permissions are required only if you use the basic authentication method. 

To create a new target domain for asset ingestion:

To create an SSRS-PBRS connection:

  • You have a global role with the Product Rights > System administration global permission.
  • You have a global role that has the Manage Edge sites global permission.
  • You have a global role that has the Manage connections and capabilities global permission.
  • A resource role with Configure external systemresource permission, for example Owner.
  • If you want to add connection values from a vault, you have added the vault to your Edge site. If your data source connection requires a file from your vault, the file must be encoded into Base64 and stored as a regular secret in your vault. For more information, go to the Vault documentation.
    Note  Vaults are not supported on Collibra Cloud sites.

To connect to Collibra Data Lineage service instances via OAuth authentication:

To add an Edge capability:

To synchronize technical lineage: