IBM® Cognos® 8 Analytic Applications Installation and

IBM® Cognos® 8 Analytic Applications Installation and
IBM® Cognos® 8 Analytic Applications
INSTALLATION AND CONFIGURATION GUIDE
Product Information
This document applies to IBM® Cognos® 8 Analytic Applications Version 8.4 and may also apply to subsequent releases. To check for newer
versions of this document, visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html).
Copyright
Copyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company.
Portions of Cognos ULC software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188
B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2;
6,995,768 B2; 7,062,479 B2; 7,072,822 B2; 7,111,007 B2; 7,130,822 B1; 7,155,398 B2; 7,171,425 B2; 7,185,016 B1; 7,213,199 B2; 7,243,106
B2; 7,257,612 B2; 7,275,211 B2; 7,281,047 B2; 7,293,008 B2; 7,296,040 B2; 7,318,058 B2; 7,325,003 B2; 7,333,995 B2.
Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBM
and the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries or both. Java and
all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product,
or service names may be trademarks or service marks of others.
While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors 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 the information contained in this document will be documented in subsequent editions.
U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer clause at
DFARS 252.227-7013, or subparagraphs (C)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227 as applicable.
The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.
This document contains proprietary information of Cognos. All rights are reserved. No part of this document may be copied, photocopied,
reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior
written consent of Cognos.
Table of Contents
Introduction 9
Using This Document 9
Chapter 1: What’s New?
11
New Features in Version 8.4 11
Support for IBM Cognos 8 Business Intelligence 8.4 11
Additional Language Support 11
Support for DB2 Universal Driver for Content Store, Notification, and Logging Databases 12
DB2 on z/OS as Content Store, Logging, or Notification Database 12
Support for IBM Cognos 8 BI for Linux on System z 12
Support for IPv6 IP Addresses 12
Changed Features in Version 8.4 13
Installing Supplementary Languages Documentation Required for Translated Product
Documentation 13
Default Connection to an IBM DB2 Content Store Replaces Microsoft SQL Server 13
IBM Java Runtime Environment (JRE) Replaces Sun Java Runtime Environment 13
Multilingual Support for Microsoft Analysis Services Data Sources 13
Deprecated Features in Version 8.4 13
Support for DB2 JDBC Type 2 Driver for the Content Store, Notification, and Logging
Databases on Linux, UNIX and Windows (db2java.zip) 14
Removed Features in Version 8.4 14
Text-based User Interface for Installing and Uninstalling on UNIX and Linux 14
Language Support for IBM Cognos 8 User Interface Text and Messages Moved from Supplementary Languages to IBM Cognos 8 Server Installation 14
New Features in Version 8.3 14
Support for Windows Vista 14
Create a DB2 Database to use as a Data Warehouse 15
Changed Features in Version 8.3 15
SAP Interface File Location 15
Deprecated Features in Version 8.3 15
Configuring Content Manager 15
Chapter 2: Components Used by IBM Cognos 8 Analytic Applications
17
IBM Cognos 8 Runtime and Reporting Components 17
IBM Cognos 8 Adaptive Applications Framework Components 19
Other Components 19
Installing IBM Cognos 8 Analytic Applications 19
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
21
All Components on One Computer 22
IBM Cognos 8 Adaptive Applications Framework Components and IBM Cognos 8 Runtime
Components on Different Computers 22
IBM Cognos 8 Runtime or Reporting Components on Different Computers 23
All IBM Cognos 8 Runtime Components on One Computer 24
Installation and Configuration Guide 3
Table of Contents
Gateways on Separate Computers 24
Application Tier Components and Content Managers on Separate Computers 25
More Than One Content Manager 25
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
27
IBM Cognos 8 Analytic Application Components used in Upgrade 27
Upgrade Process 28
Planning the Upgrade 29
Review the Documentation 30
Recommendation - Assess Applications in the Existing Environment 30
Recommendation - Perform a Trial Upgrade 32
Moving to the Production Environment 33
Installing IBM Cognos 8 Analytic Applications in a New Directory 34
Install IBM Cognos 8 Runtime Components in a New Directory 34
Install IBM Cognos 8 Adaptive Applications Framework Components in a New Directory 36
Installing IBM Cognos 8 Analytic Applications in the Same Directory 37
Manually Configure Customization 37
Install IBM Cognos 8 Runtime Components in the Same Directory 38
Install IBM Cognos 8 Adaptive Applications Framework Components in the Same Directory 39
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
41
Recommendation - Review the Readme Before You Install 41
Verify System Requirements 41
Review Supported Environments 43
Set Up Database Connectivity for the Content Store Database 44
Recommendation - Install and Configure the Basic Installation for Single Computers 45
Install IBM Cognos 8 Runtime or Reporting Components 46
Install Translated Product Documentation 48
Install the IBM Cognos 8 Service Pack and IBM Cognos 8 Updater 49
Install IBM Cognos 8 Adaptive Applications Framework Components 51
Install Application Content Files for the ERP 54
Install Translated Product Documentation 54
Install and Configure Additional Language Fonts 55
Configure Support for Japanese Yen and Korean Won Characters 56
Install SAP Interface Files 57
Install the SAP Gateway Functions 57
Install the SAP Content Interface Files 58
Apply the SAP Gateway Functions and Content Interface Files 59
Install the IBM Cognos Compression Utility 59
Set Access Permissions for the Gateway Functions and Content Interface Files 60
Default Settings for IBM Cognos 8 Analytic Applications 62
Uninstall IBM Cognos 8 Runtime or Reporting Components 63
Uninstall IBM Cognos 8 Runtime or Reporting Components for UNIX 63
Uninstall IBM Cognos 8 Runtime or Reporting Components for Windows 64
Uninstall IBM Cognos Content Database 65
Uninstall IBM Cognos 8 Adaptive Applications Framework Components 66
Uninstall IBM Cognos 8 Adaptive Warehouse Runtime for UNIX 66
Uninstall IBM Cognos 8 Adaptive Applications Framework for Windows 67
4
Table of Contents
Uninstall Application Content Files 68
Chapter 6: Setting Up the Environment
69
Guidelines for Creating the Content Store 69
Suggested Settings for Creating the Content Store in DB2 on Linux, Windows and UNIX 70
Suggested Settings for Creating the Content Store in DB2 on z/OS 72
Suggested Settings for Creating the Content Store in Oracle 73
Suggested Settings for Creating the Content Store in Microsoft SQL Server 74
Suggested Settings for Creating the Content Store in Sybase 75
Create Tablespaces for DB2 Content Store on z/OS 76
Set Up the Database Client for the Content Store 77
Set Up Environment Variables to Use Scripts 78
Update the Java Environment 80
JDBC Driver Options for Using DB2 Database as a Content Store 80
Configure the Web Server 81
Configure the Web Browser 82
Set Up the Data Source Environment 84
Create a DB2 Database to use as a Data Warehouse 85
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
87
Start IBM Cognos Configuration 87
Configure Single Computer Installations 88
Set Database Connection Properties for the Content Store 89
Update File Location Properties 91
Save Your Configuration Settings 92
Test the Installation and Configuration 93
Import the Splash Screen for the IBM Cognos 8 Analytic Applications Portal Page 94
Copy Image Files for Adaptive Analytics Report Icons 95
Finish the Configuration 95
Configure Distributed Installations 95
Set Database Connection Properties for the Content Store 96
Set the IBM Cognos 8 Gateway and Dispatcher Connections 99
Save Your Configuration Settings 100
Test the Installation and Configuration 100
Import the Splash Screen for the IBM Cognos 8 Analytic Applications Portal Page 102
Copy Image Files for Adaptive Analytics Report Icons 103
Change the Default Configuration Settings 103
Change a URI 103
Create Another Instance of the Cognos Content Database 105
Change the Default User and Password for Cognos Content Database 106
Change Cryptographic Settings 108
Configure Reporting Components to Use IBM Cognos Application Firewall 110
Configure Temporary File Properties 111
Update File Location Properties on Windows Vista 111
Configure the Gateway to Use a Namespace 114
Enable and Disable Services 114
Specify Resources for the IBM Cognos 8 Service 115
Change the Notification Database 116
Suggested Settings for Creating a DB2 Notification Database on z/OS 116
Create Tablespaces for the DB2 Notification Database on z/OS 116
Installation and Configuration Guide 5
Table of Contents
Change the Connection Properties for the Notification Database 117
Configure the SSL Protocol 118
Configure SSL for IBM Cognos 8 Adaptive Applications Framework 118
Set Up Shared Trust Between IBM Cognos Servers and Other Servers 121
Select and Rank Cipher Suites for SSL 122
Set Data Manager Runtime Data and Log File Locations 122
Configuring Log Messages 123
Guidelines for Creating a Logging Database 123
Create Tablespaces for DB2 Logging Database on z/OS 124
Set Up the Database Connectivity for the Logging Database 125
Log Message Destinations 128
Specify the Log Messages Destination 129
Change Global Settings 132
Customize Language Support to the User Interface 133
Customize Currency Support 134
Customize Content Locale Support 134
Map Content Locales 135
Map Product Locales 137
Customize the Server Time Zone 138
Change Encoding for Email Messages 138
Customize Cookie Settings 139
Configure Fonts 139
Change the Gateway 141
Configure the Gateway for IBM Cognos Apache Web Server Module 142
Configure a Servlet Gateway 144
Change the IP Address Version 145
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
149
Disable Anonymous Access 150
Restrict User Access to the Cognos Namespace 151
Configuring IBM Cognos 8 Components to Use Active Directory Server 151
Configure an Active Directory Namespace 152
Make Custom User Properties for Active Directory Available to IBM Cognos 8 Components 153
Enabling Secure Communication to the Active Directory Server 154
Include or Exclude Domains Using Advanced Properties 154
Enabling Single Signon Between Active Directory Server and IBM Cognos 8 Components 155
Configuring IBM Cognos 8 to Use IBM Cognos Series 7 Namespace 157
Configure an IBM Cognos Series 7 Namespace 157
Enabling Secure Communication to the Directory Server Used by the IBM Cognos Series 7
Namespace 158
Enabling Single Signon Between IBM Cognos Series 7 and IBM Cognos 8 158
IBM Cognos Series 7 Namespaces and the IBM Cognos Series 7 Trusted Signon Plug-in 159
Configuring IBM Cognos 8 to Use a Custom Authentication Provider 161
Configure a Custom Authentication Namespace 161
Hide the Namespace from Users During Login 162
Configuring IBM Cognos 8 Components to Use LDAP 163
Configure an LDAP Namespace 164
Configure an LDAP Namespace for Active Directory Server 165
6
Table of Contents
Configure an LDAP Namespace for IBM Directory Server 168
Configure an LDAP Namespace for Novell Directory Server 170
Configure an LDAP Namespace for Sun Java System Directory Server 172
Make Custom User Properties for LDAP Available to IBM Cognos 8 Components 174
Enable Secure Communication to the LDAP Server 175
Enabling Single Signon Between LDAP and IBM Cognos 8 Components 176
Replace Operation 177
Configuring IBM Cognos 8 Components to Use eTrust SiteMinder 177
Configure a Netegrity SiteMinder Namespace 179
Enabling Secure Communication to the eTrust SiteMinder User Directory 180
Enable Single Signon Between eTrust SiteMinder and IBM Cognos 8 180
Protecting the IBM Cognos Web Alias 180
Hide the Namespace from Users During Login 181
Configuring IBM Cognos 8 Components to Use an NTLM Namespace 181
Configure an NTLM Namespace 181
Enable Single Signon Between NTLM and IBM Cognos 8 Components 182
Configuring IBM Cognos 8 to Use SAP 182
Configure an SAP Namespace 184
Enable Single Signon Between SAP and IBM Cognos 8 185
Test the Namespaces 185
Delete an Authentication Provider 185
Chapter 9: Setting Up an Unattended Installation and Configuration
187
Set Up an Unattended Installation 187
Set Up an Unattended Configuration 190
Set Up an Unattended Uninstallation 191
Appendix A: Troubleshooting
193
Log Files 193
Problems Starting IBM Cognos 8 195
CFG-ERR-0106 Error When Starting the IBM Cognos 8 Service in IBM Cognos Configuration 196
Unable to Start the IBM Cognos 8 Service Because the Port is Used by Another Process 197
IBM Cognos 8 Service Does Not Start or Fails After Starting 198
IBM Cognos 8 Server Fails to Start and Gives No Error Message 198
IBM Cognos BI Server Not Available When Starting IBM Cognos 8 199
Cannot Log On to a Namespace When Using IBM Cognos Connection 202
IBM Cognos 8 Services Fail to Restart After a Network Outage 203
No Warning That Installing a Later Version of IBM Cognos 8 Will Automatically Update
the Earlier Version of the Content Store 203
DB2 Returns SQL1224N Error When Connecting from AIX 203
Content Manager Error When Starting IBM Cognos 8 204
The Page Cannot Be Found When Starting IBM Cognos 8 in Windows 2003 204
The Page Is Not Shown When Opening a Portal After Installing IBM Cognos 8 204
DPR-ERR-2058 Error Appears in Web Browser When Starting IBM Cognos 8 204
DPR-ERR-2022 Error Appears in Web Browser When Starting IBM Cognos 8 206
Unable to Download the cognos.xts File 207
Application Server Startup Script Fails 207
Deploying IBM Cognos 8 to an Oracle Application Server or IBM WebSphere Application
Server Fails 207
Installation and Configuration Guide 7
Table of Contents
Unable to Deserialize Context Attribute Error When Deploying the p2pd.war File to
WebLogic 208
Error Appears After Upgrading IBM Cognos 8 on a WebLogic Application Server 208
Problems Configuring IBM Cognos 8 209
Run Database Cleanup Scripts 209
Error Trying to Encrypt Information When Saving Your Configuration 210
Problems Generating Cryptographic Keys in IBM Cognos Configuration 211
Configuration Data is Locked by Another Instance of IBM Cognos Configuration 212
Unable to Exit a Tab Sequence When Using Keyboard-only Navigation in IBM Cognos Configuration 212
Unable to Save Your Configuration 212
Java Error When Starting IBM Cognos Configuration 213
Cryptographic Error When Starting IBM Cognos Configuration 213
Current Configuration Settings Are Not Applied to Your Computer 213
CM-CFG-029 Error When Trying to Save a Configuration That Specifies a SQL Server Content
Store 214
Users are Prompted for Active Directory Credentials 214
Font on UNIX Not Found When Starting IBM Cognos Configuration 215
Group Membership is Missing From Active Directory Namespace 215
Deploying IBM Cognos 8 to an Oracle Application Server or IBM WebSphere Application
Server 216
Errors Displayed Deploying to Oracle 10G Application Server 217
CGI Timeout Error While Connected to IBM Cognos 8 Components Through a Web
Browser 217
Servlet Class Fails to Load in WebLogic 218
Desktop Icons or IBM Cognos Configuration Window Flicker on Windows 219
Index
8
221
Introduction
This document is intended for use with IBM Cognos 8 Analytic Applications. It contains instructions
for installing, configuring, adding content to, and testing IBM Cognos 8 Analytic Applications.
IBM Cognos 8 Analytic Applications is a performance management solution that includes a populated
data warehouse, packages that describe the data available in the data warehouse, and a set of predefined reports.
Using This Document
The objectives of the IBM Cognos 8 Analytic Applications documentation are
●
to provide information about the initial deployment of the application
●
to introduce the content of each application and provide a reference to it
●
to help create the data warehouse, and customize and extend the application
●
to help create reports and make them accessible to the business users of the application
You should be familiar with
●
reporting concepts
●
database and data warehouse concepts
●
security issues
●
basic Windows and/or UNIX administration skills
●
the existing server environment, enterprise resource planning systems, and the security infrastructure in your organization
Related Documentation
Our documentation includes user guides, getting started guides, new features guides, readmes, and
other materials to meet the needs of our varied audience. The following documents contain related
information and may be referred to in this document.
Note: For online users of this document, a Web page such as The page cannot be found may appear
when clicking individual links in the following table. Documents are made available for your particular installation and translation configuration. If a link is unavailable, you can access the document
on the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html).
Document
Description
IBM Cognos 8 Analytic
Installing, upgrading, configuring, and testing IBM Cognos 8 Analytic
Applications Installation Applications
and Configuration Guide
Installation and Configuration Guide 9
Introduction
Document
Description
IBM Cognos Connection Using IBM Cognos Connection to publish, find, manage, organize,
User Guide
and view IBM Cognos content, such as scorecards, reports, analyses,
and agents
IBM Cognos 8 Administra- Managing servers, security, reports, and portal services; and setting
tion and Security Guide
up the samples, customizing the user interface and troubleshooting
Adaptive Warehouse User Designing and populating a data warehouse that is used by IBM
Guide
Cognos 8 Analytic Applications
Application user guides
Reference material about the content delivered with Cognos 8 Analytic
Applications.
Finding Information
Product documentation is available in online help from the Help menu or button in IBM Cognos
products, as well as from the Windows Start menu.
You can also read PDF versions of the product readme files and installation guides directly from
IBM Cognos product CDs.
Using Quick Tours
Quick tours are short online tutorials that illustrate key features in IBM Cognos product components.
To view a quick tour, start IBM Cognos Connection and click the Quick Tour link in the lowerright corner of the Welcome page.
Getting Help
For more information about using this product or for technical assistance, visit the IBM Cognos
Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html). This site provides
information on support, professional services, and education.
Printing Copyright Material
You can print selected pages, a section, or the whole book. You are granted a non-exclusive, nontransferable license to use, copy, and reproduce the copyright materials, in printed or electronic
format, solely for the purpose of operating, maintaining, and providing internal training on IBM
Cognos software.
10
Chapter 1: What’s New?
This section contains a list of new, changed, deprecated, and removed features for this release. It
also contains a cumulative list of similar information for previous releases. It will help you plan
your upgrade and application deployment strategies and the training requirements for your users.
For changes to previous versions, see:
●
New Features in Version 8.3
●
Changed Features in Version 8.3
●
Deprecated Features in Version 8.3
To review an up-to-date list of environments supported by IBM Cognos products, such as operating
systems, patches, browsers, Web servers, directory servers, database servers, and application servers,
visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.
html).
New Features in Version 8.4
Listed below are new features since the last release. Links to directly-related topics are included.
Support for IBM Cognos 8 Business Intelligence 8.4
IBM Cognos 8 Analytic Applications now support IBM Cognos 8 Business Intelligence 8.4. For
information about using analytic applications in an IBM Cognos 8 Business Intelligence 8.4 environment, see the IBM Cognos 8 Analytic Applications Installation and Configuration Guide.
Additional Language Support
In addition to Japanese, German, and French, the installation documentation and the user interface
for the installation program and IBM Cognos Configuration are available in the following languages:
●
Chinese (simplified)
●
Chinese (traditional)
●
Korean
●
Italian
●
Spanish
●
Portuguese (Brazilian)
During the installation you can select the language to use from the first page of the installation
wizard. This determines the language of the user interfaces of the installation wizard and IBM
Cognos Configuration. For more information, see "Install IBM Cognos 8 Runtime or Reporting
Components" (p. 46).
Installation and Configuration Guide 11
Chapter 1: What’s New?
Support for DB2 Universal Driver for Content Store, Notification, and Logging
Databases
DB2 introduced a universal JDBC driver that contains both type 2 and type 4 JDBC driver support.
IBM Cognos 8 can connect to a DB2 content store, notification database, or logging database using
either type of JDBC connectivity, but you must first copy two JAR files to the IBM Cognos 8
installation directory. If you are upgrading, you can continue to use type 2 JDBC connectivity
without changing the connection properties for the DB2 content store.
For more information about connection properties for the content store, see "Set Database Connection Properties for the Content Store" (p. 89).
The two JAR files that you must copy to your IBM Cognos 8 installation directory are as follows:
●
a license file, for example db2jcc_license_cisuz.jar or db2jcc_license_cu.jar
●
a driver file, db2jcc.jar
For information about copying these files, see "Set Up Database Connectivity for the Content Store
Database" (p. 44).
DB2 on z/OS as Content Store, Logging, or Notification Database
You can use DB2 on z/OS as your content store, logging, or notification database.
Connection settings to DB2 on z/OS are similar to those for DB2 on Linux, UNIX and Windows.
However, additional advanced settings must be configured.
For information about the configuration settings, see "Suggested Settings for Creating the Content
Store in DB2 on z/OS" (p. 72), "Suggested Settings for Creating a DB2 Notification Database on
z/OS" (p. 116), and "Suggested Settings for Creating the DB2 Logging Database on z/OS" (p. 124).
You must run scripts to create tablespaces for storing Large Objects (LOBs). For more information,
see "Create Tablespaces for DB2 Content Store on z/OS" (p. 76), "Create Tablespaces for the DB2
Notification Database on z/OS" (p. 116), and "Create Tablespaces for the DB2 Notification Database
on z/OS" (p. 116).
Support for IBM Cognos 8 BI for Linux on System z
IBM Cognos 8 BI version 8.4 is available for Linux on System z. After installing the required server
components, you must install Framework Manager on a Windows computer to complete a basic
installation. Optional server and Windows components are available to extend functionality. For
more information, see the Installation and Configuration Guide for Linux on System z.
Support for IPv6 IP Addresses
IBM Cognos 8 now supports two IP address protocols: IPv4 and IPv6. IPv4 uses 32-bit IP addresses
and IPv6 uses 128-bit IP addresses. The default is IPv4.
For IBM Cognos Configuration to accept IPv6 addresses in the local URI properties, you must start
IBM Cognos Configuration with the -ipv6 option. You can specify the option each time you open
IBM Cognos Configuration from the command line.
On Windows, you can set the option permanently by adding the option to the Start menu shortcut.
12
Chapter 1: What’s New?
For more information, see "Change the IP Address Version" (p. 145).
Changed Features in Version 8.4
Listed below are changes to features since the last release. Links to directly-related topics are
included.
Installing Supplementary Languages Documentation Required for Translated
Product Documentation
You must install the Supplementary Languages Documentation to access product documentation
in languages other than English. For more information, see "Install Translated Product Documentation" (p. 48).
By default, when you install the IBM Cognos 8 gateway component, the installation documentation,
which includes the Installation and Configuration Guide, the Quick Start Installation and Configuration Guide and the Readme, is installed in all supported languages. The product documentation,
such as the Administration and Security Guide, is installed in English.
Default Connection to an IBM DB2 Content Store Replaces Microsoft SQL Server
When you start Cognos Configuration for the first time, the connection to IBM DB2 replaces
Microsoft SQL Server for the default content store.
If you did not install IBM Cognos Content Database, and want to use another database server for
the content store, you must delete the default content store. After you uninstall, if you install into
the same location as a previous release, your configuration is preserved and the existing content
store is used.
For more information, see "Set Up Database Connectivity for the Content Store Database" (p. 44).
IBM Java Runtime Environment (JRE) Replaces Sun Java Runtime Environment
IBM Cognos 8 now contains the IBM version of the JRE as part of Windows installations. This
replaces the Sun JRE for 32-bit Windows platforms.
The installation location remains the same. Any content encrypted with Sun JRE can be decrypted
with the IBM JRE.
Multilingual Support for Microsoft Analysis Services Data Sources
Users in different languages can now connect to an MSAS 2005 data source from a single instance
of IBM Cognos 8. For more information, see "Set Up the Data Source Environment" (p. 84).
Deprecated Features in Version 8.4
A deprecated feature is one that is being replaced by a newer version or a better implementation.
The intention is to discontinue the use of the feature and provide recommendations for adapting
to this change over multiple releases.
Listed below are deprecated features, including links to related topics.
Installation and Configuration Guide 13
Chapter 1: What’s New?
Support for DB2 JDBC Type 2 Driver for the Content Store, Notification, and
Logging Databases on Linux, UNIX and Windows (db2java.zip)
DB2 introduced a universal JDBC driver that contains both type 2 and type 4 JDBC driver support.
This new universal driver replaces the deprecated type 2 driver, db2java.zip.
You can continue to use type 2 connectivity with no configuration changes required. If you choose
to use type 4 connectivity, a configuration change is required.
For more information, see "Set Database Connection Properties for the Content Store" (p. 89).
This does not affect the metric store database, which continues to use the DB2 JDBC Type 2 Driver
(db2java.zip).
Removed Features in Version 8.4
Listed below are features that are removed since the last release. Links to directly-related topics are
included.
Text-based User Interface for Installing and Uninstalling on UNIX and Linux
In earlier versions of IBM Cognos 8 BI products, you could run a text-based, or console-mode,
installation or uninstallation program on systems that did not have XWindows. In the current
release, the text-based installation and uninstallation programs are not available. Users who install
on UNIX and Linux without XWindows must run an unattended installation "Set Up an Unattended
Installation " (p. 187) or uninstallation "Set Up an Unattended Uninstallation" (p. 191).
Language Support for IBM Cognos 8 User Interface Text and Messages Moved
from Supplementary Languages to IBM Cognos 8 Server Installation
IBM Cognos 8 comes with a set of user interface text and messages in several more languages than
in the previous release. You are no longer required to install supplementary languages from a separate installation program to show the user interface in one of the supported languages. The required
files are automatically installed when you install the IBM Cognos 8 server.
However, you must use Supplementary Languages Documentation to install the Andale WT fonts
for Japan and Korea. These fonts map the U+005C value as a yen or won character. For more
information, see "Install and Configure Additional Language Fonts" (p. 55).
New Features in Version 8.3
Listed below are new features since the last release. Links to directly-related topics are included.
Support for Windows Vista
IBM Cognos 8 is supported on Windows Vista. With Windows Vista, Microsoft introduced security
enhancements to further protect the Program Files directory. This necessitated changes to environment
variables and the directories where user profiles are stored. For more information, see "Update File
Location Properties on Windows Vista" (p. 111).
14
Chapter 1: What’s New?
Create a DB2 Database to use as a Data Warehouse
IBM Cognos 8 Analytic Applications now provides a script that creates and configures a DB2
database that you can use as a data warehouse. After you run this script, you must create a connection to the database in Adaptive Warehouse, in order to use it as a data warehouse.
Changed Features in Version 8.3
Listed below are changes to features since the last release. Links to directly-related topics are
included.
SAP Interface File Location
In the previous release, the installation wizard installed the SAP interface files in the application_
content_location\bin directory. In the new release, the SAP interface files are located in the application_content_location\applicatiotransports\sap\SAP_version\workforce_performance directory.
For more information, see "Install the SAP Content Interface Files" (p. 58).
Deprecated Features in Version 8.3
A deprecated feature is one that is being replaced by a newer version or a better implementation.
These features will be discontinued, and we will provide recommendations for adapting to these
changes over multiple releases.
Listed below are deprecated features, including links to related topics.
Configuring Content Manager
The Create symmetric key store property could be enabled or disabled in older versions. It was
typically set to true on the active Content Manager and false on standby Content Managers. These
settings enabled standby Content Managers to retrieve the master common symmetric key from
the active Content Manager.
The Create symmetric key store property is deprecated in Version 8.3 because Content Managers
can now dynamically determine the active Content Manager and automatically retrieve the key.
For more information, see "Change Cryptographic Settings" (p. 108).
Installation and Configuration Guide 15
Chapter 1: What’s New?
16
Chapter 2: Components Used by IBM Cognos 8
Analytic Applications
IBM Cognos components integrate 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 another database for the content store. Other resources are optional, such as a security
provider for authentication.
Some IBM Cognos components, including Adaptive Analytics, use an application server. Apache
Tomcat is provided as the default application server.
The following diagram shows the relationship between the IBM Cognos 8 Analytic Applications
components and IBM Cognos 8 BI.
Analytic Applications
Application content
files
Adaptive Applications
Framework
Adaptive Analytics
Adaptive Warehouse
Tier 1: Web
IBM Cognos 8 Business Intelligence
Gateway
IBM Cognos Connection
Cognos Viewer
Tier 2: Applications
Application Tier
Components
Content Manager
Tier 3: Data
Content store
Data source
ERP system
IBM Cognos 8 Runtime and Reporting Components
IBM Cognos 8 Analytic Applications uses the following IBM Cognos 8 runtime and reporting
components. Depending on your application, not all of the components may be available.
Installation and Configuration Guide 17
Chapter 2: Components Used by IBM Cognos 8 Analytic Applications
IBM Cognos Connection
IBM Cognos Connection is the Web portal for IBM Cognos 8. It provides a single access point to
corporate data. It also provides a single point of entry for querying and organizing data. Users can
run all their Web-based IBM Cognos 8 applications through IBM Cognos Connection. Other
business intelligence applications, and URLs to other applications, can be integrated with IBM
Cognos Connection.
Cognos Viewer
Cognos Viewer is a portlet in which you can view and interact with any type of published IBM
Cognos content. It is accessible through IBM Cognos Connection and any existing enterprise portal.
IBM Cognos Configuration
IBM Cognos Configuration is a tool that you use to configure IBM Cognos 8, and to start and stop
its services.
Gateway
Web communication in IBM Cognos 8 is typically through gateways, which reside on one or more
Web servers. A gateway is 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 Internet Server
Application Program Interface (ISAPI) and Apache Modules (apache_mod).
Content Manager
Content Manager is the IBM Cognos 8 service that manages the storage of customer application
data, including security, server configuration data, packages, and models. Content Manager also
manages the Cognos namespace.
Report Studio
Using Report Studio, report authors create, edit, and distribute a wide range of professional reports.
Note: Depending on your application, Report Studio may not be available.
Cognos Content Database
Cognos Content Database is an instance of an Apache Derby database. It is a selectable component,
and is not installed by default. If you install it on the same computer as Content Manager, Cognos
Content Database is configured as the default content store for IBM Cognos 8.
Cognos Content Database can be used if you do not want to implement another database for the
content store.
Apache Derby is open source software whose license terms can be found on the Apache Derby web
site. Modifying the Apache Derby database or using it with other products is not supported. Any
modifications that you make to the Apache Derby database are at your own risk.
You can use Cognos Content Database as a content store or notification database, but not as a
query database.
Note: Depending on your application, Cognos Content Database may not be available.
18
Chapter 2: Components Used by IBM Cognos 8 Analytic Applications
IBM Cognos 8 Adaptive Applications Framework Components
IBM Cognos 8 Adaptive Applications Framework consists of the following components.
Adaptive Warehouse
Adaptive Warehouse is a data modeling environment for users to design and populate a target data
warehouse. It provides an interface that facilitates the extraction, transformation, and loading of
application-specific data from an enterprise resource planning (ERP) source into the target data
warehouse.
Adaptive Warehouse Runtime
Adaptive Warehouse Runtime is an engine component that is used by the Adaptive Warehouse user
interface and scripts.
Adaptive Analytics
Adaptive Analytics provides a set of reports for performance monitoring, analyses, and operational
reporting. These role-based report layouts allow users to quickly start analyzing the data in their
warehouse for each performance application.
Other Components
IBM Cognos 8 Analytic Applications uses the following additional components.
Content Store
The content store is a relational database that contains data, such as report packages, that IBM
Cognos 8 Analytic Applications needs to operate. It also contains connection information about
the external namespace, and the Cognos namespace itself.
Log files are not stored in the content store.
The IBM Cognos 8 service that uses the content store is named Content Manager.
Data Sources
Data sources are relational databases or other physical data stores that you can access through IBM
Cognos 8 Analytic Applications.
Application Tier components use data source connections to access data sources.
Enterprise Resource Planning (ERP) System
IBM Cognos 8 Analytic Applications delivers pre-packaged mappings for different ERP source
systems.
Installing IBM Cognos 8 Analytic Applications
When installing Analytic Applications, consider which installation and configuration options will
provide the best possible performance, based on your requirements, resources, and preferences.
To assess your installation options, you must consider whether you want to
Installation and Configuration Guide 19
Chapter 2: Components Used by IBM Cognos 8 Analytic Applications
●
perform an initial installation, or upgrade an existing installation.
●
install the components on a single computer, or distribute them across a network.
Use the following checklist to guide you through the installation process.
❑
Upgrade existing Analytic Applications "Upgrading IBM Cognos 8 Analytic Applications" (p. 27).
❑
Install IBM Cognos 8 Runtime or IBM Cognos 8 BI Reporting
You must install IBM Cognos 8 Runtime or IBM Cognos 8 BI Reporting, or have IBM Cognos 8
BI installed and running before you can install the Adaptive Applications Framework on your
client computers. For more information, see "Install IBM Cognos 8 Runtime or Reporting
Components" (p. 46).
❑
Apply the IBM Cognos 8 service pack and updater
You must apply a service pack and updater on each IBM Cognos server, so that is compatible
with the version of Analytic Applications that you are installing. For more information, see
"Install the IBM Cognos 8 Service Pack and IBM Cognos 8 Updater" (p. 49).
❑
Install Analytic Applications Framework
You can install Analytic Applications Framework for a user based environment or a script
based environment. For more information, see "Install IBM Cognos 8 Adaptive Applications
Framework Components" (p. 51).
❑
Perform other configuration
After installing and configuring IBM Cognos 8 runtime or reporting components, and Analytic
Applications Framework, you can start using Adaptive Warehouse and Adaptive Analytics. At
this point, you can perform additional configuration procedures to address issues related to:
●
performance
●
security
●
redundancy
●
batch processing requirements
●
specific network configurations
●
operating systems
For more information, see the Administration and Security Guide.
20
Chapter 3: Distribution Options for IBM Cognos 8
Analytic Applications
IBM Cognos 8 Analytic Applications consists of the following installation CDs:
●
IBM Cognos 8 Runtime or IBM Cognos 8 BI Reporting
The CD that is available depends on your application.
You must install these components if
●
you do not have IBM Cognos 8 installed in your environment
●
your installed version of IBM Cognos 8 is incompatible with the IBM Cognos 8 Analytics
Applications installation
If you need to install these components, and IBM Cognos 8 is already installed in your environment, you must install them in a different location than IBM Cognos 8.
●
IBM Cognos 8 Adaptive Applications Framework
This Windows CD installs the Adaptive Warehouse and Adaptive Analytics user interface
components.
You should install these components if
●
●
you are setting up a demonstration or proof of concept environment
●
you are setting up a user interface development or production environment
●
you want to create scripts that run in a script-based production environment
IBM Cognos 8 Adaptive Applications Framework Runtime
This CD installs the Adaptive Warehouse Runtime component.
You should install this component if you are setting up a script-based production environment
that uses a dedicated server to perform regular updates to the database.
●
application content CD
This CD contains the application content files for your ERP system.
You can install all IBM Cognos 8 Analytic Applications components on one computer, or install
them on different computers. The best distribution option depends on your requirements, resources,
and preferences. Configuration requirements differ depending on whether you install all components
on a single or multiple computers.
We strongly recommend that you install the IBM Cognos 8 Adaptive Applications Framework
components in a different location than IBM Cognos 8 runtime components. The application content
files can be installed in any location on any computer.
Installation and Configuration Guide 21
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
All Components on One Computer
You can install the IBM Cognos 8 runtime or reporting components, the IBM Cognos 8 Adaptive
Applications Framework components, and the application content files on one Windows computer.
Choose this option for setting up a demonstration or proof of concept environment, where the user
load is small.
You must install IBM Cognos 8 runtime or reporting components in a different location on the
computer than IBM Cognos 8 Adaptive Applications Framework components.
For this option, install the IBM Cognos 8 runtime or reporting components, followed by Adaptive
Warehouse and Adaptive Analytics from the IBM Cognos 8 Adaptive Applications Framework CD.
You must also install the application content files from the application content CD.
Note: If a compatible version of IBM Cognos 8 is already installed in your environment, the IBM
Cognos 8 runtime components are available and it is not necessary to install them.
Depending on your application and whether a compatible version of Report Studio is already
installed in your environment, it may be necessary to install IBM Cognos 8 BI Reporting.
Because the gateway must be located with the Web server, the single computer must also be running
a Web server.
IBM Cognos 8 Adaptive Applications Framework Components
and IBM Cognos 8 Runtime Components on Different Computers
You can distribute the installation so that IBM Cognos 8 runtime or reporting components are
installed on one computer, and IBM Cognos 8 Adaptive Applications Framework components are
installed on a different computer.
You must install the IBM Cognos 8 server components using the IBM Cognos 8 Runtime CD or
the IBM Cognos 8 BI Reporting CD. Because the gateway must be located with the Web server,
the computer on which you install the IBM Cognos 8 runtime components must also be running a
Web server.
Note: If a compatible version of IBM Cognos 8 is already installed in your environment, the IBM
Cognos 8 runtime components are available and it is not necessary to install them. Depending on
your application, application requirements and whether a compatible version of Report Studio is
already installed in your environment, it may be necessary to install IBM Cognos 8 BI Reporting.
You can then install the IBM Cognos 8 Adaptive Applications Framework components on a different
computer. The CDs that you require for installation depend on the type of environment you are
setting up.
If you are setting up a user interface development or production environment, or you want to create
scripts that run in a script-based production environment, install Adaptive Warehouse and Adaptive
Analytics from the IBM Cognos 8 Adaptive Applications Framework CD.
22
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
If your production environment is script-based and uses a dedicated server to schedule regular
updates to the database, install the Adaptive Warehouse Runtime component from the IBM Cognos 8
Adaptive Applications Framework Runtime CD.
You must also install the application content files from the application content CD. You can install
these files in any location on any computer.
Configuration Requirements for a User Interface Environment
To configure the user interface environment, you must
●
configure your Web server (this is not required if IBM Cognos 8 is already installed in your
environment)
●
specify connection information to the content store on the computer on which IBM Cognos 8
runtime components are installed (this not required if IBM Cognos 8 is already installed in
your environment)
●
set the port numbers for the IBM Cognos 8 gateway and dispatcher, on the computer on which
IBM Cognos 8 Analytic Applications are installed
Configuration Requirements for a Script-based Environment
To configure the script-based environment for Adaptive Warehouse, you must
●
ensure your IBM Cognos 8 environment is running
●
specify connection information to the data sources
●
set up environment variables so that you can run scripts
●
set the port numbers for the IBM Cognos 8 gateway and dispatcher
IBM Cognos 8 Runtime or Reporting Components on Different
Computers
When you install IBM Cognos 8 runtime or reporting components, you specify where to install the
gateways, Application Tier Components, and Content Manager. You can install these components
using any of these options:
●
Install all components on one computer.
This option is typically used for a demonstration or in a proof of concept environment.
●
Install the gateway on a separate computer.
In this option, the gateway and Web server are on one computer, and the remaining IBM Cognos
components are on other computers. You may choose this option if you have existing Web
servers available to handle IBM Cognos component requests.
●
Install Application Tier Components and Content Manager on separate computers.
Choose this option to maximize performance, availability, capacity, or security based on the
processing characteristics of your organization.
Installation and Configuration Guide 23
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
After installing IBM Cognos 8 runtime or reporting components, you must configure them to
communicate with each other.
If a compatible version of IBM Cognos 8 is already installed in your environment, the IBM Cognos 8
runtime components are available and it is not necessary to install them. For more information on
distribution options for IBM Cognos 8, see the IBM Cognos 8 Installation and Configuration Guide.
All IBM Cognos 8 Runtime Components on One Computer
You can install all the IBM Cognos 8 runtime or reporting components on one computer. Choose
this option for proof of concept or demonstration environments where the user load is small.
Because the gateway must be located with the Web server, the single computer must also be running
a Web server.
In the following diagram, all IBM Cognos 8 server components are installed on one computer. The
content store, data sources, and Adaptive Warehouse and Adaptive Analytics are located on different
computers.
Single Computer Installation of
IBM Cognos 8 Runtime Components
Adaptive Warehouse
Adaptive Analytics
Web server
Gateway
Application Tier Components
Content Manager
Content Store
Query Databases
Configuration Requirements
If you install all IBM Cognos 8 runtime components on the same computer, you must then
●
configure your Web server to view IBM Cognos content
●
specify connection information to the content store
Gateways on Separate Computers
The gateway is installed on one or more Web servers.
24
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
You can install the gateway and a Web server on one computer, and install the remaining IBM
Cognos 8 server components on different computers. If you have a Web farm, you may want to
install a gateway on each Web server. Using multiple Web servers to manage incoming requests
provides a better level of service.
Configuration Requirements
If you install one or more gateways on separate computers, ensure that you can view IBM Cognos
content and that the gateways can communicate with other components. On each computer where
the gateway is installed you must
●
configure your Web server to host IBM Cognos content
●
configure the Dispatcher URIs
Application Tier Components and Content Managers on Separate Computers
You can install the Application Tier Components 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 are a large number of requests to process,
you can install the Application Tier Components on multiple computers dedicated to processing
incoming requests. Installing the Application Tier Components on multiple computers distributes
and balances the load among the computers. You also have better accessibility and throughput than
on a single computer, as well as support if one computer fails.
Configuration Requirements
If you install one or more Application Tier Components on a separate computer, to ensure that
they can communicate with other IBM Cognos 8 runtime reporting components you must
●
specify all Content Manager URIs
●
specify the Dispatcher URIs
●
specify the Dispatcher URI for external applications
More Than One Content Manager
You can install any number of installations of Content Manager, although only one is active at any
time. The other installations each act as a standby Content Manager. For failover support, we
recommend that you install Content Manager on two or more computers.
Content Manager stores the data that IBM Cognos 8 Analytic Applications needs to operate as well
as connection information for data sources, information about the external namespace, and the
IBM Cognos namespace. The content store is a relational database management system (RDBMS).
There is only one content store for each IBM Cognos installation.
You may choose to install Content Manager separately from the Application Tier Components.
When an active Content Manager fails, unsaved session data is lost. When the new active Content
Manager takes over, users may be prompted to log on.
Installation and Configuration Guide 25
Chapter 3: Distribution Options for IBM Cognos 8 Analytic Applications
Configuration Requirements
On each computer where you install Content Manager, you must
26
●
specify connection information to the content store
●
specify the Dispatcher URIs
●
specify all Content Manager URIs
●
specify the Dispatcher URI for external applications
Chapter 4: Upgrading IBM Cognos 8 Analytic
Applications
If you have a previous version of IBM Cognos 8 Analytic Applications installed you must upgrade
to the most recent version to use the new features available.
You can upgrade directly to the new version of IBM Cognos 8 Analytic Applications from version
8.2 or later.
New versions of IBM Cognos 8 Analytic Applications provide enhancements that may affect many
components, such as product features and functionality, performance and scalability, and usability.
Because of these improvements, upgrading may not be simple, and should be considered a process
that you perform in stages.
You should treat upgrading as an IT project that requires careful planning, adequate time, and
resources.
To upgrade IBM Cognos 8 Analytic Applications, you use several components to perform the following tasks:
❑
Plan the upgrade (p. 29).
❑
Upgrade IBM Cognos 8 Analytic Applications by installing the components in either a new
directory (p. 34), or the same directory (p. 37) as the previous version.
❑
Use Adaptive Warehouse to upgrade the model.
For more information, see the Adaptive Warehouse User Guide.
❑
Use Adaptive Analytics to upgrade your reports.
For more information, see the Adaptive Analytics User Guide.
❑
Use IBM Cognos Connection to publish reports, review, and test the output.
For more information, see the Adaptive Analytics User Guide.
IBM Cognos 8 Analytic Application Components used in
Upgrade
The following diagram shows the tasks and components that are involved in the upgrade process.
Installation and Configuration Guide 27
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
Analytic
Applications
Plan for
implementation
current
documentation
Adaptive
Warehouse
Adaptive
Analytics
IBM Cognos
Connection
Install
Analytic
Applications
Configure
Analytic
Applications
Upgrade
model
Publish
packages
Upgrade
reports
Deploy
reports
Publish
reports
Review
reports
Upgrade Process
Although you can install the new version of the product in the same location as the existing version
after you uninstall, we recommend that you first install into a new location, such as a test environment. This allows you to test your applications in both the old and new environment to ensure that
they work as expected before you move them to the production environment.
Different groups are commonly involved in each of these activities. As part of the project, you
should assess both your current IT environment and your existing applications separately, to ensure
that the infrastructure can support your business objectives.
The following diagram shows the stages in the upgrade process that we recommend. Before you
start, you plan the upgrade, assess the applications that you want to upgrade and create a test
environment. You should iteratively deploy and test content in both the existing and new environments before you move to successfully upgraded applications to a production environment.
28
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
Upgrade Process Workflow
New environment
Source environment
1
Plan the
upgrade
2
3
Assess
applications
Create new
environment
4
Deployment process
Plan
Export existing
content
Upgrade
reports
Upgrade
model
Import in new
environment
5
Test upgraded
applications
6
Move to production environment
Prepare
environment
Back up
files
Uninstall
Install new
version
Deploy from
test
environment
Planning the Upgrade
We recommend that you plan your upgrade so that you know what to expect at each stage of the
process. In the planning stage, you can review the upgrade documentation for information about
expected behavior, new features, deprecated features, compatibility between versions, and requirements for preparing your production environment. When you finish the review, you can then conduct
a site survey to identify the infrastructure, reports, and custom configuration settings. Finally, you
can test the upgrade on a subset of your data so that you can fine tune your reports and data before
committing to the full upgrade.
The following diagram shows a high level view of the phases in an upgrade project.
Source environment
Planning the
upgrade
New environment
1
2
Assess
content
Create test
environment
3
Upgrade
content
4
5
Test upgraded
applications
Move to
production
When planning your upgrade, ensure that you
●
gather the necessary information, such as the required inputs and expected outputs for each
phase
●
assess the applications in your reporting environment and group similar reports together
●
install the new software in a test environment and deploy the content to the test environment
●
test the upgraded applications to ensure reports run as expected
Deployment and testing is usually an iterative process. Assess any differences between the existing
and new environments to determine actionable activities. Move to your production environment
when you are satisfied that the deployed applications meet your business requirements.
Use the following checklist to guide you through the planning process:
❑
Review the documentation.
❑
Assess applications in the existing environment.
Installation and Configuration Guide 29
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
❑
Perform a trial upgrade.
❑
Move to the production environment.
Review the Documentation
Documentation is provided from a variety of sources to help you achieve a successful upgrade.
Steps
1. Read the What's New section in this guide.
2. Read the rest of the upgrade information in this document.
3. Review the latest versions of the following documentation:
Document
Description
The Readme specific to your application
Recent issues that may affect an upgrade
The user guide specific to your application How the content has changed since the
previous release, and how to upgrade your
application
Adaptive Warehouse User Guide
Upgrading a model
Adaptive Analytics User Guide
Upgrading a report
Recommendation - Assess Applications in the Existing Environment
Preparing to upgrade provides an opportunity to review your current BI investment, and clean up
your existing environment. Inventory your BI applications to understand the strengths, weaknesses,
and areas for improvement in your environment.
For example, you may have a hundreds of reports, packages, public folders and applications in
your environment. However, it is not uncommon to find that a number of applications are not
used, or no longer meet the company’s requirements, or do not work in the existing environments.
We recommend that you conduct an audit of your applications to determine which applications
should be upgraded. Assessing and reducing the number of reports is a useful exercise. Do not rely
only on user feedback to determine which content is used.
An audit of your existing applications may include the following:
❑
Do a site survey.
A survey will help you to assess the current production environment and identify areas that
require attention during an upgrade. The site survey should include information about the
infrastructure, applications, users, and configuration settings for your IBM Cognos 8 products.
❑
30
Assess the software that you use in your reporting application by doing the following:
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
❑
❑
●
List software, such as operating systems, Web servers, security, databases, and so on.
●
Compare the list to the supported versions for your target upgrade version, available from
the Production Information, Software Environments link at the IBM Cognos Customer
Service Center (http://www.ibm.com/software/data/support/cognos_crc.html).
●
Determine whether any other components require updating.
List your BI applications, including the following:
●
Adaptive Warehouse models and packages
●
Adaptive Analytics reports
Complete a detailed assessment of your applications.
The usage, age, size, and complexity of your applications are important factors to consider
when planning the upgrade. The total size of the applications may have an impact on the time
required to complete the upgrade.
❑
List all the reports contained in your application and do the following:
●
Interview the team members to see which cubes, views, or reports are needed and used,
which ones can be consolidated, and which ones can be eliminated. Use audit report data
to determine report usage.
Upgrade only the reports that work and that users need and use. This reduces the number
of applications that you must upgrade.
For more information about audit reports, see the IBM Cognos 8 Administration and
Security Guide.
●
Look at the purpose of each report and assign a priority.
This identifies business-critical applications and the functionality that is required in the
new environment.
●
Flag reports that fail to run or validate in the current environment.
They are unlikely to upgrade successfully. Repair these reports so that they upgrade.
❑
●
Consider retiring unused or little-used reports.
●
Group the reports into categories, such as upgrade, eliminate, no longer used, and do not
upgrade,
List the following information about your configuration:
●
configuration settings that you enabled using IBM Cognos Configuration
These settings are preserved through the upgrade. They are stored in cogstartup.xml and
coglocale.xml.
●
changes to other configuration files
Changes to other files must be made manually during the upgrade. If you changed other
configuration files, you must assess the changes that you want to preserve in the upgraded
Installation and Configuration Guide 31
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
environment. This may include .xml, .txt, and .css files in the configuration, templates,
webapps, and webcontent directories of the installation location.
Important: Changes to .ini files are not supported. If you changed .ini files, please contact
Customer Support.
❑
Back up all reports, models, and configuration data and files.
Recommendation - Perform a Trial Upgrade
Pilot upgrade projects are valuable and practical exercises because they ensure that the upgrade
produces the expected and required outcome. In addition, an evaluation of the pilot project ensures
that the upgrade is successful. If unexpected results occur, you can determine whether the differences
are enhancements for your situation or whether you should take action to mitigate the differences.
We recommend that you perform a trial upgrade several weeks before upgrading your production
system. The trial upgrade identifies components that will upgrade with minimal effort and components that may require additional actions before or after the upgrade.
Commonly, you upgrade a sample set of reports in an isolated environment, and you compare the
appearance and behavior of the reports before and after the upgrade.
Ensure skilled resources are available to perform migration work, especially for mission-critical
applications. Also, test and debug all applications prior to deployment.
Steps
1. Prepare the test environment (p. 34) by doing the following:
●
Install the new version in the test environment.
●
Configure the test system to match your production environment.
2. Using Adaptive Warehouse,
●
export the existing content file to the test environment, and ensure that the data source
connections to the data warehouse are valid
●
upgrade the data warehouse on the test system and publish the packages
For more information, see the user guide for your application and the Adaptive Warehouse
User Guide.
3. Using Adaptive Analytics,
●
upgrade your project on the test system
●
create and deploy a deployment archive
For more information, see the user guide for your application and the Adaptive Analytics User
Guide.
4. In IBM Cognos Connection, publish the reports from the deployment archive.
5. Review the applicable reports and note whether each report ran successfully.
32
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
6. Repair or exclude reports and models that do not operate correctly.
7. Test the repaired reports and models by running them again on the test system.
Troubleshoot any issues and contact IBM Cognos Software Support about unresolved upgrade
issues.
8. Revise the upgrade plan to include adaptations that you made during the trial upgrade.
Moving to the Production Environment
When all issues that you discovered during the trial upgrade are resolved, you are ready to begin
the full upgrade in your production environment. Your upgrade plan will provide the details for
each step of the full upgrade.
The following diagram shows the high level steps in the process of moving upgraded applications
to a production environment.
6
Move to production environment
Prepare
environment
Back up
files
Uninstall
Install new
version
Deploy from
test
environment
After preparing the production environment and backing up data and configuration files, you can
uninstall the older version of the software, and install the new version in the same location. Then
you can deploy the content from your test environment. For more information about deploying
content, see the Adaptive Warehouse User Guide and the Adaptive Analytics User Guide.
Use the following checklist to guide you through the process of moving to a production environment:
❑
Prepare the production environment.
●
Back up files and data.
You may have modified files other than those in the configuration folder. If so, you should
also back up the additional files before upgrading.
When you back up the configuration data, store it in a secure directory. You must protect
the directory from unauthorized or inappropriate access.
●
Install your new version in the production environment.
If you install the new software from the test environment to the same location as the
existing software, you must first uninstall the existing software.
●
❑
Configure the system.
Manually configure customizations.
●
If you manually edited any configuration files, the changes will be overwritten during the
upgrade. You must reapply the changes. You should keep a record of any customizations
to ensure that they can be reapplied after upgrading. You should also back up these files
so that you can restore the original version if necessary.
Installation and Configuration Guide 33
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
❑
●
The IBM Cognos 8 presentation service supports automatic upgrade of some system.xml
files. If you made many customization changes to system.xml files, you can use this automatic
upgrade feature instead of reapplying the changes manually after upgrading. The system.xml
files are overwritten during the installation of IBM Cognos 8. Therefore, you must back
up the customized versions of these files and then copy them to the directory after
upgrading IBM Cognos 8. The automatic upgrade will be applied when you start the IBM
Cognos 8 service.
●
The system.xml files for which automatic upgrade is supported are in the following
directories: c8_location/templates/ps, c8_location/templates/ps/portal, and c8_location/
templates/ps/qs.
●
Note: We recommend that you manually reapply changes to customized files after installing
the new software. Only perform an automatic upgrade of system.xml files when you have
made a large number of customizations to these files.
Deploy the application on the production system.
When upgrading, you can export the entire content store to a deployment archive and then
import the deployment archive into IBM Cognos 8 after upgrading the software.
❑
Deploy the reports and models from the test system to the production system.
Installing IBM Cognos 8 Analytic Applications in a New Directory
If you have a previous version of IBM Cognos 8 Analytic Applications installed, you must upgrade
both the IBM Cognos 8 runtime components and Adaptive Applications Framework components
before you can use the new version. You can install IBM Cognos 8 Analytic Applications in the
same directory as an earlier version, or in a different directory. We recommend that you first install
the upgrade version of IBM Cognos 8 Analytic Applications in a new directory, so that you can
test the results before installing it in your existing environment (p. 37).
Note: The 64-bit version of IBM Cognos 8 is not compatible with IBM Cognos 8 Analytic Applications. If you want to use analytic applications with the IBM Cognos 8 BI Server 8.4, you must
install the 32-bit version. You must also ensure that the products are the same version. For more
information on upgrading IBM Cognos 8, see the IBM Cognos 8 Installation and Configuration
Guide.
Install IBM Cognos 8 Runtime Components in a New Directory
This section describes how to upgrade IBM Cognos 8 runtime components in a different directory
than an earlier version.
These instructions assume you are upgrading components that you originally installed using the
IBM Cognos 8 Runtime CD. If you are upgrading IBM Cognos 8 Analytic Applications within an
34
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
existing IBM Cognos 8 BI environment, you must ensure your version of IBM Cognos 8 BI is
compatible, and upgrade it if necessary.
Steps
1. Using your database tools, copy your existing content store database into a new content store
database.
For information on how to do this, see the documentation for your database.
2. Back up the following files to a secure location:
●
cogstartup.xml and coglocale.xml in the c8_location/configuration directory
●
server.xml in the c8_location/tomcat4.1.27/conf directory
●
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
c8_location/templates/ps
●
In IBM Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file cogstartup.xml.
Important: Because the exported cogstartup.xml file contains unencrypted passwords,
ensure that the location is secure.
●
Back up any manually edited files in the c8_location/configuration and other directories
to a secure location.
3. Install the IBM Cognos 8 runtime components in a new directory (p. 46).
4. Copy the .xml files from the secure backup location to the following directory:
●
Copy cogstartup.xml and coglocale.xml to c8_location/configuration.
●
Copy server.xml to c8_location/tomcat4.1.27/conf.
●
Copy system.xml to the same directory in the new location as it was in the earlier version,
if required.
For example,
c8_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
5. For files that you manually edited, edit the new versions of these files in the c8_location directory
and reapply the changes that you made to the original customized files.
Do not copy the earlier versions of the files to the c8_location directories. They may not be
compatible.
6. Configure new Web server aliases (p. 81).
Installation and Configuration Guide 35
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
7. In IBM Cognos Configuration, configure IBM Cognos 8 to point to the new content store,
configure new ports and URLs, use a different cookie path, and then save the configuration
(p. 87).
Ensure that the port numbers and service name for this installation are different from those
used for earlier versions so that there are no conflicts.
Ensure that security authentication settings are not changed. For example, the namespaces must
be the same for policies, users, roles, and groups for security authentication to work correctly.
8. Start the IBM Cognos 8 service.
IBM Cognos 8 automatically upgrades the new content store. System.xml files are upgraded,
if required, to a compatible version.
9. Open the Administration portal, and unregister the dispatchers that are used with earlier versions
of IBM Cognos 8 runtime components.
When you open the Administration portal in IBM Cognos 8, you may see the dispatchers that
are registered for both versions.
For more information, see the IBM Cognos 8 Administration and Security Guide.
10. When you are ready to uninstall the previous version of IBM Cognos 8 runtime components,
do the following:
●
Stop the IBM Cognos 8 service.
●
Uninstall IBM Cognos 8 runtime components from all computers (p. 63).
When you complete the upgrade tasks, the IBM Cognos 8 runtime components are fully configured
except for new properties and features.
To ensure the security and integrity of the IBM Cognos 8 runtime components, it is important to
protect the installation directory from unauthorized or inappropriate access.
Install IBM Cognos 8 Adaptive Applications Framework Components in a New
Directory
This section describes how to upgrade IBM Cognos 8 Adaptive Applications Framework components
in a different directory than an earlier version.
Steps
1. Install IBM Cognos 8 Adaptive Applications Framework in a new directory (p. 51).
2. For files that you manually edited, edit the new versions of these files in the apps_location directory and reapply the changes that you made to the original customized files.
Do not copy the earlier versions of the files to the apps_location directories. They may not be
compatible.
3. In IBM Cognos Configuration, configure new ports and URLs, use a different cookie path, and
then save the configuration (p. 87).
36
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
Ensure that the port numbers and service name for this installation are different from those
used for earlier versions so that there are no conflicts.
Ensure that security authentication settings are not changed. For example, the namespaces must
be the same for policies, users, roles, and groups for security authentication to work correctly.
4. Start the IBM Cognos 8 service.
5. Uninstall the previous version of IBM Cognos 8 Analytic Applications from all computers.
Installing IBM Cognos 8 Analytic Applications in the Same
Directory
If you have a previous version of IBM Cognos 8 Analytic Applications installed, you must upgrade
both the IBM Cognos 8 runtime components and Adaptive Applications Framework components
to the new version. We recommend that you install the upgrade version of IBM Cognos 8 Analytic
Applications in a new directory (p. 34), so that you can test the results before deploying it to your
production environment.
Note: The 64-bit version of IBM Cognos 8 is not compatible with IBM Cognos 8 Analytic Applications. If you want to use analytic applications with the IBM Cognos 8 BI Server 8.4, you must
install the 32-bit version. You must also ensure that the products are the same version. For more
information on upgrading IBM Cognos 8, see the IBM Cognos 8 Installation and Configuration
Guide.
Manually Configure Customization
If you manually edited any configuration files, the changes will be overwritten during the upgrade.
You must reapply the changes. Keep a record of any customizations to ensure that you can reapply
them after upgrading. Back up these files so that the original version can be restored if necessary.
If you have modified files other than those in the configuration folder, you should also back up
those files before upgrading.
The IBM Cognos 8 presentation service supports automatic upgrade of some system.xml files. If
you made many customization changes to system.xml files, you can use this automatic upgrade
feature instead of reapplying the changes manually after upgrading. The system.xml files are overwritten during the installation of the IBM Cognos 8 runtime components. You must back up the
customized versions of these files and then copy them to the directory after upgrading the IBM
Cognos 8 runtime components. The automatic upgrade is applied when you start the IBM Cognos 8
service.
The system.xml files for which automatic upgrade is supported are in the following directories:
●
c8_location/templates/ps
●
c8_location/templates/ps/portal
●
c8_location/templates/ps/qs
Installation and Configuration Guide 37
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
Note: We recommend that you manually reapply customizations to your files after installing the
new software. Only use automatic upgrade of system.xml files when you have made a large number
of customizations to these files.
Install IBM Cognos 8 Runtime Components in the Same Directory
This section describes how to upgrade IBM Cognos 8 runtime components in the same directory
as an earlier version.
These instructions assume you are upgrading components that you originally installed using the
IBM Cognos 8 Runtime CD. If you are upgrading IBM Cognos 8 Analytic Applications within an
existing IBM Cognos 8 BI environment, you must ensure your version of IBM Cognos 8 BI is
compatible, and upgrade it if necessary.
Steps
1. Using your database tools, back up the existing content store database.
For information on how to do this, see the documentation for your database.
2. Back up the following files to a secure location:
●
cogstartup.xml and coglocale.xml in the c8_location/configuration directory
●
server.xml in the c8_location/tomcat4.1.27/conf directory
●
system.xml in the appropriate directory, if required
Ensure that you note the directory path. For example,
c8_location/templates/ps
3. In IBM Cognos Configuration, export the configuration data to the same secure location.
To make the data usable for upgrading, name the file cogstartup.xml.
Important: Because the exported cogstartup.xml file contains unencrypted passwords, ensure
that the location is secure.
4. Back up any manually edited files in the c8_location/configuration and other directories to a
secure location.
5. Stop all IBM Cognos services.
6. Uninstall the IBM Cognos 8 runtime components from every computer (p. 63).
7. Install the newer version of the IBM Cognos 8 runtime components in the same directory of
every computer on which you installed the previous version of the IBM Cognos 8 runtime
components (p. 41).
8. Copy the .xml files from the secure backup location as follows:
38
●
Copy cogstartup.xml and coglocale.xml to c8_location/configuration.
●
Copy server.xml to c8_location/tomcat4.1.27/conf.
●
Copy system.xml to the appropriate directory, if required.
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
For example,
c8_location/templates/ps
If you are prompted to overwrite existing files, click Yes.
9. For files that you manually edited in earlier versions of the IBM Cognos 8 runtime components,
edit the new versions of these files in the c8_location directory and reapply the changes that
you made to the original customized files.
Do not copy the earlier versions of the files to the c8_location directories. They may not be
compatible.
10. In IBM Cognos Configuration, review the configuration, and then save it.
11. Start the IBM Cognos 8 service.
The IBM Cognos 8 runtime components automatically upgrades the content store. System.xml
files are upgraded, if required, to a compatible version.
Install IBM Cognos 8 Adaptive Applications Framework Components in the Same
Directory
This section describes how to upgrade IBM Cognos 8 Adaptive Applications Framework components
in the same directory as an earlier version.
Steps
1. Uninstall IBM Cognos 8 Analytic Applications from every IBM Cognos 8 Analytic Applications
computer (p. 66).
2. Install the new version of IBM Cognos 8 Adaptive Applications Framework in the same directory
that you used for IBM Cognos 8 Analytic Applications on every computer (p. 51).
3. For files that you manually edited in earlier versions of IBM Cognos 8 Analytic Applications,
edit the new versions of these files in the apps_location directory and reapply the changes that
you made to the original customized files.
Do not copy the earlier versions of the files to the apps_location directories. They may not be
compatible.
4. In IBM Cognos Configuration, review the configuration, and then save it.
5. Start the IBM Cognos 8 service.
Installation and Configuration Guide 39
Chapter 4: Upgrading IBM Cognos 8 Analytic Applications
40
Chapter 5: Installing and Uninstalling IBM Cognos
8 Analytic Applications
There are several tasks that you should perform before you install IBM Cognos 8 Analytic Applications. After these tasks are complete, you can install the IBM Cognos 8 Analytic Applications
components.
Use the following checklist to guide you through the installation tasks:
❑
Review the Readme
❑
Ensure that your computer meets the software and hardware requirements.
❑
Review the supported environments.
❑
Set up the database connectivity for the content store database.
❑
Install IBM Cognos 8 runtime or reporting components, if required.
❑
Install translated product documentation, if required
❑
Install IBM Cognos 8 service pack and IBM Cognos 8 updater.
❑
Install IBM Cognos Adaptive Applications Framework components.
❑
Install application content files for the ERP.
❑
Install SAP interface files, if required
After you install IBM Cognos 8 Analytic Applications, you must set up your environment.
Recommendation - Review the Readme Before You Install
Before you install your IBM Cognos product, it is important to be aware of all issues that may
affect your installation strategy.
There may be late-breaking issues that were not known when this installation guide was created.
We recommend that you review the Readme before you install your product. The Readme contains
late-breaking information about known issues as well as documentation updates and deprecation
notices. The Readme is available from the first page of the installation wizard or from the product
CD.
Verify System Requirements
Before you install IBM Cognos 8 Analytic Applications, ensure that your computer meets the software
and hardware requirements. The hardware requirements depend on your environment. You may
require additional resources, such as disk space.
Installation and Configuration Guide 41
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
The following table lists the minimum hardware and software requirements to run IBM Cognos 8
Analytic Applications.
Requirement
Specification
Operating system
Windows
UNIX
RAM
Minimum 2 GB
Operating system specifications
File descriptor limit set to 1024 on Solaris (recommended)
Disk space
Minimum 1 GB of free space on the drive that contains the temporary directory used by IBM Cognos components.
Web server
A Web server installed and started
JRE
Java Runtime Environment (JRE)
JRE is installed automatically with IBM Cognos 8 for Windows.
If you are using an application server, use the JRE that is installed
with it.
Database
One of the following databases available to store data:
●
Oracle
●
DB2
●
Microsoft SQL Server
●
Sybase
●
Cognos Content Database
If it is available for your application, Cognos Content Database can be installed and configured as the default content
store database.
One of the following databases available to store Adaptive
Warehouse data:
42
●
Oracle
●
DB2
●
Microsoft SQL Server
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Requirement
Specification
Web browser
For all Web browsers, enable the following:
●
cookies
●
JavaScript
For Microsoft Internet Explorer only, enable the following:
Other
●
Run ActiveX controls and plug-ins
●
Script ActiveX controls marked safe for scripting
●
Active scripting
●
Allow META REFRESH
For a terminal emulator to install IBM Cognos 8 Analytic
Applications for UNIX, the emulation set to VT220 equivalent
or better to ensure that the hot keys in the Installation wizard
work.
For Windows, Microsoft Data Access Component (MDAC) for
use with product samples.
If you want to email reports, the ability to use a mail server.
If you are installing IBM Cognos 8 Analytic Applications for use with SAP content application files,
you must also ensure that you have an SAP Runtime Client installed. IBM Cognos 8 Analytic
Applications uses the SAP Runtime Client to communicate with the SAP server environment. The
runtime client must be installed on the same computer where IBM Cognos 8 Adaptive Applications
Framework components are installed.
The SAP Runtime Client is typically installed during the SAP GUI client installation. Contact your
SAP system administrator to confirm that the SAP Runtime Client is installed.
Review Supported Environments
To review an up-to-date list of environments supported by IBM Cognos products, such as operating
systems, patches, browsers, Web servers, directory servers, database servers, and application servers,
visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.
html).
It is important to note that the Linux operating system is available in a number of distributions and
supports a number of hardware platforms. Ensure that the operating system and hardware combination you are using is a supported combination.
Installation and Configuration Guide 43
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Set Up Database Connectivity for the Content Store Database
If you are using a database other than Cognos Content Database as the content store, you may
have to install database client software, or JDBC drivers, or both, on each computer where you
install Content Manager. Doing this allows Content Manager to access the content store database.
Steps for DB2
1. If you are using type 2 JDBC connectivity, install the DB2 client software on the Content
Manager computers.
If you use type 4 JDBC connectivity for DB2, you are not required to install the DB2 client
software where Content Manager is installed. If you are using a DB2 database on z/OS for the
content store, you must use type 4 JDBC connectivity.
For more information about the differences between type 2 and type 4 drivers, see "JDBC
Driver Options for Using DB2 Database as a Content Store" (p. 80).
2. If you are using type 2 JDBC connectivity, and the content store is on a different computer than
Content Manager, configure a database alias to the content store.
On Windows, run the DB2 Client Configuration Assistant.
On UNIX or Linux, use the DB2 command line interface.
If the content store database and Content Manager are on the same computer, the content store
name automatically becomes the alias.
When you configure the Content Manager computers, ensure that they are all configured to
use the same content store.
3. On Windows, stop the DB2 services and the HTML Search Server.
4. Copy the following files from DB2_installation/sqllib/java directory to the c8_location/webapps/
p2pd/WEB-INF/lib directory.
●
the universal driver file, db2jcc.jar
●
the license file
for DB2 on Linux, UNIX, or Windows, db2jcc_license_cu.jar
for DB2 on z/OS, db2jcc_license_cisuz.jar
If you are connecting to DB2 on z/OS, use the driver version from Linux, UNIX, or Windows
version 9.1 fix pack 5 or version 9.5 fix pack 2.
Tip: To check the driver version, run the following command
java -cp path\db2jcc.jar com.ibm.db2.jcc.DB2Jjcc -version
5. On Windows, restart the DB2 services and the HTML Search Server.
6. On UNIX, if you are using type 2 JDBC connectivity, ensure that the 32-bit DB2 libraries are
in the library search path, which is usually the $DB2DIR/lib directory or the $DB2DIR/lib32
directory.
44
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
7. Repeat this entire procedure on the IBM Cognos 8 computers where Content Manager is
installed or where notification is sent to a DB2 database.
Steps for Oracle
1. On the computer where the Oracle client is installed, go to the ORACLE_HOME/jdbc/lib
directory.
2. Copy the appropriate JAR file to the c8_location/webapps/p2pd/WEB-INF/lib directory on
computers where Content Manager is installed and where notification is sent to an Oracle
database.
●
If you use Java 1.4, copy the ojdbc14.jar file
●
If you use Java 1.5, copy the ojdbc5.jar file
If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or
ojdbc5.jar file.
The driver is available from an Oracle client or server install, and it can also be downloaded
from the Oracle technology Web site.
Steps for Sybase
1. On the computer where Sybase is installed, go to the Sybase_location/jConnect-5_5/classes
directory.
2. Copy the jconn2.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every
computer where Content Manager is installed and where notification is sent to a Sybase database.
Recommendation - Install and Configure the Basic Installation
for Single Computers
There are many different installation and configuration options for customizing IBM Cognos 8
Analytic Applications so that it fits into your corporate infrastructure.
We recommend that you do a basic installation first. This involves installing one instance of each
of the required server components (gateway, Application Tier Components and Content Manager)
from the Cognos 8 Runtime or Reporting CD, installing the service pack and updater, and then
installing Adaptive Analytics Framework on Windows.
The sequence in which you configure computers is important. You must configure and then start
the services where you installed Content Manager before you configure Adaptive Analytics
Framework on Windows.
After you install the required components, but before you configure them, additional steps are
required so that IBM Cognos components can communicate with the software in your environment.
For example, you must configure a Web server to host online content.
After you set up your environment, we recommend that initially you do only the required configuration tasks so that IBM Cognos 8 Analytic Applications run in your environment.
Installation and Configuration Guide 45
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Later, you can add optional components and customize your configuration settings to better suit
your needs.
The simplest and quickest way to get IBM Cognos 8 Analytic Applications running in your environment is to ensure that a basic installation works before you customize the configuration for your
environment.
Install IBM Cognos 8 Runtime or Reporting Components
Only install the IBM Cognos 8 runtime or reporting components if you do not have a compatible
version of IBM Cognos 8 BI installed in your environment.
Note: The 64-bit version of IBM Cognos 8 is not compatible with IBM Cognos 8 Analytic Applications. If you want to use analytic applications with the IBM Cognos 8 BI Server 8.4, you must
install the 32-bit IBM Cognos 8 BI Server 8.4. You must also ensure that the products are the same
version.
Use the installation wizard provided on the IBM Cognos 8 Runtime CD 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.
For more information about installing IBM Cognos 8 BI Reporting, see the IBM Cognos 8 BI
Installation and Configuration Guide.
You must install the IBM Cognos 8 runtime or reporting components before you install IBM
Cognos 8 Adaptive Applications Framework components.
For UNIX, IBM Cognos 8 installations respect the file mode creation mask (umask) of the account
running the installation program. This affects only the installation directories, not the file permissions
within the directories. However, runtime generated files, such as logs, respect the mask. We
recommend that you specify umask 022 on the installation directory.
For Windows, ensure that you have administrator privileges for the Windows-based computer on
which you are installing. Also 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.
Steps for UNIX
1. Set the JAVA_HOME environment variable to point to the installation location of your Java
Runtime Environment (JRE).
An example of the installation location of a Java Runtime Environment is /directory/java/java_
version/jre.
2. On HP-UX, set the _M_ARENA_OPTS environment variable as follows:
_M_ARENA_OPTS 1:4
This increases the memory allocation for HP-UX to more closely match that of other UNIX
platforms.
3. Mount the CD for your IBM Cognos product using Rock Ridge file extensions.
Important: To mount the IBM Cognos CD on HP-UX, do the following:
46
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
●
Add the pfs_mount directory in your path.
For example,
PATH=/usr/sbin/:$PATH
export PATH
●
To start the required NFS daemons and run the daemons in the background, type bg
pfs_mountd and then type bg pfsd
●
To mount the drive, type
pfs_mount -t rrip <device><mount_dir> -o xlat=unix
For example,
pfs_mount /dev/dsk/c0t2d0 /cdrom -o xlat=unix
You can now install or copy files as a non-root user using an IBM Cognos CD from this
drive.
●
When the installation is complete, type pfs_umount /cdrom and kill the pfsd and pfs_mountd
daemons to unmount the CD.
4. Go to the operating system directory on the CD.
For example, for Solaris, go to the solaris directory.
5. Type the appropriate command:
●
If you are running X-Windows, type
./issetup
If you do not use XWindows, run an unattended installation "Set Up an Unattended Installation
" (p. 187).
6. Follow the directions in the installation wizard.
Install IBM Cognos 8 runtime or reporting components in a directory that contains only ASCII
characters in the path name. Some UNIX Web servers do not support non-ASCII characters in
directory names.
7. If Cognos Content Database is available for installation and you want to use it as the content
store, you must select it from the list of components on the Component Selection page of the
wizard.
8. Choose how to proceed in the Finish page of the installation wizard.
9. Append the c8_location/bin directory to the appropriate library path environment variable.
●
For Solaris, LD_LIBRARY_PATH
●
For AIX, LIBPATH
●
For HP-UX, SHLIB_PATH
Installation and Configuration Guide 47
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
To ensure the security and integrity of IBM Cognos 8 runtime or reporting components, it is
important to protect the installation directory from unauthorized or inappropriate access.
If you want users to see product documentation in a language other than English, you must install
the Supplementary Languages Documentation component in the location where you installed the
Gateway components. For more information, see "Install Translated Product Documentation" (p. 48).
You must also update your Java security framework (p. 80) before you can configure IBM Cognos 8
runtime or reporting components. Otherwise, you may receive the following error:
[Cryptography]
1. [ ERROR ] java.lang.NoClassDefFoundError: javax/net/ServerSocketFactory:
Steps for Windows
1. Insert the IBM Cognos 8 Runtime or IBM Cognos 8 BI Reporting CD.
The Welcome page of the installation wizard should appear. If the Welcome page does not
appear, in the win32 directory on the CD, double-click the issetup.exe file.
2. Follow the directions in the installation wizard to copy the required files to your computer.
3. Choose how to proceed in the Finish page of the installation wizard.
Install Translated Product Documentation
To access translated user documentation, you must install it from IBM Cognos 8 Supplementary
Languages Documentation.
English product documentation is installed when you install the IBM Cognos 8 gateway component.
The Installation and Configuration Guide, the Quick Start Installation and Configuration Guide,
and the Readme are the exceptions, and are available in all supported languages.
Before installing the Supplementary Languages Documentation, ensure that
●
IBM Cognos 8 is installed and configured correctly
●
adequate disk space is available to install supplementary languages documentation
You need at least 220 MB of disk space.
●
your software environment is supported
Steps
1. In the location where the Gateway component is installed, insert the IBM Supplementary Languages Documentation CD or go to the directory where the installation files were downloaded
and extracted.
On UNIX or Linux, mount the CD using Rock Ridge file extensions.
On Windows, the installation wizard starts automatically from the product disk.
48
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
2. To manually start the installation wizard, go to the operating system directory and do the following:
●
On Windows, if no Welcome page appears, double-click the issetup.exe file.
●
On UNIX or Linux, type
./issetup
Note: When you use the issetup command with XWindows, Japanese characters may be
corrupted.
3. Follow the instructions in the installation wizard to copy the required files to the same location
where you installed gateway components for IBM Cognos 8.
Install in a directory that contains only ASCII characters in the path name. Some Web servers
do not support non-ASCII characters in directory names.
The supplementary languages documentation components is selected by default.
4. Choose the option you want in the Finish page of the installation wizard.
Install the IBM Cognos 8 Service Pack and IBM Cognos 8
Updater
Before you install IBM Cognos 8 Analytic Applications, you must apply the latest versions of the
IBM Cognos 8 service pack and IBM Cognos 8 updater to all IBM Cognos 8 servers. You must
install the service pack before you install the updater.
IMPORTANT: The service pack and updater are not standalone installations. They must be installed
on computers that have IBM Cognos 8 BI Server version 8.4.27.78 or higher installed. To check
your version, open the component list file at install_location\cognos\c8\cmplst.txt and check the
line that starts with CRNSRVR_version=.
Before you install the service pack, we advise you to create a backup of the content store database.
As part of the installation process, the issetup program will prompt you to allow the service pack
to create a backup copy in the installation folder prior to copying any new files. In addition, you
should also backup any customized files from the current install.
Steps for Windows
1. In IBM Cognos Configuration, stop the IBM Cognos 8 service.
2. Back up the content store database.
3. If your IBM Cognos 8 environment is customized, back up the entire IBM Cognos 8 location.
4. Insert the CD for the Windows service pack.
5. Within the service pack folder on the CD, go to the win32 folder and double-click the issetup.exe
file.
Follow the directions in the installation wizard, installing in the same location as your existing
IBM Cognos 8 installation.
Installation and Configuration Guide 49
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
6. Insert the CD for the Windows updater.
7. Within the updater folder on the CD, go to the win32 folder and double-click the appropriate
issetup.exe file, and follow the directions in the installation wizard.
8. In IBM Cognos Configuration, save the configuration and then start the IBM Cognos 8 service.
9. If you have a distributed environment, repeat these steps for all remaining IBM Cognos 8 BI
servers.
Steps for UNIX
1. In IBM Cognos Configuration, stop the IBM Cognos 8 service.
2. Back up the content store database.
3. If your IBM Cognos 8 environment is customized, back up the entire IBM Cognos 8 location.
4. Mount the service pack CD that is appropriate for your operating system, using Rock Ridge
file extensions.
Important: To mount the IBM Cognos CD on HP-UX, do the following:
●
Add the pfs_mount directory in your path.
For example,
PATH=/usr/sbin/:$PATH
export PATH
●
To start the required NFS daemons and run the daemons in the background, type bg
pfs_mountd and then type bg pfsd
●
To mount the drive, type
pfs_mount -t rrip <device><mount_dir> -o xlat=unix
For example,
pfs_mount /dev/dsk/c0t2d0 /cdrom -o xlat=unix
You can now install or copy files as a non-root user using an IBM Cognos CD from this
drive.
●
When the installation is complete, type pfs_umount /cdrom and kill the pfsd and pfs_mountd
daemons to unmount the CD.
5. To install the service pack, type the appropriate command:
●
If you use XWindows, type ./issetup
If you do not use XWindows, run an unattended installation (p. 187).
Follow the directions in the installation wizard to install to the same location as your existing
IBM Cognos 8 installation.
6. Mount the updater CD that is appropriate for your operating system, using Rock Ridge file
extensions.
50
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Important: To mount the CD on HP-UX, follow the bulleted instructions in step 4.
7. To install the updater, type the appropriate command:
●
If you use XWindows, type ./issetup
If you do not use XWindows, run an unattended installation (p. 187).
Follow the directions in the installation wizard to install to the same location as your existing
IBM Cognos 8 installation.
8. In IBM Cognos Configuration, start the IBM Cognos 8 service.
9. If you have a distributed environment, repeat these steps for all remaining IBM Cognos 8 BI
servers.
Install IBM Cognos 8 Adaptive Applications Framework Components
The type of environment that you are setting up determines whether to use the IBM Cognos 8
Adaptive Applications Framework CD or the IBM Cognos 8 Adaptive Applications Framework
Runtime CD. For more information, see "Distribution Options for IBM Cognos 8 Analytic
Applications" (p. 21).
Use the installation wizard, provided on the installation CDs, 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.
For UNIX, you can install components using either a character-based interface or a graphical user
interface. To run graphical-mode installation, the console attached to your UNIX-based computer
must support a Java-based graphical user interface.
For UNIX, IBM Cognos 8 Adaptive Applications Framework 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, runtime generated files, such
as logs, respect the mask. We recommend umask 022 on the installation directory.
For Windows, ensure that you have administrator privileges for the computer on which you are
installing. Also 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.
Steps for UNIX
1. Set the JAVA_HOME environment variable to point to the installation location of your Java
Runtime Environment (JRE).
An example of the installation location of a Java Runtime Environment is /directory/java/java_
version/jre.
2. On HP-UX, set the _M_ARENA_OPTS environment variable as follows:
_M_ARENA_OPTS 1:4
Installation and Configuration Guide 51
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
This increases the memory allocation for HP-UX to match more closely that of other UNIX
platforms.
3. Mount the CD for your IBM Cognos product using Rock Ridge file extensions.
Important: To mount the IBM Cognos CD on HP-UX, do the following:
●
Add the pfs_mount directory in your path.
For example,
PATH=/usr/sbin/:$PATH
export PATH
●
To start the required NFS daemons and run the daemons in the background, type bg
pfs_mountd and then type bg pfsd
●
To mount the drive, type
pfs_mount -t rrip <device><mount_dir> -o xlat=unix
For example,
pfs_mount /dev/dsk/c0t2d0 /cdrom -o xlat=unix
You can now install or copy files as a non-root user using an IBM Cognos CD from this
drive.
●
When the installation is complete, type pfs_umount /cdrom and kill the pfsd and pfs_mountd
daemons to unmount the CD.
4. Go to the operating system directory on the CD.
For example, for Solaris, go to the solaris directory.
5. Type the appropriate command:
●
If you are running X-Windows, type
./issetup
If you do not use XWindows, run an unattended installation (p. 187).
6. Follow the directions in the installation wizard.
Install IBM Cognos 8 Adaptive Applications Framework components in a directory that contains
only ASCII characters in the path name. Some UNIX Web servers do not support non-ASCII
characters in directory names.
7. Choose how to proceed in the Finish page of the installation wizard:
●
If you want to configure IBM Cognos 8 Adaptive Applications Framework components
immediately, click Start IBM Cognos Configuration.
●
If you want to see the latest information about IBM Cognos 8 Adaptive Applications
Framework components, select View the Readme, and then select Finish.
Tip: For character-mode installations for UNIX, close the readme text file by pressing Ctrl
+ C or q.
52
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
●
If the console attached to your computer does not support a Java-based graphical user
interface or if you want to configure IBM Cognos 8 Adaptive Applications Framework
components later, click Finish.
You can configure IBM Cognos 8 Adaptive Applications Framework components later
using Cognos Configuration by starting cogconfig.sh in the apps_location/bin directory,
or editing cogstartup.xml in apps_location/configuration directory.
8. Append the apps_location/bin directory to the appropriate library path environment variable.
●
For Solaris, LD_LIBRARY_PATH
●
For AIX, LIBPATH
●
For HP-UX, SHLIB_PATH
To ensure the security and integrity of IBM Cognos 8 Adaptive Applications Framework components,
it is important to protect the installation directory from unauthorized or inappropriate access.
You must also update your Java security framework (p. 80) before you can configure IBM Cognos 8
Adaptive Applications Framework components. Otherwise, you may receive the following error:
[Cryptography]
1. [ ERROR ] java.lang.NoClassDefFoundError: javax/net/ServerSocketFactory:
Steps for Windows
1. Insert the appropriate CD for the type of installation you require.
The Welcome page of the installation wizard should appear. If the Welcome page does not
appear, go to the win32 directory on the CD and double-click the issetup.exe file.
2. Follow the directions in the installation wizard to copy the required files to your computer.
3. Choose how to proceed in the Finish page of the installation wizard:
●
If you want to configure IBM Cognos 8 Adaptive Applications Framework components
immediately, click Start IBM Cognos Configuration.
●
If you want to see the latest information about IBM Cognos 8 Adaptive Applications
Framework components, click View the Readme.
4. Click Finish.
Use the Windows Start menu to start IBM Cognos Configuration from the shortcut folder.
Installation and Configuration Guide 53
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Install Application Content Files for the ERP
Use the installation wizard, provided on the application content CD, to select the version-specific
content files you want to install and the location on your computer where you want to install the
files for your ERP.
Steps
1. Insert the application content CD.
The Welcome page of the installation wizard should appear. If the Welcome page does not
appear, go to the win32 directory on the CD and double-click the issetup.exe file.
2. Follow the directions in the installation wizard to copy the required files to your computer.
3. In the Finish page of the installation wizard, if you want to see the latest information about
the application content files, click View the Readme.
4. Click Finish.
Install Translated Product Documentation
To access translated user documentation, you must install it from IBM Cognos 8 Supplementary
Languages Documentation.
English product documentation is installed when you install the IBM Cognos 8 gateway component.
The Installation and Configuration Guide, the Quick Start Installation and Configuration Guide,
and the Readme are the exceptions, and are available in all supported languages.
Before installing the Supplementary Languages Documentation, ensure that
●
IBM Cognos 8 is installed
●
adequate disk space is available to install supplementary languages documentation
You need at least 220 MB of disk space.
●
your software environment is supported
Steps
1. In the location where the Gateway component is installed, insert the IBM Supplementary Languages Documentation CD or go to the directory where the installation files were downloaded
and extracted.
On UNIX or Linux, mount the CD using Rock Ridge file extensions.
On Windows, the installation wizard starts automatically from the product disk.
2. To manually start the installation wizard, go to the operating system directory and do the following:
54
●
On Windows, if no Welcome page appears, double-click the issetup.exe file.
●
On UNIX or Linux, type
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
./issetup
Note: When you use the issetup command with XWindows, Japanese characters may be
corrupted.
3. Follow the instructions in the installation wizard to copy the required files to the same location
where you installed gateway components for IBM Cognos 8.
Install in a directory that contains only ASCII characters in the path name. Some Web servers
do not support non-ASCII characters in directory names.
The supplementary languages documentation components is selected by default.
4. Choose the option you want in the Finish page of the installation wizard.
Install and Configure Additional Language Fonts
To add support for the Japanese Yen or Korean Won character, you must install additional fonts
from IBM Cognos 8 Supplementary Languages Documentation.
The Unicode code point “U+005C” is officially assigned to the backslash. However, in Japan and
Korea, that code point is historically assigned to their currency symbols and many people still prefer
to see a yen or won sign in certain parts of software, for example in file paths. To accommodate
this, you can install the “Andale WT J” and “Andale WT K” fonts.
Before installing the additional fonts, ensure that
●
IBM Cognos 8 is installed and configured correctly
●
adequate disk space is available to install additional fonts
You need at least 220 MB of disk space.
●
your software environment is supported
Steps
1. In the location where Application Tier Components are installed, insert the IBM Cognos 8
Supplementary Languages Documentation CD.
On UNIX or Linux, mount the CD using Rock Ridge file extensions.
2. Go to the directory on the CD that is appropriate for your operating system.
3. Start the installation wizard by typing the following command:
●
On Windows,
issetup
●
On UNIX or Linux,
./issetup
Note: When you use the issetup command with XWindows, Japanese characters may be
corrupted.
Installation and Configuration Guide 55
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
4. Follow the instructions in the installation wizard to copy the required files to the same location
where you installed Application Tier Components.
Install in a directory that contains only ASCII characters in the path name. Some Web servers
do not support non-ASCII characters in directory names.
When you are prompted to select components, clear IBM Cognos 8 Business Intelligence Supplementary Languages Documentation, expand Additional Language Fonts, and then select the
font.
These fonts are copied to the c8_location/bin/fonts directory. This font location is defined in
the Physical fonts location property value in IBM Cognos Configuration under Environment.
If you move the fonts to another location, ensure that the new location is added to the Physical
fonts location property value.
Fonts used to display data in a report are selected using a matching process between the fonts
requested when the report is designed and the fonts that are available when the report is
rendered. For PDF output and charts, this process occurs on the server where all fonts on the
server that generates the report can be used.
5. Choose the option you want in the Finish page of the installation wizard.
After you install the additional fonts, you must configure support for them. For more information,
see "Configure Support for Japanese Yen and Korean Won Characters" (p. 56).
Configure Support for Japanese Yen and Korean Won Characters
For Japanese and Korean currency characters to display correctly, you must define the additional
fonts in the global style sheet.
Before you configure these fonts, you must install them from the IBM Cognos 8 Supplementary
Languages Documentation CD.
Steps to Configure the Fonts for Yen and Won Characters
1. Open the GlobalReportStyles.css style sheet in a text editor.
The GlobalReportStyles.css style sheet is located in the c8_location\bin directory.
2. Enable one of the following sections and modify it as shown below:
●
/* For Japanese: */
.pg,
.pp
{
font-family: 'MS UI Gothic', 'Andale WT J' , Tahoma, arial, geneva,
helvetica, sans-serif;
}
●
/* For Korean: */
.pg,
.pp
56
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
{
font-family: Gulim, 'Andale WT K' , Tahoma, arial, geneva, helvetica,
sans-serif;
}
The PDF generator uses the first available font on the server and includes all the characters in
the string to be displayed. If you prefer to use other fonts on your server, you can insert them
into the list.
3. Save the GlobalReportStyles.css file.
4. Restart the IBM Cognos 8 server.
Any changes that you make to the style sheet are overwritten if you upgrade IBM Cognos 8. You
must repeat this procedure following an upgrade.
Install SAP Interface Files
If you install IBM Cognos 8 Analytic Applications with SAP application content files, you must
also perform the following tasks:
❑
Install the SAP Gateway functions.
❑
Install the SAP content interface files.
❑
Apply the SAP Gateway functions and content interface files.
❑
Install the IBM Cognos compression utility.
❑
Set access permissions for IBM Cognos products.
Install the SAP Gateway Functions
IBM Cognos 8 Analytic Applications uses Advanced Business Applications Programming (ABAP)
function modules that interface with the SAP environment. An SAP system administrator should
install the gateway functions on each SAP server in your environment.
The installation provides ABAP function modules for different version of SAP. By default, the files
for these modules are located in application_content_location\transports directory. A separate
directory is created for each version of SAP that is supported.
Note: If you are using SAP ERP Central Components (ECC5 or ECC6), you must use the ABAP
function modules in the application_content_location\transports\v47 directory.
If your SAP servers are running on UNIX-based computers, you must copy the gateway functions
from the Windows-based computer where you installed the application content files to the UNIXbased computer where SAP is running.
Installation and Configuration Guide 57
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Even if you install IBM Cognos 8 Analytic Applications on different computers, you only need to
install the gateway functions on each SAP server once.
Steps for SAP Servers for Windows
1. Copy the file named Knn.ext from the application_content_location\transports\SAP_version
directory to the SAP_home\trans\cofiles directory on the SAP server.
2. Copy the files named Rnn.ext from the application_content_location\transports\SAP_version
directory to the SAP_home\trans\data directory on the SAP server.
You can now apply the functions.
Steps for SAP Servers for UNIX
1. Use file transfer protocol (FTP) in ASCII mode to copy the files named Knn.ext from the
application_content_location\transports\SAP_version directory to the SAP_home/trans/cofiles
directory on the SAP server.
2. Use FTP in binary (bin) mode to copy the files named Rnn.ext from the application_content_
location\transports\SAP_version directory to the SAP_home/trans/data directory on the SAP
server.
You can now apply the functions.
Install the SAP Content Interface Files
An SAP system administrator should install the required content-specific SAP interface files on each
SAP server in your environment.
By default, the interface files are located in the application_content_location\applicationtransports\
sap \SAP_version\workforce_performance directory.
If your SAP servers are running for UNIX-based computers, you must copy the interface files from
the Windows-based computer where you installed the application content files to the UNIX-based
computer where SAP is running.
Even if you install IBM Cognos 8 Analytic Applications on different computers, you only need to
install the gateway functions on each SAP server once.
Steps for SAP Servers for Windows
1. In the application_content_location\applicationtransports\sap \SAP_version\workforce_
performance directory where you installed the application content files, run TransportWFP.exe.
The files are extracted to the specified directory.
2. Copy the file named Knn.ext from the directory where you extracted the TransportWFP files
to the SAP_home\trans\cofiles directory on the SAP server.
3. Copy the files named Rnn.ext from the directory where you extracted the TransportWFP files
to the SAP_home\trans\data directory on the SAP server.
58
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
You can now apply the interface files.
Steps for SAP Servers for UNIX
1. In the application_content_location/applicationtransports/sap /SAP_version/workforce_
performance directory where you installed the application content files, run TransportWFP.exe.
The files are extracted to the specified directory.
2. Use file transfer protocol (FTP) in ASCII mode to copy the files named Knn.ext from the directory
where you extracted the TransportWFP files to the SAP_home/trans/cofiles directory on the
SAP server.
3. Use FTP in binary (bin) mode to copy the files named Rnn.ext from the directory where you
extracted the TransportWFP files to the SAP_home/trans/data directory on the SAP server.
You can now apply the functions.
Apply the SAP Gateway Functions and Content Interface Files
After you install the SAP gateway functions and content-specific SAP interface files, you must apply
them using SAP GUI. An SAP system administrator should apply the functions and interface files.
Even if you install IBM Cognos 8 Analytic Applications on different computers, you only need to
install the gateway functions and interface files on each SAP server once.
Steps
1. In the SAP GUI, start an STMS transaction.
2. Click Imports, and then double-click the queue name.
3. If a message appears prompting you to add to the import queue, click Yes and, if required, type
your password.
4. In the queue, select the transport request name that matches the name in the TRnames.txt file.
5. From the Request menu, click Import and type the target client number.
6. Click Start Import, and then click Yes. If required, type the password.
7. If you want to check the result, click Logs.
You can now install the IBM Cognos Compression Utility.
Install the IBM Cognos Compression Utility
The IBM Cognos Compression Utility is required for data compression on an SAP server. The corresponding decompression function is included in the SAP gateway functions and interface files.
For UNIX SAP servers for UNIX, you must copy the compression utility files from the installation
CD.
Installation and Configuration Guide 59
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Even if you install IBM Cognos 8 Analytic Applications on different computers, you only need to
install the IBM Cognos compression utility on each SAP server once.
Steps for SAP Servers for Windows
1. Copy the file named zlib.dll from the apps_location\bin directory to the DIR_EXECUTABLE
directory on all Windows SAP servers.
The DIR_EXECUTABLE directory is usually defined as SAP_instance\SYS\exe\run.
2. Copy the file named udacompr.exe from the application_content_location\bin directory to the
DIR_EXECUTABLE directory on all Windows SAP servers.
Steps for SAP Servers for UNIX
1. Using binary transfer mode, FTP the files from the zipfiles/operating_system directory on the
application content files CD to the DIR_EXECUTABLE directory on all UNIX SAP Servers.
The DIR_EXECUTABLE directory is usually defined as SAP_instance/SYS/exe/run.
2. Set execute privileges on each of the files.
You can now set the access permissions for the gateway functions and content interface files.
Set Access Permissions for the Gateway Functions and Content Interface Files
For the SAP gateway functions and content interface files to be able to access SAP data, the user
accounts that connect to SAP must have specific permissions.
Steps
1. Ensure that the SAP user accounts that use the SAP connector have the following privileges:
●
S_RFC, for the authorization check for RFC access
●
S_DATASET, for the authorization check for file access
●
S_BTCH_JOB, for background processing
●
S_PROGRAM, for ABAP program flow checking
●
S_TABU_DIS, for access to data in the tables
IBM Cognos 8 Analytic Applications uses SAP security to determine access for the user
profile. Ensure that your system administrator grants S_TABU_DIS privileges to the user
profile used to access SAP. If these privileges are not granted, you cannot access the data
in the tables.
Incorrect privileges may result in run-time errors, such as the following:
1 . ERROR DS-DBMS-E400: UDA driver reported the following on connection
'ALIAS_01F1A4DC': DMS-E-SAP_CONNECTION_FAILURE, Connection to SAP failed: User
UDAQC4 has no RFC authorization for function group Z70F .
2. You must also ensure that the SAP accounts have the following additional permissions to import
data:
60
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Authorization
Object
Field
Value
S_RFC
Activity
16 - Execute
Name of RFC to be protec- RFC1, SDTX, SUSO, SU_USER,
ted
SYST, ZCOGNOS_80A,
ZWFP_COGNOS
S_DATASET
Type of RFC object to be
protected
FUGR - Function group
Activity
06 - Delete
33 - Read
34 - Write
A7 - Write with filter
Physical file name
*
Program Name with Search *
Help
S_BTCH_JOB
S_PROGRAM
S_TABU_DIS
Job operations
RELE Release Jobs (Released Automatically)
Summary of jobs for a
group
''
User action ABAP/4
program
SUBMIT Execute ABAP program
Authorization group
ABAP/4 program
GBSE
Activity
03 - Display
Authorization Group
&NC&, FA, FB00, FB01, FB12,
FB21, FB32, FC, GC, KA, KCOR,
KEC, PA, PC, PC01, PS, SC, SDIC,
SS, VC
Installation and Configuration Guide 61
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Authorization
Object
Field
Value
P_ORGIN
Authorization Level
R
Infotype
0000, 0001, 0007, 0008, 0014,
0015, 0302
Personnel Area
*
Employee Group
*
Employee Subgroup
*
Subtype
*
Organizational Key
*
Authorization Level
R
P_PCLX
Area identifier for cluster in *
RELID
Tips:
●
Before importing new tables from SAP, check that your administrator has added the
authorization group to the authorization object S_TABU_DIS in table TDDAT.
●
You can use the asterisk (*) to represent all values, when it appears alone, or partial values,
when used anywhere in a string.
Default Settings for IBM Cognos 8 Analytic Applications
The following table lists the default ports and URI settings for IBM Cognos 8 Analytic Applications.
After installation, you can use the configuration tool to change the settings (p. 99).
Setting
Default
Description
Content Manager URI
http://localhost:9300/p2pd/
servlet
The URI to Content Manager
Gateway URI
http://localhost:80/cognos8/cgi- The URI to the gateway
bin/cognos.cgi
Dispatcher URI
http://localhost:9300/p2pd/
servlet/ dispatch
(Internal, External)
62
The URI to the dispatcher
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Setting
Default
Description
Dispatcher URI for external
applications
http://localhost:9300/p2pd/
servlet/ dispatch
The URI to the dispatcher
Dispatcher URIs for Gateway
http://localhost:9300/p2pd/
servlet/ dispatch/ext
The URI to the primary dispatcher used by the gateway
Log server port
9362
The port used by the local log
server
The following table lists the default settings used by IBM Cognos 8 Analytic Applications for
Tomcat. The non-SSL connector is automatically updated in the server.xml file when you use IBM
Cognos Configuration to change the dispatcher port (p. 99). You can directly update the shutdown
port using IBM Cognos Configuration.
Setting
Port
Description
Non-SSL Coyote HTTP/1.1
Connector
9300
The port Tomcat uses to pass requests from the
Web server to IBM Cognos 8
Shutdown port
9399
The port Tomcat uses to listen for a shutdown
command
Uninstall IBM Cognos 8 Runtime or Reporting Components
It is important to use uninstallation programs to completely remove all files and modifications to
system files.
If you are upgrading from an older version of Performance Applications to IBM Cognos 8 Analytic
Applications, follow the uninstallation instructions in the documentation for the older version of
Performance Applications.
Uninstall IBM Cognos 8 Runtime or Reporting Components for UNIX
If you no longer require IBM Cognos 8 Analytic Applications, uninstall IBM Cognos 8 runtime or
reporting components, if you used the IBM Cognos 8 Runtime CD or IBM Cognos 8 BI Reporting
to install these components.
You must repeat the uninstallation process on each computer that contains IBM Cognos 8 runtime
or reporting components.
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 IBM Cognos process by typing the following
command:
Installation and Configuration Guide 63
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
ps -ef | grep cogbootstrapservice
2. Stop the IBM Cognos process:
●
If you are running X-Windows, start IBM Cognos Configuration, and from the Actions
menu, click Stop.
●
If you are not running X-Windows, type:
kill -TERM pid
3. To uninstall, go to the c8_location/uninstall directory and type the appropriate command:
●
If you are running X-Windows, type
./uninst -u
●
If you are not running X-Windows, type
If you do not use XWindows, do an unattended uninstallation (p. 191).
4. Follow the prompts to complete the uninstallation.
Uninstalling does not remove any files that have changed since the installation, such as configuration
and user data files. The installation location remains on your computer, and you retain these files
until you delete them manually.
Important: Do not delete the configuration and data files if you are upgrading to a new version of
IBM Cognos 8 Analytic Applications and you want to use the configuration data with the new
version.
Uninstall IBM Cognos 8 Runtime or Reporting Components for Windows
If you no longer require IBM Cognos 8 Analytic Applications for Windows, uninstall IBM Cognos 8
runtime or reporting components, if you used the IBM Cognos 8 Runtime CD or IBM Cognos 8
BI Reporting to install these components.
You must repeat the uninstallation process on each computer that contains IBM Cognos 8 runtime
or reporting components.
We recommend that you close all programs before you uninstall. Otherwise, some files may not be
removed.
Steps
1. From the Start menu, click Programs, IBM Cognos 8, Uninstall IBM Cognos 8.
The Uninstall wizard appears.
Tip: IBM Cognos 8 is the default name of the Program Folder that is created during the
installation. If you chose another name, go to that folder to find the program.
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.
64
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
3. Delete all temporary Internet files.
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.
Important: Do not delete the configuration and data files if you are upgrading to a new version of
IBM Cognos 8 Analytic Applications and you want to use the configuration data with the new
version.
Uninstall IBM Cognos Content Database
If you want to uninstall only Cognos Content Database and leave other IBM Cognos 8 components
on your computer, you must use the following procedure. After you uninstall Cognos Content
Database you must configure a new content store before you can restart the IBM Cognos 8 service.
Depending on your application, Cognos Content Database may not be available.
Steps
1. On the computer where you installed Cognos Content Database, go to the c8_location\bin
directory, and type the following command:
●
On Windows, type
derby.bat uninstall
This command removes the Cognos Content Database service.
●
On UNIX, type
derby.sh stop
This command stops the Cognos Content Database service.
2. In the c8_location directory, delete the derby10.1.2.1 directory.
3. In the c8_location\bin directory, delete the following files:
●
On Windows, derby.bat
●
On UNIX, derby.sh and derbyenv.sh
4. On Windows, in the c8_location\logs directory, delete the derby.service file.
5. In the c8_location directory, open the cmplst.txt file in a text editor.
6. Remove lines containing Cognos Content Database values. The lines contain CCD and
CMDERBY. For example:
C8BISRVRCCD_version=
C8BISRVRCCD_name=
CCD_version=
CCD_name=
Installation and Configuration Guide 65
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
CMDERBY_version=
CMDERBY_name=
Tip: You can also comment the lines out by inserting # at the start of each line.
7. Save the file.
8. Start IBM Cognos Configuration.
9. Under Data Access, Content Manager, do the following:
●
Delete the Cognos Content database.
●
Configure a new database resource to point to a new content store.
10. Restart IBM Cognos 8.
Uninstall IBM Cognos 8 Adaptive Applications Framework
Components
It is important to use uninstallation programs to completely remove all files and modifications to
system files.
If you are upgrading from an older version of Performance Applications to IBM Cognos 8 Analytic
Applications, follow the uninstallation instructions in the documentation for the older version of
Performance Applications.
Uninstall IBM Cognos 8 Adaptive Warehouse Runtime for UNIX
If you no longer require Adaptive Warehouse Runtime for UNIX, uninstall the component.
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 IBM Cognos process by typing the following
command:
ps -ef | grep cogbootstrapservice
2. Stop the IBM Cognos process:
●
If you are running X-Windows, start IBM Cognos Configuration, and from the Actions
menu, click Stop.
●
If you are not running X-Windows, type:
kill -TERM pid
3. To uninstall Adaptive Warehouse Runtime, go to the apps_location/uninstall directory and
type the appropriate command:
●
If you are running X-Windows, type
./uninst -u
66
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
●
If you are not running X-Windows, type
If you do not use XWindows, do an unattended uninstallation (p. 191).
4. Follow the prompts to complete the uninstallation.
5. Delete all temporary Internet files.
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 manually.
Important: Do not delete the configuration and data files if you are upgrading to a new version of
IBM Cognos 8 Analytic Applications and you want to use the configuration data with the new
version.
Uninstall IBM Cognos 8 Adaptive Applications Framework for Windows
If you no longer require Adaptive Warehouse and Adaptive Analytics for Windows, uninstall the
components.
If you installed more than one component in the same location, the uninstall wizard lets you choose
the packages to uninstall. You must repeat the uninstallation process on each computer that contains
IBM Cognos 8 Adaptive Applications Framework components.
It is not necessary to back up the configuration and data files. These files are preserved during the
uninstallation.
We recommend that you close all programs before you uninstall IBM Cognos 8 Adaptive Applications
Framework. Otherwise, some files may not be removed.
Steps
1. From the Start menu, click Programs, IBM Cognos 8 Analytic Applications, Uninstall Analytic
Application Components, Uninstall Analytic Application Components.
The Uninstall wizard appears.
Tip: IBM Cognos 8 Analytic Applications is the default name of the Program Folder that is
created during the installation. If you chose another name, go to that folder to find the program.
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.
3. Delete all temporary Internet files.
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.
Installation and Configuration Guide 67
Chapter 5: Installing and Uninstalling IBM Cognos 8 Analytic Applications
Important: Do not delete the configuration and data files if you are upgrading to a new version of
IBM Cognos 8 Analytic Applications and you want to use the configuration data with the new
version.
Uninstall Application Content Files
If you no longer require the application content files for IBM Cognos 8 Analytic Applications, you
can uninstall them.
If you installed more than one component in the same location, the uninstall wizard lets you choose
the packages to uninstall. You must repeat the uninstallation process on each computer that contains
application content files.
Important: Do not delete the content files if you are upgrading to a new version of IBM Cognos 8
Analytic Applications and you want to use the data with the new version.
We recommend that you close all programs before you uninstall the application content files.
Otherwise, some files may not be removed.
Steps
1. From the Start menu, click Programs, IBM Cognos 8 Analytic Applications, Uninstall Analytic
Application Components, Uninstall Analytic Application Components.
The Uninstall wizard appears.
Tip: IBM Cognos 8 Analytic Applications is the default name of the Program Folder that is
created during the installation. If you chose another name, go to that folder to find the program.
2. Follow the instructions to uninstall the files.
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.
3. Delete all temporary Internet files.
For more information, see your Web browser documentation.
68
Chapter 6: Setting Up the Environment
After you install IBM Cognos 8 Analytic Applications, you must set up your environment.
Use the following checklist to guide you through the setup process:
❑
Create a database for the content store.
❑
Set up the database client for the content store.
❑
Create tablespaces for DB2 on z/OS
❑
Set up environment variables to run scripts.
❑
Update the Java environment, if required.
❑
Configure the Web server.
❑
Configure the Web browser.
❑
Set up the data source environment.
After you complete these tasks, you must configure the IBM Cognos components (p. 87) to work
in your environment.
Guidelines for Creating the Content Store
The content store is a database that Content Manager uses to store global configuration data, global
settings (such as the language and currency formats shown in the user interface), connections to
data sources, and product-specific content.
Design models and log files are not stored in the content store.
You must create the content store before you can use IBM Cognos 8.
Database Properties
You must create the database using one of the databases listed in the following table:
Database
Character Encoding
Protocol
DB2
UTF-8
TCP/IP
Oracle
AL32UTF8 or AL32UTF16
TCP/IP
SQL Server
UTF-8 or UTF-16
TCP/IP
Sybase
UTF-8
TCP/IP
Cognos Content Database
pre configured
pre configured
Installation and Configuration Guide 69
Chapter 6: Setting Up the Environment
Cognos Content Database
If you plan to use the Cognos Content Database as your content store, you must select it during
the installation. Upon completion of the installation, a database is created and configured.
Note: Depending on your application, Cognos Content Database may not be available.
Collation Sequence
Note that IBM Cognos 8 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. For more information about collation and collation
sequences, see the database documentation.
Suggested Settings for Creating the Content Store in DB2 on Linux, Windows
and UNIX
The database you create for the content store must contain the recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
32-bit Library Files for DB2
IBM Cognos 8 requires 32-bit library files when running in a 32-bit application server. If you have
installed DB2 version 9.5, the 64-bit library files may be set in your environment variables. You
must change the library files used or change the order in which the library files are listed so that
IBM Cognos 8 can find the 32-bit library files. The 32-bit library files must be listed first for IBM
Cognos 8.
Guidelines for Creating the Content Store in DB2 on Linux, UNIX, or Windows
If you create your own content store, use the following checklist to help you set up the content store
on DB2.
❑
70
If you use type 2 UDBC connectivity, set the appropriate environment variables for DB2, which
are as follows.
Environment variable
Description
DB2DIR
The top level directory that contains the database client
software or the entire database installation.
Chapter 6: Setting Up the Environment
Environment variable
Description
LD_LIBRARY_PATH
The load library path.You must add the driver location.
For example, LD_LIBRARY_PATH= $DB2_location/sqllib/
lib32: $LD_LIBRARY_PATH
Examples:
For Solaris and Linux:
LD_LIBRARY_PATH= $DB2DIR/lib:
$LD_LIBRARY_PATH
For AIX:
LIBPATH=$DB2DIR/lib:$LIBPATH
For HP-UX:
SHLIB_PATH=$DB2DIR/lib:$SHLIB_PATH
DB2INSTANCE
The default database server connection.
DB2CODEPAGE
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.
❑
Use UTF-8 as the code set value when you create the database.
To check if your database has the correct code set, using the command line interface, type the
following at the command prompt:
db2 get database configuration for database_name
The code set value should be UTF-8 and the code page value should be 1208.
❑
Ensure that you set the following configuration parameters.
Property
Setting
Application heap size
1024 KB
(applheapsz)
Lock timeout (locktimeout)
240 seconds
Do not set this to an infinite timeout value.
If the application heap size value is too small, out of memory errors may occur when there are
many users.
❑
Create a buffer pool with a page size of 32 KB, and a second one with a page size of 4 KB.
Installation and Configuration Guide 71
Chapter 6: Setting Up the Environment
❑
Create a system temporary tablespace using the 32 KB buffer pool you created in the previous
step.
❑
Create a user temporary tablespace using the 4 KB buffer pool you created.
Global temporary tables will be created in the user temporary tablespace.
❑
Create a regular user tablespace using the 4 KB buffer pool you created.
If you are also creating a logging database, create an additional regular user tablespace with a
page size of 8 KB.
❑
Grant the following database privileges for the user account IBM Cognos 8 will use to access
the database:
●
connect to database
●
create tables
●
create schemas implicitly
Tip: If you want to host more than one content store on your DB2 instance and you will use
both at the same time, use a different user account for each content store to ensure that each
IBM Cognos 8 instance is fully isolated from the other.
❑
Ensure that the user account has use privileges for the user temporary tablespace and other
appropriate tablespaces associated with the database.
❑
Create a schema for the user account IBM Cognos 8 will use to access the database, and ensure
the user has create, drop, and alter permissions for the schema.
❑
We recommend that you create a profile that sources the sqllib/db2profile from the DB2 user’s
home directory. For example, the content of your .profile will be similar to the following:
if
[ -f /home/db2user/sqllib/db2profile ]; then
./home/db2user/sqllib/db2profile
fi
❑
Your database administrator must back up IBM Cognos 8 databases regularly because they
contain the IBM Cognos data. To ensure the security and integrity of databases, protect them
from unauthorized or inappropriate access.
Suggested Settings for Creating the Content Store in DB2 on z/OS
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Guidelines for Creating the Content Store in DB2 on z/OS
Use the following checklist to help you help you set up the content store in DB2 on z/OS.
❑
Create a database instance, storage group, and a user account for the content store.
A user must have permissions to create and delete tables in the database.
72
Chapter 6: Setting Up the Environment
IBM Cognos 8 uses the credentials of the user account to communicate with the database server.
❑
Ensure you reserve a buffer pool with a page size of 32 KB, and a second one with a page size
of 4 KB for the database instance.
❑
Administrators must run a script to create tablespaces to hold Large Objects and other data
for the content store and grant user rights to the tablespaces. For information about running
the script, see "Create Tablespaces for DB2 Content Store on z/OS" (p. 76).
❑
Your database administrator must back up IBM Cognos 8 databases regularly because they
contain the IBM Cognos data. To ensure the security and integrity of databases, protect them
from unauthorized or inappropriate access.
Suggested Settings for Creating the Content Store in Oracle
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Guidelines for Creating the Content Store in Oracle
Use the following checklist to help you set up the content store on Oracle.
❑
Ensure that the parameter for the database instance compatibility level of the content store
database is set to 9.0.1 or higher.
For example, you can check the COMPATIBLE initialization parameter setting by issuing the
following SQL statement:
SELECT name, value, description FROM v$parameter WHERE name='compatible';
For information about changing an instance configuration parameter, see the Oracle documentation.
❑
Determine if the database is Unicode.
Tip: One method is to type the following select statement:
select * from NLS_DATABASE_PARAMETERS
If the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database
and specify AL32UTF8 for the database character set parameters.
❑
Determine which user account will be used to access the database.
Tip: If you want to host more than one content store on your Oracle instance and you will use
both at the same time, use a different user account for each content store to ensure that each
IBM Cognos 8 instance is fully isolated from the others.
❑
Ensure that the user account that accesses the database has permission to do the following:
●
connect to the database
●
create, alter, and drop tables, triggers, views, procedures, and sequences
●
insert, update, and delete data in the database tables
Installation and Configuration Guide 73
Chapter 6: Setting Up the Environment
❑
Your database administrator must back up IBM Cognos 8 databases regularly because they
contain the Cognos data. To ensure the security and integrity of databases, protect them from
unauthorized or inappropriate access.
Suggested Settings for Creating the Content Store in Microsoft SQL Server
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Suggested settings for Microsoft SQL Server
Use the following checklist to help you set up the content store on Microsoft SQL Server.
❑
Ensure that the collation sequence is case-insensitive.
In a Custom installation, you choose a collation, which includes character sets and sort order,
during the SQL Server setup. In a Typical installation, the installation uses the locale identified
by the installation program for the collation. This setting cannot be changed later.
❑
When connecting to Microsoft SQL Server Management Studio to create the database, use SQL
server authentication.
If you connect using Windows authentication, the database that you create will also use Windows
authentication. In this situation, you must configure the database connection using a database
type of SQL Server database (Windows Authentication) in IBM Cognos Configuration.
❑
For the user account that will be used to access the database, create a new login under Security
and use the following settings:
●
Select SQL Server authentication.
●
Clear the Enforce password policy check box.
Tip: If you want to host more than one content store on your Microsoft SQL Server instance
and you will use both at the same time, use a different user account for each content store to
ensure that each IBM Cognos 8 instance is fully isolated from the others.
74
❑
For Microsoft SQL Server 2008, grant EXECUTE permission to the user account that accesses
the database.
❑
For the content store database, create a new database under Databases.
❑
Under Security for the new database, create a new schema and assign a name to it.
❑
Under Security for the new database, create a new user with the following settings:
●
For Login name, specify the new login that you created for the user account.
●
For Default schema, specify the new schema.
●
For Owned Schemas, select the new schema.
●
For Role Members, select db_datareader, db_datawriter, and db_ddladmin.
Chapter 6: Setting Up the Environment
Suggested Settings for Creating the Content Store in Sybase
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Suggested settings for Sybase
Use the following checklist to help you set up the content store on Sybase.
❑
On the Sybase server, create a server instance with an 8 KB server page size.
For instructions, see the Sybase documentation.
❑
If required, install jConnect 5.5.
This tool sets up the communication between the JDBC driver and the Sybase Adaptive Server
instance.
For instructions, see the Sybase documentation.
If your version of Sybase does not include JConnect 5.5, you must download the installer from
Sybase’s Web site.
❑
Add the UTF-8 character set to the server instance.
❑
If required, make UTF-8 the default character set on the server.
❑
Create a database device.
Tip: Set log_segment to a minimum of 10 MB.
❑
Set the new database device as the default.
Information about the new database will be stored in the new database device. Keep a backup
of the database device for recovery purposes.
❑
Create the database.
❑
Determine which user account will be used to access the database.
Tip: If you want to host more than one content store on your Sybase instance and you will use
them at the same time, use a different user account for each content store to ensure that each
IBM Cognos 8 instance is fully isolated from the others.
❑
Ensure that the user account has the following privileges for the database: create default, create
procedure, create rule, create table, and create view.
❑
Ensure that the database has the following settings and is restarted:
●
create and drop table privileges for the user account
●
Select into property is set to True
Installation and Configuration Guide 75
Chapter 6: Setting Up the Environment
Create Tablespaces for DB2 Content Store on z/OS
A database administrator must run a script to create a set of tablespaces required for the content
store database. The script must be modified to replace the placeholder parameters with ones that
are appropriate for your environment.
Ensure that you use the naming conventions for DB2 on z/OS. For example, all names of parameters
must start with a letter and the length must not exceed eight characters. For more information, see
the IBM DB2 Information Center.
Steps
1. Connect to the database as a user with privileges to create and drop tablespaces and to allow
execution of SQL statements.
2. Open the tablespace_db2zOS.sql script file and use the following table to help you to replace
the generic parameters with ones appropriate for your environment.
Not all of the parameters listed are in the script, but may be added in the future.
Parameter Name
Description
CMSCRIPT_CREATE_IN
Specifies the base tables location
For example, databaseName.baseTablespaceName
CMSCRIPT_STOGROUP
Specifies the name of the storage group.
CMSCRIPT_DATABASE
Specifies the name of the content store database.
CMSCRIPT_CS_ID
Specifies the instance identification for the content
store database.
The ID must not be longer than two characters.
CMSCRIPT_TABLESPACE
Specifies the name of the tablespace that will contain
all of the base tables in the content store.
Auxiliary tables are not included.
The name cannot be longer than six characters.
76
CMSCRIPT_LARGE_BP
Specifies the name of the large buffer pool allocated
for especially large objects.
CMSCRIPT_REGULAR_BP
Specifies the name of the regular size buffer pool
allocated for regular and large objects.
CMSCRIPT_USERNAME
Specifies the user account that accesses the content
store database.
Chapter 6: Setting Up the Environment
3. Save and run the script.
4. Grant the IBM Cognos user rights to the tablespaces that were created when you ran the
tablespace_db2zOS.sql file script:
●
In the remote access tool, open the rightsGrant_db2zOS.sql script file and replace the
placeholder parameters with values that are appropriate for your environment.
Tip: Ensure that you use the same values that you used when you allocated resources to
the buffer pools and user account.
●
Save and run the file.
The content store database is created. You can now configure a database connection.
Set Up the Database Client for the Content Store
If you use Oracle, DB2, or Sybase as the database server for the content store, additional steps are
required after you install IBM Cognos 8 Analytic Applications before you can configure it. You
must set up the following on the computer where Content Manager is installed:
Database
Additional steps
Oracle
Set up the JDBC driver.
DB2
Set up the database client software and the JDBC 2.0 driver.
Sybase
Set up the JDBC driver.
Microsoft SQL Server
The JSQLConnect.jar file is installed to the appropriate location by default and no additional steps are required.
Steps for Oracle
1. On the computer where Oracle is installed, go to the ORACLE_HOME/jdbc/lib directory.
2. Copy the ojdbc14.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory.
This file includes the driver required by the content store.
In a distributed installation, you must copy this file on the IBM Cognos 8 computers where
you must install the software.
Steps for DB2
1. Install the DB2 client software on the appropriate computers.
2. If the content store is on a different computer from Content Manager, configure a database
alias to the content store by running the DB2 Client Configuration Assistant.
If the content store database and Content Manager are on the same computer, the content store
automatically becomes the alias.
Installation and Configuration Guide 77
Chapter 6: Setting Up the Environment
When you configure the Content Manager computers, ensure that they are all configured to
use the same content store.
3. Stop the DB2 services and the HTML Search Server.
4. To copy the JDBC2 driver, copy the DB2_installation/sqllib/java/db2java.zip file to the
c8_location/webapps/p2pd/WEB-INF/lib directory.
5. Rename the db2java.zip file to db2java.jar.
6. Restart the DB2 services and the HTML Search Server.
7. Repeat this procedure on the IBM Cognos 8 Analytic Applications computers where you must
install the software.
You can tune the database to take advantage of DB2 features. For more information, see the IBM
Cognos 8 Architecture and Deployment Guide.
Steps for Sybase
1. On the computer where Sybase is installed, go to the Sybase_location /jConnect-5_5/classes
directory.
2. Copy the jconn2.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory the computer
where Content Manager is installed.
When the installation is complete, some configuration tasks are required to ensure that IBM Cognos 8
Analytic Applications (p. 87) works in your environment.
Set Up Environment Variables to Use Scripts
For Adaptive Warehouse Runtime, you must specify environment variables before you can use a
DB2 or Oracle database in a scripting environment.
The proper syntax for creating environment variables is shell dependent.
Oracle
For Oracle databases, you must set and export the database environment variables for the script
user before you start the IBM Cognos processes. Adaptive Warehouse Runtime uses these database
variables to connect to your database. One way to set these environment variables is to include
these commands in the .profile or .login script of the user who starts the IBM Cognos services.
When you set the load library paths, ensure that the 32-bit Oracle libraries are in the library search
path, which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory
if you installed a 64-bit Oracle client.
The following table describes environment variables for Oracle databases. Contact your database
or network administrator for the correct values for your system.
78
Chapter 6: Setting Up the Environment
Environment variable
Description
ORACLE_HOME
The top level directory that contains the database client
software or the entire database installation.
Example: /usr/oracle
You may be able to use an Oracle script to create the environment variables. For more information, see the Oracle
documentation.
Example: /usr/local/bin/coraenv
TNS_ADMIN
The directory that contains the Oracle tnsnames.ora file,
which allows calls to the Oracle database to determine the
required server connections.
Example:
$ORACLE_HOME/network/admin
PATH
The variable to locate executable files.
Example:
$PATH:$ORACLE_HOME/bin
The load library path.
On Solaris:
Solaris Examples:
LD_LIBRARY_ PATH
LD_LIBRARY_PATH=$ORACLE_HOME/ lib:$LD_
LIBRARY_PATH
LD_LIBRARY_PATH=$ORACLE_HOME/ lib32:$LD_
LIBRARY_PATH
On AIX:
AIX Examples:
LIBPATH
LIBPATH=$ORACLE_HOME/ lib:$LIBPATH
LIBPATH=$ORACLE_HOME/ lib32:$LIBPATH
On HP-UX:
HP-UX Examples:
SHLIB_PATH
SHLIB_PATH=$ORACLE_HOME/ lib:$SHLIB_PATH
SHLIB_PATH=$ORACLE_HOME/ lib32:$SHLIB_PATH
DB2
For IBM DB2 databases, you must set the database variables by running the environment setup
scripts included with the IBM DB2 installation. For Bourne or Korn shells, run the following command or add it to the .profile script:
Installation and Configuration Guide 79
Chapter 6: Setting Up the Environment
DB2_installation_path/db2profile
Contact your database or network administrator for the correct values for your system.
Update the Java Environment
IBM Cognos 8 Analytic Applications cryptographic services use specific .jar (Java Archive) files in
your Java Runtime Environment (JRE) to determine the allowed strength of the JRE. IBM Cognos 8
Analytic Applications provides the necessary jurisdictional policy .jar files in case your JRE does
not have the minimum require cryptographic strength.
If you do not have a JAVA_HOME variable already set or if JAVA_HOME points to a Java version
that is not valid for IBM Cognos 8 Analytic Applications, the JRE files provided with the installation
will be used, and you do not need to update any files in your environment.
To use your own JRE and have JAVA_HOME set to that location, you may need to update the
Java environment for the cryptographic services.
The need to update your Java environment depends on the relative strength of jurisdictional policy
.jar files in your environment. For example, if you already have stronger files in your environment
than are provided with IBM Cognos 8 Analytic Applications, you do not need to update the environment. Doing so, in this case, may cause other applications to not work correctly.
If you update your Java environment, we recommend that you make a backup copy of the files you
overwrite. If other applications fail, you may need to replace the original jurisdictional policy .jar
files.
For Windows, you can set JAVA_HOME as a system variable or a user variable. If you set it as a
system variable, it may be necessary to restart your computer for it to take effect. If you set it as a
user variable, set it so that the environment in which Tomcat is running can access it.
Java 1.4.2 is the minimum supported JRE for IBM Cognos 8 Analytic Applications. Ensure that
you installed the correct JRE for the hardware that you are using. The encryption .jar files provided
with the installation are for Java 1.4.2.
Steps
1. Ensure that the JAVA_HOME environment variable is set to the JRE location.
For example, to set JAVA_HOME to a JRE that you are already using, the path is Java_location/bin/jre/version.
2. Copy the bcprov-jdknn-nnn.jar file from the c8_location/bin/jre/version/lib/ext directory to the
Java_location/jre/lib/ext directory.
JDBC Driver Options for Using DB2 Database as a Content Store
IBM Cognos 8 uses JDBC connectivity to access the database used for the content store.
If you use DB2 on Windows, Linux or UNIX as your content store you must choose whether to
use the type 2 or type 4 JDBC driver depending on how you want to connect to the content store.
80
Chapter 6: Setting Up the Environment
If you are using a DB2 database on z/OS for the content store, you must use type 4 JDBC
connectivity.
You specify the driver type to use in IBM Cognos Configuration.
Configuration Options for the Universal Driver
DB2 introduced a universal JDBC driver that contains both type 2 and type 4 JDBC driver support.
The universal driver, db2jcc.jar, replaces the deprecated type 2 JDBC driver, db2java.zip.
If you are upgrading, you can continue to use type 2 JDBC connectivity with no configuration
change required. If you want to use the type 4 JDBC connectivity, you must change your configuration to include the host name and port number of the database server.
For both type 2 and type 4 JDBC connectivity, however, you must copy the new universal driver,
db2jcc.jar, and the accompanying license file, db2jcc_license_*.jar, to your IBM Cognos 8 installation
location.
For more information, see "Set Up Database Connectivity for the Content Store Database" (p. 44).
Using the Type 2 JDBC Driver
Type 2 JDBC drivers are comprised of a native-API component and a Java component.
The connection to the DB2 database occurs through the DB2 CLI libraries, which comprise the
native component that communicates with the database server.
Because type 2 JDBC drivers require common client code and rely on the native code of the product,
a DB2 product must be installed to use this driver. For example, a DB2 client must be installed on
the computer where you have Content Manager installed.
Using the Type 4 JDBC Driver
Type 4 JDBC drivers are pure Java drivers which provide direct access to DB2 database features
through network communication.
The type 4 driver is considered an independent product. It does not require the DB2 product to be
installed. For example, you do not need to install the DB2 client on the computer where you have
Content Manager installed.
Configure the Web Server
Before you can use Web pages generated by IBM Cognos 8 Analytic Applications, 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 IBM Cognos 8 Analytic Applications. You must also set
the content expiry for the images directory in your Web server so that the Web browser does not
check image status after the first access.
Steps
1. Create the following virtual directories:
Installation and Configuration Guide 81
Chapter 6: Setting Up the Environment
Alias
Location
Permission
cognos8
c8_location/webcontent
Read
cognos8/cgi-bin
c8_location/cgi-bin
Execute
You can use a name other than cognos8 in the aliases. However, you must use cgi-bin as the
second part of the alias, and you must change the virtual directory in the Gateway URI property
to match the new alias. For more information about changing the gateway URI, see "Set the
IBM Cognos 8 Gateway and Dispatcher Connections" (p. 99).
For Apache Web Server, ensure that you define the cognos8/cgi-bin alias before the cognos8
alias in the httpd.conf file located in the Apache_installation/conf directory. You must define
the cognos8/cgi-bin alias as a ScriptAlias.
For Java System Web Server, ensure that you define the cognos8/cgi-bin alias before the cognos8
alias.
Note: Java System Web Server was formerly named Sun ONE Web Server or iPlanet Web
Server.
2. Set the content expiry on the c8_location/pat/images virtual directory in your Web server.
Each time a user opens IBM Cognos 8 Analytic Applications, their Web browser checks with
the Web server to determine if images are current. Because there are over 600 images, this can
result in excess network traffic. You can postpone this check until a specified date by using the
content expiry feature of the Web server.
For information on setting content expiry, see the documentation for your Web server.
If you use Web aliases other than cognos8, or your Web server is on another computer, or you are
using Microsoft Internet Application Interface (ISAPI), apache_mod or a servlet gateway, change
the Gateway URI (p. 99) when you configure IBM Cognos components.
Configure the Web Browser
IBM Cognos 8 Analytic Applications uses the default browser configurations provided by Microsoft,
Netscape, and Firefox. For all browsers, you must ensure that settings are enabled for cookies and
Java scripts. Additional required settings are specific to the browser.
The following table shows the settings that must be enabled in the supported Web browsers.
Browser
Setting
IBM Cognos component
Internet Explorer
Allow Cookies
IBM Cognos Connection
Active Scripting
Cognos Viewer
Allow META REFRESH
82
Chapter 6: Setting Up the Environment
Browser
Setting
IBM Cognos component
Netscape
Allow Cookies
IBM Cognos Connection
JavaScript
Firefox
Allow Cookies
IBM Cognos Connection
Enable Java
Cognos Viewer
Enable JavaScript
Load Images
IBM Cognos 8 Analytic Applications uses the following cookies to store user information:
Cookie
Type
Purpose
AS_TICKET
Session temporary
Created if IBM Cognos 8 Analytic Applications is configured
to use an IBM Cognos Series 7
namespace
Cam_passport
Session temporary
Stores a reference to a user session stored on the Content
Manager server
cc_session
Session temporary
Holds session information that
is specific to IBM Cognos Connection
cc_state
Session temporary
Holds information during edit
operations, such as cut, copy,
and paste
CRN
Session temporary
Contains the content and
product locale information, and
is set for all IBM Cognos users
PAT_CURRENT_ FOLDER
Persistent
Stores the current folder path if
local file access is used, and is
updated after the Open or Save
dialog box is used
qs
Persistent
Stores the settings that the user
makes for user interface elements such as menus and toolbars
Installation and Configuration Guide 83
Chapter 6: Setting Up the Environment
After upgrading or installing new software, restart the Web browser and advise users to clear their
browser cache.
Set Up the Data Source Environment
IBM Cognos 8 Analytic Applications creates and manages metadata used for reporting. Because
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 the data source environment. Commonly,
these things depend on the technology you use for your data source.
If you use a Sybase data source, these steps are not necessary.
If you upgraded, you are not required to set up anything in the data source environment. You must
set up the data source environment only if you installed your modeling tool in a different location
from the older version.
Users operating in different languages can connect to an MSAS 2005 data source from the same
instance of IBM Cognos 8. Modelers must create a separate package for each language. Users can
run reports in any language.
Ensure that you install the appropriate fonts to support the character sets and currency symbols
you use. For Japanese and Korean currency symbols to appear correctly, you must install the
additional fonts from the Supplementary Languages Documentation CD. For more information,
see "Install Translated Product Documentation" (p. 48).
Steps
1. Set the environment variable for multilingual support:
●
For Oracle, set the NLS_LANG (National Language Support) environment variable on
each computer where IBM Cognos 8 Adaptive Applications Framework and IBM Cognos 8
Application Tier Components are installed by typing the following command:
NLS_LANG = language_territory.character_set
An example is NLS_LANG = JAPANESE_JAPAN.UTF8
The value of the variable determines the locale-dependent behavior of IBM Cognos 8. Error
messages, sort order, date, time, monetary, numeric, and calendar conventions automatically
adapt to the native language and locale.
●
For DB2, set the DB2CODEPAGE environment variable to a value of 1252.
For more information about whether to use this optional environment variable, see the
DB2 documentation.
2. For Oracle, add $ORACLE_HOME/lib to your LD_LIBRARY_PATH.
3. For Oracle, copy the ojdbc14.jar file from ORACLE_HOME/jdbc/lib to the c8_location/webapps/
p2pd/WEB-INF/lib directory.
After you complete these tasks, you must configure the IBM Cognos components (p. 87) to work
in your environment.
84
Chapter 6: Setting Up the Environment
Create a DB2 Database to use as a Data Warehouse
You can create a database on DB2 by using a script that is located in the ap_location\pw\scripts
directory.
You must run this script from a DB2 account that has the privileges required to access and write
to the database. This script will create and configure a database that you can use as your data
warehouse.
Note: the script creates the database in the first DB2 instance in your path. If you have more than
one DB2 instance, ensure that the DB2 instance in which you want to create the database is the
first in the path.
Steps
1. From ap_location\pw\scripts, copy the appropriate script to your DB2 server.
●
On Windows, copy aaf_create_dw.bat
●
On UNIX, copy aaf_create_dw.sh
2. On the DB2 server, log onto a DB2 account that has the required privileges.
3. In a command line utility, type the following:
●
On Windows, type
aaf_create_dw.bat db_namedrive
●
On Unix, type
./aaf_create_dw.sh db_namepath
Value
Setting
db_name
The name of the database that will be created.
drive/path
On Windows, the drive on which the database objects will
be created. On UNIX, the path where the database objects
will be created.
After you run the script, you must create a connection to the database in Adaptive Warehouse
before you can use it as a data warehouse.
Installation and Configuration Guide 85
Chapter 6: Setting Up the Environment
86
Chapter 7: Configuring IBM Cognos 8 Analytic
Applications
After you install one or more IBM Cognos 8 Analytic Applications components on your computer,
you must configure them to work in your IBM Cognos environment. Initially, default property
settings are used to configure the IBM Cognos 8 Analytic Applications 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 types of installation (p. 21), 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 IBM Cognos 8 Analytic Applications across more than one computer, 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 components is also important.
Other configuration tasks are optional and depend on your environment. Use these optional configuration tasks to customize your configuration so that IBM Cognos 8 Analytic Applications easily
integrates into your existing environment. For example, you can configure features for IBM Cognos
Application Firewall or specify the amount of resources IBM Cognos 8 uses. You can also configure
IBM Cognos 8 Analytic Applications to use other resources, such as using an authentication provider
and then enabling single signon for the database connection and the users.
Start IBM Cognos Configuration
Use IBM Cognos Configuration to configure your IBM Cognos Environment URIs and to specify
the database connection properties to the content store. If you change the value of a property, you
must save the configuration and then restart the IBM Cognos 8 service to apply the new settings
to your computer.
To start IBM Cognos Configuration on a Windows computer, do the following:
●
From the Start menu, click Programs, IBM Cognos 8 Analytic Applications, IBM Cognos
Configuration.
Alternatively, you can start IBM Cognos Configuration from the last page of the installation wizard.
You should start IBM Cognos Configuration in the last page of the installation wizard only if
additional setup is not required. For example, if you use a database server other than Microsoft
SQL for the content store, we recommend that you copy the JDBC drivers to the appropriate location
before you start the configuration tool.
If your UNIX environment does not support a Java-based graphical user interface, you must configure your components by editing the cogstartup.xml file located in the apps_location/configuration
directory or the c8_location/configuration directory. After you edit the file, you can run IBM Cognos
Installation and Configuration Guide 87
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Configuration in silent mode to apply the configuration. For more information, see the IBM Cognos
Configuration User Guide.
Steps for Windows
1. To start IBM Cognos Configuration to configure IBM Cognos 8 server components on a
Windows computer, from the Start menu, click Programs, IBM Cognos 8, IBM Cognos Configuration.
2. To start IBM Cognos Configuration to configure IBM Cognos 8 Adaptive Applications
Framework on a Windows computer, from the Start menu, click Programs, IBM Cognos 8,
IBM Cognos Configuration.
Steps for UNIX
1. Go to the installation_location/bin directory.
2. Type the appropriate command.
●
If you use XWindows, type
./cogconfig.sh
●
If you do not use XWindows, type
./cogconfig.sh -s
Configure Single Computer Installations
If you install all IBM Cognos 8 Analytic Applications components on one computer, some configuration tasks are required so that the components work in your IBM Cognos environment.
Before you configure IBM Cognos 8 Analytic Applications, ensure that
●
IBM Cognos 8 runtime or reporting components are installed
●
a Web server is installed, configured, and running
●
a Web browser is installed, configured, and running
●
you created a database for the content store
●
you have set the required environment variables, if you intend to run scripts
Use the following checklist to guide you through the required configuration tasks:
88
❑
Set the database connection properties for the content store.
❑
Save the configuration settings.
❑
Test the installation and configuration.
❑
Import the splash screen for the IBM Cognos 8 Analytic Applications portal page, if required.
❑
Copy the image files for Adaptive Analytics report icons, if required.
❑
Finish the configuration.
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Set Database Connection Properties for the Content Store
You must specify the database server information to ensure that Content Manager can connect to
the database you use for the content store. Content Manager uses the database logon to access the
content store. After you set the database connection properties, you can test the connection between
Content Manager and the content store.
For some applications, you can select and install Cognos Content Database. If you install Cognos
Content Database, the database connection properties use the default connection settings and you
are not required to change them.
Ensure that you use one of the supported database servers to create the content store. You must
create the content store using Oracle, Microsoft SQL Server, or DB2. IBM Cognos 8 Analytic
Applications requires the TCP/IP protocol to access data and the content store. Ensure that the
database server has the protocol set to TCP/IP. For more information, see "Guidelines for Creating
the Content Store" (p. 69).
Note: Some database servers are available with advanced features. When you select an advanced
database, IBM Cognos 8 Analytic Applications uses features of the database server to manage the
connection. If you select the advanced Oracle database, for example, IBM Cognos 8 Analytic
Applications uses enterprise-oriented Oracle features to select a listener, switch to another listener
if the first listener fails, automatically reconnect to the database if the connection fails, balance
connection requests among listeners, and balance connection requests among dispatchers.
Steps for Cognos Content Database
1. Start IBM Cognos Configuration.
2. In the Explorer window, under Data Access, Content Manager, right-click Content Store, and
then click Delete. Click Yes to confirm the deletion.
This action deletes the connection to default database.
3. Right-click Content Manager, and then click New resource, Database.
4. In the Properties window, configure IBM Cognos 8 to use Cognos Content Database as the
content store:
●
For Name, type cm.
●
For Database server and port number, type the name of the computer where you installed
Cognos Content Database.
●
For User ID and password, click the edit button and specify the userid and password to
access Cognos Content Database.
We recommend that you change the default user ID and password after configuring the new
resource.
5. From the File menu, click Save.
The logon credentials are immediately encrypted.
6. In the Explorer window, right-click Content Store and click Test to test the connection between
Content Manager and the content store.
Installation and Configuration Guide 89
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
You must start the Cognos Content Database service before you test.
Content Manager connects to the database, checks the database permissions, and creates and
populates a table. The table is not deleted and is used each time that the test is repeated.
Content Manager can now create the required tables in the content store when you start the IBM
Cognos 8 service for the first time. If the connection properties are not specified correctly, the tables
are not created and you cannot connect to IBM Cognos Connection.
Steps for DB2
1. If you are using type 2 JDBC connectivity, install the DB2 client software on the Content
Manager computers.
If you use type 4 JDBC connectivity for DB2, you are not required to install the DB2 client
software where Content Manager is installed. If you are using a DB2 database on z/OS for the
content store, you must use type 4 JDBC connectivity.
For more information about the differences between type 2 and type 4 drivers, see "JDBC
Driver Options for Using DB2 Database as a Content Store" (p. 80).
2. If you are using type 2 JDBC connectivity, and the content store is on a different computer than
Content Manager, configure a database alias to the content store.
On Windows, run the DB2 Client Configuration Assistant.
On UNIX or Linux, use the DB2 command line interface.
If the content store database and Content Manager are on the same computer, the content store
name automatically becomes the alias.
When you configure the Content Manager computers, ensure that they are all configured to
use the same content store.
3. On Windows, stop the DB2 services and the HTML Search Server.
4. Copy the following files from DB2_installation/sqllib/java directory to the c8_location/webapps/
p2pd/WEB-INF/lib directory.
●
the universal driver file, db2jcc.jar
●
the license file
for DB2 on Linux, UNIX, or Windows, db2jcc_license_cu.jar
for DB2 on z/OS, db2jcc_license_cisuz.jar
If you are connecting to DB2 on z/OS, use the driver version from Linux, UNIX, or Windows
version 9.1 fix pack 5 or version 9.5 fix pack 2.
Tip: To check the driver version, run the following command
java -cp path\db2jcc.jar com.ibm.db2.jcc.DB2Jjcc -version
5. On Windows, restart the DB2 services and the HTML Search Server.
90
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
6. On UNIX, if you are using type 2 JDBC connectivity, ensure that the 32-bit DB2 libraries are
in the library search path, which is usually the $DB2DIR/lib directory or the $DB2DIR/lib32
directory.
7. Repeat this entire procedure on the IBM Cognos 8 computers where Content Manager is
installed or where notification is sent to a DB2 database.
Steps for Oracle
1. On the computer where the Oracle client is installed, go to the ORACLE_HOME/jdbc/lib
directory.
2. Copy the appropriate JAR file to the c8_location/webapps/p2pd/WEB-INF/lib directory on
computers where Content Manager is installed and where notification is sent to an Oracle
database.
●
If you use Java 1.4, copy the ojdbc14.jar file
●
If you use Java 1.5, copy the ojdbc5.jar file
If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or
ojdbc5.jar file.
The driver is available from an Oracle client or server install, and it can also be downloaded
from the Oracle technology Web site (http://www.oracle.com/technology).
Steps for Sybase
1. On the computer where Sybase is installed, go to the Sybase_location/jConnect-5_5/classes
directory.
2. Copy the jconn2.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every
computer where Content Manager is installed and where notification is sent to a Sybase database.
Update File Location Properties
If you install IBM Cognos 8 on Windows Vista, you must change file locations properties in IBM
Cognos Configuration so that IBM Cognos 8 can use a single data location for all users.
Windows Vista has a security enhancement that restricts multiple users from sharing data locations.
You can define environment variables and use them in IBM Cognos Configuration when specifying
file locations. This allows you to direct applicable files to an area that will be accessible by IBM
Cognos 8 users. On Windows, two environment variables are preset for users: one for all users and
one for the specific user
Because the environment variables represent system root locations, we recommend that you also
include the root directory name of the installation location when you specify file locations in IBM
Cognos Configuration. The default root directory for IBM Cognos 8 is c8.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
Installation and Configuration Guide 91
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
3. In the Properties window, click Deployment files location.
4. Replace the relative path element, "..", with the appropriate environment variable and root
directory:
●
For a single file location per user, %LOCALAPPDATA%
●
For a single file location for all users on the computer, %PUBLIC%
For example,
To set a single file location per user, specify the path %LOCALAPPDATA%/c8/deployment.
5. Repeat step 4 for the following properties:
●
Under Environment,
- Data files location
- Map files location
- Temporary files location
●
Under Environment, Logging, File,
- Log file location
●
Under Cryptography,
- Common symmetric key store location
●
Under Cryptography, Cognos,
- Certificate location
- Signing key store location
- Encryption key store location
6. From the File menu, click Save.
Save Your Configuration Settings
After you specify the values for the mandatory configuration properties, or make any changes to
local property values, you must save the configuration.
When you save the configuration, passwords are encrypted and a certificate is issued to validate
the identity of the computer. You can save the configuration in the default encoding of your computer
or in UTF-8 encoding.
Each time that you save your configuration, the changes are stored in the cogstartup.xml and the
coglocale.xml files in the apps_location/configuration directory. At the same time, a backup copy
of these files, containing the previous configuration settings, is created with a timestamp in the
apps_location/configuration directory.
Steps
1. From the File menu, choose which encoding to use to save the configuration:
92
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
If you use more than one language or character set in the configuration settings, click Save
As UTF-8.
●
If you use the default encoding of your computer, click Save.
Errors, such as missing values for mandatory properties, cause an error message to appear. To
view the cause of the error, click the Details box.
Tip: Restart the IBM Cognos service to apply the saved configuration values to your computer.
2. If you plan to use the local configuration as a template for configuring other computers that
have the same installed IBM Cognos components, export the configuration. For information,
see the IBM Cognos Configuration User Guide.
Test the Installation and Configuration
You can test your configuration settings by running the test feature as you configure IBM Cognos 8.
After you have completed the configuration and started the services, you can test the installation
by connecting to the IBM Cognos 8 portal.
Before you can use IBM Cognos 8 Analytic Applications, you must start the IBM Cognos 8 service.
For Windows, the IBM Cognos 8 service is configured to start automatically by default. For UNIX,
to start the IBM Cognos 8 process automatically, you must configure the process as a daemon. For
more information, see your operating system documentation.
Steps
1. Open a Web browser.
2. Test that Content Store was successfully created and Content Manager started by typing
http://host_name:port/p2pd/servlet
3. Test the availability of the dispatcher by typing
http://host_name:port/p2pd/servlet/dispatch
If the response includes the string State: Running, the dispatcher is available.
4. Connect to the IBM Cognos 8 portal by typing one the following, where cognos8 is the virtual
directory you created when you configured the Web server.
●
For the CGI gateway:
http://host_name:port/cognos8
●
For an ISAPI gateway:
http://host_name:port/cognos8/isapi
●
For Apache Connector:
http://host_name:port/cognos8/cgi-bin/cognos_module
●
For a gateway servlet:
http://host_name:port/context_root/servlet/Gateway
Installation and Configuration Guide 93
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
It may take a few minutes for the Web page to open. If you see the Welcome page in the IBM
Cognos 8 portal, your installation is working.
Steps for Adaptive Warehouse
1. Start the IBM Cognos 8 service.
2. To start Adaptive Warehouse, from the Start menu, click Programs, IBM Cognos 8 Analytic
Applications, IBM Cognos 8 Adaptive Warehouse.
If you see the Welcome page of Adaptive Warehouse, your installation is working.
Steps for Adaptive Analytics
1. Start the IBM Cognos 8 service.
2. To start Adaptive Analytics, from the Start menu, click Programs, IBM Cognos 8 Analytic
Applications, IBM Cognos 8 Adaptive Analytics.
If you see the Welcome page of Adaptive Analytics, your installation is working.
Import the Splash Screen for the IBM Cognos 8 Analytic Applications Portal
Page
The IBM Cognos 8 deployment archive that is created by IBM Cognos 8 Analytic Applications
does not include the splash screen for the IBM Cognos 8 portal. While you can still traverse folders
and run reports, you can manually import the splash screen to improve the IBM Cognos 8 Analytic
Applications portal experience.
Steps
1. Go to the apps_location/analyticcontent/staticcontent directory.
2. Copy the file splash.zip to the c8_location/deployment directory.
3. Start IBM Cognos 8 by typing the following in the Address box of your web browser:
http://your computer name/IBM cognos8
4. In the IBM Cognos 8 Welcome screen, click IBM Cognos Connection.
5. From the Tools menu, click Content Administration.
6. Click New Import.
7. Select the Splash deployment archive, and then click Next.
Tip: If the Splash deployment archive is not listed, open IBM Cognos Configuration and confirm
that you copied splash.zip to the location specified in the Deployment file location of the
Environment group.
8. Click Next to accept the default name and description.
9. Select the check box adjacent to the Analytic Applications folder in the Name column.
10. Ensure the Disable after input check box is cleared, and then click Next.
94
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
11. Click Next to accept the default general options.
12. Click Next to accept the summary.
13. Click Save and run once, and then click Finish.
14. Click Run.
15. Click OK to start the import.
After importing the splash screen, you can also manually create an IBM Cognos 8 portal tab, which
will make the user experience even better. For more information, see the IBM Cognos Connection
User Guide.
Copy Image Files for Adaptive Analytics Report Icons
You must copy the image files, used for the report icons in Adaptive Analytics, to the correct location
so that they appear correctly in reports.
Steps
1. Go to apps_location/webcontent/skins/adaptive, and copy the contents of this directory.
2. Paste the copied contents to the c8_location/webcontent/skins directory.
Finish the Configuration
After you complete the required configuration tasks, you can perform some additional configuration
tasks to customize the behavior of IBM Cognos 8 components to better suit your environment
(p. 103).
We recommend that you specify the amount of resources the IBM Cognos 8 service uses (p. 115) to
ensure that performance is optimized.
After you have completed the configuration, you can create a database to contain your data warehouse and then create an Adaptive Warehouse project. For more information, see the Adaptive
Warehouse User Guide.
Configure Distributed Installations
You must configure components in an environment where you distribute IBM Cognos 8 Analytic
Applications components across more than one computer.
You 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 at least one dispatcher.
●
The Application Tier Components computer must know the location of the Content Manager
computer, and the database to use for job and schedule information.
You must also configure cryptographic properties to ensure that each computer uses the same settings.
Installation and Configuration Guide 95
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
In a distributed environment, the sequence in which you configure computers is important. You
must configure and then start the IBM Cognos 8 service on at least one computer where you installed
Content Manager before you configure other computers in your IBM Cognos environment. You
must configure the gateway computer last so that cryptographic keys are shared and secure communication can take place among the three components. The server specified for the External Dispatcher
URI property on the gateway computer must be the last server that you start.
Other configuration tasks, such as using an authentication provider (p. 149), enabling and disabling
services (p. 114) are optional and change the default behavior of IBM Cognos 8 Analytic Applications
components to better suit your reporting objectives.
Before you configure IBM Cognos 8 Analytic Applications, ensure that
●
IBM Cognos 8 runtime or reporting components are installed
●
a Web server is installed, configured, and running
●
a Web browser is installed, configured, and running
●
you created a database for the content store
●
you have set the required environment variables, if you intend to run scripts
Use the following checklist to guide you through the required configuration tasks:
❑
Set the database connection properties for the content store.
❑
Set the IBM Cognos 8 gateway and dispatcher connections.
❑
Save the configuration settings.
❑
Test the installation and configuration.
❑
Import the splash screen for the IBM Cognos 8 Analytic Applications portal page, if required.
❑
Copy the image files for Adaptive Analytics report icons, if required.
❑
Finish the configuration
After you complete these configuration tasks, you can change the default behavior of IBM Cognos 8
Analytic Applications components (p. 103) to better suit your IBM Cognos environment.
We recommend that you specify the amount of resources the IBM Cognos 8 service uses (p. 115) to
ensure that performance is optimized.
Set Database Connection Properties for the Content Store
For all installations, you must specify the database server information to ensure that Content
Manager can connect to the database you use for the content store. Content Manager uses the
database logon to access the content store. After you set the database connection properties, you
can test the connection between Content Manager and the content store.
Ensure that you use one of the supported database servers to create the content store. The content
store must be created using Oracle, Microsoft SQL Server, or DB2. IBM Cognos 8 Analytic
Applications requires the TCP/IP protocol to access data and the content store. Ensure that the
96
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
database server has the protocol set to TCP/IP. For more information, see "Guidelines for Creating
the Content Store" (p. 69).
Note: Some database servers are available with advanced features. When you select an advanced
database, IBM Cognos 8 Analytic Applications uses features of the database server to manage the
connection. If you select the advanced Oracle database, for example, IBM Cognos 8 Analytic
Applications uses enterprise-oriented Oracle features to select a listener, switch to another listener
if the first listener fails, automatically reconnect to the database if the connection fails, balance
connection requests among listeners, and balance connection requests among dispatchers.
Steps for Cognos Content Database
1. On the computer where you installed Content Manager, start IBM Cognos Configuration.
2. In the Explorer window, under Data Access, Content Manager, click Content Store.
3. In the Properties window, change the following properties:
●
For Name, type cm.
●
For Database server and port number, type the name of the computer where you installed
Cognos Content Database.
●
For User ID and password, click the edit button and specify the userid and password to
access Cognos Content Database.
We recommend that you change the default user ID and password after configuring the new
resource. For information about changing default values, see "Change the Default User and
Password for Cognos Content Database" (p. 106).
4. From the File menu, click Save.
The logon credentials are immediately encrypted.
5. From the Actions menu, click Test to test the connection between Content Manager and the
content store.
You must start the Cognos Content Database service on the computer where it is installed
before the test will succeed.
Content Manager connects to the database, checks the database permissions, and creates and
populates a table. The table is not deleted and is used each time that the test is repeated.
Steps for DB2
1. In the location where you installed Content Manager, start IBM Cognos Configuration.
2. In the Explorer window, under Data Access, Content Manager, click Content Store.
3. In the Properties window, for the Database name property, type the name of the database or
the database alias.
4. Change the logon credentials to specify a valid user ID and password:
●
Click the Value box next to the User ID and password property and then click the edit
button when it appears.
Installation and Configuration Guide 97
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
Type the appropriate values and click OK.
5. To use type 4 JDBC connectivity, for the Database server and password property, type a value,
using host:port syntax.
If you leave this property blank, type 2 JDBC connectivity is used.
For more information about the differences between the driver types, see "JDBC Driver Options
for Using DB2 Database as a Content Store" (p. 80).
6. From the File menu, click Save.
The logon credentials are immediately encrypted.
7. Test the connection between Content Manager and the content store.
Tip: In the Explorer window, right-click the new database and click Test.
Content Manager connects to the database, checks the database permissions, and creates and
populates a table. The table is not deleted and is used each time that the test is repeated.
Steps for Microsoft SQL Server, Oracle, and Sybase
1. On the computer where you installed Content Manager, start IBM Cognos Configuration.
2. In the Explorer window, under Data Access, Content Manager, right-click Content Store and
click Delete.
This deletes the connection to the default resource. Content Manager must be configured 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.
If you are upgrading and want to use an existing content store, ensure that you select the type
of database you use for the older version.
If you installed more than one version of IBM Cognos 8, you must use a different content store
for each version. When a content store is used by a new version of IBM Cognos 8, it cannot
be used by an older version.
Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection,
select Oracle database (Advanced).
6. In the Properties window, provide values depending on your database type:
●
If you use a Microsoft SQL Server database, type the appropriate values for the Database
server with port number or instance name and Database name properties.
For a Microsoft SQL Server database, you can choose to use a port number, such as 1433,
or a named instance as the value for the Database server with port number or instance
name property.
98
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
To connect to a named instance, you must specify the instance name as a JDBC URL
property or a data source property. For example, you can type localhost\instance1. If no
instance name property is specified, a connection to the default instance is created.
Note that the properties specified for the named instance, along with the user ID and
password, and database name, are used to create a JDBC URL. Here is an example:
jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required
●
If you use an Oracle database, type the appropriate values for the Database server and port
number and Service name properties.
●
If you use an advanced Oracle database, for the Database specifier property, type the Oracle
Net8 keyword-value pair for the connection.
Here is an example:
(description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl)))))
When you select the advanced Oracle database, IBM Cognos 8 uses enterprise-oriented
Oracle features to select a listener, switch to another listener if the first listener fails, automatically reconnect to the database if the connection fails, balance connection requests
among listeners, and balance connection requests among dispatchers.
●
If you use a Sybase database, type the appropriate values for the Database server and port
number and Database name properties.
7. If you want to change the logon credentials, specify a user ID and password:
●
Click the Value box next to the User ID and password property and then click the edit
button when it appears.
●
Type the appropriate values and click OK.
8. From the File menu, click Save.
The logon credentials are immediately encrypted.
9. Test the connection between Content Manager and the content store.
Tip: From the Actions menu, click Test to test the connection between Content Manager and
the content store.
Content Manager connects to the database, checks the database permissions, and creates and
populates a table. The table is not deleted and is used each time that the test is repeated.
Content Manager can now create the required tables in the content store when you start the IBM
Cognos 8 service for the first time. If you do not specify the connection properties correctly, the
tables are not created and you cannot connect to IBM Cognos Connection.
Set the IBM Cognos 8 Gateway and Dispatcher Connections
You must configure a connection to the IBM Cognos 8 gateway and dispatcher on the computer
where IBM Cognos 8 Adaptive Applications Framework components are installed.
Installation and Configuration Guide 99
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
If you installed IBM Cognos 8 Adaptive Applications Framework components on the same computer
as IBM Cognos 8 runtime or reporting components, the default settings may be appropriate.
However, your installation may need to use ports that differ from the default.
If IBM Cognos 8 Adaptive Applications Framework components are installed on another computer,
your installation must point to a dispatcher.
Steps
1. In IBM Cognos Configuration, click Environment.
2. Click the Value box for Gateway URI, and type the location for the IBM Cognos 8 gateway.
3. Click the Value box for Dispatcher URI for external applications, and type the location for the
IBM Cognos 8 dispatcher.
Save Your Configuration Settings
After you specify the values for the mandatory configuration properties, or make any changes to
local property values, you must save the configuration.
When you save the configuration, passwords are encrypted and a certificate is issued to validate
the identity of the IBM Cognos computer. You can save the configuration in the default encoding
of your computer or in UTF-8 encoding.
Each time that you save your configuration, the changes are stored in the cogstartup.xml and the
coglocale.xml files in the apps_location/configuration directory. At the same time, a backup copy
of these files, containing the previous configuration settings, is created with a date and time stamp
in the apps_location/configuration directory.
Steps
1. From the File menu, choose which encoding to use to save the configuration:
●
If you use more than one language or character set in the configuration settings, click Save
As UTF-8.
●
If you use the default encoding of your computer, click Save.
Errors, such as missing values for mandatory properties, cause an error message to appear. To
view the cause of the error, click the Details box.
Tip: Restart the IBM Cognos service to apply the saved configuration values to your computer.
2. If you plan to use the local configuration as a template for configuring other computers that
have the same installed IBM Cognos components, export the configuration. For information,
see the IBM Cognos Configuration User Guide.
Test the Installation and Configuration
You can test your configuration settings by running the test feature before you start the IBM
Cognos 8 service. Then you can test the installation by starting the IBM Cognos 8 service and then
opening IBM Cognos Connection. You can test the IBM Cognos 8 Analytic Applications components
by starting the required component and creating a project.
100
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Before you can use IBM Cognos 8 Analytic Applications, you must start the IBM Cognos 8 service.
For Windows, the IBM Cognos 8 service is configured to start automatically by default. For UNIX,
to start the IBM Cognos 8 process automatically, you must configure the process as a daemon. For
more information, see your operating system documentation.
Steps
1. Open a Web browser.
2. Test that Content Store was successfully created and Content Manager started by typing
http://host_name:port/p2pd/servlet
3. Test the availability of the dispatcher by typing
http://host_name:port/p2pd/servlet/dispatch
If the response includes the string State: Running, the dispatcher is available.
4. Connect to the IBM Cognos 8 portal by typing one the following, where cognos8 is the virtual
directory you created when you configured the Web server.
●
For the CGI gateway:
http://host_name:port/cognos8
●
For an ISAPI gateway:
http://host_name:port/cognos8/isapi
●
For Apache Connector:
http://host_name:port/cognos8/cgi-bin/cognos_module
●
For a gateway servlet:
http://host_name:port/context_root/servlet/Gateway
It may take a few minutes for the Web page to open. If you see the Welcome page in the IBM
Cognos 8 portal, your installation is working.
Steps for Adaptive Warehouse
1. Start the IBM Cognos 8 service.
2. To start Adaptive Warehouse, from the Start menu, click Programs, IBM Cognos 8 Analytic
Applications, IBM Cognos 8 Adaptive Warehouse.
If you see the Welcome page of Adaptive Warehouse, your installation is working.
Steps for Adaptive Analytics
1. Start the IBM Cognos 8 service.
2. To start Adaptive Analytics, from the Start menu, click Programs, IBM Cognos 8 Analytic
Applications, IBM Cognos 8 Adaptive Analytics.
If you see the Welcome page of Adaptive Analytics, your installation is working.
Installation and Configuration Guide 101
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Import the Splash Screen for the IBM Cognos 8 Analytic Applications Portal
Page
The IBM Cognos 8 deployment archive that is created by IBM Cognos 8 Analytic Applications
does not include the splash screen for the IBM Cognos 8 portal. While you can still traverse folders
and run reports, you can manually import the splash screen to improve the IBM Cognos 8 Analytic
Applications portal experience.
Steps
1. Go to the apps_location/analyticcontent/staticcontent directory.
2. Copy the file splash.zip to the c8_location/deployment directory.
3. Start IBM Cognos 8 by typing the following in the Address box of your web browser:
http://your computer name/IBM Cognos8
4. In the IBM Cognos 8 Welcome screen, click IBM Cognos Connection.
5. From the Tools menu, click Content Administration.
6. Click New Import
.
7. Select the Splash deployment archive, and then click Next.
Tip: If the Splash deployment archive is not listed, open IBM Cognos Configuration and confirm
that you copied splash.zip to the location specified in the Deployment file location of the
Environment group.
8. Click Next to accept the default name and description.
9. Select the check box adjacent to the Analytic Applications folder in the Name column.
10. Ensure the Disable after input check box is cleared, and then click Next.
11. Click Next to accept the default general options.
12. Click Next to accept the summary.
13. Click Save and run once, and then click Finish.
14. Click Run.
15. Click OK to start the import.
After importing the splash screen, you can also manually create an IBM Cognos 8 portal tab, which
will make the user experience even better. For more information, see the IBM Cognos Connection
User Guide.
102
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Copy Image Files for Adaptive Analytics Report Icons
You must copy the image files, used for the report icons in Adaptive Analytics, to the correct location
so that they appear correctly in reports.
Steps
1. Go to apps_location/webcontent/skins/adaptive, and copy the contents of this directory.
2. Paste the copied contents to the c8_location/webcontent/skins directory.
Change the Default Configuration Settings
When you install IBM Cognos 8 Analytic Applications, the installation uses default configuration
settings. You may decide to change some settings to better suit your environment. You can change
the settings during the initial configuration, or later, using IBM Cognos Configuration.
Some of the optional configuration tasks you can do include:
●
change a URI
●
configure cryptographic settings
●
configure the reporting components to use IBM Cognos Application Firewall
●
configure temporary file properties
●
update file location properties on Windows Vista
●
configure the gateway to use a namespace
●
enable and disable services
●
specify the amount of resources the IBM Cognos 8 service uses
If you install the IBM Cognos 8 components on more than one computer, ensure that you configure
all computers where you install Content Manager before you change default configuration settings
on other computers.
If you change the value of a property, you must save the configuration and then restart the IBM
Cognos 8 service to apply the new settings to your computer.
Change a URI
You change the URI for one of the environment settings if
●
your installation is distributed
●
you change the gateway
●
there is a port conflict
You can change certain elements in a URI depending on your environment.
A URI contains the following elements:
●
for a Content Manager URI, Dispatcher URI for external applications, or dispatcher URI
Installation and Configuration Guide 103
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
protocol: //host_name_or_IP:port/context_root/alias_path
●
for a Gateway URI or a Web content URI
protocol: //host_name_or_IP:port/virtual_directory/gateway_application
OR
protocol: //host_name_or_IP:port/context_root/alias_path
Element
Examples
Description
protocol
http
Specifies the protocol used to request and
transmit information.
host name or IP
localhost or 192.168.0.1 Specifies the identity of the network host.
You can use an IP address, a computer
name, or a fully qualified domain name.
In a distributed installation, you must
change the localhost element of a URI.
port
9300 or 80
Specifies the port on which the host system
listens for requests.
The default port for Tomcat is 9300. The
default port for a Web server is 80.
context root
p2pd
Used by Tomcat to determine the context
of the application so that the request can
be routed to the correct Web application
for processing.
alias path
servlet/ dispatch
Used by the application server to route a
request to the correct component within a
Web application.
The alias path must not be modified or IBM
Cognos 8 Adaptive Applications Framework components will not function correctly.
virtual directory
cognos8/
Used by the Web server to map a virtual
directory or alias to a physical location.
For example, in the default Gateway URI
of http://localhost:80/cognos8/cgi-bin/
cognos.cgi, the virtual directory is
cognos8/cgi-bin.
104
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Element
Examples
Description
gateway application
cognos.cgi
Specifies the name of the IBM Cognos
gateway application that is used.
For example, if you use the default Common Gateway Interface (CGI), the gateway
application is cognos.cgi.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window click the appropriate group or component:
●
To change an element for the dispatcher, click Environment.
●
To change an element for the local log server, under Environment, click Logging.
3. In the Properties window, click the Value box next to the URI property that you want to change.
4. Select the element and type the new information.
Tips:
●
To change the port used by the local dispatcher, 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.
●
If you change the dispatcher port in the dispatcher URI, ensure that you specify the new
port number when you configure remote computers that use the dispatcher or Content
Manager services.
5. From the File menu, click Save.
Create Another Instance of the Cognos Content Database
If available for your application, you can create another content store database in Cognos Content
Database.
During Cognos Content Database installation, a database is created and IBM Cognos 8 is already
configured to use that database.
If you want to install Cognos Content Database on a separate server, you must do so before you
configure Content Manager. In the installation wizard, clear all components and select only Cognos
Content Database.
Steps for Cognos Content Database
1. On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
2. Start the ij utility using the ij.bat or ij.ksh script.
Installation and Configuration Guide 105
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
The ij utility is a command line utility for creating and managing Cognos Content Database.
3. Create a database by typing the following ij utility command:
connect 'jdbc:derby://host:port/db_name;create=true;user=username; password=password';
For example, to create a database named contentstore on the localhost computer on port
number 1527 as a user named cognos with a password of cognos, you would type
connect 'jdbc:derby://localhost:1527/contenstore;create=true;user=cognos;password=cognos';
The database name is case sensitive.
The database files are located in the c8_location\contentstore directory.
4. Close the ij utility by typing the following command:
disconnect;
You can also change the default user and password for Cognos Content Database.
Change the Default User and Password for Cognos Content Database
If you install Cognos Content Database, the default database that is created is given a user ID and
password. We recommend that you change this user ID and password.
Administration tasks for Cognos Content Database are performed using a utility named ij. For
information about this utility, see the Apache Derby documentation. The documentation is available
in the c8_location\derby10.1.2.1\docs directory where you installed Cognos Content Database.
Steps to Change the Default User Password
1. On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
2. Start the ij utility using the ij.bat or ij.ksh script file.
The ij utility is a command line utility for creating and managing Cognos Content Database.
3. Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your
Cognos Content Database.
The default database is named cm. The database name is case sensitive.
4. Change the default password for the user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', 'NewPassword');
The new password must be used for the next connection to the database.
5. Close the ij utility by typing the following command:
106
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
disconnect;
Steps to Create a New User and Password
1. On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
2. Start the ij utility using the ij.bat or ij.ksh script file.
3. Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your
Cognos Content Database.
The default database is named cm. The database name is case sensitive.
4. Create a new user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.NewUser',
'NewUserPassword');
5. Give the new user full access to the database by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers','cognos, NewUser');
The property that you are changing, the list of users, is a comma-delimited field. In this step,
you are including the new user in the list of users with full access. The default user, cognos, is
still part of the list of users with full access. You can remove the cognos user.
6. Close the ij utility by typing the following command:
disconnect;
Steps to Remove a User
1. On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
2. Start the ij utility using the ij.bat or ij.ksh script file.
3. Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=NewUser; password=NewUserPassword';
4. Choose the kind of user that you want to remove:
●
To remove a user from the list of users with full access, type the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers', 'NewUser');
You omit the user name from the list of users with full access. For example, the above
command removes the default cognos user and keeps the new user that you just created.
Installation and Configuration Guide 107
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
To remove a user from the database, type the following ij utility command and omit the
user password:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', '');
This command removes the password for the default cognos user, which also removes the
user from the database.
5. Close the ij utility by typing the following command:
disconnect;
Change Cryptographic Settings
You can change cryptographic and cryptographic provider settings to better suit your environment.
Cognos 8 Analytic Applications requires a cryptographic provider. If you delete the default cryptographic provider, you must configure another provider to replace it. By default, the cryptographic
provider uses keys up to 56 bits in length for data encryption and secure sockets layer (SSL) protocol.
Some of the common settings that you can change include:
●
advanced algorithms
These include signing and digest algorithms.
●
common symmetric key store (CSK) properties
The CSK is used 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.
In a distributed installation, IBM Cognos 8 Adaptive Applications Framework computers obtain
the cryptographic keys from Content Manager. If you reinstall Content Manager, the cryptographic
keys change and you must delete the cryptographic keys on all other IBM Cognos 8 Adaptive
Applications Framework computers. You must then re-save the configuration on each computer
to ensure that each of the computers acquire the new cryptographic keys from Content Manager.
All IBM Cognos 8 Adaptive Applications Framework components must be configured with the
same cryptographic provider settings.
Steps for Cryptographic Settings
1. Start IBM Cognos Configuration.
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:
108
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
Only on the default active Content Manager computer, under CSK settings, set Create
symmetric key store to True. On all other computers, including standby Content Manager,
you must change Create symmetric key store to False.
●
On computers that do not contain Content Manager, if you do not want to store the CSKs
locally, under CSK settings, change Store symmetric key locally to False.
When Store symmetric key locally is False, the key is retrieved from Content Manager when
required. The Common symmetric key store location property is ignored.
●
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. This property must
be true to ensure all transmissions are encrypted.
●
If you want to change the digest algorithm, for the Digest algorithm property, select another
value.
4. From the File menu, click Save.
5. Test the cryptographic provider on a gateway computer only. In the Explorer window, rightclick Cryptography and click Test.
Components check the availability of the symmetric key.
After you configure the cryptographic provider, passwords in your configuration and any data you
create are encrypted.
Steps for Cryptographic Provider Settings
1. Start IBM Cognos Configuration.
2. In the Explorer window, under Security, Cryptography, click IBM Cognos.
●
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 want to use a third-party certificate authority, under Certificate Authority settings,
change Use third party CA to True.
You must also ensure that you use the same values for the -k parameter as you used for
the Signing key store location and Encryption key store location properties.
Important: The Confidentiality algorithm value determines how data is encrypted. For example,
database passwords entered in IBM Cognos Configuration are encrypted when you save the
configuration. The algorithm selected when the data is encrypted must also be available for the
data to be decrypted at a later date.
The availability of confidentiality algorithms can change if there are changes to your environment. For example, if your Java Runtime Environment (JRE) has changed or if you have installed
third-party cryptographic software on the computer. If you have made changes to a computer,
Installation and Configuration Guide 109
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
such as upgraded the JRE or installed software that has upgraded the JRE, this may affect the
availability of confidentiality algorithms. You must ensure that the Confidentiality algorithm
that was selected when the data was encrypted is also available when you want to access the
data.
3. From the File menu, click Save.
If you use a third-party Certificate Authority (CA) server, you must now configure IBM Cognos 8
Analytic Applications components to use the CA.
Configure Reporting Components to Use IBM Cognos Application Firewall
IBM Cognos Application Firewall analyzes and validates HTTP and XML requests before they are
processed. IBM Cognos Application Firewall may modify these HTTP and XML requests.
IBM Cognos Application Firewall protects the IBM Cognos Web products from malicious data.
The most common forms of malicious data are buffer overflows and cross-site scripting attacks
(XSS links), either through script injection in valid pages or redirection to another Web site.
You can change settings for XSS checking. You can also add host and domain names to the IBM
Cognos list of validated names.
You can track firewall activity by checking the log file, which contains rejected requests only. If
firewall validation fails, you can check the log file to find where the failure occurred. By default,
log messages are stored in the c8_location/logs/cogserver.log file. In a gateway-only installation,
the file is named caf.log. If you configure a destination for log messages, IBM Cognos Application
Firewall log messages are sent to the specified destination.
IBM Cognos Application Firewall also has a Secure Error feature, which gives administrators control
over which groups or users can view detailed error messages. For more information, see the IBM
Cognos 8 Administration and Security Guide.
Steps
1. On each computer identified as an external dispatcher, start IBM Cognos Configuration.
2. In the Explorer window, under Security, click IBM Cognos Application Firewall.
3. In the Properties window, for the CAF enabled property, set the appropriate values.
By default, IBM Cognos Application Firewall is enabled.
Important: The IBM Cognos Application Firewall is an essential component of IBM Cognos
security, helping to provide protection against penetration vulnerabilities. Disabling the IBM
Cognos Application Firewall will remove this protection; therefore, this should not be done
under normal circumstances.
The CAF enabled property must have the same setting on all IBM Cognos 8 computers. If it is
disabled on some computers and enabled on other computers, unexpected behavior and product
errors may result.
4. In the Properties window, to use third-party cross site scripting (XSS):
●
110
For the Is third party XSS checking enabled property, change the value to True.
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
For the Third party XSS characters property, add any additional characters that are prohibited by SiteMinder. The default characters are >, <, and ’.
5. Add host and domain names to the IBM Cognos list of validated names:
●
For the Valid domains and hosts property, click the value and then click the edit button.
●
In the Value - Valid domains or hosts dialog box, click Add.
●
In the blank row of the table, click and then type the host or domain name.
●
Repeat the previous two bulleted steps for each name to be added.
●
Click OK.
IBM Cognos Application Firewall validates domain and host names to protect URLs that are
created. By default, IBM Cognos Application Firewall considers domain names derived from
the environment configuration properties to be safe domain names. You can add names
manually to the list of valid domains and hosts. Adding names is useful when you need to
redirect requests to non-IBM Cognos computers using the Back or Cancel functions within the
web browser.
6. Save the configuration.
Configure Temporary File Properties
You can change the location where components store recently viewed reports, and you can choose
to encrypt their content. By default, components store temporary files in the c8_location/temp
directory and the files are not encrypted.
We recommend that you first set up read-only access for all users to the c8_location directory.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. In the Properties window, for the Temporary files location 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 IBM Cognos 8 Adaptive Applications Framework
components run have the appropriate privileges to the temporary files location. For example,
for Windows, full control privileges.
Update File Location Properties on Windows Vista
If you install Adaptive Analytics Framework components on Windows Vista, you must change file
locations properties in IBM Cognos Configuration on both client and server computers so that IBM
Cognos 8 can use a single data location for all users.
Installation and Configuration Guide 111
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Windows Vista has a security enhancement that restricts multiple users from sharing data locations.
You can define environment variables and use them in IBM Cognos Configuration when specifying
file locations. This allows you to direct applicable files to an area that will be accessible by IBM
Cognos 8 users. On Windows, two environment variables are preset for users: one for all users and
one for the specific user.
Because the environment variables represent system root locations, we recommend that you also
include the root directory name of the installation location when you specify file locations in IBM
Cognos Configuration. The default root directory for IBM Cognos 8 is c8.
Steps on Modeling Computers
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. In the Properties window, click Deployment files location.
4. Specify the file location relative to the /bin directory. Replace the relative path element “..”
with “../../../../path” and add the appropriate environment variable.
For example, if you install IBM Cognos 8 in the directory C:/Programs Files/cognos/c8, and
you want a path to C:/Users/Public/c8, enter ../../../../Users/Public/c8 as the path.
●
●
On Windows, use the preset environment variables as shown in the table.
Operating system Per user
All users
Windows XP
%APPDATA%
%ALLUSERSPROFILE%
Windows Vista
%LOCALAPPDATA%
%PUBLIC%
On UNIX, use the environment variables that you set in advance.
5. Repeat step 4 for the following properties:
●
Under Environment,
- Data files location
- Map files location
- Temporary files location
●
Under Environment, Logging, File,
- Log file location
●
Under Cryptography,
- Common symmetric key store location
●
Under Cryptography, IBM Cognos,
- Certificate location
112
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
- Signing key store location
- Encryption key store location
6. From the File menu, click Save.
Steps on Server Computers
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. In the Properties window, click Deployment files location.
4. Replace the relative path element, “..”, with the appropriate environment variable and root
directory:
●
●
On Windows, use the preset environment variables as shown in the table.
Operating system Per user
All users
Windows XP
%APPDATA%
%ALLUSERSPROFILE%
Windows Vista
%LOCALAPPDATA%
%PUBLIC%
On UNIX, use the environment variables that you set in advance.
For example,
On Windows XP, to set a single file location for all users, specify %ALLUSERSPROFILE%/
c8/deployment.
On UNIX, if you set an environment variable such as MYHOME for single users, specify
$MYHOME/c8/deployment.
5. Repeat step 4 for the following properties:
●
Under Environment,
- Data files location
- Map files location
- Temporary files location
●
Under Environment, Logging, File,
- Log file location
●
Under Cryptography,
- Common symmetric key store location
●
Under Cryptography, IBM Cognos,
- Certificate location
- Signing key store location
Installation and Configuration Guide 113
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
- Encryption key store location
6. From the File menu, click Save.
The environment variables are resolved when the file locations are accessed during system activities.
Configure the Gateway to Use a Namespace
If IBM Cognos 8 Adaptive Applications Framework components use multiple namespaces or if
anonymous access is enabled and the components use one namespace, you can configure the gateway
to connect to one namespace. Users logged onto the Web server where the gateway is located are
not 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 IBM Cognos Configuration.
2. In the Explorer window, click Environment.
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.
4. From the File menu, click Save.
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.
Note: The default values for dispatcher service and presentation service are false on computers that
have the Content Manager only installed. On all other types of installations, the default values are
true.
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
1. Start IBM Cognos Configuration.
2. In the Explorer window, under Environment, click IBM Cognos 8 service.
114
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
3. In the Properties window, click the Value next to 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.
5. From the File menu, click Save.
Specify Resources for the IBM Cognos 8 Service
To improve performance in a distributed environment, you can change the amount of resources
that the IBM Cognos 8 service uses by choosing a configuration template.
By default, the IBM Cognos 8 service is configured to use minimal memory resources to optimize
startup time.
The IBM Cognos 8 service is available only on the computers where you installed Content Manager
or the Report Server.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window, under Environment, IBM Cognos 8 service, right-click IBM Cognos 8,
and click Delete.
This deletes the default configuration template for the service.
3. Right-click IBM Cognos 8 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.
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.
7. From the File menu, click Save.
Installation and Configuration Guide 115
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Change the Notification Database
By default, the notification server uses the same database that Content Manager uses for the content
store. You can use a separate database for notification in situations where you run large volumes
of batch reports and email.
Using a separate database for notification involves the following tasks:
❑
Create a notification database.
For DB2, Oracle, Microsoft SQL Server, or Sybase, use the same procedure that was used to
create the content store database, "Guidelines for Creating the Content Store" (p. 69).
For DB2 on z/OS, use the instructions in "Suggested Settings for Creating the Content Store in
DB2 on z/OS" (p. 72).
❑
Set up the database connectivity. You can use the same procedure as to set the connectivity for
the content store database, "Set Up Database Connectivity for the Content Store Database" (p. 44).
❑
Change the connection properties for the notification database.
Suggested Settings for Creating a DB2 Notification Database on z/OS
The database you create for the notification database must contain some recommended configuration
settings.
To ensure a successful installation, use the following guidelines when creating the notification
database.
Use the following checklist to help you help you set up the notifications database in DB2 on z/OS.
❑
Create a database instance, storage group, and a user account for the notification database.
A user must have permissions to create and delete tables in the database.
IBM Cognos 8 uses the credentials of the user account to communicate with database server.
❑
Ensure you reserve a buffer pool with a page size of 32 k, and a second one with a page size
of 4 k for the database instance.
❑
Administrators must run a script to create tablespaces to hold Large Objects and other data
for the notification database to use the tablespaces. For information about running the script,
see "Create Tablespaces for the DB2 Notification Database on z/OS" (p. 116).
❑
Your database administrator must back up IBM Cognos 8 databases regularly because they
contain the IBM Cognos data. To ensure the security and integrity of databases, protect them
from unauthorized or inappropriate access.
Create Tablespaces for the DB2 Notification Database on z/OS
A database administrator must run a script to create a set of tablespaces required for the notification
database. The script must be modified to replace the placeholder parameters with ones that are
appropriate for your environment.
116
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Ensure that you use the naming conventions for DB2 on z/OS. For example, all names of parameters
must start with a letter and the length must not exceed eight characters. For more information, see
the IBM DB2 Information Center.
Steps
1. Connect to the database as a user with privileges to create and drop tablespaces and to allow
execution of SQL statements.
2. Open the NC_TABLESPACES.sql script file and use the following table to help you to replace
the placeholder parameters with ones appropriate for your environment.
Not all of the parameters listed are in the script, but may be added in the future.
Parameter Name
Description
NCCOG
Specifies the name of the notification database.
DSN8G810
Specifies the name of the storage group.
BP32K
Specifies the name of the buffer pool.
3. Save and run the script.
The notification database is created. You can now change the notification database in IBM Cognos
Configuration, (p. 117).
Change the Connection Properties for the Notification Database
After you create a separate database for notification, you must configure IBM Cognos 8 to use the
new database.
You must configure all Content Managers and Application Tier Components to use the same
notification database.
Steps
1. In each location where Content Manager or Application Tier Components is installed, start
IBM Cognos Configuration.
2. In the Explorer window, under Data Access, click Notification.
3. Identify the database that is used for notification:
●
In the Explorer window, right-click Notification and select New resource, Database.
●
Type a name for the database resource.
●
Select the type of database from the pull-down menu.
●
Click OK.
4. In the Properties window, enter the values for the notification database resource.
Installation and Configuration Guide 117
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
5. From the File menu, click Save.
6. Test the notification. In the Explorer window right-click Notification and click Test.
IBM Cognos 8 tests the database connection and tests the mail server connection.
If you have been using the content store database for notification, the schedules will be replicated
in the tables of the new notification database.
Important: Ensure that the values used to identify the notification database resource are the same
on all Content Manager and Application Tier Components computers. To use the default notification
database, you do not have to edit the values in the Properties window.
Configure the SSL Protocol
The Secure Sockets Layer (SSL) protocol is used to secure communication between IBM Cognos
components installed on the same computer or on different computers.
In addition, you may want to set up SSL connections between IBM Cognos components and other
servers. You must ensure that SSL is set up for the other servers and then you must set up a shared
trust between IBM Cognos components and the other servers.
After configuring the SSL protocol, you can select and rank cipher suites, which control the quality
of protection used in the SSL connection.
To configure SSL protocol, do the following:
❑
Configure SSL for IBM Cognos 8 Analytic Applications.
❑
Set up shared trust between IBM Cognos severs and other servers.
❑
Select and rank Cipher Suites for SSL.
Configure SSL for IBM Cognos 8 Adaptive Applications Framework
You can configure IBM Cognos components to use the 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, IBM Cognos 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 IBM Cognos
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. You must also configure
the Content Manager URIs and the dispatcher URI for external applications to use the same protocol
and port as the external dispatcher.
118
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
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 URIs, Dispatcher URI for external applications, and
Gateway URI to use SSL, if required.
Tomcat Connectors
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.
If the internal and external dispatcher URIs use different protocol or ports, the internal dispatcher
port is accessible only to the components on the local computer. The internal dispatcher URI must
also specify localhost.
Single Computer Installations
In single computer installations, if you are running IBM Cognos 8 without SSL, you must stop the
service before adding SSL to your configuration. After you save the configuration with SSL settings,
you can restart the service.
Distributed Installations
In distributed installations, if you are using the IBM Cognos certificate authority service, you must
first configure all IBM Cognos computers to use the non-secure (http) protocol before you configure
IBM Cognos components 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 the default active 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 default active Content Manager
computer and starting the services, you ensure that the certificate authority service on the default
active Content Manager computer can issue certificates to other computers in the IBM Cognos
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 IBM Cognos components are
working properly. After you test your installation, you can configure the SSL protocol.
When you configure IBM Cognos 8 to use the SSL protocol, ensure that you first configure the
default active Content Manager computer to use the protocol and start the services on the default
active Content Manager computer. After you do this, you can configure the SSL protocol on other
IBM Cognos computers in your environment.
Add a Computer to an Installation
If you add a computer to an SSL-enabled environment, you will be prompted to temporarily accept
trust for a certificate when you save the configuration. Accepting the temporary certificate will
allow permanent trust to be established with the Content Manager computer.
Installation and Configuration Guide 119
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Add a Component to a Computer
You can later add a component to the same location as other IBM Cognos components. If you add
the component to a different location on the same computer as other IBM Cognos components,
you will be prompted to temporarily accept trust for a certificate when you save the configuration.
Accepting the temporary certificate will allow permanent trust to be established between the new
component and the Content Manager computer.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. 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 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.
If you use Tomcat, the Internal dispatcher URI property must also specify localhost.
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.
If you use Tomcat, the Internal dispatcher URI property must also specify localhost.
The ports in the two dispatcher URIs must be different.
●
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.
4. Configure the SSL protocol for the other environment URIs, including the Content Manager
URIs, the Dispatcher URI for external applications, 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.
5. In the Explorer window, click Security, Cryptography.
6. To use SSL protocol, you must specify passwords for the IBM Cognos 8 encryption key stores.
There are more settings under Security, Cryptography, IBM Cognos.
120
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
7. From the File menu, click Save.
Set Up Shared Trust Between IBM Cognos Servers and Other Servers
If you want to use the default IBM Cognos certificate authority and you want to use SSL for connections from other servers to IBM Cognos servers, you must add the IBM Cognos certificate to
the trust store on the other servers.
Note: If you use browsers to connect to IBM Cognos components, the browsers automatically
prompt users to update their trust stores.
If you want the connection between IBM Cognos servers and the other server to be mutually
authenticated, you must also copy the certificate from your certificate authority to the trust store
for IBM Cognos servers.
If you have configured IBM Cognos components to use a third-party certificate authority (CA),
you do not have to set up shared trust between IBM Cognos server and other servers.
Steps to Copy the IBM Cognos Certificate to Another Server
1. Go to the c8_location/bin directory.
2. Extract the IBM Cognos certificate by typing the following command:
●
For UNIX, type
ThirdPartyCertificateTool.sh -E -T -r destination_file -D c8_location/configuration/
signkeypair -p password
●
For Windows, type
ThirdPartyCertificateTool.bat -E -T -r destination_file -D c8_location/configuration/
signkeypair -p password
3. Import the certificate to the trust store on your server.
For information on updating the server trust store, see the documentation for your server.
Steps to Copy the CA Certificate to IBM Cognos Servers
1. Copy the certificate from your certificate authority to a secure location on the IBM Cognos
server.
Ensure that the CA certificate is in Base-64 encoded X.509 format.
2. Import the CA certificate by typing the following command:
●
For UNIX, type
ThirdPartyCertificateTool.sh -T -i -r CA_certificate_file -D c8_location/configuration/
signkeypair -p password
●
For Windows, type
ThirdPartyCertificateTool.bat -T -i -r CA_certificate_file -D c8_location/configuration/
signkeypair -p password
Installation and Configuration Guide 121
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Select and Rank Cipher Suites for SSL
An SSL connection begins with a negotiation in which the client and server present a list of supported
cipher suites in a priority sequence. A cipher suite provides the quality of protection for the connection. It contains cryptographic, authentication, hash, and key exchange algorithms. The SSL protocol
selects the highest priority suite that the client and the server both support.
IBM Cognos provides a list of supported cipher suites for SSL. You can eliminate cipher suites that
do not meet your requirements and then assign a priority, or preference, to the remaining cipher
suites. The selected cipher suites are presented in priority sequence for the client and server sides
of the negotiation. At least one of the selected cipher suites between the client and server platforms
must match.
The list of supported cipher suites is dynamically generated on each computer, and depends on the
Java Runtime Environment (JRE) or if you have third-party cryptographic software installed on
the computer. If you have made changes to a computer, such as upgraded the JRE or installed
software that has upgraded the JRE, this may affect the supported cipher suites available on that
computer. If you no longer have a supported cipher suite that matches the other computers in your
environment, you may have to change the JRE on the computer to match the other computers in
your environment.
Steps
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Cryptography, IBM Cognos.
3. In the Properties window, click the Value column for the Supported ciphersuites property.
4. Click the edit button.
●
To move a cipher suite to the Current values list, click the check box in the Available values
list and then click Add.
●
To move a cipher suite up or down in the Current values list, click the check box and then
click the up or down arrows.
●
To remove a cipher suite from the Current values list, click the check box and then click
Remove.
5. Click OK.
6. From the File menu, click Save.
Set Data Manager Runtime Data and Log File Locations
You use IBM Cognos Configuration if you want to change the data and log file locations for Data
Manager Runtime log files.
Steps
1. In IBM Cognos Configuration, expand Environment, and click Data Manager.
122
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
2. Click the Value box, and select a location for the data and log files.
Configuring Log Messages
Log messages are an important diagnostic tool for investigating the behavior of IBM Cognos 8. In
addition to error messages, log messages provide information about the status of components and
a high-level view of important events. For example, log messages can provide information about
attempts to start and stop services, completion of processing requests, and indicators for fatal errors.
Audit logs, which are available from a logging database, provide information about user and report
activity.
The IBM Cognos 8 services on each computer send information about errors and events to a local
log server. A local log server is installed in the c8_location/logs folder on every IBM Cognos 8
computer that contains Content Manager or Application Tier Components. Because the log server
uses a different port from the other IBM Cognos 8 components, it continues to process events even
if other services on the local computer, such as the dispatcher, are disabled.
The following workflow shows the tasks that are required to prepare for logging.
Configure logging
Plan log message processing
Set up logging
❑
During planning, determine the logging configuration that is suitable for your environment.
For example, evaluate various log message destinations, such as remote log servers and log
files, such as the UNIX or Linux syslog or the Windows NT Event log, in addition to the local
log file. You can also send only audit logging information to a database. Consider security,
such as methods available for protecting log files from system failures and user tampering. For
information about planning, see the Architecture and Deployment Guide.
❑
During configuration, define the startup properties for logging, such as connection settings for
databases. You must also create a logging database if you plan to collect audit logs. If communication between a local log server and a remote log server must be secured, make the appropriate configuration changes on both IBM Cognos 8 computers. For information about configuring logging, see the Installation and Configuration Guide.
❑
When setting up logging, specify the level of detail to log to focus messages on the information
that is relevant in your organization. Audit reports may also be set up to track user and report
activity. For information about setting up logging, see the Administration and Security Guide.
For information about using log messages to solve problems and resolving logging-related issues,
see the Troubleshooting section of the Administration and Security Guide.
Guidelines for Creating a Logging Database
You can create a database to store log messages. Creating a logging database involves the following
tasks:
❑
Create a logging database.
Installation and Configuration Guide 123
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
For DB2, Oracle, Microsoft SQL Server, or Sybase, use the same procedure that was used to
create the content store database "Guidelines for Creating the Content Store" (p. 69).
For DB2 on z/OS, use the instructions in "Suggested Settings for Creating the DB2 Logging
Database on z/OS" (p. 124).
❑
Set up the database connectivity.
❑
Specify the log messages destination.
Suggested Settings for Creating the DB2 Logging Database on z/OS
The database you create must contain some recommended configuration settings.
Use the following checklist to help you set up the logging database on DB2.
❑
Log on to the z/OS system as a user with administrator privileges in DB2 on z/OS.
❑
Create a database instance, storage group, and a user account for the content store. IBM
Cognos 8 uses the credentials of the user account to communicate with the database server.
❑
Ensure that you allocate a buffer pool with a page size of 8 KB for the database instance.
❑
For a logging database in DB2 on z/OS, administrators must run a tablespace script to create
tablespaces to hold large objects and other data for the logging database, and then grant user
rights to the table. For information about running the tablespace script, see "Create Tablespaces
for DB2 Logging Database on z/OS " (p. 124).
Create Tablespaces for DB2 Logging Database on z/OS
A database administrator must run a script to create a set of tablespaces required for the logging
database. The script must be modified to replace the placeholder parameters with ones that are
appropriate for your environment.
Ensure that you use the name convention for DB2 on z/OS. For example, all names of parameters
must start with a letter and the length must not exceed eight characters. For more information, see
the IBM DB2 Information Center.
Steps
1. Connect to the database as a user with privileges to create and drop tablespaces and to allow
execution of SQL statements.
2. Open the LS_tablespace_db2zOS.sql script file and use the following table to help you to replace
the generic parameters with ones appropriate for your environment.
Not all of the parameters listed are in the script, but may be added in the future.
124
Parameter Name
Description
IPFSCRIPT_DATABASE
Specifies the name of the logging database.
IPFSCRIPT_STOGROUP
Specifies the name of the storage group.
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Parameter Name
Description
IPFSCRIPT_TABLESPACE
Specifies the name of the tablespace that contains
the base tables in the logging database.
This tablespace is not for Auxiliary tables.
IPFSCRIPT_LOB_TABLESPACE
Specifies the name of the tablespace that is allocated
for auxiliary tables.
IPFSCRIPT_BP
Specifies the name of the 8 k buffer pool that is
allocated for regular objects.
IPFSCRIPT_USERNAME
Specifies the user account that accesses the logging
database.
3. Save and run the script.
4. Grant the IBM Cognos user rights to the tablespaces that were created when you ran the LS_
tablespace_db2zOS.sql script file:
●
Open the LS_rightsGrant_db2zOS.sql script file, which is located in the
c8_location\configuration\schemas\logging\db2zOS directory.
●
Replace the parameter values with those that are appropriate for your environment.
Tip: Ensure you use the same values that you used when you created the buffer pools and
user account.
●
Save and run the LS_rightsGrant_db2zOS.sql script.
The logging database is created.
Set Up the Database Connectivity for the Logging Database
After you create a database for audit logs, additional steps are required to set up the database client
if you use Oracle, DB2, or Sybase as the database server.
You cannot use Cognos Content Database as a logging database.
Note: In a distributed environment, the local log server on an Application Tier Component computer
may send log messages to a remote log server, which then sends messages to the logging database.
For Oracle, Sybase, and DB2, the appropriate JDBC driver and database client software (DB2 only)
is required only on the Application Tier Components computer with the remote log server that
connects to the logging database.
Microsoft SQL Server Database
If you use a Microsoft SQL Server database, the JSQLConnect.jar file is installed to the appropriate
location by default. The only additional step is to ensure that the Microsoft SQL Server uses TCP/IP
connectivity.
Installation and Configuration Guide 125
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Oracle or Sybase Database
If you use an Oracle or Sybase database, you must set up the JDBC driver on all Application Tier
Components computers with a connection to the logging database. You must also set up the JDBC
driver on the Content Manager computer, unless you are using the same type of database for the
log messages as you use for the content store.
DB2 Database
IBM Cognos 8 uses JDBC connectivity to access the database used for the logging database.
For a DB2 database, you must set up the database client software and the JDBC driver on all
Application Tier Components computers with a connection to the logging database. You must also
set up the database client software and the JDBC driver on the Content Manager computer, unless
you are using the same type of database for the log messages as you use for the content store.
If you use DB2 on Windows, Linux or UNIX as your logging database you must choose whether
to use the type 2 or type 4 JDBC driver depending on how you want to connect to the logging
database.
For more information about JDBC driver options for a DB2 database, see "JDBC Driver Options
for Using DB2 Database as a Content Store" (p. 80).
Steps for Oracle
1. On the computer where Oracle is installed, go to the ORACLE_HOME/jdbc/lib directory.
2. Copy the appropriate JAR file to the c8_location/webapps/p2pd/WEB-INF/lib directory on
computers where Content Manager or Application Tier Components is installed.
●
If you use Java 1.4, copy the ojdbc14.jar file
●
If you use Java 1.5, copy the ojdbc5.jar file
If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or
ojdbc5.jar file.
Steps for DB2 on Linux, UNIX, and Windows
1. If you are using type 2 JDBC connectivity, install the DB2 client software on the Content
Manager computers.
If you use type 4 JDBC connectivity for DB2, you are not required to install the DB2 client
software where Content Manager is installed.
For more information about the differences between type 2 and type 4 drivers, see "JDBC
Driver Options for Using DB2 Database as a Content Store" (p. 80).
2. If you are using type 2 JDBC connectivity, and the logging database is on a different computer
than log server, configure a database alias to the logging database.
126
●
On Windows, run the DB2 Client Configuration Assistant.
●
On UNIX or Linux, use the DB2 command line interface.
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Note: If the logging database and log server are on the same computer, the logging database
name automatically becomes the alias.
3. On Windows, stop the DB2 services and the HTML Search Server.
4. Copy the following files from the DB2_installation/sqllib/java directory to the c8_location/
webapps/p2pd/WEB-INF/lib directory.
●
the universal driver file, db2jcc.jar
●
the license file
for DB2 on Linux, UNIX, or Windows, db2jcc_license_cu.jar
for DB2 on z/OS, db2jcc_license_cisuz.jar
Tip: To check the driver version, run the command java -cp path\db2jcc.jar com.ibm.db2.jcc.
DB2Jjcc -version.
5. On Windows, restart the DB2 services and the HTML Search Server.
6. Repeat this entire procedure on the IBM Cognos 8 computers where the software must be
installed.
Steps for DB2 on z/OS
1. Go to the DB2_installation/sqllib/java directory.
2. Copy the following files to the c8_location/webapps/p2pd/WEB-INF/lib directory and c8_location/bin directories.
●
the universal driver file, db2jcc.jar
●
the license file, for example, db2jcc_license_cisuz.jar
If you are using a DB2 database on z/OS for the logging database, you must use type 4 JDBC
connectivity.
The driver version must be at least JCC 3.7 from Linux, UNIX, or Windows version 9.1 fix pack
or JCC 3.42 from Linux, UNIX, or Windows version 9.5 fix pack 2.
Steps for Sybase
1. On the computer where Sybase is installed, enable the JDBC driver using the following script:
Sybase_location/jConnect-5_5/sp/sql_server12.5.sql
2. Go to the Sybase_location/jConnect-5_5/classes directory.
3. Copy the jconn2.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on the
appropriate Content Manager or Application Tier Components computers.
Installation and Configuration Guide 127
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Log Message Destinations
A local log server is automatically installed when you install Content Manager or the Application
Tier Components. You can specify one or more destinations where the local log server sends log
messages:
●
remote log server
●
file
●
database
●
UNIX or Linux syslog or the Windows NT Event log
For information about log messages, see the Architecture and Deployment Guide.
Remote Log Server
In a distributed installation, you can configure the log server on each IBM Cognos 8 computer to
send log messages to a single remote log server, which acts as a common log server. You can then
configure the common log server to send the log messages to a local file or database on the same
or different computer.
If the remote log server becomes unavailable, log messages are redirected to recovery files on the
local computer in the c8_location\logs\recovery\remote directory. These recovery files have timestamp
information in their file names, and are not readable like regular log files. When the remote log
server becomes available, an automatic recovery process moves all log information to the remote
log server and deletes the local log files.
File
The log server is configured by default to send log messages to the c8_location/logs/cogserver.log
file. If the default log file does not exist when the IBM Cognos 8 service starts, it is created
automatically.
You can configure the log server to send log messages to a different file. If you configure a different
log file, IBM Cognos 8 attempts to automatically create this file on startup, in addition to the default
log file. If the location for the configured log file is different from the c8_location/logs directory,
you must ensure the path to the log file exists before starting the IBM Cognos 8 service. For example,
if you configure the log server to send messages to the c:/log_files/cognos.log file, IBM Cognos 8
attempts to automatically create the cognos.log file in the c:/log_files folder. If this folder does not
exist, IBM Cognos 8 does not create the cognos.log file and no log messages can be recorded in it.
Note that these log messages are not recorded in the default log file. Although IBM Cognos 8
automatically creates the default log file even when another log file is configured, the default log
file is not used as a backup.
Database
The log server can also send audit logs to a database on the same or another computer. Audit logs
provide information about user and report activity.
The logging database has the same configuration and user account requirements as the content
store database. After you configure IBM Cognos 8 components to send messages to a logging
128
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
database, and restart the IBM Cognos 8 service, IBM Cognos 8 components create the required
tables and table fields. You can test the connection to the logging database before you restart the
IBM Cognos 8 service.
Specify the Log Messages Destination
You can configure a type of destination for the log messages, and then configure properties for the
specific destination. You can also configure more than one destination for log messages.
Before you specify a database as a destination, ensure that you
❑
created the logging database
❑
set up the database client
Steps for DB2, Linux, and Windows
1. On the computer where you installed Content Manager or the Application Tier Components,
start IBM Cognos Configuration.
2. In the Explorer window, under Environment, click Logging.
3. In the Properties window, use the following table to help set the log server properties.
Task
Action
Use TCP between IBM Cognos 8 Set the Enable TCP property to True.
components on a computer and
UDP provides faster communication with a lower
its local log server
risk of lost connections than TCP. However, the risk
of losing a local TCP connection is low. TCP is
always used for communication between a local log
server and a remote log server.
Change the number of threads
available to the local log server
Type the value in the Local log server worker threads
property.
Set a value between 1 and 20. The default value of
10 is recommended.
However, if you have a high number of log messages,
you can allocate more threads to improve performance.
Apply UTF-8 encoding for log
messages written to a file
Set the Use UTF8 encoding property to True.
If the IBM Cognos 8 component is using multibyte
encoding, you must set this property to True and use
a UTF-8 editor to view the log file. Otherwise, the
log file may contain unreadable characters.
Installation and Configuration Guide 129
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
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 destination.
6. In the Type list, click the type of destination and then click OK.
7. If the destination is a file, in the Properties window, type the appropriate values for the mandatory and optional properties.
8. If the destination is a remote log server, in the Properties window, type the appropriate values
for the mandatory and optional properties.
If the Internal dispatcher URI of the destination IBM Cognos 8 computer is configured to use
SSL, in the Properties window, set the Enable SSL property to True.
You must later specify the log messages destination when you configure the remote log server.
9. If the destination is a database, in the Explorer window, under Logging, specify the type of
database and its properties, as follows:
●
Right-click the database name, and click New resource, Database.
●
In the Name box, type the name of the destination.
●
In the Type list, click the type of database and then click OK.
●
In the Properties window, type the appropriate values for the mandatory and optional
properties.
For a Microsoft SQL Server database, you can choose to use a port number, such as 1433,
or a named instance as the value for the Database server with port number or instance
name property.
To connect to a named instance, you must specify the instance name as a JDBC URL
property or a data source property. For example, you can type localhost\instance1. If no
instance name property is specified, a connection to the default instance is created.
Note that the properties specified for the named instance, along with the user ID and
password, and database name, are used to create a JDBC URL. Here is an example:
jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required
●
Test the connection to the new database. In the Explorer window, under Environment,
right-click Logging and click Test.
IBM Cognos 8 components connect to the database. If you configured more than one
database for logging messages, IBM Cognos 8 components test all the databases.
10. Repeat steps 5 to 10 for each destination to which you want the log server to send messages.
11. From the File menu, click Save.
12. In the Explorer window, click IBM Cognos 8 service, IBM Cognos 8.
13. From the File menu, click Restart.
130
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
If you selected a database as the destination, IBM Cognos 8 components create the required
tables and fields in the database that you created.
If the destination was a remote log server, configure and start the remote log server. Then restart
the IBM Cognos 8 service on the local computer.
If the destination was a database, you can use IBM Cognos 8 components to run log reports from
the database.
You can also set the logging level, which controls the amount of detail and type of messages that
are sent to a log file or database. For instructions, see the Administration and Security Guide.
Steps for DB2 for z/OS
1. On the computer where you installed Content Manager or the Application Tier Components,
start IBM Cognos Configuration.
2. In the Explorer window, under Environment, click Logging.
3. In the Properties window, use the following table to help set the log server properties.
Task
Action
Use TCP between IBM Cognos 8 Set the Enable TCP property to True.
components on a computer and
UDP provides faster communication with a lower risk
its local log server
of lost connections than TCP.
TCP is used for communication between a local log
server and a remote log server.
Change the number of threads
available to the local log server
Type the value in the Local log server worker threads
property.
Set a value between 1 and 20. The default value of 10
is recommended. However, if you have a high number
of log messages, you can allocate more threads to
improve performance.
Apply UTF-8 encoding for log
messages written to a file
Set the Use UTF8 encoding property to True.
If the IBM Cognos 8 component is using multibyte
encoding, you must set this property to True and use
a UTF-8 editor to view the log file. Otherwise, the log
file may contain unreadable characters.
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 destination.
6. In the Type list, click Database and then click OK.
Installation and Configuration Guide 131
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
7. In the Explorer window, under Logging, right-click the database name, and click New resource,
Database.
8. In the Name box, type the name of the destination.
9. In the Type list, click DB2 database and then click OK.
10. In the Properties window, type the Database server and port number, User ID and password,
and the z/OS Database name.
Ensure that the User ID is the same as the value you specified for the IPFSCRIPT_USERNAME
parameter in the LS_tablespace_db2zOS.sql script file, (p. 124).
11. In the Explorer window, click Local Configuration.
12. In the Properties window, next to Advanced properties, click inside the Value box, and then
click the edit button.
13. Click Add, and then add the following configuration parameter names and values:
Parameter Name
Value
IPFSCRIPT_CREATE_IN
The base tables location.
For example, databaseName.baseTablespaceName
IPFSCRIPT_STOGROUP
The name of the storage group.
IPFSCRIPT_DATABASE
The name of logging database.
IPFSCRIPT_LOB_TABLESPACE The name of the tablespace that is reserved for auxiliary tables in the logging database.
14. From the File menu, click Save.
15. Test the connection to the new database. In the Explorer window, under Environment, rightclick Logging and click Test.
IBM Cognos 8 components connect to the database. If you configured more than one database
for logging messages, IBM Cognos 8 components test all the databases.
Change Global Settings
You change global settings
132
●
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
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
to map content locales
●
to add fonts to your IBM Cognos environment
●
to customize the default time zone
●
to change the encoding for email messages
●
to customize cookie settings
By default, IBM Cognos 8 server components ensure 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.
Important: If you change global settings on one Content Manager computer, you must make the
same changes on the other Content Manager computers.
Customize Language Support to the User Interface
Use the Product Locales 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.
If you change the user interface language of the product, data is not affected.
If you want users to see product documentation in a language other than English, you must install
the Supplementary Languages Documentation. For more information, see "Install Translated Product
Documentation" (p. 48).
Ensure that you install the appropriate fonts to support the character sets and currency symbols
you use. For Japanese and Korean currency symbols to appear correctly, you must install the
additional fonts from the Supplementary Languages Documentation CD.
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions 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.
Installation and Configuration Guide 133
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
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 IBM Cognos 8 show 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 c8_location/bin/ directory.
If you add a currency code that is not supported by IBM Cognos 8, you must manually add it to
the i18n_res.xml file in the c8_location/bin/ directory. Copy this file to each IBM Cognos computer
in your installation.
Adding currencies to the IBM Cognos 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
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
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 where the currency originates.
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.
7. From the File menu, click Save.
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. By default, content locale overrides product locale in the portal
for some content.
If a locale is not required, you can remove it from the list. You must leave at least one content locale
in the list for the report server to operate.
Adding incomplete locales (languages) to the IBM Cognos 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.
134
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
If you view reports in Thai language, digits are not supported.
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
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.
7. From the File menu, click Save.
Map Content Locales
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 or scorecard 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 or
scorecard 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 (enus), or French France (fr-fr).
The following examples shows the method that IBM Cognos 8 use 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). IBM Cognos 8 uses the
locale mapping to determine which report the user sees.
First, IBM Cognos 8 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, IBM Cognos 8 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
Installation and Configuration Guide 135
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
fr. IBM Cognos 8 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, IBM Cognos 8 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. IBM Cognos 8 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), IBM Cognos 8 maps each
locale to en. The user will see the report in the locale setting that IBM Cognos 8 chooses.
Example 3
The report and the user locales do not map to a common language. IBM Cognos 8 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),
IBM Cognos 8 chooses the language.
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
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 the locale to use for a range of keys, use the wildcard character (*) with the
Key value and then, in the Locale Mapping box, type the locale. For example, if you want all
the German keys to use the German locale, type de* in the Key box and type de in the Locale
Mapping box.
6. In the Locale Mapping box, type the language portion of the locale.
136
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
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.
9. From the File menu, click Save.
Map Product Locales
Use the Product Locale 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
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
3. Click the Product Locale Mappings tab.
4. Click Add.
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.
9. From the File menu, click Save.
Installation and Configuration Guide 137
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Customize the Server Time Zone
You can customize the time zone used by Content Manager by selecting a different server time zone
in IBM Cognos Configuration.
Content Manager is configured to use the time zone of your operating system by default. All
scheduled activities in IBM Cognos 8 are set using this time zone. In addition, users in IBM Cognos
Connection use this time zone if they set their preferences for the default time zone. For more
information about setting user preferences in IBM Cognos Connection, see the Administration and
Security Guide.
Steps
1. Start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
3. In the Global Configuration window, click the Server tab.
4. Click the Value column for Server time zone and select another time zone from the list.
5. From the File menu, click Save.
Change Encoding for Email Messages
By default, IBM Cognos 8 uses UTF-8 encoding in emails. This value sets the default encoding used
by the delivery service in this instance for all email messages. You may have older email clients or
send email from IBM Cognos 8 to cell phones and PDAs that do not recognize UTF-8. If so, you
can change the email encoding to a value that works on all your email clients (for example, ISO8859-1, Shift-JIS). Each instance of IBM Cognos 8 that has an available delivery service must be
changed.
The specified encoding affects only the subject, attachment names, and plain body text of the message.
HTML body text and the content of the attachments remains in UTF-8 encoding.
Note: The conversion from Unicode to the Japanese encoding EUC-JP and ISO-2022-JP is not fully
supported by the Java runtime environment. If you select either of these two settings, the characters
are not supported in the subject or body text of the email.
Steps
1. Start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
3. In the Global Configuration window, click the Server tab.
4. Click the Value column for the Email Encoding property.
5. Scroll to the desired setting and click it.
6. From the File menu, click Save.
138
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Customize Cookie Settings
Based on the requirements of your environment, you may need to modify the settings that IBM
Cognos 8 uses to create cookies. You can use IBM Cognos Configuration to customize the cookie
domain, path, and secure flag.
IBM Cognos 8 determines the cookie domain from the HTTP request submitted by the client, which
is typically a Web browser. In most network configurations, HTTP requests pass through intermediaries such as proxy servers and firewalls as they travel from the browser to IBM Cognos 8 components. Some intermediaries modify the information that IBM Cognos 8 components use to calculate
the cookie domain, and IBM Cognos 8 then cannot set cookies. The usual symptom of this problem
is that users are repeatedly prompted to log on. To avoid this problem, configure the cookie domain.
To set the correct value for the cookie domain, use the format and value that represents the widest
coverage for the host.
Host
Format for domain
Example
computer or server
computer or server name (no
dots)
mycompany
suffix is .com, .edu, .gov, .int,
.mil, .net, or .org
.name.suffix
.mycompany.com
other
.name1.name2.suffix
(two dots)
.travelinfo.co.nz
(three dots)
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
2. From the Actions menu, click Edit Global Configuration.
3. Click the Server tab.
4. Click in the Value column under Cookie Settings for each property that you want to change
and specify the new value.
If you leave the Domain property blank, the dispatcher derives the domain from the host name
of the request.
5. Click OK.
Configure Fonts
IBM Cognos 8 uses fonts to render PDF reports on the IBM Cognos server. IBM Cognos 8 also
uses fonts 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, install the fonts on the IBM Cognos server. If a requested font is not
available, IBM Cognos 8 substitutes a different font.
Installation and Configuration Guide 139
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Because HTML reports are rendered on a browser, the required fonts must be installed on the
computer of each person 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 IBM Cognos Environment
You can add fonts to the list of supported fonts in your IBM Cognos environment if you want to
generate reports that use fonts that are currently not available. You can also remove fonts.
By default, IBM Cognos 8 uses a set of global fonts, which are available on all IBM Cognos server
computers.
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
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.
6. From the File menu, click Save.
All global fonts, including new fonts that you add, must be installed on all IBM Cognos computers in your environment.
If a global font is not installed on all IBM Cognos computers, you must map the global font to an
installed, physical font name.
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 c8_location/bin/fonts directory of the
IBM Cognos computer. If IBM Cognos 8 components are installed on a Windows computer, they
also use the fonts installed in the Windows font directory.
You specify the font location on all computers where Application Tier Components are installed.
Steps
1. On each Application Tier Components computer, start IBM Cognos Configuration.
140
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
2. In the Explorer window, click Environment.
3. In the Properties window, for the Physical fonts locations property, specify the location of the
fonts.
Tip: If there are multiple font paths, separate each path by a semicolon (;).
4. From the File menu, click Save.
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 IBM Cognos
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 IBM Cognos
computers. However, you must specify the location of the font.
Steps
1. On each Application Tier Components computer, start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. In the Properties window, click the Value box next to the Physical fonts map property, and
then click the edit button.
The Value - Physical fonts map 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 Physical
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.
10. From the File menu, click Save.
Now, if required, you must specify the location of the font.
Change the Gateway
To improve Web server performance, you can configure IBM Cognos 8 to use alternate gateways
that replace the default CGI program. You can use one of the following gateways:
Installation and Configuration Guide 141
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
Microsoft Internet Application Programming Interface (ISAPI) for Microsoft Internet Information
Services for Windows
●
apache_mod for Apache Web Server
●
servlet for an application server or Web server that supports Java
There is no additional Web server configuration required to use ISAPI. To access IBM Cognos 8
using ISAPI, in IBM Cognos Configuration, change the cognos.cgi portion of the Gateway URI
property to cognosisapi.dll. Then specify the ISAPI URI, http://host_name/cognos8/isapi, in your
browser.
Before you change the gateway, we recommend that you first ensure that the default CGI gateway
and your configuration work in your environment.
Configure the Gateway for IBM Cognos Apache Web Server Module
IBM Cognos 8 provides two Apache modules. The IBM Cognos Apache module requires Apache
Server 1.3.x and the IBM Cognos Apache 2 module requires Apache Server 2.0.x.
Steps
1. Stop Apache Web Server.
2. Append the c8_location/cgi-bin directory to the appropriate environment variable:
●
On Solaris or Linux, LD_LIBRARY_PATH
●
On HP-UX,
For Apache 1.3, SHLIB_PATH
For Apache 2.0, SHLIB_PATH and LD_LIBRARY_PATH
●
On AIX, LIBPATH
3. On HP-UX PA-RISC, do the following:
●
Ensure that the LD_PRELOAD environment variable contains /usr/lib/libcl.2.
●
For Apache 1.3, set the COG_CGIBIN_DIR environment variable to c8_location/cgi-bin.
4. Go to the Apache_installation/conf directory.
5. Open the httpd.conf file in an editor.
6. Add the following to the end of the load module list:
LoadModule cognos_module "c8_location/cgi-bin/module_name"
where module_name is as follows:
142
Operating system
Apache 1.3 module
Apache 2.0 module
Windows
mod_cognos.dll
mod2_cognos.dll
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Operating system
Apache 1.3 module
Apache 2.0 module
Solaris, AIX
mod_cognos.so
mod2_cognos.so
HP-UX PA-RISC
mod_cognos.sl
mod2_cognos.sl
HP-UX IA, Linux
(not supported)
mod2_cognos.s0
7. For Apache 1.3, add the following to the end of the add module list:
AddModule mod_cognos.cpp
8. Add the following to the aliases section:
ScriptAlias /cognos8/cgi-bin "c8_location/cgi-bin"
Alias /cognos8 "c8_location/webcontent"
<Directory "c8_location/webcontent">
Options Indexes MultiViews
</Directory>
The <Directory> directive is optional.
Tip: Ensure that you define the cognos8/cgi-bin alias before the cognos8 alias.
9. Add the following to the server status reports section:
<Location /cognos8/cgi-bin/cognos_module>
SetHandler cognos-handler
</Location>
10. To enable the gateway diagnostic page, add the following to the server status reports section:
<Location /cognos8/cgi-bin/diag_cognos_module>
SetHandler cognos-handler
</Location>
The diag_ string is required.
11. For Apache 1.3, for Windows, Solaris, and AIX, add the following to the user directory section:
<IfModule mod_cognos.cpp>
CGIBinDir "c8_location/cgi-bin"
</IfModule>
12. For Apache 2.0, add the following to the user directory section:
<IfModule mod_cognos.c>
CGIBinDir "c8_location/cgi-bin"
</IfModule>
13. Save and close the file.
14. For Apache 2.0, on HP-UX, enable searching for LD_LIBRARY_PATH by running the following
command in the Apache_installation/bin directory:
Installation and Configuration Guide 143
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
chatr +s enable +b enable httpd
15. Start Apache Web Server.
16. In IBM Cognos Configuration, configure the Gateway URI property to use the apache_mod
gateway:
http://host_name:port/cognos8/cgi-bin/filename
where filename matches the name that you used in step 9.
Configure a Servlet Gateway
You can configure the Servlet Gateway to run under a supported application server.
After ensuring that the required components are installed and operating, copy IBM Cognos security
provider files to the JVM environment, configure IBM Cognos 8, change the application server
startup script, and then deploy the IBM Cognos servlet gateway to the application server.
The IBM Cognos security provider files must be located in the JVM environment used by your
application server. These files provide additional encryption and decryption routines that are not
supplied as part of a default JVM installation. To ensure security, encryption files must be loaded
by the JVM using the java extensions directory.
Before you set up the IBM Cognos servlet gateway, ensure that
●
the application server is installed and operational on each computer where the servlet gateway
is to be installed
●
IBM Cognos 8 Gateway components are installed on the same system as the application server
●
the IBM Cognos 8 dispatcher and Content Manager components are installed and running in
the environment
●
the application server user account has full access permissions for the IBM Cognos installation
We recommend that you create a new UNIX group named cognos8. This group must contain
the user that starts the application server and the user that owns the IBM Cognos files. Change
the group ownership of the IBM Cognos files to the IBM Cognos8 group and change the file
permissions for all IBM Cognos files to GROUP READABLE/WRITABLE/EXECUTABLE. For
simplicity, you can also use the application server user account to install and run IBM Cognos
components.
Steps to Copy IBM Cognos Security Provider Files
1. Backup the JVM_version /jre/lib/ext directory if it exists.
2. Create one of the following directories if it does not exist in your JVM environment:
For JDK, JVM_version/jre/lib/ext
For JRE, JVM_version/lib/ext
Some JVM distributions do not ship with either of these directories.
3. Copy the contents of the c8_location/bin/jre/version/lib/ext directory to the JVM_version/jre/lib/ext directory for the JVM environment.
144
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
Important: Do not overwrite any existing files.
Steps to Configure IBM Cognos 8
1. Set the JAVA_HOME environment variable to point to the JVM used by the application server.
Tip: If the application server ships with a JVM, then set the JAVA_HOME environment variable
to reference it.
IBM Cognos Configuration uses this variable to locate the JVM used by the applications server
and the security provider files supplied by IBM Cognos.
2. From the c8_location/bin directory, start IBM Cognos Configuration:
●
For Windows, type cogconfig.bat in a command window or select IBM Cognos Configuration from the Start menu.
●
For UNIX, type cogconfig.sh
If you have existing incompatible encryption keys, you will be prompted to automatically
generate new ones at this time.
3. In the Explorer window of IBM Cognos Configuration, expand Environment.
4. In the Properties window, under Gateway settings, change the Dispatcher URIs for Gateway
property to use the port number and host name or IP address of the server where the dispatcher
component is installed.
The default context root value for the servlet gateway is /ServletGateway.
5. Complete other required configuration changes such as enabling security.
6. Save the configuration.
New cryptographic keys are created using the JVM that is defined by the JAVA_HOME variable.
7. To create the application file to deploy to the application server, from the Actions menu, click
Build Application Files.
The Build Application Wizard opens and allows you to select the type of application to build
and the context root to use to access the application.
8. Close IBM Cognos Configuration.
If you are using an application server, you must now change the application server startup
script and then configure the application server properties and deploy IBM Cognos components.
A maximum heap memory setting of between 256MB and 512MB is a suggested starting value
that you can change to suit your environment.
Change the IP Address Version
IBM Cognos 8 supports two IP address versions: IPv4 and IPv6. IPv4 uses 32-bit IP addresses and
IPv6 uses 128-bit IP addresses. For example:
●
IPv4: 192.168.0.1:80
Installation and Configuration Guide 145
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
IPv6: [2001:0db8:0000:0000:0000:148:57ab]:80
In IBM Cognos Configuration, you can select IPv4 or IPv6 for IBM Cognos 8 communication using
the IP Version for Host Name Resolution property. By default IPv4 is employed.
The setting applies only to the computer where it is set. If you selectPrefer IPv4 stack, all outgoing
IBM Cognos 8 connections on that computer are established using IPv4 and the dispatcher accepts
only incoming IPv4 connections. If you select Prefer IPv6 addresses, all outgoing IBM Cognos 8
connections on that computer are established using IPv6 and the dispatcher accepts both incoming
IPv4 and IPv6 connections.
IPv4 client computers can communicate with dispatcher computers that are configured for IPv6.
Hostnames specified within a URI are resolved based on the value of the Network Configuration
property. However, if a URI has been specified with a numeric address, it has precedence over this
setting and communication takes place using IPv4.
The setting applies only to the computer where it is set. If you select Use IPv4 addresses, all outgoing
IBM Cognos 8 connections on that computer are established using IPv4 and the dispatcher accepts
only incoming IPv4 connections. If you select Use IPv6 addresses, all outgoing IBM Cognos 8 connections on that computer are established using IPv6 and the dispatcher accepts both incoming
IPv4 and IPv6 connections.
IPv4 client computers can communicate with dispatcher computers that are configured for IPv6.
Hostnames specified within a URI are resolved based on the value of the IP Version for Host Name
Resolution property. However, if a URI has been specified with a numeric address, it has precedence
over this setting and communication takes place using IPv4.
For IBM Cognos Configuration to accept IPv6 addresses in the local URI properties, you must start
IBM Cognos Configuration with the -ipv6 option. You can specify the option each time you open
IBM Cognos Configuration from the command line.
On Windows, you can set the option permanently by adding the option to the Start menu shortcut.
Steps to Set the IP Version
1. Start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. Click the Value box for IP Version for Host Name Resolution and click Use IPv4 addresses or
Use IPv6 addresses.
4. From the File menu, click Save.
5. Close IBM Cognos Configuration.
Steps to Manually Enable the IPv6 Option When Opening IBM Cognos Configuration
1. Go to the c8_location\bin directory.
2. Start IBM Cognos Configuration by including the IPv6 option in the command, as follows:
●
On Windows, type
cogconfig.bat -ipv6
146
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
●
On UNIX or Linux, type
./cogconfig.sh -ipv6
3. Edit the URI properties that use IPv6 format, specify the values, and then from the File menu,
click Save.
Steps to Always Open IBM Cognos Configuration With the IPv6 Option on Windows
1. From the Start menu, select Programs, IBM Cognos 8, and then right-click IBM Cognos Configuration, Properties.
2. On the Shortcut tab, in the Target box, type
"c8_location\bin\cogconfigw.exe -ipv6"
3. Click OK.
Installation and Configuration Guide 147
Chapter 7: Configuring IBM Cognos 8 Analytic Applications
148
Chapter 8: Configuring IBM Cognos 8 Components
to Use an Authentication Provider
IBM Cognos 8 components run with two levels of logon: anonymous and authenticated. By default,
anonymous access is enabled.
You can use both types of logon with your installation. If you choose to use only authenticated
logon, you can disable anonymous access.
For authenticated logon, you must configure IBM Cognos 8 components with an appropriate
namespace for the type of authentication provider in your environment. 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 upgraded from ReportNet and IBM Cognos 8 detects a previously configured namespace
that is no longer configured, the unconfigured namespace appears in the list of authentication providers in the Administration portal. You can configure the namespace if you still require the user
account information. Otherwise, you can delete the namespace. For information about deleting the
namespace, see the Administration and Security Guide.
Also, when upgrading from one version to another, you must use the same authentication namespace
for both versions. Otherwise, the new version may not contain the same policies, users, roles, and
groups.
IBM Cognos 8 components support the following types of servers as authentication sources:
●
Active Directory Server
●
IBM Cognos Series 7
●
Custom Authentication Provider
●
LDAP
●
eTrust SiteMinder
●
NTLM
●
SAP
If you use more than one Content Manager computer, you must configure identical authentication
providers on each Content Manager computer. This means that the type of authentication provider
you select and the way you configure it must be identical on all computers for all platforms. The
configuration must contain information that is accessible by all Content Manager computers.
When IBM Cognos 8 is installed on a single Linux computer, or when Content Manager is installed
on a Linux computer, IBM Cognos 8 can be configured to use only LDAP V3-compliant directory
servers and custom providers as authentication sources.
Installation and Configuration Guide 149
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Some authentication providers require libraries external to the IBM Cognos 8 environment to be
available. If these libraries are not available on Linux, the authentication provider cannot be initialized.
If you want to configure one of the following as your authentication source, you must install Content
Manager on a non-Linux computer:
●
IBM Cognos Series 7 namespace
●
Active Directory Server
●
NTLM
●
eTrust SiteMinder
●
SAP BW
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 delete a
namespace, the user preferences, My Folders, and My Pages entries are permanently lost. Existing
permission settings will refer to users, groups, or roles that no longer exist. While this does not
affect how the permissions work, a user administering the permission settings may see "unknown"
entries. Because these entries refer to users, groups, and roles which no longer exist, you can safely
delete them.
After you configure an authentication provider for IBM Cognos 8 components, you can enable
single signon between your authentication provider environment and IBM Cognos 8 components.
This means that a user logs on once and can then switch to another application without being asked
to log on again.
Users can select namespaces when they log in to the IBM Cognos 8 portal. You can hide Custom
Java namespaces (p. 162) and eTrust SiteMinder namespaces (p. 181) from users.
To use an authentication provider and to require users to authenticate
❑
Disable anonymous access, if required.
❑
Configure IBM Cognos 8 components to use an authentication provider.
Disable Anonymous Access
By default, IBM Cognos 8 components do not require user authentication. Users can log on
anonymously.
If you want to use authenticated logon only, you can use IBM Cognos Configuration to disable
anonymous access.
Steps
1. In each location where Content Manager is installed, start Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click Cognos.
150
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
The IBM Cognos resource represents the Cognos namespace. The Cognos namespace stores
information about IBM 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.
4. From the File menu, click Save.
Now, users are required to provide logon credentials when they access IBM Cognos resources.
Restrict User Access to the Cognos Namespace
You can restrict access to users belonging to any group or role defined in the IBM Cognos built-in
namespace. By default, all users belong to several built-in groups or roles. To restrict access, you
must
●
enable the property to restrict access
●
remove the Everyone group from the IBM Cognos built-in roles and groups
●
ensure that authorized users belong to at least one IBM Cognos role or group
Steps
1. On each Content Manager computer, start IBM Cognos Configuration.
2. In the Explorer window, under Security, click Authentication.
3. In the Properties window, change the value of Restrict access to members of the built-in
namespace to True.
4. From the File menu, click Save.
You must now use the portal to remove the Everyone group from the IBM Cognos built-in roles
and groups, and then ensure that authorized users belong to at least one IBM Cognos built-in role
or group.
For information about adding or removing members of an IBM Cognos group or role, see the
Administration and Security Guide.
Configuring IBM Cognos 8 Components to Use Active Directory
Server
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 use an LDAP namespace
to configure Active Directory as your authentication source. If you install Content Manager on
Windows and UNIX computers, you must use an LDAP namespace to configure Active Directory
on all Content Manager computers. When you use an LDAP namespace to authenticate against
Installation and Configuration Guide 151
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Active Directory Server, you are limited to LDAP features only. You do not have access to Active
Directory features such as advanced properties for domains (p. 154) and single signon using Kerberos
delegation (p. 156).
If you install Content Manager on a Linux computer, the same restrictions apply as for UNIX. You
must use an LDAP namespace to configure Active Directory as your authentication source.
For more information, see "Configure an LDAP Namespace for Active Directory Server" (p. 165).
If you want to use Microsoft SQL Server or Microsoft Analysis Server as a data source and use
single signon for authentication, you must use Active Directory as your authentication source.
You cannot connect to the Active Directory Global Catalog, which is a caching server for Active
Directory Server. If the connection uses port 3268, you must change it. By default, Active Directory
Server uses port 389.
To use an Active Directory Server namespace and to set up single signon, do the following:
❑
Configure IBM Cognos 8 components to use an Active Directory Server namespace
❑
Enable secure communication to the Active Directory Server, if required
❑
Enable single signon between Active Directory Server and IBM Cognos 8 components
Configure an Active Directory Namespace
You can use Active Directory Server as your authentication provider.
You also have the option of making custom user properties from the Active Directory Server
available to IBM Cognos 8 components.
For IBM Cognos 8 to work properly with Active Directory Server, ensure that the Authenticated
users group has Read privileges for the Active Directory folder where users are stored.
If you are configuring an Active Directory namespace to support single signon with a Microsoft
SQL Server or Microsoft Analysis Server data source, ensure the following configuration:
●
The IBM Cognos 8 gateway is installed on an IIS Web server that is configured for Windows
Integrated Authentication.
●
The gateway is assigned to the local intranet Web site in your Web browser.
●
Content Manager is installed on a Windows 2000 or Windows 2003 server.
●
Content Manager, Application Tier Components, IIS Web server, and the data source server
(Microsoft SQL Server or Microsoft Analysis Server) belong to the Active Directory domain.
●
The data source connection for Microsoft SQL Server or Microsoft Analysis Server is configured
for External Namespace and that namespace must be the Active Directory namespace.
For more information about data sources, see the Administration and Security Guide.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
152
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
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 IBM Cognos 8 components
can locate and use your existing authentication provider.
7. Specify the values for the Host and port property.
To support Active Directory Server failover, you can specify the domain name instead of a
specific domain controller. For example, use mydomain.com:389 instead of dc1.mydomain.com:389.
8. If you want to search for details when authentication fails, specify the user ID and password
for the Binding credentials property.
Use the credentials of an Active Directory Server user who has search and read privileges for
that server.
9. From the File menu, click Save.
10. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Make Custom User Properties for Active Directory Available to IBM Cognos 8
Components
You can use arbitrary user attributes from your Active Directory Server in IBM Cognos 8 components. To configure this, you must add these attributes as custom properties for the Active Directory
namespace.
The custom properties are available as session parameters through Framework Manager. For more
information about session parameters, see the Framework Manager User Guide
You can also use the custom properties inside command blocks to configure Oracle sessions and
connections. You can use the command blocks can be used with Oracle light-weight connections
and virtual private databases. For more information, see the Administration and Security Guide.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click the Active Directory namespace.
Installation and Configuration Guide 153
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
3. In the Properties window, click in the Value column for Custom properties and click the edit
button.
4. In the Value - Custom properties window, click Add.
5. Click the Name column and type the name you want IBM Cognos 8 components to use for the
session parameter.
6. Click the Value column and type the name of the account parameter in your Active Directory
Server.
7. Repeat steps 4 to 6 for each custom parameter.
8. Click OK.
9. From the File menu, click Save.
Enabling Secure Communication to the Active Directory Server
If you are using an SSL connection to the Active Directory Server, you must copy the certificate
from the Active Directory Server to the Content Manager computer.
Steps
1. On every Content Manager computer, use your Web browser to connect to the Active Directory
Server and copy the CA root certificate to a location on the Content Manager computer.
2. Add the CA root certificate to the certificate store of the account that you are using for the
current IBM Cognos session:
●
If you are running the IBM Cognos session under a user account, use the same Web browser
as in step 1 to import the CA root certificate to the certificate store for your user account.
For information, see the documentation for your Web browser.
●
If you are running the IBM Cognos session under the local computer account, use Microsoft
Management Console (MMC) to import the CA root certificate to the certificate store for
the local computer.
For information, see the documentation for MMC.
3. In IBM Cognos Configuration, restart the service:
●
In the Explorer window, click IBM Cognos 8 service, IBM Cognos 8.
●
From the Actions menu, click Restart.
Include or Exclude Domains Using Advanced Properties
When you configure an authentication namespace for IBM Cognos 8, users from only one domain
can log in. By using the Advanced properties for Active Directory Server, users from related (parentchild) domains and unrelated domain trees within the same forest can also log in.
154
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Authentication in One Domain Tree
If you set a parameter named chaseReferrals to true, users in the original authenticated domain and
all child domains of the domain tree can log in to IBM Cognos 8. Users above the original authenticated domain or in a different domain tree cannot log in.
Authentication in All Domain Trees in the Forest
If you set a parameter named MultiDomainTrees to true, users in all domain trees in the forest can
log in to IBM Cognos 8.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click the Active Directory namespace.
3. In the Properties window, specify the Host and port property:
●
For users in one domain, specify the host and port of a domain controller for the single
domain.
●
For users in one domain tree, specify the host and port of the top-level controller for the
domain tree.
●
For users in all domain trees in the forest, specify the host and port of any domain controller
in the forest.
4. Click in the Value column for Advanced properties and click the edit button.
5. In the Value - Advanced properties window, click Add.
6. Specify two new properties, chaseReferrals and MultiDomainTrees, with the following values:
Authentication for
chaseReferrals
MultiDomainTrees
One domain
False
False
One domain tree
True
False
All domain trees in the forest
True
True
7. Click OK.
8. From the File menu, click Save.
Enabling Single Signon Between Active Directory Server and IBM Cognos 8
Components
By default, the Active Directory provider uses Kerberos delegation and integrates with the IIS Web
server for single signon if Windows integrated authentication (formerly named NT Challenge
Response) is enabled on the IIS Web server.
Installation and Configuration Guide 155
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
If Windows integrated authentication is enabled, you are not prompted to reenter authentication
information when accessing IBM Cognos content that is secured by the Active Directory namespace.
If you do not want Kerberos delegation, you can configure the provider to access the environment
variable REMOTE_USER to achieve single signon. You must set the advanced property
singleSignOnOption to the value IdentityMapping. You must also specify bind credentials for the
Active Directory namespace. Microsoft sets REMOTE_USER by default when you enable Windows
integrated authentication. If Kerberos authentication is bypassed, single signon to Microsoft OLAP
(MSAS) data sources will not be possible.
Steps for Single Signon Using Kerberos Delegation
1. Set up Windows integrated authentication on the IIS Web server.
2. Install Content Manager on a computer that is part of the domain, for the active and standby
Content Manager computers.
3. Set up the computers, or the user account under which Content Manager runs, to be trusted
for delegation.
When setting up the computers using the Active Directory user tool, do not select the Account
attribute, which is sensitive and cannot be delegated.
Steps for Single Signon Using REMOTE_USER
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click the Active Directory namespace.
3. Click in the Value column for Advanced properties and then click the edit button.
4. In the Value - Advanced properties dialog box, click Add.
5. In the Name column, type singleSignOnOption
6. In the Value column, type IdentityMapping.
7. Click OK.
8. Click in the Value column for Binding credentials, and then click the edit button.
9. In the Value - Binding credentials dialog box, specify a user ID and password and then click
OK.
The Active Directory provider now uses REMOTE_USER for single signon.
Tip: To switch back to Kerberos delegation, edit Advanced properties and, in the Value column,
type KerberosAuthentication.
156
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Configuring IBM Cognos 8 to Use IBM Cognos Series 7
Namespace
You can configure IBM Cognos 8 components to use an IBM Cognos Series 7 namespace as the
authentication provider. Users will be authenticated based on the authentication and signon configuration of the IBM Cognos Series 7 namespace.
A IBM Cognos Series 7 namespace is required if you want to use IBM Cognos Series 7 PowerCubes
and Transformer models in IBM Cognos 8. You must configure the namespace before you load the
Transformer models.
If you plan to run IBM Cognos 8 products within a 64-bit application server, you cannot configure
an IBM Cognos Series 7 namespace as your authentication source.
If you want to configure an IBM Cognos Series 7 namespace as your authentication source, you
must install Content Manager on a computer that supports IBM Cognos Series 7.
Note: You cannot use an IBM Cognos Series 7 Local Authentication Export (LAE) file for authentication with IBM Cognos 8 components.
You can configure IBM Cognos 8 components to use multiple IBM Cognos Series 7 authentication
providers. We recommend that all IBM Cognos Series 7 namespaces use the same primary IBM
Cognos Series 7 Ticket Server. Otherwise, you may receive errors or be prompted for authentication
more than once. To maintain performance, also ensure that the ticket server is running.
If you change the configuration information stored in the directory server used for IBM Cognos
Series 7, you must restart the IBM Cognos 8 service before the changes take effect in the IBM
Cognos installation.
A user must be in at least one Access Manager user class to log on to IBM Cognos 8 components.
To use an IBM Cognos Series 7 namespace and to set up single signon, do the following:
❑
Configure IBM Cognos 8 to use an IBM Cognos Series 7 namespace
❑
Enable secure communication to the directory server used by the IBM Cognos Series 7
namespace, if required
❑
Enable single signon between IBM Cognos Series 7 and IBM Cognos 8
Configure an IBM Cognos Series 7 Namespace
You can configure IBM Cognos 8 to use one or more IBM Cognos Series 7 namespaces for
authentication.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
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.
Installation and Configuration Guide 157
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
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 IBM Cognos 8 components
can locate and use your existing authentication provider.
If your IBM Cognos Series 7 namespace version is 16.0, ensure that the Data encoding property
is set to UTF-8. In addition, the computers where Content Manager is installed must use the
same locale as the data in the IBM Cognos Series 7 namespace.
The host value can be a computer name or an IP address. If you are publishing from PowerPlay
Enterprise Server to IBM Cognos 8, you must use the same value format used in IBM Cognos
Series 7 Configuration Manager for the location of the directory server. For example, if the
computer name is used in IBM Cognos Series 7 Configuration Manager, you must also use the
computer name in IBM Cognos Configuration for IBM Cognos 8.
7. If your namespace environment includes version 15.2 of the IBM Cognos Series 7 namespace,
you must disable the Series7NamespacesAreUnicode setting.
●
In the Properties window, in the Advanced Properties value, click the edit button.
●
In the Value - Advanced properties window, click Add.
●
In the Name box, type Series7NamespacesAreUnicode.
●
In the Value box, type False, and then click OK.
8. In the Properties window, under Cookie settings, ensure that the Path, Domain, and Secure
flag enabled properties match the settings configured for IBM Cognos Series 7.
9. From the File menu, click Save.
10. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
Enabling Secure Communication to the Directory Server Used by the IBM Cognos
Series 7 Namespace
If you are using an SSL connection to the Directory Server used by the IBM Cognos Series 7
namespace, you must copy the certificate from the Directory Server to each Content Manager
computer.
For more information, see the IBM Cognos Access Manager Administrator Guide and the documentation for your Directory Server.
Enabling Single Signon Between IBM Cognos Series 7 and IBM Cognos 8
If your IBM Cognos Series 7 namespace has been configured for integration with your external
authentication mechanisms for single signon, the IBM Cognos Series 7 provider will automatically
use this configuration.
158
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
By configuring single signon, you are not prompted to reenter authentication information when
accessing IBM Cognos content that is secured by the IBM Cognos Series 7 namespace.
Steps
1. Ensure that you configured IBM Cognos 8 components to use an IBM Cognos Series 7 namespace
as an authentication provider (p. 157).
2. For IBM Cognos Series 7, start Configuration Manager.
3. Click Open the current configuration.
4. On the Components tab, in the Explorer window, expand Services, Access Manager - Runtime
and click Cookie Settings.
5. In the Properties window, ensure that the Path, Domain, and Secure Flag Enabled properties
match the settings configured for IBM Cognos 8.
6. Save and close Configuration Manager.
7. If the IBM Cognos Series 7 namespace uses the Trusted Signon plug-in for single signon, you
must now define the SaferAPIGetTrustedSignonWithEnv function.
You can now add IBM Cognos Upfront Series 7 NewsBoxes to your IBM Cognos Connection portal
pages.
IBM Cognos Series 7 Namespaces and the IBM Cognos Series 7 Trusted Signon
Plug-in
If the IBM Cognos Series 7 namespace uses the Trusted Signon plug-in for single signon, you must
define the SaferAPIGetTrustedSignonWithEnv function in your plug-in. Then you must recompile
and redeploy the library for single signon to be achieved between IBM Cognos 8 components and
your authentication mechanism.
The SaferAPIGetTrustedSignonWithEnv function is an updated version of the SaferAPIGetTrustedSignon function. This update is required because IBM Cognos 8 logon is not performed at the Web
server as is the case for IBM Cognos Series 7 applications. Therefore, it is not possible for the plugin to perform a getenv() API call to retrieve Web server environment variables. The plug-in can
request that specific environment variables be removed from the Web server using the SaferAPIGetTrustedSignonWithEnv function.
If you are running both IBM Cognos Series 7 and IBM Cognos 8 products using the same plug-in,
both the SaferAPIGetTrustedSignonWithEnv and SaferAPIGetTrustedSignon functions are required.
For information about the SaferAPIGetTrustedSignon function, see the IBM Cognos Series 7 documentation.
SaferAPIGetTrustedSignonWithEnv Function
For users to be successfully authenticated by Access Manager, OS signons must exist and be enabled
in the current namespace.
Installation and Configuration Guide 159
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
The memory for the returned trustedSignonName and trustedDomainName is allocated internally
in this API. If the function returns SAFER_SUCCESS, Access Manager calls SaferAPIFreeTrustedSignon to free the memory allocated.
The memory for the returned reqEnvVarList is allocated internally in this API. If the function returns
SAFER_INFO_REQUIRED, Access Manager calls SaferAPIFreeBuffer() to free the memory allocated.
You must implement both the SaferAPIGetTrustedSignon and SaferAPIFreeBuffer functions to
successfully register the library when SaferAPIGetTrustedSignonWithEnv is implemented. The
function SaferAPIGetError is required only if you want specific error messages returned from your
plug-in.
Syntax
SaferAPIGetTrustedSignonWithEnv(
160
EnvVar
envVar[],
/*[IN]*/
char
**reqEnvVarList,
/*[OUT]*/
void
**trustedSignonName,
/*[OUT]*/
unsigned long
*trustedSignonNameLength,
/*[OUT]*/
void
**trustedDomainName,
/*[OUT]*/
unsigned long
*trustedDomainNameLength,
/*[OUT]*/
SAFER_USER_TYPE
*userType,
/*[OUT]*/
void
**implementerData);
/*[IN/OUT]*/
Parameter
Description
[in] envVar
An array of environment variable names and values that
were retrieved from the Web server. The end of the array
is represented by an entry with a null envVarName and a
null envVarValue. Note that the first time this API is called,
the envVar array contains only the end of array marker.
[in] reqEnvVarList
A string that contains a comma separated list of environment variable names that are requested by the Safer implementation. The end of the list must be null-terminated.
[out] trustedSignonName
A sequence of bytes that identifies the currently authenticated user. This value does not need to be null-terminated.
This value is mandatory.
[out] trustedSignonNameLength
An integer value that indicates the length of the trustedSignonName. This length should exclude the null terminator, if there is one. This value is mandatory.
[out] trustedDomainName
A sequence of bytes that identifies the domain of the currently authenticated user. You do not need to null-terminate
this value. If there is no trustedDomainName, the return is
null. This value is optional.
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Parameter
Description
[out] trustedDomainNameLength An integer value that indicates the length of the trustedDomainName. This length should exclude the null terminator,
if there is one. This value is mandatory and must be set to
zero if there is no trustedDomainName.
[out] userType
A value that indicates the type of user that Access Manager
will authenticate. This value is mandatory.
The following return values are required for Access Manager to successfully authenticate users:
SAFER_NORMAL_USER
A named user. OS signons must exist and be enabled in the
current namespace.
SAFER_GUEST_USER
A guest user. A guest user account must exist and be enabled
in the current namespace.
SAFER_ANONYMOUS_USER
An anonymous user. An anonymous user account must
exist and be enabled in the current namespace.
[in/out] implementerData
A pointer used to preserve implementation-specific data
between invocations. An invocation occurs every time
Access Manager calls the trusted signon plug-in. This value
is valid only if the trusted signon plug-in was invoked and
you set a value for it.
Configuring IBM Cognos 8 to Use a Custom Authentication
Provider
If you implemented a custom Java authentication provider with your existing security infrastructure,
you can configure IBM Cognos 8 components to use it.
You can use a custom authentication provider to access and authenticate users to an alternate
authentication source. You can also use it as a single signon mechanism to integrate IBM Cognos 8
components with your security infrastructure. You can hide the namespace from users during logon.
For more information, see the Custom Authentication Provider Developer Guide.
Configure a Custom Authentication Namespace
You can configure IBM Cognos 8 components to use a custom authentication namespace. Any
additional configuration for authentication source access, single signon, or custom attributes are
dependent on the custom authentication provider implementation.
Installation and Configuration Guide 161
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Ensure that the versions of Java Runtime Environment and Java SDK that you use are compatible
with each other. If you use supported versions of the JRE and Java SDK that are not compatible
with each other, then the custom Java authentication provider that you configure will not appear
in the list of namespaces in IBM Cognos Configuration.
Steps
1. On every computer where installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and click New resource,
Namespace.
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click Custom Java Provider 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 NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 can locate and
use your existing authentication provider.
7. From the File menu, click Save.
8. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Hide the Namespace from Users During Login
You can hide namespaces from users during login. You can have trusted signon namespaces without
showing them on the namespace selection list that is presented when users log in.
For example, you may want to integrate single signon across systems but maintain the ability for
customers to authenticate directly to IBM Cognos 8 without being prompted to choose a namespace.
Steps
1. On each computer where you configured a custom Java authentication provider, open IBM
Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click the custom Java authentication
provider.
3. In the Properties window, click the box next to Selectable for authentication and then click
False.
4. From the File menu, click Save.
162
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
The namespace is not shown on the selection list that is presented at login.
Configuring IBM Cognos 8 Components to Use LDAP
You can configure IBM Cognos 8 components to use an LDAP namespace as the authentication
provider. You can use an LDAP namespace for users that are stored in an LDAP user directory,
Active Directory Server, IBM Directory Server, Novell Directory Server, or Sun Java System Directory
Server.
You can also use LDAP authentication with DB2 and Essbase OLAP data sources by specifying the
LDAP namespace when you set up the data source connection. For more information, see the
Administration and Security Guide.
You also have the option of making custom user properties from the LDAP namespace available
to IBM Cognos 8 components.
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 these searches, 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 IBM Cognos 8 using external
identity mapping see the same users, groups, and folders as the Bind user.
If you do not use external identity mapping, you can specify whether to use bind credentials to
search the LDAP directory server by configuring the Use bind credentials for search property. When
the property is enabled, searches are performed using the bind user credentials or using anonymous
if no value is specified. When the property is disabled, which is the default setting, searches are
performed using the credentials of the logged-on user. The benefit of using bind credentials is that
instead of changing administrative rights for multiple users, you can change the administrative
rights for the bind user only.
Important: If you use a DN syntax, such as uid=${userID}, ou=mycompany.com, for the properties
User lookup, External identity mapping, or Bind user DN and password, you must escape all special
characters that are used in the DN. If you use a search syntax, such as (uid=${userID}), for the
properties User lookup or External identity mapping, you must not escape special characters that
are used in the DN.
To use an LDAP namespace and set up single signon, do the following:
❑
Configure IBM Cognos 8 components to use an LDAP namespace
❑
Make custom user properties available to IBM Cognos 8 components, if required
Installation and Configuration Guide 163
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
❑
Enable secure communication to the LDAP server, if required
❑
Enable single signon between LDAP and IBM Cognos 8 components, if required
Configure an LDAP Namespace
You can configure IBM Cognos 8 components to use an LDAP namespace when the users are stored
in an LDAP user directory. The LDAP user directory may be accessed from within another server
environment, such as Active Directory Server or eTrust SiteMinder.
If you are configuring an LDAP namespace for a directory server other than LDAP, see the appropriate section:
●
For Active Directory Server, see Configure an LDAP Namespace for Active Directory Server.
●
For IBM Directory Server, see Configure an LDAP Namespace for IBM Directory Server.
●
For Novell Directory Server, see Configure an LDAP Namespace for Novell Directory Server.
●
For Sun Java System Directory Server, see Configure an LDAP Namespace for Sun Java System
Directory Server
You can also use LDAP authentication with DB2 and Essbase OLAP data sources by specifying the
LDAP namespace when you set up the data source connection. For more information, see the
Administration and Security Guide.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
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 IBM Cognos 8 components
can locate and use your existing authentication provider.
7. If you want the LDAP authentication provider to bind to the directory server using a specific
Bind user DN and password when performing searches, then specify these values.
If no values are specified, the LDAP authentication provider binds as anonymous.
If external identity mapping is enabled, Bind user DN and password are used for all LDAP
access. If external identity mapping is not enabled, Bind user DN and password are used only
when a search filter is specified for the User lookup property. In that case, when the user DN
164
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
is established, subsequent requests to the LDAP server are executed under the authentication
context of the end user.
8. If you do not use external identity mapping, use bind credentials for searching the LDAP directory server by doing the following:
●
Ensure that Use external identity is set to False.
●
Set Use bind credentials for search to True.
●
Specify the user ID and password for Bind user DN and password.
If you do not specify a user ID and password, and anonymous access is enabled, the search is
done using anonymous.
9. Check the mapping settings for required objects and attributes.
Depending on the LDAP configuration, you may have to change some default values to ensure
successful communication between IBM Cognos 8 components and the LDAP server.
LDAP attributes that are mapped to the Name property in Folder mappings, Group mappings,
and Account mappings must be accessible to all authenticated users. In addition, the Name
property must not be blank.
10. From the File menu, click Save.
11. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Configure an LDAP Namespace for Active Directory Server
If you configure a new LDAP namespace for use with an Active Directory Server, you must modify
the necessary settings and change the values for all properties of the Active Directory objects.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
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 NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
Installation and Configuration Guide 165
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
6. Specify the values for all other required properties to ensure that IBM Cognos 8 components
can locate and use your existing authentication provider.
The following settings are examples:
●
For User lookup, specify (sAMAccountName=${userID})
●
If you use single signon, for Use external identity, set the value to True.
●
If you use single signon, for External identity mapping, specify (sAMAccountName=$
{environment("REMOTE_USER")})
If you want to remove the domain name from the REMOTE_USER variable, specify
(sAMAccountName=${replace(${environment("REMOTE_USER")}, "domain\\","")}).
●
For Bind user DN and password, specify user@domain
●
For Unique identifier, specify objectGUID
7. If you want the LDAP authentication provider to bind to the directory server using a specific
Bind user DN and password when performing searches, then specify these values.
If no values are specified, the LDAP authentication provider binds as anonymous.
8. If you do not use external identity mapping, use bind credentials for searching the LDAP directory server by doing the following:
●
Ensure that Use external identity is set to False.
●
Set Use bind credentials for search to True.
●
Specify the user ID and password for Bind user DN and password.
9. To configure the LDAP advanced mapping properties for use with the Active Directory Server
objects, use the values specified in the following table.
LDAP attributes that are mapped to the Name property in Folder mappings, Group mappings,
and Account mappings must be accessible to all authenticated users. In addition, the Name
property must not be blank.
Mappings
LDAP property
LDAP value
Folder
Object class
organizationalUnit,organization,container
Description
description
Name
ou,o,cn
Object class
group
Description
description
Member
member
Group
166
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Mappings
Account
LDAP property
LDAP value
Name
cn
Object class
user
Business phone
telephonenumber
Content locale
(leave blank)
Description
description
Email
mail
Fax/Phone
facsimiletelephonenumber
Given name
givenname
Home phone
homephone
Mobile phone
mobile
Name
displayName
Pager phone
pager
Password
unicodePwd
Postal address
postaladdress
Product locale
(leave blank)
Surname
sn
Username
sAMAccountName
These mapping properties represent changes based on a default Active Directory Server
installation. If you have modified the schema, you may have to make additional mapping
changes.
10. From the File menu, click Save.
11. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Installation and Configuration Guide 167
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Configure an LDAP Namespace for IBM Directory Server
If you configure a new LDAP namespace for use with an IBM Directory Server, you must modify
the necessary settings and change the values for all properties of the IBM Directory objects.
Steps
1. In each location where you installed Content Manager, open Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click LDAP, and then click OK.
The new authentication namespace resource appears in the Explorer window, under the
Authentication component.
5. In the Properties window, for the NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 can locate and
use your existing authentication namespace.
●
For User lookup, specify (cn=${userID})
●
For Bind user DN and password, specify cn=root
7. If you want the LDAP authentication provider to bind to the directory server using a specific
Bind user DN and password when performing searches, then specify these values.
If no values are specified, the LDAP authentication namespace binds as anonymous.
8. If you do not use external identity mapping, use bind credentials for searching the LDAP directory server by doing the following:
●
Ensure that Use external identity is set to False.
●
Set Use bind credentials for search to True.
●
Specify the user ID and password for Bind user DN and password.
9. To configure the LDAP advanced mapping properties for use with IBM Directory Server objects,
use the values specified in the following table.
LDAP attributes that are mapped to the Name property in Folder mappings, Group mappings,
and Account mappings must be accessible to all authenticated users. In addition, the Name
property must not be blank.
168
Mappings
LDAP property
LDAP value
Folder
Object class
organizationalunit,organization,container
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Mappings
Group
Account
LDAP property
LDAP value
Description
description
Name
ou,o,cn
Object class
groupofnames
Description
description
Member
member
Name
cn
Object class
inetorgperson
Business phone
telephonenumber
Content locale
(leave blank)
Description
description
Email
mail
Fax/Phone
facsimiletelephonenumber
Given name
givenname
Home phone
homephone
Mobile phone
mobile
Name
cn
Pager phone
pager
Password
userPassword
Postal address
postaladdress
Product locale
(leave blank)
Surname
sn
Username
uid
Installation and Configuration Guide 169
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
These mapping properties represent changes based on a default IBM Directory Server installation.
If you have modified the schema, you may have to make additional mapping changes.
10. From the File menu, click Save.
Configure an LDAP Namespace for Novell Directory Server
If you configure a new LDAP namespace for use with a Novell Directory Server, you must modify
the necessary settings and change the values for all properties of the Novell Directory objects.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click LDAP and then click OK.
The new authentication namespace resource appears in the Explorer window, under the
Authentication component.
5. In the Properties window, for the NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 can locate and
use your existing authentication namespace.
●
For User lookup, specify (cn=${userID})
●
For Bind user DN and password, specify the base DN for an administration user, such as
cn=Admin,0=COGNOS
7. If you want the LDAP authentication provider to bind to the directory server using a specific
Bind user DN and password when performing searches, then specify these values.
If no values are specified, the LDAP authentication namespace binds as anonymous.
8. If you do not use external identity mapping, use bind credentials for searching the LDAP directory server by doing the following:
●
Ensure that Use external identity is set to False.
●
Set Use bind credentials for search to True.
●
Specify the user ID and password for Bind user DN and password.
9. To configure the LDAP advanced mapping properties for use with Novell Directory Server
objects, use the values specified in the following table.
170
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
LDAP attributes that are mapped to the Name property in Folder mappings, Group mappings,
and Account mappings must be accessible to all authenticated users. In addition, the Name
property must not be blank.
For users to successfully log in to IBM Cognos Connection, they must have permission to read
the ou and o attributes.
Mappings
LDAP property
LDAP value
Folder
Object class
organizationalunit,organization,container
Description
description
Name
ou,o,cn
Object class
groupofnames
Description
description
Member
member
Name
cn
Object class
inetOrgPerson
Business phone
telephonenumber
Content locale
Language
Description
description
Email
mail
Fax/Phone
facsimiletelephonenumber
Given name
givenname
Home phone
homephone
Mobile phone
mobile
Name
cn
Pager phone
pager
Password
(leave blank)
Group
Account
Installation and Configuration Guide 171
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Mappings
LDAP property
LDAP value
Postal address
postaladdress
Product locale
Language
Surname
sn
Username
uid
These mapping properties represent changes based on a default Novell Directory Server
installation. If you have modified the schema, you may have to make additional mapping
changes.
10. From the File menu, click Save.
Configure an LDAP Namespace for Sun Java System Directory Server
If you configure a new LDAP namespace for use with Sun Java System Directory Server, you must
modify the necessary settings and change the values for all properties of the Sun Java System Directory objects.
Steps
1. On every computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and then click New resource,
Namespace.
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click LDAP and then click OK.
The new authentication namespace resource appears in the Explorer window, under the
Authentication component.
5. In the Properties window, for the NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 can locate and
use your existing authentication namespace.
The following settings are examples:
172
●
For User lookup, type (uid=${userID})
●
If you use single signon, for Use external identity, set the value to True.
●
If you use single signon, for External identity mapping, specify any attribute, such as the
NT user domain ID or the user ID:
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
(ntuserdomainid=$environment("REMOTE_USER")})
(uid=${environment("REMOTE_USER")})
●
For Unique identifier, type nsuniqueid
7. If you want the LDAP authentication provider to bind to the directory server using a specific
Bind user DN and password when performing searches, then specify these values.
If no values are specified, the LDAP authentication namespace binds as anonymous.
8. If you do not use external identity mapping, use bind credentials for searching the LDAP directory server by doing the following:
●
Ensure that Use external identity is set to False.
●
Set Use bind credentials for search to True.
●
Specify the user ID and password for Bind user DN and password.
9. To configure the LDAP advanced mapping properties for use with Sun Java System Directory
Server objects, use the values specified in the following table.
LDAP attributes that are mapped to the Name property in Folder mappings, Group mappings,
and Account mappings must be accessible to all authenticated users. In addition, the Name
property must not be blank.
Mappings
LDAP property
LDAP value
Folder
Object class
organizationalUnit,organization
Description
description
Name
ou,o
Object class
groupofuniquenames
Description
description
Member
uniquemember
Name
cn
Object class
inetorgperson
Business phone
telephonenumber
Content locale
preferredlanguage
Description
description
Group
Account
Installation and Configuration Guide 173
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Mappings
LDAP property
LDAP value
Email
mail
Fax/Phone
facsimiletelephonenumber
Given name
givenname
Home phone
homephone
Mobile phone
mobile
Name
cn
Pager phone
pager
Password
userPassword
Postal address
postaladdress
Product locale
preferredlanguage
Surname
sn
Username
uid
These mapping properties represent changes based on a default Sun Java System Directory
Server installation. If you have modified the schema, you may have to make additional mapping
changes.
10. From the File menu, click Save.
Make Custom User Properties for LDAP Available to IBM Cognos 8 Components
You can use arbitrary user attributes from your LDAP authentication provider in IBM Cognos 8
components. To configure this, you must add these attributes as custom properties for the LDAP
namespace. The custom properties are available as session parameters through Framework Manager.
For more information about session parameters, see the Framework Manager User Guide.
You can also use the custom properties inside command blocks to configure Oracle sessions and
connections. You can use the command blocks with Oracle lightweight connections and virtual
private databases. For more information, see the Administration and Security Guide.
Steps
1. In each location where you installed Content Manager, open Cognos Configuration.
2. In the Explorer window, under Security, Authentication, click the LDAP namespace.
174
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
3. In the Properties window, click in the Value column for Custom properties, and click the edit
button.
4. In the Value - Custom properties window, click Add.
5. Click the Name column, and type the name you want IBM Cognos 8 components to use for
the session parameter.
6. Click the Value column, and type the name of the account parameter in your LDAP authentication provider.
7. Repeat the preceding two bulleted steps for each custom parameter.
8. Click OK.
9. From the File menu, click Save.
Enable Secure Communication to the LDAP Server
Secure LDAP protocol (LDAPS) encrypts the communication between the Access Manager component
of Content Manager and the directory server. LDAPS prevents sensitive information in the directory
server and the LDAP credentials from being sent as clear text.
To enable LDAPS, install a server certificate that is signed by a certificate authority in the directory
server. Next, create a certificate database to contain the certificates. Finally, configure the directory
server and the IBM Cognos 8 LDAP namespace to use LDAPS.
The server certificate must be a copy of either
●
the trusted root certificate and all other certificates that make up the chain of trust for the directory server certificate.
The trusted root certificate is the certificate of the root certificate authority that signed the
directory server certificate.
●
the directory server certificate only
The certificates must be Base64 encoded in ASCII (PEM) format. All certificates except the trusted
root certificate must not be self-signed.
IBM Cognos 8 works with both the cert8.db and cert7.db versions of the client certificate database.
You must use the certutil tool from Netscape OpenSource toolkit NSS_3_11_4_RTM to create the
certificate database. IBM Cognos 8 does not accept other versions of cert8.db files, including those
from the certutil tool that is provided with Microsoft Active Directory. The appropriate certutil
tool is available from ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_11_4_RTM.
You must also use the NSPR library, which is available from ftp://ftp.mozilla.org/pub/mozilla.org/
nspr/releases/v4.6.7.
Steps
1. Create a directory for the certificate database.
2. Create the certificate database by typing
certutil -N -d certificate_directory
Installation and Configuration Guide 175
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
where certificate_directory is the directory that you created in step 1.
This command creates a cert8.db file and a key3.db file in the new directory.
3. Add the certificate authority (CA) certificate or the directory server certificate to the certificate
database by typing the appropriate command for the type of certificate:
●
For a CA certificate, type
certutil -A -n certificate_name -d certificate_directory -i CA.cert -t C,C,C
●
For a directory server certificate, type
certutil -A -n certificate_name -d certificate_directory -i server_certificate.cert -t P
where certificate_name is an alias that you assign, such as the CA name or host name; and
server_certificate is the prefix of the directory server certificate file.
4. Copy the certificate database directory to the c8_location/configuration directory on every
computer where Content Manager is installed.
5. Configure the directory server to use LDAPS and restart the directory server.
For more information, see the documentation for the directory server.
6. In each Content Manager location where you configured the LDAP namespace to use the directory server, start Cognos Configuration.
7. In the Explorer window, under Security, Authentication, click the LDAP namespace.
8. In the Properties window, for the Host and port property, change the port to the secure LDAPS
port.
For the SSL certificate database property, specify the path to the cert7.db file.
9. In the Explorer window, right-click the LDAP namespace and click Test.
If the test fails, revise the properties, ensuring that the correct certificate is used.
10. From the File menu, click Save.
11. From the Actions menu, click Restart.
12. Repeat steps 6 to 11 on every other computer where Content Manager is installed.
Enabling Single Signon Between LDAP and IBM Cognos 8 Components
You achieve single signon to IBM Cognos 8 components by configuring the External Identity
mapping property.
The External Identity mapping can refer to a CGI environment variable or an HTTP header variable.
In the case of an application server gateway or dispatcher entry pointing to IBM Cognos 8 components, the External Identity mapping can refer to the userPrincipalName session variable. The resolved
value of the External Identity mapping property at runtime must be a valid user DN.
When an LDAP namespace is 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
176
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
or using anonymous if no value is specified. All users who log on to IBM Cognos 8 using external
identity mapping see the same users, groups, and folders as the Bind user.
If you want IBM Cognos 8 components to work with applications that use Java or application
server security, you can configure the External identity mapping property to obtain the user ID
from the Java user principal. Include the token ${environment("USER_PRINCIPAL")} in the value
for the property. For more information, see the online help for IBM Cognos Configuration.
You can apply limited expression editing to the External Identity mapping property using the replace
operation.
Replace Operation
The replace operation returns a copy of the string with all occurrences of the old substring replaced
by the new substring.
The following rules apply:
●
The character \ escapes the characters in the function parameters. Characters such as \ and "
need escaping.
●
Nested function calls are not supported.
●
Special characters are not supported.
Syntax
${replace(str , old , new)}
Parameter
Description
str
The string to search.
old
The substring to be replaced by the new substring.
new
The substring that replaces the old substring.
Examples
${replace(${environment("REMOTE_USER")},"NAMERICA\\",)}
${replace(${environment("REMOTE_USER")},"NAMERICA\\","")}
Configuring IBM Cognos 8 Components to Use eTrust SiteMinder
You can configure IBM Cognos 8 components to use a Netegrity SiteMinder namespace as the
authentication source, provided that you installed Content Manager on a non-Linux computer.
To configure an authentication provider in an eTrust SiteMinder environment, you configure an
LDAP, NTLM, or Netegrity SiteMinder namespace depending on your eTrust SiteMinder configur-
Installation and Configuration Guide 177
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
ation. Supported eTrust SiteMinder configurations are LDAP, Active Directory Server, and NTLM
user directories.
Note: The authentication provider uses an eTrust SiteMinder SDK to implement a custom agent.
The custom agent deployment requires that you set the Agent Properties in the eTrust SiteMinder
Policy server administration console to support 4.x agents.
If you plan to run IBM Cognos 8 products within a 64-bit application server, you cannot configure
a Netegrity SiteMinder namespace as your authentication source.
If eTrust SiteMinder is Configured For More Than One User Directory
If you configured eTrust SiteMinder for more than one user directory, you must use the Netegrity
SiteMinder namespace. After configuring the Netegrity SiteMinder namespace in IBM Cognos 8,
you must also add a corresponding LDAP, Active Directory Server, or NTLM namespace to the
IBM Cognos configuration for each user directory defined in eTrust SiteMinder.
When configuring a corresponding LDAP namespace, ensure that the External identity mapping
property is enabled and that you include the token REMOTE_USER in the value for the property.
This does not mean that you must configure eTrust SiteMinder to set REMOTE_USER. The IBM
Cognos Netegrity SiteMinder namespace passes user information internally to the corresponding
LDAP namespace when it receives successful user identification from the eTrust SiteMinder environment.
When configuring a corresponding Active Directory namespace, ensure that the singleSignOnOption
property is set to IdentityMapping. The IBM Cognos Netegrity SiteMinder namespace passes user
information internally to the corresponding LDAP namespace using the REMOTE_USER environment variable when it receives successful user identification from the eTrust SiteMinder environment.
For more information, see "Enabling Single Signon Between Active Directory Server and IBM
Cognos 8 Components" (p. 155).
If eTrust SiteMinder is Configured With Only One User Directory
If eTrust SiteMinder is configured with only one user directory, the Netegrity SiteMinder namespace
is not required. You can use the user directory as your authentication source by configuring the
appropriate namespace, or you can configure the eTrust SiteMinder provider with one user directory.
For example, if the eTrust SiteMinder user directory is NTML, you can configure IBM Cognos 8
components with an NTLM namespace or configure IBM Cognos 8 components with one Netegrity
SiteMinder namespace, referring to one user directory that is an NTLM namespace.
If the eTrust SiteMinder user directory is Active Directory, you can use an Active Directory namespace
or an LDAP namespace that is configured for use with Active Directory.
If you want to use the user directory as your authentication source directly instead of configuring
a Netegrity SiteMinder namespace, configure the appropriate LDAP (p. 164), Active Directory
(p. 165), or NTLM (p. 181) namespace. In this case, verify the Agent Configuration Object properties
in eTrust SiteMinder Policy Server. Ensure that SetRemoteUser is activated.
When configuring the LDAP namespace, in this case, ensure that the External identity mapping
property is enabled and that you include the token REMOTE_USER in the value for the property.
178
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
When configuring the Active Directory namespace, in this case, ensure that the singleSignOnOption
property is set to IdentityMapping. For more information, see "Enabling Single Signon Between
Active Directory Server and IBM Cognos 8 Components" (p. 155).
To use an eTrust SiteMinder namespace and to set up single signon, do the following:
❑
Configure IBM Cognos 8 components to use a Netegrity SiteMinder namespace
❑
Enable secure communication to the eTrust SiteMinder user directory, if required
❑
Enable single signon between eTrust SiteMinder and IBM Cognos 8
❑
Protect the IBM Cognos Web alias
You can hide the namespace from users during login (p. 162).
Configure a Netegrity SiteMinder Namespace
If you configured eTrust SiteMinder for more than one user directory, you must use the Netegrity
SiteMinder namespace. After adding the Netegrity SiteMinder namespace, you must also add a
corresponding LDAP or NTLM namespace for each user directory.
You can also configure an Netegrity SiteMinder namespace if users are stored in
●
an LDAP server
●
an NTLM server
●
an Active Directory server
Steps
1. On the computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and click New resource,
Namespace.
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 NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 components
can locate and use your existing authentication provider.
7. In the Explorer window, under Security, Authentication, right-click the namespace and click
New resource, SiteMinder Policy Server.
8. In the Name box, type a name for the policy server and click OK.
Installation and Configuration Guide 179
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
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. In the Name box, type a name for the user directory and click OK.
Important: The name of the user directory must match the name that appears on the policy
server.
12. In the Properties window, type a value for the Namespace ID reference property.
13. From the File menu, click Save.
14. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
15. Configure a corresponding LDAP, Active Directory, or NTLM namespace for each LDAP,
Active Directory, or NTLM user directory.
Important: Ensure that you use the same value for the Namespace ID property that you use for
the Namespace ID property for the Netegrity SiteMinder namespace.
Enabling Secure Communication to the eTrust SiteMinder User Directory
If you use an SSL connection to the directory server, you must appropriately configure the Cognos
namespace for the user directory.
For more information, see "Configure an LDAP Namespace" (p. 164).
Enable Single Signon Between eTrust SiteMinder and IBM Cognos 8
By configuring single signon, you are not prompted to reenter authentication information.
IBM Cognos 8 components automatically refer to the eTrust SiteMinder session cookie for user
session data.
If the eTrust SiteMinder user directory is LDAP or Active Directory, you must configure the eTrust
SiteMinder user directory to use external identity mapping to the REMOTE_USER environment
variable.
If the eTrust SiteMinder user directory is NTLM, Integrated Windows Authentication is used for
single signon and no additional configuration is required.
Protecting the IBM Cognos Web Alias
Ensure that eTrust SiteMinder is configured correctly to protect the IBM Cognos Web alias.
Use the test tool provided with eTrust SiteMinder to verify that the resource is protected, authenticated, and authorized. For more information, see your eTrust SiteMinder documentation.
180
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Hide the Namespace from Users During Login
You can hide namespaces from users during login. You can have trusted signon namespaces without
showing them on the namespace selection list that is presented when users login.
For example, you may want to integrate single signon across systems but maintain the ability for
customers to authenticate directly to IBM Cognos 8 without being prompted to choose a namespace.
Steps
1. On each computer where you configured an eTrust SiteMinder authentication provider, open
IBM Cognos Configuration.
2. In the Explorer window, under Security,, Authentication, click the Netegrity Siteminder
authentication provider.
3. In the Properties window, click the box next to Selectable for authentication and then click
False.
4. From the File menu, click Save.
The namespace is not shown on the selection list that is presented at login.
Configuring IBM Cognos 8 Components to Use an NTLM
Namespace
You can configure IBM Cognos 8 components to use the Windows native security, NT LAN
Manager (NTLM), as the authentication source.
If you are not using NTLM in your IS environment, you cannot use an NTLM namespace.
If you want to use an NTLM user directory as your authentication source with eTrust SiteMinder,
you must verify the Agent Configuration Object properties in the eTrust SiteMinder Policy Server.
Ensure that SetRemoteUser is activated.
To use NTLM and to set up single signon, do the following:
❑
configure an NTLM namespace
❑
enable single signon between NTLM and IBM Cognos 8 components
Configure an NTLM Namespace
You can configure IBM Cognos 8 components to use an NTLM namespace when users are stored
in an NTLM user directory. The NTLM user directory may also be accessed using an eTrust SiteMinder authentication provider.
Steps
1. On the computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and click New resource,
Namespace.
Installation and Configuration Guide 181
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click NTLM and click OK.
The new authentication provider resource appears in the Explorer window, under the
Authentication component.
5. In the Properties window, for the NamespaceID property, specify a unique identifier for the
namespace.
Tip: Do not use colons (:) in the NamespaceID property.
6. Specify the values for all other required properties to ensure that IBM Cognos 8 components
can locate and use your existing authentication provider.
7. From the File menu, click Save.
8. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Enable Single Signon Between NTLM and IBM Cognos 8 Components
By default, the IBM Cognos NTLM provider integrates with the IIS Web server for single signon
if Windows integrated authentication (formerly named NT Challenge Response) is enabled on the
IIS Web server.
If Windows integrated authentication is enabled, you are not prompted to reenter authentication
information when accessing IBM Cognos content that is secured by the NTLM namespace.
Steps
1. Set up Windows integrated authentication on the IIS Web server.
2. Install Content Manager on a computer that is part of the domain, for the active and standby
Content Manager computers.
3. Set up the computers, or the user account under which Content Manager runs, to be trusted
for delegation.
4. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
IBM Cognos 8 loads, initializes, and configures the provider libraries for the namespace.
Configuring IBM Cognos 8 to Use SAP
To use an SAP server as your authentication provider, you must use a supported version of SAP BW.
To review an up-to-date list of environments supported by IBM Cognos products, such as operating
systems, patches, browsers, Web servers, directory servers, database servers, and application servers,
visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.
html). In addition, Content Manager must be installed on a non-Linux computer.
182
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
In SAP BW, you can assign users to user groups or roles or both. The SAP authentication provider
uses only the roles.
The authorization rights required by the SAP user depend on who uses IBM Cognos 8 components,
users or administrators.
SAP Authorization Settings for IBM Cognos 8 Users
The following authorization objects are required for any IBM Cognos user. Some of the values
shown, such as *, are default values that you may want to modify for your environment.
Authorization object
Field
S_RFC
Activity
Value
Authorization check for RFC
access
Name of RFC to be protected RFC1 RS_UNIFICATION,
SDTX, SH3A, SU_USER,
SYST, SUSO
S_USER_GRP
Type of RFC to be protected
FUGR
Activity
03
Name of user group
*
User Master Maintenance: User
Groups
SAP Authorization Settings for IBM Cognos 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 IBM
Cognos 8 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
Activity
16
RFC_NAME
PRGN_J2EE, SHSS, SOA3
Authorization check for RFC
access
Type of RFC object to be pro- FUGR
tected
Installation and Configuration Guide 183
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
Connectivity Between SAP BW and IBM Cognos 8 on UNIX
To configure connectivity between SAP BW and IBM Cognos 8 components on a UNIX operating
system, ensure that you install the SAP shared library file (provided by SAP) and add it to the library
path environment variable as follows:
●
Solaris
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<librfccm.so_directory>
●
HP-UX
SHLIB_PATH=$SHLIB_PATH:<librfccm.sl_directory>
●
AIX
LIBPATH=$LIBPATH:<librfc.a_directory>
To use SAP and to set up single signon, do the following:
❑
Configure IBM Cognos 8 components to use an SAP namespace
❑
Enable single signon between SAP and IBM Cognos 8 components
Configure an SAP Namespace
You can configure IBM Cognos 8 components to use an SAP server as the authentication source.
Steps
1. On the computer where you installed Content Manager, open IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication, and click New resource,
Namespace.
3. In the Name box, type a name for your authentication namespace.
4. In the Type list, click SAP 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.
Tip: Do not use colons (:) in the Namespace ID property.
6. Specify the values for all required properties to ensure that IBM Cognos 8 components can
locate and use your existing authentication provider.
Depending on your environment, for the Host property, you may have to add the SAP router
string to the SAP host name.
7. If the SAP system encodes the contents of cookies, enable the decode tickets feature:
184
●
In the Properties window, for Advanced properties, click the Value and then click the edit
button.
●
Click Add.
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
●
Enter the name URLDecodeTickets and enter the value true
●
Click OK.
All SAP logon tickets will be decoded by the SAP namespace before establishing a connection.
8. From the File menu, click Save.
9. Test the connection to a new namespace. In the Explorer window, under Authentication, rightclick the new authentication resource and click Test.
Enable Single Signon Between SAP and IBM Cognos 8
You can enable single signon between SAP Enterprise Portal and IBM Cognos 8 components as
well as when using the external namespace function of the SAP BW data source connections. To
do so, 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
Test the Namespaces
After you configure one or more new namespaces for IBM Cognos 8 components, you can test the
namespaces. The test can occur before or after you start the IBM Cognos 8 service. You can test
all namespaces at the same time or test them individually.
Step to Test All Namespaces
●
In the Explorer window, right-click Authentication and click Test.
IBM Cognos 8 components load, initialize, and configure the provider libraries for one
namespace before testing the next namespace.
Tip: To cancel a namespace test, click Cancel. The test stops when the current namespace test
is complete.
Step to Test a Single Namespace
●
In the Explorer window, under Authentication, right-click the new authentication resource and
click Test.
IBM Cognos 8 components load, initialize, and configure the provider libraries for the
namespace.
Delete an Authentication Provider
If they are no longer required, you can delete namespaces that you added, or unconfigure namespaces
that IBM Cognos 8 components detected.
Installation and Configuration Guide 185
Chapter 8: Configuring IBM Cognos 8 Components to Use an Authentication Provider
You must not delete the Cognos namespace. It contains authentication data that pertains to all
users and is required to save the configuration.
When you delete a namespace, you can no longer log on to the namespace. Security data for the
namespace remains in Content Manager until you permanently delete it in the portal. For more
information, see the Administration and Security Guide.
Steps
1. In each location where you installed Content Manager, open Cognos Configuration.
2. In the Explorer window, under Security, Authentication, right-click the namespace and click
Delete.
3. Click Yes to confirm.
The namespace disappears from the Explorer window and you can no longer log on to the
namespace on that computer.
4. From the File menu, click Save.
5. Repeat steps 1 to 4 for each computer where you installed Content Manager.
You must now log on to the portal and permanently delete the data for the namespace. For
more information, see the Administration and Security Guide.
After you delete a namespace, it appears as Inactive in the portal.
186
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
●
install and configure components in a UNIX or Linux environment that does not have XWindows
Before you set up an unattended installation and configuration, ensure that all the system requirements and prerequisites are met and that all other software that you need is installed and configured.
You can also set up an unattended uninstallation.
To set up an unattended installation and configuration, perform the following tasks:
❑
Configure a transfer specification file (.ats) to specify installation options.
❑
Run the installation tool in silent mode.
❑
Use a pre configured configuration file from another computer.
❑
Run the configuration tool in silent mode.
After you complete these tasks, ensure that the IBM Cognos 8 installation directory on all computers
is protected from unauthorized or inappropriate access. Then you will be ready to use IBM Cognos 8.
Set Up an Unattended Installation
Use a transfer specification file (.ats) to copy IBM Cognos 8 components, including Framework
Manager or Metric Designer, to your computer without being prompted for information.
By default, each time you install IBM Cognos 8 components using the installation wizard, the
options you select are recorded in a transfer specification file. Therefore, if you already installed
IBM Cognos 8 components 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.
You can check if the unattended installation was successful by checking the return status. A value
of zero (0) indicates success and all other values indicate that an error occurred.
Steps Using a File Generated by an Installation on Another Computer
1. Use the installation wizard to install IBM Cognos 8 components on one computer.
Installation and Configuration Guide 187
Chapter 9: Setting Up an Unattended Installation and Configuration
2. Go to c8_location/instlog.
3. Locate the transfer specification file (.ats) that was generated.
The filename format is ts-product_code-version-yyyymmdd_hhmm.ats
where product_code is as follows:
Product_code
Product
C8BISRVR
IBM Cognos 8 BI Server
C8BIMODEL
Framework Manager
CMMSRVR
IBM Cognos Metrics Manager
C8BIMEMOD
Metric Designer
C8BISAMPLES
Samples
LP
Supplementary Languages Documentation
4. Copy the transfer specification file to the computer where you plan to install IBM Cognos 8.
5. On the computer where you plan to install the software, insert the appropriate CD and copy
the contents of the CD to your computer.
6. Open the transfer specification file that you copied in a text editor.
7. In the section named License Agreement, change the ACCEPTED= property to y.
8. Save the transfer specification file in the directory where you copied the contents of the
installation CD.
9. Install IBM Cognos 8:
●
On Windows, open a Command Prompt window, and change to the win32 directory where
you copied the contents of the CD, and then type the following command, where location
is the directory where you copied filename, the transfer specification file:
issetup -s location/filename.ats
●
On UNIX or Linux, change to the directory where you copied the contents of the CD, and
in the directory for your operating system, type the following command, where location is
where you copied filename, the transfer specification file:
./issetup -s location/filename.ats
If a return status other than zero (0) is returned, check the log files for error messages. Errors are
recorded in the c8_location\instlog directory in a summary error log file. The filename format is
tl-product_code-version-yyyymmdd-hhmm_summary-error.txt.
188
Chapter 9: Setting Up an Unattended Installation and Configuration
If errors occur before sufficient initialization occurs, log messages are sent to a log file in the Temp
directory. The filename format is tl-product_code-version-yyyymmdd-hhmm.txt.
Also ensure that the installation directory is protected from unauthorized or inappropriate access.
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 operating system 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. In the section named License Agreement, change the ACCEPTED= property to y.
4. Type the installation location of the program files for IBM Cognos 8 in APPDIR=location.
Tip: There should be no space on either side of the equal sign, (=).
5. For the server components of IBM Cognos 8, 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.
You do not select components for Metric Designer.
All required files are installed.
6. 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 ALLUSERS_FLAG=
property.
7. 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
8. Save the response.ats file to a local directory after you make the necessary changes.
9. Go to the operating system directory.
10. At the command prompt type the following command, where location is the directory where
you copied response.ats:
●
On Windows,
issetup -s location/response.ats
●
On UNIX or Linux,
./issetup -s location/response.ats
Installation and Configuration Guide 189
Chapter 9: Setting Up an Unattended Installation and Configuration
If a return status other than zero (0) is returned, check the log files for error messages. Errors are
recorded in the c8_location\instlog directory in a summary error log file. The filename format is
tl-product_code-version-yyyymmdd-hhmm_summary-error.txt.
If errors occur before sufficient initialization occurs, log messages are sent to a log file in the Temp
directory. The filename format is tl-product_code-version-yyyymmdd-hhmm.txt.
Also ensure that the installation directory is protected from unauthorized or inappropriate access.
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 IBM Cognos 8 components installed. You can then run IBM Cognos
Configuration in silent mode.
The exported configuration contains the properties of the IBM Cognos 8 components that you
installed on the source computer. If you made changes to the global configuration, you must also
copy the global configuration file from the source computer to the computer where you plan to run
an unattended configuration. Global configuration includes such settings as content locale, product
locale, currencies, fonts, and cookie settings. For more information, see "Change Global Settings" (p. 132).
Ensure that the configuration settings on the local computer are appropriate to use to configure
another IBM Cognos 8 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 IBM 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.
Ensure that the folder is protected from unauthorized or inappropriate access.
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
c8_location/configuration directory on the computer where you plan to do an unattended
configuration.
6. Rename the file to cogstartup.xml.
7. If you changed the global configuration on the source computer, copy the coglocale.xml file
from the source computer to the c8_location/configuration directory on the computer where
you plan to do an unattended configuration.
8. Go to c8_location/bin.
190
Chapter 9: Setting Up an Unattended Installation and Configuration
9. Type the configuration command:
●
On UNIX or Linux, type
./cogconfig.sh -s
●
On Windows, type
cogconfig.bat -s
Tip: To view log messages that were generated during an unattended configuration, see the
cogconfig_response.csv file in the c8_location/logs directory.
You can check if the unattended configuration was successful by checking the return status. A
value of zero (0) indicates success and all other values indicate that an error occurred.
IBM Cognos Configuration applies the configuration settings specified in the local copy of cogstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts IBM Cognos 8
service or process.
Set Up an Unattended Uninstallation
Set up an unattended installation and configuration to
●
automate the removal of components on several computers that have the same components
●
remove components in a UNIX or Linux environment that does not have XWindows
Steps
1. Go to c8_location/instlog.
2. Open the transfer specification .ats file for the product in a text editor:
The filename format of the transfer specification .ats file is ts-product_code-version-yyyymmdd_hhmm.ats
where product_code is as follows:
Product_code
Product
C8BISRVR
IBM Cognos 8 BI Server
C8BIMODEL
Framework Manager
CMMSRVR
IBM Cognos Metrics Manager
C8BIMEMOD
Metric Designer
C8BISAMPLES
Samples
LP
Supplementary Languages Documentation
Installation and Configuration Guide 191
Chapter 9: Setting Up an Unattended Installation and Configuration
If you have more than one .ats file for a product, you only need to edit one of the .ats files.
3. In the section named [Component List], specify the components to remove.
●
To remove the component, type 1
●
To leave the component installed, type 0
4. Save and close the file.
5. Go to the operating system directory.
6. At the command prompt, type the following command, where filename is the name of the
transfer specification .ats file that you edited:
●
On Windows,
uninst -u -s c8_location/instlog/filename.ats
●
On UNIX or Linux,
./uninst -u -s c8_location/instlog/filename.ats
7. Repeat the entire procedure for each product that you want to uninstall.
192
Appendix A: Troubleshooting
Use this troubleshooting reference information as a resource to help you solve specific problems
you may encounter during or after the installation of IBM Cognos 8 Analytic Applications.
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, you can fix each
problem by implementing a series of actions.
When you cannot resolve a problem, the final resource is your IBM 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.
Log Files
Log files can help you troubleshoot problems by recording the activities that take place when you
work with a product. Operations performed in IBM Cognos 8 are recorded in various log files for
tracking purposes. For example, if you experienced problems installing IBM Cognos 8, consult the
transfer log file to learn what activities the installation wizard performed while transferring files.
Use IBM Cognos Configuration to specify the size, number, and location of log files, and to configure
the properties of the log server.
When troubleshooting, the following files can assist 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 c8_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-C8BISRVR-8.1-0.0-20080901_1122.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 c8_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-C8BISRVR-8.1-0.0-20080901_1122_summary_error.txt
The Startup Configuration File
This file records your configuration choices each time you save your property settings. The file
name is cogstartup.xml. If you are unable to save your configuration, or are having problems you
Installation and Configuration Guide 193
Appendix A: Troubleshooting
can revert to a previously saved configuration file. The backup configuration files are located in
the c8_location/configuration directory. The following is an example of the file name format for
backup configuration files:
cogstartup_200811231540.xml
The Startup Configuration Lock File
This file is created each time you open IBM Cognos Configuration. It prevents you from opening
more than one IBM Cognos Configuration window. If you experience problems opening IBM
Cognos Configuration, you can check the c8_location/configuration directory for the cogstartup.lock
file. If the file exists and IBM Cognos Configuration is not open, it means that IBM Cognos
Configuration did not shut down properly the last time you used it. You can delete the lock file
and then open IBM Cognos Configuration.
The Locale Configuration File
This file records the configuration choices you make in IBM 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 c8_location/configuration directory. The following is an example of
the file name format:
coglocale_200811231540.xml
The Run-Time Log File
The default IBM Cognos log file named cogserver.log file, or other log files that you configure to
receive log messages from the log server, record information after you start the IBM Cognos 8 service.
They are located in the c8_location/logs directory. If you configured another destination for log
messages, check the appropriate file or database.
Some log messages indicate problems. Most messages provide information only, but others can
help you to diagnose problems in your run-time environment.
The Gateway Log File
The gateways record errors in the gateway log file, which is located in the c8_location/logs directory.
You can use the gateway log file to troubleshoot problems that prevent the gateway from processing
requests or from using encryption. Symptoms of these problems are user IDs and passwords do not
work, single signon does not work, and the dispatcher is running but users receive the following
error message: The IBM Cognos BI server is not available. The gateway log file uses the
following naming format, where gateway_interface is cgi, mod (Apache 1.3 module), mod2 (Apache
2.0 module), or isapi.
gwgateway_interface.log (for example, gwcgi.log)
The Uninstallation Log File
This file records the activities that the Uninstall wizard performed while uninstalling files. The log
file is named cognos_uninst_log.htm and is located in the Temp directory. You can use the log file
to troubleshoot problems related to uninstalling IBM Cognos 8 components.
194
Appendix A: Troubleshooting
The Silent Mode Log File
This file records the activities that IBM Cognos Configuration performed while running in silent
mode. This log file is named cogconfig_response.csv and is located in the c8_location/logs directory.
Windows Event Viewer
Windows Event Viewer provides information about program, security, and system events. For
example, if the IBM Cognos 8 service fails to start, this fact is recorded in the event log.
For information about how to use Windows Event Viewer, see the Windows help.
Microsoft Internet Information Services (IIS) Log File
This file records Microsoft Internet Information Services (IIS) activities. The log file is found in the
c8_location/windows/system32/logFiles/W3SVC1 directory. You can use this log file to troubleshoot
problems related to your IIS Web server. For example:
●
Code 404 is a page not found error.
Your virtual directory may not be configured correctly.
●
Code 304 is a security credential error.
Your directory security may not be configured correctly.
●
Code 200 indicates that IIS is working correctly.
The problem you are encountering is not related to your IIS Web server.
For more information, see the Microsoft Internet Information Services help.
Problems Starting IBM Cognos 8
You may encounter problems when you try
●
to start the IBM Cognos 8 service
●
to open the Welcome page for the IBM Cognos 8 portal for the first time
●
to start an application server, such as WebLogic or WebSphere
Symptoms
Solution
You do not see the splash screen for the IBM Check your Web server configuration.
Cognos 8 portal when you start IBM Cognos 8.
The service starts but no tables are created in
the content store database.
Check your content store configuration.
The service does not start.
Ensure that you wait a few moments before
submitting a request.
Installation and Configuration Guide 195
Appendix A: Troubleshooting
Symptoms
Solution
The application server does not start.
Check the file permissions and directory names
of the application server installation location.
Ensure that you use other software that is supported by IBM Cognos components. You can view
an up-to-date list of environments, such as operating systems, patches, browsers, Web servers, directory servers, and database servers on the IBM Cognos Resource Center (http://www.ibm.com/
software/data/support/cognos_crc.html).
CFG-ERR-0106 Error When Starting the IBM Cognos 8 Service in IBM Cognos
Configuration
When you start the IBM Cognos 8 service, you may receive the following error message:
CFG-ERR-0106 Cognos Configuration received no response from the Cognos 8 service in the
allotted time. Check that Cognos 8 service is available and properly configured.
There are two possible causes for this problem:
●
The IBM Cognos 8 service needs more time to start.
●
A standby Content Manager computer may be configured incorrectly.
The IBM Cognos 8 Service Needs More Time
By default, IBM Cognos Configuration checks the progress of the start request every half second
for three minutes. If IBM Cognos Configuration does not receive a response within this time, the
error message appears.
To avoid this error, you can change the amount of time that IBM Cognos Configuration waits to
receive a response from the IBM Cognos 8 service. You do this by configuring the ServiceWaitInterval and ServiceMaxTries properties in the c8_location/configuration/cogconfig.prefs file.
The ServiceWaitInterval property represents the time interval, in milliseconds, at which IBM Cognos
Configuration checks the progress of the start request. By default, its value is 500, which is equivalent
to half a second.
The ServiceMaxTries property represents the number of times that IBM Cognos Configuration
checks the progress of the start request. By default, its value is 360.
Content Manager Is Configured Incorrectly
If the error message appears on a standby Content Manager computer, the setting for storing the
symmetric keys may be incorrect.
To avoid this problem, configure the standby Content Manager computer to store the symmetric
keys locally.
Steps to Change the Wait Time
1. Using IBM Cognos Configuration, stop the IBM Cognos 8 service.
2. Open the c8_location/configuration/cogconfig.prefs file in an editor.
196
Appendix A: Troubleshooting
This file is created automatically the first time you open IBM Cognos Configuration.
3. Add the following code to the file:
ServiceWaitInterval=number of milliseconds
ServiceMaxTries=number of times
Tip: Add the numeric values that correspond to your configuration needs.
4. Save the file.
5. Using IBM Cognos Configuration, start the IBM Cognos 8 service.
Steps to Store Symmetric Keys Locally
1. On the standby Content Manager computer, start IBM Cognos Configuration.
2. In the Explorer window, under Security, click Cryptography.
3. In the Properties window, under CSK settings, set Store symmetric key locally to True.
4. From the File menu, click Save.
5. From the Actions menu, click Start.
This action starts all installed services that are not running. If you want to start a particular
service, select the service node in the Explorer window and then click Start from the Actions
menu.
Unable to Start the IBM Cognos 8 Service Because the Port is Used by Another
Process
You may not be able to start the IBM Cognos 8 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 IBM Cognos Configuration to change the default port that IBM Cognos 8 uses.
When you change the port used by the local dispatcher, you must change the value of the Dispatcher
URI properties. 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 want to change the dispatcher
port, replace 9300 in all dispatcher and Content Manager URIs with the new port number.
Steps to Change the Default Port
1. Start IBM Cognos Configuration.
2. In the Explorer window, click the appropriate group or component:
●
To access the port number in the dispatcher and Content Manager URIs, click Environment.
●
To access the port number for the local log server, under Environment, click Logging.
Installation and Configuration Guide 197
Appendix A: Troubleshooting
●
To access the shutdown port number, under Environment, click IBM Cognos 8 service,
IBM Cognos 8.
●
To access the port number for the location of the applications.xml file used by Portal Services, under Environment, click Portal Services.
3. In the Properties window, click the Value box next to the property that you want to change.
4. Change the value from 9300 to the new value.
Ensure that you change the ports in all URIs that contain localhost:9300.
5. From the File menu, click Save.
6. From the Action menu, click Start.
IBM Cognos 8 Service Does Not Start or Fails After Starting
You start the IBM Cognos 8 service but services either do not start correctly or are very slow to
start. After services start, the system fails a short time afterwards. While services are starting, Java
uses 100 percent of the CPU time. You may also receive multiple occurrences of error messages
such as the following:
●
DPR-DPR-1035 Dispatcher detected an error.
●
CAM-CRP-1157 Unable to synchronize the local common symmetric key store with Content
Manager.
If you use a DB2 database for the content store, ensure that the database version and Java version
are compatible. For DB2 version 8.2, Java 1.5 is not supported. For DB2 version 9, Java 1.5 is
supported on all operating systems except HPUX and Solaris.
To review an up-to-date list of environments supported by IBM Cognos products, such as operating
systems, patches, browsers, Web servers, directory servers, database servers, and application servers,
visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.
html).
IBM Cognos 8 Server Fails to Start and Gives No Error Message
A IBM Cognos 8 server may fail to start after an upgrade or new installation, but no error message
appears. This may occur when a previously running or new IBM Cognos 8 server is configured to
use a large amount of memory.
If the server on which IBM Cognos 8 is installed contains version 1.0 of Microsoft security update
921883, there may be an issue when a lot of contiguous memory is requested by an application.
This is a known issue with version 1.0 of Microsoft security patch 921883. Microsoft distributed
a second version of the patch to fix the problem. As a workaround, uninstall the first security patch,
or install version 2.0 of the patch. Alternatively, you can configure the IBM Cognos 8 server to use
less memory.
For more information, see the Microsoft knowledge base article about programs using a lot of
contiguous memory failing, at http://support.microsoft.com.
198
Appendix A: Troubleshooting
IBM Cognos BI Server Not Available When Starting IBM Cognos 8
After you configure IBM Cognos components and start the IBM Cognos 8 services, when you
connect to the IBM Cognos 8 portal, the following error message may appear:
The Cognos Gateway is unable to connect to the Cognos BI server.
The server may be unavailable, or the gateway may not be correctly configured.
Check the IBM Cognos server log file for more information. By default, the cogserver.log file is
located in the c8_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 IBM 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 for the content
store 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-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 for the content
store is not supported.
CM-SYS-5124 The content store database server uses the code page 1252.
●
For Sybase:
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 for the content
store is not supported.
For Content Manager to connect to the content store, the content store must use the appropriate
character encoding.
Installation and Configuration Guide 199
Appendix A: Troubleshooting
Database
Character encoding
Oracle 9i
AL32UTF8
AL32UTF16
DB2 UDB
Codeset UTF-8
Sybase ASE
UTF-8
Microsoft SQL Server
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 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-CFG-5063 A Content Manager configuration error was detected while connecting to the content
store.
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 <parameter>.
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 not case sensitive. For more information, see the database documentation.
Invalid Configuration Settings
If the following or similar messages appear in the log file, you did not configure the content store
correctly in IBM Cognos Configuration.
●
For Microsoft SQL Server:
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the
content store.
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-CFG-5063 A Content Manager configuration error was detected while connecting to the
content store.
200
Appendix A: Troubleshooting
CM-SYS-5003 Content Manager is unable to access the content store. 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-5063 A Content Manager configuration error was detected while connecting to the
content store.
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.
●
For Sybase:
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the
content store.
CM-CFG-5036 Content Manager failed to connect to the content store. The connection string
is "jdbc:sybase:Tds:localhost:5000/cm".
JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect.
If you are using an Oracle database, do not use illegal characters such as an underscore in IBM
Cognos Configuration for the Service Name property. If the Service Name includes illegal characters,
tables are not created in the content store database when the IBM Cognos 8 service is started.
Steps for Microsoft SQL Server, Oracle, DB2, and Sybase
1. On the computer where you installed Content Manager, start IBM Cognos Configuration.
2. In the Explorer window, under Data Access, Content Manager, right-click Content Store and
click Delete.
This deletes the default resource. Content Manager must be configured 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.
If you are upgrading and want to use an existing content store, ensure that you select the type
of database you use for the older version of ReportNet or IBM Cognos 8.
If you installed more than one version of IBM Cognos 8, you must use a different content store
for each version. When a content store is used by a new version of IBM Cognos 8, it cannot
be used by an older version of ReportNet or IBM Cognos 8.
Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection,
select Oracle database (Advanced).
6. In the Properties window, provide values depending on your database type:
Installation and Configuration Guide 201
Appendix A: Troubleshooting
●
If you use a Microsoft SQL Server database, type the appropriate values for the Database
server with port number or instance name and Database name properties.
For a Microsoft SQL Server database, you can choose to use a port number, such as 1433,
or a named instance as the value for the Database server with port number or instance
name property.
To connect to a named instance, you must specify the instance name as a JDBC URL
property or a data source property. For example, you can type localhost\instance1. If no
instance name property is specified, a connection to the default instance is created.
Note that the properties specified for the named instance, along with the user ID and
password, and database name, are used to create a JDBC URL. Here is an example:
jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required
●
If you 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.
●
If you use an advanced Oracle database, for the Database specifier property, type the Oracle
Net8 keyword-value pair for the connection.
Here is an example:
(description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl)))))
●
If you use a Sybase database, type the appropriate values for the Database server and port
number and Database name properties.
7. If you want to change the logon credentials, specify a user ID and password:
●
Click the Value box next to the User ID and password property and then click the edit
button when it appears.
●
Type the appropriate values and click OK.
8. From the File menu, click Save.
The logon credentials are immediately encrypted.
9. Test the connection between Content Manager and the content store.
Tip: In the Explorer window, right-click the new database and click Test.
Content Manager connects to the database, checks the database permissions, and creates and
populates a table. The table is not deleted and is used each time that the test is repeated.
Cannot Log On to a Namespace When Using IBM Cognos Connection
You open IBM Cognos 8 through IBM Cognos Connection. However, when you attempt to create
a data source and log on to a namespace, the following error messages appear:
●
202
PRS-CSE-1255 Exception error encountered in data decryption.
Appendix A: Troubleshooting
●
CAM-CRP-1064 Unable to process the PKCS #7 data because of an internal error. Reason:
java.lang.IndexOutOfBoundsException.
This issue may occur if you do not have the necessary permissions for the following directories:
●
c8\configuration
●
c8\configuration\csk
●
c8\configuration\encryptkeypair
●
c8\configuration\signkeypair
The solution is to enable the read and execute permissions on the directories listed above for anyone
who must start the IBM Cognos 8 service.
IBM Cognos 8 Services Fail to Restart After a Network Outage
The IBM Cognos Bootstrap Service restarts IBM Cognos 8 services after a network outage for
Tomcat installations where a network IP address is specified in the internal dispatcher URI. During
the restart, the IBM Cognos 8 services may not initialize successfully, requiring a manual restart
after the network is restored.
To resolve the problem, configure the Internal dispatcher URI property in IBM Cognos Configuration
to use localhost or the network host name.
No Warning That Installing a Later Version of IBM Cognos 8 Will Automatically
Update the Earlier Version of the Content Store
You have a version of IBM Cognos 8 installed on your computer. You install a later version into
a new location. You use the same database for the content store for both versions. After you configure the later version and start the IBM Cognos 8 service, the earlier version of IBM Cognos 8 no
longer works because all content is automatically upgraded.
If you want to use different versions of IBM Cognos 8 after you upgrade, ensure that before you
install the later version, you
●
back up the database you use for the content store
●
restore the backup to a new location
Alternatively, you can choose to use the deployment tool to import the entire content store from
an earlier version to the later version. All existing content in the content store database is replaced
by the imported content. You receive a warning message about this.
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.
Installation and Configuration Guide 203
Appendix A: Troubleshooting
Content Manager Error When Starting IBM Cognos 8
After starting IBM Cognos 8, no BIBUSTKSERVMA process is started. There are errors listed in
the pogo******.log and cogserver.log files. Users receive errors in the browser when connecting
to the IBM Cognos 8 portal.
In the pogo******.log file, an error related to Content Manager appears.
In the cogserver.log file, the following error appears:
An attempt to register the dispatcher in Content Manager was unsuccessful. Will retry periodically.
When connecting to http://computer name/cognos8, the following error messages appear in the
browser:
●
DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still
initializing
●
SoapSocketException: Connection Refused
IBM Cognos Configuration uses a user ID to bind to the LDAP database. If this user ID is moved
to another group, IBM Cognos Configuration can no longer locate it.
To correct the problem, move the user ID back to the original group.
The Page Cannot Be Found When Starting IBM Cognos 8 in Windows 2003
After installing IBM Cognos 8 on Windows 2003, the following message may appear when you try
to start IBM Cognos 8:
The page cannot be found. The page you are looking for might have been removed, had its name
changed, or is temporarily unavailable. HTTP Error 404 - File or Directory not found.
This error is caused by a security feature in Windows 2003 Internet Information Services (IIS). This
security feature does not allow unknown cgi file extensions.
To resolve this problem, add a new file extension in IIS for the cognos.cgi file. For more information,
see the IIS documentation.
The Page Is Not Shown When Opening a Portal After Installing IBM Cognos 8
After you install and configure IBM Cognos 8, you are unable to connect to the Cognos 8 portal.
This may be because the Web server is not properly configured. For example, the virtual directories
required for IBM Cognos 8 may not exist or they may point to the wrong physical folders.
For information about configuring the Web server, see the Installation and Configuration Guide.
DPR-ERR-2058 Error Appears in Web Browser When Starting IBM Cognos 8
After you start the services in IBM Cognos Configuration and then try to open the portal, a message
similar to one of the following may appear:
DPR-ERR-2058 The dispatcher encountered an error while servicing a request. XTS handler must
be initialized before being invoked.
204
Appendix A: Troubleshooting
DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still initializing. Please try again or contact your administrator.
These error messages usually occur when the dispatcher cannot communicate with Content Manager.
To help you determine the specific cause, look in the cogserver.log file in the c8_location/logs
directory. The most common causes are listed below, with solutions.
IBM Cognos Services are Not Done Initializing
After you start the services in IBM 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.
Content Manager is Not Available
In a distributed installation, ensure that Content Manager is installed, configured, and running.
Ensure also that the other IBM Cognos computers are configured with the correct Content Manager
URI.
The Content Store is Not Available or is Not Configured Properly
Ensure that the content store database was created and that you configured it correctly in IBM
Cognos Configuration.
Tables are Not Created in the Content Store
Ensure that you are using a version of DB2, Microsoft SQL Server, Oracle, or Sybase that is supported by IBM Cognos components.
The Logon Credentials for the Content Store Are Incorrect
Check whether the information changed. For example, DB2 reads information from the NT user
management. If the password for the NT account changed, you must also change the logon credentials
for the content store in IBM Cognos Configuration.
Check for special characters in the logon password. Occasionally, the JDBC driver does not accept
characters that are reserved for xml, such as %, !, <, and >.
The User Does not Have Appropriate Permissions
Ensure that the user has the appropriate permissions.
Out of Memory on HP-UX
If you are using Tomcat, you can determine the issue is related to HP-UX server configuration. You
may be exceeding the expected maximum number of simultaneously active threads per process.
Steps to Check for an HP-UX Configuration Problem
1. In the /bin/startup.sh file, find
../tomcat4.1.27/bin/catalina.sh start "$@"
2. Change it to the following:
../tomcat4.1.27/bin/catalina.sh run "$@"
The run command causes the Tomcat output to appear in the console window for IBM Cognos 8.
Installation and Configuration Guide 205
Appendix A: Troubleshooting
3. Stop and restart IBM Cognos 8 using the ./shutdown.sh and ./startup.sh commands.
If the following error message appears in the console window for any of the application servers,
the issue is an HP-UX configuration problem:
OutofMemoryException error: Unable to create new native thread on HP-UX.
The problem is that the default values for HP-UX 11.0 and 11i are set too low for most Java
applications.
Tip: You can check the number of threads in your process by using the -eprof option available
in JDK 1.1.8 and by analyzing the Java.eprof file using HPjmeter by selecting the threads metric.
Steps to Increase the maximum Number of Threads Per Process
1. Have your system administrator change the Kernel parameter as follows:
●
max_thread_proc = 512
●
nkthread = 1024
2. Ensure that the ulimit settings are unlimited.
Content Manager Cannot Connect to the Content Store on Oracle
If you are using an Oracle database as a content store, the DPR-ERR-2058 error may be generated
when logging onto the portal http://host_name/cognos8. All tables are created on the database.
You may also receive the following error messages:
●
CM-CFG-5036 Content Manager failed to connect to the content store.
●
ORA-01017: invalid username/password; logon denied
Steps to Set the Oracle Database Server Name
1. In the Explorer window, click Data Access, Content Manager, Content Store.
2. Change the Oracle database server name to a fully qualified name such as host_name.companyname:1534 to match the name in the tnsnames.ora file.
DPR-ERR-2022 Error Appears in Web Browser When Starting IBM Cognos 8
After you start the services in IBM Cognos Configuration and then try to open the portal, a message
similar to the following 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.
Opening the Portal Too Soon
This problem can occur if you try to open the portal before IBM Cognos services are initialized.
To avoid this problem, after you start the services in IBM 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.
206
Appendix A: Troubleshooting
The system.xml File Contains Errors
The system.xml file may have been edited.
Replace the system.xml file in the c8_location\templates\ps\portal directory with a copy from backup
or use an XML editor to edit it.
Unable to Download the cognos.xts File
After installing IBM Cognos 8, you are prompted to download the cognos.xts file when connecting
to the IBM Cognos 8 portal. The following error message may appear:
You have chosen to download a file from this location. cognos.xts from servername
This problem occurs when the permissions on the virtual directories are not set properly. You must
provide the cgi-bin virtual directory in the Microsoft Internet Information Service (IIS) with execute
permissions.
To resolve this problem, recreate the virtual directories in IIS with the following permissions.
Alias
Path
Permissions
cognos8
c8_location\Program Files\
Cognos\c8\webcontent
Read
cognos8\ cgi-bin
c8_location\Program Files\
Cognos\c8\cgi-bin
Read Execute
cognos8\help
c8_location\Program Files\
Cognos\c8\webcontent\
documentation
Read
Application Server Startup Script Fails
You may have problems running the startup scripts for an application server to deploy the IBM
Cognos application if IBM Cognos 8 components are installed in a directory with a name that
includes spaces.
To resolve this problem, rename the directory and do not include spaces in the new name. If this
solution is not easily handled by the startup scripts, try adding quotation marks around the directory
name that includes spaces or use the 8.3 DOS naming convention.
Deploying IBM Cognos 8 to an Oracle Application Server or IBM WebSphere
Application Server Fails
Deploying IBM Cognos 8 to an Oracle application server or an IBM WebSphere application server
may fail with any of the following errors:
●
Browser timeout in administration console
●
Error Message: HTTP 500 Internal Error
Installation and Configuration Guide 207
Appendix A: Troubleshooting
●
Error Message: Deployment failed: Base Exception: java.rmi.RemoteException (Oracle)
●
Return to application file selection page (IBM WebSphere)
These errors can occur because the application file that you are trying to deploy is too large.
To solve this problem, do the following:
●
If you are using the Build Application Wizard, clear the Include static files from the Webcontent
folder check box when you select the application to build.
This will reduce the size of the application file. If static content is required, you can manually
copy it to the deployed application location after you have successfully deployed IBM Cognos 8
into the application server.
●
If you are deploying the application file manually for an Oracle application server, type the
following command:
dcmctl deployapplication -f path_and_name_of_ear_file -a application_name -co
OC4J_instance_name
This command is not supported for Oracle Release 3.
For more information about deploying IBM Cognos 8 to an application server, see the Installation
and Configuration Guide.
Unable to Deserialize Context Attribute Error When Deploying the p2pd.war File
to WebLogic
When you deploy the p2pd.war file to WebLogic, you may see the following error:
Error [context]Could not deserialize context attribute
java.io.NotSerializableException: com.cognos.logserver.LogService
This error does not affect the deployment of the p2pd.war file.
To avoid this problem, add at least one language preference in Internet Explorer.
Error Appears After Upgrading IBM Cognos 8 on a WebLogic Application Server
You are using WebLogic and upgrade IBM Cognos 8 from an earlier release. After you deploy the
p2pd.war file for the new installation, a message similar to the following may appear:
<BEA-101215> <Malformed Request "null". Request parsing failed, Code: -10>
This can occur if you undeploy IBM Cognos 8 from WebLogic and some files from the earlier version
are not removed from the system.
To solve this problem, use the administrative tools for your application server to ensure that IBM
Cognos 8 has been undeployed. For information about undeploying applications, see your application
server documentation.
If the directory to which IBM Cognos 8 was originally deployed is not removed during the undeploy
process, delete the directory. Also, remove any IBM Cognos 8 .jar files that are cached in your
application server environment. For example, in WebLogic 7.0, .jar files are sometimes left in %WL_
208
Appendix A: Troubleshooting
HOME%\user_projects\<domain-name>\<managed-server-name>\.wlnotdelete\c8_p2pd_p2pd\
jarfiles
You can remove them by deleting the WEB-INF directory.
In WebLogic 8.1.2, the cache location is %WL_HOME%\user_projects\domains\<domainname>\<managed-server-name>\.wlnotdelete\extract\c8_p2pd_p2pd\jarfiles
After you remove all files from the previous installation, you can redeploy IBM Cognos 8.
Problems Configuring IBM Cognos 8
After you install IBM Cognos 8 components, you may encounter problems when you save changes
in IBM Cognos Configuration.
Ensure that you
●
configure and start the services on the computer where Content Manager is located before you
configure other components
●
restart the IBM Cognos 8 service after you make any configuration changes
Run Database Cleanup Scripts
In some troubleshooting situations, you may be advised to start with new configuration data.
You can run an SQL script to delete all the tables in any of the following databases that IBM
Cognos 8 components use:
●
content store for data that IBM Cognos 8 needs to operate
●
delivery database for report notifications
●
log database for log messages
When you delete a table, its structural definition and data are deleted permanently from the database.
When you restart the IBM Cognos 8 service, a new set of required database tables are created
automatically in the location specified by your configuration settings.
Steps
1. On each computer where Content Manager is located, stop the IBM Cognos 8 service.
2. Go to the appropriate directory:
●
To delete tables from the log database, go to c8_location\configuration\schemas\logging.
●
To delete tables from the content store, go to c8_location\configuration\schemas\content.
●
To delete tables from the notification database, go to c8_location\configuration\schemas\
delivery.
3. Go to the appropriate database directory.
Installation and Configuration Guide 209
Appendix A: Troubleshooting
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 store
DB2
dbClean_db2.sql
Derby
dbClean_derby.sql
Microsoft SQL Server
dbClean_mssqlserver.sql
Oracle
dbClean_oracle.sql
Sybase
dbClean_sybase.sql
DB2
NC_DROP_DB2.sql
Derby
NC_DROP_Derby.sql
Microsoft SQL Server
NC_DROP_MS.sql
Oracle
NC_DROP_ORA.sql
Sybase
NC_DROP_SYBASE.sql
DB2
LS_dbClean_db2.sql
Derby
LS_dbClean_derby.sql
Microsoft SQL Server
LS_dbClean_mssql.sql
Oracle
LS_dbClean_oracle.sql
Sybase
LS_dbClean_sybase.sql
Notification
Log
5. Start the IBM Cognos 8 service.
Error Trying to Encrypt Information When Saving Your Configuration
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.
The cryptographic information cannot be encrypted. Do you want to save the configuration in
plain text?
210
Appendix A: Troubleshooting
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. In addition, ensure that your Java environment is configured correctly, the URIs are correct, and the same certificate authority password
is configured for all Content Manager computers.
On Linux, ensure that you copied the appropriate .jar files to the installation location of your Java
Runtime Environment.
Also, an error message similar to the following may appear:
java.lang.NoClassDefFoundError: javax/net/ServerSocketFactory.
The cryptographic error usually means the Java environment is not configured correctly. Ensure
that the JAVA_HOME environment variable is set correctly and the appropriate security providers
are installed, such as JSSE for JRE 1.31.
Steps to Check the Configuration
1. On the Content Manager computer, start IBM Cognos Configuration.
2. In the Explorer window, click Environment.
3. In the Properties window, verify these properties:
●
Under Gateway Settings, Gateway URI
●
Under Dispatcher Settings, External dispatcher URI and Internal dispatcher URI
●
Under Other URI Settings, Dispatcher URI for external applications and Content Manager
URIs
4. In the Explorer window, click Security, Cryptography, Cognos.
5. In the Properties window, under Certificate Authority settings, click the value for Password.
Ensure that the same password is used on all Content Manager computers.
6. Save the configuration and restart IBM Cognos 8.
Problems Generating Cryptographic Keys in IBM Cognos Configuration
When you uninstall IBM Cognos 8, some temporary folders are left behind. Reinstalling the product
to the same location without first removing the temporary folders may cause problems while
attempting to generate the cryptographic keys in IBM Cognos Configuration.
To resolve this problem, uninstall IBM Cognos 8, remove the c8_location/temp/cam folder, and
install IBM Cognos 8 again.
Installation and Configuration Guide 211
Appendix A: Troubleshooting
Configuration Data is Locked by Another Instance of IBM
Cognos Configuration
You may get an error message that the configuration data is locked by another instance of IBM
Cognos Configuration.
When you start IBM Cognos Configuration, it checks to see if the cogstartup.lock file exists in
c8_location/configuration. The file may exist if a previous instance did not shut down properly or
if another instance of IBM Cognos Configuration is running.
If another instance of IBM 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 IBM Cognos Configuration is running, delete the cogstartup.lock file in
c8_location/configuration.
If the IBM Cognos 8 service is stopped, click Start.
Unable to Exit a Tab Sequence When Using Keyboard-only
Navigation in IBM Cognos Configuration
If you use the Tab key to navigate in IBM 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 IBM Cognos Configuration is a Java application, when you want to close the
Properties window, you must press Ctrl+Tab.
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, DB2, or Sybase. You
cannot replace the Cognos namespace. You can recreate it, but you must then recreate your Cognos
groups and roles.
For more information about creating groups and roles in IBM Cognos Connection, see the
Administration and Security Guide.
Steps to Recreate the Cognos Namespace
1. Start IBM Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication and then click New resource,
Namespace.
3. In the Name box, type a name for the resource.
4. In the Type box, click Cognos, and then click OK.
The Cognos namespace appears in the Explorer window.
212
Appendix A: Troubleshooting
5. From the File menu, click Save.
Java Error When Starting IBM Cognos Configuration
When you start IBM Cognos Configuration, you may receive an error message that the Java Runtime
Environment (JRE) has changed and that the current cryptographic information is not compatible
with the new JRE. You may then be prompted to regenerate the cryptographic information for the
new JRE or exit to switch back to the previous JRE.
This error may occur for one of these reasons:
●
Your configuration data was encrypted using a different JRE than the one IBM Cognos 8
components are currently using.
●
The cryptographic information may have been corrupted.
If you click Regenerate in the error dialog, the IBM Cognos 8 service is stopped and the cryptographic
information is regenerated.
If you click Exit in the error dialog, you must set the JAVA_HOME environment variable to point
to the JRE that you used to save your configuration.
On Windows, if you want IBM Cognos 8 components to use the JRE that is installed by default,
unset JAVA_HOME or set JAVA_HOME to c8_location/bin/jre.
Note: If you want to change from one JRE to another, see the topic on changing the version of JVM
that IBM Cognos 8 components use. For more information, see the Installation and Configuration
Guide.
Cryptographic Error When Starting IBM Cognos Configuration
When you start IBM Cognos Configuration, the following error message may appear:
The cryptographic information may have been corrupted or the cogstartup.xml file is invalid. You
may have to fix this file or remove it from disk. For more information, see the Installation and
Configuration Guide.
This error occurs when IBM Cognos 8 components detect an error in the cogstartup.xml file. This
can occur when the cogstartup.xml file is manually edited and there is an error in the changed text.
To resolve the problem, replace the cogstartup.xml file with a copy from your backup location.
Current Configuration Settings Are Not Applied to Your Computer
You change default property values or add a resource to your installation in IBM 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.
Installation and Configuration Guide 213
Appendix A: Troubleshooting
To apply the new settings to your computer, you must restart the IBM Cognos 8 service.
Steps to Restart the IBM Cognos 8 Service
1. Start IBM Cognos Configuration.
2. From the Actions menu, click the appropriate command:
●
If the IBM Cognos 8 service is currently running, click Restart.
This action starts all installed services that are not running and restarts services that are
running. If you want to restart a particular service, select the service node in the Explorer
window and then click Restart from the Actions menu.
●
If the IBM Cognos 8 service is stopped, click Start.
This action starts all installed services that are not running. If you want to start a particular
service, select the service node in the Explorer window and then click Start from the Actions
menu.
CM-CFG-029 Error When Trying to Save a Configuration That
Specifies a SQL Server Content Store
In IBM Cognos Configuration, you try to save a configuration and the following error message
appears in the cogserver.log file:
CM-CFG-029 Content Manager is unable to determine whether the content store is initialized.
EXECUTE permission is denied on object "sp_tables", database "master", owner "dbo'.
This indicates that you do not have the correct permissions to initialize a content store or create a
table in the database.
The solution is to ensure that the content store user has permissions to use the sp_tables stored
procedure in the master database.
Users are Prompted for Active Directory Credentials
The single signon mechanism does not work when IBM Cognos 8 is configured as follows:
●
Microsoft Internet Explorer runs on a Windows NT computer.
●
The authentication namespace is configured with the Active Directory provider.
●
Microsoft Internet Explorer on a Windows 2000 or Windows 2003 server is configured for
Integrated Windows Authentication.
As a result, users are prompted for their Active Directory credentials.
This problem occurs because the IBM Cognos 8 Active Directory provider uses ADSI protocol and
Kerberos delegation for authentication in a single signon environment. When Microsoft Internet
Explorer runs on Windows NT, it cannot authenticate to the IIS server using Kerberos delegation.
214
Appendix A: Troubleshooting
When your system is configured for Windows Integrated Authentication, for the single signon to
work with IIS, you must
●
configure IBM Cognos 8 to communicate with the Active Directory server using the LDAP
provider.
●
configure the external identity mapping property to read the REMOTE_USER environment
variable.
Font on UNIX Not Found When Starting IBM Cognos Configuration
When you start IBM 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 IBM 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.
Group Membership is Missing From Active Directory Namespace
If an Active Directory namespace is configured for the same forest and a user is authenticated using
a credential, the group membership will be missing.
The process identity of IBM Cognos 8, when running as a local system account or a domain user,
must have one of these privileges:
●
impersonate a client after authentication
●
act as part of the operating system
If the privilege is missing, there is no group membership for the authenticated user.
To solve this problem, perform the following steps.
Steps
1. From the Start menu, click Settings, Control Panel.
2. Click Administrative Tools, and then double-click Local Security Policy.
3. In the console tree, click Security Settings, Local Policies.
4. Click User Rights Assignment.
5. Add the process identity of IBM Cognos 8 to one of the following policies:
Installation and Configuration Guide 215
Appendix A: Troubleshooting
●
Impersonate a client after authentication
The default is Administrators, Service.
For more information, see http://technet2.microsoft.com/WindowsServer/en/Library/
fe1fb475-4bc8-484b-9828-a096262b54ca1033.mspx
●
Act as part of the operating system
The default is Local system.
For more information, see http://technet2.microsoft.com/WindowsServer/en/Library/
ec4fd2bf-8f91-4122-8968-2213f96a95dc1033.mspx
Both of these privileges give an account the ability to act as another user.
The privilege Impersonate a client after authentication is similar to the Act as part of the
operating system privilege except that it will only allow a process to impersonate after
authentication, whereas the privilege Act as part of the operating system allows a process to
impersonate before authentication.
For more information, see http://www.microsoft.com/technet/prodtechnol/windowsserver2003/
technologies/security/tkerbdel.mspx
Deploying IBM Cognos 8 to an Oracle Application Server or
IBM WebSphere Application Server
You are deploying IBM Cognos 8 to an Oracle application server or an IBM WebSphere application
server and you receive the following errors:
●
Browser timeout in administration console
●
Error Message: HTTP 500 Internal Error
●
Error Message: Deployment failed: Base Exception: java.rmi.RemoteException (Oracle)
●
Return to application file selection page (IBM WebSphere)
This error can occur because the application file that you are trying to deploy is too large.
To solve this problem, on an Oracle application server, you can deploy the application file manually
using the following command:
dcmctl deployapplication -f <path and name of ear file> -a <application name> -co <OC4J instance
name>
For either IBM WebSphere or Oracle application servers, clear the Include static files from the
Webcontent folder option when you use the Build Application Wizard. Not including the static
content will reduce the size of the application file. If static content is required, you can manually
copy it to the deployed application location after you have successfully deployed IBM Cognos 8
into the application server. For more information about deploying IBM Cognos 8 to an application
server, see the Installation and Configuration Guide.
216
Appendix A: Troubleshooting
Errors Displayed Deploying to Oracle 10G Application Server
You are deploying IBM Cognos 8 to an Oracle 10G Application Server, and get the following error
messages:
CMM-APP-3254 The initialization of the metrics store failed. DIS-ERR-3115 Task execution failed.
MDS-RUN-3213 Unable to locate database bulk load utility. Please install the appropriate database
tool for this platform ('bcp' for SQL Server, 'sqlldr' for Oracle)
This occurs because the bulk loading utilities (SQL Loader on Oracle) are not included in the
deployment file created by IBM Cognos Configuration.
To resolve this error, you must use the Oracle client software on the computer where you installed
the Oracle 10G Application Server to install the missing components. Ensure that you install SQL
Loader.
CGI Timeout Error While Connected to IBM Cognos 8 Components Through a Web Browser
When performing operations through your Web browser, you receive the following error message:
CGI Timeout, process will be deleted from server.
The error occurs when you use Windows Internet Information Services (IIS) as your Web server
and the gateway is configured to use CGI. IIS has a default timeout for CGI applications.
To resolve this problem, you can configure the gateway to use ISAPI. IIS does not have a default
timeout for ISAPI applications. Or, if you want to keep using a CGI gateway, you can increase the
CGI timeout in IIS.
Steps to Change the Gateway to ISAPI
1. On the gateway computer, start IBM Cognos Configuration.
2. Under Environment, for the Gateway URI property, change the cognos.cgi portion of the URI
to
cognosisapi.dll
3. In your Web browser, specify the ISAPI URI:
http://computer_name/cognos8/isapi
Steps to Increase the CGI Timeout
1. In the Windows administrative tools, open Internet Information Services.
2. Under the local computer node, right-click Websites and select Properties.
3. In the Home Directory tab, click Configuration.
4. In the Process Options tab, increase the CGI script timeout.
Installation and Configuration Guide 217
Appendix A: Troubleshooting
Servlet Class Fails to Load in WebLogic
You may have problems when configuring a distributed server installation and using WebLogic as
the application server for IBM Cognos 8.
When deploying the p2pd.war for the Application Tier Components computer, you may receive
servlet exceptions and the dispatcher does not start. The cogserver.log is also not created.
The following error messages appear in the WebLogic Server console:
<Jul 9, 2004 3:47:37 PM EDT> <Error> <HTTP><BEA-101249> <[ServletContext
(id=19023494,name=p2pd,context-path=/p2pd)]:Servlet class com.cognos.pogo.isolation.ServletWrapper for servletcfgss could not be loaded because the requested class was not found
in the classpath /host2/bea812/user_projects/domains/c8/applications/p2pd/WEB-INF/classes.
java.lang.ClassNotFoundException: com.cognos.pogo.isolation.ServletWrapper.>
<Jul 9, 2004 3:47:37 PM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "cfgss" failed to preload
on startup in Web application: "p2pd".
javax.servlet.ServletException: [HTTP:101249][ServletContext(id=19023494,name=p2pd,contextpath=/p2pd)]: Servlet class com.cognos.pogo.isolation.ServletWrapperfor servlet cfgss could not be
loaded because the requested class was not found in the classpath /host2/bea812/user_projects/
domains/c8/applications/p2pd/WEB-INF/classes.java.lang.ClassNotFoundException:
com.cognos.pogo.isolation.ServletWrapper. at weblogic.servlet.internal.ServletStubImpl.prepareServlet (ServletStubImpl.java:799)
at weblogic.servlet.internal.WebAppServletContext.preload Servlet(WebAppServletContext.java:3252)
To avoid this problem, do not deploy the p2pd application from the WebLogic applications directory.
Create the p2pd directory in another location and deploy p2pd from there.
Steps
1. Open IBM Cognos Configuration and configure the Application Tier Components computer.
2. Restart the Content Manager computer.
3. Create a p2pd directory in a location that is accessible by the WebLogic server but is not in the
WebLogic applications directory.
For example, create a directory named p2pd in the following location:
WebLogic_location/user_projects/domain_name
4. Create the p2pd.war file.
5. In the p2pd directory, extract the p2pd.war file to the WebLogic installation using the following
command:
%JAVA_HOME%/bin/jar xvfm "c8_location/p2pd.war" .
6. Start WebLogic.
7. In the WebLogic Server Console, deploy the p2pd application.
218
Appendix A: Troubleshooting
Desktop Icons or IBM Cognos Configuration Window Flicker
on Windows
When you run IBM Cognos Configuration on Windows, you may notice that the desktop icons or
the IBM Cognos Configuration window flickers.
To resolve this issue, start IBM Cognos Configuration using the -noddraw command line option.
Installation and Configuration Guide 219
Appendix A: Troubleshooting
220
Index
A
Active Directory Server
advanced properties, 154
authenticating in multiple domains, 154
enabling single signon, 155
enabling SSL, 154
missing group membership, 215
using for authentication, 151
with an LDAP namespace, 165
Adaptive Analytics
copy image files, 95, 103
IBM Cognos 8 Analytic Applications components, 19
installing, 51
testing installation and configuration, 94, 101
uninstalling on Windows, 67
Adaptive Warehouse
IBM Cognos 8 Analytic Applications components, 19
installing, 51
testing installation and configuration, 94, 101
uninstalling on Windows, 67
Adaptive Warehouse Runtime
IBM Cognos 8 Analytic Applications components, 19
installing, 51
uninstalling on UNIX, 66
adding
fonts, 139
additional fonts
installing, 55
AIX
error connecting to DB2 database, 203
aliases
configuring on Apache Web Server, 142
configuring on Web servers, 81
anonymous logon
disabling, 150
Apache gateways
configuring, 142
Apache Web Server
configuring aliases, 81
Apache Web servers
configuring as gateways, 142
application content files
installing, 54
application servers
servlet class fails to load in WebLogic, 218
servlet gateways, 144
startup script fails, 207
Application Tier Components
log server, 123
audit
logs, 123
audit logs
log destinations, 123
See Also log messages
See Also troubleshooting
authentication
Active Directory Server, 151
configuring IBM Cognos Series 7 namespace, 157
custom authentication providers, 161
custom properties for Active Directory Server, 153
custom user properties for LDAP, 174
deleting namespaces, 185
disabling anonymous logon, 150
domain trees for Active Directory Server, 154
eTrust Siteminder, 177, 179, 180
LDAP, 163, 164
LDAP using Active Directory Server, 165
LDAP using IBM Directory Server, 168
LDAP using Novell Directory Server, 170
LDAP using Sun Java System Directory Server, 172
NTLM, 181
requirements for single signon with Microsoft Analysis Server or Microsoft SQL Server, 152
SaferAPIGetTrustedSignon function, 159
SAP, 182
single signon for NTLM, 182
single signon using Active Directory Server, 155
single signon using eTrust SiteMinder, 180
Installation and Configuration Guide 221
Index
single signon using IBM Cognos Series 7
namespace, 158
single signon using LDAP, 176
single signon using SAP, 185
SSL for eTrust Siteminder, 180
SSL using LDAP, 175
testing namespaces, 185
trusted signon plug-ins for IBM Cognos Series 7, 159
using namespaces, 149
B
backslashes appear instead of currency, 56
basic installations
single location, 45
Bind user DN and password property
special characters for LDAP namespace, 163
C
CAM-CRP-1157 error, 198
CGI timeout error, 217
changing
configuration settings, 103
URI, 103
characters
encoding not supported, 199
chase_referral files, 154
cipher suites
configuring for SSL connections, 122
code pages for data sources, 84
Cognos Content Database
changing users and passwords, 106
component description, 18
content store, 70
creating another instance, 105
Cognos namespace
recreating, 212
Cognos Viewer
component description, 18
cogstartup.lock file, 194
cogstartup.xml file
invalid file, 213
collation sequence, 70
collation sequences
case-sensitive, 199
common symmetric keys, 108
222
components, 19
Cognos Content Database, 18
Cognos Viewer, 18
Content Manager, 18, 25, 46
content store, 19
data sources, 19
ERP system, 19
gateway, 46
gateways, 18
IBM Cognos 8 runtime, 17
IBM Cognos Configuration, 18
IBM Cognos Connection, 18
installing on multiple computers, 22
installing on one computer, 22
Report Studio, 18
used by IBM Cognos 8 Analytic Applications, 17
confidentiality algorithm, 109
configuration
automating, 187
Content Manager, 25
copy image files for Adaptive Analytics, 95, 103
cryptographic information cannot be encrypted, 210
customizing during upgrade, 37
data locked, 212
error when encrypting information, 210
lock file, 194
requirements for single signon with Microsoft Analysis Server or Microsoft SQL Server, 152
settings for IBM Cognos 8 Analytic Applications, 62
settings not applied, 213
testing, 93, 100
unable to open IBM Cognos Configuration, 194
unable to save, 212
unattended, 187, 190
configuration files
exporting, 190
configuration issues, 209
configuration settings
changing, 103
saving, 92, 100
configuratios
upgrade considerations, 34
configuring
Active Directory namespace, 152
custom authentication providers, 161
destination for log messages, 123
Index
distributed installations, 95
email encoding, 138
eTrust SiteMinder namespace, 179
fonts, 139
gateways, 141
global settings, 132
IBM Cognos 8 Analytic Applications, 87
JDBC drivers, 77
LDAP namespace, 164
LDAP namespace for Active Directory Server, 165
LDAP namespace for IBM Directory Server, 168
multiple computers in a script-based environment, 23
multiple computers in a user-interface environment, 23
notification databases, 117
NTLM namespace, 181
SAP namespace, 184
shared trust, 121
single computer installations, 88
SSL protocols, 118
temporary files location, 111
time zones, 138
transfer specification files (.ats), 187
unattended, 190
Web browser, 82
Web server, 81
connection management
for the content store, 89, 96
console mode
for installing on UNIX and Linux, 14
content locales
configuring, 134
mapping to user locales, 135
Content Manager
an attempt to register the dispatcher, 204
component, 18, 25
configuration, 25
failover protection, 25
installation options, 25
installing, 46
log server, 123
requirements if using IBM Cognos 8 Transformer
with Series 7 namespace, 157
setting up a content store, 69
standby, 25
content store
compatible versions of DB2 and Java, 198
component, 19
creating, 41, 69
creating another instance of Cognos Content Database, 105
creating on Oracle, 73
database connections, 89, 96
DB2 JDBC drivers, 12, 80
deleting tables from the database, 209
invalid settings, 199
new default in version 8.4, 13
setting up database clients, 77
setting up JDBC drivers, 77
support for DB2 on z/OS for version 8.4, 12
upgrading, 203
context attribute cannot be deserialized, 208
context error, 208
cookies
enabling in Web browser, 82
settings, 139
creating
content store, 41
DB2 database, 85
credentials
changing for Cognos Content Database, 106
cross-script checking
configuring in IBM Cognos Application Firewall, 110
cryptographic error, 213
cogstartup.xml file invalid, 213
JRE error, 213
problems after upgrading, 211
cryptographic information cannot be encrypted, 210
currency
configuring, 134
fonts required for Yen or Won character, 55
won, 56
yen, 56
custom authentication providers, 161
custom user properties
Active Directory Server, 153
LDAP, 174
Installation and Configuration Guide 223
Index
D
data
locked by IBM Cognos Configuration, 212
database client
setting up for a content store, 77
setting up for a logging database, 125
database connections
content store, 89, 96
database connections for content store
setting, 89, 96
database connection strings for content store
IBM DB2, 89, 96
Microsoft SQL Server, 89, 96
Oracle, 89, 96
database connectivity
content store, 44
databases
bulk load utility missing, 217
content store, 69
deleting tables, 209
logging, 128
logging database client, 125
Data files location
configuring for Windows Vista, 111
Data Manager logging options
setting, 122
data sources, 19
data warehouse, 95
create a DB2 database, 85
DB2
code pages, 84
create a database, 85
environment variables for scripts on UNIX, 79
JDBC drivers, 12, 80
supported Java versions, 198
DB2 databases
setting up JDBC drivers, 77
db2java.zip
deprecated in version 8.4, 14
default configuration settings
Tomcat, 62
demonstration environments, 88
deploying
failure on Oracle or WebSphere Application
Server, 207
IBM Cognos 8, 216
224
Deployment files location
configuring for Windows Vista, 111
diagnostics, See troubleshooting
directory not found error, 204
dispatcher
does not start on Application Tier Components
computer, 218
distributed installations
configuring, 95
IBM Cognos 8 runtime components, 23
scenarios, 21
documentation
translated files, 13
domains
Active Directory Server domain trees, 154
DPR-DPR-1035 error, 198
E
email messages
encoding, 138
encryption
configuration errors, 210
environments
supported, 43
supported operating systems, 43
environment variables
content store, 69
requirements on Windows Vista, 111
setting up for scripts, 78
ERP system
component, 19
error messages
CAM-CRP-1064, 202
CFG-ERR-0106 Cognos Configuration received no
response, 196
CGI timeout, 217
CM-CFG-029 Content Manager is unable to
determine, 214
CMM-APP-3254 The initialization of the metrics
store failed, 217
corrupt cryptographic information, 213
could not deserialize context attribute, 208
cryptographic information cannot be encrypted, 210
DIS-ERR-3115 Task execution failed, 217
DPR-ERR-2022 No response generated, 206
DPR-ERR-2058, 204
Index
HTTP Error 404, 204
Java Runtime Environment, 213
malformed request, 208
MDS-RUN-3213 Unable to locate database bulk
load utility, 217
page not found, 204
PRS-CSE-1255, 202
servlet class fails to load on WebLogic, 218
SoapSocketException, 204
SQL1224N, 203
you have chosen to download a file, 207
eTrust SiteMinder
configuring namespaces, 179
enabling single signon, 180
protecting the IBM Cognos 8 Web alias, 180
SSL, 180
using for authentication, 177
event logs, 128
exporting
configuration files, 190
external identity mapping property
editing for an LDAP namespace, 177
External identity mapping property
special characters for LDAP namespace, 163
F
failover protection, 25
file location
properties, 91
file locations
requirements on Windows Vista, 111
files
not found, 204
flicker, 219
fonts
configuring, 139
not found when starting IBM Cognos Configuration
on UNIX, 215
G
gateway
configuring, 141
configuring to use a namespace, 114
installing, 46
log file, 194
recommended settings for Microsoft IIS, 217
servlets gateways, 144
when to use ISAPI, 217
gateways
component description, 18
groups
missing membership in Active Directory Server, 215
H
HTML cookies, See cookies
HTTP Error 404, 204
I
IBM Cognos 8
service does not start, 198
service pack, 49
updater, 49
IBM Cognos 8 Adaptive Applications Framework
installing, 51
uninstalling on UNIX, 66
uninstalling on Windows, 67
IBM Cognos 8 Analytic Applications
components, 17
configuring, 87
default settings, 41
upgrading, 27
IBM Cognos 8 Analytic Applications components
Adaptive Analytics, 19
Adaptive Warehouse, 19
Adaptive Warehouse Runtime, 19
IBM Cognos 8 Runtime
setting dispatcher location, 99
setting gateway location, 99
IBM Cognos 8 runtime components, 17
installation options, 23
installing, 46
uninstalling on UNIX, 63
uninstalling on Windows, 64
IBM Cognos 8 server
fails to start, 198
IBM Cognos 8 service
configuring, 115
server not available, 199
starting, 213
IBM Cognos Application Firewall
configuring, 110
Installation and Configuration Guide 225
Index
IBM Cognos Configuration
component description, 18
font not found error on UNIX, 215
invalid settings, 199
problems opening, 194
problems saving a configuration, 209
problems with keyboard navigation, 212
starting, 87
trouble generating cryptographic keys after
install, 211
unable to start, 212
unattended mode, 190
IBM Cognos Connection
component, 18
unable to open, 204
IBM Cognos Content Database
uninstalling, 65
IBM Cognos Resource Center, 10
IBM Cognos Series 7
enabling single signon, 158
enabling SSL, 158
trusted signon plug-ins, 159
using for authentication, 157
IBM DB2
creating connection strings for content store, 89, 96
IBM Directory Server
with an LDAP namespace, 168
IIS Web servers
single signon using Active Directory, 155
installation
basic for single locations, 45
checklist, 41
testing, 93, 100
unattended, 187
installing
Adaptive Analytics, 51
Adaptive Warehouse, 51
Adaptive Warehouse Runtime, 51
additional fonts, 55
application content files, 54
Content Manager, 25
IBM Cognos 8, 187
IBM Cognos 8 Adaptive Applications Framework, 51
IBM Cognos 8 Analytic Applications, 41
IBM Cognos 8 runtime components, 46
226
SAP interface files, 57
Supplementary Languages Documentation, 48, 54
unattended install, 187
using transfer specification file (.ats), 187
using transfer specification files (.ats), 187
Integrated Windows Authentication
issues, 214
integrating
other components, 19
interface
configuring languages, 133
Internet Explorer
browser settings, 82
invalid cogstartup.xml file, 213
invalid settings
content store, 199
IBM Cognos Configuration, 199
IP address version, 145
iPlanet Web Server, See Sun Java System Web Server
IPv4, 145
IPv6, 145
ISAPI
when to use for a gateway, 217
J
Japanese currency, 56
Japanese Yen
font requirements, 55
jar file
error when starting configuration, 213
Java
supported versions for DB2 content store, 198
uses all of CPU, 198
JAVA_HOME
setting, 213
Java error when starting configuration, 213
Java Runtime Environment
IBM JRE replaces Sun Java Runtime Environment, 13
Java Runtime Environment (JRE), 80
Java scripts
enabling in Web browser, 82
JDBC
database connectivity for content store, 44
JDBC drivers, 12, 77, 80
db2java.zip deprecated in version 8.4, 14
Index
setting up DB2 databases, 77
setting up Oracle databases, 77, 126
K
keyboard
navigation problems, 212
Korean currency, 56
Korean Won
font requirements, 55
L
languages
configuring for user interfaces, 133
content locale, 134
new support in version 8.4, 11
user interface and message files, 14
language support, 13
LDAP
Active Direcetory Server, 165
configuring a namespace, 164
custom properties, 174
editing the External identity mapping property, 177
enabling single signon, 176
enabling SSL, 175
IBM Directory Server, 168
Novell Directory Server, 170
Sun Java System Directory Server, 172
using for authentication, 163
Linux
console-mode installation is deprecated, 14
log messages, 128
on System z, 12
load balancing
enabling and disabling services, 114
location
files, 91
log database
deleting tables, 209
log destinations
types of, 123
log files, 193
for gateway errors, 194
locale configuration, 194
run-time, 194
silent mode, 195
startup configuration, 193
transfer, 193
transfer summary, 193
uninstallation, 194
logging
configuring, 129
database, 128
database client, 125
remote log servers, 128
using files, 128
logging database
support for DB2 on z/OS for version 8.4, 12
logging databases
creating, 69
logging in
hiding namespaces during, 162, 181
log messages
enabling for IBM Cognos Application Firewall, 110
log destinations, 123
remote log server, 123
See Also audit logs
See Also troubleshooting
logs
message processing, 123
M
managing
connections for the content store, 89, 96
Map files location
configuring for Windows Vista, 111
memory
configuring, 115
metric store
failure, 217
Microsoft
security update affects memory, 198
Microsoft Analysis Server
namespace requirement, 152
Microsoft Analysis Services
single signon to MSAS data sources, 155
Microsoft IIS Web servers
recommended gateway settings, 217
Microsoft SQL Server
creating connection strings for content store, 89, 96
namespace requirement, 152
model
create a DB2 database, 85
Installation and Configuration Guide 227
Index
multi_domain_tree, 154
N
namespace
Active Directory Server missing group membership, 215
cannot log on, 202
recreating, 212
namespaces
authentication, 149
configuring custom authentication providers, 161
configuring for a gateway, 114
deleting, 185
hiding during login, 162, 181
requirements for Content Manager if using Transformer with Series 7 namespace, 157
testing, 185
Netegrity SiteMinder, See eTrust SiteMinder
network outage
services fail to start, 203
no response generated, 206
notification database
configuring, 117
creating, 116
deleting tables, 209
settings for DB2 on z/OS, 116
support for DB2 on z/OS for version 8.4, 12
tablespaces for DB2 on z/OS, 116
Novell Directory Server
with an LDAP namespace, 170
NTLM, 181
configuring, 181
enabling single signon, 182
NTLM, See Also Windows native security (NTLM)
Oracle Application Server
deploying IBM Cognos 8, 216
IBM Cognos 8 deployment failure, 207
P
p2pd.war file for WebLogic, 208
page not found error
starting IBM Cognos 8 in Windows 2003, 204
passwords
changing for Cognos Content Database, 106
portal
errors in starting, 204, 206
portal problems
unable to open, 204
ports
changing, 103
default configuration settings, 62
ports already in use, 197
problems opening IBM Cognos Configuration, 194
processing log messages, 123
product
name changes, 13
production environment
upgrading, 33
product locales
mapping for user interfaces, 137
product versions, 49
proof of concept, 88
properties
file location, 91
temporary files location, 111
protocol
IP address, 145
Q
O
OLAP data sources
members missing or inaccessible, 215
Oracle
creating connections strings for content store, 89,
96
database JDBC drivers, 77, 126
deployment errors, 217
environment variables for scripts on UNIX, 78
multilingual support, 84
228
quick tours
using, 10
R
readme
reviewing before you install, 41
recreating the Cognos namespace, 212
relational data sources
members missing or inaccessible, 215
remote log servers, 128
configuring, 129
Index
reports
configuring languages, 134
Report Studio
component, 18
response.ats file, 187
reviewing the readme before you install, 41
S
SaferAPIGetTrustedSignon function
using for authentication, 159
SAP
enabling single signon, 185
transport files, 15
using for authentication, 182
SAP BW
authorization settings for IBM Cognos 8 administrators, 184
authorization settings for IBM Cognos 8 users, 182
connectivity, 184
SAP interface files
installing, 57
saving
configuration settings, 92, 100
screen flicker, 219
scripts
setting up environment variables, 78
to delete tables from databases, 209
secure LDAP communication, 175
Secure Sockets Layer, See SSL
security
issues with Integrated Windows Authentication, 214
services
enabling and disabling, 114
fail to start after network outage, 203
unable to start, 197
servlet gateway, 144
setting
database connections for content store, 89, 96
silent configuration, See unattended configuration
silent installations, See unattended installation
silent mode, See unattended mode
silent uninstallation, 191
single computer installation
configuring, 88
single server installations, 45
single signon
Active Directory namespace, 155
eTrust SiteMinder user directory, 180
issues with Integrated Windows Authentication, 214
LDAP namespace, 176
NTLM namespace, 182
SAP namespace, 185
using IBM Cognos Series 7 namespace, 158
special characters
in LDAP namespace properties, 163
SSL
Active Directory Server, 154
configuring protocols, 118
eTrust SiteMinder user directory, 180
LDAP namespace, 175
quality of protection, 122
setting up shared trust, 121
using IBM Cognos Series 7 namespace, 158
standby Content Manager, 25
starting
IBM Cognos Configuration, 87
startup
configuration lock file, 194
DB2 returns SQL1224N error when connecting from
AIX, 203
IBM Cognos 8 service, 213
page not found, 204
problems, 195
script fails, 207
unable to download cognos.xts, 207
unable to open IBM Cognos Connection, 204
unable to start service, 197
Startup
failure without error, 198
Sun Java Runtime Environment
replaced by IBM JRE, 13
Sun Java System Directory Server
with an LDAP namespace, 172
Sun Java System Web Server, 81
Sun ONE Web Server, See Sun Java System Web Server
Supplementary Languages Documentation
installing, 48, 54
new in version 8.4, 13
supported environments, 43
Sybase
database drivers, 45, 91
Installation and Configuration Guide 229
Index
syslog
destination for log messages, 128
system requirements
IBM Cognos 8 Analytic Applications, 41
System z
installing on Linux, 12
T
Tab key
problems in IBM Cognos Configuration, 212
tables
deleting from a database, 209
tablespaces
DB2 Notification Database on z/OS, 116
temporary directories
deleting before reinstall, 211
temporary files, 111
Temporary files location
configuring for Windows Vista, 111
testing
configuration, 93, 100
installation, 93, 100
time zones
changing, 138
Tomcat
default configuration settings, 62
transfer specification files (.ats)
configuration, 187
Transformer
requirements for Content Manager if using Series 7
namespace, 157
transport files
install location, 15
trial upgrades
moving to the production environment, 33
troubleshooting
logging, 123
U
unable to open IBM Cognos Configuration, 194
unattended configuration
setting up, 187
unattended installation, 191
setting up, 187
unattended mode, 187
230
uninstalling
Adaptive Analytics on Windows, 67
Adaptive Warehouse on Windows, 67
Adaptive Warehouse Runtime on UNIX, 66
IBM Cognos 8 Adaptive Applications Framework
on UNIX, 66
IBM Cognos 8 Adaptive Applications Framework
on Windows, 67
IBM Cognos 8 runtime components on UNIX, 63
IBM Cognos 8 runtime components on Windows, 64
IBM Cognos Content Database, 65
unattended, 191
UNIX
console-mode installation is deprecated, 14
font not found error, 215
log messages, 128
system requirements, 41
uninstalling Adaptive Warehouse Runtime, 66
uninstalling IBM Cognos 8 Adaptive Applications
Framework, 66
uninstalling IBM Cognos 8 runtime components, 63
unsupported characters, 199
updating
.jar files, 80
updating IBM Cognos 8, 49
upgrading
content store, 203
IBM Cognos 8 Analytic Applications, 27, 34, 37
problems with cryptographic keys, 211
production environment, 33
URI
changing, 103
default configuration settings, 62
user interfaces
mapping for product locales, 137
user locales
mapping to content locales, 135
User lookup property
special characters for LDAP namespace, 163
users
changing for Cognos Content Database, 106
V
virtual directories
setting up, 81
Index
W
Web aliases
setting up, 81
Web browsers
configuring, 82
errors in starting the Web portal, 206
errors when starting the web portal, 204
WebLogic
could not deserialize context attribute, 208
deploying p2pd.war file, 208
servlet class fails to load, 218
startup script fails, 207
Web servers
configuring, 81
servlet gateways, 144
single signon using Active Directory and IIS Web
server, 155
WebSphere Application Server
deploying IBM Cognos 8, 216
IBM Cognos 8 deployment failure, 207
startup script fails, 207
Windows
system requirements, 41
uninstalling Adaptive Analytics, 67
uninstalling Adaptive Warehouse, 67
uninstalling IBM Cognos 8 Adaptive Applications
Framework, 67
uninstalling IBM Cognos 8 runtime components, 64
Windows event log
destination for log messages, 128
Windows IIS
recommended gateway settings, 217
Windows integrated authentication, 155
Windows native security (NTLM)
enabling single signon, 182
using for authentication, 181
Windows Vista
requirements for file locations, 111
won character, 56
Won character
font requirements, 55
Y
yen character, 56
Yen character
font requirements, 55
Installation and Configuration Guide 231
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising