Cognos ReportNetTM Installation and Configuration Guide

COGNOS (R) ENTERPRISE BUSINESS 

INTELLIGENCE 

COGNOS REPORTNET TM INSTALLATION AND 

CONFIGURATION GUIDE 

Installation and Configuration Guide 

13-08-2003 

CR Transfer 

1.02MR1 

Type the text for the HTML TOC entry 

Type the text for the HTML TOC entry 

Cognos ReportNet (TM) Readme 

ReportNet (TM) Installation and Configuration Guide 

Cognos ReportNet TM verson 1.02 MR1 

1.02 

Installation and 

THE NEXT LEVEL 

OF PERFORMANCE (TM)

Product Information 

This document applies to Cognos ReportNet TM verson 1.02 MR1 and may also apply to subsequent releases. To check for newer versions of 

this document, visit the Cognos support Web site (http://support.cognos.com). 

This edition published 2003. 

Copyright 

Copyright (C) 2003 Cognos Incorporated 

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. 

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. 

Information about Cognos Products and Accessibility can be found at www.Cognos.com

Table of Contents 

Introduction 7 

Additional Materials 9 

Chapter 1: ReportNet 11 

Infrastructure Resources 11 

Cognos Components 11 

ReportNet Installation Options 12 

Installing All Components On One Computer 12 

Installing ReportNet Gateways On A Separate Computer 13 

Installing Report Servers and Content Manager on Separate Computers 13 

Framework Manager Installation Options 15 

Web Servers Other Than Microsoft IIS 15 

Microsoft IIS Web Servers 15 

Chapter 2: Installing ReportNet on UNIX 17 

System Requirements for UNIX 17 

Default Settings for UNIX 19 

Create the Database for the Content Store 19 

Install ReportNet on UNIX 22 

Set Up the Database Client for the Content Store Database 23 

Update Your Java Environment 24 

What’s Next? 24 

Chapter 3: Installing ReportNet on Windows 25 

System Requirements for Windows 25 

Default Settings for Windows 26 

Create the Database for the Content Store 27 

Install Cognos ReportNet on Windows 30 

Set Up the Database Client for the Content Store Database 30 


Chapter 4: Configuring ReportNet 33 

Start Cognos Configuration 33 

Configuring Single Computer Installations 33 

Configuring Your Web Server 34 

Set the Database Connection Properties for the Content Store 34 

Configure a Mail Server Account 35 

Configuring Web Browsers 36 

Test the Installation and Configuration 36 

Configuring Distributed Installations 37 

Configuring the Content Manager Computer 38 

Configuring Report Server Computers 38 

Configuring Gateway Computers 39 

Finishing the Configuration of Distributed Installations 40 

Installation and Configuration Guide 3

Changing Default Configuration Settings 40 

Change a Port Number 40 

Using an Authentication Provider 41 

Configure Cryptographic Settings 46 

Configure the SSL Protocol 47 

Configure Temporary File Properties 49 

Specify Where to Send Log Messages 49 

Configure ReportNet to Use Alternate Gateways 51 

Configure the Gateway to Use a Namespace 53 

Enable and Disable Services 53 

Specify the Amount of Resources the ReportNet Service Uses 54 

Change Global Settings 54 

Configuring Fonts 58 

Change the Default Font for Reports 59 

Configure Cognos Portal Services 60 


Chapter 5: Installing Framework Manager 63 

System Requirements for Framework Manager 63 

Default Settings for Framework Manager 64 

Install Framework Manager 64 


Chapter 6: Configuring Framework Manager 67 

Start Cognos Configuration 67 

Configure Framework Manager for Distributed Installations 67 

Changing Default Configuration Settings 68 

Change a Port 68 

Configure SSL Protocol 69 

Configure Temporary File Properties 71 

Configure Cryptographic Settings 71 

Configure a Source Control System 72 

Change the Gateway URI to Use an Alternate Gateway 73 

Setting Up Data Sources 73 

Test the Framework Manager Installation and Configuration 75 


Chapter 7: Advanced Configuration Options 77 

Change the JVM Used by ReportNet 77 

Configuring ReportNet to Use An Alternative Application Server 78 

Configure ReportNet to Use a WebSphere Application Server 78 

Configure ReportNet to Use a WebLogic Application Server 81 

Preparing Your Environment If ReportNet Previously Used Tomcat 86 

Configuring ReportNet to use a Third-Party Certificate Authority 87 

Generate Keys and Signing Requests 87 

Configure ReportNet to use a Third-Party Certificate Authority 89 

Chapter 8: Setting Up the Samples 91 

Restore Backup Files for the Samples Databases 91 

Create Data Source Connections to the Samples Databases 92 

Modify the Sample Model for Oracle and DB2 93 

Import the Samples 93 

Remove the Samples from ReportNet 94 

Sample Model 95 

Chapter 9: Setting Up an Unattended Installation and Configuration 97 

Set Up an Unattended Installation 97 

Set Up an Unattended Configuration 99 

4 Cognos ReportNet TM

Chapter 10: Uninstalling Cognos ReportNet 101 

Uninstall ReportNet on UNIX 101 

Uninstall ReportNet on Windows 101 

Uninstall Framework Manager 102 

Appendix A: Manually Configuring ReportNet 103 

Manually Change Default Configuration Settings 103 

Add a Component to Your Configuration 104 

Manually Change the Global Settings 105 

Run Cognos Configuration in Silent Mode 106 

Appendix B: Troubleshooting 107 

Unable to Start ReportNet 108 

Current Configuration Settings Are Not Applied to Your Computer 108 

Unable to Start Cognos Configuration Because the Configuration Data is Locked by Another 

Instance of Cognos Configuration 109 

Unable to Save Your Configuration 109 

Error Trying to Encrypt Information When Saving Your Configuration 109 

Fonts Do Not Appear Properly in the Configuration Tool User Interface 109 

DB2 Returns SQL1224N Error When Connecting from AIX 110 

Cognos BI Server Not Available When Opening the Portal 110 

Web Server Error When Trying to Browse Images 112 

Font on UNIX Not Found When Starting Cognos Configuration 113 

Entries and Folders in the Cognos Web Portal Sorted Incorrectly 113 

DPR-ERR-2022 and DPR-ERR-2058 Errors Appear in Web Browser When Starting the 

Web Portal 114 

Report Link in Email Notification Does Not Work 114 

Unable to Uninstall Another Version of ReportNet Service on Windows 114 

Database Connectivity Errors When Running Reports 115 

Unable to Exit a Tab Sequence When Using Keyboard-Only Navigation in Cognos 

Configuration 115 

PDF Report Does Not Print But Print Status Shows Succeeded 115 

PDF Outputs Too Large 115 

Appendix C: Database Schema for Log Messages 117 

Table Definitions 117 

Logging Conditions 117 

Appendix D: Database Clean Up Scripts 119 

Delete Tables from Databases Used by ReportNet 119 

Glossary 121 

Index 125 



Introduction 

This document is available as online help and as an online book. For information about related 

documents, see "Additional Materials" (p. 9). 

ReportNet 

ReportNet is a Web product for creating and managing ad hoc and managed reports. 

Installation and Configuration Guide 

This document gives instructions for installing and configuring ReportNet. 

To use this guide, you should have basic Windows and/or UNIX administration skills. You should 

be familiar with the existing server environment and security infrastructure in your organization. 

You should also understand basic security concepts. 

Questions or Comments? 

For additional technical information about using ReportNet, visit the Cognos support Web site 

(http://support.cognos.com). 


Introduction 


Additional Materials 

In this guide, we refer to other documents. Their locations are listed below. 

Topic 

How to set ReportNet security 

Securing your content store 

How to manage ReportNet 

services 

How to deploy data 

How to configure ReportNet using 

Cognos Configuration 

How to plan the ReportNet 

architecture, develop installation 

strategies and optimize 

performance 

How to install and set up source 

control systems 

Log failover and recovery 

mechanism. 

How to identify and troubleshoot 

problems with ReportNet 

How to install and migrate Series 

7 Architect models and 

Impromptu Catalogues to 

Framework Manager 

How to deploy Cognos content 

using a third-party portal 

Location 

ReportNet Administration and 

Security Guide 







ReportNet Configuration Guide 

ReportNet Architecture and 

Planning Guide 

Framework Manager User Guide 

ReportNet Architecture and 

Planning Guide 

ReportNet Troubleshooting Guide 

ReportNet Metadata Migration 

User Guide 

Cognos Portal Services 

Administration Guide 

Formats 

Our documentation includes user guides, tutorial guides, reference books, and other materials 

to meet the needs of our varied audience. 

Online Help 

All information is available in online help. Online help is available from the Help button in a Web 

browser, or the Help menu and Help button in Windows products. All online help is also available 

from the Windows Start menu (Start, Programs, Cognos ReportNet, Documentation). 


Additional Materials 

Books for Printing 

The information in each online help system is available in online book format (PDF). However, 

the information from a given help system may be divided into more than one online book. Use 

online books when you want to print a document or when you want to search the whole 

document. 

You can print selected pages, a section, or the whole book. Cognos grants you a non-exclusive, 

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

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

maintaining the Cognos software. 

Online books are available from the introduction to the online help for each component. 

All online books are available on the Cognos documentation CD. 

You can also read the product readme files and the installation guides directly from Cognos 

product CDs. 


Chapter 1: ReportNet 

Before implementing ReportNet, decide how you will install ReportNet in your environment. You 

can install all ReportNet components on one computer, or distribute them across a network. The 

best distribution option depends on your reporting requirements, resources, and preferences. 

Configuration requirements differ depending on whether you install all components on a single 

or multiple computers. 

Infrastructure Resources 

ReportNet integrates easily into your existing infrastructure by using resources that are in your 

environment. Some of these existing resources are required, such as a Java Virtual Machine or 

a third party database for the content store. Other resources are optional, such as using a 

third-party security provider for authentication. 

By default ReportNet uses Tomcat as an application server. You can configure ReportNet to run 

on application servers such as WebSphere or WebLogic that you currently use in your reporting 

environment. 

Cognos Components 

The following components provide the functionality for ReportNet and are the tools you use. 


Framework Manager is a Windows-based metadata modeling tool for ReportNet. You use 

Framework Manager to create and manage the metadata required for the reporting functions 

performed by ReportNet. The metadata is stored in the ReportNet content store and is 

published to one of the ReportNet reporting tools as a package. 

Report Studio 

Report Studio is a Web-based report authoring tool. Use it to create, present, and distribute 

business intelligence (BI) reports that analyze corporate data according to specific information 

needs. 

Query Studio 

Query Studio is an ad-hoc reporting tool. Use it to retrieve specific information from a data 

source. This data is organized and formatted as a report that you can save, analyze, and 

distribute. 

Cognos Connection 

Cognos Connection is the portal to ReportNet. The portal provides a single access point to your 

corporate data available in ReportNet. Use the portal to view, create, or edit reports to suit your 

business needs. 

Administrators use the portal to administer servers, optimize performance, set access 

permissions and to schedule and distribute reports. 



ReportNet Installation Options 

When you install ReportNet, you specify where to place the ReportNet gateways, report 

servers, and Content Manager. You can install the components using any of these scenarios 

• Install all components on one computer 

This scenario is typically used for a demonstration or proof of concept environment. 

• Install the ReportNet gateway on a separate computer 

In this scenario, the ReportNet gateway and Web server are on one computer, and the 

remaining ReportNet components are on other computers. You may choose this option if 

you have existing Web servers available to handle ReportNet requests. 

• Install report servers and Content Manager on separate computers. 

Choose this scenario to maximize performance, availability, capacity, or security based on 

the processing characteristics of your organization. 

After installing the ReportNet components, you must configure them so they can communicate 

with each other. 

In addition to installing the ReportNet components, you must install Framework Manager, the 

metadata modeling application. No matter which ReportNet installation scenario you follow, you 

can install Framework Manager and the ReportNet content store on a computer separate from 

the server components. 

Installing All Components On One Computer 

You can install all the ReportNet server components on one computer. Choose this scenario for 

proof of concept or demonstration environments where the user load is small. 

Because the ReportNet gateway must be located with the Web server, the single computer must 

also be running a Web server. If your Web server is on UNIX, you must install the 

Windows-based Framework Manager on a separate computer that runs under Windows. 

In the following diagram, all ReportNet components, except Framework Manager, are installed 

on one computer. The content store and Framework Manager, the Windows-based metadata 

modeling application, are located on separate computers. 

Framework 

Manager 

Single Computer Installation of 

ReportNet Server Components 

Web server 

ReportNet gateway 

Report server 

Content Manager 

Content store 

Configuration Requirements 

If you install all ReportNet components on the same computer, you must then 

• configure your Web server to view ReportNet content 

• specify connection information to the ReportNet content store 

• set up an email account for notifications (if you intend to email reports) 



Installing ReportNet Gateways On A Separate Computer 

The ReportNet gateway manages all ReportNet communications. It can reside on one or more 

Web servers. 

You can install the ReportNet gateway and a Web server on one computer, and install the 

remaining ReportNet components on other computers. If you have a Web farm, you may want to 

install a ReportNet gateway on each Web server. Using multiple Web servers to manage 

incoming requests provides a better level of service. 

If you install only the ReportNet gateway component on the same computer as the Web server, 

your Web server manages the core Web services and does not process user requests. This 

separation of processing may be required if you have a firewall between the Web server and 

your ReportNet server. 

In the following diagram, two Web servers each have a gateway installed. Incoming requests are 

passed to either gateway and forwarded to the report server computer. If request information is 

not saved, the result is returned from the report server. If request information is saved, it is 

saved in Content Manager. 

Multiple Gateways 

Installation 

Web server 


Web server 


Report server 



If you install one or more ReportNet gateways on a separate computer, you must ensure that 

you can view ReportNet content and that the gateways can communicate with other ReportNet 

components. On each computer where the ReportNet gateway is installed you must 

• configure cryptographic properties 

• configure your Web server to view ReportNet content 

• configure the Dispatcher URI 

Installing Report Servers and Content Manager on Separate Computers 

One or more report servers use the Cognos Connection interface to balance loads, access data, 

perform queries, schedule jobs, and render reports. Content Manager stores all report 

specifications, results, packages, folders, and jobs in the content store. 

You can install the report servers and Content Manager on the same computer, or on different 

computers. Installing on different computers can improve performance, availability, and capacity. 

To improve scalability in an environment in which there is typically a large volume of report 

requests to process, you can install the report server on multiple computers dedicated to 

processing incoming requests. By installing the report server on multiple computers, you 

distribute and balance loads among the computers. You also have better accessibility and 

throughput than on a single computer, as well as failover support. 



In the following diagram, incoming requests are routed to a ReportNet gateway. The gateway 

forwards the request to one of the report servers. The report server forwards the request to 

Content Manager, which queries the content store and sends the results back to the report 

server for rendering. 

Multiple Report Servers 

Installation 

Web server 


Web server 


Report servers 



If you install one or more report servers on a separate computer, to ensure that the report server 

can communicate with other ReportNet components you must 


• specify the Content Manager URI 

• specify the Dispatcher URI 

• specify the SDK URI 

Separate Content Manager 

There is only one Content Manager and one content store for each installation of ReportNet. 

Content Manager stores all ReportNet information in a relational database management system 

(RDBMS). 

You may choose to install Content Manager separately from the ReportNet report servers if your 

data contains sensitive information. Data is then stored in the data tier along with your security 

information. 

You may also choose to install Content Manager on a separate computer if large volumes of 

data are managed by Content Manager. In this type of environment, ReportNet scalability can 

be improved by increasing the size of the processor on which Content Manager is installed. 


On the computer where you install Content Manager, you must 


• specify connection information to the content store 

• specify the Dispatcher URI 

• Specify the Content Manager URI 

• specify the SDK URI 

• setup an email account for notifications (if you want to email reports) 



Framework Manager Installation Options 

No matter where you install the ReportNet components, you must also install and configure 

Framework Manager, the metadata modeling application. 

Framework Manager stores run-time models on the ReportNet server. It can communicate with 

the server using one of two routes: 

• Route 1: through the Web server gateway 

• Route 2: directly to the ReportNet server dispatcher 

Route 1. Route 2. 

Framework 

Manager 

Framework 

Manager 

Web server 


Web server 


ReportNet server 


Dispatcher 

Dispatcher 

Where you install Framework Manager, and how you configure it, can depend on how large your 

metadata models are and on which Web server you use. 

Web Servers Other Than Microsoft IIS 

For Web servers other than Microsoft Internet Information Services (IIS), there is no functional 

difference between the two communication routes between Framework Manager and the 

ReportNet server dispatcher. For either route, Framework Manager uses the BI Bus SOAP API. 

If you use the Web server route, and you have medium-sized and large models (approaching 1 

MB in size), the models are broken into smaller pieces (chunked) for transmission. 

If you use a Web server other than Microsoft IIS, we recommend that you configure Framework 

Manager to communicate through your Web server gateway (Route 1). This eliminates the need 

to set up additional communications channels if you use firewalls to separate Framework 

Manager, your Web server, and your ReportNet server. 

Microsoft IIS Web Servers 

Microsoft IIS does not support chunking. As a result, if you use Microsoft IIS, and you build 

medium-sized or large models (approaching 1 MB in size), you must configure Framework 

Manager to communicate directly with the ReportNet server dispatcher. 



Firewall Considerations 

When Framework Manager communicates directly with the dispatcher, communications issues 

can arise. If Framework Manager is installed outside a firewall that protects the ReportNet 

server, measures must be taken to ensure that communication can occur through the firewall, as 

shown below. 

Framework 

Manager 

Firewall 

Firewall 

Communication with 


1 

2 

3 3 

Web server 


ReportNet 

server 

To avoid this requirement, you can install Framework Manager in the same architectural tier as 

the ReportNet server, as shown below. 

Firewall 

Framework 

Manager 

Firewall 

1 

2 

Web server 


ReportNet 

server 

Communication with 


3 3 


Framework Manager communicates with the ReportNet server, which can be installed on one or 

more Web servers. To publish models, you must configure Framework Manager to communicate 

with the dispatcher, either through the gateway or directly. This is done by configuring the SDK 

URI. 

You must ensure that Framework Manager can communicate with ReportNet components. On 

the computer where Framework Manager is installed, configure cryptographic properties and 

the following environment properties: 

• Gateway URI 

• SDK URI 


Chapter 2: Installing ReportNet on UNIX 

To install ReportNet, use the installation wizard to copy the components to your computer. You 

can install all components on one computer or across several computers. 

Use this checklist to guide you through the installation process: 

❑ Check your system requirements. 

❑ Review the ReportNet default settings. 

❑ Create the database for the content store. 

❑ Install ReportNet. 

❑ Set up the database client for the content store (Oracle and DB2). 

❑ Update your Java Runtime Environment. 

After you complete these tasks, you must configure the ReportNet components (p. 33) to work 

in your environment. 

System Requirements for UNIX 

Before you install ReportNet, ensure that your computer meets ReportNet’s software and 

hardware requirements. The hardware requirements depend on your reporting environment. 

You may require additional resources, such as disk space. 

The following table lists the minimum hardware and software requirements to run ReportNet. 

Requirement 

Operating system 


specifications 

Disk space 

Web server 

JRE 

Database 

Specification 

One of the following: 

• Sun Solaris 

• HP-UX 

• IBM AIX 

File descriptor limit set to 1024 on Solaris 

(recommended) 

Minimum: 1 GB 

A Web server installed and started 

Version 1.3.1 of a Java Runtime Environment 

(JRE) 

• Sun Solaris: 1.3.1_07 

• HP-UX: 1.3.1_08 

• IBM AIX: 1.3.1 (ca131-20030122a) 

One of the following databases available to 

store Cognos data: 

• Oracle 

(version 8.1.7.2 or later if Oracle Server is 

on a different operating system from 

ReportNet) 

• DB2 

• Microsoft SQL Server 



Requirement 

Web browser 

Other 

SAP BW 

Specification 

For all Web browsers, the following enabled: 

• cookies 

• JavaScript 

For Microsoft Internet Explorer only, the 

following enabled: 

• Run ActiveX controls and plug-ins 

• Script ActiveX controls marked safe for 

scripting 

• Active scripting 

For a terminal emulator to install Cognos 

products, the emulation set to VT220 

equivalent or better to ensure that the hot keys 

in the Installation wizard work 

If you want to email reports, the ability to use a 

mail server 

The following SAP Front-End components 

installed on each ReportNet server computer: 

• SAP GUI 6.20 

• BW Add-on 

Database Connectivity for the Reporting Database 

The 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 Windows, the report server supports 

either native database connectivity or ODBC. On UNIX, the report server supports the native 

database connectivity. Also on UNIX, for Microsoft SQL Server only, the report server supports 

the Data Direct ODBC driver for Microsoft SQL Server. This driver is available from Data Direct. 

Database Connectivity for the Content Store Database 

The database client software for the database that is used as the content store must be installed 

and configured on the computer where you install Content Manager. For Oracle databases, 

Content Manager uses the JDBC thin client, classes12.jar. For DB2 databases, Content 

Manager uses the JDBC thick client. For Microsoft SQL Server, the data connectivity is included 

in ReportNet and no other connectivity is required. 

Supported Environments 

You 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 apply all required 

operating system patches and to use only the versions of third-party software that are supported 

for a Cognos product. Otherwise, your product may not work properly. 



Default Settings for UNIX 

The following table lists the default ReportNet ports and URI settings. After installation, you can 

use the configuration tool to change the settings. You can also change them by editing the 

crnstartup.xml file in the crn_location/configuration directory. 

Setting Default Description 

Content Manager URI 

Gateway URI 

Dispatcher URI 

SDK URI 

http://localhost:9300/p2pd 

/servlet 

http://localhost:80/crn/cgibin/cognos.cgi 


/servlet/dispatch 



The URI to Content Manager 

The URI to the ReportNet 

gateway 

The URI to the dispatcher 


Log server port 9362 The port used by the local log 

server 

The following table lists the default settings used by ReportNet for Tomcat. The non-SSL and 

SSL connectors are automatically updated in the server.xml file when you use Cognos 

Configuration to change the dispatcher port (p. 40) or to enable the SSL protocol (p. 47). You 

can directly update the shutdown port using Cognos Configuration. 

. 

Setting Port Description 

Non-SSL Coyote HTTP/1.1 

Connector 

SSL Coyote HTTP/1.1 

connector 

9300 The port Tomcat uses to pass 

requests from the Web server 

to ReportNet 

9334 The port Tomcat uses to listen 

for secure connections 

Shutdown port 9399 The port Tomcat uses to listen 

for a shutdown command 

Create the Database for the Content Store 

You must create the database that is used for the content store using either Oracle, Microsoft 

SQL Server, or DB2 UDB. ReportNet uses this database to store, organize, and retrieve 

information. 

The database you create must use UTF-8 encoding. 

It is important to note that for each installation, ReportNet uses a single sort order that specifies 

the rules used by the database to interpret, collect, compare, and present character data. For 

example, a sort order defines whether the letter 'a' is less than, equal to, or greater than the 

letter 'b', whether the collation is case-sensitive; and whether the collation is accent-sensitive. 

Your database administrator must back up the ReportNet content store regularly because it 

contains all the ReportNet data. To ensure the security and integrity of the content store, it is 

also important to protect the database from unauthorized or inappropriate access. 

Steps for Microsoft SQL Server 

1. If you performed a Typical installation of Microsoft SQL Server, after you install you must 

change the authentication mode to SQL Server and Windows. 

For more information, see the knowledge base article 269587 on the Microsoft Web site. 



2. Create the database. 

If you modified the default settings when you installed Microsoft SQL Server, you must 

specify a database collation sequence for the content store that is case-insensitive. 

3. Determine which user account ReportNet will use to access the content store. 

4. Grant create and drop table privileges for the content store to the user account. 

Ensure that the user account is a member of the db_ddladmin role. 

Steps for Oracle 

1. Set the appropriate environment variables for the Oracle database. 

Environment variable 

ORACLE_HOME 

TNS_ADMIN 

NLS_LANG 

Description 

The top level directory that contains the 

database client software or the entire 

database installation. 

The directory that contains the Oracle 

file tnsnames.ora. This file calls the 

Oracle database to determine the 

required server connections. 

This setting provides support for 

multilingual databases. Its three 

components are: language, territory, 

and character set: 

NLS_LANG = 

language_territory.charset 

Ensure the charset is UTF8, UTF16, 

AL32UTF8, or AL16UTF16. 

2. If you use Oracle 8.1.7, ensure that the compatibility level parameter of the content store is 

set to 8.1 and not to the default setting of 8.0. 

For information about changing an instance configuration parameter, see the Oracle 

documentation. 

3. In SQL Plus, determine if the database is unicode by typing the following select statement: 

select * from NLS_DATABASE_PARAMETERS 

The result set returns NLS_CHARACTERSET is UTF-8 or UTF-16, or AL32UTF8 or 

AL16UTF16, or not unicode. 

4. If the result set returns NLS_CHARACTERSET is not unicode, create the database. 

• For Oracle 8.1.7, ensure that you specify UTF-8 or UTF-16 as the character set for the 

national character set and the database character set parameters. 

• For Oracle 9i, specify AL32UTF8 or AL16UTF16 as the character set for the national 

character set and the database character set parameters. 



Ensure that the user account is granted the CONNECT and RESOURCE roles. 



Steps for DB2 

1. Set the appropriate environment variables for DB2. 


DB2DIR 

On Solaris: 

LD_LIBRARY_PATH 

On AIX: LIBPATH 

On HP-UX: SHLIB_PATH 

DB2INSTANCE 

DB2CODEPAGE 

Description 

The top level directory that contains 

the database client software or the 

entire database installation. 

The load library path.You must add 

driver location. 

Examples: 

Solaris example: 

LD_LIBRARY_PATH=$DB2DIR/lib: 

$LD_LIBRARY_PATH 

AIX example: 

LIBPATH=$DB2DIR/lib: $LIBPATH 

HP-UX example: 

SHLIB_PATH=$DB2DIR/lib: 

$SHLIB_PATH 

The default database server 

connection. 

Setting this optional environment 

variable to a value of 1208 provides 

support for multilingual databases. 

For information about whether to 

use this environment variable, see 

the DB2 documentation. 

2. Determine if the database is unicode by typing the following at the command prompt: 

db2 get database configuration for database_name 

The codepage is Unicode if it has a value of 1208. 

3. If the codepage is not Unicode, create a database that has a codepage value of 1208. 

4. Ensure that you set the following configuration parameters. 

Property 

Application heap size 

(applheapsz) 

Lock Timeout 

Setting 

1024k 

4 min. (or 240 sec.) 

We recommend that you set the Lock Timeout configuration parameter to a reasonably 

long timeout value, such as four minutes or 240 seconds. Do not set it to an infinite timeout 

value. 

5. Create a buffer pool with a page size of 16k. 

6. Create a system temporary tablespace with a page size of 16k. 

7. Create a user temporary tablespace with a page size of 4k. 




9. Grant create and drop table privileges on the content store to the user account. 

Ensure that the user account has CREATETAB, CONNECT and IMPLICITSCHEMA 

privileges for the content store. 

Ensure that the user account has USE privileges for the USER TEMPORARY tablespace 

and other appropriate tablespaces associated with the content store. 

For Windows XP, ensure that the user account has GRANT privileges for the USER 

TEMPORARY tablespace. 

Install ReportNet on UNIX 

Use the installation wizard to select the components you want to install and the location on your 

computer where you want to install them. Only the components that you choose to install are 

copied from the CD to your computer. 

Tip: You can install the gateway and Report Server components on multiple computers. You 

install Content Manager on only one computer. 

Install ReportNet components using either a character-based interface or a graphical user 

interface. To run graphical-mode installation, the console attached to your UNIX computer must 

support a Java-based graphical user interface. 

ReportNet respects the file mode creation mask (umask) of the account running the installation 

program. This affects only the installation directories. It does not affect the file permissions 

within the directories. However, run-time generated files, such as logs, respect the umask. We 

recommend umask 022 on the installation directory. 

Ensure that you verified your system requirements (p. 17) and that you created the database for 

the content store. Ensure also that required third-party software, such as a Web server and a 

Java Virtual Machine, is available. 

Ensure that if ReportNet uses a relational database as a data source for metadata, you set the 

environment variables for these databases. 

Tip: If you plan to use ReportNet with a third party application server, such as WebSphere or 

WebLogic, to avoid file permission conflicts, create a new UNIX group. You could call this group 

reportnet. This group must contain the user that starts the application server and the user that 

owns the ReportNet files. Change the group ownership of the ReportNet files to the reportnet 

group and change the file permissions for all ReportNet files to GROUP 

READABLE/WRITABLE/EXECUTABLE. 

Steps 

1. Set the JAVA_HOME environment variable to point to the location of your Java Runtime 

Environment (JRE). 

2. Mount the ReportNet CD with Rock Ridge file extensions. 

Important: To mount the Cognos CD on HP-UX, do the following: 

• Confirm that the pfs_mount daemons are running by typing 

ps | grep pfs 

• If the pfs_mount daemons are not running, type 

bg pfs_mountd 

bg pfsd 

• Type 

pfs_mount -t rrip /Device Name/cd-rom 

• Type 

pfs_umount 

• Stop the pfsd and pfs_mountd daemons to unmount the CD. 



3. Go to the directory that is appropriate for your operating system and start the installation: 

• If you use XWindows, type 

./xstartup 

• If you do not use XWindows, type 

./xwsetup 

4. Follow the directions in the installation wizard and copy the required files to your computer. 

5. Choose how to proceed in the Finish page of the installation wizard: 

• We recommend that you do not configure ReportNet immediately because you must do 

other tasks first to ensure that your environment is properly set up. However, if the 

console attached to your computer supports a Java-based graphical user interface, you 

can click Start Cognos Configuration 

• If you want to see late-breaking information about Cognos ReportNet, select View the 

Readme and then select Finish. 

Tip: For character-mode installations on UNIX, close the readme text file by pressing 

Crtl + C or q. 

• If the console attached to your computer does not support a Java-based graphical user 

interface or if you want to configure ReportNet later, click Finish. 

You can later configure ReportNet using Cognos Configuration by starting crconfig.sh in 

the crn_location/bin directory, or editing crnstartup.xml in crn_location/configuration 

directory. 

6. On HPUX, append the crn_location/bin directory to the SHLIB_PATH environment variable. 

If you use Oracle or DB2, you can now set up the database client for the content store. You must 

update your Java security framework. 

Set Up the Database Client for the Content Store 

Database 

If you use Oracle or DB2 as the database server for the content store, additional steps are 

required after you install ReportNet before you can configure ReportNet. 

If you use an Oracle database for the content store, you must set up the JDBC driver. 

If you use a DB2 database for the content store, you must set up the database client software 

and the JDBC 2.0 driver. 

If you use a Microsoft SQL Server database, the JSQLConnect.jar file is installed to the 

appropriate location by default and no additional steps are required. 


1. On the computer where Oracle is installed, go to the ORACLE_HOME/jdbc/lib directory. 

2. Copy the classes12.zip file to the crn_location/webapps/p2pd/WEB-INF/lib directory on the 

computer where Content Manager is installed. 

3. Rename the classes12.zip file to classes12.jar. 

Steps for DB2 

1. Install the DB2 client software on the computer where Content Manager is installed. 

2. Run the DB2 Client Configuration Assistant to configure a database alias to the content 

store. 

3. On Windows, stop the DB2 services and the HTML Search Server. 



4. Go to the appropriate directory to copy the JDBC2 driver: 

• For version 7.2, on Windows, go to DB2_installation\java12 directory and run the 

usejdbc2.bat script. 

This copies the JDBC2 driver, db2java.zip, to the DB2_installation/java directory. 

• For version 7.2, on UNIX, go to the DB2_installation/java12 directory. 

• For version 8, go to the DB2_installation/java directory. 

5. Copy the db2java.zip file to the crn_location/webapps/p2pd/WEB-INF/lib directory. 

6. Rename the db2java.zip file to db2java.jar. 

7. On Windows, restart the DB2 services and the HTML Search Server. 

8. On UNIX, for version 7.2, ensure that you include the DB2_installation/java12 directory in 

the library path environment variable and that it comes before the DB2_installation/lib 

directory. 

Update Your Java Environment 

Before 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). 

What’s Next? 

Steps 

1. Check that the following JAR (Java Archive) files exist in the JRE_location/lib/ext: 

• sunjce_provider.jar 

• US_export_policy.jar 

• local_policy.jar 

• jce1_2_1.jar 

• jcert.jar 

• jnet.jar 

• jsse.jar 

• bcprov-jdk13-113.jar 

Tip: An example of the installation location of a Java Runtime Environment is 

/directory/java/java_version/jre. 

2. If any files are missing, go to crn_location/bin/jre/1.3.1/lib/ext directory and copy the 

appropriate JAR files to the JRE_location/lib/ext directory. 

After you install ReportNet components on one or more UNIX computers, some configuration 

tasks are required so that the ReportNet components work in your reporting environment 

(p. 33). 

To deploy Cognos content using a third-party portal such as SAP Enterprise Portal, you must 

complete additional configuration using the portal tools. For more information, see Cognos 

Portal Services Administration Guide. Also, you may have to modify the default property settings 

for Cognos Portal Services using Cognos Configuration. 


Chapter 3: Installing ReportNet on Windows 

To install ReportNet, use the installation wizard to copy the components to your computer. You 

can install all components on one computer or across several computers. 

Use this checklist to guide you through the installation process: 

❑ Verify your system requirements. 

❑ Review the ReportNet default settings. 

❑ Create the database for the content store. 

❑ Install ReportNet. 

❑ Set up the database client for the content store (Oracle and DB2). 

After you complete these tasks, you must configure the ReportNet components (p. 33) to work 


System Requirements for Windows 

Before you install ReportNet, ensure that your computer meets ReportNet’s software and 

hardware requirements. The hardware requirements depend on your reporting environment. 

You may require additional resources, such as disk space. 

The following table lists the minimum hardware and software requirements to run ReportNet. 

Requirement 


RAM 

Disk space 

Web server 

Database 

Specification 

Windows 

Minimum: 512 MB 

Recommended: 1 GB 

Minimum: 1 GB of free space on the drive that 

contains the temporary directory used by the 

ReportNet 

A Web server installed and started 

One of the following databases available to 

store Cognos data: 

• Oracle 

(version 8.1.7.2 or later if Oracle Server is 

on a different operating system from 

ReportNet) 

• DB2 

• Microsoft SQL Server 



Requirement 

Web browser 

Other 

Specification 

For all Web browsers, the following enabled: 

• cookies 

• JavaScript 

For IE only, the following enabled: 


• Script ActiveX controls marked safe for 

scripting 

• Active scripting 

Microsoft Data Access Component (MDAC) 

2.6 or later for use with product samples 

If you want to email reports, the ability to use a 

mail server 

A Web browser configured to accept cookies 

Database Connectivity for the Reporting Database 

The 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 Windows, the report server supports 

either native database connectivity or ODBC. On UNIX, the report server supports the native 

database connectivity. Also on UNIX, for Microsoft SQL Server only, the report server supports 

the Data Direct ODBC driver for Microsoft SQL Server. This driver is available from Data Direct. 

Database Connectivity for the Content Store Database 

The database client software for the database that is used as the content store must be installed 

and configured on the computer where you install Content Manager. For Oracle databases, 

Content Manager uses the JDBC thin client, classes12.jar. For DB2 databases, Content 

Manager uses the JDBC thick client. For Microsoft SQL Server, the data connectivity is included 

in ReportNet and no other connectivity is required. 







Default Settings for Windows 



crnstartup.xml file in the crn_location/configuration directory. 


Content Manager URI 

Gateway URI 

Dispatcher URI 


/servlet 




The URI to Content Manager 


gateway 





SDK URI 




Log server port 9362 The port used by the local log 

server 

The following table lists the default settings used by ReportNet for Tomcat. The non-SSL and 

SSL connectors are automatically updated in the server.xml file when you use Cognos 

Configuration to change the dispatcher port (p. 40) or to enable the SSL protocol (p. 47). You 

can directly update the shutdown port using Cognos Configuration. 

. 

Setting Port Description 

Non-SSL Coyote HTTP/1.1 

Connector 

SSL Coyote HTTP/1.1 

connector 

9300 The port Tomcat uses to pass 

requests from the Web server 

to ReportNet 

9334 The port Tomcat uses to listen 

for secure connections 

Shutdown port 9399 The port Tomcat uses to listen 

for a shutdown command 

Create the Database for the Content Store 

You must create the database that is used for the content store using either Oracle, Microsoft 

SQL Server, or DB2 UDB. ReportNet uses this database to store, organize, and retrieve 

information. 

The database you create must use UTF-8 encoding. 

It is important to note that for each installation, ReportNet uses a single sort order that specifies 

the rules used by the database to interpret, collect, compare, and present character data. For 

example, a sort order defines whether the letter 'a' is less than, equal to, or greater than the 

letter 'b', whether the collation is case-sensitive; and whether the collation is accent-sensitive. 

Your database administrator must back up the ReportNet content store regularly because it 

contains all the ReportNet data. To ensure the security and integrity of the content store, it is 

also important to protect the database from unauthorized or inappropriate access. 

Steps for Microsoft SQL Server 

1. If you performed a Typical installation of Microsoft SQL Server, after you install you must 

change the authentication mode to SQL Server and Windows. 

For more information, see the knowledge base article 269587 on the Microsoft Web site. 

2. Create the database. 

If you modified the default settings when you installed Microsoft SQL Server, you must 

specify a database collation sequence for the content store that is case-insensitive. 



Ensure that the user account is a member of the db_ddladmin role. 




1. Set the appropriate environment variables for the Oracle database. 


ORACLE_HOME 

TNS_ADMIN 

NLS_LANG 

Description 

The top level directory that contains the 

database client software or the entire 

database installation. 

The directory that contains the Oracle 

file tnsnames.ora. This file calls the 

Oracle database to determine the 

required server connections. 

This setting provides support for 

multilingual databases. Its three 

components are: language, territory, 

and character set: 

NLS_LANG = 

language_territory.charset 

Ensure the charset is UTF8, UTF16, 

AL32UTF8, or AL16UTF16. 

2. If you use Oracle 8.1.7, ensure that the compatibility level parameter of the content store is 

set to 8.1 and not to the default setting of 8.0. 

For information about changing an instance configuration parameter, see the Oracle 


3. In SQL Plus, determine if the database is unicode by typing the following select statement: 

select * from NLS_DATABASE_PARAMETERS 

The result set returns NLS_CHARACTERSET is UTF-8 or UTF-16, or AL32UTF8 or 

AL16UTF16, or not unicode. 

4. If the result set returns NLS_CHARACTERSET is not unicode, create the database. 

• For Oracle 8.1.7, ensure that you specify UTF-8 or UTF-16 as the character set for the 

national character set and the database character set parameters. 

• For Oracle 9i, specify AL32UTF8 or AL16UTF16 as the character set for the national 

character set and the database character set parameters. 



Ensure that the user account is granted the CONNECT and RESOURCE roles. 



Steps for DB2 

1. Set the appropriate environment variables for DB2. 


DB2DIR 

On Solaris: 


On AIX: LIBPATH 

On HP-UX: SHLIB_PATH 

DB2INSTANCE 

DB2CODEPAGE 

Description 

The top level directory that contains 

the database client software or the 

entire database installation. 

The load library path.You must add 

driver location. 

Examples: 

Solaris example: 

LD_LIBRARY_PATH=$DB2DIR/lib: 

$LD_LIBRARY_PATH 

AIX example: 

LIBPATH=$DB2DIR/lib: $LIBPATH 

HP-UX example: 

SHLIB_PATH=$DB2DIR/lib: 

$SHLIB_PATH 

The default database server 

connection. 

Setting this optional environment 

variable to a value of 1208 provides 

support for multilingual databases. 

For information about whether to 

use this environment variable, see 

the DB2 documentation. 

2. Determine if the database is unicode by typing the following at the command prompt: 

db2 get database configuration for database_name 

The codepage is Unicode if it has a value of 1208. 

3. If the codepage is not Unicode, create a database that has a codepage value of 1208. 

4. Ensure that you set the following configuration parameters. 

Property 

Application heap size 

(applheapsz) 

Lock Timeout 

Setting 

1024k 

4 min. (or 240 sec.) 

We recommend that you set the Lock Timeout configuration parameter to a reasonably 

long timeout value, such as four minutes or 240 seconds. Do not set it to an infinite timeout 

value. 

5. Create a buffer pool with a page size of 16k. 

6. Create a system temporary tablespace with a page size of 16k. 

7. Create a user temporary tablespace with a page size of 4k. 




9. Grant create and drop table privileges on the content store to the user account. 

Ensure that the user account has CREATETAB, CONNECT and IMPLICITSCHEMA 

privileges for the content store. 

Ensure that the user account has USE privileges for the USER TEMPORARY tablespace 

and other appropriate tablespaces associated with the content store. 

For Windows XP, ensure that the user account has GRANT privileges for the USER 

TEMPORARY tablespace. 

Install Cognos ReportNet on Windows 

Use the installation wizard to select the components you want to install and the location on your 

computer where you want to install them. Only the components that you choose to install are 

copied from the CD to your computer. 

You can install the gateway and Report Server components on multiple computers. You install 

Content Manager on one computer only. 

Ensure that you have administrator privileges for the Windows computer you are installing on. 

Ensure that you verified your system requirements and that you created the content store. 

Ensure also that the required third-party software is available. For example, a Web server must 

be installed and started. 

Ensure that your computer has a TEMP system variable that points to the directory where you 

want to store temporary files. During installation, files from the CD are temporarily copied to this 

directory. 

Tip: If you use a Oracle, see the Oracle documentation about how to set up multilingual data 

access support. 

Before you install ReportNet, we recommend that you close all programs that are currently 

running to ensure that the installation program copies all the required files to your computer. 

Steps 

1. Insert the ReportNet for Windows CD and then open the installation menu. 

The Welcome page of the installation wizard should appear. 

2. If no Welcome page appears, in the win32 directory on the CD, double-click the 

xwsetup.exe file. 

3. Select the language to use for the installation. 

4. Follow the directions in the installation wizard to copy the required files to your computer, 

5. In the Finish page of the installation wizard: 

• If you want to configure ReportNet components immediately, click Start Cognos 

Configuration. 

• If you want to see late-breaking information about Cognos ReportNet, click View the 

Readme. 

6. Click Finish. 

Use the Windows Start menu to start Cognos Configuration from the shortcut folder. 

If you use Oracle or DB2, you can now set up the JDBC drivers for the content store. 

Set Up the Database Client for the Content Store 

Database 

If you use Oracle or DB2 as the database server for the content store, additional steps are 

required after you install ReportNet before you can configure ReportNet. 

If you use an Oracle database for the content store, you must set up the JDBC driver. 

If you use a DB2 database for the content store, you must set up the database client software 

and the JDBC 2.0 driver. 








computer where Content Manager is installed. 


Steps for DB2 


1. Install the DB2 client software on the computer where Content Manager is installed. 

2. Run the DB2 Client Configuration Assistant to configure a database alias to the content 

store. 













directory. 

After you install ReportNet components on one or more Windows computers, some 

configuration tasks are required to ensure that ReportNet components work in your reporting 

environment (p. 33). 

To deploy Cognos content using a third-party portal such as SAP Enterprise Portal, you must 

complete additional configuration using the portal tools. For more information, see Cognos 

Portal Services Administration Guide. Also, you may have to modify the default property settings 

for Cognos Portal Services using Cognos Configuration. 




Chapter 4: Configuring ReportNet 

After you install one or more ReportNet components on your computer, you must configure 

them to work in your reporting environment. Initially, default property settings chosen by Cognos 

are used to configure the components. However, you may want to change these default settings 

if existing conditions make the default choices inappropriate, or to better suit your environment. 

For all Windows and most UNIX installations, use Cognos Configuration to configure your 

settings. However, the console attached to the UNIX computer on which you are installing 

ReportNet may not support a Java-based graphical user interface. You must then manually edit 

the crnstartup.xml file in the crn_location/configuration directory, and then run Cognos 

Configuration in silent mode. 

For all types of installations, some configuration tasks are required. For example, you must 

configure your Web server and specify the database connection properties to the content store. 

If you distribute ReportNet components across several computers, some additional 

configuration tasks are required to ensure that the components can communicate with each 

other. The order in which you configure and start the computers is also important. 

Other configuration tasks are optional and depend on your reporting environment. Use these 

optional configuration tasks to customize your configuration so that ReportNet easily integrates 

into your existing reporting environment. For example, you can add resources to your 

environment, such as configuring ReportNet to use an authentication provider. Also, you can 

deliver Cognos content using an SAP Enterprise Portal by configuring Cognos Portal Services. 

Start Cognos Configuration 

Use the configuration tool, Cognos Configuration, to configure ReportNet components, or to 

start and stop ReportNet services. 

The account under which ReportNet runs must have access to all required resources, such as 

printers and Web servers. For example, on Windows, to print reports using a network printer, the 

account must already have access to the network printer, or you must assign a logon account to 

the ReportNet service. You can configure the ReportNet service to use a special user account 

by selecting the Cognos ReportNet service from the list of services shown in the Services 

window in Windows. 

You should start Cognos Configuration in the last page of the installation wizard on Windows 

and UNIX only if additional setup is not required. For example, if you use an Oracle or DB2 

database server for the content store, we recommend that you copy the JDBC drivers to the 

appropriate location before you start the configuration tool. 

To start Cognos Configuration in interactive mode: 

• On UNIX, go to the crn_location/bin directory and then type 

crconfig.sh 

• On Windows, from the Start menu, click Programs, Cognos ReportNet, Cognos 


Configuring Single Computer Installations 

If you install all ReportNet server components on one computer, some configuration tasks are 

required so that ReportNet works in your reporting environment. 

Additional configuration tasks are required if the Windows modelling tool, Framework Manager, 

is installed on a separate computer. 



If you change the value of a property, you must save the configuration and then restart the 

ReportNet service to apply the new settings to your computer. 

Before you configure ReportNet, ensure that 

• all ReportNet server components are installed on one computer 

• a Web server is installed and running on the same computer as the ReportNet components 

• you created the database for the content store on an available computer in your network 

Use the following checklist to guide you through the required configuration tasks: 

❑ Configure your Web server. 

❑ Set the database connection properties for the content store. 

❑ Configure a mail server account. 

❑ Configure your Web browser. 

❑ Test the installation and configuration. 

After you complete these configuration tasks, you can change the default behavior of ReportNet 

(p. 40) to better suit your reporting environment. 

Configuring Your Web Server 

For all installations, before you use Web pages generated by ReportNet, you must configure 

your Web server. You must set up virtual directories, also known as Web aliases, for the 

directories that contain the HTML and Web files for ReportNet. 

On UNIX, the account under which the Web server runs must have read access to the 

crnstartup.xml in the crn_location/configuration directory. By default the crnstartup.xml file has 

read permission for others. If you run your Web server under a specific group, you can change 

the crnstartup.xml file permissions to ensure that it belongs to the same group as the Web 

server. You can then remove the read permission for others. 

The following virtual directories are required for all Web servers. You can use a name other than 

crn in the aliases. However, you must use cgi-bin and help as the second part of the alias. 

Alias Location Permission 

crn crn_location\webcontent Read 

crn/cgi-bin crn_location\cgi-bin Execute 

crn/help crn_location\webcontent\documentation Read 

Tips 

• If you use Apache Web server, ensure that you define the crn/cgi-bin alias before the crn 

and crn/help aliases in the httpd.conf file located in the Apache_installation/conf directory. 

• If you use Web aliases other than crn, your Web server is on another computer, or you are 

using Microsoft Internet Application Interface (ISAPI), apache_mod or a servlet gateway, 

you must change the value of the Gateway URI property in the Environment group in 

Cognos Configuration. 

• To use Report Studio’s image browser, you must enable Web Distributed Authoring and 

Versioning (WebDAV) on your Web server. For information about configuring WebDAV, see 

your Web server documentation. 

Note: iPlanet does not support WebDAV. 

Set the Database Connection Properties for the Content Store 

For all installations, you must specify the database server information to ensure that ReportNet 

can connect to the database you use for the content store. Content Manager uses the database 

logon to access the content store. 

Ensure that you used one of the supported database servers to create the content store. 



Steps for Oracle and DB2 Databases 

1. On the computer where you installed Content Manager, start Cognos Configuration. 

2. In the Explorer window, under Data Access, Content Manager, right-click Content Store 

and click Delete. 

This deletes the default resource. You can configure ReportNet to access only one content 

store. 

3. Right-click Content Manager, and then click New resource, Database. 

4. In the Name box, type a name for the resource. 

5. In the Type box, select the type of database and click OK. 

6. In the Properties window: 

• If you are use a DB2 database, for the Database name property, type the database 

alias. 

• If you use an Oracle database, type the appropriate values for the Database server 

and port number and Service name properties. 

7. Click the Value box next to the User ID and password property and then click the edit 

button when it appears. 

8. Type the appropriate values in the Enter the user ID and password dialog box and then 

click OK. 

9. From the File menu, click Save. 

The logon credentials are immediately encrypted. 

Content Manager can now create the required tables in the content store when you start the 

ReportNet service for the first time. If the connection properties are not specified correctly, the 

tables are not created and you cannot connect to Cognos Connection, the ReportNet Web 

portal. 

Steps for Microsoft SQL Server Databases 


2. In the Explorer window, under Data Access, Content Manager, click Content Store. 

By default, ReportNet uses properties for a Microsoft SQL Server database. 

3. If necessary, in the Properties window, change the default value for the Database server 

and port number. 

4. For the Database name property, type the name of the database you previously created in 

Microsoft SQL Server to use as the content store. 



6. In the Enter the user ID and password dialog box, type the appropriate values and then 

click OK. 



Content Manager can now create the required tables in the content store when you start the 

ReportNet service for the first time. If the connection properties are not specified correctly, the 

tables are not created and you cannot connect to Cognos Connection, the ReportNet Web 

portal. 

Configure a Mail Server Account 

If you want to send reports by email, you must configure a mail server account. 

To be able to load balance, you must configure mail server settings on each Content Manager 

and report server computer. 

Tip: To be able to open reports that are sent by email, you must change the host name portion 

of the Gateway URI from localhost to either the IP address of the computer or the computer 

name. Otherwise the URL in the email will contain localhost and remote users will not be able to 

open the report. 



Steps 

1. On each computer where Content Manager or the report server is installed, start Cognos 


2. In the Explorer window, under Data Access, click Notification. 

3. In the Properties window, for the SMTP mail server property, type the host name and port 

of your SMTP (outgoing) mail server. 

4. Click the Value box next to the Account and password property and then click the edit 



click OK. 

6. In the Properties window, type the appropriate value for the default sender account. 


Configuring Web Browsers 

ReportNet uses the default browser configurations provided by Netscape and Microsoft. To 

ensure that Cognos Connection and Query Studio operate effectively, an administrator should 

ensure the following settings are enabled: 

• Allow Cookies (Internet Explorer and Netscape Navigator) 

• JavaScript (Netscape Navigator) 

• Active Scripting (Internet Explorer) 

To ensure that Report Studio operates effectively, an administrator should ensure that the 

following settings are enabled in Internet Explorer: 

• Allow Cookies 

• Active Scripting 


• Script ActiveX controls marked safe for scripting 

Notes 

• Only the ActiveX controls that are installed as part of Internet Explorer are enabled through 

this configuration. ReportNet does not provide or download ActiveX controls. Report Studio 

uses the native Microsoft Internet Explorer XML support, which is a component of the 

browser. ActiveX support must be enabled for Report Studio because Microsoft implements 

XML using ActiveX. 

• ReportNet uses the two cookies to store user information. Cam_passport is a session 

temporary cookie which stores a reference to a user session stored on the Content 

Manager server. Report_Studio_12 is a persistent cookie that stores a user’s Report Studio 

preferences. 

Test the Installation and Configuration 

You can test your installation and configuration by starting the ReportNet service and then 

opening Cognos Connection, the ReportNet Web portal. 

On Windows, the ReportNet service is configured to start automatically by default. 

On UNIX, to start the ReportNet process automatically, you must configure the process as a 

daemon. For more information, see your operating system documentation. 

You must install and configure both ReportNet and Framework Manager before you can use 

ReportNet for reporting. 

Steps 

1. Start Cognos Configuration. 

2. Ensure that you save your configuration, otherwise you will not be able to start the 

ReportNet service. 



3. From the Actions menu, click Start. 

It may take a few minutes for the ReportNet service to start. 

4. Open a Web browser. 

5. Start ReportNet by typing one the following, where crn is the virtual directory you created 

when you configured the Web server. 

For the CGI gateway: 

http://server_name/crn 

For an ISAPI gateway: 

http://server_name/crn/isapi 

For Apache Connector on Windows: 

http://server_name/crn/cgi-bin/mod_cognos.dll 

For Apache Connector on Solaris and AIX: 

http://server_name/crn/cgi-bin/mod_cognos.so 

For Apache Connector on HPUX: 

http://server_name/crn/cgi-bin/mod_cognos.sl 

For a gateway servlet: 

http://server_name:9300/ServletGateway/servlet/Gateway 

It may take a few minutes for the Web page to open. 

If you see the Welcome page of Cognos Connection, your installation is working. 

The configuration of a single computer installation is now complete. You can perform additional 

configuration tasks to customize the behavior of ReportNet components to better suit your 

reporting environment (p. 40). If you are satisfied with your configuration, you can install and 

configure the Windows modeling tool, Framework Manager. 

Configuring Distributed Installations 

To improve performance or to enhance security, you can install any one the following 

components on a separate computer: 

• gateway 

• report server 

• Content Manager 

For information about planning a distributed installation, see the Architecture and Planning 

Guide. 

You can install the report server or gateway on multiple computers. You can install Content 

Manager on only one computer. 

If you install ReportNet components on more than one computer, some configuration tasks are 

required so that the components can communicate with each other and work in your reporting 

environment. Other configuration tasks, such as using an authentication provider (p. 41) or 

enabling and disabling services (p. 53) are optional and change the default behavior of 

ReportNet to better suit your reporting objectives. 

Communication Between Distributed Components 

If you install ReportNet components on more than one computer, you must configure 

environment properties so that the distributed components can communicate with each other: 

• The Content Manager computer must know the location of the content store. 

• The gateway computer must know the location of a dispatcher. 

The dispatcher can be located on the Content Manager or report server computer. 

• The report server computer must know the location of Content Manager. 

You must also configure cryptographic properties to ensure that each computer uses the same 

settings. 



In a distributed environment, the sequence in which you configure computers is important. You 

must configure and then start the services on the Content Manager computer before you 

configure other ReportNet computers. The server specified in the External Dispatcher URI on 

the gateway computer must be the last server that you start. 

Use the following checklist to guide you through the required configuration tasks: 

❑ Configure your Web server. 

❑ Configure the Content Manager computer. 

❑ Configure the report server computers. 

❑ Configure the gateway computers. 

❑ Configure your Web browser. 

❑ Test the installation and configuration. 

After you complete these configuration tasks, you can change the default behavior of ReportNet 

(p. 40) to better suit your reporting environment. 

Configuring the Content Manager Computer 

In a distributed installation, the computer where you installed Content Manager must be 

configured, running and accessible before you configure other computers in your ReportNet 

environment. This ensures that the certificate authority service, which is installed with Content 

Manager, is available to issue certificates to other ReportNet computers. 

Before you configure Content Manager, ensure that you created the database for the content 

store on an available computer in your network. 

Use the following checklist to guide you through the required configuration tasks for the Content 

Manager computer: 

❑ Set the Database Connection Properties for the Content Store (p. 34). 

❑ Configure a Mail Server Account (p. 35). 

❑ Start the ReportNet service. 

Other configuration tasks are optional and may be performed later. 

After you complete the required configuration tasks, the certificate authority service is available 

to issue certificates to other ReportNet computers. You can now perform the required 

configuration tasks on other computers, such as the report server and gateway computers. 

Otherwise you can continue to configure the Content Manager computer by changing the default 

property settings (p. 40) so that they better suit your environment. For example, you can 

configure ReportNet to use an authentication provider (p. 41), enable and disable services 

(p. 53) on the Content Manager computer, or change global settings (p. 54). 

Configuring Report Server Computers 

You can install the report server component on one or more computers, depending on your 

environment. 

Ensure that the Content Manager computer is configured and available before you configure 

report server computers. 

If Content Manager and the report server are installed on separate computers, on the report 

server computer, you must 

❑ Configure a Mail Server Account (p. 35). 

❑ Configure Environment properties. 

❑ Start the ReportNet service (if not already running). 


After you complete these required configuration tasks, the report server computer can work in 

your environment. 



Configure Environment Properties for the Report Server Computer 

If you install the report server component on a different computer than Content Manager, you 

must configure the report server computer so that it knows the location of Content Manager. The 

distributed components can then communicate with each other. 

Steps 


2. In the Explorer window, click Environment. 

3. In the Properties window, specify the appropriate value for the Gateway URI, by changing 

the localhost portion to the name of the ReportNet gateway computer. 

4. In the Properties window, specify the appropriate value for the Content Manager URI, by 

changing the localhost portion to the name of the Content Manager computer. 

5. In the Explorer window, under Cryptography, click Cognos, the default cryptographic 

provider. 

6. Under the Certificate Authority settings property group, set the Password property to 

correspond to the one configured on the Content Manager computer. 

7. Ensure that all other cryptographic settings correspond to the ones you set on the Content 

Manager computer. 


9. From the Actions menu, click Start. 

After you completed the required configuration tasks for each report server computer in your 

environment, you can now perform the required configuration tasks on other computers, such as 

the gateway computers. Otherwise you can continue to configure the report server computers 

by changing the default property settings so that they better suit your environment. For example, 

you can enable and disable services (p. 53), configure where to send log messages (p. 49) or 

configure the amount of resources the ReportNet service uses (p. 54). 

Configuring Gateway Computers 

You can install the ReportNet gateway on one or more Web server computers. 

The gateway computer must know the location of a dispatcher. The dispatcher can be located 

on the Content Manager or report server computer. You must configure the Environment 

properties. 


Ensure that the Content Manager computer is configured and available before you configure 

gateway computers. 

After you do the required configuration tasks, the gateway computer can work in your 

environment. 

Configure Environment Properties for the Gateway Computer 

If you install the gateway component on a different computer than Content Manager or report 

servers, you must configure the gateway computer so that it knows the location of a dispatcher. 

The distributed components can communicate with each other. 

Steps 



3. In the Properties window, specify the appropriate value for the External Dispatcher URI, 

by changing the localhost portion to the name of the Content Manager or report server 

computer. 


provider. 



5. Under the Certificate Authority settings property group, set the Password property to 

correspond to the one configured on the Content Manager computer. 

6. Ensure that all other cryptographic settings correspond to the ones you set on the Content 



After you completed the required configuration tasks for each gateway computer in your 

environment, you can continue to configure the gateway computers by changing the default 

property settings so that they better suit your environment. For example, you can configure a 

gateway to use a namespace. 

Finishing the Configuration of Distributed Installations 

After you complete the required configuration tasks, you can perform some additional 

configuration tasks to customize the behavior of ReportNet to better suit your reporting 


Ensure that you configured the Content Manager computer before you change default 

configuration settings on other ReportNet computers. 

• For distributed installations, we recommend that you specify the amount of resources the 

ReportNet service uses to ensure performance is optimized. 

If you are satisfied with your configuration, you can now install and configure Framework 

Manager. 

Changing Default Configuration Settings 

When you install ReportNet components, the installation uses default configuration settings. If 

you have any reason not to use these default values, such as a port is being used by another 

process, use Cognos Configuration to change the value. 



You can also change the default behavior of ReportNet. For example you can 

• change a port number 

• use an authentication provider 

• configure cryptographic settings 

• configure SSL protocol 

• configure temporary file properties 

• specify where to send log messages 

• configure ReportNet to use alternate gateways 

• configure the gateway to use a namespace 

• enable and disable services 

• specify the amount of resources the ReportNet service uses 

• change global settings, such as product and content locales 

• configure fonts 

• change the default font for reports 

• configure Cognos Portal Services 

After you change the default behavior of ReportNet to better suit your reporting environment, 

you can test the installation and configuration or install and configure Framework Manager. 

Change a Port Number 

If you have any reason not to use a default port, such as it is used by another process, you can 

change it. 



When you change the port used by the local dispatcher, you must change the value of the 

Internal dispatcher URI property. Because the change affects all the URIs that are based on the 

local dispatcher, you must change the URIs of all local components. By default, local 

components contain localhost in the URI. 

For example, if you install all components on one computer and you change the dispatcher port, 

you must also change the port in the local Content Manager URI and local SDK URI. 

If you change the dispatcher port in the local Dispatcher URI, ensure that you specify the new 

port numbers when you configure remote computers that use the Dispatcher URI, Content 

Manager URI, and SDK URI properties. 

Steps 


2. In the Explorer window click the appropriate group or component: 

• To change the port number for the dispatcher, click Environment. 

• To change the port number for the local log server, under Environment, click Logging. 

3. In the Properties window, click the Value box next to the property that you want to change. 

4. If you change the dispatcher port, ensure that you change the ports in other URIs that 

contain localhost. 


Using an Authentication Provider 

ReportNet runs with or without authentication providers. By default, anonymous access is 

enabled. 

You can configure multiple namespaces for authentication and then choose at run time which 

namespace you want to use. For more information, see the Administration and Security Guide. 

If you enable security, you must configure security settings immediately after you complete the 

installation and configuration process. For more information, see the Administration and 

Security Guide. 

Important: We recommend that you do not disable security after you enable it. If you previously 

configured a namespace that is no longer in the current configuration, when you start 

ReportNet, the namespace, including the user accounts, are permanently deleted from the 

content store. Restoring the namespace definition, by using a previously saved crnstartup.xml 

file for example, does not restore the user accounts. This means that for the users defined in the 

deleted namespace, their preferences, My Folders and My Pages entries are permanently lost. 

Existing policies will continue to refer to users, groups or roles that no longer exist. While this will 

not affect how the policies work, a user administering the policy may see "unknown" entries. 

Because these entries refer to users, groups, and roles which no longer exist, you can safely 

delete them. 

To use an authentication provider and to require users to authenticate: 

❑ Disable anonymous access. 

❑ Configure ReportNet to use an authentication provider. 

Disable Anonymous Access 

By default, ReportNet does not require user authentication. Users can logon anonymously. 

You can use Cognos Configuration to disable anonymous access. 

Steps 


2. In the Explorer window, under Security, Authentication, click Cognos. 

The Cognos resource represents the Cognos namespace. The Cognos namespace stores 

information about Cognos groups, such as the Anonymous User, contacts, and distribution 

lists, and refers to objects in other security namespaces. For more information, see the 

Administration and Security Guide. 



3. In the Properties window, click the box next to the Allow anonymous access property and 

then click False. 


Now, users are required to provide logon credentials when they access ReportNet resources. 

Configure ReportNet to Use a Third-Party LDAP Server 

To bind a user to the LDAP server, the LDAP authentication provider must construct the 

distinguished name (DN). If the Use external identity property is set to True, it uses the External 

identity mapping property to try to resolve the user's DN. If it cannot find the environment 

variable or the DN in the LDAP server, it attempts to use the User lookup property to construct 

the DN. 

If users are stored hierarchically within the directory server, you can configure the User lookup 

and External identity mapping properties to use search filters. When the LDAP authentication 

provider performs a search, it uses the filters you specify for the User lookup and External 

identity mapping properties. It also binds to the directory server using the value you specify for 

the Bind user DN and password property or using anonymous if no value is specified. 

When an LDAP namespace has been configured to use the External identity mapping property 

for authentication, the LDAP provider binds to the directory server using the Bind user DN and 

password or using anonymous if no value is specified. All users who log on to ReportNet using 

external identity mapping see the same users, groups, and folders as the Bind user. 

Configure ReportNet to Use a Cognos Series 7 Namespace 

You can configure ReportNet to use multiple Cognos Series 7 authentication providers. We 

recommend that you configure the same host and port values for all instances. Otherwise, you 

may receive errors or be prompted for authentication more than once. 

If you change the configuration information stored in the directory server used for Cognos 

Series 7, you must restart the ReportNet service before the changes take effect in the 

ReportNet installation. 

After you configure the Cognos Series 7 namespace as your authentication source, you can 

configure single signon between ReportNet and Cognos Series 7 products. 

Configure ReportNet to Use Windows Native Security 

You cannot use a Windows Native Security (NTLM) authentication provider with an Active 

Directory domain. 

Configure ReportNet to Use an Active Directory Server 

To use Active Directory Server as your authentication provider, you must install the Active 

Directory Client Extension on any computer running Windows NT. For more information, see the 

Microsoft Web site. 

To configure single signon between your Active Directory domain and ReportNet, you must 

• run Active Directory domain in the native mode 

• set up NT Challenge Response on the IIS Web server 

• install Content Manager on a computer that is part of the domain 

• set up the computer, or the user account under which Content Manager runs, to be trusted 

for delegation 

If you install ReportNet on UNIX, you can use a Windows Active Directory Server as your 

authentication source. 

If you install Content Manager on a Windows computer, you can configure Active Directory as 

your authentication source using an Active Directory namespace. 

If you install Content Manager on a UNIX computer, you must instead configure Active Directory 

as your authentication source using an LDAP namespace. When you configure the new LDAP 

namespace, check that the default settings still apply. Change the values for all properties in the 

advanced mappings property groups to match the settings required for the Active Directory 

properties. 



The following table lists the values to use for the LDAP advanced mapping properties if you use 

default values for Active Directory. 

Mappings LDAP Property LDAP Value 

Folder Object class * 

Description 

Name 

description 

name 

Group Object class group 

Description 

Member 

Name 

description 

member 

cn 

Account Object class user 

Business phone 

Content locale 

Description 

Email 

Fax/Phone 

Given name 

Home phone 

Mobile phone 

Name 

Pager phone 

Password 

Postal address 

Product locale 

Surname 

telephonenumber 

(leave blank) 

description 

mail 

facsimiletelephonenumber 

givenname 

homephone 

mobile 

displayName 

pager 

(leave blank) 

postaladdress 

(leave blank) 

sn 

Configure ReportNet to Use an SAP Server 

To use a SAP server as your authentication provider, you must use SAP BW version 3.0 B or 

later. 

In SAP BW, you can assign users to user groups or activity groups or both. The SAP 

authentication provider uses only the activity groups. 

The authorization rights required by the SAP user depend on how the user will use ReportNet. 



Authorization Settings for ReportNet Users 

The following authorization objects are required for any ReportNet user. Some of the values 

shown, such as *, are default values that you may want to modify for your environment. 

Authorization object Field 

Value 

S_RFC 

Authorization check 

for RFC access 

Activity 16 

Name of RCF to be 

protected 

Type of RFC object to 

be protected 

RFC1 

RS_UNIFICATION, 

SDTX, SH3A, 

SU_USER, SYST, 

SUSO 

FUGR 

S_USER_GRP 

User Master 

Maintenance: User 

Groups 

Activity 03 

Name of user group * 

Authorization Settings for ReportNet Administrators 

If users will perform administrative tasks and searches for users and roles, the following values 

must be added to the S_RFC authorization object in addition to the values listed above for 

ReportNet users. Some of the values shown, such as *, are default values that you may want to 

modify for your environment. 

Authorization object Field 

Value 

S_RFC 

Authorization check 

for RFC access 

Activity 16 

RFC_NAME 


be protected 

PRGN_J2EE, SHSS, 

SOA3 

FUGR 

Enable Single Signon Between SAP BW and ReportNet 

To enable single sign on between SAP BW and ReportNet, ensure that you set the following 

system parameters on the SAP BW server: 

• login/accept_sso2_ticket = 1 

• login/create_sso2_ticket = 1 

• login/ticket_expiration_time = 200 

Configure ReportNet to Use Netegrity SiteMinder 

To use Netegrity SiteMinder as your authentication provider, you must configure it to protect the 

ReportNet portal. The users must be stored in an LDAP server or as part of an NTLM domain. 

Therefore, in addition to the Netegrity SiteMinder provider, you must add a corresponding LDAP 

or NTLM authentication provider to your configuration for each user directory. 



Steps for Netegrity SiteMinder 

1. On the computer where you installed Content Manager, open Cognos Configuration. 

2. In the Explorer window, under Security, right-click Authentication, and click New 

resource, Namespace Type. 

3. In the Name box, type a name for your authentication namespace. 

4. In the Type list, click the Netegrity SiteMinder namespace and then click OK. 

The new authentication provider resource appears in the Explorer window, under the 

Authentication component. 

5. In the Properties window, for the Namespace ID property, specify a unique identifier for the 

namespace. 

6. Specify the values for all other required properties to ensure that ReportNet can locate and 

use your existing authentication provider. 

7. In the Explorer window, under Security, Authentication, right-click the Netegrity 

namespace and click New resource, SiteMinder Policy Server. 

8. In the Name box, type a name for the policy server and click OK. 

9. In the Properties window, specify the Host property and any other property values you 

want to change. 

10. In the Explorer window, right-click the new SiteMinder Policy Server and click New 

resource, User directory. 

Tip: Configure a user directory for each user directory in the SiteMinder policy server. 

11. For each user directory, configure a corresponding LDAP or NTLM namespace. 

12. If users are stored in an LDAP server, set the Use external identity property to True and 

the External identity mapping property to the default value. 

13. In the Name box, type a name for the user directory and click OK. 

14. In the Properties window, type a value for the Namespace ID reference property. 

Tip: Ensure that you use the same value as the Namespace ID property for the 

corresponding LDAP or NTLM authentication provider. 


Steps for All Types of Authentication Provider Except Netegrity SiteMinder 

1. On the computer where you installed Content Manager, open Cognos Configuration. 

2. In the Explorer window, under Security, right-click Authentication, and click New 

resource, Namespace Type. 

3. In the Name box, type a name for your authentication namespace. 

4. In the Type list, click the appropriate namespace and then click OK. 

The new authentication provider resource appears in the Explorer window, under the 

Authentication component. 

5. In the Properties window, for the Namespace ID property, specify a unique identifier for the 

namespace. 

6. Specify the values for all other required properties to ensure that ReportNet can locate and 

use your existing authentication provider. 

7. If you want to customize the authentication for ReportNet, specify the values for other 

properties. 


Configure Single Signon Between ReportNet and Cognos Series 7 Products 

To configure single signon between ReportNet and Cognos Series 7 products, ensure that the 

cookie settings match. That means that the configuration properties for the cookie properties 

must be the same for both ReportNet and Cognos Series 7. 

By configuring single signon, you will not be prompted to reenter authentication information. You 

can then add Cognos Upfront Series 7 NewsBoxes to your ReportNet Web portal pages. 



Ensure that you configured ReportNet to use a Cognos Series 7 namespace as an 

authentication provider (p. 42). 

Steps for ReportNet 

1. On the computer where Content Manager is installed, start Cognos Configuration. 

2. In the Explorer window, under Security, Authentication, click the Cognos Series 7 

namespace. 

3. In the Properties window, under Cookie settings, ensure that the Path, Domain and 

Secure flag enabled properties match the settings configured for Cognos Series 7. 

Steps for Cognos Series 7 

1. Start Configuration Manager. 

2. Click Open the current configuration. 

3. On the Components tab, in the Explorer window, expand Services, Access Manager - 

Runtime and click Cookie Settings. 

4. In the Properties window, ensure that the Path, Domain and Secure Flag Enabled 

properties match the settings configured for ReportNet. 

Configure Cryptographic Settings 

ReportNet requires a cryptographic provider; otherwise it will not run. 

You can configure cryptographic and cryptographic provider settings, including the following: 

• advanced algorithms 

These include signing, digest, and confidentiality algorithms. 

• common symmetric key store (CSK) properties 

The CSK is used by ReportNet components to encrypt and decrypt data. 

• signing key store properties 

The signing key pair includes the private key used to generate the digital signature and the 

public key used to verify authenticity. 

• encryption key store properties 

The encryption key pair includes the private key used to encrypt data and the public key 

used to decrypt data. 

ReportNet requires a cryptographic provider. By default, the cryptographic provider for 

ReportNet uses keys up to 40 bits in length for data encryption and secure sockets layer (SSL) 

protocol. You can configure other cryptographic providers which use key sizes greater than 40 

bits, such as the Enhanced Encryption Module for OpenSSL or the Enhanced Encryption 

Module for Entrust, available from Cognos. For more information, see the Enhanced Encryption 

Module for OpenSSL Installation and Configuration Guide or the Enhanced Encryption Module 

for Entrust Installation and Configuration Guide. 

Steps for Cryptographic Settings 


2. In the Explorer window, under Security, click Cryptography. 



3. In the Properties window, change the default values by clicking the Value box and then 

selecting the appropriate value: 

• If you do not want to store the CSKs locally, under CSK settings, change Store 

symmetric key locally to False. Then change the Common symmetric key store 

location to the key store location of the Content Manager computer. 

When Store symmetric key locally is False, the key must be retrieved from Content 

Manager. 

• If you want the computers at both ends of a transmission to prove their identity, under 

SSL Settings, change Use mutual authentication to True. 

We recommend that you do not change the Use confidentiality setting. Set this 

property to true to ensure all transmissions are encrypted. 

• If you want to change the confidentiality algorithm, under Advanced algorithm 

settings, change Confidentiality algorithm to the other 40-bit key value. 

If you select and try to save an algorithm that does not use a 40-bit key, you will receive 

an error message. These other algorithms are reserved for use with other cryptographic 

providers. For more information, see the Enhanced Encryption Module for OpenSSL 

Installation Guide or the Enhanced Encryption Module for Entrust Installation Guide. 


After you configure the cryptographic provider, passwords in your configuration and any data 

you create are encrypted. 

Steps for Cryptographic Provider Settings 


2. In the Explorer window, under Security, Cryptography, click Cognos. 

• If you want to use a third-party certificate authority, under Certificate Authority 

settings, change Use third party CA to True. 

• If you want to change the location of the signing keys, under Signing key settings, 

change the Signing key store location property to the new location. 

• If you want to change the location of the encryption keys, under Encryption key 

settings, change Encryption key store location to the new location. 


If you use a third-party Certificate Authority (CA) server, you must now configure ReportNet to 

use the CA. 

Configure the SSL Protocol 

You can configure ReportNet components to use the Secure Sockets Layer (SSL) protocol for 

• internal connections only 

• external connections only 

• internal and external connections 

• connections to local and remote log servers. 

If you configure SSL only for internal connections, ReportNet components on the local computer 

communicate using this protocol. The dispatcher listens for secure connections on a different 

port than for remote, http requests. Therefore, you must configure two dispatcher URIs. 

If you configure SSL only for external connections, communications from remote ReportNet 

components to the local computer use the SSL protocol. You must configure the dispatcher to 

listen for secure, remote requests on a different port than local, http requests. 

If you configure SSL for all connections, the dispatcher can use the same port for internal and 

external connections. Similarly, if you do not use SSL for local or remote communication, the 

dispatcher can use the same port for all communications. 

You must also update the Content Manager URI, SDK URI, and Gateway URI to use SSL, if 

required. 



Tomcat Connectors 

When the internal and external dispatcher URIs are the same, only one HTTP/1.1 connector is 

required in Tomcat’s configuration file, the server.xml file, located in the 

crn_location/tomcat4.1.18/conf directory. The port number in the dispatcher URIs is used to 

update the port number in the appropriate non-SSL Coyote HTTP/1.1 or SSL Coyote HTTP/1.1 

connector. 

If the internal dispatcher URI is prefixed with http but the external dispatcher URI is prefixed with 

https, or vice versa, both the non-SSL Coyote HTTP/1.1 and SSL Coyote HTTP/1.1 connectors 

are enabled in the server.xml file. 

Distributed Installations 

In distributed installations, if you are using the ReportNet certificate authority service, you must 

first configure all ReportNet computers to use the non-secure (http) protocol before you 

configure ReportNet to use the SSL protocol. You must do this because you cannot set up the 

SSL protocol before trust has been established. 

Also, ensure that you follow the required order of configuring computers in a distributed 

environment. That means that you must first configure the computer where Content Manager is 

installed and then start the services on this computer before you configure other computers or 

start services on other computers. By first configuring the Content Manager computer and 

starting the services, you ensure that the certificate authority service on the Content Manager 

computer can issue certificates to other computers in the ReportNet environment. 

After you configure all computers in the distributed installation to use the default, non-secure 

protocol, we recommend that you test your installation to ensure that ReportNet is working 

properly. After you test your installation, you can configure the SSL protocol. 

When you configure ReportNet to use the SSL protocol, ensure that you first configure the 

Content Manager computer to use the protocol and start the services on the Content Manager 

computer. After you do this, you can configure the SSL protocol on other ReportNet computers 


Add a Computer to an Installation 

If you later add a computer to your distributed environment and SSL is enabled for external 

connections, you must reconfigure the Content Manager computer to use the non-secure 

protocol. Then, you start the services on the Content Manager computer. This ensures that the 

certificate authority service that is installed on the Content Manager computer can issue a 

certificate to the new computer. After the Content Manager computer is configured and running, 

you must configure the new computer to use the non-secure protocol. You must then save your 

configuration on the new computer so that the computer can get the certificate from the Content 


After this occurs, you can re-enable SSL on the Content Manager computer and then configure 

the new component to use SSL. 

Add a Component to a Computer 

You can later add a component to the same location as other ReportNet components. If the 

existing components currently use the SSL protocol, you do not have to disable the SSL 

protocol on the Content Manager computer before configuring the new component to use SSL. 

The computer has a certificate and the certificate is in a known location. 

However, you can also add a component to a different location on the same computer as other 

ReportNet components. If the existing components use SSL, you must disable the SSL protocol 

on the Content Manager computer before configuring the new component to use SSL. Another 

certificate is issued for this new installation when you save your new configuration. After this 

occurs, you can re-enable SSL on the Content Manager computer and then configure the new 

component to use SSL. 

Steps for a new installation 



3. To use SSL protocol, you must specify passwords for the ReportNet encryption key stores. 




5. In the Properties window, type the appropriate values for the Internal dispatcher URI and 

External dispatcher URI values: 

• To configure SSL for internal connections only, for the Internal dispatcher URI 

property, type https and a port for SSL communication. For the External dispatcher 

URI property, type http and use the default or another available port. 

The ports in the two dispatcher URIs must be different. 

• To configure SSL for external connections only, for the External dispatcher URI 

property, type https and a secure port. For the Internal dispatcher URI property, type 

http and use the default or another available port. 


• To configure SSL for all connections, type the same URI for both the Internal 

dispatcher URI and External dispatcher URI properties. Type https and a secure 

port, such as 9343. 

Note: You do not have to use port 9343, the default SSL port. You can choose any available 

port. 

6. Configure the SSL protocol for the other environment URIs, including the Content Manager 

URI, the SDK URI and Gateway URI. 

• For internal connections only, type https in the URIs that contain localhost. 

• For external connections only, type https in the URIs that do not contain localhost. 

• For all connections, type https in all the URIs. 

7. In the Explorer window, click Logging. 

8. In the Properties window, set the following properties to True: 

• Enable TCP 

• Enable SSL 

9. If you configured a remote log server, in the Explorer window, under Logging, click the 

name of the remote log server and then, in the Properties window, set the Enable SSL 

property to True. 


Configure Temporary File Properties 

You can change the location where ReportNet stores recently viewed reports, and you can 

choose to encrypt their content. By default, ReportNet stores temporary files in the 

crn_location/temp directory and the files are not encrypted. 

We recommend that you first set up read-only access for all users to the crn_location directory. 

Steps 



3. In the Properties window, for the Temp folder property, specify the new location. 

4. If you require the content of temporary files to be encrypted, set the Encrypt temporary 

files property to True. 

5. Ensure that the user account under which ReportNet runs has the appropriate privileges to 

the temporary files location. For example: 

• on Windows, full control privileges 

• on UNIX, read-write privileges 

Specify Where to Send Log Messages 

You can specify where the local log server sends log messages. 



A local log server is automatically installed when you install Content Manager or the report 

server. 

The log server can send log messages to any number of storage media including the following: 

• file 

• database 

• UNIX syslog 

• NT Event log 

The log server can also send messages to a remote log server. If a remote log server is 

unavailable, log messages are redirected to recovery files on the local computer in the 

crn_location/logs/recovery/remote location. These recovery files have timestamp information in 

their file names, and are not readable like regular log files. These files are created until the 

remote log server becomes available. After the remote log server becomes available, an 

automatic recovery process starts. For more information, see the Architecture and Planning 

Guide. 

By default, the log server sends log messages to the crnserver.log file located in the 

crn_location/logs directory. 

Tip: The logging database has the same configuration and user account requirements as 

described when you created the database for the content store. 

Steps 

1. On the computers where you installed Content Manager or the report server, start Cognos 


2. In the Explorer window, under Environment, click Logging. 

3. In the Properties window, set the log server properties. 

Tip: To use SSL protocol for communication between ReportNet components and the log 

server, set the Enable TCP property and Enable SSL properties to true. 

4. In the Explorer window, under Environment, right-click Logging, and click New resource, 

Destination. 

5. In the Name box, type the name of the storage media or remote log server. 

6. In the Type list, click the appropriate type and then click OK. 

7. To configure a database: 

• Right-click the database, and click New resource, Database. 

• In the Name box, type the name of the database. 

• In the Type list, click the database type, and then click OK. 

8. In the Properties window, type the appropriate values for the mandatory and optional 

properties. 

9. Repeat steps 4 to 8 for each destination to which you want the log server to send 

messages. 


If you use a DB2 or Oracle database to store the log messages, you must now set up the 

database client software or the JDBC 2.0 driver. 

Set Up the Database Client for the Log Database 

After you configure a database as the output device for your log messages, if you use Oracle or 

DB2 as the database server, additional steps are required. 

If you use an Oracle database, you must set up the JDBC driver. 

If you use a DB2 database, you must set up the database client software and the JDBC 2.0 

driver. 








computer where you configured the log database. 


Steps for DB2 

1. Install the DB2 UDB client software on the computer where the log database is located. 

2. Run the DB2 Client Configuration Assistant to configure a database alias to the log 

database. 













directory. 

Configure ReportNet to Use Alternate Gateways 

To improve Web server performance, you can configure ReportNet to use alternate gateways 

that replace the default CGI program. You can use one of the following gateways: 

• Microsoft Internet Application Programming Interface (ISAPI) to support Microsoft Internet 

Information Services on Windows 

• apache_mod to support Apache Web Server 

• servlet 

Before you configure an alternate gateway, we recommend that you first check that the 

ReportNet CGI gateway and your configuration work in your environment. 

Steps to configure apache_mod gateway 

1. Stop Apache Web Server. 

2. Append the crn_location/bin/cgi-bin directory to the appropriate environment variable: 

• On Solaris, LD_LIBRARY_PATH 

• On HPUX, SHLIB_PATH 

• On AIX, LIBPATH 

3. On HPUX, ensure that the LD_PRELOAD environment variable points to the location of the 

shared libraries in the system directory (usually /usr/lib or /usr/lib/libcl.2) so that the Apache 

server can load the Cognos connector. 

4. On the Apache Web Server computer, 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: 

• On Windows 

LoadModule cognos_module "crn_location\cgi-bin\mod_cognos.dll" 

• On Solaris and AIX, 

LoadModule cognos_module "crn_location/cgi-bin/mod_cognos.so" 

• On HPUX, 

LoadModule cognos_module "crn_location/cgi-bin/mod_cognos.sl" 

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" 

 

Options Indexes MultiViews 

 

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: 

• On Windows 

 

SetHandler cognos-handler 

 

• On Solaris and AIX 

 


 

• On HPUX 

 


 

10. Add the following to the user directory section: 

 

CGIBinDir "crn_locaton/cgi-bin" 

 

11. Start Apache Web Server. 

Steps to configure servlet gateway 

1. Ensure your Web server infrastructure supports servlets. 

2. On the ReportNet gateway computer, go to the crn_location/war/gateway directory. 

3. Type the appropriate command to create the ServletGateway.war in crn_location: 

• On UNIX, type build.sh 

• On Windows, type build.bat 

4. Copy the ServletGateway.war file to your Web server installation. 

For information about the requirements for using servlets, see your Web server 


5. From the command line, type the following option after the command that starts the Java 

VM: 

-DCRN_ROOT="crn_location" 



6. Add the crn_location/bin path to the following environment variable. 

Operating System 

Windows 

AIX 

Solaris 

HPUX 

Environment Variable 

PATH 

LIBPATH 


SHLIB_PATH 

7. To access ReportNet using the servlet gateway, configure the Gateway URI to use the 

servlet address format as configured in the Web server administration tool. 

Configure the Gateway to Use a Namespace 

If ReportNet uses multiple namespaces or anonymous access is enabled and ReportNet uses 

one namespace, you can configure the ReportNet gateway to connect to one namespace. 

Users logged onto the Web server where the gateway is located are not be prompted to choose 

an authentication source. 

For example, if you have two Web servers, you can configure each Web server to use a different 

namespace. 

Steps 

1. On the computer where the gateway is located, start Cognos Configuration. 


3. In the Properties window, in the Value box next to the Gateway namespace property, type 

the Namespace ID of the namespace you want to use. 


Enable and Disable Services 

In a distributed installation, you can send certain types of requests to specific computers by 

enabling or disabling the installed services. For example, to dedicate a computer to running and 

distributing reports, you can disable the presentation service on a report server computer. 

If you installed all components on several computers, you can disable appropriate services on 

each computer to get the distributed configuration you require. Requests are sent only to 

dispatchers where a given service is enabled. 

Disabling a service prevents the service from loading into memory. When disabled, services do 

not start and therefore do not consume resources. The service does not run until you enable it. 

If you disable the dispatcher service, all services that run under that dispatcher are also 

disabled. Only dispatcher services that are enabled can process requests. 

Steps 


2. In the Explorer window, under Environment, click ReportNet Service. 

3. In the Properties window, click the Value box beside the service that you want to disable or 

enable. 

By default, all services are enabled. 

4. Click the appropriate state for the services: 

• To disable the service, click False. 

• To enable the service, click True. 




Specify the Amount of Resources the ReportNet Service Uses 

To improve performance in a distributed environment, you can change the amount of resources 

that the ReportNet service uses by choosing a configuration template. 

By default, the ReportNet service is configured to use minimal memory resources to optimize 

startup time. 

The ReportNet service is available only on the computers where you installed Content Manager 

and the report server. 

Steps 


2. In the Explorer window, under Environment, ReportNet Service, right-click Cognos 

ReportNet, and click Delete. 

This deletes the default configuration template for the service. 

3. Right-click ReportNet Service, and click New resource, Configuration. 

4. Type a name for the service. 

In Windows, the name you choose is used to register the service. You will see this name in 

the list of services running on your computer. In UNIX, the name you choose is used as the 

process identification number (pid). In both Windows and UNIX, if you don’t use the default 

port number, the port number is appended to the service name. 

5. In the Type box, click the configuration template to use: 

• If you previously changed the default setting and now want to reduce the startup time, 

memory footprint, and resources used, click Small configuration. 

• If you want a balance between fast startup time and quick operating speeds, click 

Medium configuration. 

• If you want to maximize operating speeds and if performance is more important than 

fast startup time, and if your computer has more resources, click Large configuration. 

6. In the Properties window, edit the properties so that they are appropriate for your 

environment. 


Change Global Settings 

You change global settings 

• to customize language support for the user interface 

• to customize currency support 

• to customize content locale support 

• to map the language used in the product user interface 

• to map content locales 

• to add fonts to your ReportNet environment 

By default, ReportNet ensures that all locales, which may come from different sources and in 

various formats, use a normalized form. That means that all expanded locales conform to a 

language and regional code setting. 

Each computer has a default system locale and one user locale per user. The user locales may 

be different from the default system locale. 

Customize Language Support to the User Interface 

Use the Product Languages table to add or remove the user interface language support. For 

example, if you do not require a German user interface, you can remove the language from the 

list. 

Before you can add language support to the user interface, you must use the Cognos 

Localization Development Kit to translate the strings that appear in the ReportNet user interface. 

You must also install the language files on all computers in your distributed installation. For more 

information, contact your Cognos support representative. 



Adding languages to the ReportNet environment does not guarantee that your computer has a 

font that can display Web pages in your preferred languages. Ensure that you install the 

appropriate language packs to support the character sets you use. 

If you change the user interface language of the product, data is not affected. 

Steps 


2. From the Action menu, click Edit Global Configuration. 

3. Click the Product Locales tab. 

4. Click Add. 

Tip: To remove support, select the check box next to the Supported Locale and then click 

Remove. 

5. In the second column, type the language portion of a locale. 

6. Repeat steps 3 to 5 for other language support that you want to add. 

7. Click OK. 

8. From the File menu click Save. 

Customize Currency Support 

If you require additional currencies or want to remove some from the user interface, you can 

update the list of supported currencies in the Currencies table. 

By default ReportNet shows only a subset of supported currencies in the user interface. 

Currencies are identified by their ISO 4217 currency code. The complete list of supported 

currencies that can be added are listed in the i18n_res.xml file in the crn_location/bin/ directory. 

If you add a currency code that is not supported by Cognos, you must manually add it to the 

i18n_res.xml file in the crn_location/bin/ directory. Copy this file to each ReportNet computer in 

your installation. 

Adding currencies to the ReportNet environment does not guarantee that your computer has a 

font with the required characters to display the currency. Ensure that you install the appropriate 

language packs to the support currency symbols you use. For example, to display the Indian 

currency symbol (rupee) correctly, you must run a Japanese operating system or install a 

Japanese language. 

Steps 



3. Click the Currencies tab. 

4. Click Add. 

Tip: To remove support, select the check box next to the supported item and then click 

Remove. 

5. In the second column, type an appropriate value. 

The value you add must comply with ISO 4217 codes for the representation of currencies 

and formats. Usually the value you add is a three-letter alphabetic code. The first two 

characters are letters representing the ISO 3166 country code for the country the currency 

is from. The additional letter represents the first letter of the currency. 

6. Repeat steps 3 to 5 for other types of support that you want to add. 


Customize Content Locale Support 

To ensure users see reports, data or metadata in their preferred language, or specific to their 

region, you can add partial locales (language) or complete locales (language-region) to the 

Content Locales table. This way, if content is available in different languages, or in different 

locales, it is rendered to users based on their user locale. 

If a locale is not required, you can remove it from the list. 



Map Content Locales 

Adding incomplete locales (languages) to the ReportNet environment does not guarantee that 

your computer has a font that can display Web pages in your preferred languages. Ensure that 

you install the appropriate language packs to support the character sets you use. 

Steps 



3. Click the Content Locales tab. 

4. Click Add. 

Tip: To remove support, select the check box next to the supported item and then click 

Remove. 

5. In the second column, type an appropriate value. 

• To add language support for report data and metadata, type a partial local (language) 

setting. 

• To add support specific to a region, type a complete locale (language-region) setting. 

6. Repeat steps 3 to 5 for each additional locale that you want to support. 


Use the Content Locale Mappings table to map user locales to a complete (language-region) or 

partial (language) locale. You can also map a user’s preferred language to another language if 

content is not available in the user’s preferred language. 

For example, if a report is not available in a preferred language, for example Vietnamese, but is 

available in French and German, you can use the Content Mappings table to map the preferred 

language (Vietnamese) to another language (French or German). This way, you see the report 

in the mapped language. 

By default, the Content Locale Mappings table includes locales that do not contain the region. 

This allows you to use only the language portion of the locale when you specify locale settings 

and ensures that you always see the correct information. For example, in a multilingual 

database, data is usually available in different languages, such as French (fr), Spanish (es) and 

English (en), rather than being available in different locales, such as English Canada (en-ca), 

English United States (en-us), or French France (fr-fr). 

The follow examples shows the method that ReportNet uses to determine which report the user 

sees if the multiple language versions are available. 

Example 1 

A report is available in Content Manager in two locales, such as en-us (English-United States) 

and fr-fr (French-France), but the user locale is set to fr-ca (French-Canadian). ReportNet uses 

the locale mapping to determine which report the user sees. 

First, ReportNet checks to see if the report is available in Content Manager in the user’s locale. 

If it is not available in the user’s locale, ReportNet maps the user’s locale to a normalized locale 

configured on the Content Locale Mapping tab. Because the user’s locale is fr-ca, it is mapped 

to fr. ReportNet uses the mapped value to see if the report is available in fr. In this case, the 

report is available in en-us and fr-fr, not fr. 

Next, ReportNet maps each of the available reports to a normalized locale. Therefore, en-us 

becomes en and fr-fr becomes fr. 

Because both report and the user locale maps to fr, the user having the user locale fr-ca will see 

the report saved with the locale fr-fr. 

Example 2 

The user’s locale and the report locales all map to the same language. ReportNet chooses 

which locale to use. For example, if a user’s locale is en-ca (English-Canada) and the reports 

are available in en-us (English-United States) and en-gb (English-United Kingdom), ReportNet 

maps each locale to en. The user will see the report in the locale setting that ReportNet 

chooses. 



Example 3 

Map Product Languages 

The report and the user locales do not map to a common language. ReportNet chooses the 

language. In this case, you may want to configure a mapping. For example, if a report is 

available in en-us (English-United States) and fr-fr (French-France), but the user locale is es-es 

(Spanish-Spain), ReportNet chooses the language. 

Steps 



3. Click the Content Locale Mapping tab. 

4. Click Add. 

5. In the Key box, type the user locale: 

• To ensure all regions for a user locale see content in a specific language, type the 

language portion of the locale, followed by a dash (-) and an asterisk (*). 

For example, type fr-* 

• To ensure a user locale (language-region) sees content in a specific language, type the 

complete locale. 

For example, type fr-ch 

• To map a preferred language to another language, type the preferred language portion 

of the locale. 

For example, type zh 

Tip: To specify which locale to use as the default, use the wildcard character (*) for the Key 

value and then, in the Locale Mapping box type the locale. 

6. In the Locale Mapping box, type the language portion of the locale. 

User locales specified in the Key box will see content in this language. 

7. Repeat steps 3 to 5 for other mappings you want to do. 

8. Click OK. 


Use the Product Language Mappings table to specify the language used in the user interface 

when the language specified in the user’s locale is not available. 

You can ensure that all regions for a locale use the same language, or that a specific, complete 

locale (language-region) uses a particular language. 

By default, the user sees the product interface in the language that matches the language 

setting of the user locale. 

Steps 



3. Click the Product Language Mappings tab. 

4. Click Add. 



Configuring Fonts 

5. In the Key box, type the user locale: 

• To ensure all regions for a locale see the user interface in a specific language, type the 

language portion of the locale, followed by a dash (-) and an asterisk (*). 

For example, type es-* 

• To ensure a complete locale (language-region) see the user interface in a specific 

language, type the complete locale. 

For example, type es-es 

• To map a preferred language to another language, type the preferred language portion 

of the locale. 

For example, type zh 

Tip: To specify which locale to use as the default, use the wildcard character (*) for the Key 

value and then, in the Locale Mapping box type the locale. 

6. In the Locale Mapping box, type the language portion of the locale. 

User locales specified in the Key box will see content in this language. 

7. Repeat steps 3 to 5 for other mappings you want to do. 

8. Click OK. 


ReportNet uses fonts 

• to display HTML reports and pages in browsers 

• to render PDF reports on the ReportNet server 

• to render charts used in PDF and HTML reports 

To show output correctly, fonts must be available where the report or chart is rendered. In the 

case of charts and PDF reports, the fonts must be installed on the ReportNet server. If a 

requested font is not available, ReportNet substitutes a different font. 

Because HTML reports are rendered on a browser, the required fonts must be installed on the 

computer of each ReportNet user who will read the HTML report. If a requested font is not 

available, the browser substitutes a different font. 

If you want to use a new font in your reports, you must 

❑ add the font to the list of supported fonts 

❑ specify the file location of the new font 

❑ map the new font to the physical font name, if required 

Add Fonts to the ReportNet Environment 

You can add fonts to the list of supported fonts in your ReportNet environment if you want to 

generate reports that use fonts that are currently not available. You can also remove fonts. 

By default, ReportNet uses a set of global fonts, which are available on all ReportNet server 

computers. 

Steps 


2. From the Actions menu, click Edit Global Configuration. 

3. Click the Fonts tab. 

4. Click Add. 

Tip: To remove a font from the list of supported fonts, click the box next to the font name and 

then click Remove. 

5. In the Supported Font Name box, type the font name and then click OK. 


All global fonts, including new fonts that you add, must be installed on all ReportNet computers 

in your environment. Otherwise, you must map the global font to an installed, physical font. 



Specify the Location of Available Fonts 

You must specify the installation location of all fonts, including fonts that you add to the list of 

supported fonts. 

By default, the list of fonts consists of fonts installed in the crn_location/bin/fonts directory of the 

ReportNet computer. If ReportNet is installed on a Windows computer, it also uses the fonts 

installed in the Windows font directory. 

You specify the font location on all computers where the report server is installed. 

Steps 

1. On each report server computer, start Cognos Configuration. 


3. In the Properties window, in the Value box for the Physical font paths property, specify the 

location of the fonts. 

Tip: If there are multiple font paths, separate each path by a semicolon (;). 


Map Supported Fonts to Installed Fonts 

You can substitute global fonts, which are not installed on the computer, for physical fonts. 

For example, you add a font to the list of supported fonts that is not installed on the ReportNet 

computer. You can specify which font to use as a substitute. 

You map fonts on each computer where the report server is installed. 

No mapping is required if you add a font to the supported font list that is installed on ReportNet 

computers. However, you must specify the location of the font. 

Steps 

1. On each report server computer, start Cognos Configuration. 


3. In the Properties window, click the Value box next to the Physical fonts map property, and 

then click the edit button. 

The Edit Physical Font Mappings dialog box appears. 

4. Click Add. 

Tip: To remove a font, select the check box next to the font and click Remove. 

5. In the Global Font Name box, type the name of the font you added to the supported font 

list. 

6. Click the Physical Font Name box. 

7. If you know the physical font name, type it. Otherwise, click the edit button. In the Select a 

font name dialog box, click Search Now and then click a font name from the results. 

8. Repeat steps 4 to 7 for each global font that requires mapping. 

9. Click OK. 


Now, if required, you must specify the installation location of the fonts. 

Change the Default Font for Reports 

You can change the default font that ReportNet uses for reports. You see this default font when 

you open a report. 

You change the default font on the computer where Content Manager is installed. After you 

make the change, the font becomes the default for all computers in your installation. 

Ensure that the default font is installed on all computers in your ReportNet installation. 



Steps 



3. In the Properties window, for the Default font, type the font you want to use as the default 

for reports. 

4. On all report server computers, ensure that the installation location of the default font is 

specified in the Physical font paths property or that the font is in the Windows font 

directory. 

Configure Cognos Portal Services 

For most deployments of Cognos Portal Services you must modify some Cognos Portal 

Services property settings. The default property settings are only appropriate for a single 

computer installation that uses anonymous access. This type of installation is typically used for 

proof of concept purposes. 

The most common changes are to specify the details about the host of the Cognos Portal 

Services web content, and to specify the authentication method used by ReportNet. 

For more information, see the Cognos Portal Services Administration Guide. 

Specify the Location of Cognos Portal Services Web Content 

To support access to the required Web content from a client browser on a different computers, 

you must specify details about Cognos Portal Services computer. 

Steps 

1. On the computer where you installed the report server, start Cognos Configuration. 

2. In the Explorer window, under Environment, click Cognos Portal Services. 

3. In the Properties window, click the Value box beside Web Content URI. 

4. Replace localhost with a valid host name or IP address, and, if necessary, replace the 

default port number. 

The Web Content URI host and port number should be the same as the Gateway URI that 

appears under Environment. 


Specify the Authentication Method 

If ReportNet is configured to use an authentication provider, you must change the default 

property setting from anonymous logon to the appropriate authentication method. If SAP BW 

and SAP EP are configured to share the SAP logon ticket, you can use the Single Sign-on 

option. For other authentication configurations, you must use the Logon As option and specify 

information about the common profile that is used by all users that access ReportNet content 

using SAP Enterprise Portal. 

Steps to Use Single Signon 



3. In the Properties window, click the Value box beside Authentication Method, and then 

click Single Sign-On. 

4. Specify a value for Namespace ID. 


Steps to Use a Common Logon Profile 





3. In the Properties window, click the Value box beside Authentication Method, and then 

click Logon As. 

4. Specify values for Namespace ID, Username, and Password. 


Manage the Applicatons.xml File in a Distributed Environment 

If you use the applications.xml file as part of a custom application, all report server computers in 

a distributed environment must reference the same applications.xml file. You should not have 

multiple instances of the applications.xml file. 

Steps 




3. In the Properties window, click the Value box beside Location of ’applications.xml’. 

4. Replace localhost with a valid host name or IP address, and, if necessary, replace the 

default port number. 


After you configure ReportNet components and test the installation and configuration, you can 

install and configure the Windows modeling tool, Framework Manager. 




Chapter 5: Installing Framework Manager 

When you install Framework Manager, the metadata modeling tool for ReportNet, all required 

files are copied to one computer. Default settings chosen by Cognos are used for the 

configuration. However, you may want to change these default settings if existing conditions 

make the default choices inappropriate, or if you installed ReportNet on a different computer. 

You can also install two migration utilities, which allow you to migrate Series 7 Architect models 

and Impromptu catalogs to Framework Manager. For information about installing and using the 

utilities, see the Metadata Migration User Guide on the Cognos support site 

(http://support.cognos.com). 

Use this checklist to guide you through the installation process for Framework Manager: 

❑ Check your system requirements. 

❑ Review the default settings. 

❑ Install Framework Manager. 

After you complete these tasks, the installation process is complete and you can configure 

Framework Manager (p. 67). 

System Requirements for Framework Manager 

Before you install Framework Manager, ensure that the Windows computer meets ReportNet’s 

software and hardware requirements. The size of the models you create affects the hardware 

requirements. You may require additional resources, such as disk space, depending on the size 

of your models. 

The following table lists the minimum hardware and software requirements to run Framework 

Manager. 

Requirement 


RAM 

Disk space 

Database 

Other 

SAP BW 

Specification 

Windows 

Minimum: 512 MB 

Recommended: 1 GB 

Minimum: 500 MB of free space on the drive 

that contains the temporary directory used by 

the ReportNet 

Database connectivity set up 

Microsoft Data Access Component (MDAC) 

2.6 or later for use with product samples 

The following SAP Front-End components 

installed on each ReportNet server computer: 

• SAP GUI 6.20 

• BW Add-on 









Default Settings for Framework Manager 



crnstartup.xml file in the crn_location\configuration directory. 

Component Default Description 

Gateway 

SDK URI 





gateway 


Log Server Port 9362 The port used by the local log 

server 

Install Framework Manager 

You can install Framework Manager on the same computer as ReportNet components, or on a 

different computer. 

Before you install Framework Manager, we recommend that you close all programs that are 

currently running to ensure that the installation program copies all the required files to your 

computer. 

Also, ensure that you have administrator privileges for the Windows computer you are installing 

on. 

We recommend that you install and configure all ReportNet server components, before you 

must install Framework Manager. 

If you are installing Framework Manager in the same directory as ReportNet, stop any 

ReportNet services that are running. Otherwise you are prompted to do so during the 

installation. 

Tips 

• If you are not an administrator, ask your system administrator to add you to the 

Administrator group on your computer. 

• If you use an Oracle database as a data source for your reports, you must set the 

NLS_LANG (National Language Support) environment variable on each computer where 

Framework Manager and the ReportNet server is installed. This variable enables 

multilingual support. The value of the variable determines the locale-dependent behavior of 

ReportNet. Error messages, sort order, date, time, monetary, numeric, and calendar 

conventions automatically adapt to the native language and locale. 

The NLS_LANG environment variable has three components: 

• language 

• territory 

• character set 

To set the NLS_LANG environment variable, type: 

NLS_LANG = language_territory.UTF8 

An example is: NLS_LANG = JAPANESE_JAPAN.UTF8 



Steps 


1. Insert the Framework Manager for Windows CD and then open the installation menu. 

The Welcome page of the installation wizard should appear. 

2. If no Welcome page appears, in the win32 directory on the CD, double-click the 

xwsetup.exe file. 

3. Select the language to use for the installation. 

4. Follow the directions in the installation wizard to copy the required files to your computer, 

5. In the Finish page of the installation wizard: 

• If you want to configure ReportNet components immediately, click Start Cognos 


• If you want to see late-breaking information about Cognos ReportNet, click View the 

Readme. 


Use the Windows Start menu to start Cognos Configuration from the shortcut folder. 

After you install Framework Manager on your Windows computer, some configuration tasks may 

be required to ensure that it works in your reporting environment (p. 67). 




Chapter 6: Configuring Framework Manager 

After you install Framework Manager on your Windows computer, you configure it so that it 

works in your reporting environment. 

Some configuration tasks are optional. You perform them to change the default property values 

used by Framework Manager. 

If you install Framework Manager on the same computer as ReportNet, no configuration is 

required if you 

• configure your Web server using the default virtual directories 

• use the default ports 

• use the default resources 

• use the default cryptographic settings 

If the default configuration is suitable, you can test the installation (p. 75). 

Otherwise, if you want to change the default configuration values additional configuration is 

required (p. 68). 

Start Cognos Configuration 

Use the configuration tool, Cognos Configuration, to configure ReportNet components, or to 

start and stop ReportNet services. 

You can run the Cognos Configuration in silent mode, as part of an unattended installation. 

You can start Cognos Configuration on the last page of the installation wizard. 

To start Cognos Configuration in interactive mode: 

• From the Start menu, click Programs, Cognos ReportNet, Cognos Configuration. 

Configure Framework Manager for Distributed 

Installations 

If you install Framework Manager on a different computer from ReportNet, you must configure it 

to communicate with ReportNet. 

We recommend that you install and configure ReportNet components before you configure 

Framework Manager. However, you must first install and configure Content Manager and then 

start the ReportNet service on the Content Manager computer before you configure Framework 

Manager. This ensures that the certificate authority service issues a certificate to the 

Framework Manager computer. 

Ensure that the Web server is configured and running. 

Steps 

1. On the computer where you installed Framework Manager, start Cognos Configuration. 




3. In the Properties window, in the Gateway URI box, type the appropriate value. 

• To use ISAPI, replace cognos.cgi with cognosasapi.dll. 

• To use apache_mod, replace cognos.cgi with mod_cognos.dll. 

• To use a servlet gateway, use the following syntax: 

http[s]://host:port/contextName/servlet/Gateway 

Note: contextName is the name you assigned to the ServletGateway Web application 

when you deployed the ServletGateway WAR file. 

4. Change the host name portion of the Gateway URI from localhost to either the IP address 

of the computer or the computer name. 

5. Specify the value for the SDK URI: 

• If your Web server is configured not to allow anonymous access, type the Dispatcher 

URI, ensuring that you change the host name in the URI from localhost. 

• If your Web server supports chunking, type the Dispatcher URI, ensuring that you 

change the host name in the URI from localhost. 

• Otherwise, type the same value you specified for the Gateway URI, ensuring that you 

change the host name in the URI from localhost. 


provider. 

7. Under the Certificate Authority settings property group, for the Password property, type 

the same password you configured on the Content Manager computer. 


Framework Manager is now configured to communicate with ReportNet. You can change default 

configuration settings if required for your environment, or test your installation and configuration. 

Changing Default Configuration Settings 

Change a Port 

When you install ReportNet components, the installation uses default configuration settings. If 

you have any reason not to use these default values, such as a port is being used by another 

process, use Cognos Configuration to change the value. 



You can also change the default behavior of ReportNet. For example you can 

• change a port 

• configure SSL protocol 

• change temporary file properties 

• configure cryptographic settings 

• configure source control systems 

• change the Gateway URI to use an alternate gateway 

• setting up data sources 

If you have any reason not to use a default port, such as it is used by another process, you can 

change it. 


Internal dispatcher URI property. Because the change affects all the URIs that are based on the 

local dispatcher, you must change the URIs of all local components. By default, local 

components contain localhost in the URI. 








Steps 


2. In the Explorer window click the appropriate group or component: 





contain localhost. 


Configure SSL Protocol 

You can configure ReportNet components to use the Secure Sockets Layer (SSL) protocol for 

• internal connections only 

• external connections only 

• internal and external connections 

• connections to local and remote log servers. 

If you configure SSL only for internal connections, ReportNet components on the local computer 

communicate using this protocol. The dispatcher listens for secure connections on a different 

port than for remote, http requests. Therefore, you must configure two dispatcher URIs. 

If you configure SSL only for external connections, communications from remote ReportNet 

components to the local computer use the SSL protocol. You must configure the dispatcher to 

listen for secure, remote requests on a different port than local, http requests. 

If you configure SSL for all connections, the dispatcher can use the same port for internal and 

external connections. Similarly, if you do not use SSL for local or remote communication, the 

dispatcher can use the same port for all communications. 

You must also update the Content Manager URI, SDK URI, and Gateway URI to use SSL, if 

required. 

Tomcat Connectors 

When the internal and external dispatcher URIs are the same, only one HTTP/1.1 connector is 

required in Tomcat’s configuration file, the server.xml file, located in the 

crn_location/tomcat4.1.18/conf directory. The port number in the dispatcher URIs is used to 

update the port number in the appropriate non-SSL Coyote HTTP/1.1 or SSL Coyote HTTP/1.1 

connector. 

If the internal dispatcher URI is prefixed with http but the external dispatcher URI is prefixed with 

https, or vice versa, both the non-SSL Coyote HTTP/1.1 and SSL Coyote HTTP/1.1 connectors 

are enabled in the server.xml file. 

Distributed Installations 

In distributed installations, if you are using the ReportNet certificate authority service, you must 

first configure all ReportNet computers to use the non-secure (http) protocol before you 

configure ReportNet to use the SSL protocol. You must do this because you cannot set up the 

SSL protocol before trust has been established. 

Also, ensure that you follow the required order of configuring computers in a distributed 

environment. That means that you must first configure the computer where Content Manager is 

installed and then start the services on this computer before you configure other computers or 

start services on other computers. By first configuring the Content Manager computer and 

starting the services, you ensure that the certificate authority service on the Content Manager 

computer can issue certificates to other computers in the ReportNet environment. 

After you configure all computers in the distributed installation to use the default, non-secure 

protocol, we recommend that you test your installation to ensure that ReportNet is working 

properly. After you test your installation, you can configure the SSL protocol. 



When you configure ReportNet to use the SSL protocol, ensure that you first configure the 

Content Manager computer to use the protocol and start the services on the Content Manager 

computer. After you do this, you can configure the SSL protocol on other ReportNet computers 


Add a Computer to an Installation 

If you later add a computer to your distributed environment and SSL is enabled for external 

connections, you must reconfigure the Content Manager computer to use the non-secure 

protocol. Then, you start the services on the Content Manager computer. This ensures that the 

certificate authority service that is installed on the Content Manager computer can issue a 

certificate to the new computer. After the Content Manager computer is configured and running, 

you must configure the new computer to use the non-secure protocol. You must then save your 

configuration on the new computer so that the computer can get the certificate from the Content 


After this occurs, you can re-enable SSL on the Content Manager computer and then configure 

the new component to use SSL. 

Add a Component to a Computer 

You can later add a component to the same location as other ReportNet components. If the 

existing components currently use the SSL protocol, you do not have to disable the SSL 

protocol on the Content Manager computer before configuring the new component to use SSL. 

The computer has a certificate and the certificate is in a known location. 

However, you can also add a component to a different location on the same computer as other 

ReportNet components. If the existing components use SSL, you must disable the SSL protocol 

on the Content Manager computer before configuring the new component to use SSL. Another 

certificate is issued for this new installation when you save your new configuration. After this 

occurs, you can re-enable SSL on the Content Manager computer and then configure the new 

component to use SSL. 

Steps for a new installation 



3. To use SSL protocol, you must specify passwords for the ReportNet encryption key stores. 


5. In the Properties window, type the appropriate values for the Internal dispatcher URI and 

External dispatcher URI values: 

• To configure SSL for internal connections only, for the Internal dispatcher URI 

property, type https and a port for SSL communication. For the External dispatcher 

URI property, type http and use the default or another available port. 


• To configure SSL for external connections only, for the External dispatcher URI 

property, type https and a secure port. For the Internal dispatcher URI property, type 

http and use the default or another available port. 


• To configure SSL for all connections, type the same URI for both the Internal 

dispatcher URI and External dispatcher URI properties. Type https and a secure 

port, such as 9343. 

Note: You do not have to use port 9343, the default SSL port. You can choose any available 

port. 

6. Configure the SSL protocol for the other environment URIs, including the Content Manager 

URI, the SDK URI and Gateway URI. 

• For internal connections only, type https in the URIs that contain localhost. 

• For external connections only, type https in the URIs that do not contain localhost. 

• For all connections, type https in all the URIs. 

7. In the Explorer window, click Logging. 



8. In the Properties window, set the following properties to True: 

• Enable TCP 

• Enable SSL 

9. If you configured a remote log server, in the Explorer window, under Logging, click the 

name of the remote log server and then, in the Properties window, set the Enable SSL 

property to True. 


Configure Temporary File Properties 

You can change the location where ReportNet stores recently viewed reports, and you can 

choose to encrypt their content. By default, ReportNet stores temporary files in the 

crn_location/temp directory and the files are not encrypted. 

We recommend that you first set up read-only access for all users to the crn_location directory. 

Steps 



3. In the Properties window, for the Temp folder property, specify the new location. 

4. If you require the content of temporary files to be encrypted, set the Encrypt temporary 

files property to True. 

5. Ensure that the user account under which ReportNet runs has the appropriate privileges to 

the temporary files location. For example: 

• on Windows, full control privileges 

• on UNIX, read-write privileges 

Configure Cryptographic Settings 

ReportNet requires a cryptographic provider; otherwise it will not run. 

You can configure cryptographic and cryptographic provider settings, including the following: 

• advanced algorithms 

These include signing, digest, and confidentiality algorithms. 

• common symmetric key store (CSK) properties 

The CSK is used by ReportNet components to encrypt and decrypt data. 

• signing key store properties 

The signing key pair includes the private key used to generate the digital signature and the 

public key used to verify authenticity. 

• encryption key store properties 

The encryption key pair includes the private key used to encrypt data and the public key 

used to decrypt data. 

ReportNet requires a cryptographic provider. By default, the cryptographic provider for 

ReportNet uses keys up to 40 bits in length for data encryption and secure sockets layer (SSL) 

protocol. You can configure other cryptographic providers which use key sizes greater than 40 

bits, such as the Enhanced Encryption Module for OpenSSL or the Enhanced Encryption 

Module for Entrust, available from Cognos. For more information, see the Enhanced Encryption 

Module for OpenSSL Installation and Configuration Guide or the Enhanced Encryption Module 

for Entrust Installation and Configuration Guide. 

Steps for Cryptographic Settings 


2. In the Explorer window, under Security, click Cryptography. 



3. In the Properties window, change the default values by clicking the Value box and then 

selecting the appropriate value: 

• If you do not want to store the CSKs locally, under CSK settings, change Store 

symmetric key locally to False. Then change the Common symmetric key store 

location to the key store location of the Content Manager computer. 

When Store symmetric key locally is False, the key must be retrieved from Content 

Manager. 

• If you want the computers at both ends of a transmission to prove their identity, under 

SSL Settings, change Use mutual authentication to True. 

We recommend that you do not change the Use confidentiality setting. Set this 

property to true to ensure all transmissions are encrypted. 

• If you want to change the confidentiality algorithm, under Advanced algorithm 

settings, change Confidentiality algorithm to the other 40-bit key value. 

If you select and try to save an algorithm that does not use a 40-bit key, you will receive 

an error message. These other algorithms are reserved for use with other cryptographic 

providers. For more information, see the Enhanced Encryption Module for OpenSSL 

Installation Guide or the Enhanced Encryption Module for Entrust Installation Guide. 


After you configure the cryptographic provider, passwords in your configuration and any data 

you create are encrypted. 

Steps for Cryptographic Provider Settings 



• If you want to use a third-party certificate authority, under Certificate Authority 

settings, change Use third party CA to True. 

• If you want to change the location of the signing keys, under Signing key settings, 

change the Signing key store location property to the new location. 

• If you want to change the location of the encryption keys, under Encryption key 

settings, change Encryption key store location to the new location. 


If you use a third-party Certificate Authority (CA) server, you must now configure ReportNet to 

use the CA. 

Configure a Source Control System 

To help you manage, share and secure different versions of your metadata you can configure 

Framework Manager to use a source control system. 

You must already have one of the following source control system clients set up on the same 

computer as Framework Manager: 

• ComponentSoftware Concurrent Versions System 

• Visual Source Safe 

For more information about installing and setting up source control systems, see the Framework 

Manager User Guide. 

Steps 


2. In the Explorer window, under Environment, right-click Source Control Systems, click 

New resource, Source Control System. 

3. In the Name box, type a name for your source control system. 

4. In the Type box, select a source control system from the list. 

5. Click OK. 

6. In the Properties window, type the appropriate values for the mandatory properties. 




Change the Gateway URI to Use an Alternate Gateway 

The value you specify for the Gateway URI property depends on 

• the gateway you use 

• whether the gateway is on the same computer as Framework Manager 

• whether you plan to distribute reports 

Ensure that you also configure ReportNet to use alternate gateways. 

Steps 


2. Click Environment. 

3. In the Properties window for the Gateway URI property, replace the cognos.cgi portion of 

the URI with the appropriate value: 

• If you use Microsoft Internet Application Programming Interface (ISAPI) to support 

Microsoft Internet Information Services on Windows, type cognosasapi.dll. 

• If you use apache_mod to support Apache Web Server, type mod_cognos.dll. 

• If you use a servlet gateway, use the following syntax: 

http[s]://host:port/contextName/servlet/Gateway 

Note: contextName is the name you assigned to the ServletGateway Web application 

when you deployed the ServletGateway WAR file. 

4. Change the host name portion of the Gateway URI from localhost to either the IP address 

of the computer or the computer name. 

To be able to open reports that are sent by email, you must change the host name portion of 

the Gateway URI from localhost. Otherwise the URL in the email will contain localhost and 

remote users will not be able to open the report. 


After you configured Framework Manager, you can test the Framework Manager installation and 

configuration. 

Setting Up Data Sources 

Framework Manager creates and manages metadata required for the reporting functions 

performed by ReportNet. Because this metadata is derived from data sources in multi-platform, 

or multilingual environments, there are several things you must think about or do when you set 

up data sources. Commonly, these things depend on the third-party technology you use for you 

data source. 

Ensure that you install the appropriate language packs to support the character sets and 

currency symbols you use. 

Oracle 

To enable multilingual support, you must set the NLS_LANG (National Language Support) 

environment variable on each computer where Framework Manager and the ReportNet server 

is installed. 

DB2 

To enable multilingual support, you can set the DB2CODEPAGE environment variable to a value 

of 1252. 

For more information about whether to use this optional environment variable, see the DB2 


SAP BW 

To enable Framework Manager to retrieve metadata from SAP BW, proper authorizations must 

be set up within the SAP system. 



The following authorization objects must be configured. Some of the values shown, such as *, 

are default values that you may want to modify for your environment. 

Authorization object Field Value 

S_RFC Activity 16 

Name of RFC to be 

protected 


be protected 

SYST, RSOB, SUGU, 

RFC1, 

RS_UNIFICATION, 

RSAB, SDTX, 

SU_USER 

FUGR 

S_TABU_DIS Activity 03 

Authorization Group 

&NC& 

S_USER_GRP Activity 03, 05 

User group in user 

master main 

* 

S_RS_COMP Activity * 

Info Area 

InfoCube 

Name (ID) of 

reporting component 

Type of reporting 

component 

InfoArea Technical 

Name 

InfoCube Technical 

Name 

* 

* 

S_RS_COMP1 Activity * 

Name (ID) of 

reporting component 

Type of reporting 

component 

Owner (Person 

Responsible) 

* 

* 

* 

S_RS_HIER Activity 71 

Hierarchy Name 

InfoObject 

Version 

Hierarchy Name 

InfoObject Technical 

Name 

Hierarchy Version 

S_RS_ICUBE Activity 03 

InfoCube sub-object 

DATA 

DEFINITION 



Authorization object Field Value 

InfoArea 

InfoCube 

InfoArea Technical 

Name 

InfoCube Technical 

Name 

Tips 

• &NC& represents any table that does not have an authorization group. For security reasons, 

create a new authorization group and assign the table RSHIEDIR to it. The new 

authorization group restricts the user’s access to the above table only, which is needed by 

Framework Manager. Create the new authorization group as a customization in the SAP 

system. 

• For more information about SAP BW authorization objects, go to Transaction SU03. 

Test the Framework Manager Installation and 

Configuration 


Before you can use Framework Manager, you must start the ReportNet service. 

Note: ReportNet cannot access any data, unless the data is first packaged in Framework 

Manager. 

Steps 

1. Start ReportNet. 

2. Start Framework Manager. 

3. Create a new project. 

4. Publish the project. 

You successfully installed and configured ReportNet. To take a tour of ReportNet, start Cognos 

Connection and select Quick Tour. For information about using different ReportNet components, 

see their documentation. 




Chapter 7: Advanced Configuration Options 

Advanced configuration options are changes that you make after installation to the configuration 

properties of the resources that ReportNet components use.You cannot use Cognos 

Configuration to make these changes. Advanced configuration options enhance security, 

improve performance, or change the default behavior of ReportNet. 

Change the JVM Used by ReportNet 

To better suit your reporting environment, you can change which Java Virtual Machine (JVM) 

ReportNet uses, using the following criteria: 

• Java HotSpot Client VM 

Use this JVM for proof of concept, demonstration, or development environments. This JVM 

is specially tuned to reduce both the startup time for applications and the memory footprint. 

This is the default setting for ReportNet installation on Windows. On UNIX platforms, 

Cognos does not provide a Java Runtime Environment (JRE). Therefore, the default JVM 

that ReportNet uses depends on the current setting in your existing JRE. 

• Java HotSpot Server VM 

Use this JVM for long-running server applications to maximize operating speeds when 

performance is more important than fast startup time. 

• Classic VM 

For compatibility reasons, you may have to use the Classic VM. Not all Java Development 

Kits (JDKs) have a Classic VM. In UNIX, if you are using JavaSoft Solaris JDK 1.3 or any of 

the JavaSoft 1.4 JDKs, you have only the HotSpot VM. 

For more information, see the Sun Microsystems Inc. Web site. 

Because all application servers, such as Tomcat, WebLogic, and WebSphere, require a JVM to 

run, you must already have one installed. 

Steps 

1. Go to the location where your Java Runtime Environment (JRE) libraries are installed: 

• In Windows, go to crn_location\bin\jre\1.3.1\lib. 

• In UNIX, go to JAVA_HOME/jre/lib. 

2. Open jvm.cfg in an editor. 

3. Ensure that the JVM that you want to use is the first uncommented line. Enter the 

appropriate text for the JVM you want to use: 

JVM 

Hotspot Client 

Hotspot Client 

Classic 

Text 

hotspot 

server 

classic 

4. Save and close the file. 



Configuring ReportNet to Use An Alternative Application 

Server 

Instead of using Tomcat, the default servlet container included with ReportNet, you can 

configure ReportNet to use either a WebSphere or a WebLogic application server. This optional 

configuration may be appropriate if you want to use an existing application server 

implementation. It may provide greater flexibility for supporting additional applications. 

Before you configure ReportNet to use an alternative application server, do the following: 

❑ Install ReportNet and select the components that will run on each computer. 

❑ If required, the Oracle and DB2 clients must be installed and set up prior to running 

ReportNet. The appropriate environment variables must be set prior to starting the 

application server. 

For information about setting up the database client on UNIX, see "Set Up the Database 

Client for the Content Store Database" (p. 23), or on Windows, see "Set Up the Database 

Client for the Content Store Database" (p. 30). 

❑ Install the application server or identify an existing application server that you can use for 

ReportNet. 

❑ If you have WebLogic 6.1 SP4 or WebLogic 7.0 SP2, add the chunking patch to the 

WebLogic installation. 

• For WebLogic 6.1 SP4, add CR102751_61sp4.jar to WebLogic_location 

/wlserver6.1/lib, or upgrade to SP5. 

• For WebLogic 7.0 SP2, add CR100172_70sp2.jar to 

WebLogic_location/weblogic700/common/lib. 

This patch corrects a servlet container issue where HTTP chunked requests are not 

handled properly. 

Tip: To obtain the required chunking patch for the servlet container issue, contact BEA 

support. 

❑ On UNIX, to avoid file permission conflicts, create a new UNIX group. You could call this 

group reportnet. This group must contain the user that starts WebSphere or WebLogic and 

the user that owns the ReportNet files. Change the group ownership of the ReportNet files 

to the reportnet group and change the file permissions for all ReportNet files to GROUP 

READABLE/WRITABLE/EXECUTABLE. 

❑ If ReportNet was previously configured to use Tomcat, you must complete additional steps 

to prepare the ReportNet installation (p. 86). 

Configure ReportNet to Use a WebSphere Application Server 

You can use a WebSphere application server instead of Tomcat, the default. The following steps 

are based on a default WebSphere installation. You can also configure a customized 


Steps 

1. If ReportNet was previously configured to use Tomcat, you must stop the ReportNet service 

and then delete the cryptographic keys (p. 86). 

2. On each computer that includes ReportNet and WebSphere, from the 

crn_location/bi/jre1.3.1/lib/ext directory, copy the contents of the ext directory to 

WebSphere_location/java/jre/lib/ext. 

Important: Some or all of the jar files may already exist in the WebSphere ext directory. If 

so, do not overwrite the WebSphere versions of the files. 



3. Set the JAVA_HOME environment variable: 

• On Windows, set a system environment variable. 

• On UNIX, from crn_location/bin, edit crconfig.sh. 

Operating 

System 

Windows 

UNIX 

Environment Variable Command 

set JAVA_HOME= 

WebSphere_location\AppServer\java\jre 

For csh: setenv JAVA_HOME= 

WebSphere_location/AppServer/java/jre 

For ksh: JAVA_HOME= 


export JAVA_HOME 

For sh: JAVA_HOME= 



4. From the crn_location/bin, start Cognos Configuration: 

• On Windows, type crconfigw.exe -java:env 

• On UNIX, type crconfig.sh 

5. In the Explorer window, expand Environment and then change the following properties to 

use the WebSphere port number and host name. The WebSphere default port is 9080. 

• Internal Dispatcher URI 

• External Dispatcher URI 

• Content Manager URI 

• SDK URI 

6. Under Environment, ReportNet Service, right-click Cognos ReportNet, and then click 

Delete. 

Now ReportNet will not run as a service, which is not required for WebSphere. 

7. Complete other required configuration changes such as 

• specifying properties for the Content Manager database 

• entering user IDs and passwords 

If you used the default settings for the ReportNet installation, you may only have to make 

minor changes to the default configuration settings (p. 40). You can review the configuration 

for single computer installations (p. 33), or for distributed installations (p. 37), to determine if 

there are any additional changes required. 

8. Save the configuration and close Cognos Configuration. 

If you are prompted to start the ReportNet service, click No. 

Cryptographic keys are created using the WebSphere JVM. 

9. From WebSphere_location/AppServer/bin, open the startServer.bat file (Windows) or 

startServer.sh file (UNIX) in an editor. 



10. Add a new environment variable entry, CRN_ROOT, that points to crn_location. 

Operating 

system 

Windows 

UNIX 

Environment variable command 

Set CRN_ROOT= crn_location 

For csh: setenv CRN_ROOT crn_location 

For ksh: CRN_ROOT=crn_location 

export CRN_ROOT 

sh: CRN_ROOT=crn_location 


11. Append crn_location/bin to the appropriate environment variable. 


Windows 

AIX 

Solaris 

HPUX 


PATH 

LIBPATH 


SHLIB_PATH 


13. From the crn_location/war/p2pd directory, run the following script: 



This creates the Web archive file, p2pd.war in crn_location. You will install this file in the 

WebSphere environment as an Enterprise Application. 

14. Start the WebSphere Application Server, and then start the WebSphere Administrative 

Console. 

15. Add a JVM system property (WebSphere 4.x) or a JVM custom property (WebSphere 5.x) 

named CRN_ROOT that points to the crn_location, and then save the changes. 

16. Install a new Enterprise Application using the p2pd.war file and use p2pd as the application 

name and the context root. 

17. If you use WebSphere version 5.x, ensure that the Classloader_Mode is set to 

PARENT_LAST for the p2pd application and the web_module. 

18. Save changes. 

19. Stop and then restart the WebSphere Enterprise Application used for ReportNet. 

20. If ReportNet was previously configured to use Tomcat, you must unregister the associated 

dispatcher (p. 86). 

If the Web server is configured and started, the configuration is complete and you can now test 

ReportNet. 

Enable SSL for WebSphere 

You must complete the following additional configuration to enable SSL. 

Steps 

1. Configure WebSphere to use SSL. 

This will generate an SSL server certificate. 

For more information, refer to the WebSphere documentation 

2. Copy the CA certificate to the crn_location/bin directory and rename the file to ca.cer. 

This file must be Base-64 encoded X.509 format. 



3. From the crn_location/bin directory: 

• On UNIX, type: 

ThirdPartyCertificateTool.sh -T -i -r ca.cer -k 

../configuration/signkeypair/jCAKeystore -p password 

• On Windows, type: 

ThirdPartyCertificateTool.bat -T -i -r ca.cer -k 


Important: You must type jCAKeystore as the name of the certificate authority key store. 

This ensures that ReportNet trusts the certificate authority that generated the server 

certificate. 

Configuring ReportNet to Use a Customized WebSphere Application Server 

To help you configure ReportNet in a customized application server environment, we suggest 

that you review the steps for configuring a default WebSphere environment (p. 78) to obtain a 

general understanding of the requirements. To configure a customized environment, you must 

design a configuration process that is appropriate for your environment. 

Use the following checklist to ensure that the configuration process you design achieves the 

required results. 

❑ Copy the encryption files from the ReportNet installation to the WebSphere installation. 

❑ Add environment variable information to the WebSphere configuration files. 

❑ Install ReportNet as an Enterprise Application in WebSphere. 

❑ If required, enable SSL. 

For more information about working with WebSphere, see the documentation included with the 

WebSphere installation. 

Configure ReportNet to Use a WebLogic Application Server 

You can use a WebLogic application server instead of Tomcat, the default. The following steps 

are based on a default WebLogic installation. You can also configure a customized environment 

(p. 85). 

Steps 

1. If ReportNet was previously configured to use Tomcat, you must stop the ReportNet service 

and then delete the cryptographic keys (p. 86). 

2. On each computer that includes ReportNet and WebLogic, copy the contents of the 

crn_location/bin/jre/1.3.1/lib/ext directory to the WebLogic_location//jre/lib/ext 

directory. 

Important: Some or all of the jar files may already exist in the WebLogic ext directory. If so, 

do not overwrite the WebLogic versions of the files. 



3. Set the JAVA_HOME environment variable. 

• On Windows, set a system environment variable. 

• On UNIX, from crn_location/bin, edit crconfig.sh. 

Operating 

System 

Windows 

UNIX 


set JAVA_HOME= 

WebLogic_location\\jre 

For csh: setenv JAVA_HOME= 

WebLogic_location//jre 

For ksh: JAVA_HOME= 



For sh: JAVA_HOME= 



4. From the crn_location/bin directory, start Cognos Configuration: 

• On Windows, type crconfigw.exe -java:env 

• On UNIX, type crconfig.sh 

5. In the Explorer window, expand Environment and change the following properties to use 

the WebLogic port number and host name. The WebLogic default port is 7001. 

• Internal Dispatcher URI 

• External Dispatcher URI 

• Content Manager URI 

• SDK URI 

6. Under Environment, ReportNet Service, right-click Cognos ReportNet, and then click 

Delete. 

Now ReportNet will not run as a service, which is not required for WebLogic. 

7. Complete other required configuration changes such as 

• specifying properties for the Content Manager database 

• entering user IDs and passwords 

If you used the default settings for the ReportNet installation, you may have to make other 

minor changes to the default configuration settings (p. 40). You can review the configuration 

for single computer installations (p. 33), or for distributed installations (p. 37), to determine if 

there are any additional changes required. 

8. Save the configuration and close Cognos Configuration. If you are prompted to start the 

ReportNet service, click No. 

Cryptographic keys are created using the WebLogic JVM. 

9. From the crn_location/war/p2pd directory, run the following script: 



This creates the Web archive file, p2pd.war in crn_location. You will install this file in the 

WebLogic environment. 

10. In WebLogic, create a WLS domain for ReportNet. 

Tip: To make it easier to complete the remainder of the configuration, use ReportNet as the 

domain name. If you use a different domain name, you will have to modify some path names 

shown in the following steps and the information in the template files. 

11. Start the WebLogic Application Server associated with the ReportNet domain. 



12. In the WebLogic console, create a new XML registry by changing the default settings to the 

following: 

• document builder factory 

org.apache.xerces.jaxp.DocumentBuilderFactoryImpl 

• SAX parser factory 

org.apache.xerces.jaxp.SAXParserFactoryImpl 

• transformer factory 

org.apache.xalan.processor.TransformerFactoryImpl 

13. Add the server to the targets and then apply the changes. 

14. Stop the WebLogic Application Server associated with the ReportNet domain. 

15. Create a directory called p2pd. 

• For WebLogic 6.1, create the directory in 

WebLogic_location/wlserver6.1/config/ReportNet/applications 

• For WebLogic 7.0, create the directory in 

WebLogic_location/user_projects/ReportNet/applications 

16. Extract the p2pd.war file created in step 8 to the WebLogic installation using the following 

command. 

Important: You must run the command from the p2pd directory created in step 15. A space 

and then a period are required at the end of the command. In this command, the period 

does not refer to the current directory. 

WebLogic_location//bin/jar xvfm "crn_location/p2pd.war". 

17. From the following location, open the startWebLogic.cmd file (Windows) or the 

startWebLogic.sh file (UNIX) in an editor. 

• For WebLogic 6.1: WebLogic_location/wlserver6.1/config/ReportNet 

• For WebLogic 7.0: WebLogic_location/user_projects/ReportNet 

18. Add a new environment variable entry, CRN_ROOT, that points to crn_location. 

Operating 

System 

Windows 

UNIX 


Set CRN_ROOT=crn_location 

For csh: setenv CRN_ROOT crn_location 

For ksh: CRN_ROOT=crn_location 


For sh: CRN_ROOT=crn_location 


19. Append crn_location/bin to the appropriate environment variable. 

Operating System 

Windows 

AIX 

Solaris 

HPUX 

Environment Variable 

PATH (for WebLogic 6.x) 

PRE_PATH (for WebLogic 7.x) 

LIBPATH 


SHLIB_PATH 



20. Insert the P2PD_LIB environment variable and add the required jar files to the CLASSPATH 

value (WebLogic 6.1) or PRE_CLASSPATH value (WebLogic 7.0). 

If you use a WebLogic version other than WebLogic 6.1 SP4 or WebLogic 7.0 SP2, you may 

have to remove the chunking patch entry. 

Ensure that there are no spaces in the CLASSPATH or PRE_CLASSPATH value. Use the 

correct character format. For example, on Windows use "\" instead of "/", and 

"%%" instead of "$". Replace with 

the correct path. 

Tip: To make it easier to enter this information in the startWeLogic script file, you can copy 

the information from a template file included with the ReportNet installation. The templates 

include information for all supported versions of WebLogic. The templates, 

wblg_tmplt_ux.txt for UNIX and wblg_tmplt_win.txt for Windows, are located in the 

crn_location/webcontent/documentation directory. 

• For example, for WebLogic 6.1 SP4 on UNIX, insert the following information after the 

existing CLASSPATH entry: 

P2PD_LIB=/wlserver6.1/config/ReportNet/applications/p2pd/WEB- 

INF/lib 

CLASSPATH=/wlserver6.1/lib/CR102751_61sp4.jar:$P2P 

D_LIB/xml-apis.jar:$P2PD_LIB/xercesImpl.jar:$P2PD_LI 

B/xalan.jar:$P2PD_LIB/xtsext.jar:$P2PD_LIB/xsltc.jar: 

$P2PD_LIB/i18nj.jar:$P2PD_LIB/icu4j.jar:$P2PD_LIB 

/dom4j.jar:$P2PD_LIB/commons-discovery.jar:$P2PD_LIB 

/commons-httpclient.jar:$P2PD_LIB/commons-logging.jar 

:$P2PD_LIB/jaxrpc.jar:$P2PD_LIB/jcam_jni.jar:$CLASSPATH 

• For example, for WebLogic 7.0 SP2 on UNIX, insert the following information after the 

JAVA_OPTIONS entry: 

P2PD_LIB=/user_projects/ReportNet/applications/p2pd/WEB-INF/l 

ib 

PRE_CLASSPATH=/weblogic700/common/lib/


Enable SSL for WebLogic 

28. For WebLogic 6.1, configure a new Web application using the following settings: 

• name = p2pd 

• path = WebLogic_location/wlserver6.1/config/ReportNet/applications/p2pd 

Note: WebLogic 7.0 automatically creates a Web application. 

29. Set the reload period for the Web application to -1. 

30. Add the server to the targets, and then apply the changes. 

31. Stop and then restart the WebLogic Application Server associated with the ReportNet 

domain. 

32. If ReportNet was previously configured to use Tomcat, you must unregister the associated 

dispatcher (p. 86). 

If the Web server is configured (p. 34) and started, the configuration is complete and you can 

now test ReportNet. 

You must complete the following additional configuration to enable SSL. 

Steps 

1. Configure WebLogic to use SSL. 

This will generate an SSL server certificate. 

For more information, refer to the WebLogic documentation. 

2. Copy the CA certificate to the crn_location/bin directory and rename the file to ca.cer. 

This file must be Base-64 encoded X.509 format. 

3. From the crn_location/bin directory: 








This ensures that ReportNet trusts the certificate authority that generated the server 

certificate. 

Configuring ReportNet to Use a Customized WebLogic Application Server 

To help you configure ReportNet in a customized application server environment, we suggest 

that you review the steps for configuring a default WebLogic environment (p. 81) to obtain a 

general understanding of the requirements. To configure a customized environment, you must 

design a configuration process that is appropriate for your environment. 

Use the following checklist to ensure that the configuration process you design achieves the 

required results 

❑ Create a new domain for ReportNet. 

❑ Add environment variable information to the WebLogic configuration files. 

❑ Generate an XML registry in WebLogic. 

❑ Package ReportNet into a war file that you will install in the WebLogic environment. 

❑ Modify the startWebLogic file. 

❑ Configure the WebLogic web application. 

❑ If required, enable SSL. 

For more information about working with WebLogic, see the documentation included with the 

WebLogic installation. 



Preparing Your Environment If ReportNet Previously Used Tomcat 

If you previously configured ReportNet to run in your environment using Tomcat, the default 

servlet container, and now plan to use WebSphere or WebLogic, you must: 

❑ stop the Cognos ReportNet service 

❑ delete any existing cryptographic keys before you configure the alternative application 

server 

❑ unregister dispatchers that are no longer used after you configure ReportNet to run on 

WebSphere or WebLogic 

Delete Cryptographic Keys 

Before you configure ReportNet to use a third-party application server, ensure that any 

cryptographic keys that were previously created are deleted. This ensures that the correct 

security and Java environment is used. 

Remove Dispatchers 

Steps 

1. Stop the Cognos ReportNet service using Cognos Configuration. 

2. Save and close Cognos Configuration. 

3. Back up the contents of the following directories: 

• crn_location/configuration/csk 

• crn_location/configuration/encryptkeypair 

• crn_location/configuration/signkeypair 

4. Ensure that the startup configuration does not contain encrypted passwords: 

• If timestamped versions of the crnstartup.xml files are available in the 

crn_location/configuration directory, rename the crnstartup_timestamp.xml file with the 

earliest timestamp to crnstartup.xml. 

Note: To allow you to undo some configuration changes, ReportNet creates a 

timestamped version of crnstartup.xml before applying any changes to the file. The file 

with the earliest timestamp should be the original version of the file and does not 

contain encrypted passwords. 

• If the timestamped versions of the files are not available, in Cognos Configuration, 

re-enter the passwords for the following resources or components, if they exist: Content 

Manager database, the Notification database, the Notification mail server, log database, 

and your LDAP authentication source. 

5. Delete the csk, encryptkeypair, and signkeypair directories. 

After you start the application server, remove ReportNet services that have been previously 

registered and that are no longer used. 

To access the server administration tool, you must have execute permissions for the 

Administration secured function. 

Steps 

1. Open the ReportNet portal. 

2. On the portal toolbar, click Server Administration. 

3. Click the Monitor tab. 

4. Under Type, click Dispatchers. 

A list of dispatchers appears. 

5. Select the check box for the dispatcher you want to unregister and, on the toolbar, click the 

unregister button. 

Tip: You can also unregister dispatchers by clicking More in the Actions column. 

A message confirms the action. 

6. Click OK. 



The dispatcher information is removed from Content Manager. 

Configuring ReportNet to use a Third-Party Certificate 

Authority 

By default, ReportNet uses its own certificate authority (CA) service to establish the root of trust 

in the ReportNet security infrastructure. You can configure ReportNet to use another certificate 

authority, if you already have an existing third-party certificate authority, such as iPlanet or 

Microsoft, in your reporting environment. 

When you configure ReportNet to use a third-party certificate authority, ensure that you specify 

the same information in both the command line utility tool and in Cognos Configuration. 

To configure ReportNet to use your third-party certificate authority, you must 

❑ generate ReportNet security keys and certificate signing requests to use with your 

third-party CA 

❑ add the ReportNet security keys and signing certificates to your third-party certificate 

authority 

❑ configure ReportNet to use a third-party certificate authority. 

Generate Keys and Signing Requests 

Use the command line utility to generate all the keys for the ReportNet key stores and to 

generate the certificate signing requests (CSR). 

Ensure that the encryption key store and the certificate authority key store are in the same 

location. You must run the command line tool once for each certificate request. 

The following table lists the options for the command-line tool used to generate keys and signing 

requests. 

Command 

Main operation mode 

Description 

-c Create a new CSR 

-i Import a certificate 

Operation modifiers 

-s Work with the signing identity 

-e Work with the encryption identity 

-T Work with the trust store (only with -i) 



Command 

Information flags 

Description 

-d DN to use for certificate 

-r CSR or certificate file location (depends 

on mode) 

-t certificate authority certificate file (only 

with -i) 

-p Key Store password (must be provided) 

-a Key pair algorithm. RSA or DSA. 

Default: RSA 

The following sample values are used: 

Property 

Signing certificate DN 

Value 

CN=SignCert,O=MyCompany,C=CA 

Encryption certificate DN CN=EncryptCert,O=MyCompany,C= 

CA 

Key store password 

password 

Steps 

1. Go to the crn_location/bin directory. 

2. Create the signing certificate request by typing the following command: 


ThirdPartyCertificateTool.sh -c -s -d "CN=SignCert,O=MyCompany,C=CA" -r 

signRequest.csr -k ../configuration/signkeypair/jSignKeystore -p password 


ThirdPartyCertificateTool.bat c -s -d "CN=SignCert,O=MyCompany,C=CA" -r 

signRequest.csr -k ../configuration/signkeypair/jSignKeystore -p password 

Important: You must type jSignKeystore as the name of the signing key store. 

Tip: UNIX filenames are case-sensitive and must be entered exactly as shown. 

3. Create the encryption certificate request by typing the following command: 


ThirdPartyCertificateTool.sh -c -e -d "CN=EncryptCert,O=MyCompany,C=CA" -r 

encryptRequest.csr -k ../configuration/encryptkeypair/jEncKeystore -p password 


ThirdPartyCertificateTool.bat -c -e -d "CN=EncryptCert,O=MyCompany,C=CA" -r 

encryptRequest.csr -k ../configuration/encryptkeypair/jEncKeystore -p password 

Important: You must type jEncKeystore as the name of the encryption key store. 

4. Input the certificate signing request (CSR) files into the third party certificate authority. 

For more information, see your third-party CA documentation. 

The certificate authority produces a signing certificate and an encryption certificate. 

5. Copy the contents of the CA certificate into ca.cer 

6. Copy the contents of the signing certificate into signCertificate.cer. 

7. Copy the contents of the encryption certificate into encryptCertificate.cer 

8. Copy ca.cer, signCertificate.cer, and encryptCertificate.cer to crn_location\bin. 

These files must be Base-64 encoded X.509 format. 



9. Import the signing certificate by typing the following command: 


ThirdPartyCertificateTool.sh -i -s -r signCertificate.cer -k 

../configuration/signkeypair/jSignKeystore -p password -t ca.cer 


ThirdPartyCertificateTool.bat-i -s -r signCertificate.cer -k 

../configuration/signkeypair/jSignKeystore -p password -t ca.cer 

Important: You must type jSignKeystore as the name of the signing key store. 

10. Import the encryption certificate by typing the following command: 


ThirdPartyCertificateTool.sh -i -e -r encryptCertificate.cer -k 

../configuration/encryptkeypair/jEncKeystore -p password -t ca.cer 


ThirdPartyCertificateTool.bat -i -e -r encryptCertificate.cer -k 

../configuration/encryptkeypair/jEncKeystore -p password -t ca.cer 

Important: You must type jEncKeystore as the name of the encryption key store. 

11. Import the CA certificate by typing the following command: 








Now, you must use your third-party certificate authority configuration tool to add the ReportNet 

keys and certificate signing requests to your certificate authority. For more information, see your 

third-party certificate authority documentation. 

Configure ReportNet to use a Third-Party Certificate Authority 

You must configure each ReportNet computer to use an external certificate authority by setting 

the appropriate property in Cognos Configuration. 

By setting this property, ReportNet assumes that all required keys have been generated and 

vetted by the external certificate authority. 

Ensure that the key store locations and password in Cognos Configuration match the ones you 

typed in the command-line tool. 

Steps 

1. Start Cognos Configuration 


3. In the Properties window, under Certificate Authority settings property group, click the 

Value box next to the Use third party CA property and then click True. 

Note: When you set this property to true, all properties for the certificate authority and 

identity name are ignored 

4. Configure the following properties to match the ones you typed in the command line utility: 

• Signing key store location 

• Signing key store password 

• Encryption key store location 

• Encryption key store password 

• Certificate Authority key store password 


6. If you want to start the ReportNet service, from the Actions menu, click Start. 




Chapter 8: Setting Up the Samples 

You can use the Cognos sample model, package, and reports to help you learn how to use 

ReportNet and Framework Manager. 

ReportNet provides four samples databases that contain sales and marketing information for a 

fictional company named the Great Outdoors Company that sells camping equipment. 

Before you can use the samples databases, ReportNet and Framework Manager must be 

installed, configured, and running. 

To set up the samples, you 

❑ restore the samples databases 

❑ create the data source connections 

❑ modify the sample model for Oracle and DB2, if required 

❑ import the sample package and reports into the content store 

After you complete these tasks, use ReportNet to run the sample reports, or Framework 

Manager to modify the sample model and package. You can later remove the ReportNet 

samples. 

Restore Backup Files for the Samples Databases 

To use the sample model, package, and reports, you must restore backup files for the samples 

databases. When you restore, you recreate multilingual versions of the Great Outdoors 

databases. 

The following samples databases and associated files are provided with ReportNet. Each 

database is delivered as a Microsoft SQL Server backup file, Oracle export file (.dmp), and DB2 

move files. The DB2 move files are compressed and you must extract them before you can 

restore the DB2 databases. 

Database 

description 

Great 

Outdoors 

sales 

Great 

Outdoors 

retailers 

Great 

Outdoors 

sales data 

warehouse 

Great 

Outdoors 

market 

research 

SQL Server 

file Oracle file DB2 file 

gosl gosl.dmp gosl.tar.gz 

gort gort.dmp gort.tar.gz 

gosldw gosldw.dmp gosldw.tar.gz 

gomr gomr.dmp gomr.tar.gz 

Important: You must give the restored databases the same names as the backup or export file 

names for the sample model, package, and reports to work. 

Ensure that you restore the samples databases using the UTF-8 character set. 



Before you restore the samples databases, ensure that you have 50 MB of disk space available 

in the target location. 

SQL Server Considerations 

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

Microsoft SQL Server 7. 

DB2 Considerations 

Before you restore the DB2 move files on Unix or Windows, extract the DB2 move files by using 

the gnutar -xcvf DB2_move_file_name or tar -xcvf DB2_move_file_name command. Also, 

when you set up the gosldw database in DB2, create a large buffer pool of 16k and an 

associated tablespace. 

If you use WinZip to extract the DB2 move files on Windows, ensure that the TAR file smart 

CR/LF conversion option is not selected. 

Steps 

1. On the computer where ReportNet is installed, go to the sqlserver, oracle, or db2 directory 

located in crn_location\webcontent\samples\db. 

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

directory. 

3. Restore the four samples databases with your database management tool. 

4. Create one user who has select permissions for all the tables in the restored databases. 

The Great Outdoors databases are restored. You can now create the data source connections 

in the portal. 

Create Data Source Connections to the Samples 

Databases 

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

ReportNet uses this information to connect to the samples databases and run the sample 

reports or use the sample package. 

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

samples databases. Also, ensure that ReportNet is running. 

To create data sources, you must have execute permissions for the Administration secured 

function. 

Steps 

1. Open Cognos Connection. 

2. On the toolbar, click Directory. 

3. Click the Data Sources tab. 

4. Click the new data source button. 

The New Data Source wizard appears 

5. In the Name box, type gosales and click Next. 

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

select an isolation level, and then click Next. 

The connection string page for the selected database appears. 



7. Do one of the following: 

• If you restored the samples databases in SQL Server, in the Server Name box, type the 

name of the server where the restored databases are located. In the Database name 

box, type gosl. 

• If you restored the samples databases in Oracle, in the SQL*Net connect string box, 

type the Oracle connection string. 

• If you restored the samples databases in DB2, in the DB2 database name box, type 

gosl. In the DB2 connect string box, type the DB2 connection string. 

8. Under Signons, select the User ID, Password, and Create a signon that the Everyone 

group can use check boxes, type the user ID and password for the user that you created 

when you restored the databases, and then click Finish. 

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


10. Repeat steps 4 to 9 for the goretailers samples database. Use goretailers for the data 

source name and gort for the database name. 

The Great Outdoor data source connections appear as entries in the Data Sources tab of the 

Directory tool. 

You can now import the samples unless there is a syntax error in the connection string or an 

incorrect parameter. 

Modify the Sample Model for Oracle and DB2 

The sample model is based on the gosl and gort samples databases. Because the sample 

model is built in Microsoft SQL Server, if you want to use it with the samples databases in Oracle 

and DB2, you must modify its data source properties. 

Before you can modify the sample model, the data source connections to the samples 

databases must be created. 

Steps 

1. Launch Framework Manager. 

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

3. Go to the crn_location\webcontent\samples\Models\gosales_goretailers directory, click the 

gosales_goretailers.cpf file, and then click Open. 

4. In the Project Viewer pane, expand the Data Sources folder, and click gosales. 

The properties of the data source appear in the Properties pane. 

5. Click the Content Manager Datasource property, delete the existing setting, type the name 

of the Oracleor DB2 data source. 

Tip: To edit a property value, you can click the ellipses button beside the value. 

6. Click the Catalog property and delete the existing setting. 

7. Click the Schema property, delete the existing setting, and type the name of the schema for 

Oracleor DB2 specified when you set up the data sources. 

8. Double-click the Type property, click the Interface property, delete the existing setting, and 

type OR for Oracle or D2 for DB2. 

9. To test the modified data source properties, in the Project Viewer pane, in the Data 

Sources folder, right-click gosales, and then click Test Data Source. 

A message appears to inform you whether the test was successful. 

10. Repeat steps 4 to 10 for the goretailers data source. 

Import the Samples 

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

archive using the deployment tool. 



Before you import the samples, you must restore the databases and create a named user who 

has Select permissions for the database tables. You must also create data source connections 

to the samples databases. 

To use the deployment tool, you must have execute permissions for the Administration secured 

function. 

Steps 

1. Copy the Cognos_Samples.zip file from the crn_location/webcontent/samples/content 

directory to the directory where your deployment archives are saved. 

The default location is crn_location/deployment. The location in which deployment archives 

are saved is set in the configuration tool. For information about changing the location, see 

the configuration tool online help. 


3. On the toolbar, click Deployment. 

4. Click the Import tab. 

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

The New Import wizard appears 

6. In the Deployment archive box, click Cognos_Samples and click Next. 

7. If you want, type a description and screen tip for the deployment specification, select the 

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

8. In the Public folders content list, select the check box for the GO Sales and Retailers 

package. 

9. If you do not want users to access the sample package and its entries, select the check box 

in the Disable after import column. 

This is useful when you want to test the reports before you make them available in the target 

environment. 

10. Click Next. 

11. In the Specify the general options page, click Next. 

The summary information appears. 

Tip: If you want to change information, click Back and follow the instructions. 

12. Click Import Now. 

ReportNet imports the sample package. This may take a few minutes. 

13. When the import is done, click Finish. 

You can now use the sample package to create reports in Report Studio and Query Studio. You 

can also run the sample reports that are available on the Public Folders tab in the portal. 

Remove the Samples from ReportNet 

You can delete the packages on which the samples are based after you finish using the sample 

reports to learn about ReportNet and Framework Manager. This permanently removes the 

samples from the content store. 

Steps 


2. Click the Public Folders tab. 

3. Select the check box for the GO Sales and Retailers sample package. 

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

To use the samples again, you must set up the samples (p. 91). 



Sample Model 

The sample model provided with ReportNet is named gosales_goretailers and refers to the 

samples databases gosl and gort. 

The model is designed for use in Framework Manager and is divided in the following views: 

• a database view 

• a presentation view 

• summary queries 

Database View 

The query subjects in the database view correlate directly with the tables in the gort and gosl 

databases. The database view 

• defines relationships between database query subjects 

• renames objects to reflect their business use 

• modifies the SQL in some query subjects to handle language requirements 

Presentation View 

The presentation view defines model query subjects that are formed from the database query 

subjects in the database view. The model query subjects in the presentation view are organized 

to reflect a logical use based on a business case. For example, product line, product type, and 

product are presented as items in a single subject. 

Because relationships are defined in the database view, there are no explicit relationships 

between any of the model query subjects. 

Model query subjects are the only part of the published package visible to the report author. 

Summary Queries 

The model includes two summary queries that combine detail information into monthly values 

that other query subjects can use. 

Products by month is a query that combines the quantity of products sold into monthly periods. 

Data from this query is compared to data in the Product forecasts model query subject. Product 

forecasts is generated from the relationship between Products by month and Product forecasts. 

Revenue by month is a query that combines the revenue for products, retailers, and sales staff. 

Data from this query is compared to data in the Sales targets model query subject. Sales 

targets, is generated from the relationship between Sales target and Revenue by month. 




Chapter 9: Setting Up an Unattended 

Installation and Configuration 

Set up an unattended installation and configuration to 

• install an identical configuration across several computers on your network 

• automate the installation and configuration process by specifying options and settings for 

users 

Before you set up an unattended installation and configuration, ensure that all the system 

requirements and prerequisites are met and that all third-party products are installed and 

configured. 

To set up an unattended installation and configuration: 

❑ configure a transfer specification file (.ats) to specify installation options 

❑ run the installation tool in silent mode 

❑ use a preconfigured configuration file from another computer 

❑ run the configuration tool in silent mode 

After you complete these tasks, you are ready to use ReportNet for reporting. 

Set Up an Unattended Installation 

Use a transfer specification file (.ats) to copy ReportNet components to your computer without 

being prompted for information. 

By default, each time you install ReportNet components, including Framework Manager, using 

the installation wizard, the options you select are recorded in a transfer specification file. 

Therefore, if you already installed ReportNet or Framework Manager on a sample computer, you 

can use the generated transfer specification file as a template for unattended installations on 

different computers. 

If you do not use the installation wizard to install components, you can use the default transfer 

specification file named response.ats that is available on the CD. You must modify the 

response.ats file for your environment before you can use it for an unattended installation. 

Steps Using a File Generated by a Previous Installation 

1. Use the installation wizard to install ReportNet or Framework Manager on your computer. 

2. Go to crn_location/instlog. 

3. Locate the transfer specification file (.ats) that was generated: 

• If you installed Framework Manager, the file name is 

ts-FRAMEWORK MANAGER-version-yyyymmdd_hhmm.ats. 

• If you installed ReportNet, the file name is 

ts-COGNOS REPORTNET-version-yyyymmdd_hhmm.ats. 

4. Copy the transfer specification file to the computer where you plan to install Framework 

Manager or ReportNet. 

5. On the computer where you plan to install Framework Manager or ReportNet, insert the 

appropriate CD and copy the contents of the Cognos directory to your computer. 


Chapter 9: Setting Up an Unattended Installation and Configuration 

6. Install ReportNet components, including Framework Manager: 

• On Windows, from the Start menu, click Programs, Command Prompt to open a 

Command Prompt window, and then type the following command, where location is 

the directory where you copied filename, the transfer specification file: 

xwsetup -s location\filename.ats 

• On UNIX, type the following command on a single line, where location is where you 

copied filename, the transfer specification file: 

xwsetup -s location\filename.ats 

Any errors that occur are recorded in the installation directory in the following log file: 

• For Framework Manager, the file name is 

tl-FM-version-yyyymmdd-hhmm_summary-error.txt. 

• For ReportNet server components, the file name is 

tl-CRN-version-yyyymmdd-hhmm_summary-error.txt. 

If errors occur before sufficient initialization occurrs, log messages are sent to one of the 

following log files in the Temp directory: 


tl-FM-version-yyyymmdd-hhmm.txt. 

• For ReportNet, the file name is 

tl-CRN-version-yyyymmdd-hhmm.txt. 

After all errors are resolved, you can set up an unattended configuration. 

Steps Using the Response.ats File 

1. On the target computer, insert the CD and copy the contents to your computer. 

2. Go to the win32 directory and open the response.ats file in a text editor. 

Each section in the response.ats file corresponds to a dialog box in the installation wizard. 

3. For the appPath=setting, type the installation location of the program files for ReportNet 

components or Framework Manager. 

Tip: There should be no space on either side of the equal, (=). 

4. For ReportNet, in the section named [Component List], next to each component: 

• To install the component, type 1. 

• To not install the component, type 0. 

Note: You do not select components for Framework Manager. All required files are installed. 

5. For a Windows installation, for the APPFOLDER= property, type the name of the Start 

menu folder that contains your program shortcuts. 

Tip: To ensure that the shortcut folder is visible to all users, type 1 for the VISIBLETOALL= 

property. 

6. For the install information in the [Install Conditions] section: 

• To specify the condition is true, type 1. 

• To specify the condition is false, type 0. 

7. Save the response.ats file to a local directory after you make the necessary changes. 

8. Go to the win32 directory. 

9. At the command prompt type the following command, where location is the directory where 

you copied response.ats: 

• On Windows, type 

xwsetup -s location\response.ats 

• On UNIX, type 

xwsetup -s location/response.ats 

Any errors that occur are recorded in the installation directory in the following log file: 


tl-FM-version-yyyymmdd-hhmm_summary-error.txt. 

• For ReportNet server components, the file name is 

tl-CRN-version-yyyymmdd-hhmm_summary-error.txt. 



If errors occur before sufficient initialization occurrs, log messages are sent to one of the 

following log files in the Temp directory: 


tl-FM-version-yyyymmdd-hhmm.txt. 

• For ReportNet, the file name is 

tl-CRN-version-yyyymmdd-hhmm.txt. 

After all errors are resolved, you can set up an unattended configuration. 

Set Up an Unattended Configuration 

Before you set up an unattended configuration, you must export a configuration from another 

computer that has the same ReportNet components installed. You can then run Cognos 

Configuration in silent mode. 

Ensure that the configuration settings on the local computer are appropriate to use to configure 

another ReportNet computer with the same installed components. For example, if you changed 

the host name portion of the Gateway URI property from local host to an IP address or computer 

name, ensure this setting is appropriate for the new computer’s configuration. 

Steps 

1. In Cognos Configuration, from the File menu, click Export as. 

2. If you want to export the current configuration to a different folder, in the Look in box, locate 

and open the folder. 

3. In the File name box, type a name for the configuration file. 

4. Click Save. 

5. Copy the exported configuration file from the source computer or network location to the 

crn_location/configuration directory on the the computer where you plan to do an 

unattended configuration. 

6. Rename the file to crnstartup.xml. 

7. Go to crn_location/bin. 

8. Type the configuration command: 

• On UNIX, type 

./crconfig.sh -s 

• On Windows, type 

crconfigw.exe -s 

Tip: To view log messages that were generated files that were during an unattended 

configuration, see the crconfig_response.csv file in the crn_location/logs directory. 

Cognos Configuration applies the configuration settings specified in the local copy of 

crnstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts 

ReportNet service or process. 




Chapter 10: Uninstalling Cognos ReportNet 

It is important to use uninstall programs to completely remove all files and modifications to 

system files. 

To uninstall ReportNet, you uninstall server components and Framework Manager. 

Uninstall ReportNet on UNIX 

If you no longer require ReportNet or if you are upgrading, uninstall all ReportNet components. 

Before you uninstall, ensure that you back up any data that you added to the crn_location 

directory or any configuration files that are located in the crn_location/configuration directory. 

Steps 

1. If the console attached to your computer does not support a Java-based graphical user 

interface, determine the process identification (pid) of the ReportNet by typing the following 

command: 

ps -ef | grep process 

2. Stop the ReportNet process: 

• If you run XWindows, start Cognos Configuration, and from the Actions menu, click 

Stop. 

• If you do not run XWindows, type: 

kill -TERM pid 

3. Go to the directory where you installed ReportNet and type 

rm -rf crn_location 

4. Delete all temporary Internet files. 

All files are removed from the crn_location directory. 

Uninstall ReportNet on Windows 

If you no longer require ReportNet or if you are upgrading, uninstall all ReportNet components 

and uninstall the ReportNet service. 

If you installed Framework Manager in the same location as ReportNet, the Framework 

Manager files are removed when you uninstall ReportNet. 

If you installed more than one component in the same location, you cannot choose which 

components to uninstall. You remove all ReportNet server components installed on that 

computer. You must repeat the uninstallation process on each computer that contains 

ReportNet components 

We recommend that you close all programs before you uninstall ReportNet. Otherwise, some 

files may not be removed. 

Steps 

1. From the Start menu, click Programs, Cognos ReportNet, Uninstall Cognos ReportNet. 

The Uninstall wizard appears. 

Tip: Cognos ReportNet is the default name of the Program Folder that is created during 

installation. If you chose another name, go to that folder to find the program. 


Chapter 10: Uninstalling Cognos ReportNet 

2. Follow the instructions to uninstall the components. 

The Cognos_uninst_log.htm file records the activities that the Uninstall wizard performs 

while uninstalling files. 

Tip: To find the log file, look in the Temp directory. 


For more information, see your Web browser documentation. 

Uninstalling does not remove any files that changed since the installation, such as configuration 

and user data files. Your installation location remains on your computer, and you retain these 

files until you delete them using Windows Explorer. 

Uninstall Framework Manager 

If you no longer require Framework Manager or if you are upgrading, uninstall it. 

If you install Framework Manager in the same location as ReportNet, the Framework Manager 

files are uninstalled when you uninstall ReportNet. 

We recommend that you close all programs before you uninstall Framework Manager. 

Otherwise, some files may not be removed. 

Steps 

1. From the Start menu, click Programs, Cognos ReportNet, Uninstall Cognos ReportNet. 

The Uninstall wizard appears. 

Tip: Cognos ReportNet is the default name of the Program Folder that is created during 

installation. If you chose another name, go to that folder to find the program. 

2. Follow the instructions to uninstall. 

The Cognos_uninst_log.htm file records the activities that the Uninstall wizard performs 

while uninstalling files. 

Tip: To find the log file, look in the Temp directory. 


For more information, see your Web browser documentation. 

Uninstalling does not remove any files that changed since the installation, such as configuration 

and user data files. Your installation location remains on your computer, and you retain these 

files until you delete them using Windows Explorer. 


Appendix A: Manually Configuring ReportNet 

The console attached to the UNIX computer on which you are installing ReportNet may not 

support a Java-based graphical user interface. You must 

❑ manually change default configuration settings by editing the crnstartup.xml file, located in 

the crn_location/configuration directory 

❑ manually change language or currency support, or locale mapping by editing the 

crnlocale.xml file, located in the crn_location/configuration directory 

❑ apply the configuration and the locale settings to your computer by running Cognos 

Configuration in silent mode 

For all installations, some configuration tasks are required so that ReportNet works in your 

environment. If you distribute ReportNet components across several computers, the order in 

which you configure and start the computers is important. 

Other configuration tasks are optional and depend on your reporting environment. You can 

change the default behavior of ReportNet by editing the crnstartup.xml file to change property 

values. You can also use sample files that enable ReportNet to use resources that already exist 


Manually Change Default Configuration Settings 

If the console attached to your UNIX computer does not support a Java-based graphical user 

interface, you must edit the crnstartup.xml to configure ReportNet to work in your reporting 

environment. 

Before you edit the crnstartup.xml file, ensure that you 

• make a backup copy 

• create the content store on an available computer in your network (p. 19) 

• review the configuration requirements for your installation type (p. 33) 

If you want ReportNet to use a resource, such as an authentication provider that already exists 

in your environment, you can add a component to your configuration. You do this by copying the 

required XML code from the sample files into the crnstartup.xml file and then edit the values to 

suit your environment. 

Important: By default, the crnstartup.xml file is encoded using UTF-8. When you save the 

crnstartup.xml file, ensure that you change the encoding of your user locale to match the 

encoding used. The encoding of your user locale is set by your environment variables. 

When you edit the crnstartup.xml file, remember that XML is case-sensitive. Case is important 

in all uses of text, including element and attribute labels, elements and values. 

Steps 

1. Go to the crn_location/configuration directory. 

2. Open the crnstartup.xml file in an editor. 

3. Find the configuration setting you want to change by looking at the help and description 

comments that appear before the start tag of the elements. 

4. Change the value of the element to suit your environment. 

Tip: Use the type attribute to help you determine the data type for the configuration 

property. 

5. Repeat steps 3 to 4 until the configuration values are appropriate your environment 

6. Save and close the file 



You should now use a validating XML editor to validate your changes against the rules in the 

crnstartup.xsd file, located in the crn_location/configuration. 

Add a Component to Your Configuration 

The crnstartup.xml file contains configuration settings used by ReportNet and by default 

third-party components.You can change the components that ReportNet uses by copying XML 

elements from sample files into the crnstartup.xml file. You can then edit the configuration 

values to suit your environment. 

For example, to use an Oracle database instead of a Microsoft SQL Server database for the 

content store, you can use the ContentManager_language code.xml sample file to replace the 

default database connection information. 

ReportNet can use only one instance at a time of the following elements: 

• the database for the content store 

• a cryptographic provider 

• a configuration template for the ReportNet service 

You should be familiar the structure of XML files before you start editing them. 

Steps 

1. Go to the crn_location/configuration/samples directory. 

2. Choose a sample file to open in an editor: 

• To use Oracle or DB2 for the content store, open the 

ContentManager_language_code.xml file. 

• To use an authentication provider, open the Authentication_language_code.xml file. 

• To use a third-party cryptographic provider, open the Cryptography_language_code.xml 

file. 

• To send log messages somewhere other than a file, open the 

Logging_language_code.xml file. 

• To use a medium or large template for the amount of resources the ReportNet process 

uses, open the ReportNetService_language_code.xml file. 

3. Copy the elements that you need. 

Tip: Ensure that you copy the code including the start and end tags for the 

element. 

For example, look for the (Begin of) and (End of) comments: 

 

 

... 

 

 


5. Open the crnstartup.xml file in an editor. 

6. Paste the code from the sample file to the crnstartup.xml file and replace the appropriate 

element. 

7. Change the values of these new elements to suit your environment. 

For the element, don’t change the class attribute. You can change the name 

attribute to suit your environment. 

For example, if you use an Oracle database for the content store, change only the name 

attribute to suit your environment. 

 




9. Run Cognos Configuration in silent mode by typing the following command: 


This ensures that the file is valid and that passwords are encrypted. 

Manually Change the Global Settings 

If the console attached to your UNIX computer does not support a Java-based graphical user 

interface, you must manually edit the crnlocale.xml file located in the crn_location/configuration 

directory. 

You change global settings 

• to specify the language used in the user interface when the language in the user’s locale is 

not available 

• to specify the locale used in reports when the user’s locale is not available 

• to add currency or locale support to report data and metadata 

• to add language support to the user interface 

By default, ReportNet ensures that all locales, which may come from different sources and in 

various formats, use a normalized form. That means that all expanded locales conform to a 

language and regional code setting. 

Before you can add language support to the user interface, you must use the ReportNet 

Localization Kit to translate the strings that appear in the ReportNet user interface. You must 

also install the language files on all computers in your distributed installation. For more 

information, contact your Cognos support representative. 

Example 1 

A report is available in Content Manager in two locales, such as en-us (English-United States) 

and fr-fr (French-France), but the user locale is set to fr-ca (French-Canadian). ReportNet uses 

the locale mapping to determine which report the user sees. 

First, ReportNet checks to see if the report is available in Content Manager in the user’s locale. 

If it is not available in the user’s locale, ReportNet maps the user’s locale to a normalized locale 

configured on the Content Locale Mapping tab. Because the user’s locale is fr-ca, it is mapped 

to fr. ReportNet uses the mapped value to see if the report is available in fr. In this case, the 

report is available in en-us and fr-fr, not fr. 

Next, ReportNet maps each of the available reports to a normalized locale. Therefore, en-us 

becomes en and fr-fr becomes fr. 

Because both report and the user locale maps to fr, the user having the user locale fr-ca will see 

the report saved with the locale fr-fr. 

Example 2 

The user’s locale and the report locales all map to the same language. ReportNet chooses 

which locale to use. For example, if a user’s locale is en-ca (English-Canada) and the reports 

are available in en-us (English-United States) and en-gb (English-United Kingdom), ReportNet 

maps each locale to en. The user will see the report in the locale setting that ReportNet 

chooses. 

Example 3 

The report and the user locales do not map to a common language. ReportNet chooses the 

language. In this case, you may want to configure a mapping. For example, if a report is 

available in en-us (English-United States) and fr-fr (French-France), but the user locale is es-es 

(Spanish-Spain), ReportNet chooses the language. 

Steps 

1. On the computer where you installed Content Manager, go to the crn_location/configuration 

directory. 

2. Open the crnlocale.xml file in an editor. 



3. Add or modify the required element and attribute between the appropriate start and end 

tags. 

Type of Support Start Tag End Tag 

Language 

Content Locales 

Currency 

Product Locale 

Mapping 

Content Locale 

Mapping 

 

 

 

 

Fonts 

Tip: To remove support, delete the element. 


Tip: We recommend that use a validating XML editor to validate your changes against the rules 

in the crnstartup.xsd file, located in the crn_location/configuration. 

If you add a currency code that is not supported by Cognos, you must manually add it to the 

i18n_res.xml file in the crn_location/bin/ directory. Copy this file to each ReportNet computer in 

your installation. 

Run Cognos Configuration in Silent Mode 

Run Cognos Configuration in silent mode to apply the configuration settings on your computer if 

the console attached to your UNIX computer does not support a Java-based graphical user 

interface. 

Before you run the configuration tool in silent mode, you should use a validating XML editor to 

validate your changes against the rules in the crnstartup.xsd file, located in the 

crn_location/configuration. 

Steps 

1. Ensure that the crnstartup.xml file in the crn_location/configuration directory on the local 

computer contains the property settings you want to use for your configuration. 

2. Go to crn_location/bin. 

3. Type the following configuration command 


Tip: To view log messages that were generated files that were during an unattended 

configuration, see the crconfig_response.csv file in the crn_location/logs directory. 

Cognos Configuration applies the configuration settings specified in the local copy of 

crnstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts 

ReportNet service or process. 


Appendix B: Troubleshooting 

Use this troubleshooting reference information and solutions as a resource to help you solve 

specific problems you may encounter during or after the installation of ReportNet components. 

Problems are characterized by their symptoms. Each symptom can be traced to one or more 

causes by using specific troubleshooting tools and techniques. After being identified, each 

problem can be fixed by implementing a series of actions. 

When you are troubleshooting, several files can help you: 

• The transfer log file 

This file records the activities that the installation wizard performed while transferring files. 

The transfer log file is located in the crn_location\instlog directory. The file name identifies 

the product name, version, and build number, and includes a time stamp. The following is an 

example of the file name format: 

tl-CRN-8-0-0-0-20021104_0942.txt 

• The transfer summary-error log file 

This file records the components you installed, disk space information, the selections you 

made in the transfer dialogs, and any errors the installation wizard encountered while 

transferring components. The transfer summary-error log file is located in the 

crn_location/instlog directory. The file name identifies the product name, version, and build 

number, and includes a time stamp. The following is an example of the file name format: 

tl-CRN-8-0-0-0-20021106_1122_summary-error.txt 

• The startup configuration file 

This file records your configuration choices each time you save your property settings. If you 

are unable to save your configuration, or are having problems you can revert to a previously 

saved configuration file. The backup configuration files are located in the 

crn_location/configuration directory. The following is an example of the file name format: 

crnstartup_200211231540.xml 

• The crnlocale.xml file 

This file records the configuration choices you make in Cognos Configuration for product 

and content locales, locale mapping, and currency support. If you experience problems with 

language support in the user interface or in reports, use these files to track your changes. 

The backup configuration files are located in the crn_location/configuration directory. The 

following is an example of the file name format: 

crnlocale_200211231540.xml 

• The default ReportNet log file named crnserver.log file, or other log files that you configure 

to receive log messages from the log server 

This file records information after you start the ReportNet service. Some log messages 

indicate problems. Most messages provide information only, but others can help you to 

diagnose problems in your run-time environment. 

• The cognos_uninst_log.htm file 

This file records the activities that the Uninstall wizard performed while uninstalling files. 

The log file is located in the Temp directory. You can use the log file to troubleshoot 

problems related to uninstalling ReportNet components. 

• The crconfig_response.csv file 

This file records the activities that Cognos Configuration performed while running in silent 

mode. This log file is located in the crn_location/logs directory. 

Another valuable troubleshooting tool is the Knowledge Base, which is available on the Cognos 

support site (http://suppport.cognos.com). The Knowledge Base is a database of problems and 

solutions for all Cognos products. 



When you cannot resolve a problem, the final resource is your Cognos technical support 

representative. To analyze a problem, your technical support representative requires information 

about the situation and the symptoms that you are experiencing. To help isolate the problem, 

collect the necessary data before you contact your representative. 

Unable to Start ReportNet 

You may not be able to start the ReportNet service or process if one of the default ports is used 

by another process. 

Tip: To view the current network TCP/IP network connections, use the netstat command. 

Use Cognos Configuration to change the default port that ReportNet uses. 


Dispatcher URI property. Because the change affects all the URIs that are based on the local 

dispatcher, you must change the URIs of all local components. By default, local components 

contain localhost in the URI. 






Steps to Change the Default Port 


2. In the Explorer window, click the appropriate group or component: 





contain a local host. 


6. From the Action menu, click Start. 

Current Configuration Settings Are Not Applied to Your 

Computer 

You change default property values or add a resource to your installation in Cognos 

Configuration. After saving the current configuration, you may not see the changes or be able to 

use the resource in the run-time environment. 

To apply the new settings to your computer, you must restart the ReportNet service. 

Steps to Restart the ReportNet Service 

1. Open Cognos Configuration. 

2. From the Actions menu, click the appropriate command: 

• If the ReportNet service is currently running, click Restart. 

• If the ReportNet service is stopped, click Start. 



Unable to Start Cognos Configuration Because the 

Configuration Data is Locked by Another Instance of 

Cognos Configuration 

You may get an error message that the configuration data is locked by another instance of 

Cognos Configuration although there is no other instance running. 

When you start Cognos Configuration, it checks to see if the crnstartup.lock file exists in 

crn_location/configuration. The file may exist if a previous instance did not shut down properly or 

if another instance of Cognos Configuration is running. 

If another instance of Cognos Configuration is running, you should exit that instance. Otherwise, 

any changes you make to the local configuration may result in errors. If no other instance of 

Cognos Configuration is running, delete the crnstartup.lock file in crn_location/configuration. 

Unable to Save Your Configuration 

You may be unable to save your configuration because you are missing a resource. For 

example, you delete a resource such as the Cognos namespace, a cryptographic provider, or 

the content store. You can replace the default database type for the content store with Oracle or 

DB2. You cannot replace the Cognos namespace. 

Steps to Recreate the Cognos Namespace 


2. In the Explorer window, under Security, right-click Authentication and then click New 

resource, Namespace. 


4. In the Type box, click Cognos, and then click OK. 

The Cognos namespace appears in the Explorer window. 


Error Trying to Encrypt Information When Saving Your 


When you save your configuration using the configuration tool, you may see an error message 

that the cryptographic information cannot be encrypted. An error occurred when requesting a 

certificate from the Certificate Authority. 

Before you can encrypt your configuration settings, the computer where Content Manager is 

installed must be configured and running. On UNIX, ensure that you copied the appropriate JAR 

files to the installation location of your Java Runtime Environment. 

Fonts Do Not Appear Properly in the Configuration Tool 

User Interface 

You may notice that some characters in the user interface of the configuration tool do not appear 

properly. Because the configuration tool is a Java application, it needs a properly configured 

Java environment to find the fonts required for the user interface. 

To resolve this problem, see your Java documentation, or change the font in the user interface. 



Steps to Change the Font that the Configuration Tool Uses in the User Interface 


2. From the View menu, click Font. 

The text of the Font command and in the Font dialog box is in English. 

Tip: The View menu is the second menu from the left. Font is the second command in the 

View menu. 

3. In the Name box, click the font that you want to apply to use. 

Tip: The Name box is the first box from the left of the dialog box. 

4. In the Style box, click the format that you want to use. 

Tip: The Style box is the second box from the left of the dialog box. 

5. In the Size box, click the font size you want to use. 

6. Click OK. 

DB2 Returns SQL1224N Error When Connecting from AIX 

If your content store is a DB2 database and you receive an SQL1224N error on AIX, check the 

db2diag.log file for additional information about the error. If the error includes reason code 18, 

you may need to change the DB2 configuration to accept more connections. For more 

information, see the IBM DB2 support pages for the error SQL1224N. 

Cognos BI Server Not Available When Opening the Portal 

After you configure ReportNet components and start the ReportNet service, when you open the 

ReportNet Web portal, the following error message may appear: 

The Cognos BI server is not available. 

SoapSocketException: Connection refused 

Check the ReportNet server log file for more information. By default, the crnserver.log file is 

located in the crn_location/logs directory. If you configured another destination for log 

messages, check the appropriate file or database. 

Content Manager may not be able to connect to the content store if the content store is not 

configured properly. This may occur if 

• the content store uses an unsupported character encoding 

• the content store uses a database collation sequence that is case-sensitive 

• the configuration settings you specified in Cognos Configuration are not valid 

Unsupported Character Encoding 

If the following messages appear in the log file, the database you created for the content store 

does not use a supported character encoding: 

For Oracle: 

CM-CFG-5063 A Content Manager configuration error was detected while connecting to the 

content store. 

CM-SYS-5121 Content Manager cannot start because the database character set is not 

supported. 

CM-SYS-5126 The content store database server uses the character set US7ASCII. 

CM-SYS-5125 The content store database client uses the character set US7ASCII. 

For DB2 UDB: 



CM-SYS-5121 Content Manager cannot start because the database character set is not 

supported. 

CM-SYS-5124 The content store database server uses the code page 1252. 



For Content Manager to connect to the content store, the content store must use the appropriate 

character encoding. 

Database 

Oracle 8.1.7 

Oracle 9i 

DB2 UDB 

Mircrosoft SQL Server 

Character encoding 

UTF8 

UTF16 

AL32UTF8 

AL32UTF16 

Codeset UTF-8 

UTF8 

UTF16 

To resolve this problem, you must recreate the content store database using the correct 

character encoding, or convert the character encoding. For more information, see the database 

vendor documentation. 

Case-sensitive Collation Sequence 

If the following messages appear in the log file, the database you created for the content store 

uses a database collation sequence that is case-sensitive: 



CM-SYS-5122 The content store database has a default collation that is case-sensitive. 

Content Manager requires a content store that has a case-insensitive collation. 

CM-SYS-5123 The content store database server uses the collation Latin1_General_CS_AS. 

CM-SYS-5007 Content Manager build @cm_build_version@ failed to start! Review the Content 

Manager log files and then contact your system administrator or customer support. 

To resolve this problem, you must recreate the content store database using a database 

collation sequence that is context-insensitive. For more information, see the database vendor 


Invalid Configuration Settings for the Content Store 

If the following or similar messages appear in the log file, you did not configure the content store 

correctly in Cognos Configuration. 

For Microsoft SQL Server: 



CM-CFG-5036 Content Manager failed to connect to the content store. The connection 

string is "jdbc:JSQLConnect://localhost:1433/cm". 

Failed Logon:com.jnetdirect.jsql.x: Cannot open database requested in login 'cm'. Login 

fails. url:jdbc:JSQLConnect://localhost:1433/cm 

For DB2: 



CM-SYS-5003 Content Manager is unable to access the content store database. Verify your 

database connection parameters and then contact your database administrator. 

[IBM][CLI Driver] SQL1013N The database alias name or database name "CM123" could not be 

found. 

For Oracle: 



CM-CFG-5036 Content Manager failed to connect to the content store. The connection 

string is "jdbc:oracle:thin:@localhost:1521:pb1" 

ORA-01017: invalid username/password; logon denied 

To resolve this problem, check the configuration settings you specified in Cognos Configuration 

for the content store. 



Steps to Reconfigure Oracle and DB2 Databases 


2. In the Explorer window, under Data Access, Content Manager, right-click Content Store 

and click Delete. 

This deletes the default resource. You can configure ReportNet to access only one content 

store. 

3. Right-click Content Manager, and then click New resource, Database. 


5. In the Type box, select the type of database and click OK. 

6. In the Properties window: 

• If you are use a DB2 database, for the Database name property, type the database 

alias. 

• If you use an Oracle database, type the appropriate values for the Database server 

and port number and Service name properties. 




click OK. 



Steps to Reconfigure Microsoft SQL Server Databases 


2. In the Explorer window, under Data Access, Content Manager, click Content Store. 

By default, ReportNet uses properties for a Microsoft SQL Server database. 

3. If necessary, in the Properties window, change the default value for the Database server 

and port number. 

4. For the Database name property, type the name of the database you previously created in 

Microsoft SQL Server to use as the content store. 



6. In the Enter the user ID and password dialog box, type the appropriate values and then 

click OK. 



Web Server Error When Trying to Browse Images 

When you want to insert an image into a report and you try to browse to the location (URL) 

where the image is located, an error message like the one below appears: 

Web server error: 

501 Not Implemented 

To browse images on a Web server, you must enable Web-based Distributed Authoring and 

Versioning (WebDAV) on your Web server. 

Note: iPlanet Web server does not support WebDAV. 

Steps to Enable WebDav 

1. If you are using an Apache Web server, configure WebDAV for your server. 

For more information, see the Apache documentation. 



2. If you are using Microsoft Internet Information Services (IIS), enable the Read and Directory 

Browsing properties for the URL you want to access: 

• Open the Control Panel and double-click Internet Services Manager. 

• Right-click the directory that points to the folder containing the image you want to insert 

and click Properties. 

If no directory exists for the folder, create one and point it to the folder. 

• In the Virtual Directory or Directory tab, select the Read and Directory Browsing 

check boxes and click OK. 

3. To verify that WebDAV is configured correctly, use Internet Explorer as a WebDAV client: 

• In Internet Explorer, from the File menu, click Open. 

• In the Open box, type the URL containing the images you want to browse. 

• Select the Open as a Web Folder check box. 

• Click OK. 

If the folder opens successfully, WebDAV is configured correctly. 

Font on UNIX Not Found When Starting Cognos 


When you start Cognos Configuration, the following error message may appear: 

Font specified in font.properties not found... 

This is a common problem on UNIX. It means that the Java Virtual Machine (JVM) is trying to 

use one or more fonts that are not installed on your computer. However, the JVM should use the 

system default, and Cognos Configuration should start and run normally. 

To avoid these errors, add the missing fonts to your Java Runtime Environment by editing the 

font.properties files. Several font.properties files, which contain standard font environment 

information, are installed with your Java SDK. You can find these files in the JRE_location/lib 

directory. 

For more information, see the Java documentation. 

Entries and Folders in the Cognos Web Portal Sorted 

Incorrectly 

If you change the locale settings for the ReportNet product and content, you may expect the 

order of the entries or folders in the Cognos Web portal to follow the encoding rules for the 

language. However, the entries are sorted based on the default database collation you set when 

you created the content store database. 

To view entries in the correct order, you must set the database collation for the content store to 

the sort order that you want to use. 

For more information, see the database vendor documentation. 



DPR-ERR-2022 and DPR-ERR-2058 Errors Appear in Web 

Browser When Starting the Web Portal 

After you start the services in Cognos Configuration and then try to open the portal, one of the 

following or similar messages may appear: 

DPR-ERR-2022 No response generated. This may be due to an incorrect configuration, a 

damaged installation, or the dispatcher not having finished initializing. 

DPR-ERR-2058 The dispatcher encountered an error while servicing a request. XTS handler 

must be initialized before being invoked. 

DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is 

still initializing. 

This can occur if you try to open the portal before the ReportNet services are initialized. 

You can avoid these error messages. After you start the services in Cognos Configuration and 

the configuration tool shows that the services are running, wait a few minutes for all services to 

start before you open the portal. 

Report Link in Email Notification Does Not Work 

If a report link in an email notification does not work, the Gateway URI may not be configured 

correctly. 

You must change the host name portion of the Gateway URI from localhost to either the IP 

address of the computer or the computer name. If the URL in the email contains localhost, 

remote users cannot open the report. 

Unable to Uninstall Another Version of ReportNet Service 

on Windows 

You install ReportNet, but another version of the ReportNet service continues to run. 

You can install more than one instance of ReportNet in different locations on the same 

computer. If the instances use the same ports, the Installation wizard may not upgrade the 

service correctly. Cognos Configuration upgrades to the most recently configured service for 

ReportNet. You must manually remove the service. 

To see if the correct ReportNet service is running, check the version number in the About 

window in Cognos Configuration. 

Steps 


2. From the Action menu, click Stop. 

3. Open a Command Prompt window. 

4. Go to the crn_location/bin directory. 

5. Uninstall the service: 

• If you used the default name for the service, type 

cogbootstrapservice -u 

• If you specified another name, type 

cogbootstrapservice -u -name="crn_service_name" 

6. Close the Command Prompt window. 

7. Restart Cognos Configuration to upgrade to the correct service. 



Database Connectivity Errors When Running Reports 

You receive a database connectivity error (for example, Oracle service name could not be 

resolved) when you run a report. 

This may occur if the ReportNet server computer is not configured for connectivity with the 

query database computer. 

In a distributed environment, requests can be sent to any ReportNet server computer. You must 

install database API software on every ReportNet server and configure the servers identically, to 

access all defined data sources. 

Unable to Exit a Tab Sequence When Using 

Keyboard-Only Navigation in Cognos Configuration 

If you use the Tab key to navigate in Cognos Configuration, you may experience problems 

exiting a tab sequence. For example, in the Properties window, you can press the Tab key to 

move from one property to another. However, because Cognos Configuration is a Java 

application, when you want to close the Properties window, you must press Ctrl+Tab. 

PDF Report Does Not Print But Print Status Shows 

Succeeded 

You chose to Print the Report in PDF Format on a network printer using a Windows installation 

of ReportNet, but it did not print. 

When you start the ReportNet service using Cognos Configuration, the account under which 

ReporNet runs, usually the local system account, may not have access to network resources. If 

you use a network printer, you must either specify an account that has access to the printer or 

configure the ReportNet service so that it can access the printer. 

PDF Outputs Too Large 

Your chose to run PDF reports, but they are too large. 

By default, all fonts are embedded to ensure they display properly. More specifically, the 

minimum number of glyphs required from a given font are embedded. This may result in 

increased network resource consumption due to the size of the font information. 

To limit the number of embedded fonts to a specific list, you must manually edit and then rename 

a configuration file. 

If a font you have chosen not to embed does not display properly, you must either change the 

configuration to embed the font, or use a different font. 

Steps 


2. Open the PdfDefaults.cps.noEmbed file in an editor. 

3. If you want to add fonts to the current list of fonts to embed, which includes the Arial, Times 

New Roman, Courier New font families, add the font name to the list beside the 

dfltFontEmbeded property. 

For example, dfltFontEmbeded = "Arial;Times New Roman;Courier New;NewFont" 

Tip: Ensure each font family is separated by a semi-colon (;). 

4. Change the default setting for the dfltUseEmbeded property, if required: 

• To embed all fonts, change the value to "0". 

• To embed only the fonts listed for the dfltFontEmbeded property, use the default value, 

"1". 



5. If you want to embed licensed fonts, add the font name to the list beside the 

dfltFontEmbededLicensed property. 

The license for some fonts prohibits embedding. Ensure you have permission from the 

vendor to embed licensed fonts. 


7. Rename the file to PdfDefaults.cps. 


Appendix C: Database Schema for Log 

Messages 

If you configure ReportNet to send log messages to a database, the database, including the 

tables and the fields in each table, is automatically created when you start the ReportNet 

services. 

Table Definitions 

The following database table definitions are created in the log database. 

Table Name 

COGIPF_ACTION 

COGIPF_USERLOGON 

COGIPF_NATIVEQUERY 

COGIPF_PARAMETER 

COGIPF_RUNJOB 

COGIPF_RUNJOBSTEP 

COGIPF_RUNREPORT 

COGIPF_VIEWREPORT 

COGIPF_SYSPROPS 

Description 

Stores information about 

operations performed on objects 

Stores user logon (including log 

off) information 

Stores query information that 

ReportNet makes to third-party 

components 

Stores parameter information 

logged by a component 

Stores information about job 

executions 

Stores information about job step 

executions 

Stores information about report 

executions 

Stores information about report 

view requests 

Stores version information about 

the schema for upgrade purposes 

Logging Conditions 

Messages are recorded in a table in the log database under certain conditions. These 

conditions depend on the logging level that you configure in the Web portal and the action that a 

user performs. For information about logging levels, see the Administration and Security Guide. 


Appendix C: Database Schema for Log Messages 

The following table describes the conditions under which log messages are recorded in a 

database table. 

Table 

Logging 

Level 

Description 

ACTION 3 Operations performed on objects 

USERLOGON 2 • Logon 

• Log off 

• Logon expires (passport 

expires) 

NATIVEQUERY 5 Query information that ReportNet 

makes to third-party components 

PARAMETER 3 Parameter information logged by a 

component 

RUNJOB 3 Information about job executions 

RUNJOBSTEP 3 Information about job step 

executions 

RUNREPORT 3 Information about report executions 

VIEWREPORT 3 Information about report view 

requests 

Note: When a user logs on to ReportNet, a session ID is assigned and recorded in all log 

messages. You can use the session ID to identify all actions performed by a user. 


Appendix D: Database Clean Up Scripts 

You can run an SQL script to delete all the tables in one of the following databases that 

ReportNet uses: 

• content store for ReportNet application data 

• log database for log messages 

• delivery database for report notifications 

Delete Tables from Databases Used by ReportNet 

If you want to remove all existing ReportNet related information such as applications or log 

entries, and start over, you can run a special SQL script. 

When you delete a table, its structural definition and data are deleted permanently from the 

database. 

Ensure that you stop the ReportNet service before you run the scripts. When you restart the 

ReportNet service, the required database tables are created automatically in the location 

determined by your configuration settings. 

Steps 

1. On the computer where Content Manager is located, stop the ReportNet service. 

2. Go to the appropriate directory: 

• To delete tables from the log database, go to the 

crn_location\configuraton\schemas\logging 

• To delete tables from the content store database, go to the 

crn_location\configuraton\schemas\content 

• To delete tables from the delivery database, go to the 

crn_location\configuraton\schemas\delivery 

3. Go to the appropriate database directory. 

4. Depending on the database and database type, run one of the following scripts in the 

appropriate database tool to delete the tables. 

Database Database Type Script Name 

Content DB2 dbClean_db2.sql 

Microsoft SQL 

Server 

Oracle 

dbClean_mssqlserver.sql 

dbClean_oracle.sql 

Delivery DB2 NC_DROP_DB2.sql 

Microsoft SQL 

Server 

Oracle 

NC_DROP_MS.sql 

NC_DROP_ORA 

Logging DB2 LS_dbClean_db2.sql 


Appendix D: Database Clean Up Scripts 

Database Database Type Script Name 

Microsoft SQL 

Server 

Oracle 

LS_dbClean_mssql.sql 

LS_dbClean_oracle.sql 

5. Start the ReportNet service. 


Glossary 

anonymous access 

A method of accessing resources in which users are not authenticated. 

authentication 

The process of verifying the identity of users when they log on. Authentication is usually done by 

comparing a user name and password to those in an authorized list in the authentication 

provider. Users must be authenticated before they can be authorized to use any secured 

resources. 

certificate 

A document that identifies someone or something by name and by a reference to a certification 

authority. In ReportNet, each computer in a distributed installation uses a different certificate. 

Certificates are used for encryption and decryption. 

certificate authority (CA) 

The component of ReportNet that issues certificates (identification) to each computer on which 

ReportNet components are installed. You can also use a third-party certificate authority. 

common gateway interface (CGI) 

A standard that describes how Web servers should access other programs in order to create a 

document that will appear in a Web browser. For example, Web servers often use CGI programs 

to process forms. 

content locale 

The code or setting that specifies what language and regional preferences to use for the data 

that appears in a report. 


The ReportNet service that manages the storage of reporting applications, including 

application-specific security, configuration data, models, reports, and report output. Content 

Manager is needed to publish models, retrieve or store report specifications, manage 

scheduling information, and manage the Cognos namespace. 

content store 

The database that contains all data that ReportNet needs to operate, such as 

• report specifications, published models, and the packages that contain them 

• connection information for data sources 

• information about the external namespace, and the Cognos namespace itself 

• information about scheduling and bursting reports 

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

The ReportNet service that uses the content store is named Content Manager. 

credentials 

Information stored about the identity of a ReportNet user, usually a user name and password. 

You can assign your credentials to someone else so that they can use resources that you are 

authorized to use. 


Glossary 

Credentials are created for the components of ReportNet. If a user schedules or programs an 

action, then credentials must be stored in the content store. 

data source connection 

The named information that defines the type of the data source, its physical location, and any 

signon requirements. A data source can have more than one connection. 

data source 

A named set of connections to physical databases. Framework Manager uses the name of the 

data source for models. The ReportNet server uses the data source connections to access the 

physical databases. 

deployment archive 

A file used for deployment. A deployment archive contains the data from the content store that is 

being moved. 

gateway 

An extension of a Web server program that transfers information from the Web server to another 

server. Gateways are often CGI programs, but may follow other standards such as ISAPI and 

NSAPI. 

glyphs 

An image of a character in a font. 

Letters are glyphs, but in most cases, the term is used in discussions of non-alphabetic writing 

systems. 

HTTPS 

A secure version of HTTP that incorporates secure sockets layer (SSL) security. HTTPS is 

designed to transmit individual messages securely. The URL-accessed method is https://. The 

default HTTPS port number is 443. This default number is assigned by the Internet Assigned 

Numbers Authority. 

Cognos products use HTTPS and SSL to encrypt and transmit passwords securely over the 

Internet. 

job 

A group of reports and other jobs in ReportNet that you run and schedule as a batch. 

job step 

The smallest part of a job that can be run separately. Usually, a job step is a report. A job step 

can also be another job. 

locale 

A code that is used to set 

• the language or dialect used for browsers, report text, and so on 

• the regional preferences, such as formats for time, date, money, money expressions, and 

time of day 

In ReportNet, you can specify a locale for the product interface (product locale) and for the data 

in the report (content locale). A locale is also stored to record what locale an author used to 

create a report specification or a Framework Manager project. 

namespace 

In security, a collection of user accounts and user groups from an authentication provider. 

In XML, namespaces uniquely identify element types and attributes. An XML namespace is 

defined by a URI (Uniform Resource Identifier) whose purpose is to name the namespace, not 

necessarily to identify a location from which to obtain information. 


Glossary 

In Framework Manager, namespaces uniquely identify query items, query subjects and so on. 

You import different databases into separate namespaces to avoid duplicate names. 

passport 

Information about the authentication of a user. ReportNet creates a passport each time a user 

logs on. The passport is retained until the session ends, either when the user logs off, or after a 

specified period of inactivity. 

A passport is a reference to a set of credentials maintained on the ReportNet server, not the 

credentials themselves. 

product locale 

The code or setting that specifies what language and regional settings to use for parts of the 

product interface, such as menu commands. 

response file 

An ASCII file that contains the setup data that is needed to automate an installation. In Cognos 

ReportNet, the response file automates only the process of copying files with the default 

configuration. 

role 

A special group that users can choose when they log on to change what groups they are 

authenticated as members of, so that they change what data they have authorization for. 

security provider 

A service that authenticates and defines users and the groups of which they are members. 


Glossary 


Index 

A 

adding 

resources, 103 

AIX 

error connecting to DB2 databases, 110 

anonymous access 

definition, 121 

disabling, 41 

application layers 


application server, alternative 

configuring ReportNet for, 78 

applications.xml 

managing for Cognos Portal Services, 61 

authentication 


authentication method 

specifying for Cognos Portal Services, 60 

authentication provider 

SAP server, 43 

authentication providers 

using, 41 

authorization 

configuring for SAP BW, 73 

single signon for SAP BW and ReportNet, 44 

C 

CA, See certificate authority 

certificate authority, 87 


certificate authority (CA) service 

configuring, 87 

certificate signing requests (CSR), 87 

certificates 


CGI, See common gateway interface 

changing 

default configuration settings, 40, 68 

JVM, 77 

character encoding 

unsupported, 110 

Cognos Configuration, 77 

font not found error, 113 

invalid settings, 110 

problems with keyboard navigation, 115 

running in unattended mode, 99 

starting, 67 

unable to see fonts correctly, 109 

unable to start, 109 

Cognos Connection 

components, 11 

Cognos Portal Services, 60 

managing the applications.xml file, 61 

specifying authentication method, 60 

Cognos Portal Servicse 

specifying Web content location, 60 

Cognos samples, 91 

collation sequence 

specifying sort order, 113 

collation sequences 

case-sensitive, 110 

common gateway interface 


replacing, 49 

common symmetric key 

in cryptographic provider, 46, 71 

communications 

distributed components 

communicating, 39 

components 

Cognos Connection, 11 

Framework Manager, 11 

gateways, 22 

installing, 12 

Query Studio, 11 

Report Studio, 11 

ReportNet, 11, 12 

third-party, 11 

configuration, 103 

adding resources, 103 

Content Manager, 14 

data locked, 109 

error when encrypting information, 109 

gateway URI for email notification, 114 

running, 106 

settings, 19 

applying, 108 

testing, 36 

unable to save, 109 

configuration files 

crnlocale.xml, 105 

crnstartup.xml, 103 

exporting, 99 

configuration settings, 40, 68 

configuration tools, 97 

configuring 

certificate authority (CA) service, 87 

Cognos Portal Services, 60 

cryptographic information, 54, 73 

Framework Manager, 15, 67-68 

iPlanet Web servers, 73 

JDBC drivers, 23 

mail server, 35, 39 

ReportNet, 33 

ReportNet for distributed installations, 37 

ReportNet for WebLogic, 81, 85 

ReportNet for WebSphere, 78, 81 

ReportNet service, 54 

required tasks, 33 

SAP BW authorization, 73 

SSL protocols, 47, 69 

temporary file location, 49, 71 

transfer specification files (.ats), 97 

Web servers, 34, 38 


Index 

configuring Framework Manager 

distributed installations, 67 

connectivity 

errors, 115 

content locales 




default settings, 26 


installation options, 14 

content store 

creating, 17, 19, 27 

creating DB2, 21, 29 

creating Microsoft SQL Server, 19, 27 

creating Oracle, 20, 28 


invalid settings, 110 

setting up database clients, 23 

setting up JDBC drivers, 17, 23, 30 

copying 

ReportNet components, 97 

copyright, 2 

creating 

content store, 17, 19, 27 

DB2 content store, 21, 29 

NLS_LANG environment variables, 30 

credentials 


crnlocale.xml, 105 

crnstartup.xml, 103, 106 

cryptographic information 

configuring, 54, 73 

cryptographic keys 

setup for alternative application server, 86 

cryptographic provider, 54, 73 

D 

data 


locked by Cognos Configuration, 109 

data source connections 

creating for Cognos samples, 92 


setting 

data sources 


database 

connectivity errors, 115 

database clients 

setting up, 23 

database connection strings 

IBM DB2, 35 

Microsoft SQL Server, 35, 112 

Oracle, 35 

database connections, See data source connections 

database connectivity 

requirements, 25 

requirements for content store, 18, 26 

database schemas 

log databases, 117 

databases 


schema for log messages, 117 

tables for log messages, 117 

DB2 

creating content store, 21, 29 

DB2 (cont'd) 

database connectivity, 18, 26 

environment variables, 21, 29 

error connecting from AIX, 110 

DB2 databases 


default configuration settings 

changing, 40, 68 


configuration, 40, 68 


gateways, 26 

log server ports, 26 

ReportNet on Windows, 26 

ReportNet ports, 19, 64 

Tomcat, 19 

URIs, 19, 64 

deleting 


demonstration environment, 67 

demonstration environments, 33 

deployment archives 


digital signatures 


disabling 

anonymous access, 41 

disk space 


dispatchers, 26 

removal, 86 

distributed installations 

configuring Framework Manager, 67 

configuring ReportNet, 37 

scenarios, 12 

document 

version, 2 

DPR-ERR-2022 error, 114 

DPR-ERR-2058 err, 114 

E 

email 

notification doesn’t work, 114 

enabling 

SSL for WebLogic, 85 

SSL for WebSphere, 80 

enabling and disabling, 53 

encryption 

configuration errors, 109 

Entrust cryptographic provider, 54, 73 

environment variables 

DB2, 21, 29 

Oracle, 20, 28 

environments 

supported, 18, 26, 64 

supported operating systems, 18 

exporting 

configuration files, 99 

F 

files 

using a previous installation version, 97 

using response.ats, 98 

fonts 

not found error when starting Cognos Configuration, 113 

unable to see correctly in configuration tool, 109 


Index 



configuring, 15, 67-68 


sample models, 95 

system requirements, 63 

testing, 75 

uninstalling, 102 

upgrading, 102 

G 

gateway 

configuring the URI, 114 

gateways 




generating 

keys, 87 

global configurations 

setting, 54 

glyphs 


Great Outdoors, See Cognos samples 

H 

HTTPs 


I 

IBM DB2 

creating connection strings, 35 

images 

browsing errors, 112 

Web server errors, 112 

installation 

checklist, 17 

failure to update, 114 

Framework Manager, 63, 64 

ReportNet, 11 

ReportNet on UNIX, 17, 19, 22 

ReportNet on Windows, 25, 30 

testing, 36 

installation files 

transfer specification file (.ats), 97 

installation options 



installation tools 

running, 97 

integrating 

third-party components, 11 

invalid settings 


content store, 110 

iPlanet Web servers 


J 

Java Archive files (JAR), 24 

updating in UNIX, 24 

Java Runtime Environment (JRE), 24 

updating, 17 

Java Virtual Machine (JVM) 

changing, 77 

Java Virtual Machine, See JVM 

java.security 

updating in UNIX, 24 

JDBC 

database connectivity for content store, 18, 26 



setting up DB2 databases, 23, 31, 51 

setting up Oracle databases, 23, 31, 51 

job steps 


jobs 


K 

keyboard 

navigation problems, 115 

keys 

generating, 87 

L 

load balance 

enabling and disabling services, 53 

load-balancing 

setting, 13 

locales 


log databases 

logging levels, 117 

schema, 117 

log messages 

conditions, 117 


tables for databases, 117 

log server 

default settings for port, 26 

default settings for ports, 26 

messages, 49, 72 

logging levels 


M 

mail server 


memory 


messages 

log server, 49, 72 

Microsoft IIS Web servers, 15 

Microsoft SQL Server 

creating connection strings, 35, 112 


Microsoft SQL server 


models 

modifying for samples, 93 

samples, 95 

modifying 

response.ats file, 97 

sample models, 93 


Index 

N 

namespaces 


recreating, 109 

NLS_LANG environment variables 

creating, 30 

O 

Oracle 

creating connections strings, 35 



environment variables, 20, 28 

service name error, 115 

Oracle databases 


P 

passports 


PDF report 

does not print, 115 

portal 

errors in starting, 114 

ports 

default settings for ReportNet, 19, 64 

printing a PDF report, 115 

product 

version, 2 

product locales 


proof of concept, 33, 67 

properties 

temporary file location, 49, 71 

Q 

Query Studio 


R 

replacing 

common gateway interface, 49 

report server 

configuration requirements, 14 

configuring database connectivity, 115 

report servers 


Report Studio 


image browsing errors, 112 

Web server errors, 112 

ReportNet 




configuring to use on alternative server, 78 


default settings for UNIX, 17, 19 

installation, 11 


installing on Windows, 25 

report servers, 22 

restarting services, 108 

server not available, 110 

ReportNet (cont'd) 

service fails to update, 114 

system requirements on UNIX, 17 

system requirements on Windows, 25 

troubleshooting installations, 107 

uninstalling on UNIX, 101 

uninstalling on Windows, 101 

uninstalling service, 101 

unsupported characters, 110 

upgrading on UNIX, 101 

upgrading on Windows, 101 

ReportNet components 

copying, 97 

ReportNet gateways 


ReportNet on Windows 


ReportNet service 


reports 

Oracle service name error, 115 

PDF report does not print, 115 

remote users unable to open, 114 

required tasks 


requirements 

database connectivity for content store, 18, 26 

for SAP BW on Windows, 63 

SAP BW on UNIX, 18 

resources 

adding, 103 

response files 


response.ats, 97 

using, 98 

response.ats 

modifying, 97 

roles 


running 

Apache Jakarta Project Connector, 49 

configuration tools, 97 

installation tools, 97 

Microsoft Internet Application Programming Interface, 49 

S 

samples (Cognos) 

deleting, 94 

models, 95 


SAP 

configuring authentication provider, 43 

SAP BW 

authorization settings for ReportNet administrators, 44 

authorization settings for ReportNet users, 44 

configuring authorization, 73 

enabling single signon with ReportNet, 44 

requirements for UNIX, 18 

requirements for Windows, 63 

Schedule Management tool 

PDF report does not print, 115 

schemas 

database for log messages, 117 

SDK, See software development kit 

Secure Sockets Layer, See SSL 

security providers 



Index 

server administration 

logging levels, 117 

services, 53 

enabling and disabling, 53 

failure to update, 114 

uninstalling, 101 

setting 

communication, 39 

data source connections 

global configurations, 54 

setting up 


samples, 91 

settings 

Web browsers, 25 

silent configurations, See unattended configurations 

silent installations, See unattended installations 

silent mode, See unattended mode 

single signon 

for SAP BW and ReportNet, 44 

software development kit 


sorting 

incorrect sort order in Cognos Connections, 113 

SQL Server databases 


SQL Server, See Microsoft SQL Server 

SSL 

enabling for WebLogic, 85 

enabling for WebSphere, 80 

SSL protocols 


starting 


ReportNet service, 108 

supported environments, 18, 26 

system requirements 


ReportNet on UNIX, 17 


T 

Tab key 

problems in Cognos Configuration, 115 

tables 

database for log messages, 117 

temporary file location 


properties, 49, 71 

testing 

configuration, 36, 75 


installation, 36, 75 

Tomcat 

default settings, 19, 26 

transfer specification files (.ats) 


troubleshooting, 107 

ReportNet service does not update, 114 

U 

UDB, See DB2 

unable to print a PDF report, 115 

unattended configuration, 106 

setting up, 97, 99 

unattended configurations, 97 

unattended installation 


unattended installations, 97 

response files, 98 


transfer specification files, 97 

unattended mode, 97 

running Cognos Configuration, 99 

uninstalling 




UNIX 

font not found error, 113 

installing ReportNet, 17 


uninstalling ReportNet, 101 

upgrading ReportNet, 101 

updating 

JAR, 24 

java.security in UNIX, 24 

JRE in UNIX, 24 

upgrading 




ReportNet service does not update, 114 

URI, 13 


URIs 


using 

authentication providers, 41 

preconfigured configuration files, 97 

V 

version 

product, 2 

W 

web browser 

errors in starting the web portal, 114 

Web browser settings, 25 

Web content 

specifying location for Cognos Portal Services, 60 

Web servers, 15 


errors when browsing images, 112 

Microsoft IIS, 15 

WebLogic 

configuring ReportNet for, 81, 85 

enabling SSL, 85 

WebSphere 

configuring ReportNet for, 78, 81 

enabling SSL, 80 

Windows 

installing ReportNet, 25 


uninstalling ReportNet, 101 

upgrading ReportNet, 101 


Index

Cognos ReportNetTM Installation and Configuration Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?