Configuring a new integration
This section shows you how to use the Integration configuration wizard to set up a new integration of Data Quality & Observability (self-hosted) metadata from profile findings, rules, and alerts into Collibra Platform.
Prerequisites
To use the SQL Assistant for Data Quality with an OAUTH-based Data Quality & Observability (self-hosted) integration with Collibra Platform, you must have Data Quality & Observability (self-hosted) version 2026.03 or later.
For the Integration API to run successfully, ensure that you review and meet the following criteria.
The most recent versions (recommended) of Data Quality & Observability (self-hosted) and Collibra Platform. For more information on versions, go to Supported versions.
You have an Admin role or a role mapped to specific connections in Data Quality & Observability (self-hosted) to use the configuration wizard.
You have an Admin or Dataset Manager role in Data Quality & Observability (self-hosted) to enable or disable individual datasets for integration.
Your Collibra Platform profile must have Sysadmin and DataSteward global roles to manage all assets and objects of the integration.
You have followed the steps on how to add Data Quality Rules to Assets in Collibra Platform.
You have an aggregation path set for your Data Quality Rule in Collibra Platform
Settings
Operating model
Data quality rules.The DigiCert root and intermediate CA certificates are installed in the Data Quality & Observability (self-hosted) Java truststore. Collibra uses DigiCert as its Certificate Authority to issue the
*.collibra.comSSL certificate that secures Collibra Platform instances.
Steps
Hover your cursor over the
icon and click Integrations.
The Integrations page opens.
In the upper right corner, click Add Integration. The Integration Setup wizard appears.
On the Credentials step, enter the required information.
Service Type
The application with which to integrate Data Quality & Observability (self-hosted) metadata.
This value is always Data Intelligence Cloud.
Yes
Service URL
The URL of the Collibra Platform environment to send Collibra DQ metadata. For example, "https://dg-example.collibra.com".
Yes
Authentication Mode
The method of authenticating the API call to Collibra Platform.
You can select either Basic or OAuth.
Yes
OAuth Token Endpoint
The Collibra Platform URL where Data Quality & Observability (self-hosted) sends requests to obtain the OAuth access token. The OAuth Token Endpoint must be in this format: https://<yourdomain>.collibra.com/rest/oauth/v2/token
To change the OAuth scopes that Data Quality & Observability (self-hosted) requests from Collibra Platform, go to Configuring the default OAuth scope.
To register your Collibra DQ instance, go to the OAuth Applications settings page.
Yes
Service Account
The username of your Collibra Platform environment. For example, "integration.user" or "Admin".
Yes
Password
The password of your Collibra Platform environment.
Yes
Client ID
The public identifier provided by your OAuth service provider.
Yes
Client Secret
The credential string from your OAuth service provider used to verify the identity of Data Quality & Observability (self-hosted) during the token request process.
Yes

Click Next. The Connections step opens.
On the Connections step, map your Collibra DQ connections to the appropriate database, schema, table, and column assets in Collibra Platform.
Optionally, select the Map to primary column only switch to see only the column identified as the primary column related to the rule in Collibra Platform.
From the Select Connection drop-down list, select a Collibra DQ database to integrate into Collibra Platform.
In your Collibra Platform environment, open the asset page of the database you intend to map, then copy the URL from the UUID of the database asset from the URL.
From the Connections tab in Collibra DQ, paste the copied UUID from Collibra Platform, or enter the UUID manually.
If this is the first integration, then click , then Run to create an automatic mapping between the schemas within your selected Collibra DQ database and the schemas within Collibra Platform. If this is not the first integration, then proceed to the next step.
When the connection loads, click , then Show Full Mapping to expand the entire database mapping, including schemas, tables, and columns. You can use the Auto Map feature or manually map (or a combination of both) for each schema.

Optionally, click
, then Delete Mapping to delete all the mapping records for the specific schema, including data quality rules, columns, jobs, and asset table relations.
Optionally, click Add New to map another connection and then repeat this process.
Click Next. The Mapping Status step opens.
On the Mapping Status step, optionally review mapping details.
Mapping Status allows you to view mapping details, such as the number of available tables in a schema that are mapped and when a connection mapping fails.
Connection Name
The name of the data source included in the mapping.
Schema Name
The name of the schema included in the mapping.
Status
The state of completion of the mapping.
Start Time
The time stamp, in yyyy-MM-dd hh:mm:ss format, of when the mapping began.
End Time
The time stamp, in yyyy-MM-dd hh:mm:ss format, of when the mapping stopped.
Tables Mapped
The number of tables that mapped out of the total tables available in the schema. The 3 numbers shown in x/y/z format represent:
x = partial column table count. The number of tables found in Data Quality & Observability (self-hosted) and Collibra Platform where some (>0 and < all column count) of the columns were mapped.
y = all column table count. The number of tables found in and Collibra Platform where all columns were mapped.
z = all tables discovered count. The total table count found in Data Quality & Observability (self-hosted) using the datasource connection for the "automap" schema.
Exception
When an error during the mapping occurs, a message describes the issue. If the error message is truncated, you can hover your cursor over it to view the full message in a tooltip.
When an exception did not occur, the value in this column is N/A.
Actions
When a mapping job is in progress, a option appears in this column to allow you to cancel the job if necessary.

Click Next. The Tenants step opens.
On the Tenants step, enter the required information.
Optionally, choose to align your Collibra DQ tenant with an existing Collibra Platform community.
Align
Select a Collibra Platform community from the drop-down list with which to align your tenant.
Don't Align,
Enter the name of a new community with which to align your tenant.

tenant mapping screenshot
Click Next. The Dimensions step opens.
On the Dimensions step, enter the required information.
Select a dimension from the drop-down list of the Data Intelligence Platform Dimension column that corresponds with the Data Quality Dimension you want to identify as a match.

Click Next. The Layers step opens.
On the Layers step, select which layers to synchronize to Collibra Platform.
If needed, clear the Create Metric Assets option. When selected, metric assets, such as Passing Fraction and Loaded Rows, are automatically created during integration to support the required data quality metrics for your Collibra Platform aggregation path or workflow design. When cleared, metric assets are not created during integration.
Select a layer in the Sync on Integration column to automatically create a new asset in Collibra Platform when the integration runs.
Select the Sync on Breaks option to create a new asset in Collibra Platform only when the layer has a finding.

Click Finish.
Known limitation
During the integration between Data Quality & Observability (self-hosted) and Collibra Platform, the Last Job Run and Last Successful Job Run attributes are sent as strings instead of dates. As a result, the time zone is converted to UTC (the Collibra Platform standard) instead of the user's time zone.
What's next
Enable a dataset for integration and start ingesting metadata from Collibra DQ into Collibra Platform.
Last updated
Was this helpful?