Oracle Data Modeler (ODM) 4.x (via erwin 4 XML) - Export
Bridge Requirements
This bridge:is only supported on Microsoft Windows.
Bridge Specifications
Vendor | Oracle |
Tool Name | Oracle Data Modeler (ODM) |
Tool Version | 4.x |
Tool Web Site | http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html |
Supported Methodology | [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via COM API on Native (.ER1) or Export (.XML) File |
SPECIFICATIONS
Tool: Oracle / Oracle Data Modeler (ODM) version 4.x via COM API on Native (.ER1) or Export (.XML) File
See http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html
Metadata: [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout
Component: CaErwin4XmlExport.OracleDataModeler version 11.2.0
OVERVIEW
This bridge generates an erwin DATA MODELER V4.X (ER1 FORMAT) 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
Q: What versions of erwin 4 does this model bridge support?
A: This erwin 4 model bridge exports XML files compatible with:
* erwin 4.0 with Service Pack 1 (build 1511) and later builds such as erwin 4.0 Service Pack 2 (build 1687),
* erwin 4.1
This erwin 4 model bridge does not support the XML format as specified in earlier versions of erwin 4, such as erwin 4.0 Patch 1 (build 1338).
To update your copy of erwin 4, please contact your the vendor representative.
Q: erwin complains that my model's target database is no longer supported, what should I do?
A: Use erwin to change the model's target database to a new equivalent target database.
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 ER1 metadata files. Therefore, erwin 4 Data Modeler must be properly installed on the machine prior to 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 | This bridge generates either an XML or .ER1 (native erwin) file. This bridge determines which format based upon the extension of the file 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 |
|
Mandatory | |||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||
Target database | The target database type. 'Auto Detect' Attempt to auto-detect the target database type from the source model Database types suffixed with (*) Only valid in erwin since version 4.1. Databases suffixed with (**) Only valid in erwin since version 4.1.4. |
ENUMERATED |
|
Auto Detect | |||||||||||||||||||||||||||||||||||||||||||||
Transform level | The objects you want to transform during the export. | ENUMERATED |
|
Many to many and generalization | |||||||||||||||||||||||||||||||||||||||||||||
Order Attributes on Primary Key position | Order the Attributes in the order of the Primary key. The default is to order the Attributes based on their position in the Entity. |
BOOLEAN | False | ||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||
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) |
"Oracle Data Modeler (ODM) 4.x (via erwin 4 XML)" Metamodel CaErwin4Xml |
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 |
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, Validation Rule | |
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 | |
LowerBound | Validation_Rule_Max_Value | |
Name | Name | |
PhysicalName | Physical_Domain_Name | Mapped only if the Model is generated as Physical Only |
Scale | Datatype | |
UpperBound | Validation_Rule_Max_Value | |
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 | |
Projection | Drawing Object | Graphical Information |
BackgroundColor | background color | |
Bold | bold | |
FontColor | font color | |
FontName | font | |
FontSize | font size | |
Height | height | |
Italic | italic | |
LineColor | outline color | |
Strike | strikeout | |
Underline | underline | |
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 | background color | |
Bold | bold | |
FontColor | font color | |
FontName | font | |
FontSize | font size | |
Italic | italic | |
LineColor | outline color | |
LinePoints | Relationship path | |
Strike | strikeout | |
Underline | underline | |
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 | Drawing Object | |
BackgroundColor | Fill Color | Shape's background color |
Bold | Font, Bold | Text property |
FontColor | Font Color | |
FontName | Font | Font typeface name |
FontSize | Font Size | |
Height | Used to provide location information for the shape | |
Italic | Font Italic | Text property |
LineColor | Line Color | Shape outline color |
LinePoints | Vertex coordinates for polygons and polylines, end points for straight lines | |
Name | Name | Name of the shape as stored in MIR model |
ShapeType | Type of the shape in the drawing objects palette | |
Strike | Font Strikeout | Text property |
Underline | Font Underline | |
X | Used to provide location information for the shape | |
Y | Used to provide location information for the shape | |
Z | If present, specifies Z order of the shape | |
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 | |
Name | Name | |
Trigger | Trigger | Table Trigger |
Comment | Comment | |
Name | Name | |
Semantics | Trigger_Body | |
TriggerType | Trigger_Fire | |
TypeValue | Validation Rule | |
Name | Name | |
Position | Order | |
Value | Definition |