Qlik integration preflight checks

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

In your Qlik environment

To establish a secure connection between Edge and Qlik, ensure that you have the client ID and client secret of your OAuth client in Qlik, and provide them when creating a Qlik connection.

If you do not have an OAuth client, follow the steps in Creating and managing OAuth clients in the Qlik documentation. When creating the OAuth client, use the following settings:

  • Select Web for the client type.
  • Select one of the following scopes based on your company policy.
    • admin_classic. This scope might provide more complete lineage.
    • user_default.
  • Select the Allow Machine-to-Machine (M2M) checkbox.
  • Change the consent method to Trusted.

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 a Qlik connection:

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

To add an Edge capability:

To synchronize technical lineage: