Configuring Collibra export
Prepare your Collibra instances for integration with data lineage. Define the target Collibra location where you want to add the exported lineage, and the mappings to display data correctly.
Required configuration in Collibra
In each Collibra instance that you use for integration with data lineage, you must create and configure custom entities and a scope.
Create custom entities in Collibra
Create custom relation types and a custom attribute type.
Relation types
In Collibra Settings > Operating model > Relation types, create these custom relation types:
| Head | Role | Co-role | Tail |
|---|---|---|---|
| Report | implemented in | implements | Technology Asset |
| File | source of | source | Mapping Specification |
| File | target of | target | Mapping Specification |
| Data element | source of | target of | Data Element |
Attribute types
In Collibra Settings > Operating model > Attribute types, create a custom attribute type Manta Link of kind Text. Assign this attribute type to column, table
and mapping specification assets.
Create and configure a custom scope in Collibra
A scope in Collibra is a container for communities and domains. You refer to a scope when you assign an asset type. Before you export data lineage, complete these steps:
- Create a custom scope dedicated for the exported lineage metadata in Collibra Settings > Operating model > Scopes.
- Assign required data to the custom scope:
- Add all communities that you use for the exported data to the scope.
- Assign all custom relation types to their corresponding assets in the scope.
- Assign all asset attributes to their corresponding assets in the scope.
- Generate mapping assignments for the scope for all asset types.
Collibra instances
The target Collibra instance where you want to add lineage is identified with a data source definition. It contains information about host and port.
To create a Collibra instance, go to Administration > Configuration and settings > Data lineage setup > Export configurations > Collibra.
After you create an instance, configure the following parameters. You can find the values for these parameters in Collibra Settings > Operating Model in the Attribute types and Relation types tabs.
- Manta Link
- Report implemented in a Technology Asset
- Data attribute model for a Data Element
- File source of a Mapping Specification
- File target of a Mapping Specification
- Data element source of a Data Element
Collibra mappings
Create Collibra mappings to define the following details:
- Select the target Collibra instance and define specific community and domain to store lineage metadata.
- Select the data source of the lineage to export.
- Optionally, change names of the source assets to conform to the Collibra naming conventions.
To create a Collibra mapping, go to Administration > Configuration and settings > Data lineage setup > Export configurations > Collibra.
Collibra location
When you define the location of the exported lineage in Collibra, you first select a data source definition that you defined earlier in a Collibra instance. To provide more detailed location for the lineage metadata, you provide community and domains.
Specify values for the following parameters:
- Community name: the target Collibra community to store the lineage metadata.
- Technology domain: the target domain that contains systems and databases.
- Physical data dictionary domain: the domain that contains physical data assets.
- Mapping domain: the domain that contains mappings.
Source for lineage
To define the source of the lineage to export, select a data source definition of the technology that you want to export. When the Collibra and a source technology data source definitions are linked in a mapping, they can't be used in other mappings.
Name mappings
When asset names follow different naming conventions in the source and target systems, you can create a name mapping to define how source and target assets are linked and named in the target system. For example, the source asset in data lineage
is called CATALOG_DM_8 and you want it to be displayed as DM_8 in Collibra. When you define the name mapping for this asset, after the lineage is successfully exported to Collibra, this asset is displayed as DM_8 in Collibra.