Application Level Lineage Configuration

The calculation of application-level lineage is turned on by default as of IBM Automatic Data Lineage R42, and it adds about 15% to the overall performance of the full scan process. There is an option to turn it off, and it is crucial for customers with large data landscapes. It is also possible to run it separately.

Enabling or Disabling

To create an Application Level Lineage, you need to have a ready-made connection for an Application Level Lineage. One connection is by default, but you can also create a new one through the “Add connection” button.

An image of the Application level connection menu

To temporarily disable the creation of Application Level layer, you can turn off the connection toggle switch that follows the ApplicationLevelConnection title. To permanently remove the creation of an Application Level layer, you can delete the connection as a whole.

Application Level Lineage Properties

Application Level Lineage is configured with connections. New connections can be created in the Manta Admin UI under the Connections tab. The connection configuration for Application Level Lineage has the following structure.

Property name Description Example
manta.applicationLevel.id Name of the Application Level Lineage connection PhysicalToApplicationLevel
manta.applicationLevel.baseLayer Name of the base layer (the layer FROM which will be create new layer) Physical
manta.applicationLevel.derivedLayer Name of new Application Level layer Application Level

Process manager and scenario execution

Since the Application Level layer is the post-processing scenario, it will be performed during the analysis stage, if one is included in the workflow (as an example Run Workflow). It is also important that by

default, Application Level layer is enabled only for a major revision.

A picture showing the workflow designer menu

Here is an example of how to make an Application Level layer for a minor revision. You can execute scenario separately through the scenario panel or select them in the Creating New Workflow when you turn on the advanced mod:

  1. Through scenario panel

    1. Automatic Data Lineage → New Minor Revision Scenario

    2. ApplicationLevel → Application Level Scenario

    3. Automatic Data Lineage → Commit Revision Scenario

  2. Through Creating New Workflow

    1. Analysis → Automatic Data Lineage → GENERAL → New Minor Revision Scenario

    2. Analysis → ApplicationLevel → ApplicationLevelConnection → Application Level Scenario

    3. Analysis → Automatic Data Lineage → GENERAL → Commit Revision Scenario

Major revision scenarios will have the same behavior.