Professional Documents
Culture Documents
Query users use the package in Query Studio to create adhoc queries.
Critical for business success because data accuracy depends on the design
Continued
After define a Framework Manager Project and namespace, one can publish one
or more packages containing metadata information to the Cognos Connection.
BI users use the model to analyze and report on their data sources.
Reporting Layer
Cognos 10 Metadata Model
Relational
Files
Cubes
Other
Enroll Now : https://goo.gl/KC31Ea
Data Sources:
A project can contain data from one or more data sources
Namespaces:
A namespace uniquely identifies query items, query subjects and
other objects. Import different databases into separate namespaces to
avoid duplicate names.
Parameter map
Parameter Maps are substitution tables that are populated when the
package is published
Continued
Query Subjects:
query subjects refers tables in database. A project is built upon query subjects.
There are 3 types of query subjects:
- Data source:
A data source query subject directly references data in data source . A single Framework
Manager project can contain data source query subjects from one or more data sources
from one or more vendors. This provides heterogeneous database access. Data source
query subject can be enhanced by adding filters or calculations to create additional query
items
- Model:
Model query subjects can contain query items from an arbitrary set of data source query
subjects. Model query subjects can be enhanced by adding filters or calculations to create
additional query items.
- Stored procedure:
The stored procedure query subject operates much like a data source query subject in that
it defines a set of query items that are available to the model from the underlying data
source. Stored procedure query subjects cannot be enhanced by filters or
calculations.
Continued
Query Items:
Query items are contained in query subjects. For example, a query subject that
references an entire table contains query items that represent each column in the table.
Note Calculated query items can have a dramatic impact on the performance of your SQL queries. It is
strongly recommended that calculated query items use database-only functions or are incorporated
directly into the database when possible.
Usage property
When a business user interacts with a model, the behavior of the data will be determined by how the
properties of the query item are set. For example, when the business user adds a query item that
references a numeric value to a report, will the value be totaled or will it be averaged? Maybe nothing
will happen. Cognos Studios determine the proper behavior for the data referenced by a query item by
looking at the usage of the query item being referenced
Continued
Identifiers If the source column is a database key or date/datetime, the query item usage
will be set to
an Identifier.
Facts If the source column is a numeric value or a time interval, the query item usage will be set to
Measure.
Attributes If the query item is not an Identifier or a Measure, the query item usage will be set to
Attribute.
Regular Aggregate
The Usage property is important because of the impact that the property has on the aggregation setting
of a query item. The Regular Aggregate property, as with all the other properties, is set during the initial
metadata load. This property determines how the values of a query item will be calculated when a
summarization is applied to those values.
When a query item is determined to be an Identifier or an Attribute, the Regular Aggregate property will
be set to Count. This means that if a business user applies a summary to a column of Identifiers or
Attributes, the value displayed in the summary cell will be a count of the rows returned by the report or
query. If the query item is an Attribute or an Identifier, and the data type is a Date, the Regular Aggregate
defaults to Unsupported. Applying a summarization to a query item with an Unsupported Regular
Aggregate property will have no effect on the data.
When a query item is determined to be a Fact, the Regular Aggregate property will be set to Sum. In this
case, applying a summarization to a column of Facts, the value displayed in the summary cell will be the
total of all the values added together.
Continued
Physical View
The first view in our model is the Physical View. This view is used to hold the query subjects and relationships
used to build the model. The query subjects in this view should be unmodified views of the source tables. This
ensures that simple select statements are sent to the database, which prevents additional metadata calls at
runtime.
Business View
The second view is the Business View. This view contains query subjects that have been optimized for use by
the business user. This is where items are renamed, folders are created for organizational purposes, query subjects
are consolidated, and, when necessary, query subjects are merged.
Presentation View
The final view is the Presentation View. As the name implies, this is the view of the model that will be
presented to the business user. The query subjects in this view are organized to make sense for the business user.
Usually Business View query subject short cuts
Continued
Star Schema and Snowflake
A star schema is a database design optimized for reporting. The design is based on a central fact table
that is surrounded by dimension tables
Snowflake-- it contains a dimensional query subject that is not directly joined to the central fact table
Fact Table
In its simplest terms, a fact table contains measures that will be aggregated in a report or some
other tool. A fact table is used to hold transactional data and the keys to the attributes that describe those
transactions
Dimension Table
A dimension table, again in simplest terms, is a table that does not contain any measures. In a
database, a dimension table hods attributes, or descriptive values, that can be applied to one or more fact
tables. nonconformed, conformed, and role-playing. When a dimension can be used by more than one fact
table with consistent and give correct results, it is known as a conformed dimension.
When a single table is used to provide different dimensional information based on a join or filter, that
table is said be a role playing or alias table. A common example of this is an employee dimension.
Project File
A Framework Manager project appears as a folder that contains a project file (.cpf) and
the specific .xml files that define the project. The files in a project folder are unique to
each project
The contents of a project folder are..
<project name>.cpf :
The Framework Manager project file, which references the .xsd and
used to define a project
.xml files
model.xml:
The actual model data created by Framework Manager users
Preferences.xml:
The preferences for Framework Manager projects
customdata.xml:
This file contains the layout information for the diagram. If this file is deleted, layout
information is lost. An automatic layout will be applied.
repository.xml:
The logged version history for each project or segment that was added to a
repository. This file exists only if you have added projects to a repository
After create or open a project, the project page appears. This page
contains several panes and views that one can use to view and modify
the objects in a project
Project Viewer:
The Project Viewer shows the objects in a project in a hierarchical view.
You can use the Project Viewer to view, modify, and create these objects:
Query subjects
Data sources
Namespaces
Parameter maps
Folders
Links
Calculations
Filters
Packages
Object Viewer:
The Object Diagram View shows the relationships between objects in a
project in a diagram. Relationships between query subjects are shown as
lines with cardinality notation.
The Object Explorer Views shows Query Subjects and relationships between
Query objects in the form of Icons
Dimension map is used to create Regular dimension.
Planning
PLAN
Plan for
Implementation
MANAGE
MODEL
AUTHOR
CONSUME
Install
Framework
Manager
Projects
Author
Reports/Analyses
Run, View,
Print
Reports/Analyses
Configure
Setup &
Maintain
Security
Administer
Servers
& Reports
Publish
Package
Prepare
Prepare
Metadata
Metadata
Model Metadata
Metadata &&
Model
Prepare
the
Prepare the
Business View
View
Business
Publish
Publish
Report Studio
Query Studio
Analysis Studio
Content
Store
Createand
and
Create
Manage
Manage
Packages
Packages
Manage
Manage
Project
Project
Set
Set
Security
Security
Create
Project
Prepare
Metadata
Prepare
Analyze:
work with report authors to understand business reporting requirements
know your data and the structure of your data sources
Create:
create a project
identify the project structure
import the required metadata
Metadata
Prepare:
examine, modify, and create relationships
add multilingual support
examine and modify object properties
USA : +1 940 440 8084, IND : +91 953 383 7156
Email Id : info@maxonlinetraining.com
Create and
Manage
Packages
Set
Security
Email Id : info@maxonlinetraining.com