IDERA ER/Studio Business Architect (via DM1) - Import
Availability-note
AWS
AWS-only features are available at any of the following URLs: us.cloud.talend.com, eu.cloud.talend.com, ap.cloud.talend.com
Bridge Requirements
This bridge:is only supported on Microsoft Windows.
Bridge Specifications
| Vendor | IDERA |
| Tool Name | ER/Studio Business Architect |
| Tool Version | 1.5 |
| Tool Web Site | https://www.idera.com/er-studio-data-architect-software |
| Supported Methodology | [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via DM1 File |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting |  |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: IDERA / ER/Studio Business Architect version 1.5 via DM1 File
See https://www.idera.com/er-studio-data-architect-software
Metadata: [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout
Component: EmbarcaderoErStudioImport.EmbarcaderoEaStudio version 11.2.0
OVERVIEW
This bridge imports data models from an ER/Studio .DM1 file, including up to one logical model with Entities, Attributes, Domains, and any number of related physical models with Tables, Columns, Data Types. This bridge also imports all relationships and their implementation (e.g. PK/FK) as well as the graphical layout of the data models (diagrams). In addition, this bridge reverse engineers any semantic relationships between the data elements in the logical model (if available) and their corresponding data elements in the various physical models.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | ||||
| File | Specify the DM1 file to import. | FILE | *.dm1 | Mandatory | |||||
| Model selection | DM1 files are composed of multiple independent models. Select which types of models this bridge should import: 'All models' The logical and physical models are imported. 'Logical model' The logical model is imported. (Default) 'Physical model' A physical model is imported. Use the parameter 'Physical model name' to select which one. Note - Selecting 'All models' means that this bridge will create a multi-model construct which is not compatible with many data modeling and design tools. Please only use this option if one intends to load the result in a tool or repository which can consume it. |
ENUMERATED |
|
Logical model | |||||
| Physical model name | Name of single physical model to import. Choose which physical model should be imported. Also, you must set the 'Model selection' parameter to 'Physical model'. | STRING | |||||||
| Import UDPs | A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects that the property applies to may have an explicit value for this property. They may instead have no value assigned at all in which case the default value of the property definition (implicit value) applies. Control how property definitions and values are imported: 'As metadata' Import the explicit value as the property value. Implicit values are not imported. The default value is kept on the property type only. 'As metadata, migrate default values' Import the explicit or implicit values as property value. 'In description, migrate default values' Append the property name and value, even if implicit, to the object's description property. 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. |
ENUMERATED |
|
As metadata | |||||
| Import owner schemas | Specifies if owner schemas should be imported. 'True' Owner schema for tables, views and other database objects is imported. '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 | True | ||||||
| Remove text formatting | Remove Rich Text Formatting (RTF) from definitions and notes. ER/Studio versions 5.1 to 16.0 store definitions and notes as plain text, while versions 16.5 and later use RTF. However, tools you may export to do not support RTF text. 'False' - If the model was generated by ER/Studio 5.1 to 16.0. - Target tool is capable of displaying RTF text. 'True' - If the model was generated by ER/Studio 16.5 or greater. - Target tool is not capable of displaying RTF text. |
BOOLEAN | True |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"IDERA ER/Studio Business Architect (via DM1)" 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 |