gtstrtd dev ed

8/3/2019 Gtstrtd Dev Ed

1/94

IBM Cognos 8 Business Intelligence

Version 8.4.1

Developer Edition Getting Started Guide


2/94

Product InformationThis document applies to IBM Cognos 8 Version 8.4.1 and may also apply to subsequent releases. To check for newer versions of this document,visit the IBM Cognos Information Centers (http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp).

CopyrightLicensed Materials - Property of IBM

Copyright IBM Corp. 2008, 2009.

US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo, ibm.com, and Cognos are trademarks or registered trademarks of International Business Machines Corp., in many jurisdictionsworldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available onthe Web at www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsphttp://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp


3/94

Table of Contents

Introduction 5

Chapter 1: Installing and Configuring IBM Cognos 8 BI Developer Edition 7

Review the System Requirements 7

Install IBM Cognos 8 BI Developer Edition 8

Start IBM Cognos 8 Developer Edition Manager 8

Install Business Intelligence Components 9

Managing Users and Roles 9

Changing Default Users 9

Changing User Roles 10

IBM Cognos Administration 10

Log onto Cognos Connection11

Chapter 2: Installing and Setting up Sample Data 13

Install the IBM Cognos 8 Samples 13

Setting Up the Samples 14

Restore Backup Files for the Samples 14

Create Data Source Connections to the Samples 17

Set Up Microsoft Analysis Services Cube Samples 19

Create Data Source Connections to OLAP Data Sources 20

Import the Samples 22

Sample Database Models 23

Remove the Samples Databases from IBM Cognos 8 24About The Great Outdoors Group of Companies 24

Employees 26

Sales and Marketing 26

Great Outdoors Database, Models, and Packages 26

Chapter 3: Using IBM Cognos 8 BI Developer Edition 31

How IBM Cognos 8 BI Developer Edition Works 33

Viewing and Organizing Content 34

How is the Developer Edition Different from IBM Cognos 8 BI? 37

Building an Application 37

Designing the Model 38Creating Reports in Query Studio 43

Creating Reports in Report Studio 48

Create Analyses in Analysis Studio 56

Manage Events in Event Studio 63

Running and Scheduling Reports 66

Chapter 4: What is IBM Cognos 8 Business Intelligence? 71

Enhanced Agility for Competitive Advantage 71

Architecture 71

Date Source Support 72

Enterprise Security 73

Licensed Materials Property of IBM

3 Copyright IBM Corp. 2008, 2009.


4/94

Integrating Business Intelligence with Existing Applications 74

Business Intelligence Capabilities 74

Total Cost of Ownership 75

Global Deployment to Worldwide Communities 77

Moving Your Content to IBM Cognos 8 Business Intelligence 77

Install IBM Cognos 8 Business Intelligence 78

Plan Your Deployment 78Create an Export Deployment Specification 79

Move the Deployment Archive 81

Import to a Target Environment 82

Test the Deployed Content 84

Uninstall IBM Cognos 8 BI Developer Edition 84

Glossary 85

Index 89

4

Table of Contents


5/94

Introduction

This document provides instructions for setting up and using IBM Cognos 8 BI Developer Edition.

The Developer Edition is intended for use on a single Windows computer with up to two single-

core CPUs or dual core CPU.

To review an up-to-date list of environments supported by Cognos products, such as operating

systems, patches, browsers, Web servers, directory servers, database servers, and application servers,

visit the IBM Cognos Resource Center site (http://www.ibm.com/software/data/support/cognos_

crc.html).

Audience

This document is intended for users who are new to IBM Cognos 8 Business Intelligence.

To use this guide, you should have basic administration skills and be familiar with the existing

server environment and security infrastructure in your organization.

Related Documentation

Our documentation includes user guides, getting started guides, new features guides, readmes, and

other materials to meet the needs of our varied audience. The following documents contain related

information and may be referred to in this document.

Note: For online users of this document, a Web page such as The page cannot be found may appear

when clicking individual links in the following table. Documents are made available for your par-

ticular installation and translation configuration. If a link is unavailable, you canaccess the document

on the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html).

DescriptionDocument

Teaching new users how to use IBM Cognos 8IBM Cognos 8 Getting Started

Using IBMCognos Connection to publish, find, manage,

organize, andview IBMCognos content, such as reports,

analyses, and agents.

IBM Cognos Connection User Guide

Creating self-service business intelligence reportsQuery Studio User Guide

Authoring reports that analyze corporate data according

to specific needs

Report Studio Professional Authoring

User Guide

Authoring financial reports that analyze corporate data

according to specific needs

Report Studio Express Authoring User

Guide


http://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.html


6/94

DescriptionDocument

Creating and publishing models using Framework

Manager

Framework Manager User Guide

Understanding the IBM Cognos 8 architecture, develop-ing installation strategies, including security considera-

tions, and optimizing performance

IBM Cognos 8 Architecture andDeployment Guide

Printing Copyright Material

You can print selected pages, a section, or the whole book. You are granted a non-exclusive, non-

transferable license to use, copy, and reproduce the copyright materials, in printed or electronic

format, solely for the purpose of operating, maintaining, and providing internal training on IBM

Cognos software.

Upgrading to IBM Cognos 8 Business Intelligence

Upgrading to IBM Cognos 8 Business Intelligence is possible by purchasing full non-restricted

licenses, installing the new software, and then deploying the applications you developed with the

Developer Edition to the new software.

Getting Help

For more information about using this product or for technical assistance, visit the IBM Web site

(http://www.ibm.com/software/data/support/cognos_crc.html). This site provides information on

support, professional services, education, and a knowledge base of documentation and

troubleshooting information.

No support is provided for IBM Cognos 8 BI Developer Edition.

6

Introduction
http://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.html


7/94

Chapter 1: Installing and Configuring

IBM Cognos 8 BI Developer Edition

IBM Cognos 8 Developer Edition is provided with a 180 day trial license. This license cannot be

extended, even with a re-install. Developer Edition is not intended for production use.

The Developer Edition enables you to easily install IBM Cognos 8 on a Windows computer.

Developer Edition will also install Apache Tomcat and Apache Derby. Tomcat is used as an

application server by IBM Cognos 8, and Derby is used as a content store database.

During the installation process you are asked to provide an installation location and a password

for the administrator user and for a range of port numbers that will be used. Default values are

used for all other configuration settings.

Use the following checklist to guide you through the process of installing the Developer Edition.

Review the system requirements

Install IBM Cognos 8 Developer Edition

Start Developer Edition Manager

Install BI Components

Managing users and roles

Log onto IBM Cognos 8 Developer Edition

Review the System RequirementsBefore you install the Developer Edition ensure that the necessary prerequisites are met in your

environment.

Steps

Verify the hardware and software requirements by doing the following:

Review the system requirements for IBM Cognos 8 version 8.4.1 avaiable at http://www.ibm.com/software/data/cognos/customercenter/

Ensure that at minimum 1 GB of physical memory available for optimum performance and

reliability. 2 GB is recommended.

Ensure that you have at least 1.5 GB of temporary disk space available during the installa-

tion, as well as adequate disk space for the Developer Edition to operate properly.

Ensure you are using Microsoft Windows XP SP3 or higher.

Ensure you are using Microsoft Internet Explorer 7.0 or higher or Mozilla Firefox 3.5 or

higher.


http://www.ibm.com/software/data/cognos/customercenter/http://www.ibm.com/software/data/cognos/customercenter/http://www.ibm.com/software/data/cognos/customercenter/http://www.ibm.com/software/data/cognos/customercenter/


8/94

Install IBM Cognos 8 BI Developer EditionThe installation wizard installs the Developer Edition Manager. The manager allows you to install

a fully configured version of IBM Cognos 8 BI and Framework Manager.

Steps

1. Double-click install.exe to start the installation wizard.

The wizard takes a few moments to initialize, install temporary files, prepare for the deployment

and to create the uninstallation program settings.

2. On the Software License Agreement page, accept the agreement, and Next.

3. On the Choose Install Folder page, enter the location where you want the product installed,

and click Next.

4. On the Choose Shortcut Folder page, select the options you want, and click Next.

5. On the Configuration page, do the following:

Select the range of port numbers you want Developer Edition to use.

Ensure that you select a range that will not conflict with any other products you have

installed on your computer. If anyport numbers conflict with other software, the installation

will not be successful.

If you are unsure, use the default values.

Enter the account information for the administrator user.

You can leave the name as administrator or you can change it to another name. We

recommend you provide a password, and that you record it in a secure place.

6. Click Next.

7. On the Pre-Installation Summary page, click Install.

After the installation wizard finishes, you can launch IBM Cognos 8 BI Developer Edition Manager.

The manager allows you to install, configure, and start the IBM Cognos 8 BI services, and install

Framework Manager. You will need both the BI and Framework Manager components to use IBM

Cognos 8.

Start IBM Cognos 8 Developer Edition ManagerUse IBM Cognos 8 BI Developer Edition Manager to install and configure IBM Cognos 8 BI and

Framework Manager. You also use manager to add users to the system and start and stop services.

Steps

1. Start the manager from the installation wizard or by clicking Start, IBM Cognos 8 BI Developer

Edition, IBM Cognos 8 BI Developer Edition.

If this is the first time you have started the manager, you are prompted to complete the

installation.

8

Chapter 1: Installing and Configuring IBM Cognos 8 BI Developer Edition


9/94

2. Click Finish.

The manager completes the initial installation and configuration.

3. Enter the username and password you entered on the Configuration page of the installation

wizard, and click OK.

Install Business Intelligence ComponentsThe business intelligence (BI) components include BI Suite and Framework Manager. BI Suite

includes the IBM Cognos 8 studios for reporting and analysis of your data. Framework Manager

is the modelling component for the IBM Cognos 8 studios. To be able to use the studios to create

reports, queries, and analyses, you must first create packages using Framework Manager.

Use Developer Edition Manager to install the BI Suite and Framework Manager components.

Steps to Install IBM Cognos 8 BI Studios

1. In Products tab of the manager, click BI Suite.

2. Click Install.

Steps to Install Framework Manager

1. In Products tab of the manager, click Framework Manager.

2. Click Install.

Managing Users and RolesDeveloper Edition allows you to have five named users as well as the administrator user that you

created during the installation.

The users have not been assigned to any roles. You can change this using the Developer Edition

Manager. Users have not been assigned to any roles. If you create new users, you must select a role

for that user. For more information about users and roles, see the IBM Cognos 8 Administration

and Security Guide.

You use the Developer Edition Manager to change the user names and configure their roles.

Changing Default Users

You use the Developer Edition Manager to edit user information. For example, you can change the

user IDs and passwords for any user.

You can have a maximum of five named users, as well as the administrator user. To change the

default users, you must remove them and then add your own users.

Steps

1. In Developer Edition Manager, under Administration, click Users.

2. Click the user whose information you want to change.

Developer Edition Getting Started Guide 9



10/94

3. Click Remove.

4. Click Add.

5. Enter the Username, Password, and any of the other fields.

6. In the Available Entries box, double click a role to copy it into the Selected Entries box.

Tip: For information about the roles, see the IBM Cognos 8 Administration and Security

Guide.

7. To assign additional roles, repeat the previous step.

8. Click OK.

Changing User Roles

You use the Developer Edition Manager to change user roles. Roles allow you to change user access

to content. For more information about users and roles, see the IBM

Cognos

8 Administrationand Security Guide.

Steps

1. In Developer Edition Manager, under Administration, click Users.

2. Click the user whose information you want to change.

3. Click Edit.

4. In the Available Entries box, double click a role to copy it into the Selected Entries box.

Tip: For information about the roles, see the IBM Cognos 8 Administration and Security Guide.

5. To assign additional roles, repeat the previous step.

6. Click OK.

IBM Cognos Administration

IBM Cognos Administration allows you manage your IBM Cognos 8 BI installation, including

monitoring the system, adding data sources, managing user groups. For more information about

using IBM Cognos Administration, see the online help.

While Cognos Administration allows you to change user settings, you should use the Developer

Edition Manager to change your user IDs, permissions, and roles.

Steps to Start IBM Cognos Administration

1. Start Developer Edition Manager, and log on as an Administrator user.

2. From the Launch menu, click IBM Cognos Administration.

10



11/94

Log onto Cognos ConnectionAfter the Developer Edition is installed and configured, and the services are started, you can start

exploring the portal and the studios by opening IBM Cognos Connection in a Web browser.

Steps from Deverlop Edition Manager

1. Start Developer Edition Manager.

2. From the Launch menu, click IBM Cognos Connection.

Steps

1. Open a Web browser.

2. Open IBM Cognos Connection by typing the following, where hostname is the name of the

computer where you installed the Developer Edition:

http://hostname:9300/p2pd/servlet/dispatch

The Log On page appears.

3. Enter your User ID and Password, and click OK.

Cognos Connection appears.

You can start to explore the studios and the portal by opening the links in the portal.

Sample reports and packages are available to be downloaded and installed. Once you have installed

and set up the samples, see "Building an Application" (p. 37) to learn how to use the Developer

Edition for your business reporting needs.




12/94

12



13/94

Chapter 2: Installing and Setting up Sample Data

This section explains the purpose, content and location of IBM Cognos 8 samples. It also discusses

the sample company, Great Outdoors, its structure, databases, model and packages.

The Great Outdoors Company samples illustrate product features and technical and business best

practices. You can also use them for experimenting with and sharing report design techniques and

for troubleshooting.

For examples related to different kinds of businesses, see the product blueprints at (http://www.

ibm.com/software/data/support/cognos_crc.html). For information about specific installation choices

and environments, see the Architecture and Deployment Guide, or the Proven Practices and the

IBM Cognos Implementation Roadmaps on the IBM Cognos Resource Center (http://www.ibm.

com/software/data/support/cognos_crc.html). For information about audit samples, see the

Administration and Security Guide.

Where to Find the Samples

The samples are provided as separate downloads for each database. To use the samples, you must

download the installation files, install them to same location as you installed Developer Edition

(p. 13), and then set them up (p. 14).

What Samples Exist

The samples consist of two databases that contain all corporate data, the related sample models

for query and analysis, and sample cubes, reports, queries, query templates, and dashboards.

Install the IBM Cognos 8 SamplesThe IBM Cognos 8 samples illustrate product features and technical and business best practices.

You can also use them for experimenting with and sharing report design techniques, and for

troubleshooting.

Install in a directory that contains only ASCII characters in the path name.

Steps

1. Double-click install.exe to start the installation wizard for the sample for the database you

want.

The samples are provided for DB2, Oracle, Microsoft SQL Server, and Informix.

2. On the Software License Agreement page, accept the agreement, and Next.

3. On the Choose Install Folder page, click Next.

The samples will be installed to the same location as you installed Developer Edition.

4. On the Pre-Installation Summary page, click Install.


http://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.html


14/94

The sample databases and report content are installed to the installation_loca-

tion\webcontent\samples directory.

Setting Up the Samples

IBM

Cognos

8 provides sample databases for SQL Server, Oracle, DB2, and Informix that containsales and marketing information for a fictional company named the Great Outdoors. You can use

IBM Cognos sample packages and reports to help you learn how to use IBM Cognos 8.

Restore Backup Files for the Samples

To use the samples, you must restore backup files for the samples databases. This action re-creates

multilingual versions of the Great Outdoors databases.

The following sample databases and associated files are provided with IBM Cognos 8. For SQL

Server and Oracle, each database is delivered as a Microsoft SQL Server backup file and an Oracle

export file (.dmp). For DB2, the database schemas are delivered in a DB2 move file. The files arecompressed, and you must extract them before you can restore the databases or schemas.

SQL Server Databases and Files

File nameDatabase or schema description

GOSALES.zipGreat Outdoors sales

GOSALES.zipGreat Outdoors retailers

GOSALESDW.zipGreat Outdoors sales data warehouse

GOSALES.zipGreat Outdoors market research

GOSALES.zipGreat Outdoors human resources

Oracle Databases and Files


GOSALES.dmp.gzGreat Outdoors sales

GOSALES.dmp.gzGreat Outdoors retailers

GOSALESDW. dmp.gzGreat Outdoors sales data warehouse

GOSALES.dmp.gzGreat Outdoors market research

GOSALES.dmp.gzGreat Outdoors human resources

14



15/94

DB2 Databases and Files


GS_DB.tar.gzGreat Outdoors sales

GS_DB.tar.gzGreat Outdoors retailers

GS_DB.tar.gzGreat Outdoors sales data warehouse

GS_DB.tar.gzGreat Outdoors market research

GS_DB.tar.gzGreat Outdoors human resources

csgodw.xmlCubing services sample cube

Informix Databases and Files


GOSALES.zipGreat Outdoors sales

GOSALES.zipGreat Outdoors retailers

GOSALESDW.zipGreat Outdoors sales data warehouse

GOSALES.zipGreat Outdoors market research

GOSALES.zipGreat Outdoors human resources

When restoring the samples databases, ensure that you do the following:

Give the restored databases the same names as the backup or export file names.

The names are case-sensitive.

Create users with select privileges for tables in multiple schemas.

Setup for the GO Data Warehouse packages specifies a single connection object and user signon.

This requires a single user named GOSALESDW with the select privilege to tables in a single

schema named GOSALESDW.

Setup for the GO Sales packages specifies a single connection object and user signon. This

requires a single user named GOSALES with the select privilege to tables in the four schemas:

GOSALES, GOSALESHT, GOSALESMR, and GOSALESRT.

Use the UTF-8 character set on the database server.

Use the UTF-8 character set on the Windows computer that is the Oracle or DB2 client to see

reports in multiple languages.




16/94

For DB2, you must set the DB2CODEPAGE environment variable to a value of 1208. For

Oracle, you must set the NLS_LANG environment variable to a value that is specific to a region.

For example, set NLS_LANG for Americas to American_America.UTF8.

Have sufficient disk space available in the target location. Reserve 150MB for the GO Sales

data (four schemas) and 200MB for the GO Data Warehouse data (one schema).

Oracle Considerations

To create foreign key constraints in tables that reference different schemas, you must run

gs_or_modify.sql, found in the same folder as the .dmp files.

SQL Server Considerations

If you restore the SQL Server backup files, you must use Microsoft SQL Server 2000 or Microsoft

SQL Server 2005. Ensure that TCP/IP connectivity is used for the SQL server.

DB2 Considerations

Before you restore the Great Outdoors schemas contained in the DB2 move file on UNIX or Win-

dows, extract the DB2 move file. On UNIX, extract the DB2 move file using the gnutar -xcvf

DB2_move_filename or tar -xcvf DB2_move_filename command. If you use WinZip to extract

the DB2 move file on Windows, ensure that the TAR file smart CR/LF conversion option is not

selected.

After extracting the DB2 move file, restore the schemas to a database named GS_DB.

To add views, constraints, user privileges, and stored procedures to GS_DB, prepare and run the

gs_db_modify files included with the samples in the following order:

Update the user name and password at the top of the gs_db_modify.sql and save it.

Execute gs_db_modify.bat

An XML file is also provided if you want to use IBM InfoSphere Warehouse Cubing Services. The

XML file, named csgodw.xml, must be imported into a data model based on the GS_DW schema,

deployed, and then added as a cube to the cube server. The cubing services sample is available only

if you install the IBM DB2 samples.

Informix Considerations

Use the dbimport command to restore the databases using the backups namedgosales and gosalesdw.Ensure that the server you restore the samples to is UTF-8. For example, the CLIENTE_LOCALE,

DB_LOCALE, and DBLANG variables must specify a UTF-8 encoding, such as EN_US.UTF8.

Steps to Restore the Database Files

1. On the computer where IBM Cognos 8 is installed, go to the sql server, oracle, db2, or informix

directory located in c8_location/webcontent/samples/datasources.

2. If required, copy the backup files for the samples databases to your database backup directory.

To ensure the security and integrity of IBM Cognos 8, copy the files to a directory that is pro-

tected from unauthorized or inappropriate access.

16



17/94

3. Restore the samples databases using your database management tool.

Tips

For SQL backup files, restore the database from a device, and ensure that the restore loca-

tions are correct for the .ldf and .mdf database files. For more information, see the Microsoft

SQL Server documentation or the IBM Cognos Knowledge Base on the IBM Cognos Cus-

tomer Service Center (http://www.ibm.com/software/data/support/cognos_crc.html).

For DB2, when you create the GS_DB database, create a buffer pool with a page size of

16 KB and an associated tablespace.

For Informix, use a page size of 16 KB and a tablespace of about 300,000 KB.

4. For each database, create at least one user who has select permissions for all the tables in the

restored databases.

Steps to Use IBM the InfoSphere Warehouse Cubing Services File

1. On the computer where IBM Cognos 8 is installed, go to the db2 directory located in c8_location/

webcontent/samples/datasources.

2. If required, copy the csgodw.xml file to your database backup directory.

3. In IBM InfoSphere Warehouse Design Studio, import the csgodw.xml metadata file into a data

model based on the DB2 GS_DW schema.

4. Deploy the CSGODW cube to the DB2 GS_DW schema.

5. Use the IBM InfoSphere Warehouse Administration Console to add the new cube to a cube

server, and run it.

Note the XMLA port number for the cube, as this number is required for the datasource con-

nection.

You can now create the data source connections in the portal.

Create Data Source Connections to the Samples

You must create data source connections to the samples databases that you restored. IBM Cognos 8

uses this information to connect to the samples databases and run the sample reports or use the

sample package.The DB2 database name that you type must use uppercase letters. Also, in Framework Manager,

the schema names that you type for the DB2 data sources must use uppercase letters.

Before you create the data source connections, you must restore the backup files for the samples

databases. Also, ensure that the IBM Cognos 8 service is running.

To create data sources, you must have execute permissions for the Data Source Connections secured

feature and traverse permissions for the Administration secured function.

Steps

1. Open Developer Edition Manager.


http://www.ibm.com/software/data/support/cognos_crc.htmlhttp://www.ibm.com/software/data/support/cognos_crc.html


18/94

2. In the upper-right corner, click Launch, IBM Cognos Administration.

3. Click the Configuration tab.

4. Click the new data source button .

5. In the Name box, type great_outdoors_sales and then click Next.

6. On the connection page, click the type of database that you restored and want to connect to,

select an isolation level, and then click Next.

The connection string page for the selected database appears.

Tip: The user specified in the great_outdoors_sales data source must have select privileges on

the tables in each of the GOSALES, GOSALESRT, GOSALESMR, and GOSALESHR schemas

(p. 14).

7. Do one of the following:

For SQL Server, in the Server Name box, type the name of the server where the restoreddatabases are located. In the Database name box, type GOSALES.

IBM Cognos 8 samples require TCP/IP connectivity with SQL Server. Ensure the SQL

Server Security is set to SQL Server and Windows, instead of Windows Only. The samples

use SQL Server security for authentication.

For Oracle, in the SQL*Net connect string box, type the Oracle connection string.

For DB2, in the DB2 database name box, type GS_DB using uppercase letters. In the DB2

connect string box, type the DB2 connection string.

8. Under Signons, select the both Password and Create a signon that the Everyone group can use

check boxes, type the user ID and password for the user that you created when you restored

the databases, and then click Finish.

Tip: To test whether the parameters are correct, click Test the connection....

9. Click Finish.

10. Repeat steps 4 to 9 for the GOSALESDW samples database or schema, and type great_outdoors_

warehouse in step 5.

The Great Outdoors data source connections appear as entries in Data Source Connections.

Steps for IBM InfoSphere Warehouse Cubing Services

1. Open Developer Edition Manager.


3. Click the Configuration tab.

4. Click the new data source button .

5. In the Name box, type sales_and_marketing_cs, and then click Next.

18



19/94

6. On the connection page, click IBM InfoSphere Warehouse cubing services (XMLA), and click

Next.


7. In the Server URL box, type the name of the server and the XMLA port number for the cube,

followed by

/IBMXmlAnalysis

For example, myserver:1999/IBMXmlAnalysis

8. Under Signons, select the both Password and Create a signon that the Everyone group can use

check boxes, and then click Finish.

Tip: To test whether the parameters are correct, click Test the connection....

9. Click Finish.

Set Up Microsoft Analysis Services Cube SamplesIBM Cognos Connection or Framework Manager provides sample cubes for Microsoft Analysis

Services (MSAS).

For finance data, use the GO Finance Fact cube derived from the GOSALESDW database. This

cube contains year-to-dateand monthly financial data for all accounts so that you can create financial

statements in Analysis Studio, Query Studio, and Report Studio. The data is in actual US dollars

submissions for 2004, 2005, 2006, or 2007 (7 months actual data only).

The MSAS2000 version of the finance cube and database is in the GOFinanceFact_XX.cab file.

The MSAS2005 version is in the GOFinanceFact_XX.abf file. XX represents the language. For

example, XX is replaced with EN which indicates English.

For sales data, use the GOSalesFact cube derived from the GOSalesFact_XX Analysis Services

database, based on the GOSALESDW SQLSERVER Database. The cube contains measures such

as unit cost, unit price, quantity, and gross profit. Dimensions include Time, Product, and Retailers.

The MSAS2000 version of the sales cube and database is archived in the GOSalesFact_XX.cab.

The MSAS2005 version is in the GOSalesFact_XX.abf restorable backup file.

The backup files are located in the c8_location/webcontent/samples/datasources/cubes/MSAS

directory. The files must be restored to a Microsoft SQL Server database running the applicable

Microsoft Analysis Services (p. 14). and hosting the GOSALESDW database.

The MSAS samples are available only if you installed the Microsoft SQL Server samples.

Note: Both Microsoft XML 6.0 Parser and Microsoft SQL 2005 Analysis Services 9.00 OLEDB

Provider must be installed on the local client to establish data source connections to MSAS cubes.

Steps

1. On the computer where IBM Cognos 8 is installed, go to the c8_location/webcontent/samples/

datasources/cubes/MSAS/en directory.

2. Copy the GOSALESDW.cab and GOSALESDW.abf files to a directory that you can access

from the Analysis Manager console in the Analysis Servers of Microsoft SQL Server.




20/94

3. Use the Microsoft Analysis Services Analysis Manager to restore the database from the GOS-

ALESDW.cab and GOSALESDW.abf files.

You can now create the data source connections using either the GOSalesFact_XX or GOFinance-

Fact_XX cubes (p. 20).

Create Data Source Connections to OLAP Data SourcesIBM Cognos 8 provides the following OLAP samples:

GO Sales Fact and GO Finance Fact Microsoft Analysis Services cubes

Great Outdoors Company cubes

Great Outdoors DB2 cube

You must create data source connections to the cubes to use the samples. You must set up the

Microsoft Analysis Services cube samples, if you are using them, before creating data source con-

nections.You can increase the read cache size to improve query performance, although this setting has no

effect on the initial time required to open a cube.

To create data sources, you must have execute permissions for the Data Source Connections secured

feature, and traverse permissions for the Administration secured function.

Steps for PowerCubes

1. Open IBM Cognos Connection by connecting to the IBM Cognos 8 portal and clicking IBM

Cognos Content on the Welcome page.


3. On the Configuration tab, click Data Source Connections.

4. Click the new data source button.

Note: You must add a data source connection for each cube.

5. To create a data source connection for the Sales and Marketing cube, type sales_and_marketing

in the Name box, and then click Next.

6. In the connection page, under Type click IBM Cognos PowerCube.


7. In the Read cache size (MB) box, type the cache size of the cube in megabytes.

If you leave this field blank or type 0, IBM Cognos Connection uses the default value in the

ppds_cfg.xml file in the configuration folder.

8. In the Windows location box, type the location and name of the Sales_and_Marketing.mdc file

for the data source connection. For example, type

c8_location/webcontent/samples/datasources/cubes/PowerCubes/En/Sales_and_Marketing.

mdc

20



21/94

9. To test whether the parameters are correct, click Test.

10. Click Finish.

You can now import the sample package for the PowerCube to use this data source.

Steps for Microsoft Analysis Service Cubes




3. On the Configuration tab, click New Data Source.

4. In the Name box, type the name of the data source connection, and then click Next.

For the GOFinanceFact cube, type GOFinanceFact_XX_MSAS2005.

For the GOSalesFact cube, type GOSalesFact_XX_MSAS2005.

5. In the Specify Connection page of the New Datasource Wizard, click Microsoft Analysis Services

2005 or click Microsoft Analysis Services (via ODBO) as appropriate to the cube you are

accessing.

6. Click Next.

7. In the Server Name box, type the name of the server where the restored databases are located.

Back slashes are not required.

8. Under Signon, select the Password check box and then select the Create a signon that the

Everyone group can use check box. Type the user ID and password for the MSAS database.

For MSAS2005, this is a network login.

9. Click Test the connection, and then click the Test button. Click Close.

10. Click Finish.

You are now prompted to create a package.

Alternatively, you can deploy an existing package from a sample deployment archive. The

names of the deployment archives match the datasource connection names specified in step 4

and contain sample reports that work with the associated cubes.

In Content Administration on the Configuration tab in IBM Cognos Administration, click New

Import. The New Import Wizard prompts you to select a deployment archive. When you select

a deployment archive, it is important to click Edit and specify a target name for the package

to prevent an existing package from being overwritten.

11. To create a package, check Create a Package and then click OK.

12. Specify a package name and then click OK.

For the GO Finance Fact cube, type GOFinanceFact_XX_MSAS2005.

For the GO Sales Fact cube, type GOSalesFact_XX_MSAS2005.




22/94

13. Specify the Analysis Services database you restored either GOFinanceFact_XX or GoSales-

Fact_XX:

For either the GOFinanceFact cube or the GOSalesFact cubes, type GOSALESDW.

For the GO Sales Fact cube, type GO Sales Fact.

14. Click the cube applicable to the database.

15. Click Finish.

Import the Samples

To use the sample package and other content, you must import them from the sample deployment

archive.

Before you import the Cognos_Samples.zip deployment archive, you must restore the databases

(p. 14). You must also create data source connections to the samples databases (p. 17).

The IBM InfoSphere Warehouse Cubing Services sample uses the deployment file named

Cognos_csgodw.zip. The sample is available only if you installed the IBM DB2 samples.

For more information about locales, see the IBM Cognos 8 Installation and Configuration Guide.

Steps

1. Copy the zip files from the c8_location/webcontent/samples/content directory to the directory

where your deployment archives are saved.

The default location is c8_location/deployment.

2. Open IBM Cognos Connection by connecting to the IBM Cognos 8 portal and clicking IBMCognos Content on the Welcome page.


4. On the Configuration tab, click Content Administration.

Note: To access this area in IBM Cognos Administration, you must have the required permissions

for the Administration tasks secured feature.

5. On the toolbar, click the new import button.

The New Import wizard appears.

6. In the Deployment Archive box, select the archive. Depending on which samples you installed,

you can deploy:

Cognos_Samples, for the Great Outdoors company samples

Cognos_DrillThroughSamples, to use Drill Through capabilities with the Great Outdoors

company samples

Cognos_csgodw, for the IBM InfoSphere Warehouse Cubing Services samples

7. Click Next.

22



23/94

8. Type a unique name and an optional description and screen tip for the deployment archive,

select the folder where you want to save it, and then click Next.

9. In the Public Folders Content box, select the deployment archive that you want to import.

10. Select the options you want, along with your conflict resolution choice for options that you

select, and then click Next.

11. In the Specify the general options page, select whether to include access permissions and refer-

ences to external namespaces, and who should own the entries after they are imported.

12. Click Next.

The summary information appears.

13. Review the summary information and click Next.

14. Select the action that you want:

To run once now or later, click Save and run once. Click Finish, specify the time and datefor the run, then click Run. Review the run time and click OK.

To schedule at a recurring time, click Save and schedule. Click Finish, and then select fre-

quency and start and end dates. Click OK.

Tip: To temporarily disable the schedule, select the Disable the schedule check box.

To save without scheduling or running, click Save only and click Finish.

15. When the import is submitted, click Finish.

You can now use the sample packages to create reports and analyses in Report Studio, Query Studio,and Analysis Studio or create agents in Event Studio. You can also run the sample reports that are

available on the Public Folders tab in the portal.

Sample Database Models

The following sample models provide information for the fictional company, the Great Outdoors

and are provided with IBM Cognos 8:

great_outdoors_sales, which refers to the samples database GOSALES

great_outdoors_warehouse, which refers to the database GOSALESDW

You can use sample database models on different platforms. For information about moving models

from one platform to another, see the Framework Manager User Guide.

GO Sales Model

This model contains sales analysis information for the fictional company, The Great Outdoors. It

also has the query items required by the Event Studio samples. The model accesses three schemas

and has two packages. One package is based on the dimensional view and the other is baed on the

query (relational) view.




24/94

GO Data Warehouse Model

This model contains financial, human resources, and sales and marketing information for the fictional

company, The Great Outdoors. The model accesses a dimensional relational data source. The model

has two packages. One package is based on the dimensional view, the other is based on the query

(relational) view.

Remove the Samples Databases from IBM Cognos 8

After you finish using the sample reports to learn about IBM Cognos 8, including Framework

Manager, you can delete the packages on which the samples are based. This action permanently

removes the samples from the content store.

Steps



2. Click the Public Folders tab.

3. Select the check box for the sample package you want to delete.

4. Click the delete button on the toolbar, and click OK.

To use the samples again, you must set up the samples.

About The Great Outdoors Group of CompaniesTo make designing examples faster, especially financial examples, some general information about

The Great Outdoors Company is useful. To look for samples that use particular product features,

see the individual sample descriptions in this appendix.

Revenue for The Great Outdoors Company comes from corporate stores and from franchise oper-

ations. The revenues are consolidated from the wholly-owned subsidiaries. There are six distinct

organizations, each with its own departments and sales branches. Five of these are regionally-based

companies.

The sixth company, GO Accessories

has its own collection of products, differentiated from the other GO companies by brand, name,

price, color and size

sells from a single branch to all regions and retailers

functions both as an operating company based in Geneva, and as a part owner of the three GO

subsidiaries in Europe.

The diagram below illustrates the consolidated corporate structure, including the percentage changes

in ownership for GO Central Europe, and shows the reporting currency and GL prefix for each

subsidiary.

24



25/94

Each corporation has the same departmental structure and the same GL structure, shown in the

table below. Divisions may not report in the same currencies. For example, the Americas subsidiary

reports in US dollars, but the Corporate division local currency is Canadian dollars, and the Oper-

ations division local currency is pesos.

Department (GL)Division (GL)

Sales (1720)Corporate (1700)

Marketing (1750)

IS&T (1760)

Human Resources (1730)

Finance (1740)

Procurement (1710)

Production and Distribution (1820)Operations (1800)

Customer Service (1820)

Each corporation has a complete chart of accounts. Most of the accounts, such as those under non-

personnel expenses, are at the department level, and contain only summary amounts. For example,

although each marketing department has expenses, the cost is unspecified at the transaction level

where marketing promotions occur.




26/94

Employees

The Great Outdoors data contains a full list of employees in all divisions, departments, and locations.

Data is available for reports about bonuses (Global Bonus report) and sales commissions (Sales

Commissions for Central Europe report), training (Employee Training by Year report), and perform-

ance reviews and employee satisfaction surveys (Employee Satisfaction 2006). If you use Metric

Studio, sample metrics for human resources are also available.

In the GO Data Warehouse (analysis) package, groups of measures and the related dimensions are

organized into folders. The employees are organized in hierarchies for region, manager, position

or department, and organization, to make different kinds of aggregation easy to report on.

Aggregation has been defined for the Employee Position Summary measures, so that Position count

and Planned position count aggregate correctly at each level of time: monthly, quarterly, or yearly.

For example, see the Planned Headcount report.

Sales and Marketing

Data about sales and marketing is available for all of the companies in the Great Outdoors group.GO Accessories has richer details to support analysis examples. For example, see the Revenue vs

% Gross Profit by Product Brand analysis, based on the Sales and Marketing cube. Marketing and

sales campaigns are tied to the Great Outdoors regional companies.

Overall, the GO companies have experienced solid growth across most product lines (Sales Growth

Year Over Year), in all regions (Revenue by GO Subsidiary 2005), because of factors like an increase

in repeat business and new or improved products, such as the high margin sunglasses product line.

In the product lines sold by the five regional companies (all but GO Accessories) promotions have

had mixed success (Promotion Success by Campaign, Bundle and Quarter).

Customer Surveys

The data also contains information from customer surveys. For example, the product line that

includes bug spray, sun screen, and so on has not been successful (Product Satisfaction - Outdoor

Protection 2005) and a source of retailer dissatisfaction may be the level of customer service rather

than the returns (Customer Returns and Satisfaction).

Sales Outlets

Revenue from the corporate outlets is available at the transaction level. Revenue from the franchise

outlets is available at the consolidated level only (Sales and Marketing cube). Metrics about retailers

show that the number of new retail outlets has dropped over the time period covered by this data.

GO Accessories sells worldwide, and sells only accessories. Transaction data for GO Accessories

is the primary source for analysis of product by brand, color and size. The other five subsidiaries

in the group of companies are regional and sell all product lines for retailers in their region. For

example, the report Top 10 Retailers in 2005 uses sparklines and list data to review revenues at

the retailer level.

Great Outdoors Database, Models, and Packages

The Great Outdoors models illustrate modeling techniques and support the samples. The models

are based on the GO data warehouse and the GO sales transactional database and are the basis for

26



27/94

the sample reports and queries. Each model contains two packages for publishing analysis (dimen-

sional) and query views of the data.

For a description of each sample report or query, see the user guide for the studio that you open

the sample in. For more information about modeling techniques, see the Guidelines for Modeling

Metadata, or the Framework Manager User Guide.

You must have access to Framework Manager, the modeling tool in IBM Cognos 8, to look at thesample models. You may also need to set up the sample databases and connections. For instructions,

see the Administration and Security Guide or the Installation and Configuration Guide.

GO Data Warehouse

The GO Data Warehouse model, great_outdoors_warehouse.cpf, is based on the database GOS-

ALESDW. It contains data about human resources, sales and marketing, and finance, grouped into

business areas. In the Database view, the three business areas are grouped into separate namespaces.

The Database view contains a fourth namespace (GO Data) for the common information.

The Database view is very similar to the structure of the underlying database. All tables (databasequery subjects) are unchanged. This enables IBM Cognos 8 to retrieve metadata directly from the

package in most cases, instead of using a metadata call to the database. The following changes and

additions have been made in the Database view:

Joins have been added as necessary.

To allow for aggregation at different levels of granularity, some model query subjects have

been created. For example, see the relationships between Time and Sales or Sales fact.

To allow single joins to be made between the lookup tables and each level in a dimension,

lookup tables have been copied. For example, see the Products look up tables.

The Business view contains only model query subjects, with no joins. The following changes and

additions have been made in the Business view:

Calculations were added to the model query subjects. For example, the time dimension contains

language calculations.

Where the database has multiple hierarchies, new dimensions have been created to organize

each hierarchy. For example, see the employee hierarchies, where employees are organized by

manager, organization, region, and position.




28/94

The GO Sales Transactional Database

The GO Sales model, great_outdoors_sales.cpf, is based on the GOSALES database, which is

structured as a transactional database. It contains principally sales data.

The Database view is very similar to the underlying database structure. The following changes and

additions have been made in the Database view: To make it possible to join the fact tables to the time dimension, model query subjects and

multipart joins have been used.

Other joins have been added as necessary.

The Business view contains only model query subjects, with no joins. The following changes and

additions have been made in the Business view:

Calculations were added to the model query subjects.

Model query subjects that were created in the Database view to enable joins on the time

dimension have been linked as reference shortcuts.


each hierarchy.

Sales Staff is a subset of the slowly changing Employee dimension.There is no unique Employee

key in GO Sales, so a filter retrieves the current record only. This model does not use historical

data.

The Samples Cubes

The following cubes are delivered with the Great Outdoors samples:

28



29/94

sales_and_marketing.mdc

employee_expenses.mdc

go_accessories.mdc

go_americas.mdc

go_asia_pacific.mdc

great_outdoor_sales.mdc

The Samples Packages

The Great Outdoors samples include seven packages. Below is a brief description of each available

package.

Go Data Warehouse (analysis) is a dimensionally modeled view of the GOSALESDW database.

This package can be used in all studios, including Analysis Studio. Using this package you can drill

up and down.

Go Sales (analysis) is a dimensionally modeled view of the GOSALES database. This package can

be used in all studios, including Analysis Studio. Using this package you can drill up and down.

Go Data Warehouse (query) is a non-dimensional view of the GOSALESDW database. This package

can be used in all studios except Analysis Studio, and is useful for reporting when there is no need

for drilling up and down.

Go Sales (query) is a non-dimension view of the GOSALES database. This package can be used in

all studios except Analysis Studio, and is useful for reporting when there is no need for drilling up

and down.

Sales andMarketing (conformed) is based on the GOSALESDW database. Dimensions are conformed

with the dimensions found in the Sales and Marketing (cube) package, in order to enable drill-

through from the cube package to the dimensional package.

Sales and Marketing (cube) is an OLAP package, based on the sales_and_marketing.mdc cube.

Great Outdoor Sales (cube) is an OLAP package, based on the great_outdoors_sales_en.mdc cube.




30/94

30



31/94

Chapter 3: Using IBM Cognos 8 BI Developer

Edition

IBM Cognos 8 BI is an integrated business intelligence (BI) suite that provides a wide range of

functionality to help you understand your organization's data. IBM Cognos 8 BI Developer Edition

leverages the report, analysis, and query capabilities of Cognos 8 BI to help you make effective

business decisions.

The Developer Edition integrates the following business intelligence activities:

ComponentActivity

Framework ManagerCreating and publishing a business view of data

Cognos ConnectionPublishing, managing, and viewing content

Query StudioAd hoc querying and self-service reporting

Report StudioProfessional reporting

Analysis StudioAnalyze your business

Event StudioEvent management and alerting

Creating a Business View of Your Data - Framework Manager

You model data within data sources to structure it in a way that is meaningful to users.

Framework Manager is the modeling tool for creating and managing business-related metadata for

use in reporting. Reporting tools, such as Query Studio or Report Studio, use the metadata, which

is published as a package, to provide a single, integrated business view of your data.

Publishing, Managing, and Viewing Content - Cognos Connection

Cognos Connection is theWeb portal. It provides the starting point for accessing your BI informationand the functionality of the Developer Edition. Use the portal to publish, find, manage, organize,

and view your organizations business intelligence content, such as reports. If you have the necessary

permissions, you can access the various studios from the portal. You can also use the portal for

content administration, including scheduling and distributing reports, and creating jobs.

Ad Hoc Querying and Self-Service Reporting - Query Studio

Query Studio is the reporting tool for creating simple queries and reports. A casual or novice user

can use Query Studio to create self-serve reports that answer simple business questions. With minimal

steps, you can

view data




32/94

author basic reports

change the report layout

filter and sort data

add formatting

create charts

When you use Query Studio, you interact directly with your data.

Professional Reporting - Report Studio

Report Studio lets professional report authors create, edit, and distribute a wide range of professional

reports. They can also define corporate-standard report templates for use in Query Studio, and edit

and modify reports created in Query Studio.

Report Studio offers two distinct authoring modes to meet the needs of both regular report authors

and financial report authors: Professional authoring mode and Express authoring mode. The userinterface for each authoring mode contains reporting features relevant to each role.

Professional Authoring Mode for Advanced Reporting Capabilities

The Professional authoring mode gives users access to the full range of Report Studio function-

ality. In this mode, you can create any report type, including charts, maps, lists, and repeaters.

This mode contains a superset of the features available in the Express authoring mode. However,

you cannot view live data.

Express Authoring Mode for Business and Financial Analysts

The Express authoring mode provides a simplified and focused Report Studio interface. It letsbusiness and financial analysts create traditional financial statement-style reports. By default,

this mode allows access to dimensionally-modeled data and uses a member-oriented data tree.

This authoring mode allows you to see live data and supports crosstab reports. It contains a

subset of the features available in the Professional authoring mode.

When you are in the Express authoring mode, if you open a report that was authored in the

Professional authoring mode, you can see the objects that you can insert only in the Professional

authoring mode, such as charts, maps, and lists. However, you cannot modify these objects.

Analyze Your Business - Analysis StudioManagers and analysts use Analysis Studio to better understand their business and to get answers

to questions that they have about their business. Users can quickly and easily perform analysis to

get to the what and why behind an event or action so that they can improve business performance.

With analysis, it is possible to see trends and understand anomalies or variances that may not be

evident with other types of reporting. Analysis Studio users can easily focus on what is important

even with large volumes of dimensional data.

When you use Analysis Studio, you interact directly with visible data.

32

Chapter 3: Using IBM Cognos 8 BI Developer Edition


33/94

Event Management and Alerting - Event Studio

Event Studio is the notification tool used to alert decision-makers in your organization of events as

they happen, so that they can make timely and effective decisions.

You can use Event Studio to create agents that monitor status changes, priority customers, your

organizations data to detect occurrences of business events, or any other factor that is important

to your business.

Specify the event condition, or a change in data, that is important to you. When an agent detects

an event, it can perform tasks, such as sending an email, adding information to the portal, and

running reports.

How IBM Cognos 8 BI Developer Edition WorksWhen you view or create a report, you are viewing and manipulating data stored in your organiza-

tions databases. The following diagram explains the steps involved in using the Developer Edition.

1. In Framework Manager, the modeler ensures that metadata is presented in a manner that business users can

understand. Modelers import the metadata from one or more databases, and then add to the model to meet user

requirements.

2. The modeler then publishes and updates packages to Cognos Connection so that authors can use them to create

reports.

3. Business users and report authors use the published packages to understand their business data.

4. Users run, view, and manage their content in Cognos Connection. Depending on their security permissions, they

may be able to simply run and view reports or manage schedules, portal layout, and other users permissions.

For more information, see the IBM Cognos 8 Architecture and Deployment Guide.




34/94

Models and Packages

Because stored data is typically designed for storage and not for reporting, a data modeler uses

Framework Manager to create metadata models. A model structures, adds to, and manages data

in ways that make sense to business users. For example, a model defines

business rules

data descriptions

data relationships

business dimensions and hierarchies

other administrative tasks

Modelers use a defined metadata model to create a package to make metadata available to report

authors. Each package must contain all the information that a specific user or group of users needs

to create reports. For example, one package can contain human resources data, and another sales

data. When users open an authoring studio, they must select which package to use. Each reportcan contain data from only one package.

Planning and creating a model is an important task that should be performed by a modeler or a

modeling team familiar with both the database structure and the needs of the business users.

For information about data modeling, see the online help in Framework Manager.

Reports

When authors create a report, they are actually creating a report specification. The report specific-

ation is an XML representation of the queries and prompts that retrieve data, as well as the layouts

and styles used to present the data. For simplicity, the report specification is called the report.

Report specifications can be useful to report authors for troubleshooting.

For information about working with report specifications, see the online help in Report Studio.

Samples

Sample reports, models, and packages are available for Developer Edition. To understand the

modeling and packaging process, users can study the sample models, packages, and reports.

The samples must be downloaded, installed, and set up for the databases you have installed.

Viewing and Organizing Content

When you view and run a report the information that you see comes from data sources, the package,

calculations, other properties added by the author, and from the product itself.

You use IBM Cognos Connection to organize your reports and other content such as URLs, and

folders. You can access public content on the Public Folders tab or custom portal pages, and store

and access your favorite content on the My Folders tab.

For more information about viewing and organizing content, see the online help in IBM Cognos

Connection.

34



35/94

Report Views

If you want to personalize an existing public report, you can create a report and save the view on

the My Folders tab. This allows you to save prompt values, modify the schedule, and change the

output format of reports.

Report Outputs

When a report is run, it contains the latest data from the data source. However, viewing the most

recent data may not always meet your needs. When you want to view older data, save and view

the report output.

Report outputs are created when you schedule a report, when a report has multiple formats or

languages, when a report has a delivery method of save, print, or email, and when a report is burst.

You can produce report outputs in the following formats:

HTML

PDF

Excel

delimited text (CSV)

XML

If you are the owner of a report or have the necessary permissions, you can specify the default

format for each report. You can also specify how many report output versions to keep.

Drill-through Links

A report can contain drill-through links, also known as Go To links, so that you can easily openrelated content. A value in the report is linked to more detailed information in another report. For

example, a report includes sales information for each continent. When you click a continent name,

a more detailed report about sales for that specific continent opens.

When you view report data in IBM Cognos Connection and Query Studio, you can also drill down

and drill up. When you drill down, you follow a link from one layer of data to a more detailed

layer within the same report. When you drill up, you access a less detailed layer.

Multilingual User Interface and Content

The product is a multilingual suite that lets you author reports once and deploy them globally.When users open a report, it automatically opens in the proper language, based on their locale set-

tings.

You can select the language that you prefer for the user interface. If your data and reports are

available in multiple languages, you can also select the language that you prefer for the content.

To deliver multilingual content, you can create each entry with multilingual properties in the

appropriate studio.




36/94

Portal Pages

In IBM Cognos Connection, you can create your own custom portal pages. You use these portal

pages to view frequently-used content, to group related reports and folders, and to combine content

within a single page. Within your portal pages, you can add portlets, which you use to view and

interact with your content.

If you have the necessary permissions, you can create public pages that other users and groups canaccess and even use as their own. You can assign security permissions to allow only certain users

to access the pages.

Content Store

The installation creates and initializes the content store. The content store is an instance of an

Apache Derby database. It contains the data that the IBM Cognos 8 components need to operate,

such as report specifications, published models, and the packages that contain them; connection

information for data sources; information about the authentication namespace, and the Cognos

namespace for user access; and information about scheduling and bursting reports.

Design models and log files are not stored in the content store.

Administration

Administrators ensure that the product runs smoothly and at its optimum performance. They can

define connections to data sources

define security permissions for users and groups in the organization

specify distribution lists, contacts, and printers

manage servers and dispatchers and fine-tune the performance

pre-define links for an entire package that authors can then easily add to their reports

Security

The Developer Edition is secured by setting permissions and user authentication. Anonymous access

is disabled. Users must provide a username and password when logging on.

Administrators define permissions so that users can access functionality. For example, to edit a

report using Report Studio, you must have the appropriate security permissions.

In addition, each entry in IBM Cognos Connection is secured to define who can read, edit, and runthe entry.

You use the Developer Edition Manager to maintain the five named users allowed to use the product.

This authentication provider is referred to as a namespace.

Scheduling Content

You can schedule most content that appears in Cognos Connection to run at a time that is convenient

for you. For example, you can schedule reports and deployments.

You can also create jobs to schedule multiple entries together.

36



37/94

How is the Developer Edition Different from IBM Cognos 8

BI?The Developer Edition delivers a subset of the capabilities that are available in IBM Cognos 8.

It also provides some differences, such as an integrated installation, preconfigured settings, and

simplified user management.

Integrated Installation

The installation program for the Developer Edition installs all of the components that you need for

a reporting solution on a single Windows server. The components include Report Studio, Analysis

Studio, Query Studio, Event Studio, Framework Manager, and IBM Cognos Connection.

Preconfigured Settings

Preconfigured settings makes the installation of Developer Edition easy, allowing you to start using

the tools quickly. The product is configured to run using Apache Tomcat application server and

an instance of an Apache Derby database as the content store. Automatic configuration helps to

reduce any possible confusion regarding startup options. In addition, sample models and reports

are available to be installed allowing you to start to explore product features without the need to

set up corporate data.

Simplified User Management

In the Developer Edition, user management is simple. Anonymous access is disabled, and five named

users are allowed to access the BI capabilities provided by the software. User and password security

administration is managed by the Developer Edition Manager.

Building an ApplicationTo help you learn the features in IBM Cognos 8 BI Developer Edition, use the samples to guide

you through the process of building an application. The samples are an introduction to key concepts

you need to understand how to model your data, create reports, and query the reports.

For more information to help you become familiar with business intelligence capabilities, see the

online help in the IBM Cognos Administration console.

Before you get started building an application, you will need to setup your environment (p. 7).

We also recommend that you download and install the product samples, and then review the dis-cussion about the samples.

The following checklist guides you through a high level view of the different functional areas and

roles involved in building an application.

Locate and prepare data sources and models (p. 38).




38/94

The Developer Edition reports from one or more data sources. Database connections are created

in the web administration interface, and are used for modeling, for authoring and for running

the application.

To use data for authoring and viewing, the business intelligence studios need a subset of a

model of the metadata (called a package). The metadata may need extensive modeling in

Framework Manager.

Build and publish the content (p. 48).

Reports and so on are created in the business intelligence studios. The studio you use depends

on the content, lifespan and audience of the report. For example, use Query Studio for self-

service reporting, and use Report Studio for scheduled reports. Report Studio reports are usually

prepared for a wider audience, published to IBM Cognos Connection, and scheduled there for

bursting, distribution, and so on. You can also use Report Studio to prepare templates for self-

service reporting. For more information, see "Creating Your Own Report Templates" (p. 51).

Deliver and view the information (p. 66).

You deliver content from the portal, and view information that has been saved, or delivered

by other mechanisms. You can also run reports from within the business intelligence studio in

which they were created.

Designing the Model

Creating an application begins with designing a model.

Framework Manager is a metadata modeling tool that drives query generation. A model is a collec-

tion of metadata that includes physical information and business information for one or more data

sources. When you add security and multilingual capabilities, one model can serve the reportingand ad hoc querying of many groups of users around the globe.

Additional Information

For information about using Framework Manager, see the online help.

Prerequisites

To get started with modeling, we recommend that you thoroughly understand the reporting problem

that you want to solve. As part of this analysis you must also know what data is available to solve

the problem, and whether the data source contains the data and metadata that you need.

You should also become familiar with Framework Manager before you start modeling. Learn about

the objects you will use in a project (p. 39). Try to create a simple project, or open the sample

project. Explore the panes and menu commands in the user interface.

The Process for Creating Models

Follow these steps to create a model:

Create a data source connection.

You must create data source connections to the databases that hold your data. The product

uses this information to connect to the database and retrieve metadata and data.

38



39/94

Create a project.

In Framework Manager, you work in the context of a project. The Framework Manager project

contains objects that you organize for your users according to the business model and business

rules of your organization. You view these objects in the project page.

Import metadata.

Include all data-source query subjects required to access the data. You can create one or more

of these namespaces for all tables in your data mart or data warehouse.

Review relationships in the data view.

Confirm the relationships and ensure cardinality rules are appropriate. Framework Manager

uses cardinality rules to generate the appropriate SQL statements. Verify all relationships to

ensure that reporting and analysis needs are met.

Verify the usage, aggregation rules and format properties for the query items, and modify them

as necessary.

Set the Usage and Regular Aggregate properties to reflect the intended use of the query item.

Format the query items to control how data appears in a report.

Create business rules and definitions.

Rename query subjects and column names with business names, and use folders and namespaces

to organize the data. Create model objects to represent the data in terms of the business or

application needs.

Resolve the multilingual data by adding a parameter map and creating filters and calculations

to retrieve the data in the locale language.

Create presentation views using shortcuts.

A business-oriented presentation view will be helpful for navigation. Create star schema

groupings using shortcuts to the model query subjects from the business view.

Use the Model Advisor.

After finding and fixing errors, use the Model Advisor to analyze the metadata in the model.

The Model Advisor applies rules based on current modeling guidelines and identifies areas of

the model that you need to examine.

Create a package for each functional area.

This ensures that the package stays as concise as possible, and also limits the requirement for

regression testing.

Publish packages.

Always validate the model before publishing.

Working with Objects in Framework Manager

When you work in Framework Manager, you work with a number of objects that are contained

in a project.




40/94

Projects

A project contains a model, namespaces, packages, data sources, and related information for

maintaining and sharing model information. A single project can span many data sources or tables.

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 project

and its associated files are contained in a project folder.

Models

A model is the set of related dimensions, query subjects, and other objects required for one or more

related reporting applications.

A model provides a business view of the information in the source data to simplify building reports

and queries. The business view can

organize items in folders that represent business areas for reporting

format items using numeric, currency, date, time, and other formats

present multilingual folder and item names, descriptions, tips, and data so that users can

operate in their language of choice

Namespaces

A namespace uniquely identifies query items, dimensions, query subjects and other objects. You

import different databases into separate namespace to avoid duplicate names.

Packages

A package is a subset of the dimensions, query subjects, and other objects defined in the project. Apackage is what is actually published to the portal, and it is used to create reports and ad hoc

queries.

Dimensions

A dimension is a broad grouping of data about a major aspect of a business, such as products,

dates, or markets.

Query Subjects

A query subject is a set ofquery items that have an inherent relationship.

In most cases, query subjects behave like tables. Query subjects produce the same set of rows

regardless of which columns were queried.

Query Items

A query item is the smallest piece of the model that can be placed in a report. It represents a single

characteristic of something, such as the date that a product was introduced.

Query items are contained in query subjects or dimensions. For example, a query subject that refer-

ences an entire table contains query items that represent each column in the table.

For your users, query items are the most important objects for creating reports. They use queryitem properties of query items to build their reports.

40



41/94

Parameter Maps

Use parameters to create conditional query subjects that allow for substitutions when the report is

run. Parameter maps are objects that store key-value pairs. Parameter maps are similar to data

source look-up tables. Each parameter map has two columns, one for the key and one for the value

that the key represents. You can manually enter the keys and values, import them from a file, or

base them on existing query items in the model.

Example - The GO Data Warehouse Model

The GO Data Warehouse model, great_outdoors_warehouse.cpf, is based on the database GOS-

ALESDW.

The GO Data Warehouse model is a collection of metadata that includes physical information and

business information about human resources, sales and marketing, and finance, grouped into

business areas.

In this exercise you will learn some of the modeling techniques that were used to create the GO

Data Warehouse model.You are a data modeler in the Great Outdoors Company. You create the models and packages on

which performance management reports are based.

Things to Notice

In the Database view, the three business areas are grouped into separate namespaces. The

Database view contains a fourth namespace (GO Data) for the common information.

The Business view contains only model query subjects, with no joins.

Calculations were added to the model query subjects. For example, the time dimension contains

language calculations.

The Dimensional view contains regular dimensions, measure dimensions, and scope relationships

that were created in Framework Manager.

The Analysis view contains the part of the model that is visible in the studios for the analysis

(dimensional) package

Shortcuts to the regular and measure dimensions in the Dimensional view are grouped in star

schemas and placed in the root of the model in folders, one for each business area. They are

clearly marked with "(analysis)" at the end of the name. They are not in a separate namespace

because that would add another level in the metadata tree in the studios.

The Query view contains the part of the model that is visible in the studios for the query and

reporting package.

Shortcuts to the model query subjects in the Dimensional view are grouped in star schemas and

are placed in folders, one for each business area. They are clearly marked with "(query)" at

the end of the name in the root of the model.




42/94


each hierarchy.

Steps

1. From the Start menu, click Programs, IBM Cognos 8 BI Developer Edition, IBM Cognos

Framework Manager.

2. From the Welcome page, click Open a project.

3. Go to the c8_location\webcontent\samples\Models\great_outdoors_warehouse and click great_

outdoors_warehouse.cpf.

4. Click OK.

5. Click Finish.

The project page appears. The project page is where you design, package, and publish project

metadata. The Project Viewer shows the objects in a project in a hierarchical view. You can

use the Project Viewer to view, modify, and create objects.

6. In the Project Viewer, expand go_data_warehouse, and expand Database View.

The Database view is very similar to the structure of the underlying database. All tables (data

source query subjects) are unchanged. This enables the product to retrieve metadata directly

from the package in most cases, instead of using a metadata call to the database. The following

changes and additions have been made in the Database view:

Joins have been added as necessary.

To allow for aggregation at different levels of granularity, some model query subjects havebeen created. For example, see the relationships between Time and Sales or Sales fact.

To allow single joins to be made between the lookup tables and each level in a dimension,

lookup tables have been copied. For example, see the Products look up tables.

7. In the Project Viewer, expand Business View.

The following changes and additions have been made in the Business view:

Calculations were added to the model query subjects. For example, the time dimension

contains language calculations.


each hierarchy. For example, see the employee hierarchies, where employees are organized

by manager, organization, region, and position.

8. In the Project Viewer, expand Dimensional View.

This view contains regular dimensions, measure dimensions, and scope relationships that were

created in Framework Manager.

9. In the Project Viewer, notice that the analysis view contains the part of the model, such as HR

(analysis) that is visible in the studios for the a