CA COOL:DBA (Terrain for DB2) 5.3.2 - Import
Availability-note
AWS
AWS-only features are available at any of the following URLs: us.cloud.talend.com, eu.cloud.talend.com, ap.cloud.talend.com
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 |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting | |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: CA technologies / COOL:DBA version 5.3.2 via VAR Export File
See http://www.ca.com/acq/sterling/
Metadata: [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing)
Component: CaTerrainDb2 version 11.2.0
OVERVIEW
n/a
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
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 | The character set encoding of the model to be imported. If there are multiple choices for a language, the actual encoding will be indicated between parentheses. |
ENUMERATED |
|
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 |