Skip to main content Skip to complementary content

erwin 7.x Data Modeler - Export

Availability-note AWS

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor erwin, Inc.
Tool Name erwin Data Modeler
Tool Version 7.x
Tool Web Site https://erwin.com/products/erwin-data-modeler/
Supported Methodology [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via COM API on Native (.erwin) or Export (.XML) File

SPECIFICATIONS
Tool: erwin, Inc. / erwin Data Modeler version 7.x via COM API on Native (.erwin) or Export (.XML) File
See https://erwin.com/products/erwin-data-modeler/
Metadata: [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout
Component: CaErwin7Xml version 11.2.0

OVERVIEW
Generates an erwin XML file.

REQUIREMENTS
WARNING: This bridge uses the COM API of a Windows based tool client and/or SDK which must be (a) properly installed, (b) licensed on behalf of a Windows user capable of running this tool, and (c) capable of accessing the tool server content. In addition:
(1) As recommended by the tool vendor, the tool server must NOT be installed/coexist on the same machine where the tool client (and the bridge) is installed/running because of potential conflicts of resources, including with respect to COM API.
(2) Windows COM API based tools are notoriously unstable after repeated failures or lack of system resources, which requires a Windows reboot to make that tool COM API work properly again.
(3) If this bridge is running as an application, then it must be logged with the same above Windows user.
If the bridge is running as a Windows service, then go to the services manager of Windows, right-click on the MIMB Application Server service, and go to the "Log On" tab to define an account by name under which the service will run.

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
When importing from a multi model source technology (e.g. a database server with multiple databases or schemas), only one model (e.g. schema) is exported. Therefore, limit the import scope to a single model (e.g. subset one schema of a database).

Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

This bridge relies on the erwin Data Modeler COM/OLE API to export erwin metadata files. Therefore, erwin 7 Data Modeler must be properly installed on the machine executing this bridge.

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 Generates either an .XML or .erwin (native erwin) file.
Determines which format based upon the extension of the file name in this bridge parameter.

In order to load the converted .XML model in erwin:

1. Choose 'Open' from the File menu.
2. In the 'List files of type' list box select XML Files (*.xml).
3. Navigate to the file directory.
4. Locate the file you want to open. Type the name of the file in the 'File Name' text box or select it from the File Name list.
5. Click 'Open'.
FILE
*.xml
*.erwin
  Mandatory
Version The file format to generate the data model in.
'*.erwin'
Extension to generate a binary file. For this format, the proper version of the software must be installed locally.

'*.xml'
Extension to generate a Repository XML file.
ENUMERATED
Latest
7.3
7.2
7.1
7.0
Latest  
Design level Design level of the data model to export:

'Logical only'
Generate a logical data model.

'Physical only'
Generate a physical data model.

'Logical & physical'
Generate a logical and physical data model.
ENUMERATED
Logical & physical
Logical only
Physical only
Logical & physical  
Target database The target database. 'Auto Detect' will attempt to auto-detect the target database from the originating model. ENUMERATED
Auto Detect
Access 2000
Advantage Ingres 2.5
Advantage Ingres 2.6
Advantage Ingres r3
DB2/390 7
DB2/390 8
DB2/zOS 9
DB2/UDB 8.1
DB2/UDB 9
DB2 iSeries 4.x/5.x
FoxPro
Informix 7.x
Informix 9.2/9.3
MySQL 5.x
ODBC/Generic 2.0
ODBC/Generic 3.0
Oracle 8i
Oracle 9.x
Oracle 10.x
Oracle 11.x
Progress 8.x
Progress 9.x
Red Brick 5.x
SAS
SQL Server 7.0
SQL Server 2000
SQL Server 2005
SQL Server 2008
Sybase 12.5
Sybase 15
Sybase IQ 12.5
Teradata 2.x
Teradata 12
Auto Detect  
Export dimensional properties Enables the dimensional modeling features for this model and exports the dimensional role (fact, dimension, outrigger) and dimensional type (fixed vs slowly changing) of the tables. BOOLEAN   False  
XML Indentation (pretty printing) Controls the pretty printing of XML, for the purpose of opening the generated file in a text editor. E.g.

'space characters'
Several space characters as indentation.

'tab key'
Tab character as indentation.

'empty'
No indentation which leads to a more compact file.
STRING      
Validate XML Validate the generated XML before it is converted to the *.erwin binary format:

'True'
Call the erwin API to validate the generated XML and then convert it to the *.erwin binary format

'False'
Call the erwin API to only convert the generated XML to the *.erwin binary format

When generating an erwin XML file only, no validation is performed.
BOOLEAN   True  
Connection Allows selecting a connection by name, if the source model contains multiple database connections.
If the source model contains multiple connections and this parameter value is left empty, the connection with the most objects is selected.
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"erwin 7.x Data Modeler"
Metamodel
CaErwin7Xml
Mapping Comments
     
Association Relationship  
Aggregation Identifying/ Non Identifying  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name Computed if not set
PhysicalName Physical_Name Foreign Key Constraint Name
AssociationRole Relationship  
DesignLevel Logical Only, Physical Only  
ExtraConstraint Delete, Insert, Update Rule  
Multiplicity Cardinality or Relationship_No_Nulls  
Name Child_To_Parent_Phrase or Name  
Source   Based on the multiplicity of each role and the Identifying/Non Identifying property
AssociationRoleNameMap Attribute/Index Used to connect the attributes involved in a Relationship
Attribute Attribute/Column  
Comment Comment  
Description Definition  
DesignLevel Logical Only, Physical Only  
ExtraConstraint Validation_Rule_Ref if the validation rule cannot be set on the type
Name Name  
Optional Null Option  
PhysicalName Physical_Name  
Position Order, Physical_Order  
BaseType Domain, Attribute Data Type No equivalent, We create the 5 base types erwin requires
BusinessRule Default Values, Validation Rules  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
LowerBound Validation_Rule_Min_Value  
Name Name  
PhysicalName Physical_Name  
UpperBound Validation_Rule_Max_Value  
CandidateKey Key Group/Index (non Foreign Key)  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
PhysicalName Physical_Name if set by the user
UniqueKey   Create an Inversion Entry if uniqueKey is false
Class Entity/Table  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
DimensionalRole Dimensional Modeling Role  
DimensionalType Dimension Type  
Name Name  
PhysicalName Physical Name  
ClassDiagram Subject Area  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
DatabaseSchema Owner Table, View or Index owner
DesignLevel Logical_Only, Physical_Only  
Name Name  
DerivedType Domain, Attribute Data Type  
Comment Domain_Comment  
DataType Datatype See datatype conversion arrays
Description Domain_Definition  
InitialValue Default and Default_Value imported from the Not Mapped value tag associated to this type
Length Datatype  
Name Name  
PhysicalName Physical_Domain_Name Mapped only if the Model is generated as Physical Only
Scale Datatype  
UserDefined   Mapped as a Domain only if it is user defined
ForeignKey Key Group/Index (Foreign Key)  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
PhysicalName Physical_Name if set by the user
Generalization Supertype/Subtype  
DesignLevel Logical_Only, Physical_Only set to Logical Only if a transformation is created
Name Name Computed.
GeneralizationRole Supertype/Subtype Relationship  
Identity Sequence, Identity properties  
Cycle Cycle  
IncrementValue Increment By  
MaximumValue Maximum Value  
MinimumValue Minimum Value  
StartValue Starting Value  
Index Key Group/Index  
Clustered Index Clustered  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
PhysicalName Physical_Name  
IndexMember Key Group Member/Index Member  
DesignLevel Logical_Only, Physical_Only  
Name Name  
Position Key Group Member Position  
SortOrder Key_Group_Sort_Order  
Note Note  
Value   note value
Projection Drawing Object Graphical Information
BackgroundColor fill color  
FontColor font color  
Height height  
LineColor outline color  
Width width  
X x  
Y y  
PropertyElementTypeScope User Defined Property  
Scope UDP Class  
PropertyType User Defined Property  
DataType Type  
Description Description  
DesignLevel   UDP design level: Logical and/or Physical
InitialValue Default value  
Name Name  
NativeId   Object id
PhysicalName   Not used
Position position  
Usage   set to User
PropertyValue User Defined Property used for UDP values and column physical information specific to Teradata: COMPRESS, CASE and FORMAT
Value Value value set on an object
RelationshipProjection Drawing Object Graphical Information
BackgroundColor fill color  
FontColor font color  
LineColor outline color  
LinePoints relationship path  
X x relationship mid point
Y y relationship mid point
SQLViewAssociation View Relationship  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name Computed if needed
PhysicalName Physical_Name  
SQLTableSequence Relationship Sequence  
SQLViewAttribute View Column  
Comment Comment  
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
PhysicalName Physical_Name  
Position Order  
SQLViewEntity View Table View Entity
Comment Comment No equivalent, (erwin fails to import)
Description Definition  
DesignLevel Logical_Only, Physical_Only  
Name Name  
PhysicalName Physical_Name  
WhereClause View SQL or Where clause  
Sequence Sequence  
DataType Datatype  
Length Datatype  
Name name  
NativeDataType Datatype  
Scale Datatype  
Shape Shape, Text Box  
BackgroundColor Fill Color  
Bold Font Bold  
FontColor Font Color  
FontName Font  
FontSize Font Size  
Height   Used to provide placement information
Italic Font Italic  
LineColor Line Color Object outline color
Name Name Object name as stored in MIR model
ShapeType   Type of the drawing object corresponding to the Drawing Objects palette
Strike Font Strikeout  
Underline Font Underline  
X   Used to provide placement information
Y   Used to provide placement information
Z   Z-order of the object
StoreModel Model/Diagram The model is built using the elements contained in the erwin file
Description Definition optional: UDP values can be added to the description
DesignLevel Logical_Only, Physical_Only  
Name Name Model Name
SystemType Target Server  
SystemTypeOld Target Server  
StoredProcedure Stored Procedure  
Comment Comment  
Description   optional: UDP values can be added to the description
DesignLevel Logical_Only, Physical_Only  
Name Name  
Semantics Template_Code  
Trigger Trigger Table Trigger
Comment Comment  
Name Name  
Semantics Trigger_Body  
TriggerType Trigger_Fire  
TypeValue Validation Rule  
Name Name  
Position Order  
Value Definition  

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!