IBM Cognos Framework Manager 10 Fundamentals

Recommended by 0 users

IBM Cognos Framework Manager

  • FM is a windows based metadata modeling tool to build models for designing reports
  • It is used to create projects
  • Use FM to access the metadata from one or more data sources
  • The data source may be homogenous ore heterogeneous
  •  When we are working in FM we work with the projects

Project definition in COGNOS

  • Project includes model, namespace, query subject, query item, folders, shortcuts, parameter map, packages, data source, filters and calculations
  • Project is a store in file system with extension .cpf ( Cognos Project File )
  • A project is a set of files that describes the metadata in one or more models
  • A project also known as presentation layer/metadata layer which is derived from the physical layer database
  • A project created using FM appears as a folder and contains the following set of files

* Project.cpf ( Cognos Project File)

* Model.xml



  • The files in the folder are unique to the project


  • Model is business representation of information from one or more data sources
  • Model is a set of related query subjects and query items defined in a project, required in one or more reporting applications
  • A model is an end user interface which provides an access to data from the database
  • A model provides a gateway between user and database
  • A model is created to fulfill user/report requirements defined in business vocabulary
  • A cognos Architect/Modeler is responsible for creating models by fulfilling business requirements

Report Development:

  • An Application Developer designs reports by fulfilling report requirement specifications using models
  • Carry the following tests to test each report application in a test environment

* Unit testing

*System/Data validation testing

*Performance testing

*User acceptance testing(UAT)

Framework Manager Workflow Diagram:


FM Workflow Process

A windows based tool used to design metadata Models

Datasource——› Import the data to Framework manager—-     FM design and create the project–› Prepare the metadata project(Presentation layer)–› Prepare the project business view–› Create & manage package—› setup security—-› Publish package——

—› Content store(Metadata)—› Reporting interface

Metadata sources – Cognos Application

  • Cognos impromptu
  • Cognos 10.1 model
  • Cognos Architect
  • Decision stream
  • Data Manager
  • IBM Data Source

Third party metadata sources:

  • Informatica
  • BO Designer

Metadata source-Data source-By using this option we can connect to the database by providing database type, server name, user name and password

Cognos can detect relationships based on:

  • Primary & foreign key
  • Matching indexed columns
  • Matching column names

Data source ———–     Import——-    Create the Project

Model/Metadata development:

Project model(Well described metadata in business vocabulary)—-     Publish as package(Well described metadata according to the user needs)—–    Content store Database(Physical layer-Tables)——–     Import the table structure—-   Model(Presentation/logical layer— Views)

A package may contain multiple models

Data Source—› Project—–› Model/s—–› Package

  • Tables in Database are called as Query Subjects in Cognos
  • Columns in Database are called as Query Items in Cognos

Project Def:

A project is a set of files that describes the metadata in one or more models

  • A project contains well organized metadata defined according to the business rules
  • It is a business/logical/metadata/presentation layer 

Model Def:

A model represents business requirements and data source

  • A project can contain one or more models

Query Subject:

  • Maps to the table in the data source
  • A query subject uses an SQL to retrieve the data from data sources

Query Item:

  • Represents column of the database table
  • A query subject contains the query items


  • A namespace is a container which holds query subjects
  • It uniquely identifies query subjects and query items
  • We can import different database into separate namespace to avoid duplicate names
  • Generally project will have 3 layers
  • Database layer
  • Business layer
  • Preparation layer
  • But we will talk about only 2 layers

-DB Layer
-Preparation Layer


Folders are used to organize query subject and other objects based on function or subject

  • In model same objects can not be accepted in different folder


These are logical pointers to an alternate table name

  • These are used to resolve loops
  • Loop occurs when more than one path exists from one table to another table in database

Parameter Map:

  • It is used to substitute runtime objects


  • A join is a relationship that explains how the data of one query subject relates to data of another query subject
  • The relationships can be defined using inner/outer joins


  • A package contains a set of query subjects and other related metadata which is available for publishing to report authors/developers

Preparing Business View:

  • Creating namespace
  • Model based query subjects
  • Filters/calculations as per the business requirements

Create & Manage package:

  • Include
  • Exclude
  • Hide

Setup Security:

  • Package level security
  • Object level security
  • Data level security

Publish Package: It is moving the package to the content store

Content Store:

It is a relational container which is used store package.

  • It holds report specifications, connection information, user account Information

Enroll for Live Instructor Led Online Cognos Training

0 Responses on IBM Cognos Framework Manager 10 Fundamentals"

Leave a Message

Your email address will not be published. Required fields are marked *

Copy Rights Reserved © Mindmajix.com All rights reserved. Disclaimer.
Course Adviser

Fill your details, course adviser will reach you.