IDERA ER/Studio Repository - Import - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

  • requires the tool to be installed to access its SDK.

Bridge Specifications

Vendor IDERA
Tool Name ER/Studio Repository
Tool Version 5.1 to 18.x
Tool Web Site https://www.idera.com/er-studio-data-architect-software
Supported Methodology [Data Modeling] Multi-Model, Metadata Repository, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via COM API on DM1 File
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

BRIDGE INFORMATION
Import tool: IDERA ER/Studio Repository 5.1 to 18.x (https://www.idera.com/er-studio-data-architect-software)
Import interface: [Data Modeling] Multi-Model, Metadata Repository, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via COM API on DM1 File from IDERA ER/Studio Repository
Import bridge: 'EmbarcaderoErStudioRepository' 10.1.0

BRIDGE DOCUMENTATION
ER/Studio installation:
This bridge connects to the IDERA ER/Studio Repository server using the ER/Studio Data Architect COM API.
Thus, IDERA ER/Studio Data Architect must be fully installed with a valid license on the machine where the bridge is running.
Make sure that this license is authorizing access to ER/Studio Repository and that this license is the only one, or configured as default.
InstantOn virtualized installations do not register the COM API, and are therefore not supported.
You may check that a key exists in the windows registry in HKEY_CLASSES_ROOT\ERStudio.Application
The repository server machine name must be specified in ER/Studio Data Architect, in the 'Repository' / 'Repository Properties' menu.
In order to test this, start ER/Studio Data Architect and make sure you can open a model from the ER/Studio Repository.
You may use the check-box 'Repository Operation Status' / 'Do Not Show Dialog Again' to hide popup windows.

ER/Studio Data Architect saves the repository properties into the windows registry, for example:
HKEY_CURRENT_USER\Software\Idera\ER/Studio Data Architect 17.0\Repository
HKEY_CURRENT_USER\Software\Embarcadero\ER/Studio Data Architect 10.0\Repository
HKEY_CURRENT_USER\Software\Embarcadero\ER/Studio Data Architect 9.5\Repository
The bridge will use the ER/Studio Data Architect COM API to retrieve the server machine name from the Windows registry.

ER/Studio Windows User:
The bridge must run on behalf of the Windows user who performed the configuration above.
If the bridge is running as part of a desktop application, the current Windows login of the application should be the same user.
If the bridge is running as part of a Windows service, it is important to configure the user running such service, in the service logon tab.
Go to the Windows services and click on the 'Properties' menu of such service, go to the 'Log On' tab, select 'This account' and specify the same user name and password used as Windows session when using ER/Studio, and restart the Windows service.

ER/Studio COM API:
The bridge uses the ER/Studio Windows COM API. This can be tested using a script:
cd .\conf\MIRModelBridgeTemplate\ERStudio
cscript.exe //E:jscript //Nologo ERStudioRepository.js parameters.xml browse output.xml
If this script fails, then you have an ER/Studio installation or setup issue, and need to contact IDERA support.


Bridge Parameters

Parameter Name Description Type Values Default Scope
User name Specify here your user name. If no password is specified and the user name matches with the current Windows session login, ER/Studio will attempt to log in under the current Windows account. STRING   Admin Mandatory
Password Specify here your user password. If no password is specified and the user name matches with the current Windows session login, ER/Studio will attempt to log in under the current Windows account. PASSWORD      
Repository subset Specify here a list of Diagrams (DM1 file names), separated by semicolon.
For example: OrangeMart.DM1
REPOSITORY_SUBSET      
Import UDPs This parameter defines how an Attachment, also called a User Defined Property, or UDP, is imported from ERStudio. An Attachement usually has a default value, and the objects bound to the Attachement may override it with an explicit value, or reuse the Attachment default value.

'As metadata' - Import an explicit value as Property Value, default values are not imported, the default value is kept on the Property Type only (default)

'As metadata, migrate default values' - Import explicit and default values as Property Value objects

'In description, migrate default values' - Append the property name and value, even if implicit, to the object's description and/or comment (depending upon the design level). This allows you to export the UDP values to another tool which does not support the notion of UDP

'Both, migrate default values' - Import the UDP value, even if implicit, both as metadata and in the object's description and/or comment (depending upon the design level).
ENUMERATED
As metadata
As metadata, migrate default values
In description, migrate default values
Both, migrate default values
As metadata  
Import owner schemas Specifies if owner schemas should be imported.

'True' - The owner schema for Tables, Views and other database objects is imported. This is the default value.

'False' - The owner schema for Tables, Views and other database objects is ignored. This option may be useful for models where physical names are not unique, to indicate the model should be treated as a logical model (not ready for SQL DDL generation) while physical information is still maintained the model.
BOOLEAN
False
True
True  
__Import mappings This parameter specifies whether the data mapping specifications are imported from ER/Studio.

'True' - Data mapping specifications are imported from ER/Studio. (default)
'False' - No data mapping specifications are imported.
BOOLEAN
False
True
True  
Multiple threads Number of worker threads to harvest metadata asynchronously.
Leave the parameter blank to have the bridge compute the value, between 1 and 6, based on JVM architecture and number of available CPU cores.
Specify a numeric value greater or equal to 1 to provide the actual number of threads.
If the value specified is invalid, a warning will be issued and 1 will be used instead.
If you experience out of memory conditions when harvesting metadata asynchronously, experiment with smaller numbers.
If your machine has a lot of available memory (e.g. 10 Gb or more), you can try larger numbers when harvesting many documents at once.
Note that setting the number too high can actually decrease the performance due to resource contention.
NUMERIC      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"IDERA ER/Studio Repository"
Metamodel
EmbarcaderoErStudio
Mapping Comments
     
Association Relationship/Foreign Key  
Aggregation Relationship Type True if Identifying
Description Definition optional: Attachment values can be added to the description
DesignLevel Type of Data Model  
Name Name  
AssociationRole Relationship/Foreign Key  
DesignLevel Type of Data Model  
ExtraConstraint Parent Action/Child Action  
Multiplicity Cardinality, Existence  
Name Verb Phrase, Inverse Verb Phrase  
Source   Parent/Child information
AssociationRoleNameMap ForeignKeyColumn  
Attribute Attribute/Column  
Comment Column Definition  
Description Attribute Definition optional: Attachment values can be added to the description
DesignLevel Type of Data Model  
ExtraConstraint Check Constraint, Rule  
InitialValue Declared Default, Default  
Name Attribute Name Logical Rolename if set
Optional Allow Nulls  
PhysicalName Column Name Physical Rolename if set
Position Sequence  
BaseType Domain, User Datatype, Attribute  
DataType Datatype See datatype conversion array
Name   Derived from the datatype
PhysicalName   Derived from the datatype
CandidateKey Key/Index  
Name Name  
UniqueKey Key Type True for Primary Key/Alternate Key
Class Entity/Table  
Comment Table Definition  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Entity Definition optional: Attachment values can be added to the description
DesignLevel Type of Data Model  
DimensionalRole Dimensional model Table Type  
DimensionalType Dimension Table Type  
Name Entity Name  
PhysicalName Table Name  
ClassDiagram Submodel  
Description Definition The Definition property is available only since version 8.0 . optional: Attachment values can be added to the description
Name Name  
DatabaseSchema Entity/Table, View  
Name Owner  
DerivedType Domain, User Datatype, Attribute  
DataType Datatype See datatype conversion array
Description Description optional: Attachment values can be added to the description
InitialValue Default, Declared Default  
Length Length  
LowerBound Reference Value Minimum  
Name Name Derived from the datatype if Attribute based
PhysicalName   Derived from the datatype
Scale Scale  
UpperBound Reference Value Maximum  
UserDefined   True for User Datatype and Domain
DesignPackage Data Model  
Description   optional: Attachment values can be added to the description
DesignLevel Type  
Name Name  
UserDefined   set to TRUE
ForeignKey ForeignKey  
Name Name  
Generalization Supertype/Subtype Cluster  
Description   optional: Attachment values can be added to the description
GeneralizationRole Supertype/Subtype Relationship  
Identity Sequence, Identity properties  
Cycle Cycle  
IncrementValue Increment By  
MaximumValue Max Value  
MinimumValue Min Value  
StartValue Start Value  
Index Key/Index, ForeignKey  
Clustered Index Type  
Description   optional: Attachment values can be added to the description
Name Name  
IndexMember IndexColumn  
Position Sequence  
SortOrder Sort Ordering  
Projection Element Display Graphical information
BackgroundColor background color  
Height height  
Width width  
X x  
Y y  
PropertyElementTypeScope Attachment Type  
Scope Usage  
PropertyType Attachment, Attachment Type  
DataType Data type  
Description Description  
Group Attachment Type Name  
InitialValue Value  
Name Name  
PropertyValue Attachment Binding  
Value Value  
RelationshipProjection Relationship Display not supported
SQLViewAssociation View Table  
Name Alias  
SQLTableSequence Sequence  
SQLViewAttribute View Column  
Description   optional: Attachment values can be added to the description
Expression Expression  
Name Alias, Parent Column Name  
Position Sequence  
SQLViewEntity View  
Description Definition optional: Attachment values can be added to the description
Name Name  
WhereClause DDL  
Sequence Sequence  
DataType Datatype  
Length Datatype  
Name name  
NativeDataType Datatype  
Scale Datatype  
Shape Shape  
BackgroundColor Shape Background Shape Editor -> Color and Fonts -> Background
Bold Font Style  
FontColor Text Color Color dropdown in Colors and Fonts -> Text
FontName Font Font typeface name
FontSize Text Font Size  
Height   Height of the shape
Italic Text Font Style  
LineColor Shape Outline  
LinePoints   Vertex coordinates for pentagon, hexagon and octagon, or endpoints for straight line
Name Shape Name Accessible in Shape Editor, Name
ShapeType Shape Type Type of the shape according to the Drawing Shapes toolbar
Strike Text Font Strikeout  
Underline Ttext Font Underline  
Width   Width of the shape
X   X coordinate of the shape center
Y   Y coordinate of the shape center
Z   Z order of the shape
StoreModel Diagram The model is built using the elements contained in the ERStudio file
Description Definition optional: Attachment values can be added to the description
Name Name  
SystemType Database Platform  
SystemTypeOld Database Platform  
StoredProcedure Procedure  
Description description  
Name name  
Semantics SQL  
Synonym Synonym  
Description Description  
Name Name  
Trigger Trigger  
Description Definition optional: Attachment values can be added to the description
Name Name  
Semantics Value  
TriggerType information parsed from Value  
TypeValue Reference Value  
Name Value Description  
Position Sequence  
Value Value