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

MIMB Bridge Documentation

MIMB Export Bridge to IBM InfoSphere Data Architect (IDA)

Bridge Specifications

Vendor IBM
Tool Name InfoSphere Data Architect (IDA)
Tool Version 6.1 to 9.1
Tool Web Site http://www.ibm.com/software/data/integration/rda/
Supported Methodology [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via IDA Eclipse Java API on LDM or DBM or DDM XML File

Export tool: IBM InfoSphere Data Architect (IDA) 6.1 to 9.1 (http://www.ibm.com/software/data/integration/rda/)
Export interface: [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via IDA Eclipse Java API on LDM or DBM or DDM XML File to IBM InfoSphere Data Architect (IDA)
Export bridge: 'IbmRationalDataArchitect' 10.0.0

This bridge generates physical or logical model files (.dbm or .ldm).

FREQUENTLY ASKED QUESTIONS

Q: Does the bridge have any 3rd party dependencies?
A: Yes. The bridge depends on a set of plugin files that you can find under your Data Architect's plugins directories in version 6.1 or in the shared directory in version 7.
Here is the list of ids for the required plugin files:

org.eclipse.gmf.runtime.notation
org.eclipse.emf.common
org.eclipse.emf.ecore.xmi
org.eclipse.emf.ecore
org.eclipse.emf.commonj.sdo
org.eclipse.emf.ecore.sdo
org.eclipse.wst.rdb.models.sql
com.ibm.db.models.db2
com.ibm.datatools.datanotation
com.ibm.db.models.logical
com.ibm.db.models.oracle
com.ibm.db.models.teradata

Please configure the 'Installation directory' option to specify the Data Architect installation path.


Bridge Parameters

Parameter Name Description Type Values Default Scope
Version Select here the version of Data Architect you want to connect to.

This software version must be installed on the computer running this bridge.
ENUMERATED
Latest
9.1.3
9.1.2
9.1.1
9.1.0
8.5.0
8.1.0
7.6.0
7.5.3
7.5.2
7.5.0
7.0 FP3
7.0
6.1 FP1
6.1
Latest  
Directory Directory where to generate Data Architect physical and/or logical model files (.dbm or .ldm).

In order to load the converted model(s), start the tool and import the file(s).
DIRECTORY     Mandatory
Base file name Base name of the file(s) to produce.

The bridge uses the target directory and base file name in combination with file extension (.DBM or .LDM) to produce the complete output file(s) path(s).

When converting a single model, this bridge may generate 1 or 2 LDM, DBM files, depending on the 'Design level' parameter and the Design level of the source model. The name of these files can be specified in this bridge parameter, or computed from the source model name if unspecified here.

When exporting from multi-model sources, this bridge may generate many LDM and DBM files, named according to their original names from the source tool.
STRING      
Design level Design level of the data model to generate.

'Auto detect' : will generate a data model according to the design level set in the source tool
'Logical only' : will generate a logical data model
'Physical only' : will generate a physical data model
The default value for this option is 'Auto detect'
ENUMERATED
Auto detect
Physical only
Logical only
Auto detect  
Target database Specifies the database type of the generated physical model (if any).

By choosing the default value 'Auto detect', the bridge will try to auto-detect the target database from the source model.
Choosing a specific database type will force the bridge to generate a physical model for this database:

- the Database object 'Type' and 'Version' properties will be set accordingly

- all columns datatypes will be generated according to datatypes available on this platform.

The Tables and Columns names are not automatically changed by this parameter.

If the selected database has specific name length constraints, the names may have to be updated manually.
ENUMERATED
Auto detect
IBM Cloudscape 5.1
IBM Derby 10.0
IBM DB2 UDB V8.1
IBM DB2 UDB V8.2
IBM DB2 UDB V9.1
IBM DB2 UDB V9.5
IBM DB2 UDB V9.7
IBM DB2 UDB V9.8
IBM DB2 UDB V10.1
IBM DB2 UDB V10.5
IBM DB2 UDB iSeries V5R1
IBM DB2 UDB iSeries V5R2
IBM DB2 UDB iSeries V5R3
IBM DB2 UDB iSeries V5R4
IBM DB2 UDB iSeries V6R1
IBM DB2 UDB iSeries V7R1
IBM DB2 UDB zSeries V7
IBM DB2 UDB zSeries V8 (New-Function Mode)
IBM DB2 UDB zSeries V8 (Compatibility Mode)
IBM DB2 UDB zSeries V9 (New-Function Mode)
IBM DB2 UDB zSeries V9 (Compatibility Mode)
IBM DB2 UDB zSeries V10 (New-Function Mode)
IBM DB2 UDB zSeries V10 (Conversion Mode)
IBM DB2 UDB zSeries V11 (New-Function Mode)
IBM DB2 UDB zSeries V11 (Conversion Mode)
IBM InfoSphere BigInsights 2.1
Generic JDBC 1.0
INFORMIX SQL 9.2
INFORMIX SQL 9.3
INFORMIX SQL 9.4
INFORMIX SQL 10.0
INFORMIX SQL 11.1
INFORMIX SQL 11.5
INFORMIX SQL 11.7
Microsoft SQL Server 2000
Microsoft SQL Server 2005
Microsoft SQL Server 2008
Microsoft SQL Server 2012
MySQL 4.0
MySQL 4.1
MySQL 5.0
MySQL 5.1
Netezza 6.x
Netezza 7.x
ORACLE Version 7.3
ORACLE Version 8
ORACLE Version 9
ORACLE Version 10
ORACLE Version 11
PostgreSQL 8.x
PostgreSQL 9.x
Sybase 12.0
Sybase 12.5
Sybase 12.x
Sybase 15.0
Sybase ASE 15.0
SAP ASE 15.5
SAP ASE 15.7
Teradata 2.x
Teradata 12.x
Teradata 13.x
Teradata 14.x
Auto detect  
Installation directory The full path to the Data Architect installation directory. The directory is used to search for proper JAR files used by the bridge.

For version 7.x, it should contain the eclipse 'configuration' directory, where the file 'platform.xml' exists.
For version 7.6.0, it might be 'C:\Program Files\IBM\IDA7.6.0'.
For version 7.5.2, it might be 'C:\Program Files\IBM\IDA7.5.2'.
For version 7.5.x, it might be 'C:\Program Files\IBM\SDP'.
For version 7.0.x, it might be 'C:\Program Files\IBM\SDP70'.

For version 6.x, it should contain the eclipse 'plugins' directory.
For version 6.1, it might be 'C:\Program Files\IBM\Rational\RDA\V6.1'.
DIRECTORY     Mandatory
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)
"IBM InfoSphere Data Architect (IDA)"
Metamodel
IbmRationalDataArchitect
Mapping Comments
     
Name Label  
Argument Parameter  
DefaultValue   Not used
Description Documentation  
Kind Mode  
Name Label  
PhysicalName Name  
Position   position of the argument in the Procedure or Function
Association Relationship / Foreign Key  
Aggregation Identifying / Not Identifying  
Description Documentation Not used
ExtraConstraint   Not used
Name Label Not used
PhysicalName Name Not used
UserDefined   Not used
AssociationRole Relationship / Foreign Key Two roles are created for each Relationship
CppContainment   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
Description   Not used
ExtraConstraint   Not used
Multiplicity Existence, Cardinality  
Name Verb Phrase, Inverse Verb Phrase / Label  
Navigable   Not used
OnDelete Referential Integrity: Delete  
OnInsert Referential Integrity: Insert  
OnUpdate Referential Integrity: Update  
Ordered   Not used
PhysicalName   Not used
Position   Not used
Source   Identifies the parent side (PrimaryKey) of the relationship
Attribute Attribute / Column  
Description Documentation  
ExtraConstraint   Not used
InitialValue DefaultValue Not used
Name Label  
Optional Required / Not Null Not used
PhysicalName Name  
Position   position in the entity/table
BaseType Attribute / Column Datatype No equivalent, Attributes linked to a BaseType are exported with their ItemType set to the equivalent DataType
DataType Datatype see datatype conversion array
Description   Not used
Length Length  
Name   Not used
PhysicalName   Not used
Scale Scale  
BusinessRule Domain Constraint, Entity Constraint, Check Constraint BusinessRules related to Class and Attribute are exported as Entity Constraint BusinessRules related to user-defined DerivedType are exported as DomainConstraint (LDM). BusinessRules of type TextPhysical and associated to Attributes and Classes are exported as Table CheckConstraints (DBM)
Description Documentation  
LowerBound   Not used
Name Label  
PhysicalName Name  
Type   export Enumeration Constraint if set to ENUMERATED_LIST export Entity Constraint if set to PHYSICAL_TEXT and related to Class or Attribute (LDM). only BusinessRules of type TEXT_PHYSICAL are exported (DBM)
UpperBound   Not used
Value   Not used
CandidateKey PrimaryKey, AlternateKey, InversionEntry  
Comment Documentation  
Name Label  
PhysicalName Name  
UniqueKey   InversionEntry if set to FALSE (LDM). A UniqueConstraint is created for each CandidateKey A PrimaryKey is created if the CandidateKey is Primary of its Class (DBM)
Class Entity / Table  
CppAbstract   Not used
CppClassType   Not used
CppConcurrency   Not used
CppMultiplicity   Not used
CppPersistent   Not used
CppScope   Not used
CppSpace   Not used
Description Documentation  
DimensionalRole   Not used
DimensionalType   Not used
Name Label  
PhysicalName Name  
ClassDiagram Diagram  
Description   Not used
Name Name  
PhysicalName   Not used
DatabaseSchema Schema  
Comment   default in LDM
Description Documentation default in LDM
Name Label default in LDM
PhysicalName Name default in LDM
DerivedType AtomicDomain, Attribute DataType  
DataType Item type Use the parent DerivedType as ItemType if it defined as a Domain, otherwise, map the DataType to a base ItemType (see datatype conversion array)
Description Documentation  
InitialValue   Not used
Length   create a Length Constraint to represent the length
LowerBound   create a MaximumInclusive Constraint to represent the lowerBound property
Name Label Based on the datatype
NativeDataType   Not used
NativeLogicalDataType   Not used
PhysicalName Name Derived from the datatype (DBM)
Scale   create a FractionDigit Constraint to represent the scale
UpperBound   create a MinimumInclusive Constraint to represent the upperBound property
UserDataType   Not used
UserDefined   Only UserDefined DerivedTypes are exported as Domain
DesignPackage Package  
Description Documentation  
Name Label  
PhysicalName Name  
UserDefined   Only UserDefined DesignPackages are exported
ForeignKey ForeignKey  
Description Documentation  
Name Label  
PhysicalName Name  
Generalization Generalization  
CppFriend   Not used
CppScope   Not used
CppVirtual   Not used
Description Documentation  
Name Label  
PhysicalName Name  
GeneralizationRole Generalization  
Identity Identity properties  
Cycle Cycle  
IncrementValue Increment By  
MaximumValue Maximum Value  
MinimumValue Minimum Value  
StartValue Starting Value  
Index Index  
Clustered Clustered  
Description Documentation  
Generate   Not used
Name Label  
PhysicalName Name  
Unique Unique  
IndexMember IndexColumn  
Description Documentation  
Name Label  
PhysicalName Name  
Position   index member position in its Index
SortOrder SortOrder  
Operation Function  
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description Documentation  
Name Label  
PhysicalName Name  
Position   Not used
Postcondition   Not used
Precondition   Not used
Semantics Source  
Projection Diagram Node  
BackgroundColor FillColor  
Bold Bold  
FontColor FontColor  
FontName FontName  
FontSize FontSize  
Height Height The height is not exported in order to Autosize the box
Italic Italic  
LineColor LineColor  
Name   Not used
Strike StrikeThrough  
Underline Underline  
Width Width The width is not exported in order to Autosize the box
X X  
Y Y  
PropertyElementTypeScope User Defined Property  
Scope   Object type the property applies to
PropertyType User Defined Property  
DataType   set to VARCHAR
Description   Not used
DesignLevel   Not used
Group   Not used
InitialValue   Not used
Name Name  
PhysicalName   Not used
Position   Not used
Usage   only USER properties are exported
PropertyValue User Defined Property  
Value Value  
RelationshipProjection Diagram Edge  
BackgroundColor FillColor  
Bold Bold  
FontColor FontColor  
FontName FontName  
FontSize FontSize  
Height   Not used
Italic Italic  
LineColor LineColor  
LinePoints BendPoints  
Name   Not used
Strike StrikeThrough  
Underline Underline  
Width   Not used
X   Not used
Y   Not used
SQLViewAssociation View Dependency  
Description Documentation  
Name Label  
PhysicalName Name  
SQLTableSequence   Not used
SQLViewAttribute ViewColumn  
Description Documentation  
Expression   Not used
Name Label  
Optional Not Null  
PhysicalName Name  
Position   column position
SQLViewEntity View  
Description Documentation  
DimensionalRole   Not used
Name Label  
PhysicalName Name  
WhereClause SQL  
StoreModel Package / Physical Data Model A root Package is created to represent the Model
Description Documentation Not used in DBM
Name Label / DBM File Name  
PhysicalName Name Not used in DBM
SystemMajorVersion   Not used
SystemMinorVersion   Not used
SystemReleaseVersion   Not used
SystemType Database Type and Version set to <Logical> for LDM. The value can be overloaded with the "Target database" bridge option for DBM
SystemTypeOld Database Type and Version set to <Logical> for LDM. The value can be overloaded with the "Target database" bridge option for DBM
StoredProcedure Procedure  
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description Documentation  
Name Label  
PhysicalName Name  
Position   Not used
Postcondition   Not used
Precondition   Not used
Semantics Source  
Synonym Alias  
Description Documentation  
Name Label  
PhysicalName Name  
Trigger Trigger  
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description Documentation  
FireOnDelete Delete  
FireOnInsert Insert  
FireOnUpdate Update  
Name Label  
PhysicalName Name  
Postcondition   Not used
Precondition   Not used
Semantics SQL  
TriggerType ActionTime  
TypeValue Value No equivalent and not exported in RDA DBM, only used in LDM.Each Value of an EnumerationConstraint is imported as TypeValue
Description Documentation  
Name Label  
PhysicalName Name  
Position   position in the list
Value Name  

Last updated on Wed, 15 Aug 2018 14:48:03

Copyright © Meta Integration Technology, Inc. 1997-2018 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.