ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (16.0.0) 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Import Lineage

After you have scanned your lineage, you need to import the lineage metadata to ONE and map it to the relevant catalog items.

Upload lineage file

To do this, go to Knowledge Catalog > Lineage Import. The following import options are available depending on where your lineage metadata originates from:

Upload lineage file

  1. Manta API: Upload a MANTA lineage file via API from the MANTA scanner.

  2. Manta file: Upload a MANTA lineage file directly to ONE.

  3. Ataccama file: Upload an Ataccama lineage file directly to ONE. This can either be custom content or a file generated by the standalone lineage scanner.

  4. Scan results: Upload an Ataccama lineage file from the built-in scanner internal storage.

Upload Ataccama file

To use a local Ataccama lineage file, select Ataccama file and drag and drop your lineage ZIP file into the file uploader. Alternatively, select Browse files and choose the file from your local drive.

Continue with step Map connections.

Load scan results

If you’re running a built-in lineage scanner, select Scan results. Choose a scan result from the list of built-in lineage scanner successful executions and select Upload the selected lineage extraction.

Load scan results

Continue with step Map connections.

Upload MANTA file

To use a local MANTA lineage file, select Manta file and drag and drop your lineage ZIP file into the file uploader. Alternatively, select Browse files and choose the file from your local drive.

Upload Manta lineage file

Continue with step Map connections.

Use MANTA API

To use this option, you first need to configure a connection to the MANTA server, then upload an extraction run to finish importing the lineage metadata.

Configure Manta connection

Configure connection to the MANTA server

  1. Select Manta API and open the settings (the gear icon).

  2. Provide the following information:

    • Manta Admin UI server URL: The URL where the MANTA Admin interface is available.

    • Keycloak server URL: The Keycloak endpoint used for authorization of the MANTA client.

    • Manta Realm: The MANTA realm name in Keycloak.

    • Client ID used with Manta API: The MANTA client name in Keycloak.

    • Client secret used with the client ID: The MANTA client secret in Keycloak.

  3. To check whether the connection is correctly configured, select Test Connection. If the connection is successful, continue with the following step.

    Otherwise, verify that your configuration is correct and that your MANTA server is running.

    Server visibility issues might mean you can’t use the API to extract your lineage metadata from MANTA. This can be caused by firewalls blocking the connection. In these cases, you can export your lineage data from MANTA and upload it to ONE manually.

    For instructions about how to prepare and export this file, see Configure MANTA Export.

  4. Select Save. Continue with step Upload lineage extraction.

Upload lineage extraction

  1. Select a lineage extraction to import. Only successful extractions runs that finished without any errors can be selected.

    If you see an error message, ensure that your MANTA server information is correct.

  2. Select Upload the selected lineage extraction

  3. Continue with step Map connections.

Map connections

Once your lineage extraction finishes uploading, select Next and wait for the processing to finish. This might take some time, especially if you’re importing a large amount of data.

You can continue using the platform and return to the Lineage Import tab later once the processing is finished. Your progress is saved automatically.

Map the connection names from the import file to the corresponding data source connections in ONE. You can also map individual connection names to multiple connections (select Add to include additional connections).

If you don’t want to import every connection name, clear the Import field as needed.

Map connection names from the lineage file
Connections are prefiltered based on the identified connection type (technology). If the connection you are looking for is configured but not displayed, select Load more items.

If ONE doesn’t have a corresponding connector for one of your dictionaries and you still want to import the metadata, map this dictionary to Not available in Knowledge Catalog. In this case, the imported metadata will be shown in your lineage but the nodes cannot be reached or enriched in Knowledge Catalog or Data Quality. However, the nodes will be listed in Lineage Assets.

You can also use this mapping if the connection is not yet configured in Ataccama. Keep in mind that, once you set up the connection, you need to re-import the metadata and map it again.

Once you’re happy with your configuration, select Next. Continue with step Publish new lineage metadata.

Publish new lineage metadata

As the final step in the import process, you need to make the new metadata from the import file visible to other users. To do this, choose between Overwrite and Expand modes.

Import modes

Publish in overwrite mode

If you publish in Overwrite mode, your lineage repository is cleared and any content is replaced with the new metadata. Switch to the Overwrite tab and select Overwrite.

Continue with step View import overview.

Publish in expand mode

If you publish in Expand mode, your lineage repository is enriched with the new metadata instead. Switch to the Expand tab and select Expand.

Continue with step View import overview.

Cancel the import

To cancel importing new metadata, switch to the Keep tab and select Keep. This clears the previously mapped connections and other settings.

View import overview

After you publish the import, you can view a summary of the latest lineage import and mapping on the Lineage Import screen.

Lineage repository list by connection

This shows:

  • Last modification information: An overview of when the lineage was imported, who imported it, and the last import type.

  • Connection type: The type of connection (technology).

  • ONE connection name: The name of the connection in ONE to where the source was mapped.

  • Source connection name: The name of the connection in the source in case it was not mapped to a connection in ONE.

  • Number of catalog items: The number of catalog items contained in the imported lineage with and without a match.

Ideally, all catalog items from the import should be match to catalog items in ONE. If this is not the case, there are several reasons why it can happen:

  • Some connections in the lineage import come from a source that has not been imported into ONE.

  • There are objects in the lineage import for which no relevant catalog items exist, such as temporary tables.

  • These catalog items are not included in the data catalog scope.

To view the lineage, you need to choose a specific catalog item from the Lineage Assets list or open the Lineage tab for a specific catalog item.

Was this page useful?