Collibra DGC: Quick Start Guide / Configuration Checklist

This article is a concise checklist to get the export from Manta Data Lineage to Collibra DGC up and running.

Verify all the following steps. Then, test the export by running the IBM Manta Data Lineage collibraExportScenario scenario script (located here: \mantaflow\cli\scenarios\manta-dataflow-cli\bin).

After configuration, consider reviewing the following article for testing defined use-cases: How to Effectively Test Export to Collibra DGC.

Collibra Preparation and Steps

1. Create a test community for export (from Manta Data Lineage) in Collibra

• Community names must be unique per Collibra instance.

  • That is, name the community MyTestCommunity.

2. For an account with appropriate access rights (to the REST API), ensure that the community manager of the community is being used for export

• Go to the Community page, select Responsibilities, click Add a User or Group, and assign the appropriate account/role.

3. Create a new scope called Manta Data Lineage (Settings > Scopes)

• Once created, also ensure that the community being used for export is linked to this scope.

  • Check the boxes next to the appropriate communities under the organization (Community and Domain).

    For more information, see Integration Returns the Error "You are not allowed to add, edit or remove an attribute whose type is read only."

4. Ensure all relevant assets are assigned to the newly created Manta Data Lineage scope

• Settings > Asset Types > The asset you want to edit > Add Assignment button > Tick the radio button next to the Manta Data Lineage scope > Green Add Assignment button.

  For more information, see Integration Returns the Error "You are not allowed to add, edit or remove an attribute whose type is read only."

5. Create all necessary (where applicable) custom assets and relation types

Assets: Settings > Asset Types > Add
Relations: Settings > Characteristics > Relations > Add

For more information, see Integration Returns the Error "You are not allowed to add, edit or remove an attribute whose type is read only."

Manta Flow Collibra Export Model features all of the relevant assets and attributes that are needed.

Manta Preparation and Steps

1. Collibra export settings (Manta Admin GUI) Configuration > Integrations > Collibra > Collibra Export

1. Supply the account credentials (Collibra username and Collibra password).

   This is the same Collibra account that requires the correct accessrights (to REST API) and needs to be assigned as the community manager for the targeted Collibra community for export.

2. Supply the Collibra server name, Collibra server port, and Collibra connection protocol (HTTP or HTTPS).

   • For Collibra Server Name, just provide the URL or IP address: that is, mantatools.collibra.com.

   • If there's no port number specified in the Collibra DGC URL, use the default port numbers (80 for HTTP / 443 for HTTPS).

     If the Collibra instance is HTTPS, follow the steps outlined under the section Keystore Certificate for an HTTPS Connection to Collibra DGC found here to add the certificate from Collibra to the Manta Data Lineage truststore: Notes on Integration API.

3. For first time configurations, set the single synchronization ID to false.

   Choose true if a single synchronization ID should be used for all
   communities (requires Collibra DGC 5.6.2 or later); choose false if a specific synchronization ID should be used for each community.

2. Collibra export filter settings (Manta Admin GUI) Configuration > Integrations > Collibra > Collibra Export Filter

• Supply the correct community name in the export filter row (the target Collibra DGC Community that Manta Data Lineage exports the specified metadata to).

  • Click the edit icon to the right, update the Community Name field, and click the Save button.

3. Collibra entity type settings (Manta Admin GUI) Configuration > Integrations > Collibra > Collibra Entity Types

• Ensure all the entity IDs (for assets and relations) correlate to those in the corresponding Collibra instance.

  • Start by verifying all the entries which don't adhere to the standard formatting conventions (for example, custom assets and custom relations).

  • In Collibra, each ID is featured in the Resource ID column for your assets and relations.
    Assets: Settings > Asset Types > Resource ID column
    Relations: Settings > Characteristics > Relations > Resource ID column

    This portion includes validation when you attempt to save the configuration. This helps highlight which values are correct and which ones still need to be updated.