Supported connections for importing lineage with MANTA Automated Data Lineage

You can connect to many data sources from which you can import lineage metadata with MANTA Automated Data Lineage.

This information applies to MANTA Automated Data Lineage service.

Requirements and restrictions

Users must be authorized to access the connections to the data sources. For metadata import, the user running the import must have the SELECT or a similar permission on the databases in question.

Required configuration

For lineage capture, the knowledge graph feature and use of the FoundationDB graph database must be enabled in IBM Knowledge Catalog, and a MANTA Automated Data Lineage for IBM Cloud Pak for Data license key must be installed. A MANTA Automated Data Lineage for IBM Cloud Pak for Data license key is required for importing lineage of business intelligence assets, data integration assets, or data models.

For more information, see Installed features and license requirements.

Supported connectors

You can import lineage metadata from the following data sources.

For information about connectors that support metadata import with the goal Discover, see Supported connectors for discovery, enrichment, and data quality.

File storage connectors

IBM Cognos Analytics
- Cognos Analytics connections that use secrets from a vault as credentials cannot be used for metadata import.
- Specific JDBC drivers are required. See Uploading JDBC drivers for lineage import in the IBM Software Hub documentation.

Database connectors

Amazon Redshift
- Specific JDBC drivers are required. See Uploading JDBC drivers for lineage import in the IBM Software Hub documentation.
Apache Hive
- Specific JDBC drivers are required. See Uploading JDBC drivers for lineage import in the IBM Software Hub documentation.
- Hive connections with Kerberos authentication require some prerequisite configurations. See Configuring Hive with Kerberos for lineage imports in the IBM Software Hub documentation.
Google BigQuery
- Connections must be configured with the authentication method Account key (full JSON snippet).
Greenplum
IBM Cloud Databases for PostgreSQL
IBM Db2
IBM Db2 for z/OS
IBM Db2 on Cloud
IBM Netezza Performance Server
Microsoft Azure Databricks (Hive metastore and Unity catalog)
Microsoft SQL Server
Oracle
- Table and column descriptions are imported only if the connection is configured with one of the Metadata discovery options No synonyms or Remarks and synonyms.
PostgreSQL
Snowflake
Teradata
- Specific JDBC drivers are required. See Uploading JDBC drivers for lineage import in the IBM Software Hub documentation.

Other connections

The following connectors support metadata import of the types Discover and Get lineage:

In addition, you can import these types of data to catalogs:

Business intelligence assets from the following tools:
- Microsoft SQL Server Analysis Services (discovery and lineage)
- Statistical Analysis System (SAS) (discovery and lineage)
To import metadata from these sources, you must provide an input file. For more information, see Preparing manual input for importing business intelligence reports.
Data integration assets from the following tools:
- DataStage on Cloud Pak for Data (discovery and lineage)
- Informatica PowerCenter (discovery and lineage)
- InfoSphere DataStage (discovery and lineage)
- Talend (discovery and lineage)
To import metadata from these sources, you must provide an input file. For more information, see Preparing ETL job files for metadata import.
Data models that were created in the following tools:
- ER/Studio (discovery)
- erwin Data Modeler (discovery)
- SAP PowerDesigner (discovery)
To import metadata from these sources, you must provide an input file. For more information, see Preparing data model files for metadata import.

Learn more

Parent topic: Supported data sources for curation and data quality