CA COOL:DBA (Terrain for DB2) 5.3.2 - 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:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor CA technologies
Tool Name COOL:DBA
Tool Version 5.3.2
Tool Web Site http://www.ca.com/acq/sterling/
Supported Methodology [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing) via VAR Export File
Remote Repository Browsing for Model Selection
Data Profiling
Multi-Model Harvesting
Incremental Harvesting

Import tool: CA technologies COOL:DBA 5.3.2 (http://www.ca.com/acq/sterling/)
Import interface: [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing) via VAR Export File from CA COOL:DBA (Terrain for DB2) 5.3.2 Import bridge: 'CaTerrainDb2' 10.1.0

Please enter a description


Bridge Parameters

Parameter Name Description Type Values Default Scope
File When a model is currently loaded in Sterling Software COOL:DBA (Cayenne Terrain for DB2):

1. Choose 'Export' from the 'File' menu.

2. Type the file name for the model you are saving in the 'File Name' text box (browse to select a specific directory).

3. Click 'Save'.

The bridge will use the generated VAR file as input.

Some versions of the Terrain design tool, such as Sterling COOL:DBA 2.1.6, may offer the choice between multiple VAR export format flavors:
- The 'Terrain for DB2 5.3 format' flavor is supported by this bridge
- The 'Terrain for DB2 5.4 format' flavor is supported by this bridge
- The 'COOL:DBA 2.1 format' flavor is supported by this bridge
- The 'COOL:DBA 2.x Full Meta Format' flavor is not supported by this bridge
FILE *.var   Mandatory
CREATE VIEW fix This option adds an extra ';' at the end of the 'CREATE VIEW' SQL statement. This is a workaround for some of our customers and should not be changed unless you know for certain that you need it. 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)
"CA COOL:DBA (Terrain for DB2) 5.3.2"
Metamodel
CaTerrainDb2
Mapping Comments
     
Association Foreign Key, Primary Key Created for each foreign key
Aggregation   Based on attributes belonging both to a primary key and a foreign key associated with the association
AssociationRole Foreign Key, Primary Key  
ExtraConstraint Delete Rule  
Multiplicity 1-n/1-1 or 1-n/0-1 Based on the NULL status of the attribute belonging to the foreign key
Source   False for the Association Role attached with the foreign key
AssociationRoleNameMap Foreign Key, Primary Key When columns at the same position don't have the same name
Attribute Table Column  
Comment Comment On  
Description Description  
Name Name  
Optional Nulls group  
PhysicalName Name  
Position Number  
BaseType Attribute (Type property) Created as side effect of Derived Type creation
DataType Type See datatype conversion array
Name Type Standard name based on the type
PhysicalName Type Standard name based on the type
CandidateKey Primary Key, Index  
Description Description  
Name Name  
PhysicalName Name  
UniqueKey Unique  
Class Table  
Comment Comment On  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Description  
Name Name  
PhysicalName Name  
ClassDiagram   No equivalent in Terrain for DB2. A main class diagram "Main" will be created to contain all entities/references
DerivedType Attribute (Type property)  
DataType Type See datatype conversion array
Length Length  
Name Name  
PhysicalName Name  
Scale Scale  
UserDefined   Always False
DesignPackage   No equivalent in Terrain for DB2. A main package "Logical View" will be created to contain all entities/references
ForeignKey Foreign Key  
Description Description  
Name Name  
PhysicalName Name  
Index Index, Primary Key, Foreign Key Associated with each key
Name Name  
PhysicalName Name  
IndexMember   Associated with each attribute in a key
Position Position  
SortOrder Ascending/Descending order  
PhysicalObject TableSpace, Database, StorageGroup, BufferPool  
PhysicalRelationship   To connect the Physical Object
PhysicalTarget   One object is created for a DB2 target system
Projection TableProjection Graphical Information
Height height  
Width width  
X x  
Y y  
SQLViewAssociation View (selected Tables)  
SQLViewAttribute View Column When the View Column is associated with a Table Column
Position Number  
SQLViewEntity View  
Comment Comment On  
Description Description  
Name Name  
PhysicalName Name  
WhereClause Create View Statement  
StoreModel Terrain for DB2 design  
Name Name  
Synonym Table Synonym, View Synonym  
Name Name