Collibra Integration details
Learn about the architecture of the Reltio Integration for Collibra and how it maps Reltio objects to Collibra data assets
Reltio Integration for Collibra is implemented through our Reltio Integration Hub (RIH). The integration consists of Reltio and Collibra connections and recipes to read the tenant business config from Reltio and create corresponding objects in Collibra.
-
Entity types
-
Entity attributes - Simple, Nested, Reference
-
Relationship types
-
Relationship attributes - Simple, Nested
-
Community -
Reltio -
Domain -
Master Data Management (Technology Asset)
The Reltio tenant is created as a Data Model under the Reltio System in Collibra using the implements relationship.
The Data Model name is derived using the label_tenantid_env. Since the data model name uses the tenant ID and env, it is always unique for a tenant, so the same Collibra account can be used for multiple tenants.
Reltio objects mapping to Collibra data assets
These Reltio objects are mapped to Collibra data assets.
- Entity Types
-
Entities within a tenant are created as
Data Entityin Collibra with anis part ofrelationship with the data model. - Simple Attributes
-
Simple attributes in the Entity type are created as
Data Attributesin Collibra with acontainsrelationship with its entity. - Nested Attributes
-
Nested attributes in a Reltio entity type are also created as
Data Entityin Collibra with aContainsrelationship with the parent entity typeData Entity. Sub nested attributes are created as data attributes with aContainsrelationship with the nested attribute data entity.This screenshot shows an Individual entity type that contains the Email nested attribute, which further contains multiple sub nested attributes like username, domain type, etc.
- Reference Attributes
-
A Reference attribute group in a Reltio entity type is also created as
Data Entityin Collibra with aReferencesrelationship with the parent entity typeData Entity. Sub reference attributes are created asData Attributeswith aContainsrelationship with the reference attribute bucket data entity.This screenshot shows an Individual entity with a Reference attribute called
Address, which contains multiple simple attributes like verification status, PO Box, state, country, etc., and some nested attributes like Zip and Geo Location. - Relationship Types
-
Relationship Types are created as a new Data Asset called
Reltio Relationshipin Collibra. Reltio Relationship also hasis part ofrelationship with the data model.This new data asset is connected with start and end entity type using the relation as defined in the tenant's L3 configuration.Relationship attributes are added as data attributes with a
Containsrelation with the Reltio Relationship asset.This screenshot shows an Organization entity type with a
has addressrelationship with the Location entity type. Thehas addressrelationship has four simple data attributes:Address Type,Address Rank,StatusandActive.Relationship data attributes can further have a
Containsrelation with the Reference attribute that contains it. In the example below, theAddress Typerelationship data attributes is referenced by theOrganizationentity type.
Lookup tables
The integration uses these lookup tables.
- Collibra Created Assets
-
Stores the asset ID of assets created in Collibra. Will be used for deleting assets.
- Reltio URI->Collibra Asset ID Mapping
-
Stores Reltio URI of entities & attributes and its corresponding created asset IDs. Will be used for creating relation between entities & relation between reference attributes and referred attributes.
- Collibra Reference Attributes
-
Stores ID of reference attributes and its array of referred URIs. This is created for avoiding going through the L3 configuration twice in order to create reference attributes.
- Recursion
-
Acts as a stack for storing function calls for implementing recursive calls for processing nested attributes. Stores attribute’s json, asset ID of parent, asset type of parent, asset full name of parent. Contains a dummy field called processed which is not used but is required for getting a single entry from the table.