Overview: Tableau integration v2 and migration

The Tableau integration v2 enables you to harvest Tableau metadata and create new Tableau assets in Data Catalog. Collibra Data Intelligence Cloud analyzes and processes the metadata and presents it as specific asset types, retaining their original names.

Steps

The following table shows the steps and prerequisites required to ingest metadata in Collibra via lineage harvester (Tableau integration v2) and run the migration script.

Note

This overview assumes that you have already ingested Tableau assets via Tableau integration v1.
In the commands that you enter to run the migration, you need to specify which custom asset types, attribute types and relation types you want to migrate.

Step	What?	Description	Prerequisites
1	Set up Tableau.	Before you start the Tableau integration in Data Catalog, make sure that the lineage harvester can reach the Tableau metadata. Perform these tasks before you start the actual Tableau ingestion process. Warning Because these tasks are performed outside of Collibra, it is possible that the content changes without us knowing. We strongly recommend that you carefully read the source documentation.	You have a Tableau subscription.
2	Create a new domain.	Before you can ingest Tableau metadata, you have to create a new domain or choose an existing domain to store the new Tableau assets. Warning If you are using Collibra Data Intelligence Cloud 2021.11 or older, you have to add all Tableau attributes in the operating model to a scope and create a scoped assignment before you ingest Tableau via the lineage harvester. For complete information and step-by-step instruction, see Tableau general troubleshooting.	You have a resource role with the following resource permissions: Domain: Add
3	Prepare the physical data layer.	You prepare Data Catalog's physical data layer to enable Data Catalog to automatically stitch the Tableau assets to existing assets in Data Catalog.	You have a global role with the Catalog global permission, for example, Catalog Author. You have set up the JDBC driver of your source data, for example Snowflake. You have a resource role with the following resource permissions on the Schema community: Asset > add Attribute > add Domain > add Attachment > add You have the permissions to retrieve the metadata of the following database components through the JDBC Driver Database Metadata methods: Schemas Tables Columns
4	Download and install the lineage harvester	You use the lineage harvester to trigger the creation of Tableau assets, their relations and a technical lineage in Data Catalog. You can download the lineage harvester from the Collibra Product Resource Downloads page. For a list of lineage harvester installation requirements, see About the lineage harvester installation.	Your environment meets the system requirements to install and use the lineage harvester.
5	Prepare the lineage harvester configuration file and run the lineage harvester.	You create a lineage harvester configuration file with Tableau connection information and run the lineage harvester to import the results of the Tableau integration and the technical lineage for Tableau into Data Catalog. As a result, you now have a duplicate of your Tableau metadata in Collibra.	You have downloaded the lineage harvester version 2022.03 or newer. Your environment meets the system requirements to install and run the lineage harvester. You have a global role with the Catalog global permission, for example, Catalog Author. You have a global role with the Technical lineage global permission. You have a global role with the Data Stewardship Manager global permission. A resource role with the following resource permission on the community level in which you created the BI Data Catalog domain: Asset: add Attribute: add Domain: add Attachment: add
6	Run the migration script	The migration script is triggered by a lineage harvester command. You then use arguments to migrate your customized asset types and custom attribute types and relation types. Note You need lineage harvester version 2022.03.0-5 or newer. We recommend that you use the newest lineage harvester.	Same prerequisites as for the previous step.
7	Verify the migration results	Compare your Tableau integration v2 assets to the respective Tableau integration v1 assets. Look to see that the metadata that you manually added to your integration v1 assets has been added to your integration v2 assets.	None
8	Delete your Tableau integration v1 metadata.	If you've reviewed the migration results and everything looks fine, you can delete your Tableau integration v1 assets and any assets of custom asset types.	You have a global role with the Catalog global permission, for example, Catalog Author. You have a resource role with the following resource permission on the community level in which you created the BI Data Catalog domain: Asset: Remove Domain: Remove

Naming convention

When you synchronize Tableau, Collibra follows a strict naming convention for the names of the new assets. Each asset has a display name and full name. The full name represents the asset path from asset to the database it belongs to. You can freely edit the display name. However, you should never edit the full name, because Data Catalog needs it for a successful migration. Changing the full name may also break the synchronization process.

Warning We highly recommend that you not edit the full names of any Tableau assets. Doing so will likely lead to errors during the migration and synchronization process.