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

MIMB Bridge Documentation

MIMB Import Bridge from IBM Cognos Framework Manager (FM)

Bridge Specifications

Vendor IBM
Tool Name Cognos Framework Manager
Tool Version C8 v8.1 to C10
Tool Web Site http://www.ibm.com/software/analytics/cognos/
Supported Methodology [Business Intelligence] BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing) via XML File

Import tool: IBM Cognos Framework Manager C8 v8.1 to C10 (http://www.ibm.com/software/analytics/cognos/)
Import interface: [Business Intelligence] BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing) via XML File from IBM Cognos Framework Manager (FM)
Import bridge: 'CognosRnFrameworkManager2' 10.0.0

The bridge imports IBM Cognos Framework manager models in XML format.


KNOWN LIMITATIONS:

Cognos expressions may use a cognos proprietary macro language, the syntax of this language is not supported (parsed). Therefore lineage might be incomplete if any such macros are used.
SUPPORT

Q: How do I provide IBM Cognos Framework Manager metadata to support team to reproduce an issue?
A: If you have the Framework Manager project from which you published the package, please ZIP up that project and submit to support team.
If you do not have the Framework Manager project, you can export the IBM Cognos package of interest and send the resulting archive to support team.
For more details on exporting IBM Cognos server metadata please refer to IBM Cognos documentation, or to the description of IBM Cognos Content Manager import bridge.


Bridge Parameters

Parameter Name Description Type Values Default Scope
File The bridge uses the native XML file from IBM Cognos Framework Manager:

Use the ellipsis (...) button to navigate to the project's directory you want to import and select the file 'model.xml'.
FILE *.xml   Mandatory
Folder representation Select how folders from IBM Cognos Framework Manager should be represented.
'Ignore' - Folders are ignored
'Flat' - Folders are represented as Diagrams. Their hierarchy is not preserved
'Hierarchical' - Folders are represented as Diagrams and their hierarchy is preserved
ENUMERATED
Ignore
Flat
Hierarchical
Ignore  
Package representation Select how the packages from IBM Cognos Framework Manager should be represented.
'Ignore' - Ignore subject areas (default)
'Subject Areas' - Represent packages as subject areas
'Model' - Represent the package as the model (For published packages only)
ENUMERATED
Ignore
Subject Areas
Model
Ignore  
Tables 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.
'Logical and physical' - the tables will appear both in the logical view and in the physical view of the model.
'Physical' - the tables will appear only in the physical view of the model (default).
ENUMERATED
Physical
Logical and physical
Physical  
Ignore usage property Specify whether the usage property of a queryItem should be used.

'True' - a queryItem of usage attribute will be represented as a dimension attribute, and a queryItem of usage fact will be represented as a measure. (default)

'False' - ignore query items
BOOLEAN   True  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"IBM Cognos Framework Manager (FM)"
Metamodel
CognosRnFrameworkManager2
Mapping Comments
     
Name parameterName  
Argument ProcParameter  
DefaultValue value  
Kind mode  
Name parameterName  
Position   Position of the ProcParameter in the xml file
AssociationRole   No equivalent, see Join Role
Attribute QueryItem All QueryItems of a dbQuery will be mapped to an Attribute
Description description  
Name name  
Optional nullable  
PhysicalName columnName  
Position   Position of the QueryItem in the xml file
BaseType QueryItem Computed from the datatype of the QueryItem
DataType datatype  
Length precision,size Use Precision if it is not null, use Size otherwise
Name datatype  
Scale scale  
CandidateKey Key The first key by position in the xml file will be mapped as the primary candidate key of the dbQuery
Name name  
UniqueKey   Always set to true
Class dbQuery All dbQueries will be mapped to a Class
Description description  
Name name  
ClassDiagram Folder, Package A Class Diagram will be created for each folder if the option "Import folders" is not set to "No". And a Class Diagram will be created for each package if the option "Import packages" is set to "Yes".
Description description  
Name name  
ClassifierMap modelQuery,Filter,Relationship A Classifier Map will be created for each modelQuery/Filter/Relationship
Name   The name will be computed from the name of the modelQuery/Filter/Relationship
Condition Filter.Relationship  
Name   The name will be computed from the name of the Filter/Relationship
DatabaseSchema Data Source A Schema will be created for each Datasource with a non empty schema
Name schema  
DerivedType QueryItem Computed from the datatype of the QueryItem
DataType datatype  
Length precision,size Use Precision if it is not null, use Size otherwise
Name datatype  
Scale scale  
DesignPackage Namespace, Folder A Package is created for each namespace, and for each folder if the option "Import folders" is set to "Hierarchical"
Description description  
Name name  
UserDefined   Set to false only for the packages created to keep the folder hierarchy.
Dimension modelQuery  
Description description  
Name name  
Type   Set to "FactDimension" if the Dimension contains at least one measure
DimensionAttribute QueryItem All QueryItems of usage "attribute" or "identifier" of a modelQuery will be mapped to a Dimension Attribute
Description description  
Hide hidden  
Name name  
Sort unsortable  
Name name  
Name name  
FeatureMap QueryItem,Filter,Relationship A FeatureMap will be created for each QueryItem of a modelQuery and each expression of a Filter/Relationship
Name   The name will be computed from the name of the queryItem or Filter/Relationship
Operation expression  
Filter Filter  
Description description  
Name name  
Hierarchy Hierarchy  
Name name  
HierarchyLevelAssociation Hierarchy,Level  
Index Index  
Generate   Always set to true
Name   A name will be computed
IndexMember Index,QueryItem  
Name   The name will be computed from the name of the QueryItem
Position   Position of the QueryItem in the xml file
Join Relationship  
Type cardinality  
JoinRole Relationship  
Multiplicity cardinality  
Level Level  
Name name  
LevelAttribute Level,QueryItem  
Name name  
LevelKey Level  
Name name  
Measure QueryItem All QueryItems of usage "fact" of a modelQuery will be mapped to a Measure
DefaultAggregation regularAggregate  
Description description  
Hide hidden  
Name name  
Sort unsortable  
Projection Graphical information of Classes  
RelationshipProjection Graphical information of Associations  
SQLViewAssociation   No equivalent, see SQLViewEntity
SQLViewAttribute   No equivalent, see SQLViewEntity
SQLViewEntity   Not mapped: all dbQueries will be mapped as Class. See Class.
StoreConnection Data Source A Catalog will be created for each Datasource with a non empty catalog.
Name catalog  
StoreModel Namespace The Model is the root Namespace.
Description description  
Name Name  
StoredProcedure StoredProcedure,Function  
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description description  
Name name  
Postcondition   Not used
Precondition   Not used

Last updated on Tue, 19 Sep 2017 18:35:01

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