IBM InfoSphere Data Architect (IDA) - Import - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • requires the tool to be installed to access its SDK.

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] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via Eclipse Java API on LDM or DBM XML File
Remote Repository Browsing for Model Selection
Data Profiling
Multi-Model Harvesting
Incremental Harvesting

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

BRIDGE DOCUMENTATION
Imports physical, logical model or domain model files (.dbm, .ldm or .ddm) generated by IBM Rational Data Architect.

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  
File Specify here the file path of the Data Architect physical, logical or domain model file (.dbm, .ldm or .ddm) to import. FILE
*.dbm
*.ldm
*.ddm
  Mandatory
Project Specify here the directory path of the Data Architect project.
It is used to detect references to Domain Models.
DIRECTORY      
Import dimensional diagrams as Data Architect models may use dimensional notation, allowing tables to be marked as a Dimension or Fact. Therefore, the model may contain one or more relational diagrams, in addition to one or more dimensional diagrams. In order to ensure the correct forward engineering into Business Intelligence tools, you may want to specify how diagrams are converted.

'Dimensional diagrams only' : the diagram will only display the dimensions and facts
'Relational diagrams only' : the diagram will only display the relational tables
'Relational and dimensional' : the diagram will display both the dimensions, facts, and the associated relational tables

The default value for this option is 'Relational and dimensional'.
ENUMERATED
Dimensional diagrams only
Relational diagrams only
Relational and dimensional
Relational and dimensional  
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

 

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  
Description Documentation  
Name Label  
PhysicalName Name  
AssociationRole Relationship / Foreign Key Two roles are created for each Relationship
Description Documentation  
Multiplicity Existence, Cardinality  
Name Verb Phrase, Inverse Verb Phrase / Label  
OnDelete Referential Integrity: Delete  
OnInsert Referential Integrity: Insert  
OnUpdate Referential Integrity: Update  
PhysicalName Name  
Source   set to True on the Primary/Candidate Key side
Attribute Attribute / Column  
Description Documentation  
InitialValue Default Value  
Name Label  
Optional Required / Not Null  
PhysicalName Name  
Position   derived from the position in the Entity/parent table
BaseType Attribute / Column Datatype  
DataType   See datatype conversion array
Name   Based on the datatype
PhysicalName   Derived from the datatype
BusinessRule Domain Constraint, Entity Constraint, Check Constraint Each constraint is imported as a BusinessRule and connected to its applicable object (LDM). Table level CheckConstraints are imported as BusinessRules (DBM)
Description Documentation  
Name Label  
PhysicalName Name  
Type   set to ENUMERATION_LIST for Domain Enumeration Constraint set to PHYSICAL_TEXT for Entity SQL Constraints set to LOGICAL_TEXT for Entity non-SQL Constraints
Value Expression  
CandidateKey PrimaryKey, AlternateKey, InversionEntry  
Comment Documentation  
Name Label  
PhysicalName Name  
UniqueKey   set to TRUE for PrimaryKey, AlternateKey set to FALSE for InversionEntry
Class Entity / Table  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Documentation  
Name Label  
PhysicalName Name  
ClassDiagram Diagram  
Description   Not used
Name Name  
PhysicalName   Not used
DatabaseSchema Schema A default schema is created to connect the entities to the default catalog in LDM
Comment   default in LDM
Description Documentation default in LDM
Name Label default in LDM
PhysicalName Name default in LDM
DerivedType Attribute Type, Domain / Column DataType, Distinct UserDefined Type  
DataType Item type See datatype conversion array
Description Documentation  
Length Length or inherited from a Domain Length Constraint, if any
LowerBound   inherited from a MinimumInclusive (or MinimumExclusive) constraint
Name Label Based on the datatype
NativeDataType Item type / DataType If the Item type is another Domain, use the parent Domain Item type see the DataType conversion array
PhysicalName Name Derived from the datatype (DBM)
Scale Scale or inherited from a Domain FractionDigit Constraint, if any
UpperBound   inherited from a MaximumInclusive (or MaximumExclusive) constraint
UserDataType   set to FALSE(LDM), set to TRUE for Distinct UserDefined Type, FALSE otherwise (DBM)
UserDefined   set to TRUE for Domains (LDM), set to TRUE for Distinct UserDefined Type, FALSE otherwise (PDM)
DesignPackage Package(LDM) / Schema (DBM) An equivalent DesignPackage is created for each DatabaseSchema
Description Documentation  
Name Label  
PhysicalName Name  
UserDefined   set to TRUE (LDM), False (DBM)
ForeignKey ForeignKey  
Description Documentation  
Name Label  
PhysicalName Name  
Generalization Generalization  
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  
Name Label  
PhysicalName Name  
Unique Unique  
IndexMember IndexColumn  
Description Documentation  
Name Label  
PhysicalName Name  
Position   column position
SortOrder SortOrder  
Note Diagram Note Notes attached to Entities are imported as Notes
Name   Not used
Value Description  
Projection Diagram Node  
BackgroundColor FillColor  
Bold Bold  
FontColor FontColor  
FontName FontName  
FontSize FontSize  
Height Height The height is not available if the box is in AutoSize mode
Italic Italic  
LineColor LineColor  
Name   Not used
Strike StrikeThrough  
Underline Underline  
Width Width The width is not available if the box is in AutoSize mode
X X  
Y Y  
PropertyElementTypeScope User Defined Property  
Scope   Object type the property applies to
PropertyType User Defined Property  
DataType   set to VARCHAR
Name Name  
Usage   set to USER
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  
SQLViewAttribute ViewColumn  
Description Documentation  
Name Label  
Optional Not Null  
PhysicalName Name  
Position   column position
SQLViewEntity View  
Description Documentation  
Name Label  
PhysicalName Name  
WhereClause SQL  
StoreModel Logical Data Model/Physical Data Model The model is built using the elements contained in the .LDM file
Name file name  
SystemType Database Type and Version set to <Logical> for LDM
SystemTypeOld Database Type and Version set to <Logical> for LDM
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  
Description Documentation  
Name Label  
PhysicalName Name  
Trigger Trigger  
Description Documentation  
FireOnDelete Delete  
FireOnInsert Insert  
FireOnUpdate Update  
Name Label  
PhysicalName Name  
Semantics Source  
TriggerType ActionTime  
TypeValue Value No equivalent in RDA DBM, only used in LDM.Each Value of an EnumerationConstraint is imported as TypeValue
Description Description  
Name Label  
Position   derived from the Value position in the Enumeration List
Value Name