2.1. Getting Started with REDLIN

This guide covers how to set up the REDLIN lineage generator and run your first extraction.

2.1.1. Prerequisites

  • RED-Framework installed

  • Business ETL Version

Optional:

  • Access to the Microstrategy environment (Harvesting BI Lineage)

  • Access to the Dataspot environment (Pushing Lineage to a Data Governance Tool)

2.1.2. Installation

The Installation is part of the RED-Framework installation and nothing special has to be done.

2.1.3. Configuration

The configuration is covered with the red_params.conf file on the batch server. See red_params.conf Configuration.

2.1.4. Running the Harvester

You can trigger the lineage generation via the REDLIN command-line interface. For example:

redlinctl --enable-consolelog generate

See LIN_GEN_LINEAGE Reference for details on how to generate lineage via the SQL-interface.

2.1.5. Infrastructure Planning

Batch Server: Parsing the the Lineage is done via the redlinctl script on a batch server. Parallel parsing is configureable via the red_params.conf file. Depending on the amount of views and tables in the business ETL it might take a lot of resources (Memory and CPU).

Exasol Server: The Exasol Database is used for storing the lineage (end of the process) and harvesting the metadata in the beginning of the process. There shouldn’t be any issues running the lineage generator.

2.1.6. Security

Access to the data lineage data is controlled by the R_REDLIN role. This role is given to any human user.

Configuration Changes are subject to Application Managers. The API_REDLIN schema is holding APIs for changing the configuration. These APIs are protected by a separate DB role which is only given to Application Managers.