29 October 2015 TCS Confidential Overview of Cognos 8 BI Features Open data access Integrated...

April 20, 2023TCS Confidential

Overview of Cognos 8 BI Features• Open data access

• Integrated Enterprise planning and Consolidation

• Dimensional Reporting and Dashboarding

• Deep, large data comparative analysis

• Extended Self-service reporting

• Process Integration and Event Life Cycle

• Actionable Scorecards in Metric Studio

• Extended data transformation services in Data Manager

• Integrated Portal


Cognos 8 Workflow


Open Data Access Capability


Examine the Various Studio in Cognos 8 BI• Metric Studio helps you manage the performance of your organization by monitoring

and analyzing metrics at all Levels.

• Query Studio helps you quickly answer a focused Question.

• Analysis Studio performs simple to complex analyses and comparisons of data to discover trends , risks and opportunities

• Report Studio builds sophisticated reports , Including multi-page, Multi-Query reports against multiple data sources.

• Event Studio notifies users of key operational or performance-related events that any affect their business.


Examine the Role of Framework Manager• Cognos 8 Metadata Model is a business presentation of information from one or more

data sources.

• BI User use the model to analyze and report on their data sources


Framework Manager Workflow

Design/Create

Project

Prepare Metadata

Prepare the Business View

Manage

Project

Import

Create and Manage

Packages

Set

SecurityPublish

Content Store

DataSources

Report Studio

Query Studio

Analysis studio

.


What is Framework Manager?

Framework Manager provides the metadata model development environment for Cognos ReportNet.

Use Framework Manager to model the business presentation of data derived from one or more data sources.

In Framework Manager, you work in a project, which contains:

a model

namespaces

data sources

parameter maps

packages


Examine the Framework Manager UI

Project Info

Object Explorer

Object Diagram


Describe the Framework Manager Environment

• In a Framework Manager project, you will interact with the following objects:

– Model: the set of metadata objects organized fro report authors according to the business model and rules. Which will be availble for publishing to c8 server.

– Namespace:

– folder

– query subject

– query item

– relationship

– parameter map

– package


Project Objects….• Model: the set of metadata objects organized fro report authors according to the

business model and rules. Which will be availble for publishing to c8 server.

• Namespace: a qualifying container for objects that provides unique name to prevent naming conflicts.

• Datasource: a relations database ,dimensional cube, file ,or any physical data store that can be accessed through Cognos 8.

• Parameter map- a list of parameters used to create conditional QS that allow for substitutions at run time.

• Package: a subset of the query subjects and other objects defined in the project ,published for use as a model by report authors.


Examine the Project• A project appears in a file system as a folder that contains a project file (.cpf) and XML

files.

• X.cpf: Project file references files used to define the model.

• Model.xml: Actual model data created by FM developer

• Preferences.xml: preferences for FM Projects.

• Customdata.xml: stored diagram information, layout, fonts ,colors.

• Repository.xml: Logged version of the History for each project or segment that added to rep.

• When u publish the package the server compiles the XML specification into binary runtime information .


Examine the Model

• Examine the model from the perspective of the report or ad hoc query author.


Examine Query Subject Types

• Data source query subject• SQL query that acts as a view into the underlying query data source

• default data source query subjects are created based on imported objects

• Model query subject• contains query items based on other existing objects in the model

• Allows simplification of the model for the business views.

• Provide a way to control of Query Generation.

• Allows Users to override the settings specified for the data sources query subjects to meet reporting requirements.

• Stored procedure query subject• contains query items based on the return list of a stored procedure


Design and Create a Project

• Analyze & Design:

– Know your data and the structure of your data sources.

– Work with report authors to understand business reporting requirements.

– Identify project structure.

• Create

– Create a project.

– Import the required metadata.

• Organize

– Organize objects to create a physical view of the metadata.

Design/Create

Project


Prepare Metadata

• Administer

– Specify query processing type.

– Define function sets.

• Clean Up

– Examine and modify object properties.

– Examine, modify, and create relationships.

– Edit SQL.

– Add Multilingual support.

Prepare Metadata


Identify the Cardinality• 0..1 : Zero occurrences to one occurrences

• 1..n: One occurrence to Multi occurrences

• 0…1: Zero occurrence to one occurrence

• 1…1:Must have one occurrence.

• (0/1): Optional or Mandatory.

• (1/n): Minimum or Maximum.


Usage Property:

• Identifier:Column that is used to group or summarize the data in the fact with which it has relationship. Index columns, Date, time columns. Product Number, Date of Joining.

• Fact: Column contains numeric data and can be group or summarize, such as Product cost, Date ranges.

• Attribute: A column which is neither fact or Identifier, such as description. Like Product name.

• Unknown: If not defined the usage property.


Examine the Data Traps• Chasm Trap:

• Transitive relationship Trap:

• Connection Trap:

• Fan Trap:

– A Data Trap doesn’t necessarily indicate a problem, only an area is worth inspection and possible treatment.

– A data modeler must carefully examine any area that does not appear to present the data completely.

– The modeler must examine which relationship is missing with traps.


Chasm Traps..• Many to Many relationships are called Chasm Traps.

• This structure cannot record and amaintain data. It lets the information fall into a Chasm

• A chasm trap is not wrong when designing at high level. It just does not show all the necessary details


Examine Transitive Relationships..• A transitive relationship exists, if there is more than one path between two tables.


Examine Fan Trap..• A fan trap is identified by a multiple one-to-Many relationship fan out from a single

table.


Examine Connection Trap..• A Connectino trap is an optional path through different entities .

• There must be a reliable path through all truly related entities.


Examine Naming Conventions

Objects in Framework Manager:

have an identifier

can have the same name but must be uniquely identified using a namespace

The identifier can consist of one, two, or three parts. For example:

query items have a three-part identifier

e.g., [GoSales].[Product].[ProductCode]

namespaces, functions, shortcuts to namespaces, and shortcuts to folders have a one-part identifier

e.g., [GoSales]

all other objects have a two-part identifier

e.g., query subjects:[GoSales].[Product]


Model metadata and prepare Business View

• To enhance the business view of the model, you can:

– create one or more presentation views

– add calculations

– create and apply filters

– add prompts

– create dynamic queries

– use star schema groupings

– specify Determinants

– Model dimensionally of OLAP style queries.

Prepare the Business View


Types of Calculations:

• Adding new columns which is not available in Data source.

• There are Two types:

• Embedded

• Stand-alone

• To add the calculated columns , the Calculations can use:

• Query items

• Parameters

• Functions


Types of filters…• Filers are used to restrict the data retrieved by Query subject

• There are two types of UI filters available in Framework manager.

– Stand-alone: Reusable in multiple Query Subjects

– Embebbed: For a Single Query Subject


More on filters…• Filter have a Usage Setting with the following Options.

• Always: The filter will be applied in all instances regardless of whether the filtered query item is in the query or not.

• Optional- the filter is not mandatory and user may choose to enter a filter value or leave it blank.

• Design Mode Only- Limits the amount of data that is retrieved when testing in framework manager or at report design time .(authoring reports in Query studio or report studio, You can use the limited data feature to apply the filter and return results quickly.


Create a Stored Procedure Query Subject• Stored Procedures are of two types.

• Data Query :

– Return result sets based on simple to complex queries

– Must return a single uniform result set.

• Data Modification:

– Stored procedures which modify the databases such as adding , updating , or deleting records.

– Used in Event Studio only in conjunction with a Database Update task.


Use of Parameters• Parameter maps are similar to Look-up tables.

• They substitute a passed parameter with a value understood by you application.

• Each parameter consists of two columns.

• Key(Must be unique)

• Value(used for Substitution)


Set Security

• Cognos 8 security is implemented through user authentication and authorized access to content.

• To set security in Framework Manager, you can:

– define access to packages

– create security filters

– define access to objects

– define package administration access

Set

Security


Create and Manage Packages

• To create and manage packages, you can:

– define the package contents

– modify a package

– specify languages

– set governors

– view package inclusion

– enable versioning

Create and Manage

Packages


Edit Governors…


Types of SQL:• Cognos SQL:

• Generic representation of a Query.• More verbose than native sql• Formatted for readability and comprehension and generated by CQE

• Native SQL:• Designed to use the database optimizers.• Leverages features of databases wherever possible.• We cant use Native SQL in a Query subject that references more than one

data source query subjects• Pass-through SQL:

• Use When a database vendor does not extend support for a particular construct in a sub-query.

• Cognos 8 will pass anything you type directly to the database.• With Pass-through SQL what ever you type is passed to the Data base

processing with out the intervention of the Cognos 8 Query Engine


Cognos 8 Query Generation Architecture• The Cognos 8 User Interfaces are used to submit the SQL.

• The SQL option you have chosen will determine how Cognos 8 will generate the SQL.


Analyzing the Impact of Publishing of Package• View affected reports

• View the change items

• View changes made.

Verify the Project:

– Invalid references

– Invalid association containership

– Schema validation errors.


Manage the Project

• Perform project management activities such as:

– implementing multiuser modeling

• repository control– sharing and reusing information

• segmenting and linking– action logging and synchronizing

– checking a project

Manage

Project


Use Reporsitory Control• Use Repository control to implement multi-user modeling and help manage your

projects.

• Use Frame work manager to:

– Connect to and add projects to the repository

– Check In and Check Out a Project.

– Get the latest version of the a Project

– View the Project History.


Create a Segment• A segment is a new project complete with its own associated project files.

• You can create segments to :

– Organize a project according to business rules and organizational requirements.

– Share and re-use project Information.


Create a Link• Create Links so that you can:

– Organize work across large projects

– Maintain consistency

– Re-use Information.

• You can use Only create Links to:

– Folders

– Namespaces

– Projects or Segments


Consolidate Segments and Links

• You can consolidate the linked and segmented metadata in a model by publishing the package to the Network location.

• The Package should include the complete set of metadata.

• Publishing to network location creates a new set of project files without Segments or Links.


Examine Action Logging• Capture ,view, and play back actions performed on the Project.


Synchronizing the Projects.• Use log files to synchronize a project with

changes in the metadata source.

• All Actions performed in the model are replayed. The results is…

– A new project is created.

– Metadata is re-imported to capture any changes.

– The entire modeling process is repeated using updated metadata.


Modeling Recommendation

– Define reporting requirements and data access strategies

– Import only required objects and alter as little as possbile.

– Verify relationships and Query item properties.

– Customize metadata for runtime

– Model in freehand to identify query usage

– Use Model query subjects to control the query generation and usage.

– Specify the determinants

– Resolve ambiguous relationships.

– Populate the Business view using Star Schema groupings.

– Model dimensionally if OLAP style querying is required.


Optimizing and Tune FM Models.• Identify the advantage of materialization of the tables at the DB.• Examine how to achieve the minimized sql.• Set to governors to control the query execution.• Examine report and metadata caching.• Specify the query processing and aggregate computation occurs.• Place filters on the query subjects to reduce rows.• Set the query item properties appropriately.• Limit the number of database connections.• Use the Quality of Service indicator to provide the information about the performance

impart of the functions.• Examine the PC optimize utility for Power cubes.


Limit the Number of Database Connection• Use the same content Manager connection name for all data source connections to the

same database server instance.

• At runtime, this avoids making multiple connections to the database server instance


Apply Design Mode Filter on Query Subjects

• Apply design mode filters to limit the amount of data that report authors and modelers retrieve when testing and designing


Use Cached Metadata for Reports• Reports require metadata and descriptions of that metadata in order to fulfill queries

• If any metadata is not cached in the RTM file, this results an additional calls to the Database.


When the Metadata not Cached?• Metadata is not cached when you:

– Enable the Model portability governor

– Modify a data source query subject by:

• Editing the SQL Statement

• Adding embedded filters or Calculation Objects


Indicate the Performance Impact of Functions• You can Provide the report authors with a visual clue about the performance of

individual functions by setting the Quality of Service Indicator.

• The Quality of Service indicator can be set for functions in a project or at package level.

• The following Indicators are available


Examine the PC optimize utility for Power cubes.

• PC Optimizer:

– Is a Utility that accelerates the time required to open the cognos power cubes in report studio and Analysis Studio.

– Creates a form or Table of Contents.

• You need to run the following cubes through the optimizer utility:

– Cubes built prior to the Transformer S7 Version 3Mr2

– Cubes built with transformer S7 version 3 MR2 without the Optimization enabled.


Trouble Shooting the Unexpected Results….• When the results are unexpected, check the SQL.

– What kind of Joins you see.

– Do they correspond with the relationships you have in framework manager?

– Do you see a stitch query that you don’t expect?

– Do you see a Stitch query without all required conformed dimension?

– Do you see a stitch query with no conformed dimension?

• Do you have determinants specified for Multiple Levels of granularity in single query subjects.

• Are you using the correct SQL Options?

• Check the native SQL to see if it is what you expected.

29 October 2015 TCS Confidential Overview of Cognos 8 BI Features Open data access Integrated...

Documents

Transcript of 29 October 2015 TCS Confidential Overview of Cognos 8 BI Features Open data access Integrated...