IBM Cognos Framework Manager (FM) - Export - 7.3

Bridge Specifications

Vendor	IBM
Tool Name	Cognos Framework Manager
Tool Version	C8 v8.1 to C11
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 Conversion) via XML File

SPECIFICATIONS
Tool: IBM / Cognos Framework Manager version C8 v8.1 to C11 via XML File
See http://www.ibm.com/software/analytics/cognos/
Metadata: [Business Intelligence] BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Conversion)
Component: CognosRnFrameworkManager2 version 11.1.0

OVERVIEW
This bridge converts a metadata model into an IBM Cognos Framework Manager model.
REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a trouble shooting 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	The bridge uses the native XML file from IBM Cognos Framework Manager: 1. Create a new project in IBM Cognos Framework Manager. 2. Navigate to the project's directory and export in the 'model.xml' file.	FILE	*.xml		Mandatory
IBM Cognos FM Version	The version of IBM Cognos Framework Manager.	ENUMERATED	IBM Cognos 10.2 - XML v60.3 IBM Cognos 10.1 - XML v60.2 IBM Cognos 8.5 - XML v60.2 IBM Cognos 8.4 - XML v60.1 IBM Cognos 8.3 - XML v60.0 IBM Cognos 8.3 - XML v59.0 IBM Cognos 8.2 RTM FM GUI v8.2.2044.0 - XML v58.2 IBM Cognos 8.1 MR2 FM GUI v2.0.1884.0 - XML v58.1 IBM Cognos 8.1 MR1 FM GUI v2.0.1440.0 - XML v58.0 IBM Cognos 8.1 RTM FM GUI v2.0.1124.0 - XML v57.0	Cognos 10.2 - XML v60.3
Logical/Physical representation	The chosen representation of logical and physical information in IBM Cognos Framework Manager. 'Integrated' Logical and physical objects are represented as one object in IBM Cognos Framework Manager. 'Separated' Logical and physical objects are represented as two related objects in IBM Cognos Framework Manager. 'Separated (verbose)' Logical and physical objects are represented as two distinct objects in IBM Cognos Framework Manager.	ENUMERATED	Integrated Separated Separated (verbose)	Separated
Dimensional/Logical representation	The chosen representation of dimensional information in IBM Cognos Framework Manager. 'Integrated' Dimensional objects are represented as one dimensional object in IBM Cognos Framework Manager. 'Separated' Dimensional objects are represented as one dimensional and one logical object in IBM Cognos Framework Manager.	ENUMERATED	Integrated Separated	Integrated
Diagram representation	The chosen representation of Diagrams in IBM Cognos Framework Manager. 'None' Diagrams are ignored. 'As Namespaces' Diagrams are represented as Namespaces only to IBM Cognos Framework Manager. 'As Packages' Diagrams are represented as Packages only to IBM Cognos Framework Manager. 'Both' Diagrams are represented both as Namespaces and as Packages to IBM Cognos Framework Manager. The default is to represent Diagrams as both Namespaces and Packages. The recommended values are: 'As Packages' When migrating metadata from a business intelligence design tool 'Both' When migrating metadata from a data modeling tool	ENUMERATED	None As Namespaces As Packages Both	Both
Namespace hierarchy	Specify how Packages are represented in IBM Cognos Framework Manager. The CWM/UML (Common Warehouse Metadata/ Unified Modeling Language) notion of package is represented as namespace in IBM Cognos Framework Manager. 'None' The hierarchy of Packages is lost. 'Dimensional level only' The hierarchy of Packages is kept in the dimensional Namespace only. 'Logical level only' The hierarchy of Packages is kept in the logical Namespace only. 'Physical level only' The hierarchy of Packages is kept in the physical Namespace only. 'All' The hierarchy of Packages is kept in all the Namespaces.	ENUMERATED	None Dimensional level only Logical level only Physical level only All	All
Logical only classes	Specify whether the logical only Classes should be represented in IBM Cognos Framework Manager. 'Ignore' Logical only Classes are ignored. 'Show' Logical only Classes are shown along with all their Attributes.	ENUMERATED	Ignore Show	Show
Logical only attributes	Specify whether the logical only Attributes should be represented in IBM Cognos Framework Manager. Note that this option does not affect logical only Attributes in a logical only Class (see option 'Logical only classes'). 'Drop' Logical information of a Class is not shown if it contains a logical only Attribute. 'Ignore' Logical only Attributes are ignored. 'Show' Logical only Attributes are shown.	ENUMERATED	Drop Ignore Show	Show
Unreferenced dimension attributes	Specify how to represent unreferenced dimension attributes (i.e. the ones that do not participate in a level and are not referenced by any other dimension attribute). The option allows to discriminate against the unreferenced dimension attributes that participate in a join as the joins are all represented in the physical layer and not in the dimensional layer. 'Show all' All unreferenced dimension attributes are shown. 'Show join' Only unreferenced dimension attributes partitipating in a join are shown. 'Ignore join' Only unreferenced dimension attributes partitipating in a join are ignored. 'Ignore all' All unreferenced dimension attributes are ignored.	ENUMERATED	Show all Show join Ignore join Ignore all	Show all
Dimensions without dimensional information representation	Specify how to represent dimensions that do not contain any dimensional information (hierarchy or level) in IBM Cognos Framework Manager. 'Dimension' Create a dimension and a default hierarchy and level. 'ModelQuery' Create a modelQuery.	ENUMERATED	Dimension ModelQuery	Dimension
Create cubes	Specify whether the bridge should create cubes in IBM Cognos Framework Manager. The cubes will be represented as a namespace containing all the necessary information from the fact dimension, the dimensions and the joins necessary to build it.	BOOLEAN		True
Populate screentip	Specify whether the bridge should duplicate the description field into the screenTip field. This option allows to see the description field as a screentip in IBM Cognos Query Studio or IBM Cognos Report Studio.	BOOLEAN		False
DataSource name	The name of the dataSource in Content Manager.	STRING
DataSource default catalog name	The name of the default catalog for the specified dataSource in Content Manager.	STRING
DataSource default schema name	The name of the default schema for the specified dataSource in Content Manager.	STRING
Target DataBase	Specify the target database type. 'Auto Detect' means that the bridge will try to auto-detect the target database from the source model.	ENUMERATED	Auto Detect CT D2 DB IB IF IG MS OL O6 OD OR RB SB S4 SD SS ST SY TD DMS	Auto Detect
Model locale	The locale that should be used to generate the model.	ENUMERATED	cs cs-cz da da-dk de de-at de-ch de-de de-lu el el-gr en en-au en-be en-bw en-ca en-gb en-hk en-ie en-in en-nz en-ph en-sg en-us en-za en-zw es es-ar es-bo es-cl es-co es-cr es-do es-ec es-es es-gt es-hn es-mx es-ni es-pa es-pe es-pr es-py es-sv es-us es-uy es-ve fi fi-fi fr fr-be fr-ca fr-ch fr-fr fr-lu hi hi-in hu hu-hu it it-ch it-it ja ja-jp ko ko-kr nl nl-be nl-nl no no-no pl pl-pl pt pt-br pt-pt ro ro-ro ru ru-ru ru-ua sk sk-sk sv sv-fi sv-se tr tr-tr zh zh-cn zh-hk zh-mo zh-sg zh-tw	en-us
Name of the namespace containing the dimensional information	Type in the desired name for the namespace that will contain the dimensional information.	STRING		Dimensional Model
Name of the namespace containing the logical information	Type in the desired name for the namespace that will contain the logical information.	STRING		Logical Model
Name of the namespace containing the physical information	Type in the desired name for the namespace that will contain the physical information.	STRING		Physical Model
Name of the namespace containing the subject areas	Type in the desired name for the namespace that will contain the subject areas.	STRING		Subject Area
Logical Attribute Order	Determines the order of the logical attributes: 'Logical Attribute Order' Matching the entity's attribute order of the source logical data model if available. 'Physical Column Order' Matching the table's column order of the created DB query items	ENUMERATED	Logical Attribute Order Physical Column Order	logical attribute order

 

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		Order in the xml file
Association	Relationship
Name	name
AssociationRole	Relationship
Multiplicity	cardinality
Attribute	QueryItem
Description	description
Name	name
Optional	nullable
PhysicalName	columnName
Position		Position of the QueryItem in the xml file
DataType	datatype
Length	precision,size	Use Precision if it is not null, use Size otherwise
Name	datatype
Scale	scale
CandidateKey	Key
Name	name
Class	dbQuery
Description	description
Name	name
PhysicalName	name	Depending on the value of the option "Logical/Physical representation" the physical name might be used as the name of the dbQuery
ClassDiagram	Namespace,Package	Depending on the value of the option "Diagram representation", a Class Diagram will be mapped to a namespace, a package, both or none.
Description	description
Name	name
ClassifierMap	modelQuery	Used to build the sql statement of a modelQuery
Condition	Filter.Relationship	A condition is used to build the expression of a filter/relationship
DatabaseSchema	Data Source	A Schema will be created for each Datasource with a non empty schema
Name	schema
DerivedType	QueryItem
DataType	datatype	See datatype conversion array
Length	precision
Name	datatype
Scale	scale
DesignPackage	Namespace
Description	description
Name	name
UserDefined		Set to false only for the packages created to keep the folder hierarchy.
Dimension	modelQuery
Description	description
Hide		If set to "true", the modelQuery will be hidden in all the packages in belongs to
Name	name
DimensionAttribute	QueryItem
Description	description
Hide		If set to "true", the QueryItem will be hidden in all the packages in belongs to
Name	name
Sort	unsortable
Name	name
Name	name
FeatureMap	QueryItem	Used to build the expression of a QueryItem
Description	patterMapping	Mapped to the custom property "patternMapping"
Operation	expression
Filter	Filter
Description	description
Name	name
Generalization	Relationship	A relationship will be created between each supertype and each subtype of the generalization
Name		The name will be computed from the name of the generalization, of the supertype and of the subtype involved.
GeneralizationRole	Relationship
Hierarchy	Hierarchy
Name	name
HierarchyLevelAssociation	Hierarchy
Position		Order in the xml file
Index	Index
Generate		Always set to true
Name		A name will be computed
IndexMember	Index
Description		Order in the xml file
Name		The name will be computed from the name of the QueryItem
Join	Relationship
JoinRole	Relationship
Multiplicity	cardinality
Level	Level
Name	name
LevelAttribute	Level
Name	name
LevelKey	Level
Name	name
Measure	QueryItem
DefaultAggregation	regularAggregate
Description	description
Hide		If set to "true", the QueryItem will be hidden in all the packages in belongs to
Name	name
Sort	unsortable
Projection	Graphical information of Classes
RelationshipProjection	Graphical information of Associations
SQLViewAttribute	QueryItem
Description	description
Expression	sql
Name	name
PhysicalName	columnName
Position		Order in the xml file
SQLViewEntity	dbQuery
Description	description
Name	name
PhysicalName	name	Depending on the value of the option "Logical/Physical representation" the physical name might be used as the name of the dbQuery
WhereClause	sql
StoreConnection	Data Source	A datasource will be created for each catalog
Name	catalog
StoreModel	Namespace	The Model is the root Namespace.
Description	description
Name	Name
StoredProcedure	StoredProcedure,Function	A stored procedure is mapped to a function if it has a return parameter
Description	description
Name	name