Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Oracle Designer

Bridge Specifications

Vendor Oracle
Tool Name Oracle Designer
Tool Version 1.3.2, 2.1.2, 6.0, 6i to 10g
Tool Web Site http://www.oracle.com/technology/products/designer/index.html
Supported Methodology [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model) via DAT File

Import tool: Oracle Oracle Designer 1.3.2, 2.1.2, 6.0, 6i to 10g (http://www.oracle.com/technology/products/designer/index.html)
Import interface: [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model) via DAT File from Oracle Designer
Import bridge: 'OracleDesigner' 9.1.1

This bridge imports an E/R Model, or a Server Model from an Oracle Designer .DAT file.
Please refer to the bridge File parameter for details on how to generate the .DAT file.

Any given .DAT file may contain:
* an E/R Model (with entities),
* a Server Model (with tables),
* many Database Implementation Models (with table implementations).

The bridge does not support Database Implementation models.


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Start the Oracle Designer tool and provide the required Username, Password and Connect String in order to connect to the Oracle Designer Repository. Once you are logged in, start the Repository Object Navigator tool by clicking on the Navigator icon. Then, browse through the repository tree structure to select the metadata objects to export.
It is usually recommended to export a complete Application System, so that the produced DAT file is complete and does not contained references to objects not defined in the file. Alternatively, you can also select a set of individual entities or tables in the repository tree to be exported to the DAT file. However, you should not export diagram objects, since the produced DAT file will not contain the definition of the metadata objects, but only the diagram graphical information.

On Oracle Designer 6i & 9i:

1. Select 'Export...' in the 'Utilities' menu,
2. Select 'Export data to a text file' and click on 'Next'.
3. Select the object you want to export (the loaded model is selected by default) and click on 'Next'.
4. Type the name of the file you want to export to or browse to select it and click on 'Finish'.

On Oracle Designer 2000:

1. Select the set of Entities you want to export from Designer 2000.
2. Choose 'Unload' from the 'File' menu (if you use Designer 2000 1.3.2) or from the 'Utilities' menu (if you use Designer 2000 2.1.2).
3. Type the file name for the model you are saving in the 'File Name' text box (eventually press the browse button to select a specific directory).
4. Click 'Save'.
5. Click 'Ok' when the processing is finished.

The bridge will use the generated DAT file as input.

FILE *.dat   Mandatory
Model selection This option allows one to select what model to import from the file.

It is only useful when the file contains both an E/R Model and a Server Model:

'E/R Model' - Only the E/R Model is imported (default).

'Server Model' - Only the Server Model is imported.

'E/R Model and Server Model' - Both E/R Model and Server Model are imported as separate models.

In case the file contains only an E/R Model or a Server Model, this option does not apply and the bridge imports that model.
ENUMERATED
E/R Model
Server Model
E/R Model and Server Model
E/R Model  
Import UDPs A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects the property applies to may also specify an explicit value for this property, or no value at all in which case the default value of the property definition applies.

This option allows you to control how property definitions and values are imported:

By default, the bridge imports the property definition as a Property Type.

'As metadata' - Import an explicit value as Property Value, implicit values are not imported, the default value is kept on the Property Type only. This is the default behavior.

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

'In description, migrate default values' - Append the property name and value, even if implicit, to the object's description property only. 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
As metadata, migrate default values
In description, migrate default values
Both, migrate default values
As metadata  
Insert the description in the comment field Insert the Description in the Comment property for all objects. BOOLEAN   False  
Encoding Specifies the character set encoding of the model to be imported or exported:

If there are multiple choices for a language, the actual encoding will be indicated between parentheses.

The default is 'Western European (Windows 1252)' on Windows and 'Western European (ISO 8859-1)' on other platforms.
ENUMERATED
Central and Eastern European (iso-8859-2)
Central and Eastern European (windows-1250)
Chinese Traditional (big5)
Chinese Simplified (GB18030)
Chinese Simplified (GB2312)
Cyrillic (iso-8859-5)
Cyrillic (windows-1251)
DOS (ibm-850)
Greek (iso-8859-7)
Greek (windows-1253)
Hebrew (iso-8859-8)
Hebrew (windows-1255)
Japanese (shift_jis)
Korean (ks_c_5601-1987)
Thai (TIS620)
Thai (windows-874)
Turkish (iso-8859-9)
Turkish (windows-1254)
UTF 8 (utf-8)
UTF 16 (utf-16)
Western European (iso-8859-1)
Western European (iso-8859-15)
Western European (windows-1252)
Locale encoding
No encoding conversion
windows-1252  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Oracle Designer"
Metamodel
OracleDesigner
Mapping Comments
     
Association Relationship, Relationship Ends/Foreign Key an association is created for each foreign key found in the model
Aggregation   True if one of the role is part of a unique identifier (UIE). True if the foreign key columns are part of the primary key
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Foreign key name default for logical
AssociationRole Relationship, Relationship Ends/Foreign Key  
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Multiplicity Minimum Cardinality, Maximum Cardinality  
Name Relationship End Name  
Source   Based on the direction of creation, multiplicity of each role and if one end is part of a unique identifer. Set to True for the parent role (physical level)
AssociationRoleNameMap Relationship Ends/Foreign Key columns The association between the primary key attribute and the foreign key attribute. Name mapping between a foreign key column and its associated primary key column (Physical level)
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Attribute Attribute/Column see DerivedType for the attribute's datatype information mapping
Comment Comment  
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
InitialValue Default Value  
Name Name  
Optional Optional  
PhysicalName Name  
Position Sequence Number  
BaseType Attribute Format/Column Format  
DataType Format See datatype conversion array
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Name  
CandidateKey Unique Identifier/Unique Key, Primary Key Primary UID Flag indicates a primary key
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Name  
PhysicalName Name  
UniqueKey   set to True
Class Entity/Table  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
DimensionalRole DataWarehouse Type  
Name Name  
PhysicalName Short Name/Name  
ClassDiagram Entity Relationship Diagram/Server Model Diagram, Data Structure Diagram  
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Title  
PhysicalName Name  
DatabaseSchema   No equivalent in Oracle Designer ER Modeling (Logical level)
DerivedType Domain, Attribute Datatype, Allowable Values  
Comment Comment  
DataType Format See datatype conversion array
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
InitialValue Default Value  
Length Maximum Length  
LowerBound Allowable Values : Low Value  
Name Name  
PhysicalName Name / Datatype  
Scale Decimal Places  
UpperBound Allowable Values : High Value  
UserDefined   True for Domain
DesignPackage Folder Folders are not mapped into packages since this notion is only supported since version 6i. A package (Logical View) is created to contain the logical information.
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
UserDefined   set to False
ForeignKey Foreign Key Generated for associations (logical level)
Description Description default for logical level
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Name default for logical level
PhysicalName Name default for logical level
Generalization Subtype  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
GeneralizationRole Subtype  
Index Index Associated with each key for logical level
Comment Comment  
Description Description default for logical level
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Name default for logical level
PhysicalName Name default for logical level
IndexMember Index entries Links each attribute in the key to the index associated to the key
Position Usage sequence / Sequence in key Computed
Note Notes  
PropertyElementTypeScope User Extensions  
Scope   Element Type the user defined property applies to
PropertyType User Defined Property, Extended Text Property  
DataType   set to MIR_DATATYPE_VARCHAR
DesignLevel   Inferred from the Designer object Element Type the property applies to
Name Property Name Display Name is not available in the file
PhysicalName   Not used
Usage   set to User
PropertyValue User Defined Property Value  
Value property value  
SQLViewAssociation View, Table No equivalent in Oracle Designer ER Modeling (Logical level). associations between views and tables (Physical level)
SQLViewAttribute View Column  
Comment Comment  
Description Description  
Name Prompt  
PhysicalName Name  
Position Sequence in Table  
SQLViewEntity View, Materialized View  
Comment Comment  
Description Description  
Name Display Title  
PhysicalName Name  
WhereClause Where / Validation condition  
StoreModel Application Systems, ER Model The model is built using the elements contained in the Oracle Designer DAT file
Comment Comment  
Description Description  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Title The application system's title or extracted from the file name.
PhysicalName Name The application system's name or extracted from the file name.
Trigger Trigger, PL/SQL Definition  
Description Description  
FireOnDelete Delete  
FireOnInsert Insert  
FireOnUpdate Update  
Name Name  
PhysicalName Name  
Semantics PL/SQL Definition  
TriggerType Execution Time  
TypeValue Allowable values  
DesignLevel   default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object.
Name Meaning/Value  
Position RadioSequence, Display Sequence  
Value Value  

Last updated on Wed, 12 Jul 2017 18:34:41

Copyright © Meta Integration Technology, Inc. 1997-2017 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.