Integrations for metadata ingestion into Collibra

Download a Template and Request a Trial License

REPORTING AND ANALYTICS

Tableau Integration

This template loads metadata from Tableau assets into Collibra DGC. Tableau REST APIs are used to pull in the Tableau assets like Workbook, Dashboard, Worksheet, Story and the relations between them.

Metadata can be filtered by a specific Site or Workbook. The template execution can be scheduled to run at specific times or triggered on-demand from an HTTP call.

Custom workflows are also available to push the definitions back to the Tableau workbook and publish it to the Tableau server. These definitions will appear as hover help on reports.

For more information, please download the datasheet

Cognos Integration

 This loads IBM Cognos assets into Collibra DGC. Metadata for Cognos reports/models and the relations supporting them are read using the APIs from Cognos SDK. The extraction can be filtered based on specific content manager folder path and model name.

The metadata for Powerplay Transformer Cubes are read from. mdl files. The Report layout metadata is also parsed to get the layout, report attributes, and sort information. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

Custom workflows are also available to push the definitions back to the Cognos Framework manager model as Description or Screen tip of business terms.

For more information, please download the datasheet

RDBMS

SAP HANA Integration

This loads SAP HANA assets into Collibra DGC. XML definitions from catalog tables in SAP HANA are parsed to pull in the SAP HANA assets like the model views (Calculation views, Analytic views, Attribute views) etc. and the relations supporting them. The assets extraction can be filtered based on Host, Database or Schema. Dependencies across all view types and view nesting are captured. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

Netezza Integration

This loads IBM Netezza assets into Collibra DGC. The assets extraction can be filtered based on Host, Database or Schema. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

SQL Server Integration

This loads SQL Server assets into Collibra DGC. The assets extraction can be filtered based on Host, Database or Schema. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

Oracle Integration

This loads Oracle assets into Collibra DGC. The assets extraction can be filtered based on Host, Database or Schema. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

PostgreSQL Integration

This loads PostgreSQL assets into Collibra DGC. The assets extraction can be filtered based on Host, Database or Schema. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

MySQL Integration

This loads MySQL assets into Collibra DGC. The assets extraction can be filtered based on Host, Database or Schema. The template execution can be scheduled or triggered on-demand via Mule or a custom workflow.

For more information, please download the datasheet

DATA GOVERNANCE TOOLS

IBM InfoSphere Information Governance Catalog

IBM IGC REST APIs are used to pull in different asset families – Relational Database Assets, File Assets, Mappings and BI Reports and load into DGC.
They are mapped to Relational Database Assets, File Assets, Mapping Specifications and Reports in DGC. There are different filters for each asset family.

For more information, please download the datasheet

ETL TOOLS

Informatica PowerCenter

The Collibra-Informatica Powercenter integration template loads the Informatica Powercenter assets into Collibra DGC. Repository tables are used to fetch the relevant metadata about Mappings, Sources, Targets, Lookups, Expressions etc. and the relations supporting them. A custom repository on PostgresSQL would be needed to hold the metadata before it can be stitched together and loaded into Collibra. The template consists of a batch routine that has to be run from the command line, followed by a Mule template that can be scheduled or invoked over HTTP.

For more information, please download the datasheet