How to Execute Manta Flow and the Associated Logging

Main Execution

Any time a full run is executed (Run <technology>), the following sequence of steps is initiated.

1. Diagnose Repository > 2. Extraction > 3. Analysis > 4. Export (optional step)

1. Diagnose Repository (Diagnose Repository Scenario)

2. Extraction (Run Extract)

Iterates through all *Extractor Scenario for each technology.
Note: Database technologies call associated ExtractorScenario AND DictionaryMappingScenario.

Any subsequent logging will adhere to this naming convention and create individual log files for each established connection (written to \mantaflow\cli\log) such as oracleExtractorScenario.log or oracleDictionaryMappingScenario.log.

3. Analysis (Run Analyze)

1. An attempt is made to create a new revision. (A New Revision Scenario is called.)

2. Iterates through DataflowScenario for each technology (i.e., tech_name_DataFlowScenario).

   • Any subsequent logging will adhere to this naming convention and create individual log files for each established connection (written to \mantaflow\cli\log)
     such as hiveDdlDataflowScenario_DICTID.properties.log or eErwinDataflowScenario_DICTID.properties-DATE.log.

3. Finally, repository post processing and commit revision are called ( Repository Postprocessing Scenario and Commit Revision Scenario).

Note: If analysis is terminated unexpectedly/prematurely at this stage, ensure that you commit or roll back the open revision by using Commit Revision Scenario or Rollback Revision Scenario respectively.

You can also delete the last committed revision by using Delete Last Revision Scenario.

4. Export (Optional Step)

Runs one of the export modules based on the technology specified in the name of the Run <technology>.

• Run Export
  Calls Export Repository Scenario to generate standard CSV output

• Run Export Collibra
  Calls Collibra Export Scenario to export metadata to Collibra

• Run Export_iedc
  For each technology, calls <technology>Iedc Export Scenario to generate files with lineage information for EDC
  For each technology, calls <technology>oracle Iedc Upload Metadata Scenario to upload lineage information into EDC

• Run Export_igc
  For each technology, calls <technology> Igc Export Scenario to generate files with lineage information for IGC
  For each technology, calls <technology> Igc Diff Scenario to generate a difference report for the last two revisions
  For each technology, calls <technology> Igc Upload Metadata Scenario to upload lineage information into IGC