ER/Studio Resource Configuration

Before you configure your scanner, make sure you meet the prerequisites. Read our guide on ER/Studio integration requirements to double-check.

Source System Properties

This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI / Connections / Data Integration Tools / ER/Studio / specific connection. New connection can also be created via Manta Orchestration API.

Property name Description Example
erstudio.system.id Enter the name of a resource representing this ER/Studio system (a set of ER/Studio files sharing a database connection configuration, used as an input subdirectory containing the ER/Studio models and connection settings) system_name

Common Scanner Properties

This configuration is common for all ER/Studio source systems and for all ER/Studio scenarios, and is configure in Admin UI > Configuration > CLI > ER/Studio > ER/Studio Common. It can be overridden on individual connection level.

Property name

Description

Example

erstudio.input.dir

Directory with manually provided ER/Studio files and their connection configurations

${manta.dir.input}/erstudio/${erstudio.system.id}

erstudio.config.ini

Path to a system connection configuration

${manta.dir.input}/erstudio/${erstudio.system.id}/${erstudio.connections.ini}

erstudio.models

Subfolder of ${ erstudio.input.dir} containing ER/Studio files to extract

models

erstudio.connections.ini

The .INI file in ${ erstudio.input.dir} where the connections to databases that correspond to physical models in ER/Studio are defined.

The format of the .INI file as well as the processing of the specific connection is described in (Manual) Connection Mappings Explained.

Specific models are defined in the Model csv table that is in inside the .DM1 model file and contains the attribute ModelType used to determine the type — 2 (plain physical model) or 5 (physical model reverse engineered from an existing database) — and the attribute ModelNameID, which is the number that can be matched to the corresponding String_Id in the csv table SmallString or LargeString, and the physical model name is under the attribute Data.

No alt text providedNo alt text provided

An example of a defined connection in the .INI file is:

[ErStudio_Model_Example_1]
Connection_String=jdbc:db2://192.168.26.1:1000/DB
Type=DB2
Server_Name=
Database_Name=
Schema_Name=
User_Name=

connections.ini

erstudio.files.encoding

Encoding of the input ER/Studio files. See Encodings for applicable values.

UTF-8

filepath.lowercase

Whether paths to files should be lowercase (false for case sensitive file systems, true otherwise)

true

Dataflow Generation

To generate lineage over ER/Studio objects, Open Manta Interpolation needs to be configured and executed. This configuration is independent of the ER/Studio configuration. For a detailed description, see Open Manta Interpolation Configuration.