Cognos(R) ReportNet Readme

Cognos(R) ReportNetCognos ReportNet

README UPDATES

Cognos(R) ReportNet Readme

README UPDATES

Product Information

This document applies to Cognos(R) ReportNet Version 1.1 MR4 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos Global Customer Services Web site (http://support.cognos.com).

CopyrightCopyright (C) 2007 Cognos Incorporated.

Portions of Cognos(R) software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 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.

Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies.

While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document.

This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the 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 disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.

This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation 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 prior written consent of Cognos Incorporated.

Table of Contents

Readme Updates By Date 7Updated: May 11, 2007 7

Readme Updates - Microsoft Excel Known Issues 7Updated: July 25, 2007 7

Documentation Updates - Installation and Configuration Guide 7Updated: October 9, 2007 7

Documentation Updates - Installation and Configuration Guide 7

Cognos ReportNet 1.1 MR4 Readme 9New Features in this Release 9

Support for Microsoft SQL Server 2005 9Alternate Single Signon Configuration for the Active Directory Provider 9Enhanced Domain Authentication 10Enhanced Charting 10Restrict Display of All Users 12Optional Cascading Prompts 12Specify Report Header Positions 12Enhanced Prompting Security 12

Installation and Configuration 13Upgrading Tomcat 13Accented or Double-Byte Characters Do Not Display Correctly When Installing

ReportNet on Linux 13Authentication Providers for Linux Installations 13Source Control Systems Item is Not Available in Cognos Configuration on Linux 14

Product Limitations 14Cognos Report Studio and Query Studio 14

Known Issues - General 14RSV-SVR-0015 Error When Multiple Browser Windows Open for Same Session 14Running ReportNet Under IBM WebSphere 14PDF Not Created When a Report Table Exceeds Output Page Size 14

Known Issues - Series 7 Integration 14Publish to ReportNet Fails if a Different Format is Used to Identify the Series 7 Directory

Server 15Known Issues - Drilling Through to Cognos ReportNet from Series 7 15

Reauthentication Prompt 15Known Issues - Administration 15Known Issues - Security 15

Issues with Integrated Windows Authentication 15A Namespace Configured with LDAP SSL Is Not Available 16Error When Using the SDK Custom Authentication JDBC Provider Sample 16Problems Logging onto or Searching a Series 7 Namespace that Contains Non-ASCII

Characters 16Known Issues - Cognos Configuration 16Known Issues - Cognos Report Studio 17

Default Font for Reports 17Reusing Cached Data 17Drill-through Links Not Active in the Safari Browser 17Report is Re-executed When the Delivery Method is Changed 17CombinationType Properties Being Replaced 17

Readme Updates 3

Inconsistencies in Data Ordering 17Page Query Property 18

Known Issues - SAP BW Data Sources 18OP-ERR-0073 Error When Filtering 18Considerations When Creating Expressions 18Incorrect Units of Measure in Calculations 19Grouping Columns That Have the Count Summary 19Missing Measures in Crosstab Reports 19Maximum Rows Setting is Ignored 19BAPI Errors When Executing a Query With Many Hierarchies Using Limited Local

Processing 19PCA-ERR-0087 Error When Executing a Large Query Using Limited Local

Processing 20Custom Formatting for Empty Cells Does Not Appear in ReportNet 20Sorting Order is Different When Report Runs with Limited Local Processing and Sorts on

a Member Unique Name 20Creating Sections on Reports That Access SAP BW Data Sources 20Incorrect Values When Filtering Nested Query Items 21Inconsistent Summary Values for Semi-Additive Key Figures 21Cannot Perform Local Processing on a Query Item Whose Summarization Rule is

AVG 21Calculation Displays Incorrect Unit Format 21Summary Rows Return Incorrect Total Values 22

Known Issues - Framework Manager 22Links to Segmented Namespaces No Longer Work 22Testing Query Subjects Imported from Third-Party Data Sources 22QE-DEF-0177 Error When Using Native Data Source Functions in SQL Statements That

Return a CLOB or BLOB 22Time Data Type Imported Incorrectly 23Conflicting Data Type Error 23Unable to Connect Multiple Developers to a SourceSafe Repository 23Problems Arising When an IQD File Exported from Framework Manager Connects to

Two Databases 23Properties Not Set Correctly When Importing SAP BW Data 23Some Property Values Are Reset After Performing Update Query Subject 23

Known Issues - Microsoft Excel 24Multiple Pie Charts Fail in Excel 2007 24Signed URLs and Microsoft Excel 2000 24Displaying Text Columns Containing Numbers in Excel 2002/2003 24Displaying Images in Excel 24Unable to Open More Than One Excel Output Simultaneously 25

Known Issues - Lotus Notes 25Lotus Compatibility Mode 25

Known Issues - Third-Party Data Source Access 25IBM DB2 MVS 7.1 25

Documentation Updates - Installation and Configuration Guide 26Product Information 26Chapter 1: Upgrading from an Earlier Release 26Change the ReportNet Gateway 26Configuring the SAP Web Application Server 27Database Connectivity for the Reporting Database on Linux 29Database Connectivity for the Content Store Database on Linux 29Running Two Versions of ReportNet on the Same Computer 29

Documentation Updates - Quick Start Installation and Configuration Guide 31Supported Environments 31Update Your Java Runtime Environment on UNIX or Linux 31

Documentation Updates - Administration and Security Guide 31

4 Cognos ReportNet

Event-Based Report Scheduling 31Disable Support for Event-based Scheduling 33Set Up Trigger Events on a Server 33Schedule a Report on Last Day of Month 34Permissions to Create a Report View 35Incorrect Parameter Value 35Transferring the ReportNet Passport ID as a URL Parameter 35Install the Cognos Business Package 36Setting Up Oracle Proxy Connections and Virtual Private Databases 36Logging Level 5 37

Documentation Updates - Cognos Report Studio User Guide 38Specifying the Number of Decimals 39

Documentation Updates - Cognos Report Studio User Guide and ReportNet User Guide 39Excel Formats and SSL 39

Documentation Updates - Query Studio User Guide 39View a Report in Excel Format 39

Documentation Updates - ReportNet User Guide 40Print a Report 40Event-Based Report Scheduling 40

Documentation Updates - SAP BW Data Sources 42Documentation Updates - Framework Manager User Guide 42

Preserve Business Names when Importing Objects from DB2 CubeViews 42Rollup Processing Property 42The Externalize Auto Summary Property 43Changes to OLAP Function Names 43Externalizing SAP BW Query Subjects 43

Documentation Updates - Troubleshooting Guide 47ArrayIndexOutOfBoundsException Error When Running a Report 47Locale Mismatch in Cognos Navigator Portlet 48

Index 49

Readme Updates 5

6 Cognos ReportNet

Readme Updates By Date

This section contains cross references to known issues and documentation updates that were discovered after the last release.

Updated: May 11, 2007The following readme updates and documentation updates were added on May 11, 2007.

Readme Updates - Microsoft Excel Known Issues• "Multiple Pie Charts Fail in Excel 2007" (p. 24)

Updated: July 25, 2007The following readme updates and documentation updates were added on July 25, 2007.

Documentation Updates - Installation and Configuration Guide• "Change the ReportNet Gateway" (p. 26)

Updated: October 9, 2007The following readme updates and documentation updates were added on October 9, 2007.

Documentation Updates - Installation and Configuration Guide• "Product Information" (p. 26)• "Chapter 1: Upgrading from an Earlier Release" (p. 26)

Readme Updates 7

Readme Updates By Date

8 Cognos ReportNet

Cognos ReportNet 1.1 MR4 Readme

This Readme contains late-breaking information, including installation issues, limitations, and known issues.

The documentation included in this release is current as of April 30, 2007.

To view a complete list of environments currently supported by Cognos products, such as operating systems, patches, browsers, Web servers, directory servers, and database servers, visit the Cognos support website (http://support.cognos.com).

New Features in this ReleaseThere are no new features in ReportNet version 1.1 MR4. Please see the Cognos support website http://support.cognos.com for updated conformance information.

ReportNet version 1.1 MR4 includes all features from the previous MR3 release. The following is information about features that were introduced in MR3.

Support for Microsoft SQL Server 2005With this release, ReportNet supports Microsoft SQL Server 2005. You can use Microsoft SQL Server 2005 for both the Content Store and as a data source.

Alternate Single Signon Configuration for the Active Directory ProviderYou can now configure single signon between a ReportNet Active Directory authentication namespace and the Active Directory Server by enabling External Identity Mapping as opposed to Kerberos delegation.

By default, the Active Directory provider uses Kerberos delegation and integrates with the IIS Web server for single signon if Integrated Authenticated (formerly named NT Challenge Response) is enabled on the IIS Web server.

If Integrated Authenticated is enabled, you are not prompted to reenter authentication information when accessing Cognos content that is secured by the Active Directory namespace.

If you do not want Kerberos delegation, the provider can be configured to access the environment variable REMOTE_USER to achieve single signon. You must set the advanced property singleSignonOption to the value IdentityMapping. Microsoft sets REMOTE_USER by default when you enable Windows Integrated Authentication.

Steps for Single Signon Using REMOTE_USER1. On every computer where you installed Content Manager, open Cognos Configuration.2. In the Explorer window, under Security, Authentication, click the Active Directory

namespace.3. Click in the Value column for Advanced properties and then click the edit button.4. In the Value - Advanced properties window, click Add.5. In the Name column, type singleSignonOption.6. In the Value column, type IdentityMapping.7. Click OK.

The Active Directory provider now uses REMOTE_USER for single signon.If you want to switch back to Kerberos delegation, edit Advanced properties and, in the Value column, type

Readme Updates 9

http://support.cognos.com



KerberosAuthentication

Enhanced Domain AuthenticationWith this release, you can now specify an extended set of domains for log in authentication.

When you configure an authentication namespace for ReportNet, users from only one domain can log in. By using the Advanced properties for Active Directory Server, users from related (parent-child) domains and unrelated domain trees within the same forest can also log in.

Authentication in One Domain Tree

If you set a parameter named chaseReferrals to true, users in the original authenticated domain and all child domains of the domain tree can log in to ReportNet. Users above the original authenticated domain or in a different domain tree cannot log in.

Authentication in All Domain Trees in the Forest

If you set a parameter named MultiDomainTrees to true, users in all domain trees in the forest can log in to ReportNet.

Steps1. On every computer where you installed Content Manager, open Cognos Configuration.2. In the Explorer window, under Security, Authentication, click the Active Directory

namespace.3. In the Properties window, specify the Host and port property:

• For users in one domain, specify the host and port of a domain controller for the single domain.

• For users in one domain tree, specify the host and port of the top-level controller for the domain tree.

• For users in all domain trees in the forest, specify the host and port of any domain controller in the forest.

4. Click in the Value column for Advanced properties and click the edit button.5. In the Value - Advanced properties window, click Add.6. Specify two new properties, chaseReferrals and MultiDomainTrees, with the following

values:

7. Click OK.8. From the File menu, click Save.

Enhanced ChartingThis release of ReportNet includes several enhancements to the charting function.

Repeating Chart Palette Assignment

By default, ReportNet assigns the same palette colors to chart series across all charts. Where you have series values that do not appear consistently in all chart instances, and where the number of chart values exceeds the available palette colors, this behavior may not give you the best representation of the data.

Authentication for chaseReferrals MultiDomainTrees

One domain False False

One domain tree True False

All domain trees in the forest

True True

10 Cognos ReportNet


For example, a report of customer investment performance results in a chart for each customer. Each customer has between five and ten investments and there are hundreds of investments. There are 16 colors in the default palette, and ReportNet re-uses the colors when assigning colors to chart values in the series. In the report, a customer chart could include two investments with the same color assigned, reducing the usability of the report.

In this release of ReportNet, you can control the palette assignment for repeating charts by assigning colors to a chart, rather than to the chart values in the series. For instances such as the example given above, this can maximize the readability of the charts in your report.

Note: Plotting more series values than there are colors in the palette will always result in duplicate colors. Use of this charting feature enhances cases where there are fewer series values in each chart instance than there are colors in the palette (the default palette has 16 colors).

Steps1. Open Cognos Connection.2. Form the Tools menu, click Server Administration.3. Click Services.4. Click BatchReportService and ReportService in the list.5. Click Stop to stop the services.6. For each service do the following

• Click Set properties• Click the Settings tab• Click Edit for the Advanced settings entry• In the Parameter entry, type

RSVP.CHARTS.ALTERNATECOLOURSNote: Ensure that there are no leading or trailing spaces.

• In the Value entry, typeTrueNote: Ensure that there are no leading or trailing spaces.

• Click OK twice.7. Click BatchReportService and ReportService in the list.8. Click Start.

Note: In a distributed installation, you must apply these settings for each report server on each computer.

Calculated Axis Minimum Value

In ReportNet, the minimum value for a chart axis is set to zero by default. In charts with very large data values, this may not result in the best possible representation of the data.

In this release, you can now set the chart axis minimum value as a calculation based on the lowest data value rather than the default zero value. ReportNet calculates the axis so that the data interval is based on the data values in the range.

To set an axis minimum value, click the Axis icon in the chart layout, and in the Properties pane, set the Maximum Value and Minimum Value properties to zero (0).

Shared Maximum Value Property

By default, ReportNet calculates the maximum axis value and applies it to each instance of a chart. In this release, you can now set the Shared Maximum Value property to have ReportNet re-calculate the axis maximum for each chart instance.

To have ReportNet re-calculate the axis maximum, click the Axis icon in the chart layout, and in the Properties pane, set the Shared Maximum Value property to No.

Readme Updates 11


Skip Interval and Skip Interval Start Properties

For charts where labels must appear in a single line on an axis, you can group the labels to increase readability. In this release of ReportNet, you can use two new properties, Skip Interval and Skip Interval Start, to customize the display of axis labels in a chart.

The Skip Interval property tells ReportNet how many labels to group. For example, in a report displaying twelve months of data, you can use the Skip Interval property to group the months into quarters by setting it to 2 (the interval between labels). The Skip Interval Start property tells ReportNet which label in the group to display. For example, to have ReportNet display the first month of the quarter as the label, set this property to 1.

To set these new axis properties, click the Axis icon in the chart layout, and in the Properties pane, set Skip Interval and Skip Interval Start to the desired values.

Note: If you set values for Skip Interval and Skip Interval Start, you must set the Allow Truncation, Allow 45 Rotation, Allow 90 Rotatation, Allow Stagger, and Allow Skip properties to No. Failure to do so may cause unexpected results.

Restrict Display of All UsersAdministrators can choose to restrict users from displaying all names in an LDAP namespace by disabling the Show users in the list option. When you remove this option from the interface, you can prevent users from degrading performance by displaying very large lists of names.

Steps1. Close ReportNet.2. Navigate to /crn_location/templates/ps/portal directory and open the system.xml file in a text

editor. 3. Locate the following

<param name="enable-show-users-support">true</param>

4. Replace true with false.5. Save the file.6. Restart ReportNet.

Note: Setting the enable-show-users-support parameter to false removes all instances of the Show users in the list option from the ReportNet interface. 452069

Optional Cascading PromptsIn previous releases, the first prompt in a series of cascading prompts could not be optional. The first prompt acted as a filter on the contents of a subsequent prompt. In this release of ReportNet, report authors can define any prompt as optional. When the first prompt in a series of cascading prompts is optional, the contents of subsequent prompts are unfiltered.

453443

Specify Report Header PositionsIn ReportNet, reports can have both list headers and overall headers. Report authors can now define the order in which these headers will appear. By setting the new Header Position property for the list header of a report, authors have complete flexibility in the order in which their report headers appear.

461829

Enhanced Prompting SecurityIn this release of ReportNet, values entered in a report prompt by a report user are no longer saved automatically. When report users will use the same prompt values repeatedly, report authors can choose to set the prompt values in the properties for a report, or on its schedule.

12 Cognos ReportNet


If you prefer to have the prompt values saved automatically, you may set the report server advanced property RSVP.PARAMETERS.SAVE to true.

Steps1. Open Cognos Connection.2. On the Tools menu, click Server Administration.3. Click Services.4. Locate the ReportService entry and click Set properties.5. Click the Settings tab.6. On the Advanced settings line, click Edit.7. Click Override the settings acquired from the parent entry.8. In the Parameter column, type RSVP.PARAMETERS.SAVE and in the Value column, type

TRUE.9. Click OK twice.

483549

Installation and Configuration

Upgrading TomcatReportNet includes and uses Tomcat 4.1.27 as its application server and an upgraded Xerces 2.5.0. Tomcat 4.1.27 is normally shipped with the Xerces parser version 2.4.0. However, the Xerces files xml-apis.jar and xerceslmpl.jar located in the crn_location/tomcat4.1.27/common/endorsed directory are versions of Xerces 2.5.0 that Cognos has modified.

nbna

Accented or Double-Byte Characters Do Not Display Correctly When Installing ReportNet on Linux

If you are using a UTF-8 locale, accented or double-byte characters may not display correctly in the xTerminal window.

To resolve this problem, use a non-UTF-8 locale or use the character-mode installation xwsetup to install ReportNet.

Authentication Providers for Linux InstallationsWhen ReportNet is installed on a single Linux computer, or when Content Manager is installed on a Linux computer, you can configure only an LDAP namespace as your authentication source.

Some authentication providers require libraries external to the ReportNet environment to be available. If these libraries are not available on Linux, the authentication provider cannot be initialized.

If you want to configure a Cognos Series 7, Active Directory, SAP BW, or CA SiteMinder namespace as your authentication source, you must install Content Manager on a non-Linux computer.

Readme Updates 13


Source Control Systems Item is Not Available in Cognos Configuration on Linux

On IBM pSeries Linux, the Source control systems item does not appear in the Explorer window of Cognos Configuration. This item appears only when the Framework Manager SDK component is present. This component is not available for IBM pSeries Linux.

449853

Product Limitations

Cognos Report Studio and Query StudioWhen ReportNet concatenates strings locally and if any of the involved strings contain null values, the result of the concatenation is an empty cell or a null value. This occurs because ReportNet requires that an expression that involves a null value returns a null value. Many databases ignore null strings when they perform concatenations. For example, if you concatenate strings A, B, and C, and if string B is a null value, the database may concatenate only strings A and C.

408213

Known Issues - General

RSV-SVR-0015 Error When Multiple Browser Windows Open for Same SessionWhen using the Report Viewer, if you open a new Internet Explorer browser window by selecting New, Window from the File menu, you may receive an RSV-SVR-0015 error message.

This occurs because the two open windows share one server session, which is not supported behavior.

To avoid this problem, do not open new browser windows from the File menu of an existing browser window. Use the Windows Start menu instead.

512022

Running ReportNet Under IBM WebSphereIf you run ReportNet under IBM WebSphere 4, the BIBusTKServerMain process opens a new window on the server console.

nbna

PDF Not Created When a Report Table Exceeds Output Page SizeIf a report contains a table whose size is larger than the output page size, the PDF version of the report will not be created. To fix this, set the table to a smaller size, or use a relative size where the width and height default to percentage of the page size.

445137

Known Issues - Series 7 Integration

14 Cognos ReportNet


Publish to ReportNet Fails if a Different Format is Used to Identify the Series 7 Directory Server

To enable the Publish to Cognos ReportNet capability from PowerPlay Enterprise Server, you must use the same format to identify the Series 7 namespace in both Cognos Series 7 Version 3 and Cognos ReportNet.

If you specify a host name in one product and then use the IP address:port format in the other, PowerPlay Enterprise Server is not able to publish to the Cognos ReportNet portal. Instead, it detects a mismatched configuration, prompts for credentials and, even if valid credentials are entered, raises a "Publish failed" error.

The solution is to use the same format to identify the Cognos Series 7 directory server in both products.

452195

Known Issues - Drilling Through to Cognos ReportNet from Series 7

Reauthentication PromptWhen you drill through from PowerPlay to Cognos ReportNet, the computers running PowerPlay Enterprise Server and ReportNet must be located in the same domain (i.e. computer.company.com). If they are on different domains, you will be prompted to reauthenticate.

You must also ensure cookie settings are the same for both product configurations. For more information about cookie settings, see "Enable Single Signon Between Cognos Series 7 and ReportNet" in the ReportNet Installation and Configuration Guide.

nbna

Known Issues - AdministrationThere are no known Administration issues in this release.

Known Issues - Security

Issues with Integrated Windows Authentication The single signon mechanism does not work when ReportNet is configured as follows:• Microsoft Internet Explorer runs on a Windows NT computer.• The authentication namespace is configured with the Active Directory provider.• Microsoft Internet Information Services (IIS) on a Windows 2000 or Windows 2003 server is

configured for Integrated Windows Authentication.

As a result, users are prompted for their Active Directory credentials.

This problem occurs because the ReportNet Active Directory provider uses SSPI protocol and Kerberos delegation for authentication in a single signon environment. When Microsoft Internet Explorer runs on Windows NT, it cannot authenticate to the IIS server using Kerberos delegation.

When your system is configured for Windows Integrated Authentication, for the single signon to work with IIS, you can do either of the following:

Readme Updates 15


• Configure ReportNet to communicate with the Active Directory server using the LDAP provider and configure the external identity mapping property to read the REMOTE_USER environment variable

• Configure the active directory provider advanced property to include the SingleSignOnOption parameter with a value of IdentityMapping.

A Namespace Configured with LDAP SSL Is Not AvailableWhen you use an LDAP namespace and you have SSL configured for communication with the directory server, the namespace may not be available when you start ReportNet.

This problem occurs if the directory that contains the cert7.db file does not contain the key3.db file. The key3.db file is required by the LDAP SDK version used with the current version of ReportNet.

To avoid this problem, ensure that the key3.db and cert7.db files are in the same directory.

Error When Using the SDK Custom Authentication JDBC Provider Sample When you want to use the sample, a run-time error occurs because the JDBC drivers for SQL Server are not available.

To solve this problem, perform the following steps.

Steps1. Install the JDBC drivers.

The drivers are available on the Microsoft Web site.2. Copy the following files from the jdbc_driver_installation/lib directory to the

crn_installation/webapps/p2pd/WEB-INF/lib directory:• msbase.jar• mssqlserver.jar• msutil.jar

Problems Logging onto or Searching a Series 7 Namespace that Contains Non-ASCII Characters

If objects or their properties, including the namespace, users, user folders, and user classes contain non-ASCII characters, you may encounter problems when you log onto or search a Series 7 namespace. For example, not all objects may be returned when you do a search.

To work around this issue, before you start the ReportNet service on the computer where Content Manager is installed, ensure that the system locale and encoding are the same as what was used when you created the Series 7 namespace objects.

For example, if ReportNet is running on UNIX and the Series 7 namespace objects contain Japanese characters, ensure you set the environment variable LC_ALL and LANG to the following:• AIX: Ja_JP.IBM-943• HP-UX: ia_JP.SJIS• Solaris: ja_JP.PCK

To check the list of valid locales, on the computer where Content Manager is installed, go to the crn_location/bin directory and open the localemap.xml. The localemap.xml file should not be modified.

443291

Known Issues - Cognos ConfigurationThere are no known Cognos Configuration issues in this release.

16 Cognos ReportNet


Known Issues - Cognos Report Studio

Default Font for ReportsSome users may notice a change in the default font used when rendering HTML reports in Report Viewer. To fix a problem with user-defined styles, the fonts.css stylesheet is no longer included when rendering reports. Users interested in adjusting the default font for either HTML or PDF reports should refer to Knowledge Base #1015507 for a detailed description of the recommended procedure.

451407

Reusing Cached DataThere is a new property in Report Studio, Use Local Cache. When you run a report, the query is stored in the cache for your current session and reused the next time you run the report. The queries are kept in the cache for each user. The cache is cleared when the report consumer logs off or when the report server times out after five minutes of inactivity.

In Report Studio, the Use Local Cache property is set to Default. This forces the report to use the same setting as the model it is based on. If you want the report to use a different setting than the model, in the Properties pane, change the Use Local Cache property. Set the property to No if you want to always execute the query. Set the property to Yes if you want to use cached results.

Changing the Use Local Cache property for one report will not affect other reports.

Drill-through Links Not Active in the Safari BrowserWhen viewing a PDF report in the Macintosh Safari browser, you cannot open hyperlinks. This is because the Macintosh Safari browser does not have the necessary Adobe Acrobat plug-in. To avoid this problem, use the HTML format when creating drill-through reports that may be viewed in Safari.

nbna

Report is Re-executed When the Delivery Method is ChangedIn Cognos Connection, if you change the delivery method while a report is running, the run operation is cancelled. A new report execution with the new delivery options you selected is started. This can be time-consuming when running large reports. To save time, before you run the report, click the Run with options button and specify the delivery method. This way, the report is executed only once.

431041

CombinationType Properties Being ReplacedYou can use the CombinationType Override and Combination Type Rotation properties to create combination charts. These properties are being replaced in the next release by a simplified process. If you use these properties in your reports you will have to change them when you upgrade to the next release.

nbna

Inconsistencies in Data OrderingWhen running a report, query results may display null values at the end of the report.

This may occur any time a query is broken down and a sort occurs locally. For example, this may happen when• query reuse is enabled

Readme Updates 17


If a query applied to previously cached result sets requires data to be ordered in a certain manner, the sort will be done locally.

• the collation sequence used by the target database is not recognizedThis forces the sort to be done locally.

451508

Page Query PropertyIn Cognos Report Studio, you can associate a query to a page. Open the Page Structure view of the report, click the page icon in the work area, and click the Query property in the Properties pane to associate a query to the page.

This property requires that a list, crosstab, or chart container associated with the query also be present in the report. If you do not want to display the container, set the Box Type property of the container to None.

Items from the query associated with the page will display as follows:• In a list, just like any other query item.• In a crosstab, only on the row edge.• In a chart, only on the series edge.

In a crosstab and chart, no data will be displayed if the query item is placed in a column, category, or cell.

Query items can also be displayed in the page header, body, or footer. This should result in the first row of the query being displayed on each page when you run the report. However, in the current release, values from an arbitrary row, often but not always the last, are displayed. Therefore, you should only do this when the same value appears in all rows of the query result. This issue will be addressed in the next major release.

451447

Known Issues - SAP BW Data Sources

OP-ERR-0073 Error When FilteringWhen using an SAP BW data source, you may encounter problems in list reports when you filter on an unbalanced item.

For example, you create a list report that contains the facts [Geography Unbalanced]/Continent, Country, City, and Cost. European cities, such as BERLIN and PARIS are in the Country column. If you define the filter [Country]= 'PARIS', you encounter the following error:OP-ERR-0073 'PARIS' does not exist in 'Country’.

413113

Considerations When Creating ExpressionsConsider the following when you create expressions in Cognos Report Studio and Query Studio using an SAP BW data source:

If you validate an expression from within the Expression Editor, errors in filter or calculation expressions are not detected.

426658

18 Cognos ReportNet


Incorrect Units of Measure in CalculationsWhen creating calculations in Cognos Report Studio and Query Studio, you may encounter problems with the units of measure. For example, the calculation Cost*Cost returns the unit of measure CAD^2 in BEx but * in ReportNet.

You can change the format of the corresponding column to obtain the desired unit of measure.

421591

Grouping Columns That Have the Count SummaryIf you add the Count summary to a non-fact column in a list and then group the column, the column will not be grouped when you run the report.

To resolve this issue, group the column first before adding the Count summary.

435017

Missing Measures in Crosstab ReportsIf you have a crosstab with multiple measures (multiple summary types and semi-additive aggregations), one measure may not render if the default aggregation function for the measures is set to Automatic.

To resolve this issue, set the default aggregation function to None.

437751

Maximum Rows Setting is IgnoredIf you are using an SAP BW data source, all rows are returned even if you have specified a maximum number to be returned.

The following settings are ignored:• the Data Retrieval Limits specified in the Governors dialog box in Framework Manager • the query property Maximum Rows Retrieved in Cognos Report Studio• the Number of Rows specified in the Set Web Page Size dialog box in Query Studio

428910

BAPI Errors When Executing a Query With Many Hierarchies Using Limited Local Processing

When executing a query that uses a large number of hierarchies with limited local processing, the SAP BW session runs out of memory and you may encounter the following error:BAPI error occurred in function module BAPI_MDDATASET_GET_CELL_DATA.&INCLUDE INCL_INSTALLATION_ERROR

To avoid this problem, do the following:

Steps1. Stop ReportNet.2. In the /crn_location/bin directory, rename the mdds_config.xml.sample file to

mdds_config.xml.3. Open the mdds_config.xml file and navigate to the following section:

<adapter name="LESA" libraryName="lesamdds" serviceAdapter="true">

4. Add the following parameter to this section:<maxCellsPerQuery value="nnn"/>

where nnn is the value appropriate for the memory available to the SAP BW server.

Readme Updates 19


5. Save the file and then restart ReportNet.This parameter specifies the maximum number of cells in the query to populate the limited local processing cube. If the query is calculated to exceed this limit, the report runs using only database processing, regardless of what the user specified.430671

PCA-ERR-0087 Error When Executing a Large Query Using Limited Local Processing

When executing a large query against an SAP BW data source using limited local processing, you may encounter the following error:PCA-ERR-0087 The "crossJoinSet" operator is not applicable.The limit on the number of tuples per edge has been exceeded

To avoid this problem, do the following:

Steps1. Stop ReportNet.2. In the /crn_location/bin directory, rename the mdds_config.xml.sample file to

mdds_config.xml.3. Open the mdds_config.xml file and increase the value of the maxTuplesPerEdge parameter.

Note: The appropriate value for this parameter depends on the memory available to the ReportNet server. Increasing this value too much may adversely affect the performance of ReportNet.

4. Save the file and then restart ReportNet.434859

Custom Formatting for Empty Cells Does Not Appear in ReportNetIf the SAP BW server administrator configures custom formatting for empty cells on the SAP BW server, the custom format does not appear in ReportNet reports.

Administrators should configure the formatting of empty cells using ReportNet.

425064

Sorting Order is Different When Report Runs with Limited Local Processing and Sorts on a Member Unique Name

If you create a report that contains sorting on a query item that is a member unique name, and if you run the report using limited local processing against an SAP BW data source, the order is different than if the report runs using database only processing.

To avoid this problem, instead of sorting on the member unique name, sort on a query item that corresponds to a property. Typically a name property exists and is more suitable for sorting.

nbna

Creating Sections on Reports That Access SAP BW Data SourcesSAP BW data sources may have problems with sections in reports under the following circumstances:• using both date and time hierarchies in a master-detail report

If you create a master-detail report that has sections and that uses date and time hierarchies, your report will contain no data. If you remove the sections from the report, you will receive an error. Do not combine date and time when using an SAP BW data source. 438891

20 Cognos ReportNet


• using a lowest-level query item that represents an SAP BW hierarchy containing ragged paths as the sectionIf a section in a report uses the lowest-level query item in a ragged hierarchy in an SAP BW data source (for example, the children of the "not assigned" node), you may receive this BAPI error:BAPIerror occurred in function module BAPI_MDDATASET_SELECT_DATA. Value <valueName>for characteristic <cubeName> unknown

The solution is to remove the section from the lowest-level query item.443696

• using several multicubes with SAP variablesIf you create a section in a report using conformed multicubes with SAP variables, you may receive an SAP error message.The solution is to use one multicube when creating sections in reports.437613

Incorrect Values When Filtering Nested Query ItemsIn a crosstab report, you will get incorrect values in the report if you nest query items from different levels and then filter on a nested query item. For example, one query item is from level 1 of the query subject and a query item from level 2 is nested under the level 1 query item. You will receive incorrect values if you filter on the level 2 query item.

425813

Inconsistent Summary Values for Semi-Additive Key FiguresA semi-additive key figure in SAP BW has a weighted average aggregate defined for roll-ups over time. When a report is run with this key figure, the summary values are not consistent.

430507

Cannot Perform Local Processing on a Query Item Whose Summarization Rule is AVG

If the Query Processing property is assigned a value of Limited Local in either a model or in the query property sheet in Cognos Report Studio, and at least one fact query item's summary rule in the report/query is different than how it is defined in SAP BW, then Cognos ReportNet will usually perform local processing to optimize query execution.

However, if the summarization rule in SAP BW for the query item (key figure) is defined as AVG, then Cognos ReportNet will not perform local processing. Although this may cause the query to execute slower than if local processing was enabled, it is not possible to determine from SAP BW the exact manner in which the average is calculated (average, average not zero, etc...). Consequently, Cognos ReportNet allows SAP BW to execute the query to ensure the correct values are calculated.

There is no way to force local execution of this type of query.

nbna

Calculation Displays Incorrect Unit FormatWhen using an SAP BW data source, ReportNet does not correctly display the derived unit for calculated measures. This occurs because SAP does not return the correct unit format for the calculated measure, which is processed at runtime.

421591

Readme Updates 21


Summary Rows Return Incorrect Total ValuesWhen the rollup of the measure is a minimum, summary rows return incorrect total values.

409532

Known Issues - Framework Manager

Links to Segmented Namespaces No Longer Work

Last Updated: December 18, 2005

When you have a Framework Manager project that contains a segmented namespace, changing the sequence of the segments may cause an external link to the namespace to fail. Re-ordering segments, or adding additional segments, in the namespaces in linked projects may result in incorrect links between projects, or in run-time errors. When you must re-sequence segments in a namespace, first remove any links to the project, re-order the segments, and then re-create the links.

503281

Testing Query Subjects Imported from Third-Party Data SourcesYou may not be able to test a query subject that you imported from a third-party data source if any of the following conditions exist:• The Framework Manager data source object created by the third-party import, and referenced

by the query subject, does not have an identically named corresponding data source in the ReportNet content store.

• The corresponding content store data source exists but is not valid (i.e the connection information is wrong).

• The optional schema or catalog properties of the data source object that the third-party import created and the query subject references are incorrect (for the databases accepting case-sensitive identifiers, you should also make sure the case is also right).

• The database object (such as a table or view) represented by the query subject no longer exists in the database or it was renamed since the third-party model was created, or it is otherwise not accessible within the current connection.

For example, you test a query subject and get this error message:QE-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions'status='-201'.UDA-SQL-0196 The table or view "GOSALES1.COGNOS.COM.GOSALES.CONVERSION_RATE" wasnot found in the dictionary.

As a solution, ensure that none of the conditions enumerated above apply.

431249

QE-DEF-0177 Error When Using Native Data Source Functions in SQL Statements That Return a CLOB or BLOB

When a SQL statement contains a native data source function that accepts CLOB or BLOB, the following error occurs:QE-DEF-0177 An error occurred while performing operation'sqlROpen' status='-9'

To avoid this, use a SQL99 function instead of a native data source function.

22 Cognos ReportNet


431931

Time Data Type Imported IncorrectlyWhen you import a query item with a data type of Time, Framework Manager sets the data type to Character. If you want the data type to be set to Time, you must change it manually.

438756

Conflicting Data Type ErrorIf you change the data type of a prompt, you receive this error when testing the query subject:ERROR -> QE-DEF-0374 Prompt 'what' is used multiple timeswith conflicting data types.

The solution is to rename the prompt in the macro when changing the data type.

430544

Unable to Connect Multiple Developers to a SourceSafe RepositorySourceSafe and CVS repositories intended to be shared over a network must be configured with a network address.

In the Repository connection properties dialog in Framework Manager, ensure that the path to the srcsafe.ini file, or the CVSROOT directory, uses a network path to a directory one level below the shared directory, not just a local drive letter and shared directory. For example, use \\computer_name\shared_directory and not E:\shared_directory.

This must be done before the project is added to the repository.

442931

Problems Arising When an IQD File Exported from Framework Manager Connects to Two Databases

When exporting data from Framework Manager to Transformer, it is possible to externalize a single IQD file that generates SQL for two different databases. However, due to differences in the way data access layers are handled in Cognos ReportNet and Transformer, Transformer cannot import such an IQD file.

This is a known issue, and Cognos is currently developing a solution to address it.

nbna

Properties Not Set Correctly When Importing SAP BW DataWhen you import an SAP BW data source into Framework Manager, the values for the Balanced, Ragged, and Hierarchy Sort Order query subject properties may not be set correctly.

Ensure that the values for these properties are set correctly.

428156

Some Property Values Are Reset After Performing Update Query SubjectPerforming the Update Query Subject action forces Framework Manager to replan and recreate all the query items. As a result, some property values may be reset back to the default value present after the import.

448098

Readme Updates 23


Known Issues - Microsoft ExcelThis section contains known Excel limitations that affect ReportNet.

Multiple Pie Charts Fail in Excel 2007If you create a report that includes multiple pie charts and run it in Microsoft Excel 2007, only one pie is shown.

Pie charts work properly in all other supported versions of Microsoft Excel.

556093

Signed URLs and Microsoft Excel 2000To ensure that report URLs cannot be changed when passed from a client browser to the report server, ReportNet applies signatures to the URLs it generates. However, Excel 2000 multipage (XLS) does not support signed URLs. To use the Excel 2000 multipage report type, you must disable digital signing of the URLs by doing the following:

Steps to disable signed URLs1. Stop the dispatcher.2. In the /crn/configuration directory, rename the cafconfig.xml.sample file to cafconfig.xml.3. Open the cafconfig.xml and navigate to the following section:

<crn:parameter name="caf_signedReportUrls"><crn:value xsi:type="xsd:boolean">true</crn:value></crn:parameter>

4. Change ="xsd:boolean">true</crn:value> to ="xsd:boolean">false</crn:value>.5. Restart your dispatcher.

Repeat the above steps for every dispatcher in your environment, or copy the cafconfig.xml to each /crn/configuration directory and restart the dispatchers.nbna

Displaying Text Columns Containing Numbers in Excel 2002/2003When you use a ReportNet report whose format is Excel Web Archive (XLSWA) that contains character columns with numeric data, Excel may display an error message for each cell that suggests that the textual data should be converted to numeric. You can turn off this error checking option in Excel by doing the following:

Steps1. From the Tools menu, click Options.2. Click the Error Checking tab.3. In the Rules section, uncheck Number stored as text.

nbna

Displaying Images in Excel When you use a report that contains images, the URL for the image must be fully qualified, such as "http://<servername>/crn/samples/images/<imagename.jpg>". If the URL uses a relative path, such as "../samples/images/<imagename.jpg>", Excel will not be able to display the image.

nbna

24 Cognos ReportNet


Unable to Open More Than One Excel Output SimultaneouslyWhen you run a report in HTML, click on the Excel icon to view it as Excel, then go back to the window showing the report in HTML and click the Excel icon again, you will be asked if you want to open, save or cancel. If you choose open, Excel displays a message indicating that you cannot open reports with the same name.

To fix this problem: • If you are using the XLWA or SingleXLS format with Excel 2002 or above, click OK to

display the Excel output.Note: If multiple Excel outputs are open, the message may be hidden behind the most recently opened browser window. If the message is hidden, select the browser in which you opened the first Excel output.

• If you are using the XLS format with Excel 2002 and above:You cannot open more than one Excel output at the same time. You need to rename the first report, or save and close it, before running the second report.

nbna

Known Issues - Lotus NotesThis section contains known Lotus Notes limitations that affect ReportNet.

Lotus Compatibility ModeReportNet customers who use Lotus Notes mail clients and who may have had problems viewing .pdf report attachments can use a setting in ReportNet to solve the problem. When you explicitly set the lotus compatibility switch, you tell ReportNet that you are using Lotus Notes as your delivery service.

Steps1. Open Cognos Connection.2. On the Tools menu, click Server Administration.3. Click Services.4. In the Service column, locate the entry for Job and schedule monitoring.5. Click the Set properties button.6. Click the Settings tab.7. On the entry for Advanced settings, click Edit.8. Click Override the settings acquired from the parent entry to select it.9. In the Parameter column, type lotus.compatability.mode.10. In the Value column, type true.11. Click OK twice.

Known Issues - Third-Party Data Source AccessA number of issues were identified with software components of third-party data sources that we support. We are managing the status of these problems with the respective vendors, but, at the time of this release, the following issues are still unresolved in the product.

IBM DB2 MVS 7.1A query that uses MIN and SUM functions against two dimensions and two measures, and with no sort specified, generates errors.

nbna

Readme Updates 25


Documentation Updates - Installation and Configuration Guide

This section contains additions and corrections to the ReportNet Installation and Configuration Guide.

Product InformationThis document applies to Cognos ReportNetTM Version 1.1MR4 and may also apply to subsequent releases.576575

Chapter 1: Upgrading from an Earlier ReleaseThe following paragraph replaces the first paragraph in this chapter.

You may upgrade to ReportNet 1.1MR4 from ReportNet 1.1MR1, MR2, or MR3. Previous versions of ReportNet must first be upgraded to ReportNet 1.1MR1. You must upgrade all components of ReportNet at the same time. Components from different versions are not compatible. For example, you must use Framework Manager 1.1 with ReportNet 1.1.576575

Change the ReportNet GatewayThe set of steps in this topic replaces one set of steps that appears in the "Configuring ReportNet" chapter of the ReportNet Installation and Configuration Guide.

Steps to Configure an Apache Gateway1. Stop Apache Web Server.2. Append the crn_location/cgi-bin directory to the appropriate environment variable:

• On Solaris, LD_LIBRARY_PATH• On HPUX,

For Apache 1.3, SHLIB_PATHFor Apache 2.0, SHLIB_PATH and LD_LIBRARY_PATH

• On AIX, LIBPATH3. On HPUX, do the following:

• Ensure that the LD_PRELOAD environment variable contains /usr/lib/libcl.2.• For Apache 1.3, set the CRN_CGIBIN_DIR environment variable to crn_location/cgi-bin.

4. Go to the Apache_installation/conf directory.5. Open the httpd.conf file in an editor.6. Add the following to the end of the load module list:

LoadModule cognos_module "crn_location\cgi-bin\module_name"where module_name is as follows:• On Windows,

for Apache 1.3, mod_cognos.dllfor Apache 2.0, mod2_cognos.dll

• On Solaris and AIX,for Apache 1.3, mod_cognos.sofor Apache 2.0, mod2_cognos.so

• On HPUX,for Apache 1.3, mod_cognos.slfor Apache 2.0, mod2_cognos.sl

26 Cognos ReportNet


7. Add the following to the end of the add module list:AddModule mod_cognos.cpp

8. Add the following to the aliases section:ScriptAlias /crn/cgi-bin "crn_location/cgi-bin"Alias /crn "crn_location/webcontent"Alias /crn/help "crn_location/webcontent/documentation"<Directory "crn_location/webcontent"> Options Indexes MultiViews</Directory>

The <Directory> directive is optional.Tip: Ensure that you define the crn/cgi-bin alias before the crn and crn/help aliases.

9. Add the following to the server status reports section:<Location /crn/cgi-bin/filename> SetHandler cognos-handler</Location>

where filename is any arbitrary, unique name.10. To enable the gateway diagnostic page, add the following to the server status reports section:

<Location /crn/cgi-bin/diag_filename> SetHandler cognos-handler</Location>

where filename is any arbitrary, unique name.The diag_ string is required.

11. For Apache 1.3, on Windows, Solaris, and AIX, add the following to the user directory section:<IfModule mod_cognos.cpp> CGIBinDir "crn_location/cgi-bin"</IfModule>

12. For Apache 2.0, add the following to the user directory section:<IfModule mod_cognos.c> CGIBinDir "crn_location/cgi-bin"</IfModule>

13. Save and close the file.14. For Apache 2.0, on HPUX, enable searching for LD_LIBRARY_PATH by running the

following command in the Apache_installation/bin directory:chatr +s enable +b enable httpd

15. Start Apache Web Server.16. In Cognos Configuration, configure the Gateway URI property to use the apache_mod

gateway:http://computer_name:port/crn/cgi-bin/filenamewhere filename matches the name that you used in step 9.

568835

Configuring the SAP Web Application ServerThe sets of steps in this topic replace some of the steps that appear in the "Changing Application Servers" chapter of the ReportNet Installation and Configuration Guide.

The following replaces a set of steps that appear in the "Change the SAP Web Application Server Startup Script" section.

Steps for SAP Web Application Server 6.20, SP231. Open the application server startup script in an editor:

• On Windows, open SAP_location/cluster/server/go.bat• On UNIX, open SAP_location/cluster/server/go.sh

2. Insert runtime parameters into the Java command line.

Readme Updates 27


• For Windows, insert -DCRN_ROOT="%CRN_ROOT%"• For UNIX, insert -DCRN_ROOT=$CRN_ROOTDo not append these paremeters to the end of the file; insert them before the Djavax.rmi.CORBA.Util.Class parameter.Tip: If the CRN_ROOT path contains spaces, enclose the variable in quotation marks.

3. Insert the following into the Java command line to set the XML parser for ReportNet:-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser

4. Set the memory used by the JVM.Typically, the memory is set by adding or changing two JVM parameters: -Xms and -Xmx. For information about these parameters, see the JVM or application server documentation.Tip: A minimum of one-quarter of your physical memory to a maximum of one-half of your physical memory (at least 512 MB) are suggested starting values that you can change to suit your environment.

5. If you are using a JVM version prior to 1.3.1_08, you may need to set the MaxPermSize parameter in the Java command line arguments. For example:-XX:MaxPermSize=64mFor information about this parameter, see the JVM or application server documentation.

6. Save and close the file.

The following replaces a set of steps that appear in the "Configure Application Server Properties and Deploy ReportNet" section.

Steps for SAP Web Application Server 6.20, SP231. In the SAP J2EE Engine configuration tool, make the following environment changes:

• For the appropriate server, set the Enable Chunked Response parameter to True.• Check default parameters to ensure that the values are appropriate. For example, by

default, the HTTP service uses port 80. Ensure that the HTTP service for the appropriate dispatcher in the cluster is set to a port that is not being used by another program. You may also need to increase the Keep Alive time-out from the default value of 15 seconds, which may be too short.

2. Start the state controller for Sap Web Application Server 6.20.3. Start the dispatcher for the SAP Web Application Server.4. Start the server for the SAP Web Application Server.5. Use the Deploy tool to create a new project.6. Load the ReportNet archive file you created. By default, the file is named p2pd.ear.

For information about creating the ReportNet archive file, see the ReportNet Installation and Configuration Guide.If you created a WAR file instead of an EAR file, you can generate the EAR file from the WAR file. For information, see your application server documentation.

7. Using the Deploy tool, connect to the Administration tool and deploy the ReportNet archive file.

8. Save the project.9. Verify that ReportNet is running by looking for the following message in the application

server console window or in the application server log file:The dispatcher is ready to process requests.

The following is a new set of steps that willbe added to the "Configure Application Server Properties and Deploy ReportNet" section in a future release.

Steps for SAP Web Application Server 6.40 on Windows1. Open the configuration tool by typing

drive:\usr\sap\sapid\JCxx\j2ee\configtool\configtool.batFor example, if the SAP ID is J2E and the installation is on drive D, you would typeD:\usr\sap\J2E\JC00\j2ee\configtool\configtool.bat

28 Cognos ReportNet


2. When prompted to use the default DB settings, click Yes.3. Under cluster-data, instance_IDxxxxxxx, Dispatcher_IDxxxxxxx, services, where xxxxxxx is

the ID number for your installation, highlight http.4. Under Global Properties, highlight KeepAliveTimeout and type a higher number and then

click Set.Tip: We suggest a KeepAliveTimeout number of at least 60.

5. Under cluster-data, instance_IDxxxxxxx, highlight Server_IDxxxxxxx.6. Set the memory used by the JVM.

Follow the recommendations from SAP. For more information, see SAP Note 723909 in the SAP Support Portal.If your computer has less than 1.5 GB of memory, you may have issues when you run SAP Web Application Server. We suggest a minimum value of 768 MB.

7. In the Java parameters box, indicate the location of ReportNet as follows:-DCRN_ROOT=ReportNet_installation_locationTip: If the CRN_ROOT path contains spaces, enclose the variable in quotation marks.

8. In the Java parameters box, set the XML parser as follows:-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser

9. Under cluster-data, instance_IDxxxxxxx, Server_IDxxxxxxx, highlight http.10. Set CompressedOthers to false and then click Set.11. Save the changes.

You are prompted to restart the server.12. Restart the server by using the SAP Management Console or by restarting the services in

Services.13. Use the Deploy tool to create a new project.14. Load the ReportNet archive file you created. By default, the file is named p2pd.ear.

For information about creating the ReportNet archive file, see the ReportNet Installation and Configuration Guide.If you created a WAR file instead of an EAR file, you can generate the EAR file from the WAR file. For information, see your application server documentation.

15. Using the Deploy tool, connect to the Administration tool and deploy the application file.16. When you are prompted to start the application, click Yes.17. Save the project.

Database Connectivity for the Reporting Database on LinuxThe only service that accesses the query database (also known as reporting database) is the reporting engine that runs reports. Ensure that you install the database API software for your reporting sources on each ReportNet server computer. On UNIX and Linux, the report server supports the native database connectivity.

nbna

Database Connectivity for the Content Store Database on LinuxThe database client software for the database that is used as the content store must be installed and configured on each computer where you install Content Manager. For DB2 databases, Content Manager uses the JDBC driver that requires DB2 client installation.

nbna

Running Two Versions of ReportNet on the Same ComputerYou must change the service name if you want to install more than one version of ReportNet on the same Windows computer. On Windows, you cannot register two services with the same name.

There are two methods you can use to change the service name on Windows:

Readme Updates 29


• Change the port numbers in the ReportNet URI properties.• Change the ReportNet service name directly.

Port Numbers

On Windows, when you change from the default ports, the port number is automatically appended to the service name. If you change the ports after installing a second version of ReportNet, you can then register both versions of ReportNet on the same computer. You can also run both versions at the same time.

Note: The service name in Cognos Configuration does not show the port number. You can view the service name and port number under Services in your Windows administrative tools.

Service Name

You can edit the ReportNet service name directly after installing a second version of ReportNet. You can then register two versions of ReportNet on the same computer. However, you must stop one version before you start the other version.

Note: This method can also be used on UNIX and Linux.

Steps to Change the Port Numbers1. Start Cognos Configuration.2. In the Explorer window, click Environment.3. In the Properties window, click the value for Internal dispatcher URI.4. Select the port number and type the new port number.

ReportNet uses the port number from the Internal dispatcher URI property in the service name.

5. If required, change the port number for the following URIs to match the new port number that you entered for Internal dispatcher URI: • External dispatcher URI• Content Manager URIs

If the Content Manager is installed on a separate computer, do not change the port number.

• SDK URI6. Click the value for Gateway URI and ensure that the URI contains the correct Web server

alias for the second version of ReportNet.For example, replace crn with crn2.

7. If you are using Cognos Portal Services, change the following properties, under Environment, Cognos Portal Services:• Ensure that Web Content URI shows the new Gateway URI that you set in step 6.• Ensure that the port number for Location of Applications.xml is also updated.

8. Save the configuration and start ReportNet.You can now run both versions of ReportNet at the same time.

Steps to Change the Service Name1. Start Cognos Configuration for the older version of ReportNet.2. Stop the service by selecting Stop from the Actions menu.3. Start Cognos Configuration for the new version of ReportNet.4. In the Explorer window, under Environment, ReportNet services, right-click Cognos

ReportNet and select Rename.5. Enter the new name and click OK.6. In the Explorer window, click Environment. 7. In the Properties window, click the value for Gateway URI and ensure that the URI contains

the correct Web server alias for the second version of ReportNet.For example, replace crn with crn2.

30 Cognos ReportNet


8. Save the configuration and start ReportNet.You can now switch between the old and new versions of ReportNet by stopping one version and then starting the other version.nbna

Documentation Updates - Quick Start Installation and Configuration Guide

Supported EnvironmentsYou can view an up-to-date list of environments supported by Cognos products, such as operating systems, patches, browsers, web servers, directory servers, and database servers on the Cognos support site (http://support.cognos.com). It is important to note that the Linux operating system is available in a number of distributions and supports a number of hardware platforms. Ensure that the Linux distribution and hardware combination you are using is a supported combination.

nbna

Update Your Java Runtime Environment on UNIX or LinuxBefore you can use the cryptographic operations, such as data encryption and key management, implemented by ReportNet, you must check that the required JAR (Java Archive) files are present in your Java Runtime Environment (JRE).

Before updating your JRE with the required JAR files, ensure you have the correct JRE version installed. For the latest information about supported environments, see the Cognos support website at http://support.cognos.com.

For more information about updating your JRE with the required JAR files, including detailed steps, see the ReportNet Installation and Configuration Guide.

nbna

Documentation Updates - Administration and Security GuideThis section contains additions and corrections to the ReportNet Administration and Security Guide.

Event-Based Report SchedulingThis section replaces the topic "Schedule a Report Based on an Event" in the chapter Scheduling Reports.

You can schedule a report based on an event, such as a database refresh or an email. The event acts as a trigger. When the event occurs, the report runs.

Event-based report scheduling may be used to run a report automatically whenever an event occurs. It may also be used to limit when users can run report views. For example, in a warehouse environment where the database is refreshed only once a week, there is no need to run reports more frequently. An administrator may choose to schedule the report based on the database refresh so that the report runs only once a week.

Event-based scheduling applies to the report and the report views associated with it.

Setting Up Event-based Report Scheduling

Before you can use event-based report scheduling, you must set it up as follows:

❑ Schedule a report based on the event.

Readme Updates 31



❑ Have your administrator set up the trigger event on a server. See "Set Up Trigger Events on a Server."

❑ Execute event-based scheduling for your report view. Since not all users of report views want event-based scheduling, it is not executed automatically.

Note: Trigger events can also be set up by an SDK developer using the Cognos ReportNet Software Development Kit (SDK). For more information, see "Creating an Event-based Schedule" in the ReportNet Developer Guide.

You can disable an event-scheduled report or report view.

Administrators can also disable the event-based report scheduling feature. See "Disable Support for Event-based Scheduling."

To schedule a report based on an event and execute event-based scheduling for your report view, you must have read, write, execute, and traverse permissions. You also require the following access permissions to all data sources used by the report. • dataSource - Execute and Traverse• dataSourceConnection - Execute and Traverse

(With only Execute access, you are prompted to log on to the database.)• dataSourceSignon - Execute

Schedule a Report Based on an Event

As part of setting up event-based scheduling, you must schedule a report based on an event.

Steps1. In Public Folders or My Folders, click the set properties button next to the report you want to

schedule.2. Click the Run options tab.3. Under Event name, specify the name of the event.

Note: The event name that you enter may be provided to you by your administrator or developer. If not, you must inform your administrator of developer of the event name that you use.

4. Under Event description, type a short description of the event.5. Click OK.

Now when you click the schedule button for a report or report view, event information replaces frequency information on the Schedule page.

Execute Event-based Scheduling for Your Report View

Since not all users of report views want event-based scheduling, it is not used automatically for report views. As part of setting up event-based scheduling, you must open the schedule and execute the event-based scheduling for your report view.

Steps1. In Public Folders or My Folders, click the schedule button for the report you want to

schedule.2. To execute the event-based schedule, click OK.

Next time the event occurs, your report or report view runs.

Disable a Scheduled Report

You can disable a scheduled report or report view. This is useful if you don’t need a scheduled report to run for a certain period of time. When you need the scheduled report again, simply enable it.

You must have read, write, and traverse permissions for a report, report view, or job to disable its schedule.

32 Cognos ReportNet



schedule.2. Click Disable the schedule.3. Click OK.

Disable Support for Event-based Scheduling This topic replaces the topic "Disable an Event-driven Schedule" in Chapter 18: Customizing the Functionality of ReportNet.

By default, event-based report scheduling is enabled. The event acts as a trigger. When the event occurs, the report runs. You can disable this feature by modifying the system.xml file.

Steps1. Stop the ReportNet service.2. Open the crn_location/templates/ps/portal/system.xml file in an XML or text editor.3. Locate the following XML code in the system element:

<param name="enable-trigger-support"> true</param>

4. Change the value of the enable-trigger-support parameter from true to false. The XML code should appear as follows:<param name="enable-trigger-support"> false</param>

5. Save the file.6. Start the ReportNet service.

Reports that are already scheduled for event-based scheduling continue to run, but no further event scheduling can occur while support is disabled.

Set Up Trigger Events on a ServerThis topic replaces the topic "Create an Event-driven Schedule" in Chapter 18: Customizing the Functionality of ReportNet.

As part of setting up event-based report scheduling, you must set up the trigger event on a server. You link the occurrence of an external event, such as a database refresh or an email, with a trigger event on the server that causes the report to run.


The name of the event must also be specified when the report is scheduled based on an event.

Note: Trigger events can also be set up by an SDK developer using the Cognos ReportNet Software Development Kit (SDK). For more information, see the ReportNet Developer Guide.

Scripts

Using the Windows trigger.bat script or the shell script trigger.sh, you can trigger one or more events on the server.

The script syntax follows:

trigger.bat URL [username password namespace] triggerlist

where:• URL is the Cognos ReportNet server URL• username is a valid username in the specified namespace

Readme Updates 33


• password is the password for the username• namespace is the namespace for the username• triggerlist is a comma separated list of trigger names

Example

For example, if users want to schedule a report based on a database refresh and want to schedule a second report based on receipt of an email, your custom trigger command line might look similar to this:

trigger.bat http://localhost/crn/cgi-bin/cognos.cgi username password namespace databaserefreshtriggername,emailtriggername

Steps1. If you are setting up trigger events on a ReportNet server, you have the prerequisite items.

Proceed to step 3.2. If you are setting up trigger events on another server, complete the following tasks:

• Ensure that the server has either a Java Runtime Environment or a Java Development Kit, 1.3 or greater.

• From crn_location/webapps/p2pd/WEB-INF/lib on a ReportNet server, copy the following to the same location on the server:axis.jaraxisCrnpClient.jarcommons-discovery.jarcommons-logging.jarjaxrpc.jarsaaj.jarxml-apis.jarxercesImpl.jar

• From crn_location/webapps/EventTrigger on a ReportNet server, copy the following to the same location on the server:trigger.battrigger.shtrigger.class (a Java sample that can run in any Cognos-supported platform)

3. Make sure that the command line executes when the external event, such as a database refresh or email, occurs. The mechanism that you use to invoke your custom trigger command is dependent on the application that you are working with, for example a database or email application. Consult the documentation for your application.

4. Inform the users that they can now schedule reports based on the trigger event.If the user has scheduled a report based on the event, when the user clicks the schedule button for a report view, event information replaces frequency information on the Schedule page.After the script runs, the trigger method returns an integer value representing the number of schedules that were run. The following integers represent errors:• -1 usage error, such as invalid parameter or syntax• -2 communication problem with ReportNet server

Schedule a Report on Last Day of MonthYou may want to schedule a report to run automatically on the last day of each month.


schedule.2. Under Frequency, select By Month, then select Day.

34 Cognos ReportNet


3. Enter Day 31 of every 1 month(s).Entering 31 as the day ensures that the report runs on the last day of the month, regardless of how many days there are in the month.

4. Under Start, select the date and time when you want the monthly schedule to start.5. Under End, select when you want the monthly schedule to end.6. Click OK.

A schedule is created and the report runs on the last day of every month during the specified time period.nbna

Permissions to Create a Report View In the "Cognos Connection" chapter, the topic "Create a Report View" contains incomplete information. It specifies that to create a report view, read permissions for the original report are required.

The topic should specify that to create a report view, execute or read permissions for the original report are required.

449270

Incorrect Parameter Value The topic "Disable Support for Custom Portal Pages" in the chapter "Customizing the Functionality of ReportNet" specifies an incorrect parameter value in the XML code used in step 3.

The XML code should read as follows:<param name="enable-custompages"> true</param>

nbna

Transferring the ReportNet Passport ID as a URL ParameterThe following topic should appear in the Cognos Portal Services chapter.

Disable the Mechanism to Transfer the ReportNet Passport ID as a URL Parameter

You can disable the mechanism to transfer the ReportNet passport ID as a URL parameter between the users’ browsers and the ReportNet gateway to ensure a higher degree of security. You can do this only when• Cognos Portal Services is used to integrate Cognos portlets into a corporate portal.• single signon is implemented between the users’ browsers and ReportNet, and, if applicable,

Cognos Series 7.

By default, Cognos Portal Services re-creates the active credential cookie in the user’s browser by passing the passport ID as a URL parameter.

If the single signon is not implemented, when portal users interact with Cognos portlets, they are authenticated both in the portal and in ReportNet. The portal, not the user's browser, maintains the active credential token generated by ReportNet. In some situations, for example when you want to see a report in a Cognos portlet, a direct connection between the user's browser and the ReportNet gateway must be established. This may become a security risk because a valid ReportNet passport ID appears in some log files. The same applies when ReportNet is integrated with Cognos Series 7 and the active credential is passed as a URL parameter.

To disable this mechanism, for each dispatcher configured for your system, set the following parameters for the ReportNet PresentationService to 0:• CPSPropagatePassport

Readme Updates 35


Controls the transfer of the ReportNet passport ID as a URL parameter. When set to 0, it stops the transfer.

• CPSPropagateTicketControls the transfer of the Cognos Series 7 ticket ID as a URL parameter. When set to 0, it stops the transfer.

Steps1. In the Welcome page of the portal, from the Tools menu, click Server Administration.2. Click the Configure tab.3. In the Name column, click the dispatcher you want.4. For the PresentationService, in the Actions column, click the set properties button.5. Click the Settings tab.6. For the Environment category, next to Advanced settings, click the Edit link.7. Select the Override the settings acquired from the parent entry check box. 8. In the Parameter column, type the parameter names:

• CPSPropagatePassport• CPSPropagateTicketThe parameters are case sensitive.

9. In the Value column, type 0 for each parameter. 10. Click OK.11. Click OK again.12. Click the Configuration link in the path at the top of the page.

You return to the list of dispatchers.13. If you have more than one dispatcher configured, perform steps 3 to 12 for each remaining

dispatcher.nbna

Install the Cognos Business PackageThe Cognos business package is an Enterprise Portal Archive (.epa) file that includes a Portal Archive (com.cognos.pct.reportnet.ivew.par) file, two iView templates, four iViews, and a system template.

You must be logged on to the portal with administrator privileges.

You must be able to access the com.cognos.reportnet.epa file from your file system or from the network file system. If the Cognos ReportNet installation is not within network access, you must manually move the file to an accessible location.

Steps1. Copy the com.cognos.reportnet.epafile from installation_location\crn\cps\sap\package to

SAP_portal_installation_location\global\config\pcd\import.2. In the portal, click the System Administration tab.3. On the Transport tab, click Import.4. Click Browse and then click Select next to the com.cognos.reportnet.epa file.5. Click Import.

nbna

Setting Up Oracle Proxy Connections and Virtual Private DatabasesThe first note should read as follows:

Note: You cannot test the XML command blocks using Test the connection link on the connection string page. If you have SDK installed, you can ensure that your XML code validates against the schema file named crn_location/webapps/p2pd\WEB-INF/classes/DataSource.xsd.

36 Cognos ReportNet


450204

Logging Level 5The following topics should read as shown below:• Chapter 2: Server Administration, Log Messages, "Set the Logging Level"• Chapter 15, Audit Reports, Setting Up Audit Reporting, "Enable Native Query Logging"

Set the Logging Level

By setting the logging level, you specify the detail of events and messages to record in the log file or in the log database.

An event is an occurrence in your ReportNet environment that is significant enough to be tracked, such as starting or stopping a service.

There are five levels of logging available. You set the logging level for each logging category at the dispatcher level. When the logging level is set for a dispatcher or a configuration folder, all the services associated with that dispatcher or folder inherit that logging level.

The logging categories that apply to Level 5 logging are• System and service startup and shutdown• Messages at user logon• Use requests• Service requests and responses• All requests to all components along with their parameter values• Third-party queries to ReportNet components (native query)

The logging categories that apply to Level 4 logging are• System and service startup and shutdown• Messages at user logon• Use requests• Service requests and responses

The logging categories that apply to Level 3 logging are• System and service startup and shutdown• Messages at user logon• Use requests

The logging categories that apply to Level 2 logging are• System and service startup and shutdown• Messages at user logon

The logging category that applies to Level 1 logging is• System and service startup and shutdown

Increasing the logging level may negatively affect the performance of ReportNet. You can maintain system performance by managing the amount of logging performed by the server. Server performance may be adversely affected if extensive logging is performed.

The default logging level is 1.

We do not recommend that you use level 5 except for detailed troubleshooting purposes since it may significantly degrade server performance.

If you are using audit reports, the logging level must be set to 3 or higher. Native query logging is part of level 5 logging. However, if you are using audit reports, you can enable native query logging independently from the level 5 logging using the Sever Administration tool.

To access the Server Administration tool, you must have execute permissions for the Administration secured function.

Readme Updates 37


Steps1. On the portal toolbar, click Server Administration.2. Click the Configure tab.3. In the Actions column, click the set properties button for the dispatcher or configuration

folder you want.4. Click the Settings tab to view all the configuration settings.5. In the Value column, type a new value for the following settings, each of which represents a

logging category:• Audit logging level• Audit run-time usage logging level• Audit administration logging level• Audit other logging levelTip: If you want to reset a configuration setting to its default value, select its check box and click Reset to default value.

6. Click OK.

Enable Native Query Logging

If you want to create audit reports that include the queries that are run against your reporting data source, you must enable native query logging. You can use native query logging to learn what kinds of information users want or whether a report is running efficiently.

Native query logging is enabled automatically if you set the logging level to 5. However, the following procedure enables native query logging without the other logging that occurs with level 5 logging.

We do not recommend that you use level 5 except for detailed troubleshooting purposes since it may significantly degrade server performance.

Steps1. On the portal toolbar, click Server Administration.2. Click the Configure tab.3. In the Actions column, click the set properties buttonfor the dispatcher or configuration

folder you want. 4. Click the Settings tab to view all the configuration settings.5. In the Value column, click Yes next to Audit Native Query?.6. Click OK.

Print a Report

The following note should be added to the topic "Print a Report" in the chapter Distributing Reports:

Note: If the ReportNet report server runs on a Linux platform, a server printing limitation exists. There is currently no version of Adobe Acrobat Reader available for Red Hat Enterprise Linux running on IBM pSeries hardware. This affects server printing tasks, such as when a report is scheduled to be run and printed from a ReportNet server.

This is not an issue in the following situations:• Users run reports in PDF and then print the report.• The report is emailed to users in PDF format. Users can then print the PDF report from their

local computers. This works for interactive usage and for scheduled reports.• A report is scheduled to be saved in the content store. Users can then open the report using a

browser and print the report from their local computers.

Documentation Updates - Cognos Report Studio User GuideThis section contains additions and corrections to the Cognos Report Studio User Guide.

38 Cognos ReportNet


Specifying the Number of DecimalsWhen specifying the number of decimals, ReportNet uses the IEEE 754 default rounding mode known as half even. With half even rounding, numbers are rounded toward the nearest truncated value, unless both truncated values are equidistant, in which case the value ending in an even digit is chosen. That is,• if the digit immediately after the precision to be displayed is greater than 5, the number is

rounded up.• if the digit immediately after the precision to be displayed is less than 5, the number is

rounded down.• if the digit immediately after the precision is a 5, then the number is rounded down when the

preceding digit is even and rounded up when the preceding digit is odd.

For example, if you specify no decimals, the number 78.5 is rounded to 78, while the number 73.5 is rounded to 74.

In addition, if the maximum number of decimals is lower than the actual number of decimals in the number, the number is rounded to the maximum number of decimals.

428693

Documentation Updates - Cognos Report Studio User Guide and ReportNet User Guide

This section contains additions and corrections that affect both the Cognos Report Studio User Guide and the ReportNet User Guide.

Excel Formats and SSLIn the Cognos Report Studio User Guide and the Query Studio User Guide, the topic Using Secure Socket Layer (SSL) in the Producing Reports in Microsoft Excel appendix is incorrect. SSL is supported for the following formats and Microsoft Excel versions:• Single sheet XLS in Excel 2000, 2002, and 2003.• Multiple page XLS in Excel 2003.• Web archive in Excel 2000, 2002, and 2003.

nbna

Documentation Updates - Query Studio User GuideThis topic replaces the two topics "View a Report in Excel Format" and "View a Report in Excel 2002 Format" in the Query Studio User Guide.

View a Report in Excel FormatQuery Studio can produce reports in three Excel formats:• Excel 2000 single sheet format • Excel 2000 format • Excel 2002 format

Excel 2000 format can be used with Microsoft Excel versions lower than 2002. It supports up to 65,536 rows and multiple sheets.

Excel 2000 single sheet format offers improved security. Excel 2000 may have cookies in the URLs to spreadsheets, which could be used to illegally impersonate a user. Excel 2000 single sheet format does not use outgoing URLs. However, there is a limit of 65,536 rows, and page breaks for multiple-author pages are ignored.

Excel 2002 format and Excel 2000 single sheet format also offer the following benefits:

Readme Updates 39


• Both work with SSL protocol. • Both work with a single signon. Secure reports can be accessed without subsequent signons

because the system automatically identifies users and provides security information. • Both work with Netscape 7.01 • Spreadsheets are contained in a single file for reliable spreadsheet navigation.

Date Formats and Excel

The ReportNet full date format does not always display correctly in Microsoft Excel 2000, if it is on a system with a regional setting other than English. This does not occur with Microsoft Excel 2002 or 2003 versions. To fix this, re-apply the proper format in Excel.

Other limitations exist when producing reports in Microsoft Excel format.

For information about these limitations, see "Producing Reports in Microsoft Excel Format".

Steps1. Open the report that you want in Query Studio.2. From the Run Report menu, choose one of the following:

• To produce reports on one sheet using Microsoft Excel versions lower than 2002, click View in Excel 2000 Single Sheet Format.

• To produce reports using Microsoft Excel versions lower than 2002, click View in Excel 2000 Format.

• To produce reports using Microsoft Excel versions 2002 and higher, click View in Excel 2002 Format.

nbna

Documentation Updates - ReportNet User Guide

Print a ReportThe following note should be added to the topic "Print a Report" in the chapter Distributing Reports:

Note: If the ReportNet report server runs on a Linux platform, a server printing limitation exists. There is currently no version of Adobe Acrobat Reader available for Red Hat Enterprise Linux running on IBM pSeries hardware. This affects server printing tasks, such as when a report is scheduled to be run and printed from a ReportNet server.

This is not an issue in the following situations:• Users run reports in PDF and then print the report.• The report is emailed to users in PDF format. Users can then print the PDF report from their

local computers. This works for interactive usage and for scheduled reports.• A report is scheduled to be saved in the content store. Users can then open the report using a

browser and print the report from their local computers.

Event-Based Report SchedulingThis section replaces the topic "Schedule a Report Based on an Event" in the chapter Scheduling Reports.

You can schedule a report based on an event, such as a database refresh or an email. The event acts as a trigger. When the event occurs, the report runs.

40 Cognos ReportNet


Event-based report scheduling may be used to run a report automatically whenever an event occurs. It may also be used to limit when users can run report views. For example, in a warehouse environment where the database is refreshed only once a week, there is no need to run reports more frequently. An administrator may choose to schedule the report based on the database refresh so that the report runs only once a week.


Setting Up Event-based Report Scheduling

Before you can use event-based report scheduling, you must set it up as follows:

❑ Schedule a report based on the event.

❑ Have your administrator set up the trigger event on a server. See "Set Up Trigger Events on a Server."

❑ Execute event-based scheduling for your report view. Since not all users of report views want event-based scheduling, it is not executed automatically.

Note: Trigger events can also be set up by an SDK developer using the Cognos ReportNet Software Development Kit (SDK). For more information, see "Creating an Event-based Schedule" in the ReportNet Developer Guide.

You can disable an event-scheduled report or report view.

Administrators can also disable the event-based report scheduling feature. See "Disable Support for Event-based Scheduling."

To schedule a report based on an event and execute event-based scheduling for your report view, you must have read, write, execute, and traverse permissions. You also require the following access permissions to all data sources used by the report. • dataSource - Execute and Traverse• dataSourceConnection - Execute and Traverse

(With only Execute access, you are prompted to log on to the database.)• dataSourceSignon - Execute

Schedule a Report Based on an Event

As part of setting up event-based scheduling, you must schedule a report based on an event.

Steps1. In Public Folders or My Folders, click the set properties button next to the report you want to

schedule.2. Click the Run options tab.3. Under Event name, specify the name of the event.

Note: The event name that you enter may be provided to you by your administrator or developer. If not, you must inform your administrator of developer of the event name that you use.

4. Under Event description, type a short description of the event.5. Click OK.

Now when you click the schedule button for a report or report view, event information replaces frequency information on the Schedule page.

Execute Event-based Scheduling for Your Report View

Since not all users of report views want event-based scheduling, it is not used automatically for report views. As part of setting up event-based scheduling, you must open the schedule and execute the event-based scheduling for your report view.


schedule.2. To execute the event-based schedule, click OK.

Readme Updates 41


Next time the event occurs, your report or report view runs.

Disable a Scheduled Report

You can disable a scheduled report or report view. This is useful if you don’t need a scheduled report to run for a certain period of time. When you need the scheduled report again, simply enable it.

You must have read, write, and traverse permissions for a report, report view, or job to disable its schedule.


schedule.2. Click Disable the schedule.3. Click OK.

Documentation Updates - SAP BW Data SourcesThis section describes considerations related to creating reports against an SAP BW data source with Cognos Report Studio and Query Studio.

Documentation Updates - Framework Manager User GuideThis section contains corrections and additions to the Framework Manager User Guide.

Preserve Business Names when Importing Objects from DB2 CubeViewsWhen importing DB2 Cube Views objects, you can choose to import the object name or the business name as the logical name for the Framework Manager object.

This is controlled by a new third-party import option called Name Mapping, which is available in the Third Party Specific Import Options import wizard page.

Using the Name Mapping option, choose• Default Mapping to import the OLAP business name as the logical name and to import the

OLAP object name as the physical name• Alternate Mapping to import the OLAP object name as the logical name and to import the

OLAP business name as a User Defined Property

For more information about importing from third-party metadata sources, see the Framework Manager User Guide.

430745

Rollup Processing Property The following information needs to be added to the "Creating Datasources" topic in the Framework Manager User Guide.

The Rollup Processing property for data sources determines whether aggregate rollups above the lowest level are computed locally or in the database. The default is set to local if local query processing is enabled, and is set to database otherwise.

Note: This property is not applicable for SAP BW data sources.

The possible options for this property are:• unspecified

The aggregation rollup is not specified.• local

42 Cognos ReportNet


All aggregation rollups are computed locally (in the report server) using a running aggregate (for example, RSUM). Running aggregates spread the cost of this computation as the data is retrieved. Use this option if the local computer has more idle resources than the database computer, or if you find through experiment that it is the fastest method.

• database Aggregation rollups are computed by the underlying database software if possible. Otherwise, they are computed locally (provided local query processing is enabled). Running aggregates are used, but the cost is incurred by the database server instead of the report server. Use this option if the database computer has more idle resources than the local computer, or if you find through experiment that it is the fastest method.

• extended All aggregation rollups are computed by the database server using an extended aggregate (for example, XSUM). Extended aggregates incur the entire cost of this computation up front. Typically, this is the fastest method, but only where the database is set up to take advantage of materialized views. For databases where OLAP functionality is supported, this is translated into the appropriate OLAP aggregate functions.

The Externalize Auto Summary PropertyThe current documentation states that the Externalize Auto Summary property must be used with the iqd method for externalizing query subjects.

This is not correct. You can use the Externalize Auto Summary property with all externalize methods. This property is used when you want to have relational data aggregated when it is externalized. Specify dimensional information for the query subject before externalizing it.

442859

Changes to OLAP Function NamesThe following OLAP function names have changed from• avg to average• max to maximum• min to minimum• stdev to standard-deviation• var to variance• sum to total

When you create an expression using these functions, you must use the new names.

nbna

Externalizing SAP BW Query SubjectsThe topic named "Guidelines for Externalizing SAP BW Query Subjects" in the Framework Manager User Guide has been updated. Use this topic in its place.

Framework Manager provides the ability to externalize, or extract, data corresponding to a model. This functionality applies to all supported data sources, including SAP BW. However, special considerations must be given when externalizing models based on SAP BW.

This topic describes some of the different ways in which data may be extracted from SAP BW and the issues that you must address when doing so.

When extracting data from SAP BW using Framework Manager, it is important to understand the distinction that Framework Manager makes between different types of query subjects. Each type of query subject exhibits a different behavior when it is externalized and can be fine-tuned before externalizing.

Readme Updates 43


Workaround for Problems Encountered While Externalizing

When externalizing a data source from Framework Manager, you may encounter an authentication error if• the model is published to Content Manager• externalizing the data takes longer to perform than the timeout period assigned to passports

within Cognos Configuration

Users are not prompted to re-enter their authentication credentials.

If an error occurs, the externalized data is still complete and valid. However, if the modeler chooses to actually publish the model, the modeler must re-authenticate and re-publish the model, but without externalizing the data.

Another solution is to publish the model to the network, in which case the authentication error does not occur.

Characteristic Query Subjects

Characteristic query subjects are externalized independent of the type of SAP BW data source, such as InfoCube or SAP BW Query.

Framework Manager externalizes all query subjects that do not contain fact query items using a single approach. In these cases, the extract size configuration setting is used to control the manner in which data is extracted from SAP BW.

Note that model query subjects are externalized in a different manner, regardless of whether they contain fact query items or not; this is documented later.

Extract SizeThe Extract Size data source property within Framework Manager is used to control the amount of data retrieved from SAP BW at any one time.

If this setting is negative, zero, or empty, a single query is issued to SAP BW to extract the characteristic data.

If this setting is a positive value, Framework Manager issues multiple queries to SAP BW, each of which returns approximately the number of megabytes specified by the Extract Size property.

This feature can reduce the overall size of the query result on the SAP BW server. Overall query execution may take longer, but for large characteristics, not using this feature may result in consumption of a user's allotted memory space on the SAP BW server.

The entire data for a characteristic query subject will be in memory within Framework Manager prior to the production of an extract file. It is important that only the required query items be extracted from SAP BW to ensure that an extract does not fail due to memory allocation errors within Framework Manager.

Model Query Subjects

Model query subjects are extracted using the same mechanism by which queries are executed within ReportNet. Therefore, the Extract Size property has no effect on the query execution.

InfoCube Key Figures Query Subject

When externalizing the key figures query subject from a model based on an InfoCube, Framework Manager uses exactly the same approach as used for externalizing model query subjects.

For an InfoCube containing more than a few thousand transactions, externalizing an InfoCube directly from Framework Manager can easily exceed both time and memory limits on either the client or server. In such cases, it is highly recommended that an SAP BW Query be used as the basis for externalizing the SAP BW data.

44 Cognos ReportNet


SAP BW Query Key Figures Query Subject

Using a BEx query as the basis for externalizing key figures from an SAP BW data source is, in most cases, the best approach. By using a BEx variable to break the data of the key figure query subject into manageable sections (described later in this topic), arbitrarily large volumes of transaction data can be extracted from SAP BW.

Note, however, that this approach incurs some restrictions as to what can be extracted from SAP BW, and how it can be extracted. The remainder of this section describes the how an SAP BW Query is used to extract data from SAP BW, including all known restrictions and limitations.

For the remainder of this section, it is assumed that an SAP BW Query is being used as the basis for externalizing the data, not as the basis for reporting, and with the intent of exceeding the memory and time limitations associated with extracting data directly from an InfoCube.

nbna

SAP BW Query RequirementsFirst, it is not possible to externalize an arbitrary SAP BW Query. To be externalized, an SAP BW Query must adhere to the following restrictions:• Only a single field can be shown. Showing something such as "key and text" will result in

incorrect data.To change what appears for a characteristic, right-click the characteristic along the edge of the SAP BW Query and click Properties. In the Properties dialog box, set the Display As value to Key.It is strongly recommended that you use Key.

• To reduce data volumes, as well as the amount of aggregation performed by the SAP BW server, it is strongly recommended that summarization for all characteristics in the query be disabled in its property sheet. To disable summarization for a characteristic , right-click the characteristic along the edge of the SAP BW Query and click Properties. In the Properties dialog, set the Suppress Results Rows value to Always.

• If at least one characteristic in an InfoQuery is displayed as something other than Key, then summarization for all characteristics must be suppressed.

• The query must not contain the Currency/Unit characteristic.• None of the characteristics may be assigned a display hierarchy, either explicitly or by a

variable.• If a characteristic is included in an SAP BW Query as a free characteristic, no values will

appear for that characteristic in the key figures extract.A filter on a free characteristic acts as a filter on the data returned by SAP BW. It is an efficient mechanism for defining a subset of an InfoCube.Such a filter may also be applied to a characteristic along an axis of an SAP BW Query, in which case the filtered values appear in the key figures extract.

• All key figures in the SAP BW Query must be numeric.• The values of each key figure should be in a single currency since currency information is not

carried forward into a CSV extract. A variable should not be used to drive the assignment of a target currency.

• Include in the SAP BW Query only those characteristics which are to be extracted using Framework Manager. Including unnecessary characteristics increases the volume of data transferred from SAP BW, thus affecting performance.

Framework Manager ConsiderationsWhen extracting the key figure query subject from an SAP BW Query, the Extract Size property of the data source is used to control the amount of data retrieved from the SAP BW server at one time. The behavior in this case is slightly different than that described earlier in this topic. In this scenario, the setting has no affect on the SAP BW server, but it does limit the amount of memory allocated at any one time by Framework Manager to retrieve the data.

Readme Updates 45


It is important to realize that filters defined on the key figures query subject are not enforced when extracting data from an SAP BW Query. To obtain performance benefits of extracting data from an SAP BW Query, filters must be defined in an SAP BW Query.

In addition, any calculations defined within the key figures query subject are ignored. These may be defined either within the SAP BW Query in BEx, or in a model query subject in Framework Manager.

Each characteristic extracted must contain at least one query item from the lowest level of its hierarchy (if there is one) to provide linkage with the key figures extract.

Use of Variables to Externalize Key FiguresThe volume of transactions within an SAP BW Query is such that, in most cases, the use of a single query to extract the data from SAP BW will exceed the memory allocated to a user on an SAP BW server. In Framework Manager, you can use a single optional variable to extract fact data from an SAP BW Query in reasonably sized sections.

To use this feature, one characteristic included in the SAP BW Query (but not included as a free characteristic) is assigned a variable that conforms to the following restrictions:• It must be a single value.• It must be optional.• It must not have a default value.• It can be defined on the characteristic or a presentation hierarchy.

If an SAP BW Query contains such a variable and the key figures query subject is externalized, Framework Manager runs a query for each possible value associated with a variable. Thus, by choosing an appropriate characteristic, the key figures query subject can be extracted without exceeding the memory restrictions of either the client or server. Memory caches on the client and server are flushed after each query.

If a presentation hierarchy is used to drive the creation of extract sections, it is important that the values for a variable be obtained from a single level in the hierarchy, otherwise the extract will contain data summarized at different levels. To restrict the values for a variable to a single level of a hierarchy, edit the Level Restriction of the variable in Framework Manager. For example, using a value such as "2:2" indicates that only values from the second level of the hierarchy are to be used (level 0 is the root of a hierarchy).

In the presence of an SAP BW Query with one such variable, the value of the variable is reset after each query.

In an SAP BW Query contains anything more than a single variable, or one that is defined differently than described above, Framework Manager does not attempt to use a variable to break the extraction of the key figures query subject into smaller sections.

Building PowerCubes from SAP BW Data

You can build Cognos PowerCubes from SAP BW data. There are guidelines to consider for both Framework Manager and Transformer.

Framework Manager GuidelinesWhen externalizing data for the purpose of creating one or more PowerCubes, keep these considerations in mind.• The extract of each characteristic must have a common key query item that is equivalent to a

surrogate key query item in the key figures extract.• For an extract based on an SAP BW Query, it is strongly recommended that all characteristics

be displayed as Key in the SAP BW Query.• If a characteristic does not have a presentation hierarchy, or a new one is desired, extract one

or more query items that can form the basis for levels in a hierarchy.• During the import of SAP BW metadata into a model that is to be used for the purpose of

extracting data, it is desirable to limit the model to only those query items that are absolutely required to build a PowerCube. This will have the effect of improving data extract performance.

46 Cognos ReportNet


• A practical limit for PowerCubes is 1,000,000 categories (values) for a dimension (characteristic).

Transformer GuidelinesWhen using the SAP BW data that you extracted from Framework Manager, keep these considerations in mind.• Using the model wizard in Transformer, insert a data source of type Delimited-Field Text With

Column Titles and start by selecting the fact table. Do not run auto-design.• Drag all the key figure columns from the Data Sources pane into the Measures pane. Ensure

that the aggregation rule for each measure is correctly defined within Transformer to align as closely as possible with the aggregation rule defined in SAP BW.

• It is recommended that the storage type for all measures be set to 64-bit floating point.• Using the date wizard, select a query item that will provide the dates for the PowerCube. Note

that the dates for the PowerCube can be derived entirely from the transaction data.• Insert the various CSV files corresponding to the characteristics that were externalized using

Framework Manager. Each CSV file contains a column that corresponds to a column in the key figures CSV file. By right-clicking the various columns and editing the column properties, ensure the columns that provide the linkage between a characteristic and the key figures have the same name. For example, if a key figure column is named Customer and the corresponding column in the customer CSV file is named Customer - Key, then the name of the column in the key figures CSV file can be changed to Customer - Key.

• For each characteristic, create a new dimension, using the key columns, or other attributes of a characteristic, to drive the levels of the dimension. For each level, ensure that the properties for the label, short name, and description are assigned source columns, if applicable.

• For the root level of each characteristic (dimension), ensure it is marked as unique.• SAP BW presentation hierarchies may contain ragged paths, typically in association with the

"not assigned" and "#" nodes in the hierarchy. The gaps in these hierarchies produce blanks at the associated level in the Transformer hierarchy. In Transformer, it is possible to define the text that should be used for blanks (the default text is "<blank>"). A best practice is to define a more appropriate text for blank entries for all such levels.

nbna

Documentation Updates - Troubleshooting GuideThis section contains additions and corrections to the Troubleshooting Guide.

ArrayIndexOutOfBoundsException Error When Running a ReportIf your log contains the error java.lang.ArraryIndexOutOfBoundsException, it indicates a problem that may affect performance. The error is most likely to occur if you have changed your JVM from -hotspot to -server. To resolve the problem perform the following steps.

Steps• Create a file with the name .hotspot_compiler that contains the text exclude java/lang/Long

toString.Save the file to the crn_location/bin directory, or, if you are using WebLogic, save it to the Domain directory that contains the startWebLogic.cmd and startManagedServer.cmd scripts.438494

Readme Updates 47


Locale Mismatch in Cognos Navigator PortletIf you use the Cognos Navigator portlet to view a report, the language used in the report may not match the language used in the browser.

This problem can occur if the locale selected for the portal is different than the default locale of the browser.

To fix this problem, set the locale selection for the portal to nothing selected. If no locale is selected, the portal uses the default locale for the browser.

431139

48 Cognos ReportNet

Index

Symbols.db files, 16

Aaccented characters

not displayed properly, 13Active Directory Server

authenticating in multiple domains, 10enabling single signon, 9

Administrationissues, 15

Administration and Security Guidedocumentation updates, 31, 35

advanced propertiesfor Active Directory Server, 10

aggregatingexternalized query subjects, 43

aggregation and rollups, 42Apache

configuring gateway, 26ArrayIndexOutOfBoundsException errors, 47associating

queries to pages, 18attachments

Lotus Notes, 25audit reports, 38authentication

in domain trees for Active Directory Server, 10authentication providers

Linux, 13authentication with single signon

for Active Directory Server, 9axis minimum

calculated in charting, 11

BBAPI errors, 19BLOBS, 22business names

preserving during import, 42

Ccaching queries, 17calculations

SAP BW data sources, 19, 21cascading prompts

optional, 12cert7.db file, 16characteristic query subjects

externalizing, 44

chartingenhanced, 10

chartscalculated axis minimum, 11repeating palette assignment, 10shared maximum, 11skip interval and skip interval start, 12

chaseReferrals, 10CLOBs, 22Cognos Configuration

issues, 16Source control systems parameter not available on Linux,

14Cognos Portal Services

improved security, 35Cognos Report Studio

issues, 17product limitations, 14

Cognos Report Studio User Guidedocumentation updates, 38, 39

CombinationType properties, 17compatability switch

Lotus Notes, 25configuring

issues, 13ReportNet gateway, 26SAP Web Application Server, 27

confirmevent-based scheduling for report, 32, 41

copyright, 2custom formatting

not appearing for empty cells, 20custom portal pages

supporting, 35

Ddata ordering

inconsistencies, 17data sources

problems, 25data type error, 23database connectivity

requirements for content store, 29databases

known issues, 25DB2

database connectivity, 29decimals, 39default font

reports, 17disabling

event-based schedules, 33

Readme Updates 49

Index

distributing reportsto a printer, 38, 40

documentation updatesAdministration and Security Guide, 31, 35Cognos Report Studio User Guide, 38, 39Framework Manager User Guide, 42Installation and Configuration Guide, 26Query Studio User Guide, 39ReportNet User Guide, 39SAP BW data sources, 42Troubleshooting Guide, 47

domainsauthentication in domain trees for Active Directory Server,

10double-byte characters

not displayed properly, 13drilling through

Powerplay Enterprise Server to ReportNet, 15reauthentication prompts, 15

drill-through reportsviewing with Safari, 17

Eerrors

ArrayIndexOutOfBoundsException, 47RSV-SVR-0015, 14SDK Custom Authentication JDBC Provider sample, 16

event-based schedulingconfirm for report, 32, 41disable, 33scheduling reports based on event, 31, 32, 40, 41

eventslogging, 37set up trigger events on server, 33

Exceldisplaying images, 24displaying text columns with numbers, 24format, 39known issues, 24multiple outputs, 25supporting SSL, 39

excelmultiple pie charts, 24

exportingIQD files, 23query subjects, 43

expressionsissues when using SAP BW data sources, 18

externalizingcharacteristic query subjects, 44Framework Manager requirements, 45InfoCube key figures, 44model query subjects, 44query subjects, 43SAP BW Query key figures, 45, 46SAP BW Query requirements, 45SAP BW query subjects, 43

extracting SAP BW, 43

Ffeatures

new, 9fonts

default, 17Framework Manager

issues, 22SAP BW data sources, 23Source control systems parameter not available on Linux,

14Framework Manager User Guide

documentation updates, 42functions

OLAP, 43using native data source, 22

Ggrouping columns

SAP BW data sources, 19

Hheader positions

specifying, 12

IIBM DB2 MVS 7.1, 25IBM pSeries Linux

Source control systems parameter not available, 14IIS Web server

single signon with Active Directory, 9images

displaying in Excel, 24importing

preserving business names, 42time data types, 23

InfoCube key figuresexternalizing, 44

Installation and Configuration Guidedocumentation updates, 26

installingCognos business package for Cognos Portal Services on

SAP Enterprise Portal 6.0, 36issues, 13ReportNet on Linux, 13

Integrated Windows Authenticationissues, 15

Internet Explorer, 14IQD files

problems exporting, 23

JJDBC

database connectivity for content store, 29JDBC drivers, 16JRE versions JAR file versions, 31

Kkey3.db file, 16

50 Cognos ReportNet

Index

known issuesAdministration, 15Cognos Configuration, 16Cognos Report Studio, 17databases, 25drilling through to Cognos ReportNet from Series 7, 15Excel, 24Framework Manager, 22general, 14Lotus Notes, 25SAP BW data sources, 18security, 15Series 7 integration, 14

Llast day of month schedules, 34LDAP namespaces

starting ReportNet, 16limitations, 14limited local processing

error when running a large query, 20errors, 19sort order, 20

linkingsegmented namespaces, 22

Linuxauthentication providers, 13characters not displayed properly, 13source control systems item missing, 14Source control systems parameter not available, 14

Linux PDF printing restriction, 38, 40LOBs, 22local processing

SAP BW data sources, 21locale mismatch, 48logging

events and messages, 37messages, levels, 37native query, 38

logging levels, 37logging on

problems, 16lotus compatability switch, 25Lotus Notes, 25

known issues, 25ReportNet report attachments, 25

Mmacros

prompts, 23maximum rows, 19measures

SAP BW data sources, 19member unique names

sort order, 20messages

logging, 37Microsoft Excel

supporting SSL, 39Microsoft Excel 2000, 24

Microsoft SQL Serverdatabase connectivity, 29

Microsoft SQL Server 2005supported, 9

model query subjectsexternalizing, 44

MultiDomainTrees, 10multiple instances of ReportNet

renaming the service, 29

Nnamespaces

links to segmented, 22segmented, 22

native data source functions, 22native query

logging, 38nested query items

SAP BW data sources, 21new features, 9

Active Directory single signon, 9cascading prompts, 12domain authentication, 10enhanced charting, 10Microsoft SQL Server 2005, 9prompting security, 12report header position, 12restruct users display, 12

OOLAP

function names, 43OP-ERR-0073 errors, 18Oracle

database connectivity, 29Oracle databases

proxy connections, 36virtual private databases, 36

Ppages

associating queries, 18palette assignment

charts, 10PCA-ERR-0087 errors, 20PDF

not created, 14PDF printing

Linux restriction, 38, 40permissions

report views, 35pie charts, 24PowerCubes

building from SAP BW data, 46Framework Manager guidelines, 46Transformer guidelines, 47

PowerPlay Enterprise Serverdrilling through to ReportNet, 15publishing to ReportNet, 15

Readme Updates 51

Index

printingreports, 38, 40

problems logging onto a Series 7 namespace, 16product limitations, 14prompts

enhanced security, 12error, 23optional cascading, 12saving, 12

propertiesCombinationType, 17RSVP.PARAMETERS.SAVE, 12

property valuesupdate query subject, 23

proxy connections, 36publishing to ReportNet from PowerPlay Enterprise Server,

15

Qqueries

associating to pages, 18Query Studio

product limitations, 14Query Studio User Guide

documentation updates, 39query subjects

testing, 22

Rreauthentication prompts, 15renaming the ReportNet service, 29Report Studio, See Cognos Report Studioreport tables

sizing, 14report views

permissions, 35ReportNet

lotus compatability switch, 25publishing from PowerPlay Enterprise Server, 15version, 26

ReportNet gatewaychanging, 26

ReportNet servicerenaming, 29

ReportNet User Guidedocumentation updates, 39

reportsdata ordering, 17default font, 17delivery method, 17event-based, 31, 32, 33, 40, 41executing, 17printing, 38, 40schedule last day of month, 34sorting null values, 17

repositoriessharing, 23

requirementsdatabase connectivity for content store, 29

resetting property values, 23

reusing queriesReport Studio, 17

Rollup Processing propertyFramework Manager, 42

rounding decimals, 39RSV-SVR-0015 error, 14

SSafari

viewing drill-through reports, 17samples

SDK Custom Authentication JDBC Provider, 16SAP BW data sources

BAPI errors, 19calculations, 19considerations when using, 42errors when filtering, 18errors while executing large queries, 20filtering nested query items, 21Framework Manager, 23grouping columns, 19known issues, 18local processing, 21maximum rows, 19measures, 19restrictions when creating expressions, 18sectioning reports, 20semi-additive key figures, 21summary rows, 22unit formats, 21

SAP BW Query key figuresexternalizing, 45

SAP BW query subjectsexternalizing, 43

SAP Web Application Server, 27schedules

confirm event-based for report, 32, 41creating for last day of month, 34reports based on events, 31, 32, 40, 41set up trigger events on server, 33

SDK Custom Authentication JDBC Provider sample, 16sectioning reports

SAP BW data sources, 20Security

issues, 15security

enhanced prompting, 12issues with Integrated Windows Authentication, 15issues with the SDK Custom Authentication JDBC

Provider sample, 16LDAP namespaces, 16

segmented namespaceslinks, 22

semi-additive key figuresSAP BW data sources, 21

Series 7known issues, 14

Series 7 namespacesproblems logging on, 16

shared maximumcharting, 11

52 Cognos ReportNet

Index

show users in the list, 12signed URLs, 24single signon

for an Active Directory namespace, 9issues with Integrated Windows Authentication, 15

skip intervalcharting, 12

skip interval startcharting, 12

sortingdifferent order, 20null values in reports, 17

Souce control systemsparameter not available on Linux, 14

SourceSafesharing repositories, 23

specifyheader positions, 12

SSLsupport in Microsoft Excel, 39

stylesheetfonts.css, 17

summary rowsSAP BW data sources, 22

supportingcustom portal pages, 35

system.xmlset up triggers for event-based scheduling, 33

Ttesting

query subjects, 22text columns

displaying in Excel, 24third-party data sources

importing, 22time data types

importing, 23Tomcat application servers, 13

upgrading, 13total values

SAP BW data sources, 22transferring the ReportNet passport ID as a URL parameter,

35trigger events

set up on server, 33set up triggers for event-based scheduling, 33

Troubleshooting Guidedocumentation updates, 47

Uunit formats

SAP BW data sources, 21update query subject

property values, 23upgrading, 13

supported upgrade paths, 26URLs

signatures, 24Use Local Cache property, 17

usersrestrict display, 12

Vvariables

using when externalizing, 46version

ReportNet, 26support for upgrading, 26

version of document, 2viewing reports

Excel format, 39virtual private databases, 36

WWeb servers

single signon with Active Directory and IIS Web server, 9web servers

configuring an Apache gateway for ReportNet, 26WebSphere, 14Windows

renaming the ReportNet service, 29

Readme Updates 53

Index

54 Cognos ReportNet

Date post:	03-Feb-2022
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times

Cognos(R) ReportNet Readme

Documents