277 m2 Slides v1.0 PDF

Module - 2
IBM Cognos Framework Manager:

Relational Metadata Modelling
www.edureka.co/ibm-cognos-bi-training-certification
Course Topics
Module 1
Overview of Data Warehousing and Cognos
BI Architecture
Module 2
IBM Cognos Framework Manager:
Relational Metadata Modelling
Module 3
IBM Cognos Framework Manager: MultiDimensional Metadata Modelling
Module 4
Basic Report Authoring
Module 6
Report Authoring - Multi-Dimensional
Module 7
Other Report Authoring Tools
Module 8
IBM Cognos Cube Designer - Dynamic Cubes
Module 9
IBM Cognos Analyzing and Administering Queries
Module 10
IBM Cognos Administration Overview
Module 5
Advanced Report Authoring
Slide 2
Objectives
At the end of this module, you will learn:
What is Business Requirement?
What is Framework Manager?
Framework Manager workflow processes
Creation of a baseline project
To identify facts and dimensions
To identify key differences amongst type data source, model and stored
procedure query subjects

To identify the effects on generated SQL when modifying query subjects,
SQL settings and relationships
Examining relationships and cardinality
To use calculations to create calculated query items
To use embedded/model filters to reduce the data set
Slide 3
Objectives
At the end of this module, you will be able to:
Merge query subjects to create a view behavior
Create star schema groupings to provide authors with logical groupings of query subjects
Create a consolidated modeling layer for presentation purposes
Identify the conformed dimensions
Use tools to analyze the model
Create and publish a package
Use macros, parameters map and session parameters
Identify reporting traps.
Create aliases to avoid ambiguous joins, multiple paths and other traps.
Describe multi-fact, multi-grain queries & stitch queries.

Use determinants to specify multiple levels of granularity and prevent double-counting
Slide 4
Business Reporting Requirements

Before creating any project, it is essential that we know the requirements of the project report
This helps us to make better decisions regarding:
Data access strategies to be used
Metadata model design and
Report package delivery to IBM Cognos BI
Some of the important factors to be considered for making decisions are:
Reviewing the mock papers
Identifying the data sources from which we can extract the relevant data
To determine whether the data has to be prepared from scratch
How frequently will the reporting take place?
Slide 5
Business Reporting Requirements ( Contd. )

This metadata modeling can be replaced by using the data in the OLAP sources
OLAP facilitates multidimensional analysis of the business data. By using the OLAP sources, you can overcome the
requirement of the metadata modeling in IBM Cognos Framework Manager
The main advantage is that the data is calculated and aggregated in the OLAP database and hence the response time is
decreased
It is always recommended to Extract, Transform and Load (ETL) the data in the warehouse to avoid the processing time
when running the reports
We must also ensure to use features such as filters, sorting, grouping and so on, because the vendor databases are
modeled to have these kind of operations
Special attention to planning is required before we kick start on any project!
Slide 6
IBM Cognos Framework Manager

We use multiple data sources to store information. Lets take a scenario where we have relational DB, multi-dimensional
DB and semi-structured data. All of these data sources are connected to the enterprise data warehouse. You can create
a simplified metadata information that are derived from these sources
These kind of activities are done using the Cognos tool and hence IBM Cognos Framework Manager can be called as a
meta modelling tool

It is a business tool which is used to create simplified business statistics from various data sources
These metadata can be published as packages and can be stored in the relational database to create OLAP style queries
This type of model is known as a Dimensionally Modeled Relational (DMR) model

IBM Cognos 10 Framework Manager manages the semantic layer of a Cognos 10 deployment
The main focus is creating a user-friendly, comprehensive model that provides repeatable and predictable query results.
Slide 7
IBM Cognos Framework Manager ( Contd. )
Slide 8
Slide 9

The user interface includes the following panes:
Project Viewer Pane: It is on the left side of the window and provides easy access to all your project's objects
Project Info Pane: It is the center pane and provides access to the projects objects through various methods. There
are three tabs in this pane (Explorer, Diagram and Dimension Map) which allow you to create, edit, configure, or delete
objects
Properties Pane: It is located in the bottom middle of the window which allows you to configure various properties for
project's objects
Tools Pane: It is located on the right side of the window and provides access to various useful tools. This pane also
provides a search utility and object dependencies utility. Simply drag an object to the top panel, select the object and
view the dependent objects in the bottom panel
Slide 10
Framework Manager Workflow Processes

The workflow process consists of the following phases:
Design and create project
Prepare Metadata
Prepare the Business View
Create and Mange Packages
Set Security
Publish
Manage the Project
Slide 11
Framework Manager Workflow Processes
Slide 12
Create a Baseline Project

Steps to create a baseline project:
Task 1: Create a project
Task 2: Create and organize project
Task 3: Create the data source and check the connection
Task 4: Import metadata
Task 5: Test basic data access
Task 6: Change SQL generation settings and specify the function list
Task 7: Test multiple query subject data access
Slide 13
LAB Create a Baseline Project
Slide 14
Star Schema
You work with several members when creating a report, where each member has certain properties and are identified
by a Member Unique Name (MUN) to describe its position in the dimensional structure
Facts and dimensions play an important role when you create a star schema
The star schema is a design with 2 basic components:
A Table in the center called the fact table and
A Satellite table called the dimension table
The star schema technique contains very few important tables of a report. This increases the query performance rate
Star schema technique focusses on the central fact table and makes an integrity check with the dimensional table
If you have to retrieve data from a specific area, then the query will be executed faster using the star schema design
Slide 15
Identify Facts
Fact Tables are the central table of any star schema design. They have foreign keys to identify the dimensional table
but do not contain any descriptive attributes
Facts in fact table are also called as metrics, measures and key performance indicators.
There are fact tables with just the foreign keys and no facts in them
Example: In an e-commerce website, you may have a fact table which contains product-id key, customer key and a
day key which records the products checked out by a customer and when it was done.
Slide 16
Identify Dimension
Dimensions provide descriptive information
The dimensional values that can be related to various fact tables are called as conformed dimensions. Its
meaning and content does not change when they are being referred by the related fact tables
Slide 17
LAB Facts and Dimensions
Slide 18
Data Source Query Subject

The Query subjects are retrieved from the data source based on the relational metadata using SQL statements
These query subjects refer to data in single data source
A data source query subject is automatically created by Framework Manager for every table and view that you
import into your data model
The main advantage of the data source query subject is that you can directly edit the SQL statements to retrieve
the required data
Slide 19
Model Query Subject

Model Query Subject is used to provide abstract and business-oriented view of the data source
They are generated based on the query items in the other query subjects and dimensions. It also refers to the
query items of a different data model. In short, we can say that model query subjects are created from the
metadata in the model
The main advantage:
Is to reuse the complex SQL statements that exist in the model. You cannot edit the SQL statements but
only re-use them
You can refer the objects of the various data sources in the same query model
Slide 20
Stored Procedure Query Subject

When you import a procedure from the relational data source, a stored procedure query subject is created
Framework Manager supports the user-defined stored procedure
You must run the procedure in the Framework manager to get the result. It returns a single uniform result set
Only the first result set obtained will be supported. To support the different result set, the format of the result
set must match with the metadata in the Framework Manager
Each result set must return same type of results
Slide 21
Relationships and Cardinality

Relationships describe how to create a relational query for multiple objects in the model
Different types of relationships:
one-to-one Here one instance of data in a query subject relates to exactly one instance of another. For
example, each employee has one employee_id
one-to-many or zero-to-many Here one instance of data in a query subject relates to many instances of
another. For example, the manager has many employees working for him
many-to-many Here many instances of data in a query subject relate to many instances of another. For
example, many students have many teachers

Relationships are created between the objects in the model based on the primary and the foreign keys, when
importing data. Now verify the relationship and ensure the cardinality is set correctly
Slide 22

The cardinality of a relationship is the number of rows related for each of the two query subjects that form a relationship.
The rows are related using the foreign and the primary keys of a table
Advantages:
Avoid double-counting fact data
Support loop joins that are common in star schema models
Optimize access to the underlying data source system
Identify query subjects that behave as facts or dimensions
End to end relationship is marked with the minimum and maximum cardinality at the end of the relationship
Slide 23

The various cardinality ratios are:
0..1 (zero or one)
1..1 (exactly one)
0..n (zero or more)
1..n (one or more)
The first part of the notation determines the type of join for the relationship:
an inner join (1) It shows the matching rows from both objects
an outer join (0) It shows all rows from both objects. An outer join can be full, left, or right. Left and right outer joins
take everything from the left or right side of the relationship respectively and only what matches from the other side
Slide 24
LAB Relationships and Cardinality
Slide 25
Use Calculations To Create Calculated Query Items

Using the data from one or more report items, you can perform calculations in your report
You can perform complex calculations in a report if you have special edit access
The syntax of calculation is given in the Expression box of the calculated dialog box
Slide 26
Arithmetic Calculations
Slide 27
Arithmetic Calculations
Slide 28
LAB Perform Calculations
Slide 29
Embedded/Model Filters to Reduce the Data Set

You apply filter when you want to retrieve data based on a specific condition
An embed filter is used when you want to use a filter with only one dimension or query subject
2 types of filters are:
Tabular Filters: 2 types:
Detailed Filters: Filter applied on an individual row
Summary Filters: Filter applied on data after aggregation
Grouped Filters: When filter is applied to a group
Slide 30
LAB Apply Embedded Filters
Slide 31
Merge Query Subjects to Create a View Behavior

Create a Union Query
We use the Union query to combine two or more queries to produce a single result set
The queries which uses different data sources can also be combines using the Union operation
Example: You can combine a query that returns data from a dimensional data source with a query that returns data
from a relational data source
The following points have to be considered for combining / merging the 2 queries:
The two queries must have the same number of data items
The data items must appear in the same order and type
Slide 32
LAB Union of queries
Slide 33
Create a Star Schema Group

Star Schema Grouping is the process of creating quick shortcut groups
to help the user understand which objects belong together
Uses:
Multiple-fact reporting is supported by start schema. Using this the
user can identify the common dimensions in different groups and how
they can cross-function with one another
Easy to manage, maintain and enhance
In star schema, numeric and transactional data is in a central fact table

with related dimension tables attached to the fact table
The objects in the star schema cannot reference or be referred by any
object outside the group
Please note that, star schema grouping is helpful when you are working
on more than one data mart
Slide 34
Create a Star Schema Group

Star Schema based on 1 dimensions
When a fact has relationship with every dimension, you select a single object to be present in the star schema
When this happens, the following points have to be taken care of:
Framework Manager shows a list of objects with which it has relationships so that you can quickly select
the objects that you want in the group
The name of the group is based on the name of the fact table
The new group is created under the same parent as the selected object
Star Schema based on multiple dimensions - If you want to group dimensions that do not already have
relationships defined, you select multiple dimensions in the star schema design. The new group is placed under
the nearest common parent of the dimensions or query subjects.
Slide 35
LAB Create a Star Schema
Slide 36
Consolidated Modeling Layer for Presentation

When the report is error free, the next step in the modeling process is creating a Consolidated View
The consolidated view is divided into two namespaces:
Relational View It generates SQL that is shown in the database. Used for normal reporting
Dimensionally Modeled Relational (DMR) - Used for multi-dimensional analysis. DMR-model is a virtual way of
modeling the data source and does not physically stores data
Slide 37
Consolidated Modeling Layer for Presentation
Slide 38
LAB Consolidated View of Presentation
Slide 39
Tools to analyze the model

Some of the tools that apply business intelligence and analytics to develop the report environment are:
Slide 40
Creating and Publishing a Package

It is important for you to know how the changes made to the model will affect your package and the related
reports before the package is published
For example, adding a new object to the model will not affect any existing report. Changing the name of a
query item in the model or deleting a query item does affect a report
You have to analyze the objects which are directly affected by making any changes to the package
The following types of objects are analyzed:
Query subjects
Hierarchies
Query items
Levels
Measures
Stand-alone filters
Regular dimensions
Stand-alone calculations
Measure dimensions
Slide 41
LAB - Creating and Publishing a Package
Slide 42
Use Macros, Parameters Map & Session Parameters

The data that is being returned by modifying the query subjects and other model parameters can be controlled
dynamically using a combination of session parameters, parameter maps, and macros
A session parameter returns session information at run time
A parameter map is a two-column table which maps a set of keys (source) to a set of substitution values (target)
A macro is a small set of code that you can insert within filters, calculations, properties, and so on, that are to be
evaluated at run time. Macros are enclosed by # (hash) character
Slide 43
LAB Use of Macros, Parameters Map

& Session Parameters
Slide 44
Traps in Data Modeling

Potential reporting errors are known as reporting traps. These errors have to be resolved so that they do not
affect the other reports that are referring to these reports
Types of Traps in Data Modeling are:
Chasm Trap: Many to Many relationships are called Chasm Reports
Fan Trap: When there are multiple one to many relationships from a single table, Fan trap occurs
Connection Traps: An optional path through different entities creates a connection trap
Transitive Relational Traps: If there are more than one path between 2 tables, Transitive Relational Traps
occurs
Slide 45
Shortcuts
A shortcut is a pointer to an object, such as a relationship, a dimension, a query subject, or a folder
We can have multiple references to an object, using shortcuts
Example: Create folders named Orders, Products, and Customers. If you want both Orders and Customers to
contain the same dimension, you must create a shortcut to the dimension and add it to both the folders
IBM Framework Manager supports 2 kinds of shortcuts:
Regular shortcuts - Are simple references to the target object
Alias shortcuts - They behave as a copy of the original object with completely independent behavior. Alias
shortcuts are available only for shared tables and dimensions
Slide 46
LAB Create Shortcut and Alias
Slide 47
Multiple-fact, Multi-grain Queries & Stitch Queries

Multiple-fact, Multi-grain Queries: When a table with dimensional data is joined to multiple fact tables using
different key columns, multiple-fact and multi-grain queries occur
Stitch Queries: A stitch query is generated when a report encounters multiple "fact tables in the model. 2 queries
are generated, one to each fact and it's associated dimensions, and the results are stitched using full outer join
behavior using coalesce functions
Slide 48
LAB Multiple-fact, Multi-grain

Queries & Stitch Queries
Slide 49
Determinants
Determinants are used to provide control over granularity when aggregating
Determinants are required for dimensions that are connected to facts at levels of granularity that have repeating keys
Determinants can define the set of database columns (query items) that uniquely identify a set of data or it can identify
a set of columns that identify a non-unique set within the data
You can also use them to prevent the distinct clause on unique keys
They are used very rarely in the following situations:
Joins at multiple levels of granularity on a single query subject
BLOB data types in the query subject
Slide 50
Questions
Slide 51
Survey
Your feedback is important to us, be it a compliment, a suggestion or a complaint. It helps us to make
the course better!
Please spare few seconds to take the survey after the webinar.
Slide 52
Slide 53

277 m2 Slides v1.0 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

277 m2 Slides v1.0 PDF

Загружено:

Авторское право:

Доступные форматы

Module - 2

IBM Cognos Framework Manager:

procedure query subjects

Describe multi-fact, multi-grain queries & stitch queries.

Business Reporting Requirements

Business Reporting Requirements ( Contd. )

IBM Cognos Framework Manager

meta modelling tool

This type of model is known as a Dimensionally Modeled Relational (DMR) model

IBM Cognos Framework Manager ( Contd. )

IBM Cognos Framework Manager ( Contd. )

IBM Cognos Framework Manager ( Contd. )

Framework Manager Workflow Processes

Framework Manager Workflow Processes

Create a Baseline Project

LAB Create a Baseline Project

LAB Facts and Dimensions

Data Source Query Subject

Model Query Subject

Stored Procedure Query Subject

Relationships and Cardinality

example, many students have many teachers

Relationships and Cardinality

Relationships and Cardinality

LAB Relationships and Cardinality

Use Calculations To Create Calculated Query Items

LAB Perform Calculations

Embedded/Model Filters to Reduce the Data Set

LAB Apply Embedded Filters

Merge Query Subjects to Create a View Behavior

LAB Union of queries

Create a Star Schema Group

In star schema, numeric and transactional data is in a central fact table

Create a Star Schema Group

LAB Create a Star Schema

Consolidated Modeling Layer for Presentation

Consolidated Modeling Layer for Presentation

LAB Consolidated View of Presentation

Tools to analyze the model

Creating and Publishing a Package

LAB - Creating and Publishing a Package

Use Macros, Parameters Map & Session Parameters

LAB Use of Macros, Parameters Map

Traps in Data Modeling

shortcuts are available only for shared tables and dimensions

LAB Create Shortcut and Alias

Multiple-fact, Multi-grain Queries & Stitch Queries

behavior using coalesce functions

LAB Multiple-fact, Multi-grain

BLOB data types in the query subject

Вам также может понравиться