 |
|
|||||||
 |
   
|
|
||||||
|
|
|||||||
|
|
|
||||||
 |
 |
 |
 |
|
 |
|
 |
 |
| 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] 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] Data Store (Physical Data Model, Logical Data Model) via DAT File from Import bridge: 'OracleDesigner' 7.0.4 - 2012-05-15 19:35:31
| Parameter Name | Description | Type | Values | Default | Scope | ||||||||||||||||||||||||
| File | Start the Oracle Designer tool and provide the required User Name, 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. 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 | |||||||||||||||||||||||||
| Design Level Filter | This option allows to select what metadata design level should be imported from the file. It is only useful when the file contains both logical entities from an E/R Model and physical tables from a Server Model: 'None' - Entities are imported as logical only and Tables are imported as physical only (default). 'E/R Model' - Entities are imported as logical and physical, and Tables are dropped. 'Server Model' - Entities are dropped and Tables are imported as logical and physical. In case the file contains only Entities or only Tables, they are always imported as logical and physical and this option doesn't apply. |
ENUMERATED |
|
None | |||||||||||||||||||||||||
| 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 | |||||||||||||||||||||||||
| Insert the description in the comment field | Insert the Description in the Comment property for all objects. | BOOLEAN | False | ||||||||||||||||||||||||||
| Import IDs | Each object defined in the DAT file has an ID. This option allows you to specify whether the bridge should import them in the NativeId property. 'True' - The DAT file ID is saved in the NativeId property. This is the default. 'False' - The DAT file ID is ignored. |
BOOLEAN | True | ||||||||||||||||||||||||||
| 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 |
|
Western European (windows-1252) |
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Designer" Metamodel |
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 | |
| 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 Tue, 15 May 2012 19:39:38
