IBM® Cognos® 8 Business Intelligence Readme - IIS Windows Server

IBM® Cognos® 8 Business Intelligence

README

Product InformationThis document applies to IBM® Cognos® 8 Version 8.4 and may also apply to subsequent releases. To check for newer versions of this document,visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html).

CopyrightCopyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company.Portions of Cognos ULC software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2;6,995,768 B2; 7,062,479 B2; 7,072,822 B2; 7,111,007 B2; 7,130,822 B1; 7,155,398 B2; 7,171,425 B2; 7,185,016 B1; 7,213,199 B2; 7,243,106B2; 7,257,612 B2; 7,275,211 B2; 7,281,047 B2; 7,293,008 B2; 7,296,040 B2; 7,318,058 B2; 7,325,003 B2; 7,333,995 B2.Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBMand the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries or both. Java andall Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product,or service names may be trademarks or service marks of others.While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors ortechnical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information containedin this document.This document shows the publication date. The information contained in this document is subject to change without notice. Any improvementsor changes to the information contained in this document will be documented in subsequent editions.U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or dis-closure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer clause atDFARS 252.227-7013, or subparagraphs (C)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227 as applicable.The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.This document contains proprietary information of Cognos. All rights are reserved. No part of this document may be copied, photocopied,reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the priorwritten consent of Cognos.

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

Table of Contents

Chapter 1: IBM Cognos 8 Known Issues 5Review the Readme Updates 5Review the Fix List 5Installation and Configuration Issues 5

Installing IBM Cognos 8 Components in a 64-bit System 5Using a DB2 Database for the Content Store on 64-bit Systems 6Distributing Components for IBM Cognos Metrics Manager on a 64-bit System 7Importing a Large Deployment in Windows Crashes the Java Virtual Machine 7Cannot Start IBM Cognos Configuration on Red Hat 5 Linux 8

Administration Issues 8CNC-ASV-0007 Error When Calling a Report Trigger From a Web Service Task 8Cognos Metrics Manager Portlets Must Use the Default Channel to Communicate with a

Cognos Viewer Portlet 9Sybase Adaptive Server Enterprise Data Sources 9Incorrect Location of the system.xml File 10

Security Issues 10Securing Cognos PowerCubes 10

Issues Affecting Multiple Components 11Currency, Units of Measure, and Formatting Not Supported by IBM InfoSphere Warehouse

Cubing Services 11Potential Issue Using Informix 11.5 Tables Created with the VERCOLS Option 11Changes to Decimals in Currency Formats 11Adobe Reader Displays Corrupted Characters in the Bookmarks Pane 12Limited Security with TM1 Data Sources 12Unexpected Results When Using Aggregation with TM1 Data Sources 13Cannot Load the Metadata Tree for a Series 7 PowerCube in Internet Explorer 7 13Filters Are Not Correct When Users Drill Through to Upgraded Targets in Analysis Stu-

dio 14Drill-through Support for TM1 Cubes and IBM Infosphere Warehouse Cubing Services 14

Framework Manager Issues 15Chinese "GB18030" characters may be displayed as question marks on message log after

a Framework Manager model export to CWM format 15Deprecation of Native Support for VSS and CVS Repositories 15Cannot Test a Self-referencing Expression for a SAP Data Sources 15

Transformer Issues 15Publish a PowerCube 15

Go! Office Issues 16Analysis Studio Issues 16Event Studio Issues 16Metric Designer Issues 16

CCLAssert Message Encountered When Running an Extract Against an SAP Data Source 16Report From OLAP Data Source Is Not Displayed and Error Processing Template Is

Encountered 16

Readme 3

No Rollups Are Generated for Some Calculated Measures in an SAP Info Query DataSource 16

Metric Studio Issues 17Query Studio Issues 17Report Studio Issues 17

Unexpected Results Resolved for Intersections of Calculated Measures and Aggregation 17Series 7 Integration Issues 17

Chapter 2: Deprecation Notices 19Supported Environments 19Framework Manager Security Filters for SAP BW: Notice of Intent to Change the Default Set-

ting 19IQD Externalize Method 20IBM Cognos 8 PowerCube Connection Utility and cubeswap 20Cognos Viewer URL API (b_action=xts.run) 21

Index 23

4

Table of Contents

Chapter 1: IBM Cognos 8 Known Issues

This Readme contains late-breaking information about known issues, including installation issues,

limitations, and deprecation notices.

The documentation included in this release is current as of October 2008.

Review the Readme UpdatesThe Readme Updates document contains issues that arise after the product is released. We recommend

that you review the Readme Updates.

Steps

1. Go to the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_

crc.html).

2. Click Documentation.

3. Navigate to the Readme Updates for your product.

Review the Fix ListThe fix list is a list of the known issues that were addressed in this release. We recommend that you

review the fix list.

Steps

1. Go to the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_

crc.html).

2. Click Documentation, then click Troubleshoot.

3. Navigate to the fix list for your product.

Installation and Configuration IssuesThis section contains known issues about installation and configuration.

Installing IBM Cognos 8 Components in a 64-bit SystemSome IBM Cognos 8 components are available for 64-bit systems. When installing on a 64-bit system,

the components must be installed in the appropriate directories.

The default installation directory that is used by the IBM Cognos 8 components depends on the

the version that you install. Whether you are installing all server components together on a single

server or on multiple servers, 32-bit and 64-bit components must be in separate directories. For

Readme 5





32-bit installations, the default installation directory is C:\Program Files\cognos\c8. For 64-bit

installations, the default installation directory is C:\Program Files\cognos\c8_64.

Server Components That Must Be Installed in the 64-bit Directory

The following components can be installed together on one 64-bit server or installed separately on

multiple 64-bit servers. When installing the components, ensure that you start from the appropriate

directory and disk:

● IBM Cognos 8 BI Server (Content Manager, Application Tier Components, Gateway)

● IBM Cognos 8 Supplementary Languages Documentation (32-bit and 64-bit versions available

on one disk)

● IBM Cognos 8 BI Samples (32-bit and 64-bit versions available on one disk)

Server Components That Must Be Installed in the 32-bit Directory

The following components can be installed together on the 64-bit server, but in a separate directory

from the 64-bit components. They can also be installed on a separate 32-bit system:

● IBM Cognos 8 Metrics Manager (Content Manager, Application Tier Components, Gateway)

● IBM Cognos 8 Transformer (UNIX and Linux utility for building PowerCubes)

● IBM Cognos 8 Go! Dashboard

● IBM Cognos 8 Go! Search

● IBM Virtual View Manager

Client Components That Must Be Installed on a 32-bit Windows Computer

The following client components must be installed on a 32-bit Windows computer:

● Framework Manager

● Metric Designer

● IBM Cognos 8 Go! Office

● IBM Cognos 8 Transformer (Windows modeling tool)

610051

Using a DB2 Database for the Content Store on 64-bit SystemsWhen you install IBM Cognos 8 BI components in a 64-bit system, you must ensure that the correct

libraries are being used and that components can communicate.

Creating a DB2 Content Store Database

When running in a 64-bit application server and using a DB2 database for the content store, IBM

Cognos 8 requires 64-bit library files. You must ensure that the 64-bit library files are listed first

so that IBM Cognos 8 can find them. If you use DB2 version 9.5, the 64-bit library files should

already be set in your environment variables.

6


Connectivity to a DB2 Content Store Database

On the Content Manager computer, ensure that the 64-bit DB2 libraries are in the library search

path, which is usually the $DB2DIR/lib64 directory.

Distributing Components for IBM Cognos Metrics Manager on a 64-bit SystemIBM Cognos Metrics Manager can be installed as a standalone scorecarding product or it can share

resources with IBM Cognos 8 BI Server. This section includes the list of tasks that are required to

distribute IBM Cognos Metrics Manager components on a 64-bit system in both situations.

For information about installing and configuring components, see the Installation and ConfigurationGuide.

Operating as a Standalone Product

To use IBM Cognos Metrics Manager as a standalone product on a 64-bit system, install all com-

ponents and configure as you normally would, pointing to the 32-bit libraries in the library path

environment variables for the content store and metric store. If there are other IBM Cognos 8 BI

products on the system, ensure that you install IBM Cognos Metrics Manager in a separate directory

and configure it to use a different content store, aliases, and ports.

Sharing Resources with IBM Cognos 8 BI Server

To share resources, such as the content store, between IBM Cognos Metrics Manager and IBM

Cognos 8 BI Server, you must install 32-bit and 64-bit components in separate directories or on

separate computers. For the content store, point to the 64-bit libraries in the library path environment

variables. For the metric store, point to the 32-bit libraries in the library path environment variables.

The following list shows an example of distributing components using a 64-bit server, A, and a 32-

bit server, B. Other tasks, such as creating a content store, metric store, installing database clients,

setting up environment variables, and configuring the Web server are not listed. For information,

see the Installation and Configuration Guide.

1. On Server A, install the 64-bit versions of Content Manager and Application Tier Components

from IBM Cognos 8 BI Server.

2. On Server A, in IBM Cognos Configuration, configure the Gateway URI to point to Server B.

3. On Server B, install the 32-bit version of Gateway from IBM Cognos 8 BI Server.

4. On Server B, install Application Tier Components and Gateway from IBM Cognos Metrics

Manager.

Ensure that the Gateway is in the same directory as the Gateway from IBM Cognos 8 BI Server.

5. On Server B, in IBM Cognos Configuration, configure the Content Manager URIs to point to

Server A.

Importing a Large Deployment in Windows Crashes the Java Virtual MachineThe Java virtual machine under Windows crashes under the following circumstances.

1. The maximum Java memory setting is Medium (1152MB) or higher.

Readme 7


2. You are importing a large archive from a previous release of IBM Cognos 8.

3. The archive contains large models that require upgrading.

To resolve this issue, set the maximum Java memory setting to Small (768MB).576426

Cannot Start IBM Cognos Configuration on Red Hat 5 LinuxYou are using IBM Java on Red Hat 5 Linux and while running the ./cogconfig.sh command, the

following error message appears:

Exception in thread "main" java.lang.UnsatisfiedLinkError: /<path>/<java_path>/jre/bin/xawt/

libmawt.so (/usr/libXft.so.2:undefined symbol: FT_ClyphSlot_Embolden)

The versions of Freetype that are used by IBM Cognos 8 and Red Hat 5 are not compatible. To

resolve the problem, you must add the LD_PRELOAD environment variable on your Red Hat 5

Linux system.

Step

● Set the environment variable by using the following command:

● On 32-bit systems, type

setenv LD_PRELOAD /usr/lib/libfreetype.so

● On 64-bit systems, type

setenv LD_PRELOAD /usr/lib64/libfreetype.so

598110

Administration IssuesThis section contains known issues about administration.

CNC-ASV-0007 Error When Calling a Report Trigger From a Web Service TaskWhen calling a report trigger from a Web service task, the following error message may appear:

CNC-ASV-0007 An error occurred with the agent Web service task. The operation failed. org.

apache.wsif.WSIFException: CloneNotSupportedException cloning context.

This problem is related to the replacement of the Sun Java Runtime Environment (JRE) by IBM

Java Runtime Environment (JRE) in this release of IBM Cognos 8.

To avoid this problem, modify the bootstrap_win32.xml file in the c8_location\bin directory by

adding the following line of code for the spawn element under <process name="catalina"> :

<param condName="${java_vendor}" condValue="IBM">-Xss128m</param>

607436

8


CognosMetricsManager Portlets Must Use the Default Channel to Communicatewith a Cognos Viewer Portlet

When your page or a dashboard in Cognos Connection contains Cognos Viewer and any of the

Cognos Metrics Manager portlets, you can use only the default channel to enable communication

between the Cognos Metrics Manager portlets and the Cognos Viewer portlet. If a channel name

is specified, the Cognos Metrics Manager portlets will not update the Cognos Viewer portlet.

Portlet to portlet communication between any of the Cognos Metrics Manager portlets can use

either the default channel, or a specific channel.601989

Sybase Adaptive Server Enterprise Data SourcesThe information in this topic is an addition to the Data Sources chapter in the IBM Cognos 8

Administration and Security Guide.

IBM Cognos 8 supports the following Sybase Adaptive Server Enterprise data sources:

● CT-Lib

● CT-15

Sybase Adaptive Server Enterprise Connection Parameters

You specify connection parameters when you create a data source or modify a data source connec-

tion. For more information, see the IBM Cognos 8 Administration and Security Guide.

● Server name

Enter the name of the server.

● Database name

Select Master if you want the Sybase server to determine the default database. To override the

default, enter a valid database name.

● Application name

Enter the application name. If you leave this blank, the default is the name of the Cognos

executable, for example, BiBustkservermain or DataBuild.

● Collation sequence

Enter the collation sequence to be included in the database connection string. Collation sequences

are required only in rare cases where there may be sorting discrepancies between IBM Cognos 8

and a database. We recommend that you contact customer support before using a collation

sequence.

● Packet size

Enter the packet size. For CT-Lib, the default is 512. For CT-15, the default is 2048. Increase

the packet size to reduce the number of packets that must be sent. Decrease the packet size if

larger packet size is an issue. The size that you can request can not be larger than the Sybase

server allows. Contact your database administrator for more information.

Readme 9


● Asynchronous levels

Select the asynchronous level.

● Polling time slice

Enter the polling time slice. The default is 100.

● Timeouts

Specify the time in seconds within which you want the database to connect or wait for your

reply before timing out. Valid entries are zero to 32,767. To have the database wait indefinitely,

enter zero, which is the default.

● Signon

For more information on signon, see the IBM Cognos 8 Administration and Security Guide.

If a user ID or password are required in the connection string, select the User ID check box.

If a password is required, select the Password check box and enter the password in the Password

and Confirm password boxes.

To create a user ID and password that automatically connects to the data source, select Create

a signon that the Everyone group can use. Enter the User ID and then enter the password in

the Password and Confirm password boxes.

Incorrect Location of the system.xml FileThe following topics in the IBM Cognos 8 Administration and Security Guide specify incorrect

location of the referenced system.xml file:

● Allow User Access to Series 7 Reports from IBM Cognos Connection

● Restrict Content Browsing

The correct location is c8_location\templates\ps.606810

Security IssuesThis section contains known issues about security.

Securing Cognos PowerCubesThis topic in the IBM Cognos 8 Architecture and Deployment Guide does not contain complete

information about securing Cognos PowerCubes.

For information relevant to this release, see the section about adding security in the IBM Cognos 8

Transformer User Guide.

10


Issues Affecting Multiple ComponentsThis section contains general known issues. This includes issues that affect more than one IBM

Cognos 8 component, such as Query Studio and Report Studio. Issues that affect just one component

are described in the section for that component.

Currency, Units of Measure, and Formatting Not Supported by IBM InfoSphereWarehouse Cubing Services

There will be no currency symbols, units of measure, or other formatting applied when data is

returned from the cubing services technology of IBM InfoSphere Warehouse. This applies to Report

Studio, Query Studio, and Analysis Studio.

To resolve this issue, manually apply the required formatting in reports.603133

Potential Issue Using Informix 11.5 Tables Created with the VERCOLS OptionThe select * from <table> syntax does not work in IBM Cognos 8 if the referenced table was

created using the VERCOLS option.

When running a query in IBM Cognos 8, error messages similar to the following are displayed:

This query contains an error and can not be executed.

It is recommended that you view the query feedback on the Query Information tab.

RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-

3'.

UDA-SQL-0283 Metadata describing "select * from 'gosales1'.country" does not match results

from the database.

To resolve these errors, do one of the following, then re-run your query.

● If possible, create the table without the VERCOLS option.

● Specify all the required columns by name in the select statement.

Changes to Decimals in Currency FormatsWhen you open a PowerCube in an IBM Cognos 8.3 Web studio or in IBM Cognos 8 Business

Intelligence Mobile Analysis 8.3, you may notice changes in the number of default decimal places

shown in currency formats.

This behavior is due to the following changes:

● The default decimal formatting in currency formats is now determined by the measure format

selected in the cube, instead of from the data source Currency Table definition.

For example, if the Actual Revenue measure format specifies two decimal places and the USD

currency in the Currency Table specifies no decimal places, two decimal places will now be

shown in the USD currency value.

Readme 11


● Calculations that include a division operator and at least one currency operand will now show

a resulting value with three decimal places only when

● neither of the currency values includes decimals

● two currency operands have different numbers of decimal places

In all other calculations of this type, the number of decimals in the resulting value will be

determined by the number of decimals in the currency value. The following examples illustrate

this new behavior:

● $4.00 / $2.00 = $2.00

● $4 / $3.0000 = $1.3333

● $4 / $3 = $1.333

● $4.0 / $3.00 = $1.333

For more information about measure formats or currency tables, see the Transformer online help.545573, 545408, 545427, 546183

Adobe Reader Displays Corrupted Characters in the Bookmarks PaneWhen viewing documentation with Adobe Reader version 7, some extended characters (notably

the é character) display as dots (.), and the font is different from that used for the rest of the book-

marks.

To resolve this issue, upgrade your copy of Adobe Reader to version 8.

Limited Security with TM1 Data SourcesIn TM1 data sources, administrators can secure elements within a dimension so that they are visible

only to certain users. However, in IBM Cognos 8, a visible path must exist from each element to

the root of the hierarchy. It is possible to secure sub-trees of a TM1 data source hierarchy, but each

element in the sub-tree must be secured.

For example, consider the following hierarchy for Total Business Unit:

Europe

● UK

● Germany

North America

● Canada

● United States

Asia Pacific

● Australia

● Japan

12


In this example, if only the North America element is secured, leaving the Canada and United Stateselements visible to all users, the path of accessible elements is impeded. IBM Cognos 8 users may

receive messages explaining that inaccessible members were encountered.

If the entire sub-tree of North America, Canada, and United States is secured, IBM Cognos 8 will

report correctly because there is a direct, visible path from the lowest level of data in the hierarchy

to the highest level of data.

To reliably detect this situation, please install TM1 build number 9.4.00001.576.606308

Unexpected Results When Using Aggregation with TM1 Data SourcesTM1 data sources can include rule-derived cells. IBM Cognos 8 cannot identify these rule-derived

cells ahead of time, so performing an aggregation on these cells may yield unexpected results. For

example, aggregating a set containing a rule-derived value may produce unexpected results in Report

Studio and Analysis Studio.

Note: Explicit aggregation operations like sum, average, count, minimum, and maximum are not

affected.

If you are using TM1 data cubes with rule-derived cells in IBM Cognos 8, we recommend that you

install TM1 build number 9.4.00001.576, which identifies aggregation errors by marking the error

cells with dashes (--).592809.3

Cannot Load the Metadata Tree for a Series 7 PowerCube in Internet Explorer 7Using either Report Studio or Analysis studio, you cannot load the metadata tree for a Series 7

PowerCube. With Internet Explorer 7 enabled to show warnings and errors, you are waiting to be

prompted for both a Series 7 namespace and a PowerCube password. The following error is shown:

element not found

This problem may occur if you register the file shdocvw.dll after installing Internet Explorer 7.

To fix the problem, follow these steps:

Steps

1. From the Windows Start menu, click Run.

2. In the Open box, type regedit, and then click OK.

3. In the Registry Editor, go to the registry branch:

HKEY_CLASSES_ROOT\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\ 1.1

\0\win32

4. Double-click (default) and set C:\WINDOWS\system32\ieframe.dll as the value data.

5. Click OK, and then close the Registry Editor.

608677

Readme 13


Filters Are Not Correct When Users Drill Through to Upgraded Targets in AnalysisStudio

If the target of a drill-through definition is an Analysis Studio report with a drill-through filter, and

the application has been upgraded from IBM Cognos 8 version 8.3 to IBM Cognos 8 version 8.4,

then filters may not be correctly passed from the source to the target. Instead, the Analysis Studio

report appears with the authored settings unchanged, or users may be prompted to select a context.

This is true for authored drill-through definitions (created in a Report Studio report) and package

drill-through definitions (created in Cognos Connection) that use parameterized drill through.

This problem occurs because of changes in how parameters are automatically named in Analysis

Studio. To correct the problem, recreate the mapping in the drill-through definition, and save the

definition.

Steps for Authored Drill Through

1. In Report Studio, Professional Authoring, open the source report.

2. Select the report item that contains the drill-through definition.

3. From the Properties pane, open the drill-through definition (Data, Drill-Through Definitions).

4. From the Drill-Through Definitions window, open the Parameters table, and re-select the target

parameter(s).

5. Save the drill-through definition settings and then save the report.

6. Test the drill through to confirm that the problem is resolved.

For more information, see the Report Studio Professional Authoring User Guide.

Steps for Package Drill Through

1. In IBM Cognos Connection, launch Drill-through Definitions.

2. Navigate to the root of the source package, locate the drill-through definition to be updated,

and click Set Properties.

3. In the Target tab, under Parameter mapping, re-select the target parameters.

4. Save the drill-through definition.

5. Test the drill through to confirm that the problem is resolved.

For more information, see the IBM Cognos 8 BI Administration and Security Guide.607932

Drill-through Support for TM1 Cubes and IBM Infosphere Warehouse CubingServices

TM1 cubes and IBM Infosphere Warehouse Cubing Services have the same level of drill-through

support within IBM Cognos 8 as other OLAP sources.

14


Framework Manager IssuesThis section contains known issues about Framework Manager.

Chinese "GB18030" characters may be displayed as question marks on messagelog after a Framework Manager model export to CWM format

After performing a Framework Manager model export to CWM format, you may notice that some

Chinese characters in the "GB18030" encoding are displayed as question marks in the export

message log.

This is due to a known limitation of the Metadata Import/Export Bridge (MIMB) third party

component, MIMB 5.2 does not support the GB18030 characters. Support is included in more

recent metadata integration releases (6.0), which will be included in a future release of Cognos 8.599880

Deprecation of Native Support for VSS and CVS RepositoriesNative support for CVS and Visual SourceSafe repositories will be deprecated in the next release

of IBM Cognos 8 Framework Manager. If you use this feature, and still require project versioning

functionality, we recommend that you read "Using External Repository Control" in the IBM

Cognos 8 Framework ManagerUser Guide. The section explains how to maintain project versioning

outside the modeling application, and is applicable for use with all version control systems.

Cannot Test a Self-referencing Expression for a SAP Data SourcesIf an object contains a self-referencing expression, you cannot test or evaluate the object. This

applies to both regular dimensions and measure dimensions that use SAP data sources.

For example, you create a measure called "totalSales" - and you set the expression like this:

[Automobile (Original)].[Key Figures].[totalSales]

The solution is to reference the source item directly.604705

Transformer IssuesThis section contains known issues about IBM Cognos 8 Business Intelligence Transformer.

Publish a PowerCubeThis topic will include the following additions in the next version of the Transformer User Guide.

Note: A cube is locked for five minutes after you publish it using the wizard. You cannot recreate

it during that time.

The note will be added to the last step of the procedure, "Steps to Publish a PowerCube Using the

Wizard".596414

Readme 15


Go! Office IssuesThere are no known issues in IBM Cognos 8 Go! Office.

Analysis Studio IssuesThere are no known issues in Analysis Studio.

Event Studio IssuesThere are no known issues in Event Studio.

Metric Designer IssuesThis section contains known issues about Metric Designer.

CCLAssert Message EncounteredWhen Running an Extract Against an SAP DataSource

When an extract is run against an SAP data source, you encounter a CCLAssert message. This error

typically occurs if the extract is being run against a ragged hierarchy and a level filter is being used.

To resolve this issue, avoid using a filter.598823

Report From OLAP Data Source Is Not Displayed and Error Processing TemplateIs Encountered

When you drill down on a metric sourced from an OLAP data source and navigate to the report

tab, the report is not displayed. The following error is displayed:

Error processing template.

This error occurs when you execute the extract directly into staging tables from the Metric Designer

UI or by running a published extract from Cognos Connection.

Workaround: Execute the extracts to flat files and then load these files using the metrics maintenance

task Import and transfer data from files into metric store.608204

No Rollups Are Generated for Some Calculated Measures in an SAP Info QueryData Source

Metric Designer may not generate any rollups for an extract that references a calculated member

of an SAP Info Query data source. The affected measures will appear in the Framework Manager

model as having a Regular Aggregate attribute value of unknown.

There is no workaround.597596

16


Metric Studio IssuesThere are no known issues in Metric Studio.

Query Studio IssuesThere are no known issues in Query Studio.

Report Studio IssuesThis section contains known issues about Report Studio.

Unexpected Results Resolved for Intersections of Calculated Measures andAggregation

In previous versions of Report Studio, when the following conditions occurred, Report Studio

returned unexpected results:

● a calculated measure with the Rollup Aggregate Function property set to Calculated intersects

with an aggregation

● the calculated measure uses an if-then-else expression

● Report Studio solves the aggregation before the calculated measure

Report Studio now returns the correct results.609461, 595493

Series 7 Integration IssuesThere are no known issues in Series 7 integration.

Readme 17


18


Chapter 2: Deprecation Notices

This section contains information about IBM Cognos 8 BI deprecation notices.

Supported EnvironmentsThe following list describes important information related to IBM Cognos 8 supported environments:

● SAP ended mainstream maintenance support for SAP BW versions 3.1c and 3.0b in December

2006. We will continue compatible support for these versions in this IBM Cognos 8 release.

We will deprecate support for SAP BW 3.1c and 3.0b in the next major release of IBM Cognos 8.

● Informix ended support for Dynamic Server version 9.3 in April 2005. We have deprecated

support for this version in this IBM Cognos 8 release.

● Informix ended support for Dynamic Server version 9.4 in April 2006. We will continue com-

patible support for this version in this IBM Cognos 8 release. We will deprecate support for

Dynamic Server version 9.4 in the next major release of IBM Cognos 8.

● Informix ended support for Red Brick Decision Server version 6.2 in April 2006. We will con-

tinue compatible support for this version in this release. We will deprecate support for this

version in the next major release of IBM Cognos 8.

● We will discontinue support for Netscape browsers in the next major release of IBM Cognos 8.

● Sun ended support for Sun ONE Directory Server version 5 in June 2004. We will continue

compatible support for this version in this IBM Cognos 8 release. We will deprecate support

for Sun ONE Directory Server version 5 in the next major release of IBM Cognos 8.

● Support for SAP NetWeaver Portal 7.0 (SAP NetWeaver 2004s) is pending in this IBM Cognos 8

release.

● IBM ended support for DB2 V9.1 on PA-RISC. We have deprecated support for this platform

(HP PA-RISC) in this release of IBM Cognos 8 Special Edition.

nbna

Framework Manager Security Filters for SAP BW: Notice ofIntent to Change the Default Setting

In all shipped versions of IBM Cognos ReportNet and IBM Cognos 8 including IBM Cognos 8.2,

the following behavior has been enabled by default.

Multiple security filters defined within Framework Manager on metadata imported from SAP BW

sources are combined using 'AND' logic, effectively an intersection of a particular user's permissions.

This behavior is contradictory to corresponding behavior on relational data sources where similar

filters are combined using 'IN' and 'OR' (union) logic to facilitate cases where users belong to one

Readme 19

or more group and require a union of their permissions. The current default behavior for SAP BW

datasources has been determined to be a product defect and will be changed in the IBM Cognos 8.3

release to align with the behavior of relational data sources. In the IBM Cognos 8.1 Mr2 and IBM

Cognos 8.2 releases, it will be possible to get the union of filters behavior by modifying the following

switches in the qfs_config.xml configuration file. Under <provider name="OlapQueryProvider"

libraryName="oqp">, add the following new <parameter> element:

<parameter name="ORingSecurityFiltersWhenUserBelongsToMultipleGroups"value="true"/>

Effect

When multiple security filters are defined in the Data Security setting in Framework Manager for

a query subject, if a user belongs to more than one user group associated with these filters, the effect

of this switch is to perform a union of these filters instead of an intersection. For example, if a user

Joe belongs to a corporate group allowing him to see data for Asia, Europe, and America, and also

belongs to a regional group allowing him only to see data for Europe, the effect of the switch will

be to let Joe see data for Asia, Europe, and America (as compared to just Europe) when logging on

IBM Cognos 8 and authoring or running a report. Note that security filters that are based on other

security filters in the Data Security settings for a query subject continue to be intersected, just as

before, independent of whether or not the new switch is activated.

As of IBM Cognos 8.3, this behavior will become the new default for SAP BW metadata in

Framework Manager. There will be no change to the behavior of security filters applied on relational

sources. The switch will continue to be available and can be set to false by your administrator if

required to maintain existing application behavior.

IQD Externalize MethodIQDs generated by Framework Manager will continue to be supported in this IBM Cognos 8 release,

but will not be enhanced. IBM Cognos 8 Transformer will continue to support IQDs generated by

Impromptu in the next major release. IBM Cognos Enterprise Planning versions 8.1, 8.2, 8.3 and

8.4 will continue to support IQDs generated by Framework Manager. We will deprecate support

for IQDs generated by Framework Manager after end of life for these versions of IBM Cognos

Enterprise Planning.

IBM Cognos 8 PowerCube Connection Utility and cubeswapIn the next release of IBM Cognos 8 Transformer, the PowerCube Connection Utility and cubeswap

will be deprecated. The functionality provided by these utilities is no longer required when using

the automated copy and activate options on the Deployment tab of the PowerCube properties dialog

box.

For more information about the PowerCube copy and activate options, see the Transformer User

Guide.

20


Cognos Viewer URL API (b_action=xts.run)In previous releases of IBM Cognos 8, the b_action parameter specified a value of xts.run and

a number of additional parameters to support launching Cognos Viewer using a customized URL

instead of using IBM Cognos Connection. This parameter value is now deprecated and will be

removed in a future release of IBM Cognos 8. A new value, cognosViewer, is available that provides

the same functionality. Continuing to use the deprecated parameter value will still work, but may

result in reduced performance.

The xts.run value is still valid, and is not deprecated, for components other than the Cognos

Viewer, such as Report Studio and Analysis Studio.

You can map xts.run parameters to cognosViewer parameters as shown below.

xts.run parameter -> cognosViewer parameter

ui.tool -> Not applicable

ui.action (default="view") -> ui.action (default="objectDefault")

ui.object -> ui.object

ui.header -> cv.header

ui.spec -> ui.spec

run.outputFormat -> run.outputFormat

run.outputLocale -> run.outputLocale

run.prompt -> run.prompt

run.xslURL -> run.xslURL

run.outputEncapsulation -> run.outputEncapsulation

async.primaryWaitThreshold -> async.primaryWaitThreshold

async.secondaryWaitThreshold -> async.secondaryWaitThreshold

run.version -> No equivalent

ui.toolbar -> cv.toolbar

Readme 21


22


Index

Symbols64-bit installation

requirements for DB2 database as content store, 6

requirements for IBM Cognos Metrics Manager, 7

AAdobe Reader

corrupt text in bookmarks pane, 12

aggregation

with TM1 data sources, 13

Analysis Studio

troubleshooting, 13, 14

Cchanges to decimal formats, 11

Chinese GB18030 characters, 15

CNC-ASV-0007 error, 8

Cognos 8 Administration

troubleshooting, 14

configuration

workflows, 5

Content Manager

DB2 library requirements on 64-bit systems, 7

content store

requirements for DB2 library files on 64-bit sys-

tems, 6

corrupt text

Adobe Reader, 12

cubeswap, 20

Ddata sources

Sybase Adaptive Server Enterprise, 9

DB2 databases

library files for 64-bit installations, 6

decimal formats

changes, 11

deprecating

source control system, 15

documentation updates

system.xml, 10

drill-through

support for cubes, 14

Eenvironments

supported, 19

environment variables

requirement on Red Hat 5 Linux, 8

errors

CNC-ASV-0007, 8

export

CWM format, 15

externalize methods

IQD, 20

Ffix list, 5

formats

changes to decimals, 11

Framework Manager

issues, 15

security filters change for SAP BW, 19

IIBM Cognos 8 Go! Office

known issues, 16

IBM Cognos 8 PowerCube Connection Utility, 20

IBM Cognos Configuration

requirements for IBM Cognos Metrics Manager on

64-bit systems, 7

IBM Cognos Metrics Manager

installing on 64-bit systems, 7

IBM Infosphere warehouse cubing services

drill-through support, 14

inaccessible members

secured elements in TM1 data sources, 12

Informix 11.5, 11

Informix Dynamic Server

supported environments, 19

Readme 23

Informix Red Brick Decision Server


installation

workflows, 5

IQD externalize method, 20

JJava virtual machine

crashes when importing deployment, 7

Kknown issues

administration, 8

Analysis Studio, 16

Event Studio, 16

Framework Manager, 15

general, 11

IBM Cognos 8 Go! Office, 16

IBM Cognos 8 Transformer, 15

installation and configuration, 5

Metric Studio known issues, 17

Query Studio, 17

Report Studio, 17

security, 10

Series 7 integration, 17

software development kit, 16

Llibrary files

for DB2 database as content store on 64-bit sys-

tems, 6

Linux

starting IBM Cognos Configuration, 8

log file

export, 15

MMetric Designer

CCLAssert error message, 16

error processing template, 16

known issues, 16

no rollups generated, 16

report not displayed, 16

Nnative support

CVS, 15

VSS, 15

Netscape

supported browsers, 19

PPCConn utility, 20

PowerCubes

publishing, 15

securing, 10

publishing Powercubes, 15

Qquery error

Informix, 11

Rreadme updates, 5

Red Hat 5 Linux

starting IBM Cognos Configuration, 8

ReportNet 1.1 issues

Framework Manager issues, 15

Report Studio

troubleshooting, 13, 14

SSAP BW

security filter change in Framework Manager, 19


SAP data sources, 15

SAP NetWeaver Portal


securing

PowerCubes, 10

security

filter change in Framework Manager for SAP

BW, 19

secured elements in TM1 data sources, 12

self-referencing expression

testing, 15

starting IBM Cognos Configuration

on Red Hat 5 Linux, 8

Sun ONE Directory Server


24

Index


Sybase Adaptive Server Enterprise data sources, 9

system.xml

documentation updates, 10

TTM1 Cubes

drill-through support, 14

TM1 data sources

secured elements, 12

troubleshooting

Analysis Studio, 13, 14

Cognos 8 Administration, 14

Report Studio, 13, 14

Wworkflows

installation and configuration, 5

Readme 25

Index

IBM® Cognos® 8 Business Intelligence Readme - IIS Windows Server

Documents

Transcript of IBM® Cognos® 8 Business Intelligence Readme - IIS Windows Server