Home >Documents >Cognos Features

Cognos Features

Date post:26-Jan-2016
View:220 times
Download:3 times
Share this document with a friend
Cognos Features
Oracle Financial AnalyzerCognos Impromptu, for enterprise query and reporting.
Cognos Impromptu Web Reports, for easy distribution and navigation of standard reports via the Web.
Cognos PowerPlay, for powerful OLAP reporting and analysis across the enterprise in a centrally managed, single-application-server environment.
Cognos PowerPlay Web, for instant deployment of multidimensional analysis capabilities via the Web.
Cognos 4Thought, for the power of predictive modelling to business planners.
Cognos Scenario, for uncovering hidden patterns and relationships in corporate data.
Cognos DecisionStream, for building and deploying enterprise BI-ready data marts.
Cognos Accelerator, for unleashing the Business Intelligence stored in SAP applications.
Cognos HeadStart Solutions, for predefined analysis and reporting modules for delivering immediate value from corporate data stores.
Cognos NovaView, for Microsoft SQL Server 7.0 OLAP Services
Cognos Axiant 4GL for graphical client/server application development environment.
PowerHouse Web for building and deploying Web-based applications in conjunction with PowerHouse 4GL.
APL 2000 for a rapid application development language often used in financial applications.
Cognos Finance, for financial reporting, consolidation, budgeting and forecasting
Cognos Upfront, for portal service that provides end users with a single, Web-based point of personalised access to Cognos BI information and non-BI content
Hewlett-Packard MPE/iX
IBM OS/400
Data General DG/UX (Intel)
Auditing Tools
Access Manager
Creating calculations, conditions and prompts
Automating tasks
Optimizing performance
What is a catalog?
A file (with the extension .cat) that contains all the information necessary for Impromptu to access and retrieve information from a relational database.
Catalogs store metadata associated with the database structure including the
name and location of the database
names of the columns in the selected tables
join relationships between tables
A catalog does not store data, but it does provide Impromptu with a business view of the data.
Administrator’s Perspective
Different user communities can be served without modifying database
It specifies what information is available to Users and how it can be accessed
It provides single point of maintenance for entire Impromptu environment
User’s Perspective
Presents them with intuitive business view of their data
What does a Catalog contain?
Folders - Meaningful groups of information representing columns from one or more tables
Columns - Individual data elements that can appear in one or more folders
Calculations - Expressions used to compute required values from existing data
Conditions - Used to filter information so that only a certain type of information us displayed
Prompts - Pre-defined selection criteria prompts that users can include in reports
Personal Catalog
Can be used by only one person and not accessible to other Impromptu users.
Begin catalog creation process with Personal Catalog
After testing, can be converted to any other type for use by other users.
Shared Catalog
Shared catalog is generally stored on a LAN to provide access for all users.
Users can create their own reports but cannot change the catalog
All the users will work with the same catalog
By default, Users cannot add to the catalog but this ability can be assigned using Governor settings
Distributed Catalog
A Personal Distributed Catalog is made from Master for each User.
Users can create reports and make changes to their copies of catalog within limits of User classes assigned
When Master Catalog is changed, the changes are automatically applied to each Users Personal Catalog
Secured Catalog
A secured catalog is a read-only catalog that only the Creator can change.
Users cannot change the contents of the Catalog or Reports created from the Catalog and they cannot create new reports.
Users can only run reports already created, convert report to different file formats and print reports.
Limitations of Catalog
The size of the Catalog is determined by tables, folders and security restrictions
With Distributed Catalog, larger the master Catalog, longer it takes to copy the personal catalog to the user machine.
Catalogs approaching 1 MB in size can be inefficient.
When Catalog size increases
Organizing Folders become difficult
join definition becomes more complex
Joins define the relational links between tables in the physical database.
Joins relate the data in one table to the data in another table in the same database, enabling you to retrieve data from more than one table at a time.
Once joins are are defined they are available to Users and do not have to be redefined unless the database structure changes
Types of Joins
Equi join - retrieve all of the rows from one table and the rows in another table when values in the linked columns are equal
Non Equi join - retrieve all of the rows from one table that meet certain criteria in another table using operators <>, <, >,<=, >=
Self join (Reflexive) - required to join a table to itself. Can be used only by defining alias table
Outer join - retrieve rows from one table even if there are no matching rows in another table.
Compound join - useful where two columns will generate a unique key to join to another table
Complex join - Uses an expression created with the expression editor to join tables.
Organizing folders
A folder is a container used to present data in an Impromptu catalog
A folder is created automatically for each table in a Catalog
Folders contain data items, calculated data items, filter conditions and report prompts
Organize folders in a way that presents Users with one or more business views of the Organization
Organizing folders into a business view ensures the Users to easily locate the data based on a business oriented view
Organizing involve
User classes
without compromising security
Limit table access by User class(field-level security)
Limit folder access and restrict select values by User class(folder-level security)
Filter values by User class(security by value)
Set Governor values by User class
Set database tab values by user class
What is a Condition?
A condition is a true-false expression you can include in a report to filter data.
Country in (‘US’, ‘Canada’, ‘Mexico’)
What is a Calculation?
A calculation is an expression using existing data items to calculate a new data item.
If (Price - Cost) <= 0.50 * Price then (‘Low Margin’) else Null
What is a Prompt?
A prompt is an expression that you set up so users can filter the data in a report by typing or picking a filter value when the report opens.
Enter From Date:
Enter To Date:
Distribute revised Impromptu.ini file
Cognos Script Editor
Client / database-server balancing - to perform query processing by Database, Limited local processing or flexible processing
Table weighting - specifies the order in which tables will be retrieved
Qualifications - in more than one database the table name is same
Governors - make settings that affect processing variables. Sorting of Non-Indexed columns, Outer joins
Alternative Data Sources - Snapshots, Thumbnails, Hotfiles
User- defined functions - Custom functions for use within SQL statements
Bulk fetch - retrieves 100 rows of data by default in one fetch
Stored Procedures - can access stored procedures of data base
Auditing - record information about tasks performed in a log file
Use Architect as an alternative way to create catalogs
Web enable through Web Reports
Drill through Cognos query
Create PowerCubes for Powerplay
Create User Classes
Create List Report
Create a Chart
A modeling tool used to build multidimensional model from Source data
These models are distributed as a Power Cube to view in Powerplay for Windows/ Excel / Web or Visualiser
Dimension Map
The dimension map shows the dimensions and levels added to a model.
Dimensions are broad groupings of data that represent major segments of your business information
Dimensions consist of a hierarchy of categories, organized by level.
Levels are positions within the dimensional hierarchy that contain categories at the same order of detail, with a common set of attributes.
Source levels contain categories from a data source column
Data Sources List
The Data Sources list contains all data sources that you have imported into Transformer.
Measures List
The Measures list contains all available measures for your model.
Measures are numerical data used to gauge performance within the organization.
Reorganize the levels
Create Power cubes
Import Data Sources
Declare Level Uniqueness
Specify a Level Label
Create special Categories
Setup Currency conversion
SAP Business Intelligence Warehouse (SAP BW)
Drag, Choose, Swap
Add Nested Categories
What is a Visualization?
Used as an alternate to graphical representation of text or numeric data.
Use of Visualizations for presentation of data include:
Flow Charts
Several Types of Charts, including Scorecard style charts
Data from multiple metrics
Two-dimensional and three-dimensional layouts
Multiple data sources can be used can be used in a
single visualization.
Informix Dynamic Server
Select data sources
The support layer for all other layers. A visualization can have more than one sheet.
Contain an arrangement of panels. A sheet can contain more than one than one scene.
Containers for the content of the visualization. A scene can contain more than one panel.
Contains graphical display of data. Panel can contain one or more charts and maps.
From multiple data sources
At different levels of granularity
Consist of a number of data tables that can reside in any database
Provides a central repository for the information that defines how DecisionStream extracts, transforms, and delivers data.
DecisionStream catalog can be stored in either a dedicated database or target data mart database
Identifies the particular database
Specifies the connection method that DecisionStream must use to connect to the data
Provides information that the database management system (DBMS) requires when DecisionStream connects to the data,
Data Sources
Can extract data from a variety of relational sources via native interfaces and ODBC.
In addition to normalized, operational data, it can extract data from de-normalized data marts and from text files.
Where the source data contains hierarchical information, DecisionStream can be configured to accept data only at specified hierarchy levels.
Can be configured to interact with data sources by creating connections that establish the database objects and the connection methods to use.
DecisionStream supports DBMSs from many manufacturers, including ORACLE, Informix, Sybase, Microsoft, and IBM.
DecisionStream can connect to delimited text (ASCII or EBCDIC) data sources via the SQLTXT driver.
Dimensional Framework
Consists of reference dimensions, each of which models one dimension of business.
Each reference dimension can contain multiple hierarchies to represent the structure of the data independently of any source database.
DecisionStream supports an unlimited number of reference dimensions and therefore unlimited dimensionality.
Hierarchies can be built from the most appropriate source
Master Tables
Transaction Data
Static Elements
Perform aggregation
Deliver the fact and dimension data to one or more data marts
Deliver metadata to OLAP systems and Cognos e-BI applications
Fact Build wizard can be used to create builds.
Measures contain additive or semi-additive facts from the transaction data.
Attributes contain non-additive facts.
When DecisionStream performs aggregation, it consolidates
measures, attributes, and derivation elements along dimension
Data Transformation
Data may come from multiple data sources, each of which has its own naming and storage conventions.
DecisionStream can transform such data so that it exists in standard format within the target data marts.
DecisionStream derivation elements give you a powerful way to specify data transformations that meet the purposes of the target data marts.
User-defined functions help ensure consistency of calculations across many fact builds.
Dimension Build
Dimension build acquires data from a hierarchy specified and delivers data to the target data mart.
Delivers the dimension data to a single table (star schema) or to one table for each level of the hierarchy (snowflake schema), partitioned by custom criteria, or as a 'parent-child' structure.
To create dimension builds, you can use the Dimension Build wizard,
Metadata is data about the delivered relational structures.
It provides context for the fact data and describes the semantics of the dimension data.
It defines the underlying structure of the data; enabling reporting tools to process user requests rapidly.
It also provides aliases; enabling reporting tools to caption data more meaningfully.
Data Delivery
Fact data – values that represent facts. (the number of a product sold at a particular store on a particular day)
Dimension data – data that defines the core business components. (the range of products that the company produces)
Metadata – data that defines the structure of the fact data, the dimension data, and the relationships between them.

Click here to load reader

Embed Size (px)