Cognos Framework Manager
•
6 likes•7,550 views
The document discusses data modeling concepts in IBM Cognos Framework Manager including: 1) It introduces Framework Manager and discusses its benefits like creating a star schema for optimizing queries. 2) It outlines common traps to avoid in data modeling like chasm, fan, connection and transitive relationship traps. 3) It describes the Framework Manager workflow of creating a project, preparing metadata from data sources, modeling the business view, publishing packages and setting security controls.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (12)
Similar to Cognos Framework Manager
Similar to Cognos Framework Manager (14)
Cognos Framework Manager
- 1. Data Modeling IBM COGNOS Framework Manager
- 2. COGNOS 8 BI Overview COGNOS 8 Workflow Introduction to Framework Manager Benefits of a Star Schema Traps of Data Modeling Framework Manager Workflow
- 3. COGNOS 8 BI Overview Report Cognos Analysis Query Studio Event Studio Metric Studio Studio Viewer Studio Data Access Composite Metric Relational Cube Files Database More
- 4. COGNOS 8 Workflow PLAN MANAGE MODEL AUTHOR CONSUME Plan for Framework Author Run, View, Print Install Implementation Manager Projects Reports/Analyses Reports/Analyses Configure Publish Package Setup & Maintain Security Administrater Servers & Reports
- 5. Introduction to Framework Manager Basic Concepts Project Namespace Metadata Query Subject Query Item Shortcut Relationship Cardinality Data Source Package
- 6. Relationships Types of Relationships 1. One to One 2. One to Many 3. Many to Many 6
- 7. Cardinality Types of Cardinality 1. 1..1 2. 0..1 3. 1..n 4. 0..n 7
- 8. Benefits of a Star Schema Select o.amt, c.name, c.type, p.name, Select o.amt, c.name, ct.type, p.name, p.line pl.line From Order o, From Order o, Customer c, Customer_Infor ci, Product p Customer_Type ct, Where o.cust_id=c.id Product p, Product_Line pl And o.p_id=p.id Where o.cust_id=c.id and c.ct_id=ct.id and o.p_id=p.id and p.pl_id=pl.id Custom Product er Type Line Custom Product er Order Fact Custom Product er Info. Order
- 9. Traps of Data Modeling Types of traps 1. Chasm Traps 2. Fan Traps 3. Connection Traps 4. Transitive Relationships Traps 9
- 10. Chasm Traps Many-to-Many relationship are called chasm traps 1..n Supplier 1..n Part Supplier Part ID Part ID Name ID Supp ID Amount 1 1 John 1 1 100 1 2 John 1 2 200 2 1 Smith 2 1 300 2 2 Smith 2 2 400 Supp ID Part ID Name Amount 1 1 John 100 1 2 John 200 Name Total Amount 1 1 John 300 John 1000 1 2 John 400 Smith 1000 2 1 Smith 100 2 2 Smith 200 2 1 Smith 300 2 2 Smith 400
- 11. Fans Traps A fan trap is identified by mutiple one-to-many relationships that fan out from a single table 1..1 1..1 Division 1..n 1..n Branch Employee
- 12. Connection Traps A connection trap is an optional path through different entities There must be reliable path through all truly related entities 1..n 1..n Division Branch 1..1 Employee 1..1
- 13. Transitive Relationships Traps A transitive relationship exists if there is more than one path between two tables Custom 0..n Custom er Type 1..n er Info. 1..1 1..1 1..n 0..n Custom er Info.
- 14. Framework Manager Workflow Data Source Model Metadata Create and Create Prepare & Prepare the Manage Project Metadata Business View Packages Publish Set Security Report Studio Query Studio Content Analysis Studio Store …….
- 15. Q&A 15
Editor's Notes
- Project – FM creates a project file with XML format that maintain whole data model information.Namespace – is a customized scope that contains different objects of FM, such as Sub-Namespace, Query Subjects, Query Items. Filter etc.Metadata – the foundation of data model, we can consider as the database objects, such as table, view, store procedure etc.QuerySubject – the abstracted object which build on metadata. You can consider a database viewQuery Item – the attributes of query subject. Something like column of database view.Relationship – the relative between query subjects. Cardinality – consider as a factor that tell Cognos server to use which type of table join (inner, outer, full outer) should be used while generating the SQL query that retrieve the real data from data warehouse.Package – A based unit that Cognos publishes to users for generating the reports with report tools.
- We recommend to utility the star schema in order that we can retrieve the data from different tables more effieciently.
- Actually, all the traps will occur the incorrect aggregations when Cognos build the query to retrieve data from DW.
- When we bring a attribute from Branch and Employee, the relationship of them is equal to many to many
- To Employee table, more than one Division has one employee.
- Cognos doesn’t know which path can build the relationship between tables.