IBM DB2 Cube Views - 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 | IBM |
| Tool Name | DB2 Cube Views |
| Tool Version | 8.x |
| Tool Web Site | http://www.ibm.com/software/data/infosphere/warehouse/olap.html |
| Supported Methodology | [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing) via XML File |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting | |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: IBM / DB2 Cube Views version 8.x via XML File
See http://www.ibm.com/software/data/infosphere/warehouse/olap.html
Metadata: [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing)
Component: IbmDb2CubeViews version 11.2.0
OVERVIEW
n/a
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/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 CubeModel is currently loaded in IBM DB2 OLAP Center: 1. Choose 'Export...' from the 'OLAP Center' menu. 2. Type the file name for the model you are saving in the 'Export file name' text box 3. Click 'OK'. This bridge will use the generated XML file as input. |
FILE | *.xml | Mandatory | |||
| Data model table design level | This option controls the design level of the imported tables. It is particularly relevant when exporting metadata to a target tool which supports two views of the model: a logical view and a physical view. Some Data Modeling tools support this concept, where you can decide if a table appears both as a physical table and as a logical entity. Some Business Intelligence tools also support this concept, where you can decide if a table appears both in the physical model and in the business view of the model. Please set the option to: 'Logical and physical' The tables to appear both in the logical view and in the physical view of the model. 'Physical' Tables to appear only in the physical view of the model. |
ENUMERATED |
|
Physical | |||
| Dimensional model object names mapping | Controls how the OLAP objects' name and business name are imported. 'default mapping' The OLAP business name is imported as logical name, and the name is imported as physical name. 'alternate mapping' The OLAP name is imported as logical name, and the business name is imported as 'User Defined Property' for this object. |
ENUMERATED |
|
default mapping |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"IBM DB2 Cube Views" Metamodel IbmDb2CubeViews |
Mapping Comments |
| AggregationRule | AggregationScript | |
| Rule | Function | |
| Association | Join | If the Join is simple enough to be reversed engineered into a foreign key relationship |
| AssociationRole | Join | If the Join is simple enough to be reversed engineered into a foreign key relationship |
| AssociationRoleNameMap | Join | If the Join is simple enough to be reversed engineered into a foreign key relationship |
| Attribute | Column | |
| DesignLevel | as defined by the "Table Logical information" bridge option | |
| Name | name | |
| PhysicalName | Name | |
| Position | Computed from the reference position in the file | |
| BaseType | Datatype | |
| DataType | See datatype conversion array | |
| Length | Length | |
| Name | Derived from the datatype | |
| PhysicalName | Derived from the datatype | |
| Scale | Scale | |
| Class | Table | |
| DesignLevel | as defined by the "Table Logical information" bridge option | |
| Name | name | |
| ClassDiagram | CubeModel | A diagram is created for each CubeModel to represent the tables and relationships used in the CubeModel |
| Name | BusinessName | |
| ClassifierMap | Join, Dimension, Cube, CubeDimension | Used to hold the traceability of these objects, via FeatureMap objects |
| Condition | Join | used to hold the where clause of the join |
| Cube | Cube | |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| CubeDimensionAssociation | Cube, CubeDimension | defines which CubeDimensions are involved in the Cube |
| DatabaseSchema | Schema | Used to identify the relational and dimensional objects' owner |
| Name | name | |
| DesignPackage | CubeModel, Cube | One Package per CubeModel is created to store the Facts and Joins used in the CubeModel. One subPackage per Cube is created to store the CubeFacts and CubeDimension used in the Cube. In addition, one default Package is created to store all the dimensions. |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| UserDefined | Set to TRUE | |
| Dimension | Facts, Dimension, CubeDimension | |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| Type | Type | set to FACT for the Facts |
| UserDefined | set to FALSE for the CubeDimensions | |
| DimensionAttribute | Attribute, AttributeRelationship | |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| FeatureMap | Join, Attribute, Measure | Used to hold the traceability of Joins condition, Attributes and Measures |
| Description | Additional description, in case the expression is complex | |
| Operation | SQL Expression | |
| ForeignKey | Join | If the Join is simple enough to be reversed engineered into a foreign key relationship |
| Hierarchy | Hierarchy, CubeHierarchy | |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| HierarchyLevelAssociation | HierarchyAttribute | |
| Position | Computed from the position of the level in the Hierarchy | |
| Join | Join | |
| Description | Comments | |
| Name | BusinessName | |
| PhysicalName | Name | |
| Type | Join Type | |
| UserDefined | set to TRUE | |
| JoinRole | Join | |
| Multiplicity | Join Cardinality | |
| Level | HierarchyAttribute | |
| Name | BusinessName | |
| PhysicalName | Name | |
| LevelAssociation | HierarchyAttribute, RelatedAttribute | |
| Name | BusinessName | |
| PhysicalName | Name | |
| LevelKey | HierarchyAttribute | |
| Name | BusinessName | |
| Measure | Measure | |
| DefaultAggregation | Function for all dimensions | |
| Name | BusinessName | |
| PhysicalName | Name | |
| StoreModel | The model is built using the relational and dimensional defined in the XML file. | |
| Name | XML file name |