IBM Cognos Business Intelligence Version 10.2.

1

Installation and Configuration Guide

Note Before using this information and the product it supports, read the information in “Notices” on page 509.

Product Information
This document applies to IBM Cognos Business Intelligence Version 10.2.1 and may also apply to subsequent releases. Licensed Materials - Property of IBM © Copyright IBM Corporation 2005, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1. What's new? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New features in version 10.2.1 . . . . . . . . . . . . . . . . . . . New security standards in IBM Cognos BI . . . . . . . . . . . . . . 64-bit IBM Cognos gateway as default in 64-bit installations . . . . . . . . External object store for archiving of reports . . . . . . . . . . . . . . New features in version 10.2.0 . . . . . . . . . . . . . . . . . . . 64-bit IBM Cognos gateway . . . . . . . . . . . . . . . . . . . Configuration of multi-tenant applications in IBM Cognos Configuration . . . . Predefined LDAP configurations. . . . . . . . . . . . . . . . . . Option to view the status of silent installations on the screen . . . . . . . . Option to initialize Cognos Configuration from a different file . . . . . . . . New features in version 10.1.1 . . . . . . . . . . . . . . . . . . . 64-bit Report Server . . . . . . . . . . . . . . . . . . . . . . IBM Cognos Content Archival . . . . . . . . . . . . . . . . . . Script to generate an IBM DB2 content store database . . . . . . . . . . Install IBM Cognos to IBM WebSphere from the Build Application Wizard . . . New features in version 10.1.0 . . . . . . . . . . . . . . . . . . . Dynamic Query Mode . . . . . . . . . . . . . . . . . . . . . Collaboration Using IBM Cognos Workspace . . . . . . . . . . . . . Access to Software Development Kit Installation and Configuration Guide . . . Changed Features in Version 10.1.0 . . . . . . . . . . . . . . . . . . Default Installation Location and Web Alias . . . . . . . . . . . . . . Upgrade Manager is Renamed as Lifecycle Manager . . . . . . . . . . . Index Search Capabilities are Native to IBM Cognos BI Server . . . . . . . . IBM Cognos Go! Dashboard is Merged with Features from IBM Cognos Viewer into IBM Cognos Special Edition is Integrated with the IBM Cognos BI Server Products. Enhanced Support for Authentication Using a RACF Provider . . . . . . . . Support for Informix Dynamic Server Database. . . . . . . . . . . . . IBM Cognos Portal Services . . . . . . . . . . . . . . . . . . . Secure Access When Monitoring System Metrics Externally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 1 2 2 2 2 2 3 3 3 3 4 4 4 4 5 5 6 6 6 6 6 7 7 7 7 8

Chapter 2. Distribution options . . . . . . . . . . . . . . . . . . . . . . . . . . 9
IBM Cognos family . . . . . . . . . . . . . . . . . . . . . Cognos enterprise product components . . . . . . . . . . . . . . Server components . . . . . . . . . . . . . . . . . . . . Optional server components . . . . . . . . . . . . . . . . . Modeling components . . . . . . . . . . . . . . . . . . . Required database components . . . . . . . . . . . . . . . . Infrastructure components . . . . . . . . . . . . . . . . . Distributing components . . . . . . . . . . . . . . . . . . . All server components on one computer. . . . . . . . . . . . . Gateways on separate computers . . . . . . . . . . . . . . . Application Tier Components and Content Managers on separate computers IBM Cognos BI products on the same computer . . . . . . . . . . Consolidate servers for Linux on System z . . . . . . . . . . . . Installing 64-bit versions of IBM Cognos BI products . . . . . . . . Installation options for Windows modeling components . . . . . . . . Firewall considerations . . . . . . . . . . . . . . . . . . Distributing Framework Manager components . . . . . . . . . . Distributing Transformer components . . . . . . . . . . . . . Distributing Metric Designer components . . . . . . . . . . . . Distributing IBM Cognos BI scorecarding components . . . . . . . . . IBM Cognos Business Intelligence with other IBM Cognos products . . . .
© Copyright IBM Corp. 2005, 2013

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. 9 10 10 13 13 14 15 16 17 18 19 21 21 22 24 24 26 26 28 29 30

iii

IBM IBM IBM IBM

Cognos Cognos Cognos Cognos

products that can be upgraded to IBM Cognos Business Intelligence . . . Series 7 products that can be migrated to IBM Cognos Business Intelligence products that interoperate with IBM Cognos Business Intelligence. . . . Series 7 content that can be recreated in IBM Cognos Business Intelligence .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

31 32 33 36

Chapter 3. Preparing to install. . . . . . . . . . . . . . . . . . . . . . . . . . 39
Review the Release Notes Before You Install . . . . . . . . . . . . . . . . . . . Review supported environments . . . . . . . . . . . . . . . . . . . . . . . Verify system requirements . . . . . . . . . . . . . . . . . . . . . . . . . Memory settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . Java requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review the Default Port Settings for IBM Cognos Business Intelligence . . . . . . . . . . Guidelines for creating the content store . . . . . . . . . . . . . . . . . . . . . Suggested settings for creating the content store in DB2 on Linux, Windows, and UNIX operating Suggested settings for creating the content store in DB2 on z/OS . . . . . . . . . . . Suggested settings for creating the content store in Oracle . . . . . . . . . . . . . . Suggested settings for creating the content store in Microsoft SQL Server . . . . . . . . . Suggested settings for creating the content store in IBM Informix Dynamic Server . . . . . . Suggested settings for creating the content store in Sybase. . . . . . . . . . . . . . Configure a User Account or Network Service Account for IBM Cognos Business Intelligence . . . Setting up environment variables on UNIX for the metric store . . . . . . . . . . . . . Configure Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 39 40 42 43 44 45 46 48 49 50 50 51 52 53 54

Chapter 4. Upgrade IBM Cognos Business Intelligence . . . . . . . . . . . . . . . 59
Upgrade process. . . . . . . . . . . . . . . . . . Reviewing the documentation . . . . . . . . . . . . Assess applications in your environment before you upgrade. . Access content from a previous version in the portal . . . . Upgrade tasks . . . . . . . . . . . . . . . . . . Install and configure a new version of the product . . . . . Move your content to the new version of the product . . . . Upgrade your report specifications . . . . . . . . . . Use Lifecycle Manager to compare reports between your versions . . . . . . . . of . . . . . . . . the . . . . . . . . . . . . . . . . . . . . . . . . product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 60 61 62 63 63 66 70 71

Chapter 5. Installing and Configuring Product Components on One Computer . . . . . 73
Install Server Components in Interactive Mode . . . . . . . . . . . . . . Install the server components . . . . . . . . . . . . . . . . . . . . Installing server components on UNIX or Linux operating systems . . . . . . . Installing server components on Windows operating systems . . . . . . . . . Install IBM Cognos Metrics Manager . . . . . . . . . . . . . . . . . . Installing fix packs . . . . . . . . . . . . . . . . . . . . . . . . Installing IBM Cognos fix packs on UNIX or Linux operating systems. . . . . . Installing Fix Packs on Windows operating systems . . . . . . . . . . . . Set up database connectivity for the content store database . . . . . . . . . . Set up database connectivity for an IBM DB2 content store . . . . . . . . . Set up database connectivity for an Oracle content store . . . . . . . . . . Set up database connectivity for an Informix content store. . . . . . . . . . Set up database connectivity for a Sybase content store . . . . . . . . . . . Set up database connectivity for reporting databases . . . . . . . . . . . . Access OLAP data sources on Windows operating systems . . . . . . . . . Access ODBC data sources on UNIX or Linux operating systems . . . . . . . Configure IBM Cognos Business Intelligence to use Oracle Essbase . . . . . . . Configuring Oracle Essbase on a UNIX or 64-bit Microsoft Windows operating system Start IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . Configure Environment Properties in IBM Cognos Configuration . . . . . . . . Enable the 64-bit version of report server . . . . . . . . . . . . . . . . Enable Security . . . . . . . . . . . . . . . . . . . . . . . . . Set Database Connection Properties for the Content Store . . . . . . . . . . . Setting database connection properties for a DB2 content store . . . . . . . . Setting database connection properties for a Microsoft SQL Server, Oracle, Informix, or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sybase content store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 74 75 77 78 79 79 80 80 80 85 85 86 86 87 87 89 89 90 90 91 91 92 92 93

iv

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Specify a Connection to a Mail Server Account . . . . . . . . Start the IBM Cognos services . . . . . . . . . . . . . . Configuring the web server . . . . . . . . . . . . . . . Enable the 32-bit web gateway for a 64-bit installation . . . . . Use compiled gateways for production systems . . . . . . . Use CGI gateways. . . . . . . . . . . . . . . . . Configuring WebDAV to view and browse images . . . . . . Test the Installation and Configuration . . . . . . . . . . . Set variables for data source connections . . . . . . . . . . Creating a metric store database . . . . . . . . . . . . . Create a metric store database in IBM DB2 . . . . . . . . Create a metric store database in Microsoft SQL Server . . . . Create an metric store database in Oracle . . . . . . . . . Create a metric store database in Oracle using an existing database Setting up the database client for the Metric Store . . . . . . . Set up the database client for an IBM DB2 metric store . . . . Set up the database client for an Oracle metric store . . . . . Set up the database client for a Microsoft SQL Server metric store . Create a metric package . . . . . . . . . . . . . . . .

. 95 . 96 . 96 . 97 . 97 . . . . . . . . . . . . . . . 102 . . . . . . . . . . . . . . . 105 . . . . . . . . . . . . . . . 108 . . . . . . . . . . . . . . . 108 . . . . . . . . . . . . . . . 110 . . . . . . . . . . . . . . . 111 . . . . . . . . . . . . . . . 111 . . . . . . . . . . . . . . . 112 . . . . . . . . . . . . . . . 113 . . . . . . . . . . . . . . . 114 . . . . . . . . . . . . . . . 114 . . . . . . . . . . . . . . . 114 . . . . . . . . . . . . . . . 115 . . . . . . . . . . . . . . . 115

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

Chapter 6. Installing and Configuring Server Components on Different Computers . . 119
Installation sequence for server components . . . . . . . . . . . . . . . . Recommendation - Install and Configure the Basic Installation for Distributed Installations Install Server Components in Interactive Mode . . . . . . . . . . . . . . . Installing and Configuring Content Manager . . . . . . . . . . . . . . . . Active and Standby Content Manager Components. . . . . . . . . . . . . Install the Content Manager components . . . . . . . . . . . . . . . . Install Content Manager for IBM Cognos Metrics Manager . . . . . . . . . . Installing fix packs . . . . . . . . . . . . . . . . . . . . . . . Set up database connectivity for the content store database . . . . . . . . . . Start IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . Set Database Connection Properties for the Content Store . . . . . . . . . . Configure Environment Properties for Content Manager Computers . . . . . . . Specify a Connection to a Mail Server Account . . . . . . . . . . . . . . Enable Security . . . . . . . . . . . . . . . . . . . . . . . . . Start Content Manager . . . . . . . . . . . . . . . . . . . . . . Test the Content Manager Installation . . . . . . . . . . . . . . . . . Installing and Configuring Application Tier Components . . . . . . . . . . . . Install the Application Tier Components . . . . . . . . . . . . . . . . Install Application Tier Components for IBM Cognos Metrics Manager . . . . . . Installing fix packs . . . . . . . . . . . . . . . . . . . . . . . Set up database connectivity for reporting databases . . . . . . . . . . . . Start IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . Configure Environment Properties for Application Tier Components Computers . . . Enable the 64-bit version of report server . . . . . . . . . . . . . . . . Start the Application Tier Components . . . . . . . . . . . . . . . . . Test the Application Tier Components . . . . . . . . . . . . . . . . . Creating a metric store database . . . . . . . . . . . . . . . . . . . Manually define the deployment location for Metric Studio . . . . . . . . . . Setting up the database client for the Metric Store . . . . . . . . . . . . . Create a metric package . . . . . . . . . . . . . . . . . . . . . . Installing and Configuring the Gateway . . . . . . . . . . . . . . . . . Installing the gateway components on UNIX or Linux operating systems . . . . . Installing the gateway components on Windows operating systems . . . . . . . Install the Gateway for IBM Cognos Metrics Manager . . . . . . . . . . . . Installing fix packs . . . . . . . . . . . . . . . . . . . . . . . Start IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . Configure Environment and Security Properties for Gateway Computers . . . . . Configuring the web server . . . . . . . . . . . . . . . . . . . . Test the Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 122 123 123 125 125 128 129 130 136 137 140 142 143 143 144 144 144 148 148 149 153 154 156 156 157 157 161 162 163 165 166 167 168 169 170 171 172 184

Contents

v

Chapter 7. Install and Configure Modeling Tools for Reporting and Scorecarding . . . 185
Installing and Configuring IBM Cognos Framework Manager . . . Default Settings for Framework Manager . . . . . . . . . Installing Framework Manager . . . . . . . . . . . . Set variables for data source connections for Framework Manager. Environment Properties for Framework Manager Computers . . Test the Framework manager installation . . . . . . . . . Installing and Configuring Metric Designer . . . . . . . . . Default Settings for Metric Designer . . . . . . . . . . . Install Metric Designer . . . . . . . . . . . . . . . Setting up the database client for the Metric Store . . . . . . Configuring Metric Designer . . . . . . . . . . . . . Set variables for your import sources for Metric Designer . . . Test the Metric Designer installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 186 186 187 189 192 192 193 193 194 195 196 198

Chapter 8. Install and configure optional components . . . . . . . . . . . . . . . 199
IBM Cognos Transformer . . . . . . . . . . . . . . . . . . . . Install IBM Cognos Transformer . . . . . . . . . . . . . . . . . Default Settings for IBM Cognos Transformer . . . . . . . . . . . . Communication between Transformer and Business Intelligence components . . Data Sources and Transformer . . . . . . . . . . . . . . . . . . Test your Transformer installation . . . . . . . . . . . . . . . . Additional configuration tasks for IBM Cognos Transformer. . . . . . . . Installing translated product documentation . . . . . . . . . . . . . . Installing additional language fonts . . . . . . . . . . . . . . . . . Configure support for Japanese Yen and Korean Won characters . . . . . . IBM Cognos BI for Microsoft Office . . . . . . . . . . . . . . . . . Copy IBM Cognos BI for Microsoft Office Client Files to a Central LAN Location Enable SSL Support for the HTTPS Interface to PowerPlay . . . . . . . . Enable Anonymous Access for PowerPlay . . . . . . . . . . . . . . Deploying IBM Cognos for Microsoft Office Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 200 203 203 205 207 207 212 213 214 215 215 215 216 216

Chapter 9. Configuration options . . . . . . . . . . . . . . . . . . . . . . . . 219
Changing the version of Java used by IBM Cognos BI components . . . Back up existing IBM Cognos information . . . . . . . . . . . Change your Java version . . . . . . . . . . . . . . . . Changing Default Configuration Settings . . . . . . . . . . . . Change Default User and Password for Cognos Content Database. . . Port and URI Settings . . . . . . . . . . . . . . . . . Configuring Cryptographic Settings . . . . . . . . . . . . . IBM Cognos Application Firewall . . . . . . . . . . . . . Encrypt Temporary File Properties . . . . . . . . . . . . . Configure the Gateway to Use a Namespace . . . . . . . . . . Enable and Disable Services . . . . . . . . . . . . . . . Configuring fonts . . . . . . . . . . . . . . . . . . . Change the default font for PDF reports . . . . . . . . . . . Configure Embedded Fonts for PDF Reports . . . . . . . . . . Saved Report Output . . . . . . . . . . . . . . . . . . Changing the Location of Temporary Report Output . . . . . . . Change the Location of Map Charts for Report Studio. . . . . . . Use an external object store for report output. . . . . . . . . . . Verify access to the external object store . . . . . . . . . . . Configuring multitenancy settings . . . . . . . . . . . . . . Identify tenancy information . . . . . . . . . . . . . . . Enabling multitenancy . . . . . . . . . . . . . . . . . Disabling multitenancy . . . . . . . . . . . . . . . . . Customizing Server-side Printing for UNIX and Linux Platforms . . . . Change the notification database . . . . . . . . . . . . . . . Suggested settings for creating a notification database on DB2 on z/OS . Creating tablespaces for a notification database on DB2 for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 220 221 222 222 224 226 230 232 233 233 234 236 237 238 239 240 240 241 242 242 244 245 246 247 247 248

vi

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Change the Connection Properties for the Notification Database . . . . . . . . . . Create a New Content Store Using Cognos Content Database . . . . . . . . . . . . Change the security standard compliance for IBM Cognos trust stores . . . . . . . . . Restore non-NIST SP800-131a standard certificates to IBM Cognos trust stores. . . . . . Remove non-NIST SP800-131a standard certificates from the IBM Cognos trust stores . . . Configuring IBM Cognos components to use another certificate authority . . . . . . . . Create certificate signing request (CSR) files . . . . . . . . . . . . . . . . . Import the CA certificates into IBM Cognos components . . . . . . . . . . . . . Configure IBM Cognos BI Components to use certificates generated by your CA . . . . . Configuring the SSL protocol for IBM Cognos components . . . . . . . . . . . . . Configure SSL for IBM Cognos components . . . . . . . . . . . . . . . . . Set up shared trust between IBM Cognos servers and other servers . . . . . . . . . Select and rank cipher suites for Secure Socket Layer . . . . . . . . . . . . . . Configure IBM Cognos for SSL enabled Web servers . . . . . . . . . . . . . . . Configuring a Repository for Log Messages . . . . . . . . . . . . . . . . . . Guidelines for creating a logging database. . . . . . . . . . . . . . . . . . Database connectivity for the logging database . . . . . . . . . . . . . . . . Log message repositories . . . . . . . . . . . . . . . . . . . . . . . Enabling User-specific Logging . . . . . . . . . . . . . . . . . . . . . Changing Global Settings . . . . . . . . . . . . . . . . . . . . . . . . Customize Language Support to the User Interface . . . . . . . . . . . . . . . Customizing Currency Support . . . . . . . . . . . . . . . . . . . . . Customize content locale support . . . . . . . . . . . . . . . . . . . . Content Locales . . . . . . . . . . . . . . . . . . . . . . . . . . Map Product Locales . . . . . . . . . . . . . . . . . . . . . . . . . Customize the Server Time Zone . . . . . . . . . . . . . . . . . . . . . Encoding for Email Messages . . . . . . . . . . . . . . . . . . . . . . Cookie Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . Change the IP Address Version . . . . . . . . . . . . . . . . . . . . . . Setting the IP version. . . . . . . . . . . . . . . . . . . . . . . . . Manually configuring IBM Cognos Configuration to start with the IPv6 option . . . . . Configuring IBM Cognos Configuration to always start with the IPv6 option on Windows . Configuring IBM Cognos Index Search . . . . . . . . . . . . . . . . . . . . Upgrading from a Previous Version of Index Search . . . . . . . . . . . . . . Enabling and Disabling Index Services in a Distributed Installation . . . . . . . . . Scaling Index Search by Using Index Sharing . . . . . . . . . . . . . . . . . Adding IBM OmniFind Enterprise Edition Search Functionality to IBM Cognos Applications . Configuring the Collaboration Discovery URI . . . . . . . . . . . . . . . . . Configuring IBM Cognos Workspace . . . . . . . . . . . . . . . . . . . . Configuring access to IBM Cognos Workspace or its functions . . . . . . . . . . . Configuring Supported MIME Types in Microsoft Internet Information Services . . . . . Creating tablespaces for the human task and annotation database on DB2 on z/OS . . . . Setting up a database for Human Tasks and Annotations . . . . . . . . . . . . . Metric objects in IBM Cognos Workspace . . . . . . . . . . . . . . . . . . Configuring IBM Cognos Workspace to use IBM Cognos TM1 data . . . . . . . . . Configuring IBM Cognos Workspace to access IBM Cognos TM1 Applications. . . . . . Changing the style of report objects in IBM Cognos Workspace. . . . . . . . . . . Accessing the IBM Cognos Workspace samples . . . . . . . . . . . . . . . . Configure the Router to Test Dispatcher Availability . . . . . . . . . . . . . . . Configuring IBM Cognos BI to Work with Other IBM Cognos Products . . . . . . . . . Enable Scheduled Reports and Agents for IBM Cognos Planning Contributor Data Sources . File Location Properties on Windows Vista . . . . . . . . . . . . . . . . . . Update File Location Properties on Windows Vista . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

249 249 250 250 251 252 253 255 256 257 257 259 260 260 261 262 264 265 271 272 272 273 274 275 276 277 278 279 280 280 280 281 281 282 282 283 284 284 285 285 286 287 288 289 291 294 294 295 295 295 296 296 297

Chapter 10. Configuring Portal Services . . . . . . . . . . . . . . . . . . . . . 299
Specify the Location of the Applications.xml File . . . . . . . Configuring Security for Portal Services . . . . . . . . . . Disable Anonymous Access to IBM Cognos Components . . . . Enable Single Signon Using Shared Secret . . . . . . . . . Enable single signon with Sharepoint using Kerberos authentication Enable Single Signon for SAP EP with the SAP Logon Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 300 300 301 306 309

Contents

vii

Enable Enable Enable Enable Enable

Single Signon for SAP EP with User Mapping . . . . . . . . . . . . . Secure Communication Between SAP EP and IBM Cognos Components . . . . Single Signon for WebSphere Portal Using the Application Server . . . . . . Single Signon for Oracle WebCenter Interaction Portal Using Basic Authentication . Single Signon for Oracle WebCenter Interaction Portal Using CA SiteMinder. . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

309 311 311 311 312

Chapter 11. IBM Cognos content archival . . . . . . . . . . . . . . . . . . . . 313
Configure content archival . . . . . . . . . . . Creating a file location for a file system repository . . Importing custom classes definitions and properties into Importing custom classes definitions and properties into Specifying an available time to run the archival process Specifying thread execution time . . . . . . . . Archiving selected formats of report outputs . . . . Removal of marked version objects from the queue . Specifying that report specifications are not archived . . . . . IBM IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FileNet Content Manager . Content Manager 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 315 315 316 317 318 319 319 319

Chapter 12. Using Collaboration with IBM Cognos Workspace . . . . . . . . . . . 321
Installation considerations . . . . . . . . . . . . . . . . . . . . . . Installation process . . . . . . . . . . . . . . . . . . . . . . . . Mandatory updates required for IBM Connections . . . . . . . . . . . . . Allow access to IBM Connections from IBM Cognos BI . . . . . . . . . . . Enable IBM Connections to accept activities created by IBM Cognos Workspace . . . Enable single signon between IBM Connections and IBM Cognos Business Intelligence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 322 325 326 327 328

Chapter 13. Configuring IBM Cognos Components to Use an Authentication Provider
Disable Anonymous Access. . . . . . . . . . . . . . . . . . . . . . . Restrict User Access to the Cognos Namespace . . . . . . . . . . . . . . . . Configuring IBM Cognos Components to Use Active Directory Server . . . . . . . . Configure an Active Directory Namespace. . . . . . . . . . . . . . . . . Make Custom User Properties for Active Directory Available to IBM Cognos Components Enabling Secure Communication to the Active Directory Server . . . . . . . . . Include or Exclude Domains Using Advanced Properties . . . . . . . . . . . . Enable single signon between Active Directory Server and IBM Cognos components . . Configuring IBM Cognos to Use IBM Cognos Series 7 Namespace. . . . . . . . . . Configure an IBM Cognos Series 7 Namespace . . . . . . . . . . . . . . . Enabling Secure Communication to the Directory Server Used by the IBM Cognos Series 7 Enabling Single Signon Between IBM Cognos Series 7 and IBM Cognos . . . . . . . IBM Cognos Series 7 Namespaces and the IBM Cognos Series 7 Trusted Signon Plug-in . Configuring IBM Cognos to Use a Custom Authentication Provider . . . . . . . . . Configure a Custom Authentication Namespace . . . . . . . . . . . . . . . Hide the Namespace from Users During Login . . . . . . . . . . . . . . . Configuring IBM Cognos Components to Use LDAP . . . . . . . . . . . . . . LDAP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . Configure an LDAP Namespace . . . . . . . . . . . . . . . . . . . . Configure an LDAP namespace for Active Directory Server . . . . . . . . . . . Configure an LDAP Namespace for IBM Directory Server . . . . . . . . . . . Configure an LDAP Namespace for Novell Directory Server. . . . . . . . . . . Configure an LDAP Namespace for Oracle Directory Server . . . . . . . . . . . Make Custom User Properties for LDAP Available to IBM Cognos Components . . . . Enable Secure Communication to the LDAP Server . . . . . . . . . . . . . . Enabling Single Signon Between LDAP and IBM Cognos Components . . . . . . . Replace operation . . . . . . . . . . . . . . . . . . . . . . . . . Configure IBM Cognos components to use CA SiteMinder . . . . . . . . . . . . Configuring the SiteMinder namespace . . . . . . . . . . . . . . . . . . Configuring IBM Cognos to Use a RACF Provider for Authentication . . . . . . . . Configuring a RACF Namespace . . . . . . . . . . . . . . . . . . . . Enabling single signon between RACF and IBM Cognos . . . . . . . . . . . . Configure IBM Cognos to use SAP . . . . . . . . . . . . . . . . . . . . Configure an SAP Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

331
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 333 333 334 335 336 336 338 341 342 343 343 344 346 346 347 347 347 348 349 351 353 355 357 358 359 359 360 361 363 363 364 364 366

viii

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Enable Single Signon Between SAP and IBM Cognos . Delete an Authentication Provider . . . . . . . .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. 367 . 367

Chapter 14. Using an application server other than Tomcat

. . . . . . . . . . . . 369
. . . . . . . . . . . . . . . . . . . . . . . 369 370 370 371 372 373 374 375 377 378 378 379 379 380 380 381 383 384 385 385 386 386 386

Create a separate JVM instance . . . . . . . . . . . . . . . . . . . . . . . . . . . Set JVM parameters for performance . . . . . . . . . . . . . . . . . . . . . . . . Check the setup of IBM Cognos components . . . . . . . . . . . . . . . . . . . . . . . Back up existing IBM Cognos information . . . . . . . . . . . . . . . . . . . . . . . . Set environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjusting the default connection time-out value for IBM Cognos Business Intelligence . . . . . . . . . Add user role to enable single signon between IBM WebSphere profiles . . . . . . . . . . . . . . Configure IBM Cognos components to run within the application server . . . . . . . . . . . . . Use the Build Application Wizard to build and install IBM Cognos on IBM WebSphere Application Server . Identifying the JDK for WebLogic 9 on AIX . . . . . . . . . . . . . . . . . . . . . . . Change the application server startup script . . . . . . . . . . . . . . . . . . . . . . . Change the application server startup script for WebLogic . . . . . . . . . . . . . . . . . Change the application server startup script for JBoss . . . . . . . . . . . . . . . . . . . Configure application server properties and install IBM Cognos components . . . . . . . . . . . . Install IBM Cognos on WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . Install IBM Cognos on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . Install IBM Cognos on SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . Install IBM Cognos on JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the secure socket layer . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring web communication . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure virtual directory for SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . Unregister dispatchers that were configured for Tomcat . . . . . . . . . . . . . . . . . . . Upgrade to IBM Cognos BI in an application server environment . . . . . . . . . . . . . . . .

Chapter 15. Performance Maintenance

. . . . . . . . . . . . . . . . . . . . . 389
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 389 390 393 393 394 394 394 395 395 395

System Performance Metrics . . . . . . . . . . . . . . Monitoring System Metrics Externally . . . . . . . . . . Enabling Only Services That are Required . . . . . . . . . . Tuning a DB2 Content Store . . . . . . . . . . . . . . Adjusting the Memory Resources for the IBM Cognos Service . . . Reducing the number of requests per process . . . . . . . . Tune Apache Tomcat settings for 64-bit installations . . . . . . Increase the Request-handling Capacity for Cognos Content Database Improve Metric Store Database Performance . . . . . . . . . Reduce Delivery Time for Reports in a Network. . . . . . . . Increase Asynchronous Timeout in High User Load Environments .

Chapter 16. Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Manually change default configuration settings . . . . . . . . . . . . . . Adding a component to your configuration . . . . . . . . . . . . . . . Changing manually encrypted settings . . . . . . . . . . . . . . . . . Global settings on UNIX and Linux operating systems . . . . . . . . . . . Changing manually the global settings on UNIX and Linux operating systems . . Starting and stopping Cognos BI in silent mode on UNIX and Linux operating systems Starting Cognos BI in silent mode on UNIX and Linux operating systems . . . . Stopping Cognos BI in silent mode on UNIX and Linux operating systems . . . . Manually create an IBM Cognos application file . . . . . . . . . . . . . . Creating an IBM Cognos application file for the Business Intelligence software . . Creating an IBM Cognos application file for a servlet gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 398 399 400 401 402 402 402 403 403 404

Chapter 17. Using an unattended installation and configuration. . . . . . . . . . . 407
Unattended installations . . . . . . . . . . . . . . Use a response file from an installation on another computer Modifying a response file . . . . . . . . . . . . Starting an unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 408 409 410

Contents

ix

Use an unattended configuration . Use an unattended uninstallation.

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. .

. 411 . 412

Chapter 18. Uninstalling IBM Cognos BI . . . . . . . . . . . . . . . . . . . . . 413
Uninstall IBM Cognos Business Intelligence on UNIX or Linux operating systems . . Uninstall IBM Cognos Business Intelligence on Microsoft Windows operating systems . . . . . . . . . . . . . . . . . . 413 . 414

Appendix A. Accessibility features . . . . . . . . . . . . . . . . . . . . . . . 415
Keyboard Shortcuts for the Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . 415

Appendix B. Google OneBox Integration for IBM Cognos Business Intelligence. . . . 417
Configuring the IBM Cognos OneBox Components . . . . . . Set up security for a Google OneBox sample module . . . . Configure a Google OneBox sample module . . . . . . . Customizing the search results for the Google OneBox provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 419 420 421

Appendix C. IBM Cognos Configuration command-line options . . . . . . . . . . . 427 Appendix D. Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
The Sample Outdoors Company . . . . . . . . . . . . . . The Sample Outdoors Group of Companies . . . . . . . . . Employees . . . . . . . . . . . . . . . . . . . . Sales and marketing . . . . . . . . . . . . . . . . . Sample Outdoors database, models, and packages . . . . . . . Install the IBM Cognos Business Intelligence Samples . . . . . . . Installing samples on UNIX or Linux . . . . . . . . . . . Installing samples on Windows . . . . . . . . . . . . . Setting up the samples . . . . . . . . . . . . . . . . . Using samples . . . . . . . . . . . . . . . . . . . Restoring backup files for the samples databases . . . . . . . Restore the samples on IBM DB2 using a script . . . . . . . . Restore the samples on Oracle using a script . . . . . . . . . Create data source connections to the samples databases . . . . . Set Up Microsoft Analysis Services Cube Samples . . . . . . . Set Up the InfoSphere Warehouse Cubing Services Sample . . . . Set up the IBM Cognos TM1 samples . . . . . . . . . . . Set up the Essbase cube sample . . . . . . . . . . . . . Creating Data Source Connections to OLAP Data Sources . . . . Setting up the Metric Studio sample . . . . . . . . . . . . Import the samples . . . . . . . . . . . . . . . . . Framework Manager Sample Database Models . . . . . . . . Example - Running the Sample ELM Returns Agent Against Changed Remove the Sample Packages and Reports from IBM Cognos BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 429 431 431 432 434 434 435 435 436 436 439 442 446 447 448 449 450 451 454 455 458 458 460

Appendix E. Troubleshooting

. . . . . . . . . . . . . . . . . . . . . . . . . 461
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 463 464 464 465 466 467 470 470 471 472 473 474 474

Troubleshooting a problem . . . . . . . . . . . . . . . . . . . . . . . Searching knowledge bases . . . . . . . . . . . . . . . . . . . . . . Getting fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting IBM Support. . . . . . . . . . . . . . . . . . . . . . . Exchanging information with IBM . . . . . . . . . . . . . . . . . . . Subscribing to Support updates . . . . . . . . . . . . . . . . . . . . Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot run issetup on Linux operating systems . . . . . . . . . . . . . . . . Problems starting IBM Cognos Business Intelligence . . . . . . . . . . . . . . CFG-ERR-0106 error when starting the IBM Cognos service in IBM Cognos Configuration Cryptographic error when starting IBM Cognos Business Intelligence . . . . . . . Unable to start the IBM Cognos service because the port is used by another process . . IBM Cognos service does not start or fails after starting . . . . . . . . . . . . IBM Cognos Business Intelligence server fails to start and gives no error message . . .

x

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . IBM Cognos services fail to restart after a network outage . . . . . 487 . . . . . . . . . Cannot Open a Microsoft Cube or PowerCube . . . . . . Download of resource fails . . . . . . . . . . . . . Restarting the IBM Cognos service to apply configuration settings. . . . . . . . . . . . . . . . . . . CAM-CRP-0221 error when logging into the portal . . . . . . . . . . . . . . . . . Cannot log on to a namespace when using IBM Cognos Connection . . . . . . . . . . . . . . . Deploying IBM Cognos Business Intelligence IBM WebSphere Application Server fails . . . . . . . Content Manager fails to start or takes a long time to start . . . . . . . . 487 488 488 489 492 493 493 494 494 495 495 495 496 496 496 497 497 497 498 498 498 499 499 500 500 500 501 502 503 503 504 504 505 506 xi . . . Error trying to encrypt information when saving your configuration . . . . . . . . . . . . . . . . . . . . . . . Page cannot be found error running reports using IBM Cognos for Microsoft Office . . . . . . . . .xts file . Servlet class fails to load in WebLogic . . ESSBASEPATH cannot be detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .war file to WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Studio does not start . . . . Unable to deserialize context attribute error when deploying the p2pd. . . . . . . . . . . . . . . . . . . . . . . . . . . . Users are prompted for Active Directory credentials . .5 fails . . . . . . . The page cannot be found when starting IBM Cognos Business Intelligence in Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The page is not shown when opening a portal after installing IBM Cognos Business Intelligence . . . . . . . . . . .Server not available when starting IBM Cognos Business Intelligence. . . . . . . . DPR-ERR-2022 error displays in Web browser when starting IBM Cognos Business Intelligence . . . . . . . Group membership is missing from Active Directory namespace . . . .1. . . . . . . . . . . . . . . . . . CGI timeout error while connected to IBM Cognos Business Intelligence through a Web browser . . . . . . . . . . . . . DPR-ERR-2058 Error Displays in Web Browser When Starting IBM Cognos Business Intelligence . . . . . . . . IBM Cognos Business Intelligence running under WebLogic Application Server on AIX fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unable to download the cognos. . . . . . . . . . . . . . . . . . . . . . . . . . . CAM-CRP-1315 error when saving configuration . . . . . . . . . . . . . . . . . Running Database and Index Cleanup Scripts . . . DPR-ERR-2079 when Content Manager configured for failover . . . . . . . . . . . . . . . . . . . DPR-ERR-2008 error when you open a report . . . . . . . . . . Manually changing the installation directory name affects installations running under an application server Configuration data is locked by another instance of IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 474 477 477 478 478 478 478 479 480 480 480 481 482 482 484 484 484 485 485 485 486 486 486 . . . . . . . . . . . . . DPR-ERR-2014 error displays in log file on Content Manager computer . . . . . . Unable to start IBM Cognos service when upgrading multitenant installations. . . . . . . . . . . Importing a large deployment in Windows crashes the Java virtual machine . . . . . . . . . RSV-SRV-0066 a soap fault has been returned or RQP-DEF-0114 the user cancelled the request errors display in high user load environments . . . . . . . . . . . DB2 not found error for Linux on System z . . Desktop icons or IBM Cognos Configuration window flicker on Windows . . . . . . . . . . . . . . . Problems testing data source connections with IBM Cognos BI deployed on SAP NetWeaver Application Server 7. . . . . . CCL-BIT-0006 error message when using WebSphere Application Server on a heavily loaded system . . . . . . . Problems configuring IBM Cognos Business Intelligence . . . . . . . . . . . . . . . . . Application server startup script fails . . . . . . . . Errors displayed when deploying to Oracle 10G Application Server . . . . . . . . . . . . . . . . . . . . . . Cannot load TM1 Cubeviewer or WebSheet iWidget in Business Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unable to exit a tab sequence when using keyboard-only navigation in IBM Cognos Configuration . . . . . . . . . . Query fails when using Oracle Essbase Server . . . . . . . . . . . . . . . . Cryptographic error when starting IBM Cognos Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-ASCII characters in installation directory cause run-time errors . . . . . . . . . . . . . . . . . Unable to save your configuration . . . . . . . . . Java error when starting IBM Cognos Configuration . . . . . . DB2 returns SQL1224N error when connecting from AIX . . . . . . . . . . . . . . . . . . . . . . Prompted to download the ISAPI gateway . . . Error displays after upgrading IBM Cognos Business Intelligence on a WebLogic Application Server . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . Font on UNIX not found when starting IBM Cognos Configuration . . . . . . CM-CFG-029 error when trying to save a configuration that specifies a Microsoft SQL Server content store . No warning that installing later version will automatically update earlier version of content store . . . . . . . Corrupt characters while installing in some languages on Linux . . . . . . . . Accented or double-byte characters may not display correctly when installing IBM Cognos Business Intelligence on Linux . . . . . . . . . . . . . . . . . Importing a large content store in Solaris using JRE 1. . Content Manager error when starting IBM Cognos Business Intelligence . . . . . . . .1 on UNIX . . . . . . . . . . .

.2. .1: Installation and Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Missing translations for object names in some locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Notices . . . . . . . . . . . . . . . . . . 509 Index . 513 xii IBM Cognos Business Intelligence Version 10. .

com/support/ docview. 2013 xiii . access one of the IBM Cognos Information Centers (http://pic. This product has accessibility features. including all translated documentation. analysis. upgrading. v In the c10_location\webcontent\documentation\en folder. Release Notes are published directly to Information Centers. PDF documents are supplemental and. see “Keyboard Shortcuts for the Installation Wizard” on page 415. You can access the documentation by the following methods: v In IBM Cognos Administration. developer documentation is available from within the product. and event management features. and include links to the latest technotes and APARs. to use information technology products. and testing IBM Cognos BI. and under IBM Cognos Documentation you can open Software Development Kit documents in PDF or HTML format.com/infocenter/cogic/v1r0m0/index. click Help > More Documentation. IBM Cognos BI is a Web product with integrated reporting. such as restricted mobility or limited vision. you can open the documents in PDF or HTML format. you should be familiar with v reporting concepts v scorecarding concepts v database and data warehouse concepts v security issues v basic Windows or UNIX administration skills v the existing server environment and security infrastructure in your organization Finding information To find IBM Cognos product documentation on the web. or access the PDFs from the IBM Cognos product documentation web page (www. scorecarding. changing application servers.wss?uid=swg27024067). Audience To use this guide. and setting up samples. as © Copyright IBM Corp.Introduction This document is intended for use with IBM® Cognos® Business Intelligence.jsp). For information on these features. You can also read PDF versions of the product online help files by clicking the PDF links at the top of each HTML page. configuring.ibm. IBM Cognos Software Development Kit Product Documentation After you install the IBM Cognos Software Development Kit. IBM Cognos HTML documentation has accessibility features. This guide contains instructions for installing. Accessibility Features Accessibility features help users who have a physical disability.dhe. 2005.ibm.

Forward-looking statements This documentation describes the current functionality of the product. Samples disclaimer The Sample Outdoors Company. Great Outdoors Company. promise. for use as sample data to develop sample applications. contact numbers. and human resources. Other sample files may contain fictional data manually or machine generated. finance. Product names referenced may be the trademarks of their respective owners. The development.1: Installation and Configuration Guide . References to items that are not currently available may be included. and Planning Sample depict fictitious business operations with sample data used to develop sample applications for IBM and IBM customers. or transaction values is coincidental. include no added accessibility features.2. No implication of any future availability should be inferred. factual data compiled from academic or public sources. xiv IBM Cognos Business Intelligence Version 10. Any resemblance to actual names. code. Any such references are not a commitment. addresses. or functionality. or data used with permission of the copyright holder. release. product distribution. or legal obligation to deliver any material. Unauthorized duplication is prohibited. any variation of the Sample Outdoors or Great Outdoors names. The samples included with IBM Cognos Business Intelligence are for demonstration purposes only and are not fully accessible. GO Sales. These fictitious records include sample data for sales transactions.such. and timing of features or functionality remain at the sole discretion of IBM.

see “Change the security standard compliance for IBM Cognos trust stores” on page 250.com/support/ docview.2. For information about other new features for this release. database servers. For more information. New security standards in IBM Cognos BI By default.ibm. web servers. directory servers. deprecated. © Copyright IBM Corp.1 The following topics describe the new features for 10. For a 32-bit installation. and application servers. It will help you plan your upgrade and application deployment strategies and the training requirements for your users. 2005. browsers. 2013 1 . IBM Cognos version 10.1 is qualified for the NIST SP800-131a standard as the product's cryptographic functions are configured for this standard. see the New Features Guide. you had to manually move the 64-bit gateway files.2. The 64-bit version of the gateway is now the default for all 64-bit installations. patches. see the IBM Software Compatibility reports (www. External object store for archiving of reports You can configure the Content Manager to store report output to a local drive or network share instead of in the content store database by configuring an external object store. if you installed the 64-bit versions of IBM Cognos Business Intelligence. If you wanted to use the 64-bit version of the gateway. You can configure IBM Cognos BI to comply with other standards or remove cryptographic components that are associated with older standards by using the ThirdPartyCertificateTool. including information on operating systems.wss?uid=swg27037784).Chapter 1. changed. the 32-bit version of the gateway is the default for 32-bit installations. the 32-bit version of the gateway components were the default versions. and removed features that affect installation and configuration for this release.1. An external object store offers improved read and write performance by reducing the load on the Content Manager. What's new? This section contains a list of new. New features in version 10. To review an up-to-date list of environments that are supported by IBM Cognos Business Intelligence products. 64-bit IBM Cognos gateway as default in 64-bit installations In earlier versions.2.

2 IBM Cognos Business Intelligence Version 10.2.Related tasks: “Use an external object store for report output” on page 240 You can configure Content Manager to store report output to a local drive or network share by defining an external object store. In this version. Related concepts: “Configuring multitenancy settings” on page 242 Before you can use IBM Cognos multitenancy. you can configure your environment by selecting from a number of predefined LDAP authentication namespace configurations. 64-bit IBM Cognos gateway In earlier versions.ITenantProvider advanced properties to individual namespaces or to all namespaces in your environment.TenantPattern or multitenancy. you must modify configuration settings in your IBM Cognos Business Intelligence installation. the 32-bit version of the gateway is the default for 32-bit installations.OracleSunOne Option to view the status of silent installations on the screen You can use the -displayLog option to view the status of the silent installation on the screen in a UNIX or Linux environment.0 The following topics describe the new features for 10. For a 32-bit installation.IBM Tivoli® v LDAP . Configuration of multi-tenant applications in IBM Cognos Configuration You can use new properties in IBM Cognos Configuration to configure Business Intelligence environments supporting multi-tenant applications. For example. Report output is available through IBM Cognos Connection and IBM Cognos SDK. Depending on your environment. 64-bit versions of the gateway are also available. The following is a list of predefined LDAP configurations: v LDAP .0.2. The installation program uses the test. Multitenancy properties that you specify for a specific namespace override any multitenancy properties that you set globally.Active Directory v LDAP . you can apply the multitenancy.1: Installation and Configuration Guide . if you installed 64-bit versions of IBM Cognos Business Intelligence. Predefined LDAP configurations In IBM Cognos Configuration.ats as the response file and displays the status of the installation on the screen. New features in version 10. but the report output is not stored in the content store database.2. only 32-bit versions of the gateway component were available. the following command runs the installation program in silent mode. The 64-bit version of the gateway is the default for all 64-bit installations.

64-bit Report Server In the 64-bit installations.xml file must still exist in the Configuration directory. The cogstartup.xml file located in the Configuration directory to set the configuration parameters. the following command runs the installation program in silent mode using the test.xml option to specify a startup file other than the cogstartup.xml Related tasks: “Modifying a response file” on page 409 Generate and modify a response file to specify and record your installation preferences. When installing on a 64-bit system. New features in version 10. included with the Application Tier Components. is provided in both 32.1 The following are the new features since the last release. the report server component. The software supports an IBM FileNet® Content Manager with IBM FileNet® CMIS external repository. Related concepts: “Installing 64-bit versions of IBM Cognos BI products” on page 22 Some IBM Cognos BI components are available for 64-bit systems.. Option to initialize Cognos Configuration from a different file You can use the -startupfile path/filename.ats -displayLog Related tasks: “Starting an unattended installation” on page 410 You can start an unattended installation and either choose to display or not display messages during the installation process. IBM Cognos Content Archival IBM Cognos Content Archival allows you to store report output versions and their source report specifications to an external content archival repository./issetup -s test. You can also modify the response file template that is provided.sh -s -startupfile <c10_location>/configuration/test. cogconfig.xml file when starting the IBM Cognos configuration tool. the components must be installed in the appropriate directories. Chapter 1. For example.and 64-bit versions. What's new? 3 . The 64-bit version of report server is intended for use with packages created for dynamic query mode.1. IBM Cognos Content Archival is bundled with the Business Intelligence software and is used with a file system repository for test and development purposes only.

Table 1.1. New features in version 10. and configure your IBM Cognos application on IBM WebSphere® Application Server. install.” on page 313 Storing archived content in your external repository provides you with the ability to adhere to regulatory compliance requirements. Dynamic Query Mode IBM Cognos Business Intelligence Server offers improved query functionality and performance with a dynamic query mode that you can use with supported data sources. Script to generate an IBM DB2 content store database You can create an SQL Data Definition Language (DDL) file from within IBM Cognos Configuration. Query Guide 4 IBM Cognos Business Intelligence Version 10.Related concepts: Chapter 11. its IBM Cognos Business Intelligence Dynamic benefits. Install IBM Cognos to IBM WebSphere from the Build Application Wizard You can use the Build Application Wizard in IBM Cognos Configuration to install and configure IBM Cognos BI. and can enhance the scalability and performance of IBM Cognos products by reducing the size of content in the content store. The script file is called a DDL file. Related tasks: “Use the Build Application Wizard to build and install IBM Cognos on IBM WebSphere Application Server” on page 377 Use the Build Application Wizard to build. see the documents listed in the following table.0 include the following. “IBM Cognos content archival. Where to find information about dynamic query mode What are you looking for? Where to find the information An overview of the dynamic query mode. and considerations when using it.1. Related tasks: “Generating a script file to create a database for a DB2 content store” on page 81 You can generate a script file to automatically create the content store in IBM DB2 on all platforms.1: Installation and Configuration Guide . More Information about Dynamic Query Mode For more information about dynamic query mode.0 New features in version 10.2. Run the script in IBM DB2® to create a database that you can use for the IBM Cognos content store. Some configuration is required before you can use dynamic query mode. Additional options have been added to the wizard to allow you to install and configure the product directly from IBM Cognos Configuration.

you must install and configure IBM Connections and the software that it requires. In Version 10. Where to find information about dynamic query mode (continued) What are you looking for? Detailed information about techniques and product behaviors of the dynamic query mode. including caching and query service properties. or both.ibm. Where to find the information IBM Cognos 10 Dynamic Query Cookbook in the Proven Practices section of the IBM Cognos Customer Center (http://www. IBM Cognos Workspace users can create activities in IBM Connections and share them with other users who collaborate in decision-making and problem-solving processes. Information about testing reports in the dynamic query mode prior to upgrade. To take advantage of this capability.0. or Java™ Database Connectivity (JDBC) driver files.1. the required software might include database clients. IBM Cognos Business Intelligence Information about query service Administration and Security Guide administration. “Using Collaboration with IBM Cognos Workspace. Access to Software Development Kit Installation and Configuration Guide In previous releases. Depending on the data source and query mode. IBM Connections and all software components required to use it with Cognos BI are bundled with the IBM Cognos BI server products.” on page 321 Collaboration capabilities in IBM Cognos Workspace provide a bridge between using IBM Cognos Business Intelligence to discover a business problem and acting to resolve it. Information about publishing packages for the dynamic query mode. What's new? 5 . IBM Cognos Framework Manager User Guide IBM Cognos Lifecycle Manager User Guide IBM Cognos Software Development Kit Developer Guide Related concepts: “Set up database connectivity for reporting databases” on page 86 To support communication between IBM Cognos Business Intelligence and the data sources. Related concepts: Chapter 12. Collaboration Using IBM Cognos Workspace Collaboration capabilities in IBM Cognos Workspace provide a bridge between using IBM Cognos Business Intelligence to discover a business problem and using social software to track and resolve the problem. you must install additional software for your data sources on the same computer that hosts the report server. IBM Cognos Business Intelligence Installation and Configuration Guide Information about enabling connectivity for data sources supported by the dynamic query mode.com/software/data/ cognos/customercenter/).Table 1. the documentation for IBM Cognos Software Development Kit was not available online. Information about using the IBM Cognos Software Development Kit to administer query service properties and develop client applications to use dynamic query mode. Chapter 1. including IBM WebSphere Application Server and its updates.

This brings the information consumption. Index Search Capabilities are Native to IBM Cognos BI Server In earlier releases. You do not need to install a separate dashboard package. index search capabilities were available by installing IBM Cognos Go! Search with your IBM Cognos BI server product.1. see the IBM Cognos Business Intelligence Administration and Security Guide. but some tasks are required to upgrade from IBM Cognos Go! Dashboard. IBM Cognos Viewer is still available and maintained in this release. You do not need to install a separate package.com/infocenter/cbi/v10r1m0/. IBM Cognos Go! Dashboard is Merged with Features from IBM Cognos Viewer into One User Interface In earlier releases.1. 6 IBM Cognos Business Intelligence Version 10. In addition. an interactive dashboard application was available by installing IBM Cognos Go! Dashboard with your IBM Cognos BI server product.0 Links to directly-related topics are included for changed features since the last release Default Installation Location and Web Alias The path for the default installation directory is changed in IBM Cognos Business Intelligence. IBM Cognos Viewer provided the basic report consumption experience.1: Installation and Configuration Guide . is as follows: v Microsoft Windows operating system C:\Program Files\IBM\cognos\c10 v UNIX and Linux operating systems /usr/IBM/cognos/c10 The default Web alias in IBM Cognos Configuration is changed from cognos8 to ibmcognos.1. Version 10. rather than viewing and opening folders.1 MR3 or MR4 and earlier versions of IBM Cognos BI to newer versions of IBM Cognos Business Intelligence.ibm. IBM Cognos Go! Dashboard and features from IBM Cognos Viewer are now merged into one user interface. Upgrade Manager is Renamed as Lifecycle Manager Lifecycle Manager is a Microsoft Windows operating system-based application for auditing upgrades from ReportNet 1. to the forefront of the experience. The default location. and you must create the index before using the index search capability. The index search capability is now the default search mode in the IBM Cognos BI server product.0 is available from the IBM Cognos Information Center. represented by c10_location in this guide.0. Changed Features in Version 10. However. at pic. For information about creating the index and about configuring user permissions for index search.dhe. but some configuration is required to enable index services and configure scalability.2. it was named Upgrade Manager. In earlier releases.The IBM Cognos Software Development Kit Installation and Configuration Guide in version 10.

an important diagnostic tool for investigating the behavior of IBM Cognos BIs. and log database. and product-specific content. these products are bundled with the IBM Cognos BI server products. Related concepts: “Guidelines for creating the content store” on page 45 The content store is a database that Content Manager uses to store global configuration data. Version 10. and IBM HTTP Server. you can also use it for authentication in IBM Cognos products. The products included IBM WebSphere Application Server. Support for Informix Dynamic Server Database IBM Cognos Business Intelligence server supports the use of Informix® Dynamic Server as a database for the content store. notification database.0. Related tasks: “Configuring IBM Cognos to Use a RACF Provider for Authentication” on page 363 If you use a Resource Access Control Facility (RACF) provider for authentication in your enterprise environment. you can configure a RACF namespace directly in IBM Cognos Configuration on AIX® or on Linux for System z® operating systems. What's new? 7 .0.IBM Cognos Special Edition is Integrated with the IBM Cognos BI Server Products In earlier releases. IBM Cognos Special Edition provided you with all of the IBM products to create an enterprise reporting solution. Related tasks: “Running Database and Index Cleanup Scripts” on page 489 In some troubleshooting situations. IBM Cognos Portal Services BEA AquaLogic User Interaction (ALUI) Portal is replaced by Oracle WebCenter Interaction Portal. You must use one of the supported enterprise-level databases as the content store in a production environment. Scripts are also provided for cleaning up the tables and indexes in an Informix Dynamic Server database. you may be advised to start with new configuration data. In Version 10.1. Chapter 1. if you wanted to use a Resource Access Control Facility (RACF®) provider for authentication with IBM Cognos Business Intelligence server. IBM DB2 Universal Database™. Enhanced Support for Authentication Using a RACF Provider In earlier releases. connections to data sources. global settings (such as the language and currency formats shown in the user interface). “Configuring a Repository for Log Messages” on page 261 The BI Bus protocol includes log message processing. In IBM Cognos Business Intelligence server.1. you created a custom Java provider and then configured a Custom Java Provider namespace in IBM Cognos Configuration to use it.

Related tasks: “Monitoring System Metrics Externally” on page 389 You can monitor system metrics outside of IBM Cognos Administration by using industry standard Java Management Extensions (JMX). In IBM Cognos Business Intelligence Server. 8 IBM Cognos Business Intelligence Version 10.2. and view IBM Cognos reports in your working environment. IBM Cognos Configuration provides two new properties that you can use to enable secure access to the metrics in the Java environment. You can use the portlets to navigate.Related concepts: Chapter 10. you configure two JMX properties in IBM Cognos Configuration to enable secure access to the metrics in the Java environment. you could monitor system metrics externally to IBM Cognos Administration by using Java Management Extensions (JMX). “Configuring Portal Services.0.” on page 299 Portal Services provides a set of IBM Cognos portlets that you can use in IBM Cognos Connection and in other portals. search.1. Version 10. Other users can view IBM Cognos information without needing to know how to use IBM Cognos products. Secure Access When Monitoring System Metrics Externally In earlier releases. First. Then you use a secure user ID and password to connect to the metrics through a JMX connection tool.1: Installation and Configuration Guide . a technology that supplies tools to manage and monitor applications and service-oriented networks.

or both. you might expand your solution in the following way: v Start by using IBM Cognos Insight for data discovery. Cognos Express. The following table provides a comparison of products in the IBM Cognos family. and then expand your solution over time. v As your user community grows or your analytic requirements change. The solutions are scalable and deployable in different sized environments. from a desktop to a single server to a server farm. Distribution options Before implementing IBM Cognos Business Intelligence. visualization. IBM Cognos family The IBM Cognos family of products includes IBM Cognos Insight. For example. Create additional analytics to help with planning. From a server you can remotely install Cognos Insight on desktops across your organization. v Add a server that uses IBM Cognos Express to share the insights that your users acquire. you can start with a limited solution that addresses an immediate need. and reporting from large data sets. If your environment includes other IBM Cognos products. IBM Cognos Enterprise can be IBM Cognos TM1®. The best distribution option depends on your reporting or scorecarding requirements. You can acquire insights from real-time corporate information and collaborate with members of your organization through mobile devices. and Cognos Enterprise Key capabilities Dashboards Analysis What-if scenario modeling Planning and budgeting Production reports Cognos Insight X X X X Cognos Express X X X X X Cognos Enterprise X X X X X © Copyright IBM Corp. IBM Cognos Business Intelligence. decide how you will install it in your environment. 2013 9 . you must consider how IBM Cognos BI will fit into that environment. resources.Chapter 2. Table 2. and IBM Cognos Enterprise. IBM Cognos Express®. 2005. expand your capabilities by using IBM Cognos Enterprise (IBM Cognos TM1 and IBM Cognos Business Intelligence). and preferences. analysis. Comparison of the key capabilities of Cognos Insight. The IBM Cognos family of products provides integrated solutions that are the right size for your organization. and planning. IBM Cognos BI is compatible with other IBM Cognos products. Configuration requirements differ depending on whether you install all components on one computer or more than one computer. You can install all of the server components on one computer. Because the solutions share a common foundation. or distribute them across a network.

Cognos Express. Some of these existing resources are required. as well as the server functionality for routing and processing user requests. such as using a security provider for authentication. you can select to install the following server components: v Gateway v Application Tier Components 10 IBM Cognos Business Intelligence Version 10.Table 2. v Large enterprises that need to deploy analytics capabilities to hundreds or thousands of people can meet their needs with Cognos Enterprise. and planning by using Cognos Express. desktop analytics can meet their needs with Cognos Insight. v Midsize organizations or workgroups within larger organizations can meet their needs for integrated reporting. analysis.1: Installation and Configuration Guide . Server components Server components provide the user interfaces for reporting. Cognos enterprise product components IBM Cognos Business Intelligence is a Web-based business intelligence solution with integrated reporting. analysis. Other resources are optional. analysis. and event management. or using an application server. Comparison of the key capabilities of Cognos Insight.2. IBM Cognos BI integrates easily into your existing infrastructure by using resources that are in your environment. Server components provide the user interfaces for reporting and data exploration. as well as the server functionality for routing and processing user requests. By default. You can configure IBM Cognos BI products to run on supported application servers that you currently use in your environment. scorecarding. In the installation program. scorecarding. and Cognos Enterprise (continued) Key capabilities Microsoft Office integration Support for Apple iPad Support for other mobile devices Enterprise-wide collaboration Software Development Kit Cognos Insight Cognos Express X X Cognos Enterprise X X X X X The Cognos family addresses the business intelligence and performance management needs of the following entities: v Individuals who require personal. IBM Cognos BI uses Apache Tomcat as an application server. and event management features. IBM Cognos Business Intelligence includes IBM Cognos Business Intelligence Server and IBM Cognos Business Intelligence Modeling. such as using a database for the content store.

Central administration . scorecards.Report Studio Using Report Studio.gateway Web communication in IBM Cognos Business Intelligence is typically through gateways.IBM Cognos Administration IBM Cognos Administration is a central management interface that contains the administrative tasks for IBM Cognos BI. and to start and stop its services. report authors create. It is accessible through IBM Cognos Connection and any existing enterprise portal.IBM Cognos Connection IBM Cognos Connection is a Web portal provided with IBM Cognos Business Intelligence. and viewing content . Viewing and interacting with published content . and edit and modify reports created in Query Studio or Analysis Studio. A gateway is an extension of a Web server program that transfers information from the Web server to another server. which reside on one or more Web servers. Users can run all their Web-based IBM Cognos BI applications through 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. Distribution options 11 . They can also define corporate-standard report templates for use in Query Studio. and queries. An IBM Cognos BI server runs requests.IBM Cognos Configuration IBM Cognos Configuration is a tool that you use to configure IBM Cognos BI. and for creating reports. Application Tier Components The IBM Cognos Business Intelligence applications tier contains one or more IBM Cognos BI servers. managing.v Content Manager Web communication . providing a single access point to the corporate data available for its products. An IBM Cognos BI server also renders the IBM Cognos Connection and studio interfaces. Chapter 2. edit. and distribute a wide range of professional reports. such as reports. or as a servlet implementation. It provides easy access to the overall management of the IBM Cognos environment and is accessible through IBM Cognos Connection. and organizing data. analyses. but may follow other standards. Gateways are often CGI programs. such as Internet Server Application Program Interface (ISAPI). can be integrated with IBM Cognos Connection. It provides a single point of entry for querying. Professional reporting . that are forwarded by a gateway. Configuring and managing the product . Publishing. Apache Modules (apache_mod). Other business intelligence applications. and web addresses to other applications. and events. analyzing.

IBM Cognos for Microsoft Office is not included with IBM Cognos Metrics Manager. You can view and open favorite workspaces and reports. You can also use comments and activities for collaborative decision making. professional reports created in Report Studio. configuration data. Agents can publish details to the portal.2. a support call from a key customer or the cancellation of a large order may trigger an event. Facilitating decision-making . sending an e-mail to the appropriate people. Microsoft Office compatibility . Managing Application Data .IBM Cognos Workspace You can create sophisticated interactive workspaces using IBM Cognos content. For example. create and save reports to meet reporting needs not covered by the standard. deliver alerts by email. retrieve or store report specifications. report specifications. 12 IBM Cognos Business Intelligence Version 10. according to your specific information needs. Users can monitor. Microsoft Office users can access data from IBM Cognos reporting products within Microsoft Office applications. users with little or no training can quickly design.Event Studio In Event Studio. you set up agents to monitor your data and perform tasks when business events or exceptional conditions occur in your data that must be dealt with. and e-mail your findings. You can also use social software such as IBM Connections for collaborative decision making. Analyzing metrics .Query Studio Using Query Studio. and report output. people are alerted to take action. models. Content Manager stores information in a content store database. Content Manager is needed to publish packages.Content Manager Content Manager is the IBM Cognos Business Intelligence service that manages the storage of customer application data.Metric Studio In Metric Studio. analyze.1: Installation and Configuration Guide . metrics. Monitoring data for exceptional conditions . you can create and deliver a customized scorecarding environment for monitoring and analyzing metrics throughout your organization. run and distribute reports based on events. IBM Cognos for Microsoft Office components are included with IBM Cognos BI and must be installed separately. and monitor the status of events. manage scheduling information. including security. and manage the Cognos namespace. as well as external data sources such as TM1 Websheets and CubeViews.Ad hoc querying and self-service reporting . When an event occurs.IBM Cognos for Microsoft Office Using IBM Cognos for Microsoft Office. manipulate the content. and report on time-critical information by using scorecards based on cross-functional metrics.

Metadata is published for use by reporting tools as a package. Preconfigured application database . Modifying the Apache Derby database or using it with other products is not supported.Framework Manager IBM Cognos Framework Manager is the modeling tool for creating and managing business-related metadata for use in IBM Cognos BI analysis and reporting.Cognos Content Database Cognos Content Database is an instance of an Apache Derby database. it is preconfigured as the default content store for IBM Cognos Business Intelligence. integrated business view of any number of heterogeneous data sources.IBM Cognos BI Virtual View Manager IBM Cognos BI Virtual View Manager provides access to additional data sources such as LDAP. but not as a query database. You can also use them for experimenting with and sharing report design techniques.Optional server components The following optional components are available to install on the server to extend the functionality of IBM Cognos Business Intelligence. You can use Cognos Content Database as a content store or notification database. Distribution options 13 . Learning and troubleshooting using sample data . Extracts are used to map and transfer information Chapter 2.IBM Cognos BI Samples The IBM Cognos BI samples illustrate product features and technical and business best practices using data from a fictitious company. Cognos Content Database is provided to help you quickly set up a test or proof-of-concept system. Do not use Cognos Content Database for the content store in a production environment. and is not installed by default. If you install Cognos Content Database. Extracting data for scorecarding . Open XML and WSDL. The Sample Outdoors Company. Accessing multiple data sources . It is a selectable installation component. and for troubleshooting. Modeling components include the following tools: Creating a business view of your data . Modeling components Modeling components model data within data sources to structure and present data in a way that is meaningful to users. providing a single. Apache Derby is open source software whose license terms can be found on the Apache Derby web site. and improves performance when querying data from different data sources.Metric Designer Metric Designer is the modeling tool used to create extracts for use in IBM Cognos BI scorecarding applications. Java Database Connectivity (JDBC). Any modifications that you make to the Apache Derby database are at your own risk.

4. Secured IBM Cognos BI PowerCubes are not compatible with IBM Cognos Series 7. published models. Import and manage maps .IBM Cognos Transformer IBM Cognos Transformer is the IBM Cognos BI modeling tool used to create PowerCubes for use in IBM Cognos BI. such as report specifications. see the IBM Cognos Insight Installation and Configuration Guide. see the IBM Cognos Map Manager Installation and User Guide. This software allows multiple users to download and install IBM Cognos Insight on their computers from the IBM Cognos Connection interface. you can analyze data. Use the IBM Cognos Connection Installer for Cognos Insight to install provisioning software on Cognos BI servers.1: Installation and Configuration Guide . see the documentation provided with your edition of Transformer. Multidimensional modeling . 14 IBM Cognos Business Intelligence Version 10.iqd) files. Series 7 IQD Bridge The Series 7 IQD Bridge contains the connection information that IBM Cognos BI requires to use IBM Cognos Series 7 Impromptu IQD data sources and IBM Cognos BI Framework Manager externalized queries in IBM Cognos Transformer. Cognos Insight is provided with IBM Cognos BI. you can also use these workspaces to gather and consolidate management targets.Map Manager IBM Cognos Map Manager is a Window-based utility that administrators and modelers use to import maps and update labels for maps in Report Studio. Content store The content store is a relational database that contains data that your IBM Cognos BI product needs to operate. commitments.2. and influence decisions by creating personal or managed workspaces. For more information. and the packages that contain them. For information about installing and configuring versions of Transformer that are earlier than 8. explore scenarios. For more information. and forecasts. Because Cognos Insight supports write-back. administrators and modelers can define alternative names to provide multilingual versions of text that appears on the map. For map features such as country or region and city names.from existing metadata sources such as IBM Cognos Framework Manager and Impromptu® Query Definition (. Required database components In addition to the tools that are provided. It also supports the multi-processing setting in Series 7 models that are imported into IBM Cognos Transformer. IBM Cognos Business Intelligence requires the following components that are created using other resources. IBM Cognos Insight In IBM Cognos Insight. Use these interactive workspaces to communicate results to managers. connection information for data sources.

IBM Cognos PowerPlay® supports PowerCube data sources. The IBM Cognos service that uses the content store is named Content Manager. one metric store may contain content for a sales application and another metric store may contain content for a finance application. When you are ready to set up a production environment with your IBM Cognos BI product. Data sources Data sources. are relational databases.information about the external namespace. such as user preferences. or other physical data stores that can be accessed through IBM Cognos BI. that you can use to get your product running quickly in a test or proof-of-concept system. IBM WebSphere Application Server provides a secure and scalable application infrastructure for the IBM Cognos service-oriented architecture (SOA). IBM WebSphere Application Server IBM WebSphere Application Server can be used for the IBM Cognos BI report server components (Application Tier Components) and Content Manager. see the IBM Cognos Business Intelligence Administration and Security Guide. also known as query databases. For more information. dimensional or OLAP cubes. see the topic about deploying the entire content store in the IBM Cognos Business Intelligence Administration and Security Guide. set up the content store to use a supported database that can be secured and tuned for performance and stability. Metric store A metric store is a relational database that contains content for metric packages. Infrastructure components In addition to the business intelligence software. More than one metric store may be created. Chapter 2. Distribution options 15 . and the Cognos namespace itself. Your IBM Cognos BI product includes an embedded database. The administration portal provides features that you can use to back up and archive the data from Cognos Content Database before moving to the new content store database in your production environment. A metric store also contains Metric Studio settings. some offerings of IBM Cognos Business Intelligence include the following products. and information about scheduling and bursting reports. Design models and log files are not stored in the content store. Application Tier Components use data source connections to access data sources. For example. files. For more information. Scripts are provided to automate the process of creating distinct ports for multiple applications. Cognos Content Database.

the gateway and Web server are on one computer. IBM HTTP Server IBM HTTP Server is a Web server based on a partnership between IBM and the Apache Web server. v Install IBM Cognos BI server components in the same location as other IBM Cognos BI products. and reliability. If you plan to install the IBM Cognos BI reporting and scorecarding components on the same computer. Application Tier Components. availability. Choose this option to maximize performance. and the remaining IBM Cognos components are on other computers. v Install the gateway on a separate computer.IBM Connections IBM Connections is social networking software designed for the workplace. IBM Connections allows you to create and manage activities from IBM Cognos Workspace. v Install Application Tier Components and Content Manager on separate computers. you specify where to place the gateways. Different IBM Cognos BI products share components. install it on the same computer as Content Manager. This type of installation is suitable when you are setting up or customizing an installation in your environment to suit IT and infrastructure requirements. v Consolidate multiple servers by installing on System z IBM Cognos BI is supported for Linux on System z operating system. You may choose this option if you have existing Web servers available to handle IBM Cognos component requests. Cognos Content Database is automatically configured for use as your content store. This conserves resources such as disk space and memory consumption by services. install them in the same installation location. In this option. capacity. such as the Content Manager. This option is typically used for a demonstration or in a proof of concept environment. scalability. v Install components on 64-bit systems 16 IBM Cognos Business Intelligence Version 10. or security based on the processing characteristics of your organization.2. If you plan to install Cognos Content Database. IBM DB2 Universal Database IBM DB2 Universal Database provides the content store for your IBM Cognos BI data. Distributing components When you install IBM Cognos BI server components. and Content Manager.1: Installation and Configuration Guide . You can install these components using any of these options: v Install all components on one computer. DB2 provides industry leading performance. Scripts are provided to automate the process of creating and configuring a new content store. for example.

the single computer must also be running a Web server. Application Tier Components. because you must install the Microsoft Windows operating system-based Framework Manager on a separate computer that runs on Windows.Some IBM Cognos BI components are available for 64-bit systems. the metadata modeling application for business intelligence. Figure 1. the modeling and building tool for creating PowerCubes for use with IBM Cognos BI. No matter which IBM Cognos installation scenario you follow. and Framework Manager are located on separate computers. Distribution options 17 . you must then v configure your Web server to host IBM Cognos Web content Chapter 2. Single computer installation of all three server components Configuration requirements If you install all server components for IBM Cognos BI reporting on the same computer. you must install Framework Manager. and gateway components. you can install all modeling components in separate locations. After installing IBM Cognos BI server components. Because the gateway must be located with the Web server. you must configure them so they can communicate with each other. Choose this scenario for proof of concept or demonstration environments where the user load is small. The content store. In addition to installing the Content Manager. query databases. All server components on one computer You can install all the IBM Cognos BI server components on one computer. all server components are installed on one computer. 32-bit and 64-bit components must be in separate directories. Whether you are installing all server components together on a single server or on multiple servers. A single-computer installation is not possible on UNIX or Linux operating systems. You can also choose to install Transformer. In the following diagram.

It can reside on one or more Web servers. two Web servers each have a gateway installed.2. Incoming requests are passed to either gateway and forwarded to the Application Tier Components computer. This separation of processing may be required if you have a firewall between the Web server and your Application Tier Components computers. you may want to install a gateway on each Web server.v specify connection information to the content store v set up an email account for notifications (if you intend to email reports) Gateways on separate computers The gateway passes queries from the Web server and clients to the dispatcher. If you have a Web farm. In the following diagram. and install the remaining IBM Cognos BI reporting components on other computers. If you install only the gateway component on the same computer as the Web server. your Web server manages the core Web services and does not process user requests. You can install the gateway and a Web server on one computer.1: Installation and Configuration Guide . On each computer where the gateway is installed you must v configure your Web server to host IBM Cognos Web content v configure the Dispatcher URIs 18 IBM Cognos Business Intelligence Version 10. you must ensure that you can view IBM Cognos content and that the gateways can communicate with other IBM Cognos components. Installation with two gateways Configuration requirements If you install one or more gateways on separate computers. Using multiple Web servers to manage incoming requests provides a better level of service. Figure 2.

availability. When an active Content Manager fails. For failover support. One becomes active only if a failure occurs that affects the active Content Manager computer. For example. information about the external namespace and the Cognos namespace itself. Install multiple Content Managers Content Manager stores data that IBM Cognos BI needs to operate. and the packages that use them. Installing on different computers can improve performance. users may be prompted to logon. packages. folders. Chapter 2. schedule jobs. published models. Because the computer has failed. the gateway passes the request to the dispatcher (not shown). connection information for data sources. and capacity. and render reports. the request is redirected to the standby Content Manager computer. results. you may want Content Manager in your data tier instead of in the applications tier.Application Tier Components and Content Managers on separate computers Application Tier Components use the IBM Cognos Connection interface to balance loads. and jobs in the content store. which became active when the default active Content Manager computer failed. In the following diagram. Content Manager stores all report specifications. More than one Content Manager You can install any number of installations of Content Manager. You may choose to install Content Manager separately from the Application Tier Components. There is only one content store for each IBM Cognos installation. unsaved session data is lost. perform queries. which passes it to the default active Content Manager computer. You can install the Application Tier Components and Content Manager on the same computer. The other installations each act as a standby Content Manager. access data. When the new active Content Manager takes over. and information about scheduling and bursting reports. The content store is a relational database management system (RDBMS). such as report specifications. it is advisable to install Content Manager on two or more computers. Distribution options 19 . or on different computers. although only one is active at any time.

Distributing index services To distribute the index services for index search. you distribute and balance loads among the computers. with the index search service enabled.2. with the index search service and index update service enabled. you must v specify connection information to the content store v v v v specify the Dispatcher URIs specify all Content Manager URIs specify the Dispatcher URI for external applications set up a connection to an email account for notifications (if you want to email reports) More than one Application Tier Components computer To improve scalability in an environment in which there is typically a large volume of report requests to process. By installing the Application Tier Components on multiple computers. Installation with an active and a standby Content Manager Configuration requirements On each computer where you install Content Manager. Also. with the index data service enabled. install one instance of Application Tier Components in the applications tier. Example .1: Installation and Configuration Guide . you can install the Application Tier Components on multiple computers dedicated to processing incoming requests. and the index data services in the data tier. You also have better accessibility and throughput than on a single computer. Install addition Application Tier Components in the application tier as needed.Figure 3. The following diagram shows the index search service and index update service in the applications tier. as well as failover support. install an instance of Application Tier Components in the data tier. 20 IBM Cognos Business Intelligence Version 10.

and you should install the IBM Cognos BI gateway component for each product into the same location on the same computer. If you integrate different IBM Cognos BI products. Distributed index services Configuration requirements If you install one or more Application Tier Components on a separate computer. do the following: v specify all Content Manager URIs v specify the Dispatcher URIs v specify the Dispatcher URI for external applications IBM Cognos BI products on the same computer IBM Cognos BI products are designed to share components. including the gateway. This ensures that all the product documentation is available to all users. you can either use the same gateway or use separate gateways. to ensure that they can communicate with other IBM Cognos BI reporting components. If you want to use separate gateways for each product. you can install the IBM Cognos BI gateway component for each product on separate computers. yet still be able to access documentation for all components. Consolidate servers for Linux on System z Linux on System z operating system is a native implementation of the Linux operating system. If you want users to access each IBM Cognos BI product through separate gateways. Content Manager. Hosting options include running Linux in one or more logical partitions (LPAR). Chapter 2. and IBM Cognos Configuration. it is not reinstalled. all gateway components must be of the same product version.Figure 4. install them in the same installation location. The installation program checks to determine whether other IBM Cognos BI components exist in the installation location. content store. Accessing product documentation in an integrated environment The documentation for IBM Cognos BI components is installed with the gateway component. but the product documentation on each gateway will be specific for the IBM Cognos BI product you installed. If you install more than one IBM Cognos BI product on the same computer. If a component exists and can be shared. If you want to use the same gateway. Distribution options 21 . you can install each product's gateway component into the same location as your other IBM Cognos BI gateway components. IBM Cognos Connection.

The horizontal scalability in a large Linux environment is limited by the number of LPARs that can be created.Integrated facility for Linux (IFL) IFLs are System z processors dedicated to running Linux operating system workloads either natively. IFLs enable you to consolidate and centrally manage Linux resources on System z. Installing 64-bit versions of IBM Cognos BI products Some IBM Cognos BI components are available for 64-bit systems. depending on your needs. and those images will each be using a large amount of processing power. the 32-bit and 64-bit components must be in separate directories. Running Linux in LPARs may be best if you are running a small number of Linux images. Gateway) 22 IBM Cognos Business Intelligence Version 10. Default paths for 64-bit installations For a 64-bit Installation on Microsoft Windows operating systems UNIX operating systems Linux operating systems Default path C:\Program Files\IBM\Cognos\c10_64 /usr/IBM/cognos/c10_64 /opt/IBM/cognos/c10_64 /usr/IBM/cognos/c10 /opt/IBM/cognos/c10 Whether you are installing all server components together on a single server or on multiple servers. the components must be installed in the appropriate directories. or will require a very large amount of dedicated memory. Logical partition (LPAR) mode Linux operating system can run in LPARs and communicate with other Linux partitions using TCP/IP connections. or under virtualization software. When installing on a 64-bit system. ensure that you start from the appropriate download directory or disk: v IBM Cognos BI Server and IBM Cognos PowerPlay (Content Manager. Default paths for 32-bit installations For a 32-bit Installation on Microsoft Windows operating systems Default path C:\Program Files\IBM\Cognos\c10 64-bit Microsoft Windows operating systems C:\Program Files (x86)\IBM\Cognos\c10 UNIX operating systems Linux operating systems Table 4.2. This ensures that the images will not have underutilized resources allocated to them. When installing the components. Server components that can be installed together in the c10_64 directory The following components can be installed together on one 64-bit server or installed separately on multiple 64-bit servers. The default installation directory that is used by the IBM Cognos BI components depends on the version that you install. Application Tier Components.1: Installation and Configuration Guide . Table 3.

Chapter 2.v IBM Cognos BI Supplementary Language Documentation (32-bit and 64-bit versions available on one disk) v IBM Cognos BI Samples (32-bit and 64-bit versions available on one disk) Components that must be installed to a separate directory than the 64-bit components The following components can be installed together on the 64-bit server. as shown in the following diagram. By default. is provided in both 32. included with the Application Tier Components. Reports from packages that do not use dynamic query mode will not run using the 64-bit report server. and have one using the 32-bit version of report server and the other using the 64-bit version. even on a 64-bit computer. The 32-bit mode allows you to run reports from all packages. the report server component. For example. but they must be installed to a separate directory from the 64-bit components. In 32-bit installations. They can also be installed on a separate 32-bit system: v Framework Manager (Windows only) v IBM Cognos PowerPlay Client (Windows only) v IBM Cognos Transformer (UNIX and Linux utility for building PowerCubes) v IBM Cognos Transformer (Windows modeling tool) v IBM Cognos BI for Microsoft Office (Windows only) Using the 64-bit version of Report Server In the 64-bit installations. Selecting which version you use is done using IBM Cognos Configuration after installation. you must have a 32-bit report server running in your environment. while the 64-bit server components are installed to the Program Files directory. Distribution options 23 . For example.and 64-bit versions. the report server component is set to use the 32-bit mode. the default installation location for these components is the Program Files (x86) directory on a 64-bit Windows computer. whereas the 64-bit mode allows you to run only reports created from packages using dynamic query mode. only the 32-bit version of the report server component is provided. For packages that are not using dynamic query mode. you can install two Application Tier Components in your environment.

for example Framework Manager.2.1: Installation and Configuration Guide . Firewall considerations When the modeling tool is outside a network firewall that protects the Application Tier Components. A modeling tool that is outside a network firewall. Metric Designer. cannot send requests across a network firewall to the dispatcher on the IBM Cognos BI application server. you must have privileges to create data sources and publish packages in IBM Cognos Connection.Figure 5. install the modeling tool in the same architectural tier as the Application Tier Components. To avoid communication issues when communicating across a network firewall. communication issues with the dispatcher can occur. successfully communicating with the dispatcher on the IBM Cognos BI application server. Installation options for Windows modeling components You install the modeling tools. Distribution option for using the 64-bit version of Report Server You can control which servers your reports are run on using routing rules for the packages. you must configure the modeling tools to use a dispatcher. see the Administration and Security Guide. and Transformer on Microsoft Windows operating system computers. For security reasons. The following diagram shows the Framework Manager computer inside the network firewall. the default IBM Cognos BI configuration prevents the dispatcher from accepting requests from the modeling tool when it is outside the network firewall. 24 IBM Cognos Business Intelligence Version 10. such as Framework Manager. To publish packages so that they are available to users. If IBM Cognos Connection is secured. either directly or through a gateway. For more information about setting routing rules.

you can install an additional gateway that is dedicated to communication with the modeling tool as shown in the following diagram. Client computer outside of firewall Alternatively. Distribution options 25 . You then configure the modeling tool and its gateway such that the dispatcher accepts requests from the modeling tool.Figure 6. Chapter 2.

Distributing Transformer components Transformer can be installed on a computer that contains other IBM Cognos BI components or on a computer that is separate from other IBM Cognos BI 26 IBM Cognos Business Intelligence Version 10. you must configure Framework Manager to communicate with the dispatcher. which can be installed on one or more application servers. configure the following environment properties: v v Gateway URI Dispatcher URI for external applications If the modeling tool is using a dedicated gateway instead of communicating directly with the dispatcher. Client computer outside of firewall Distributing Framework Manager components Framework Manager communicates with the Application Tier Components. you must also configure the Dispatcher URIs for gateway property on the dedicated gateway computer.Figure 7.1: Installation and Configuration Guide . To publish packages. either directly or through a dedicated gateway.2. Configuration requirements On the computer where Framework Manager is installed.

You may have one or both. you can use data sources that are external to IBM Cognos BI and you cannot create secured views with dimensional filtering. set appropriate environment variables for UNIX and Linux servers. and then use the models to build the PowerCubes. When you use Transformer with other IBM Cognos BI components. It can also be used to build and publish PowerCubes. When installed separately.components. such as published packages. For more information about building and updating production PowerCubes. depending on your environment. In this scenario. v For data source connectivity. You install Transformer PowerCube building components for Linux on System z. consider the following requirements: v Database client software is installed on any computer where Transformer will be used to build PowerCubes or test data sources. You can enable such users to be self-sufficient within the IT and security infrastructure of the organization by meeting the following requirements: Chapter 2. Query Studio reports. v IBM Cognos BI servers have access to the location where PowerCubes are stored so that the report server can access the PowerCubes. Supported features When you use Transformer as a standalone product. and Report Studio reports You cannot use flat files as data sources. you can use the following features provided by IBM Cognos BI: v IBM Cognos BI authentication providers v IBM Cognos BI data sources. see the Transformer User Guide. You first design the models using Transformer Windows or MDL scripting. Business analysts or specialists You may have specialized business or power users who want to build PowerCubes that are modeled on a combination of corporate and personal data sources. Building and updating production PowerCubes can be scripted and run remotely when sufficient access and user privileges are set up. v Transformer on UNIX or Linux This is a command line utility for building PowerCubes on UNIX and Linux operating systems. These users may want to do their own analysis of the data for their line of business or a small group of users. v Transformer on Windows This is the modeling tool for Microsoft Windows operating system for designing PowerCubes that are used in IBM Cognos BI. Transformer can be used as a standalone product or it can be configured to communicate with other IBM Cognos BI components. Transformer consists of the following components. Distribution options 27 . v IBM Cognos Connection for publishing the PowerCube data source and package v building PowerCubes Role-based server considerations You may want to set up dedicated Transformer servers for optimal cube build performance and accessibility to the IBM Cognos BI users.

For more information. you must also configure the Dispatcher URIs for gateway property on the dedicated gateway computer. IBM Cognos Transformer creates and manages metadata for PowerCubes. Distributing Metric Designer components For Metric Studio. “Data Sources and Transformer” on page 205 The IBM Cognos BI modeling tools create and manage metadata. Commonly. Framework Manager packages. v Modelers must have privileges to create a data source in IBM Cognos Administration. Modelers can also use automated methods to build PowerCubes. They can create and update data sources by using Transformer or command line tools. on the Transformer computers that are used to access IBM Cognos BI data sources or IBM Cognos Series 7 IQD data sources. modelers should have FTP privileges to transfer models and execute privileges to build cubes on that server. You can provide modelers with a secured folder in IBM Cognos Connection in which to publish PowerCube packages. configure the following environment properties: v Gateway URI v Dispatcher URI for external applications If the modeling tool is using a dedicated gateway instead of communicating directly with the dispatcher. see the Administration and Security Guide. install Metric Designer to extract the data.2. If IBM Cognos Connection is secured. Because metadata is derived from data sources in multi-platform or multilingual environments. v To build PowerCubes on a specific Transformer server. either directly or through a dedicated gateway. On the computer where Transformer is installed. these things depend on the other technology you use for your data or import source. This location must also be accessible to the IBM Cognos service and can be a secured share on a LAN.1: Installation and Configuration Guide . Configuration requirements To publish PowerCube packages. there are several things you must think about or do when you set up the data source environment for IBM Cognos Transformer. or available for modelers to install.iqd files). including cubes. or Impromptu Query Definitions (. Modelers do not need direct access to IBM Cognos Administration. v Modelers must have access to a location in which to store the PowerCube after building it. Modelers can transfer models and execute cube builds using scripts.v Database client software is installed. 28 IBM Cognos Business Intelligence Version 10. you must have privileges to create data sources and publish packages in IBM Cognos Connection. you must configure Transformer to communicate with the dispatcher. Related concepts: “Install IBM Cognos Transformer” on page 200 You install Transformer if you plan to create PowerCubes for use with IBM Cognos BI. if you want to define and load metrics from relational and dimensional data sources.

see “Configure a Metrics Manager only Application Tier Components instance” on page 155. However. Chapter 2. or if you installed IBM Cognos BI on a different computer. You can install these components using any of these options: v Install all components on one computer. Distribution options 29 .Install Metric Designer after installing and configuring other IBM Cognos BI components. Distributing IBM Cognos BI scorecarding components When you install IBM Cognos BI Metrics Manager. and Content Manager. In this option. the metadata modeling tool for IBM Cognos Metrics Manager. On the computer where Metric Designer is installed. which can be installed on one or more application servers. If the modeling tool is using a dedicated gateway instead of communicating directly with the dispatcher. configure the following environment properties: v Gateway URI v Dispatcher URI for external applications Additional configuration is required after you install Metric Designer so that it can access some types of data sources. the gateway and Web server are on one computer. Configuration requirements Metric Designer communicates with the Application Tier Components. Default settings are used for the configuration. All required files are copied to one computer. you must configure Metric Designer to communicate with the dispatcher. This option is typically used for a demonstration or in a proof of concept environment. Application Tier Components. you can use a dedicated server for your Metrics Manager Application Tier Components. v Install the gateway on a separate computer. you must also configure the Dispatcher URIs for gateway property on the dedicated gateway computer. Related concepts: “Installing and Configuring Metric Designer” on page 192 You can install Metric Designer. you may want to change these default settings if existing conditions make the default choices inappropriate. You must install the Microsoft Windows operating system-based Metric Designer on a Windows computer. To publish extracts. either directly or through a dedicated gateway. you specify where to place the gateways. You may choose this option if you have existing Web servers available to handle IBM Cognos component requests. If you are installing Metrics Manager with your BI reporting components. The scorecarding components can be distributed in much the same way as the reporting components. You must ensure that Metric Designer can communicate with other IBM Cognos BI scorecarding components. on the same computer as IBM Cognos BI components. and the remaining IBM Cognos components are on other computers. or on a different computer. For more information.

If both products are accessed through the same gateway. v Server A . The fourth server hosts the common gateway. The result may be that your reports will display an error. Application Tier Components. After IBM Cognos BI is installed. you may choose to install Metric Designer. No matter which IBM Cognos installation scenario you follow.IBM Cognos Business Intelligence v Server B . the metadata modeling application for scorecarding. where each server hosts one product. Cognos Content Database is automatically configured for use as your content store.IBM Cognos PowerPlay v Server D .the Web server used for all products 30 IBM Cognos Business Intelligence Version 10. such as the report service and the presentation service.2. or security based on the processing characteristics of your organization. If you are using multiple products. you can install Metric Designer and the content store on a computer separate from the Application Tier Components. Both products have a reports service and a presentation service. If you plan to install Cognos Content Database. install it on the same computer as Content Manager. The installation wizard for IBM Cognos BI can recognize compatible directories and shows a warning when conflicts occur. you must configure them so they can communicate with each other. If you plan to install IBM Cognos BI scorecarding components on the same computer as other IBM Cognos BI products. such as IBM Cognos Business Intelligence with IBM Cognos Metrics Manager or IBM Cognos PowerPlay.1: Installation and Configuration Guide . you can access objects that are created in another IBM Cognos product in IBM Cognos BI. such as Content Manager.v Install Application Tier Components and Content Manager on separate computers. IBM Cognos Business Intelligence with other IBM Cognos products You can install IBM Cognos BI in an environment that includes other IBM Cognos products. reports that must be run on the IBM Cognos BI services could be routed to the IBM Cognos PowerPlay services. you have IBM Cognos Business Intelligence and IBM Cognos PowerPlay installed. you must ensure that you disable some of the duplicated services to ensure your products work properly. Choose this option to maximize performance. The following list shows an example of distributing components using three servers. capacity. and gateway components. IBM Cognos BI products share components.IBM Cognos Metrics Manager v Server C . Duplicated Services if Using Multiple Products Many IBM Cognos products use similar services. The requirements for access depend on how you choose to run the two products. install them in the same installation location. In addition to installing the Content Manager. After installing IBM Cognos BI scorecarding components. For example. v Install IBM Cognos BI scorecarding components on the same computer as other IBM Cognos BI products. availability.

content stores.1. Cognos Metrics Manager To use data store content from IBM Cognos Metrics Manager in IBM Cognos BI. you can continue to run the earlier versions concurrently on the same computer until you are satisfied with the transition to IBM Cognos BI. these services are not present. and cookie settings. Distribution options 31 . installing IBM Cognos BI. When you upgrade these products to IBM Cognos BI. Web aliases. see the chapter about Chapter 2. you must disable the report service and the presentation service. configuration is required only to select new ports and a new content store for IBM Cognos BI. the content store is upgraded to use the IBM Cognos BI schema and cannot be used by previous versions. you must have the report service and the presentation service enabled. 2. On Server D. You can maintain both content stores using one of the following approaches: v create a copy of the ReportNet content store database using database export utilities and use the copy with IBM Cognos BI v use the embedded export feature in IBM Cognos Connection to export the ReportNet content store database and import the exported deployment into IBM Cognos BI You can upgrade reports at the same time or upgrade them later if compatibility is required with some existing Software Development Kit applications. IBM Cognos Metrics Manager. you upgrade by exporting the content from the data store to flat files. On Server A. When you upgrade to IBM Cognos BI. Note that the cube picker feature (the ability to map specific metrics to cube intersections) in IBM Cognos Metrics Manager is not available in other IBM Cognos BI studios. IBM Cognos products that can be upgraded to IBM Cognos Business Intelligence The following IBM Cognos products are earlier versions of components that are now within IBM Cognos BI ReportNet. 3. Therefore. On Server B and Server C. You cannot use content from ReportNet directly in IBM Cognos BI until you upgrade ReportNet. you need to maintain both the old and new content stores to run both product versions. Cognos DecisionStream You can continue to run IBM Cognos DecisionStream Series 7 concurrently with IBM Cognos BI products. each version must have unique ports. Cognos ReportNet For ReportNet and IBM Cognos BI to run concurrently. Catalogs that are created using DecisionStream Series 7 must be upgraded before you can use them with Data Manager. and IBM Cognos PowerPlay Web. IBM Cognos DecisionStream. and then importing the flat files into the IBM Cognos BI metric store. If you use the default settings. For instructions about running concurrently and upgrading DecisionStream catalogs to the IBM Cognos BI Data Manager environment.

1. You can publish from PowerPlay Enterprise Server to IBM Cognos BI. IBM Cognos Series 7 products that can be migrated to IBM Cognos Business Intelligence You can migrate metadata and applications from IBM Cognos Series 7 to IBM Cognos BI.2. After completing the catalog migration process. You can use these tools to migrate to IBM Cognos Business Intelligence version 10. Impromptu You can migrate Impromptu catalogs and reports to IBM Cognos BI. The last release of the migration tools was version 10. You can also upgrade the following reports to IBM Cognos BI reports by using IBM Cognos Migration Assistant: v PowerPlay Windows reports v PowerPlay Web Explorer reports v PowerPlay for Excel reports v PowerPlay for Windows reports published to PowerPlay Web The tools are available at the IBM Cognos Customer Center (http:// www. You can also drill through between PowerPlay Web and IBM Cognos BI. The migration process maps the Upfront content structure to an IBM Cognos Connection folder structure.com/software/data/cognos/customercenter).1.ibm.1 (Report Studio or Analysis Studio).0. 32 IBM Cognos Business Intelligence Version 10.1. see the IBM Cognos Customer Center (http://www.com/software/data/support/cognos_crc.0. Impromptu client reports and catalogs from Windows.upgrading a catalog in the IBM Cognos Data Manager User Guide. provided that you use the same host name or IP address to identify the Series 7 namespace in IBM Cognos Series 7 and in IBM Cognos BI. you can migrate and deploy Impromptu reports. Content that can be migrated includes Architect models from Windows. You can also use the migration tools to migrate Series 7 PowerPlay content to IBM Cognos BI PowerPlayversion 10. Upfront content. Cognos PowerPlay Web You can continue to use PowerPlay Web reports within the PowerPlay 7 user interfaces in the IBM Cognos BI portal. it is easier to complete administrative tasks.2. and then upgrade the migrated content to IBM Cognos BI version 10. Architect You can migrate Architect models for use as a metadata source for Framework Manager. For a list of supported IBM Cognos Series 7 versions and to download IBM Cognos Migration Assistant tools and documentation. and Web-based content from Windows and UNIX.html). By preserving the existing Upfront organization. You use migrated catalogs as a metadata source for Framework Manager. such as applying security to the migrated content.2. Upfront You can migrate Upfront content to IBM Cognos BI.ibm.1: Installation and Configuration Guide .

You cannot migrate Impromptu query definition files (. With other products. Distribution options 33 . Before you migrate Impromptu Web Reports you must migrate the Impromptu catalog metadata used by the reports. With some products.3 MR1 or later. If you want to use this product with the IBM Cognos BI server. you must ensure that both products are the same version.3 MR1 or later. You cannot install IBM Cognos Planning in the same path as 64-bit IBM Cognos BI.Contributor 7. Series 7 IQD Bridge. you can access the different types of cubes or reports in the IBM Cognos BI portal.iqd files to build cubes in IBM Cognos BI Transformer 8.4. which is available to install with IBM Cognos BI on IBM Cognos Series 7 supported platforms. you must install the optional component.3 MR1 release or later. For more information. see the IBM Cognos Analyst User Guide.Analyst You can access published plan data in IBM Cognos BI by using the Generate Framework Manager Model wizard. To do so.Contributor 7. you can access unique features in the IBM Cognos BI portal.Contributor Data Server component that is included with IBM Cognos Planning . but you can continue to use existing . to IBM Cognos BI. You migrate Impromptu Web Reports content using an IBM Cognos Series 7 Deployment Manager package as the migration source. you must ensure that both products are the same version.Contributor You can access unpublished (real-time) Contributor cubes in IBM Cognos BI by custom installing the IBM Cognos BI .Impromptu Web Reports You can migrate Impromptu Web Reports content. You can access published plan data in IBM Cognos BI by using the Generate Framework Manager Model administration extension in Contributor. You can use these products in the same environment as IBM Cognos BI. but you can implement similar functionality using either the built-in administrator functionality or the IBM Cognos Software Development Kit. For more information. which requires IBM Cognos Planning Analyst 7. which requires IBM Cognos Planning . Chapter 2. see the IBM Cognos Contributor Administration Guide. PowerPrompts are not migrated. If you want to use this product with the IBM Cognos BI server. such as schedules and events. Cognos Planning . Cognos Planning .iqd). IBM Cognos products that interoperate with IBM Cognos Business Intelligence Some IBM Cognos products provide functionality that is not available in IBM Cognos BI.

and publish directly to IBM Cognos Connection. optimize the cubes for use in IBM Cognos BI by using the pcoptimizer utility. You can publish single PowerCube data sources and packages to IBM Cognos Connection interactively in Transformer or in the command line.3 or later directly in IBM Cognos BI. Otherwise. You can also access published Controller data and structures in Framework Manager for custom reporting and analysis. If you want to use this product with the IBM Cognos BI server. You can also export data and metadata from IBM Cognos Finance for use in Framework Manager. which is supplied with IBM Cognos BI. You can run reports and analyses in IBM Cognos BI against the IBM Cognos PowerCubes. You can publish PowerCubes using Transformer 8.4. This allows you to use IBM Cognos BI data sources (such as published packages). the IBM Cognos Series 7 namespace must be configured in IBM Cognos BI and the name ID that is used to configure it in IBM Cognos BI must match the name used in IBM Cognos Series 7. Cognos Controller You can access IBM Cognos BI to create IBM Cognos Controller Standard Reports by using a predefined Framework Manager model that is created when IBM Cognos Controller is installed. For more information about upgrading IBM Cognos Series 7 secured PowerCubes. Before you load the model. you can upgrade IBM Cognos Series 7.4 and does not require access to the model or data source. Cognos Transformer You can use IBM Cognos PowerCubes and Transformer models that were generated by Transformer 7. The MDC file must be in a secured location that the IBM Cognos BI dispatcher and 34 IBM Cognos Business Intelligence Version 10. If you want to use the new integration features of Transformer with IBM Cognos BI. For more information about optimizing PowerCubes.1: Installation and Configuration Guide .4 or later. list reports authored in Query Studio or Report Studio. PowerCubes that were created with previous versions of Transformer may take too long to open in the IBM Cognos BI Web studios. authenticate using IBM Cognos BI security. A user who has privileges to create data sources and packages in IBM Cognos Connection can publish PowerCubes in IBM Cognos Connection as well.2. you must ensure that both products are the same version. Framework Manager.x Transformer models to IBM Cognos BI Transformer 8. or directly in the IBM Cognos BI portal. The cubes and models are upwards compatible and require no migration or upgrade tools. For IBM Cognos Series 7 PowerCubes to be used in IBM Cognos BI. see the IBM Cognos Business Intelligence Transformer User Guide. It is not necessary to run this command line utility for cubes created in Transformer 8. This optimization utility is suitable for older PowerCubes created before Transformer 8.Cognos Finance You can access IBM Cognos Finance cubes that are secured against a Series 7 namespace by using the IBM Cognos Finance Network API Service. see the Transformer User Guide. You can also publish silently using batch scripts after building a PowerCube.4 or later.

you can use the Data Movement Service to run builds and JobStreams in IBM Cognos Connection. Report Studio. When Data Manager is installed in your IBM Cognos BI environment.1 MR3 or MR4 and earlier versions of IBM Cognos BI to newer versions of IBM Cognos BI. Distribution options 35 . Some IBM Cognos Analytic Application components are available for installation on 64-bit systems. and workspaces created in IBM Cognos Workspace on a mobile device (such as a Blackberry) or a tablet computer. view. Chapter 2. and interact with reports. packages that describe the data available in the data warehouse. The default installation directories for 64-bit installations are different from the default installation directories for 32-bit installations. Cognos Data Manager Data Manager is used to create data warehouses and data repositories for reporting.the report server process can access. Cognos Analytic Applications IBM Cognos Analytic Applications is a performance management solution that includes a populated data warehouse. 32-bit and 64-bit components must be in separate directories. require the download of a native client or require the installation of a rich client. You must install the Data Manager engine in the same location as your IBM Cognos BI Application Tier Components. you can access reports authored with Analysis Studio. Cognos Lifecycle Manager Lifecycle Manager is a Windows-based application for auditing upgrades from ReportNet 1. IBM Cognos Analytic Applications Workbench is a performance management solution that includes sample business intelligence data with which you can build applications and documentation source files which you can modify to produce your own customized documentation for the product. Both IBM Cognos Mobile and IBM Cognos BI server must be at the same version. analysis. For a successful conversion. IBM Cognos Mobile devices are either web-based. For more information. Query Studio. It provides a verification feature that validates. and a set of predefined reports. IBM Cognos Series 7 PowerCubes must be created with a system locale set to match the data in the PowerCube. Cognos Mobile With IBM Cognos Mobile. see the IBM Cognos Mobile Installation and Administration Guide. If you use an IBM Cognos Series 7 PowerCube as a data source. and performance management. To download. IBM Cognos BI converts the cube data from the encoding that was used on the system where the PowerCube was created. Packages that use multiple PowerCubes from different PowerCube definitions or PowerCubes mixed with other data sources must be published using Framework Manager. in addition to the installation of IBM Cognos BI components on the server. Both Data Manager and IBM Cognos BI must be the same version. Whether you are installing all server components together on a single server or on multiple servers.

Lifecycle Manager also automates much of the process of bundling the required files.1. see the IBM Cognos Business Intelligence Installation and Configuration Guide. accountability within a collaborative process. For more information. 36 IBM Cognos Business Intelligence Version 10. and then upgrade the migrated content to IBM Cognos BI version 10. see the IBM Cognos Lifecycle Manager User Guide. User interface design and status reporting functionality provide both a proven practice process and support for upgrade project planning and status reporting. visualizations. For more information. Cognos BI Business Viewpoint Studio IBM Cognos BI Business Viewpoint Studio helps to provide you with one version of the truth for dimensions used in an enterprise's performance management processes. You can use these tools to migrate to IBM Cognos Business Intelligence version 10. performance measurement and operational data to enable companies to optimize business effectiveness and customer interaction regardless of geography or structure. workflow-oriented business process to manage both manual and automated changes to all data related to how enterprises analyze and manage their business. This helps to identify upgrade and compatibility issues between releases. IBM Cognos Series 7 content that can be recreated in IBM Cognos Business Intelligence Some IBM Cognos products cannot be programmatically migrated with the migration tools for IBM Cognos BI. allowing managers to quickly stabilize operational fluctuations and take advantage of new opportunities. or objects.1.1 (Report Studio or Analysis Studio). This enhances system performance and extends IBM Cognos product scalability by reducing the size of the Content Store. Cognos TM1 IBM Cognos TM1 integrates business planning. Cognos Content Archival With IBM Cognos Content Archival. such as reports and models. you have a controlled.2. IBM Cognos Content Archival supports an IBM FileNet® Content Manager with IBM FileNet CMIS external repository. see the IBM Cognos TM1 User Guide. Cognos TM1 provides immediate visibility into data.executes. IBM Cognos BI offers two options for duplicating content or functionality for the products described: use the Upfront portal within the IBM Cognos BI portal or use IBM Cognos BI studios to duplicate queries. With Business Viewpoint Studio. you can store report output versions and their source report specifications to an external content archival repository. for the test case.1. and a consistent view of information. The last release of the migration tools was version 10. and compares report results from two different IBM Cognos BI releases. collaborative. while helping to adhere to strict regulatory requirements. For more information. Both IBM Cognos BI Business Viewpoint Studio and IBM Cognos BI must be at the same version.0.2.1: Installation and Configuration Guide .

Cognos NoticeCast You can duplicate alert and notification functionality by using Event Studio and other IBM Cognos BI components. and formatting options in Report Studio and Analysis Studio. Chapter 2. Foundation queries are available in IBM Cognos BI when you migrate an Architect model to Framework Manager. layout.Cognos Query You can use IBM Cognos Migration Assistant to identify IBM Cognos Query objects in the IBM Cognos Series 7 migration source. Cognos Visualizer You can duplicate some functionality by using the charting. CognosScript You can duplicate automation functionality using the IBM Cognos Software Development Kit. Cognos Portal Services You can duplicate most IBM Cognos Portal Services functionality using IBM Cognos Connection. You can then duplicate most IBM Cognos Query functionality in IBM Cognos BI. Cognos Web Services You can duplicate most IBM Cognos Web Services functionality using the IBM Cognos Software Development Kit. You can also manually replicate saved queries using SQL components in Report Studio. Distribution options 37 .

38 IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide .

configure Web browsers.Chapter 3. Configure a user or network server account for IBM Cognos BI. it is important to be aware of all issues that may affect your installation strategy.ibm. A database is created during the installation and IBM Cognos BI is configured to use it. and use only the supported versions of third-party software. 2013 39 . Review the Release Notes before you install your product. apply all minimum required operating system patches. Verify system requirements. Preparing to install Before you install IBM Cognos Business Intelligence. If you want to use Cognos Content Database as your content store. Review supported environments To ensure that your product works properly. After you complete these tasks. The Release Notes contains late-breaking information about known issues. __ v Configure Web browsers. continue with Installing IBM Cognos BI Components on One Computer or Installing IBM Cognos BI Server Components on Different Computers.com/ software/data/cognos/customercenter/). and create a user account for IBM Cognos BI. For example. Review the Release Notes Before You Install Before you install your IBM Cognos product. Set up environment variables on UNIX operating system for the metric store. © Copyright IBM Corp. you must set up resources in your environment so that the components can operate. To review an up-to-date list of environments that are supported by IBM Cognos Business Intelligence products. including information on operating systems. There may be late-breaking issues that were not known when this installation guide was created. Use the following checklist to guide you through the setup process: __ v __ v __ v __ v __ v __ v __ v Review the Release Notes. and documentation updates and deprecation notices. Review the default port settings. 2005. if using IBM Cognos BI Metrics Manager. you do not have to create a database or set up a database client. The Release Notes are available from the first page of the installation wizard or from the product disc. you must create a database for the content store. Create the database for the content store. Review supported environments. Release Notes updates are also available on the IBM Cognos Customer Center (http://www.

Additional resources may be required for distributed or production environments. Ensure that the combination of the operating system and hardware that you are using is supported.5 GB of free space is required to install the software and 4 GB of free space on the drive that contains the temporary directory used by IBM Cognos components. browsers.html) describes IBM support for virtualization environments. Verify system requirements Use the following tables to check the minimum hardware and software requirements to install and run IBM Cognos Business Intelligence components on one computer. Unless otherwise indicated. Hardware requirements Table 5. see the IBM Software Compatibility reports (www. database servers.boulder.patches. For all databases.com/infocenter/prodguid/v1r0/clarity/ vesForProduct. Ensure that you have sufficient disk space for future requirements. directory servers. IBM Cognos products are compatible with later versions of patches and service packs from the versions stated. the size will increase over time. Hardware requirements for a single computer installation Requirement Operating system Specification Microsoft Windows UNIX Linux Some IBM Cognos BI components are not supported on Linux. RAM Operating system specifications Disk space For more information.wss?uid=swg27037784).1: Installation and Configuration Guide . File descriptor limit set to 2048 on UNIX and Linux A minimum of 3.ibm.com/software/support/ virtualization_policy. and application servers. The following table lists the hardware requirements and specifications for a single computer installation.html). Cognos products and virtualization environments The IBM virtualization policy (www.2. see “Memory settings” on page 42. For more information.ibm.com/support/ docview. search supported server virtualization environments by product (publib. 40 IBM Cognos Business Intelligence Version 10. web servers. It is important to note that the Linux operating system is available in a number of distributions and supports a number of hardware platforms.ibm.

Table 5. Software requirements for a single computer installation Requirement Web server Java Runtime Environment (JRE) Specification A Web server must be installed and started. Database Cognos Content Database can be installed and configured as the default content store database in a test or proof-of-concept system. You must have one of the following databases available to store IBM Cognos data in a production environment: v Oracle v DB2 v Microsoft SQL Server v Sybase v Informix For IBM Cognos BI Metrics Manager. Preparing to install 41 . Adobe Reader requires that you configure at least one printer on the computer where you install the Application Tier Components. An IBM JRE is installed automatically with IBM Cognos BI on Windows. Other Software requirements The following table lists the software requirements and specifications for a single computer installation. Table 6. the following databases are supported for the metric store: v Oracle v DB2 v Microsoft SQL Server TCP/IP connectivity is required for all database types. Chapter 3. are sent as temporary PDF files to Adobe Reader for printing. If you are using an application server. if it is supported in IBM Cognos BI. regardless of the print format that you choose. All reports. the system requires the ability to use and access a mail server. use the JRE that is installed with it. Hardware requirements for a single computer installation (continued) Requirement Printer Specification To ensure that reports print properly on Windows. To email reports.

SAP BW The following SAP Front-End components installed on each IBM Cognos BI server computer: v SAP GUI v BW Add-ons Memory settings Memory settings depend on many factors. and acceptable response times. Software requirements for a single computer installation (continued) Requirement Web browser Specification For all Web browsers. Use the following memory settings as a starting point and adjust them based on the memory usage of your system.com/software/analytics/cognos/services/). If your environment supports more than 100 named users.Table 6. the complexity of the IBM Cognos applications. back up. such as antivirus. and enterprise management software v v v v v 4 GB for a 64-bit Content Manager JVM 4 GB for a 64-bit Application Tier JVM 2 GB for the graphics JVM (IBM Cognos Workspace) 2-4 GB for the query service (dynamic query mode) JVM 1 GB per core for the report services processes (dynamic query mode) (JVM) v 2 GB per core for the report services processes (compatible query mode) (BIBuS) The following table shows the suggested memory settings by architectural tier for a 64-bit operating system. v 2 GB for the base operating system and accompanying software. To determine the settings that are best suited for your environment. or includes any combination of these factors.1: Installation and Configuration Guide . the number of users and requests. is complex. consider completing a capacity plan. the following must be enabled: v Run ActiveX controls and plug-ins v Script ActiveX controls marked safe for scripting v Active scripting v Allow META REFRESH For Microsoft Internet Explorer version 10. the following must be enabled: v cookies v JavaScript For Microsoft Internet Explorer only. 42 IBM Cognos Business Intelligence Version 10.ibm. experiences high peak usage periods. ensure that Automatically recover from page layout errors with Compatibility Mode is enabled on the Advanced tab of Internet Option. such as the level of activity expected on the server.2. For more information. performance testing is advised. see IBM Software Services for Cognos (www.

ibm.jsp?topic= %2Fcom. and you want to use the NIST SP800-131a security standard.security. Ensure that the JRE version is supported by IBM Cognos products. Preparing to install 43 . To be compliant with this security standard.java.boulder. you may also have to install the unrestricted Java Cryptography Extension (JCE) policy file. Cryptographic standards By default. Depending on your security policy requirements. see the IBM Java Information Center (publib.Table 7. the JRE files that are provided with the installation are used. IBM Cognos BI is configured to support the NIST SP800-131a security standard. For more information about this security standard. If you are using another JRE. For more information about the supported Java versions for IBM Cognos BI. You can use an existing Java Runtime Environment (JRE) or the JRE that is provided with IBM Cognos BI. On Microsoft Windows operating systems. JAVA_HOME Set a JAVA_HOME environment variable if: v You are installing on a UNIX or Linux operating systems.ibm.com/support/ docview.html). Java requirements To support the cryptographic services in IBM Cognos Business Intelligence. if you do not have a JAVA_HOME variable.ibm. if you are installing IBM Cognos BI on WebSphere Application Server. you must ensure that the JRE supports the standard. Chapter 3.doc%2Fsecurity-component%2Fjsse2Docs %2Fsp800-131a. see the IBM Software Compatibility reports (www. The JRE that is provided for installations on Microsoft Windows operating system does support this standard. you may be required to update your version of Java or set a JAVA_HOME environment variable.component. For example. you must use a JRE that also supports this standard. v You are installing on Microsoft Windows operating systems and you want to use your own Java or a Java bundled with other software. Suggested memory settings by architectural tier Architectural Tier IBM Cognos Gateway Tier IBM Cognos Application Tier (compatible query mode) IBM Cognos Application Tier (dynamic query mode IBM Cognos Content Manager Tier Memory settings 2 GB 2 GB per core 4 GB + 1 GB per core 4 GB More resources might be required when installing additional software.wss?uid=swg27037784).com/infocenter/java7sdk/v7r0/index.

The non-SSL and SSL connectors are automatically updated in the server. You can directly update the shutdown port using IBM Cognos Configuration. For Java that is provided by IBM. you can use the configuration tool to change the settings. You can also change them by editing the cogstartup.cgi http://localhost:9300/ p2pd/servlet/dispatch http://localhost:9300/ p2pd/servlet/dispatch Description The URI to Content Manager The URI to the gateway Dispatcher URI (Internal. the unrestricted JCE policy file is available on the IBM website (https://www14. Dispatcher URIs for Gateway http://localhost:9300/ p2pd/servlet/dispatch/ext Log server port Listening port number 9362 1527 Default Port Settings for Tomcat The following table lists the default settings used by IBM Cognos BI for Tomcat.To verify that your JRE is supported. External) Dispatcher URI for external applications The URI to the dispatcher The URI to the dispatcher The URI to the primary dispatcher used by the gateway The port used by the local log server The port used by Cognos Content Database. go to the IBM Software Compatibility reports (www. Review the Default Port Settings for IBM Cognos Business Intelligence After installation.wss?uid=swg27037784). you can download and install the unrestricted JCE policy file. Click the link for your version of Cognos BI and locate the Java Run Time Libraries information.xml file when you use IBM Cognos Configuration to change the dispatcher port or to enable the SSL protocol. Table 8.com/support/docview.1: Installation and Configuration Guide . Default Port Settings for IBM Cognos BI Components Setting Content Manager URI Gateway URI Default Value http://localhost:9300/ p2pd/servlet http://localhost:80/ ibmcognos/cgi-bin/ cognos.do?source=jcesdk). Unrestricted JCE Policy File JREs include a restricted policy file that limits you to certain cryptographic algorithms and cipher suites.com/webapp/iwm/web/ preLogin.2.ibm.software. If you require a wider range of cryptographic algorithms and cipher suites than are shown in IBM Cognos Configuration. Default Port Settings for IBM Cognos BI Components The following table lists the default ports and URI settings for IBM Cognos Business Intelligence. 44 IBM Cognos Business Intelligence Version 10.ibm.xml file.

Chapter 3.1 connector Shutdown port Port 9300 9334 9399 Description The port Tomcat uses to pass requests from the Web server to IBM Cognos BI The port Tomcat uses to listen for secure connections The port Tomcat uses to listen for a shutdown command Guidelines for creating the content store The content store is a database that Content Manager uses to store global configuration data. Do not use Cognos Content Database for the content store in a production environment. Design models and log files are not stored in the content store. You must use one of the supported enterprise-level databases as the content store in a production environment. For more information. Table 10. Default Port Settings for Tomcat Setting Non-SSL Coyote HTTP/ 1. Cognos Content Database is provided to help you quickly set up a test or proof-of-concept system. global settings (such as the language and currency formats shown in the user interface). Character encoding and protocols for the content store database Database DB2 Oracle Microsoft SQL Server Informix Sybase Cognos Content Database Character encoding UTF-8 AL32UTF8 or AL32UTF16 UTF-8 or UTF-16 UTF-8 UTF-8 preconfigured Protocol TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP preconfigured If you plan to use the Cognos Content Database as your content store. Preparing to install 45 . You must create the content store before you can use your IBM Cognos Business Intelligence product. you can generate a DDL to allow your database administrator to create a DB2 database suitable for the content store. The following table shows the character encoding and protocol that is used by the different types of databases. Database properties You must create the content store database using one of the databases listed in the following table. a database is created and preconfigured when the installation is complete. see “Generating a script file to create a database for a DB2 content store” on page 81. connections to data sources. If you are using IBM DB2 for your content store. and product-specific content.Table 9.1 Connector SSL Coyote HTTP/1.

To ensure a successful installation. which are as shown in the following table. compare. whether the collation is case sensitive. Environment variables for DB2 Environment variable DB2PATH Description The top-level directory that contains the database client software or the entire database installation. you may have to change the library files or change the order in which the library files are listed so that IBM Cognos BI server can find the correct files. see the database documentation. For more information about collation and collation sequences. IBM Cognos BI requires 32-bit library files when running in a 32-bit application server and it requires 64-bit library files when running in a 64-bit application server. 46 IBM Cognos Business Intelligence Version 10. For example. or greater than the letter B. Library files for DB2 Ensure that you use the appropriate library files for the version of the IBM Cognos Business Intelligence server that you install.2. use the following guidelines when creating the content store. and whether the collation is accent sensitive. Table 11. Suggested settings for creating the content store in DB2 on Linux. and UNIX operating systems The database you create on the Microsoft Windows.Collation sequence Cognos BI uses a single sort order that specifies the rules used by the database to interpret. collect.1: Installation and Configuration Guide . or UNIX operating system for the content store must contain the specified configuration settings. Linux. a sort order defines whether the letter A is less than. Guidelines for creating the content store Use the following checklist to help you set up the content store on DB2. and present character data. v Set the appropriate environment variables for DB2. Depending on the version of DB2 that installed. Whichever version of library files is needed must be listed first. equal to. Use the same guidelines to create a database for log messages. Windows.

Lock timeout (locktimeout) Chapter 3. v Ensure that you set the configuration parameters as shown in the following table. using the command-line interface. Table 12. To check that your database has the correct code set. 240 seconds Do not set this to an infinite timeout value. Environment variables for DB2 (continued) Environment variable LD_LIBRARY_PATH Description The load library path. For example (replace the double hash symbol with the library file value. and type the following at the command prompt: db2 get database configuration for database_name The code set value is UTF-8 and the code page value is 1208. see the DB2 documentation.Table 11. Configuration parameters for DB2 Property Application heap size (applheapsz) Setting AUTOMATIC or at least 1024 KB If the application heap size value is too small. LD_LIBRARY_PATH= $DB2_location/sqllib/lib##: $LD_LIBRARY_PATH Examples (replace ## with 32 or 64 as appropriate): 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 DB2CODEPAGE The default database server connection. v Use UTF-8 as the code set value when you create the database. either 32-bit or 64-bit). For information about whether to use this environment variable. You must add the driver location and indicate the 32-bit or 64-bit library files as appropriate for your application server. Preparing to install 47 . out of memory errors may occur when there are many users. Setting this optional environment variable to a value of 1208 provides support for multilingual databases.

v Grant the following database privileges for the user account IBM Cognos BI 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 use both at the same time. use a different user account for each content store to ensure that each IBM Cognos BI instance is fully isolated from the other./home/db2user/sqllib/db2profile fi v Your database administrator must back up IBM Cognos BI databases regularly because they contain the IBM Cognos data. then .Table 12. Suggested settings for creating the content store in DB2 on z/OS The database you create for the content store must contain the specified configuration settings. Configuration parameters for DB2 (continued) Property DB2 registry variable (DB2_INLIST_TO_NLJN) Setting YES Setting this variable to YES improves performance. v Create a system temporary tablespace using the 32 KB buffer pool you created in the previous step. create an additional regular user tablespace with a page size of 8 KB. For example. v Create a user temporary tablespace using the 4 KB buffer pool you created. use the following guidelines when creating the content store. Use the following checklist to help you set up the content store in DB2 on z/OS®. and ensure the user has create. To ensure the security and integrity of databases. and alter permissions for the schema. protect them from unauthorized or inappropriate access. v Create a schema for the user account IBM Cognos BI that you will use to access the database. v Ensure that the user account has use privileges for the user temporary tablespace and other appropriate tablespaces associated with the database.2. 48 IBM Cognos Business Intelligence Version 10. To ensure a successful installation. drop. and a second one with a page size of 4 KB. If you are also creating a logging database. the content of your profile will be similar to the following: if [ -f /home/db2user/sqllib/db2profile ]. v Create a buffer pool with a page size of 32 KB. v Create a profile that sources the sqllib/db2profile from the DB2 user's home directory.1: Installation and Configuration Guide . Global temporary tables will be created in the user temporary tablespace. v Create a regular user tablespace using the 4 KB buffer pool you created.

value. see the Oracle documentation. Use the same guidelines to create a database for log messages.0. and sequences – Create and alter tables – Insert. v Administrators must run a script to create table spaces to hold Large Objects and other data for the content store and grant user rights to the table spaces. and drop triggers. v Determine which user account is to access the database. alter. storage group. use a different user account for each content store to ensure that each IBM Cognos Business Intelligence instance is fully isolated from the others. description FROM v$parameter WHERE name=’compatible’. IBM Cognos Business Intelligence uses the credentials of the user account to communicate with the database server. To ensure the security and integrity of the content store database. and delete data in the database tables Chapter 3. v Ensure that you reserve a buffer pool with a page size of 32 KB. you can check the COMPATIBLE initialization parameter setting by issuing the following SQL statement: SELECT name. For information about changing an instance configuration parameter. use the following guidelines when creating the content store. protect it from unauthorized or inappropriate access. procedures. Tip: If you want to host more than one content store on your Oracle instance and you will use both at the same time.1 or higher.v Log on to the z/OS system as a user with System Administrator (SYSADM) or System Control (SYSCTRL) privileges in DB2 to create the database. see “Creating tablespaces for a content store on DB2 for z/OS” on page 82. v Determine if the database is Unicode. Suggested settings for creating the content store in Oracle The database you create for the content store must contain the specified configuration settings. and a second one with a page size of 4 KB for the database instance. 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. For information about running the script. To ensure a successful installation. Use the following list to help you set up the content store on Oracle. v Ensure that the user account that accesses the database has permission to do the following: – Connect to the database – Create. For example. v Your database administrator must back up the content store regularly because it contains the IBM Cognos data application and security information. views. v Ensure that the parameter for the database instance compatibility level of the content store database is set to 9. Preparing to install 49 . and a user account for the content store. update. create a new database and specify AL32UTF8 for the database character set parameters. v Create a database instance.

the database that you create will also use Windows authentication. specify the new login that you created for the user account. select the new schema. protect them from unauthorized or inappropriate access. during the Microsoft SQL Server setup. you choose a collation. and db_ddladmin. v Ensure that the collation sequence is case-insensitive. 50 IBM Cognos Business Intelligence Version 10. v Under Security for the new database. 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. create a new database under Databases. – For Role Members. use Microsoft SQL Server authentication. create a new login under Security and use the following settings: – Select SQL Server authentication. Use the following checklist to help you set up the content store on Microsoft SQL Server. Use the same guidelines to create a database for log messages. – For Default schema. db_datawriter. use a different user account for each content store to ensure that each IBM Cognos Business Intelligence instance is fully isolated from the others. To ensure a successful installation. – For Owned Schemas. create a new user with the following settings: – For Login name. v For Microsoft SQL Server 2008.1: Installation and Configuration Guide .v Your database administrator must back up IBM Cognos BI databases regularly because they contain the Cognos data. use the following guidelines when creating the content store. create a new schema and assign a name to it. In this situation. Suggested settings for creating the content store in Microsoft SQL Server The database you create for the content store must contain the specified configuration settings. v For the content store database. v When connecting to Microsoft SQL Server Management Studio to create the database. In a Custom installation. the installation uses the locale identified by the installation program for the collation.2. specify the new schema. v Under Security for the new database. To ensure the security and integrity of databases. If you connect using Microsoft Windows operating system authentication. Suggested settings for creating the content store in IBM Informix Dynamic Server The database that you create for the content store must contain specific configuration settings. grant EXECUTE permission to the user account that accesses the database. – Clear the Enforce password policy check box. In a Typical installation. v For the user account that will be used to access the database. select db_datareader. which includes character sets and sort order. This setting cannot be changed later. you must configure the database connection using a database type of SQL Server database (Windows Authentication) in IBM Cognos Configuration.

Use the following checklist to help you set up the content store on the IBM Informix Dynamic Server database. This tool sets up the communication between the JDBC driver and the Sybase Adaptive Server instance. use the following guidelines when creating the content store. Use the same guidelines to create a database for log messages. Information about the new database will be stored in the new database device. v Create a database in mode ANSI and with logging turned on. Keep a backup of the database device for recovery purposes. Preparing to install 51 . name the property CMSCRIPT_CS_ID. create a server instance with an 8 KB server page size. v For the user account that you use to access the database. For multiple content store databases.utf8. For multiple logging databases. Suggested settings for creating the content store in Sybase The database you create for the content store must contain the specified configuration settings. You must also define the user account in each instance of the IBM Cognos Configuration application by creating an advanced property parameter and specifying the user account as the value. v Create a database device. Use the following checklist to help you set up the content store on Sybase. grant the DBA database privilege. v Create the database.To enable International Components for Unicode (ICU) functionality in Informix Dynamic Server.To set the database locale to Unicode. v Set the following environment variables: – GL_USEGLU . Use the same guidelines to create a database for log messages. For instructions. use a different user account for each database.Use the following guidelines when creating the content store. name the property IPFSCRIPTIDX. For instructions. see the Sybase documentation.instance_name. specify en_us. set the value to 1. v If required. install jConnect 6. make UTF-8 the default character set on the server. v In the file ONCONFIG. v On the Sybase server. – DB_LOCALE . v Set the new database device as the default. Tip: Set log_segment to a minimum of 10 MB. To ensure a successful installation. you must download the installer from Sybase's Web site. see the Sybase documentation. v Determine which user account will be used to access the database. Important: If you host more than one database on your Informix instance and use them at the same time. set the property SHMBASE to 0x14000000L. v Add the UTF-8 character set to the server instance. If your version of Sybase does not include JConnect 6. Chapter 3. v If required.

Administrators do not need to manage a password or maintain the account. assign a logon account to the IBM Cognos service. such as printers v have the rights to log on as a service and act as part of the operating system In addition. to print reports using a network printer. for example. You must configure the Web server to use the application pool. create table. use a different user account for each content store to ensure that each IBM Cognos Business Intelligence instance is fully isolated from the others. You can configure the IBM Cognos service to use a special user account by selecting the IBM Cognos service from the list of services shown in the Services window in Windows. Change the group ownership of the IBM Cognos files to the cognos group and change the file permissions for all IBM Cognos files to GROUP READABLE/WRITABLE/EXECUTABLE. v 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 Configure a User Account or Network Service Account for IBM Cognos Business Intelligence You can configure either a user account or a network service account for IBM Cognos Business Intelligence. The user or network service account under which IBM Cognos BI runs must: v have access to all required resources. You can then define the user account properties. For more information.2.Tip: If you want to host more than one content store on your Sybase instance and you will use them at the same time. This group must contain the user that owns the IBM Cognos files. For example. the user account must be a member of the local administrator group. see the topic about configuring the Web server. For more information. Configure a Network Service Account The network service account is the built in account NT AUTHORITY\ NetworkService in the operating system. Use an account with administrator privileges if you are installing on Windows Server 2008. create procedure.1: Installation and Configuration Guide . 52 IBM Cognos Business Intelligence Version 10. see the topic about configuring the Web server. create a new UNIX or Linux group named cognos. create rule. and create view. v Ensure that the user account has the following privileges for the database: create default. For UNIX or Linux operating system. You also need the appropriate write permissions to install to the directory. or you must assign a logon account to the IBM Cognos service. Configure a User Account For Microsoft Windows operating system. You must configure the Web Server to use aliases. the account must have access to the network printer.

see the Oracle documentation. Preparing to install 53 . For Bourne or Korn shells. you must set the database variables by running the environment setup scripts included with the IBM DB2 installation. Contact your database or network administrator for the correct values for your system. Environment variables to use an Oracle 11g metric store Environment variable ORACLE_HOME Description The top level directory that contains the database client software or the entire database installation. the 32-bit libraries are in the ORACLE_HOME/lib32 directory.profile or . For more information. you must set and export the database environment variables for the user of the metric store before you start the IBM Cognos processes. Example: /usr/oracle You might be able to use an Oracle script to create the environment variables. When you set the load library paths. which is usually the ORACLE_HOME/lib directory. Example: /usr/local/bin/coraenv TNS_ADMIN The directory that contains the tnsnames. ensure that the LIBPATH variable includes only the 32-bit libraries. ensure that the 32-bit Oracle libraries are in the library search path.ora file. If you installed the 64-bit Oracle 10g client. IBM Cognos BI uses these database variables to connect to your database. Table 13. which allows calls to the Oracle database to determine the required server connections. Oracle For Oracle databases.login script of the user who starts the IBM Cognos services.profile script: DB2_installation_path/db2profile On AIX. Example: $ORACLE_HOME/network/admin Chapter 3. The default db2profile configures LIBPATH to reference the 64-bit libraries. The proper syntax for creating environment variables is shell dependent. you must specify environment variables on a UNIX operating system before you can use a DB2 or Oracle database as the metric store. The descriptions assume an Oracle 11g client is installed. run the following command or add it to the . IBM DB2 For IBM DB2 databases.Setting up environment variables on UNIX for the metric store For IBM Cognos Business Intelligence. The following table describes environment variables for Oracle databases. One way to set these environment variables is to include these commands in the .

and calendar conventions automatically adapt to the native language and locale. monetary. Examples: For Solaris or Linux operating system: LD_LIBRARY_PATH=$ORACLE_HOME/ lib:$LD_LIBRARY_PATH For AIX: LIBPATH=$ORACLE_HOME/ lib:$LIBPATH For HP-UX: SHLIB_PATH=$ORACLE_HOME/ lib:$SHLIB_PATH NLS_LANG The value of the variable determines the locale-dependent behavior of IBM Cognos BI. Configure Web Browsers IBM Cognos Business Intelligence products use default browser configurations. Contact your database or network administrator for the correct values for your system. numeric. date.2. Example: $PATH:$ORACLE_HOME/bin libraryPATH The load library path. Environment variables to use an Oracle 11g metric store (continued) Environment variable PATH Description The variable to locate executable files. sort order. Additional required settings are specific to the browser. 54 IBM Cognos Business Intelligence Version 10.Table 13. time. Error messages.1: Installation and Configuration Guide .

Preparing to install 55 . Enabled Browser Settings for IBM Cognos BI Portal Browser Internet Explorer (settings for studios and portals) Setting Allow Cookies Active Scripting Allow META REFRESH IBM Cognos component IBM Cognos Connection IBM Cognos Administration Cognos Viewer Report Studio Query Studio Analysis Studio Event Studio Metric Studio IBM Cognos Workspace IBM Cognos Workspace Advanced Internet Explorer (settings for some studios) Run ActiveX controls and plug-ins Report Studio Query Studio Script ActiveX controls marked Analysis Studio safe for scripting Binary and script behaviors Allow programmatic clipboard access Userdata persistence Report Studio Internet Explorer (settings for a single studio) Firefox Allow Cookies Enable Java Enable JavaScript Load Images IBM Cognos Connection IBM Cognos Administration Cognos Viewer Report Studio Query Studio Analysis Studio IBM Cognos Workspace IBM Cognos Workspace Advanced Safari 5 Enable Java Enable JavaScript Do not Block Popup Windows Block Cookies: Never IBM Cognos Connection Cognos Viewer IBM Cognos Workspace Chapter 3. Table 14.Browser Settings Required for IBM Cognos BI Portal The following table shows the settings that must be enabled.

in Internet Explorer. This enables automatic prompting for file downloads.Table 14.2. from the Tools menu. Cookies Used by IBM Cognos BI Components IBM Cognos BI uses the following cookies to store user information. Cookies used by IBM Cognos BI components Cookie AS_TICKET Type Session temporary Purpose Created if IBM Cognos BI is configured to use an IBM Cognos Series 7 namespace Contains security state information caf Session temporary 56 IBM Cognos Business Intelligence Version 10. which is a component of the browser. For example. http:// <server_name>:<port_number>/ibmcognos. IBM Cognos BI does not provide or download ActiveX controls. Table 15. disable it using the per-page option. see “IBM Cognos Application Firewall” on page 230. Adblock Plus prevents some IBM Cognos Connection resources from working properly. To prevent these errors. If Adblock Plus is installed with Firefox.1: Installation and Configuration Guide . and disable Adobe PDF Reader Link Helper. For more information. you may receive Adobe link errors when you open PDF documents in the IBM Cognos portal. Enabled Browser Settings for IBM Cognos BI Portal (continued) Browser Google Chrome Setting IBM Cognos component Cookies: Allow local data to be IBM Cognos Connection set Cognos Viewer Images: Show all images IBM Cognos Workspace JavaScript: Allow all sites to run JavaScript Pop-ups: Allow all sites to show pop-ups Report Studio and Query Studio use the native Microsoft Internet Explorer XML support. then you can add the URL for your gateway(s) to the list of Trusted sites. ActiveX support must be enabled because Microsoft applications implement XML using ActiveX. If you use a Microsoft Internet Explorer Web browser. select Manage Add-ons. If you use Microsoft Internet Explorer Version 8. Only the ActiveX controls that are installed as part of Internet Explorer are enabled through this configuration.

restart the Web browser and advise users to clear their browser cache. and is updated after the Open or Save dialog box is used Stores the settings that the user makes for user interface elements such as menus and toolbars Contains all capabilities and the signature for the current user Contains a unique user session identifier. Preparing to install 57 . valid for the duration of the browser session. copy. Administrators can set the HTTPOnly attribute to block scripts from reading or manipulating the CAM passport cookie during a user's session with their web browser. such as cut. cc_session Session temporary Holds session information that is specific to IBM Cognos Connection Holds information during edit operations. see the IBM Cognos Business Intelligence Administration and Security Guide. and is set for all IBM Cognos users Stores the choice that the user makes for the view members folder in Report Studio Stores the current folder path if local file access is used. cc_state Session temporary CRN Session temporary CRN_RS Persistent PAT_CURRENT_ FOLDER Persistent qs Persistent userCapabilities Session temporary usersessionid Session temporary After upgrading or installing new software. and paste Contains the content and product locale information. Chapter 3. For more information. Cookies used by IBM Cognos BI components (continued) Cookie Cam_passport Type Session temporary Purpose Stores a reference to a user session stored on the Content Manager server.Table 15.

58 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide .2.

ensure that you perform the following tasks: v Gather the necessary information.Chapter 4. For example. 2013 59 . For more information. The following diagram shows a general upgrade workflow and the stages in the upgrade process. and custom configuration settings. Move to your production environment when you are satisfied that the deployed applications meet your business requirements. Assess any differences between the source and target environments. Deployment and testing is usually an iterative process. v Test the upgraded applications to ensure that your reports run as expected. new features. see the Lifecycle Manager documentation. The process includes the following stages: v Creating an upgrade plan.html) provides additional information to help you upgrade. Finally.html) © Copyright IBM Corp. In the planning stage. To ensure success. which includes the following activities: – Reviewing resources. Cognos Upgrade Central website The Cognos Upgrade Central website (http://www. v Assess the applications in your reporting environment and group similar reports together. and requirements for preparing your production environment. v Install the new software in a test environment and deploy the content to the test environment. reports. such as the required inputs and expected outputs for each phase. and adequate resources. 2005. compatibility between versions. Therefore it is best to perform the upgrade in stages. When planning your upgrade. you can then conduct a site survey to identify the BI infrastructure. and each plan follows the same basic upgrade process. adequate time. and links to additional resources are available on the website.ibm.com/software/analytics/ cognos/customercenter/upgrade. When you finish the review. treat upgrading as an IT project that requires careful planning. Upgrade process Every upgrade requires a plan. applications. You can use Lifecycle Manager to compare reports from a different version of IBM Cognos BI. demonstration videos.com/software/analytics/cognos/customercenter/ upgrade. frequently asked questions.ibm. you can review the upgrade documentation for information about expected behavior. You must plan your upgrade so that you know what to expect at each stage of the process. such as documentation and the Cognos Upgrade Central website (www. 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. deprecated features. Upgrade IBM Cognos Business Intelligence The enhancements in new versions of IBM Cognos Business Intelligence (BI) can affect many parts of your business intelligence environment.

ibm. – Creating a detailed plan to implement your upgrade strategy.1: Installation and Configuration Guide .– Verifying the supported environments to ensure compatibility with your other software by going to the IBM Software Compatibility reports (www. v Creating a development or test system with the new version of the product. You may also want to check this page if you are thinking of upgrading your operating system.2. Figure 8. 60 IBM Cognos Business Intelligence Version 10. v Using the information learned from the development or test system and applying it as you create your QA or production systems.wss?uid=swg27037784). Upgrade process Reviewing the documentation Documentation is provided from various sources to help you achieve a successful upgrade.com/support/docview. – Evaluating your existing system to determine what you want to move to your new version of the product.

List of upgrade documentation Document Information to search for IBM Cognos Business Intelligence Release Notes Recent issues that can affect an upgrade IBM Cognos Business Intelligence New Features New features that can affect the behavior of existing content IBM Cognos Framework Manager User Guide IBM Cognos Report Studio User Guide IBM Cognos Transformer User Guide IBM Cognos Migration Assistant User Guide Upgrading models Upgrading reports Upgrading user views and upgrading IBM Cognos Series 7 models Moving content from IBM Cognos Series 7 to IBM Cognos BI.1. and configuration settings. Procedure 1.com/infocenter/cogic/v1r0m0/index.2.ibm. review the latest versions of the documentation listed in the following table. IBM Cognos Lifecycle Manager User Guide Using Lifecycle Manager to audit trial upgrades. The last release of the migration tools was version 10. deprecated. Chapter 4. applications.com/infocenter/ cogic/v1r0m0/index.dhe. you might have many applications in your environment. It contains a list of new. changed. The site survey includes information about the infrastructure. 2. Assess applications in your environment before you upgrade Preparing to upgrade provides an opportunity to review your existing applications and clean up your source environment.1. it is not uncommon to find that a number of applications are not used or no longer meet your requirements. Assessing your applications is a useful exercise because it can reduce the number of applications to consider during an upgrade. Upgrade IBM Cognos Business Intelligence 61 . and removed features for this release.dhe.2. From the IBM Cognos Information Center (http://pic. However. Read the What’s New section in this guide.ibm.jsp). 3. and then upgrade the migrated content to IBM Cognos BI version 10.1 (Report Studio or Analysis Studio). You can use these tools to migrate to IBM Cognos Business Intelligence version 10.All the documentation is available online at the IBM Cognos Information Center (http://pic. users. For example.0.jsp). Read the rest of the Upgrade information in this document. You can also use the migration tools to migrate Series 7 PowerPlay content to IBM Cognos BI PowerPlay version 10.0. Table 16.1. An audit of your existing applications can include the following tasks: v Do a site survey to assess the current production environment and identify areas that require attention during the upgrade.

please contact Customer Support to determine whether the changes are supported in the new version of the software. and unique content store databases. v Complete a detailed assessment of your applications. v Determine whether you must re-create web deployments. and application servers.ibm.v Assess the software that you use in your environment and create a list of the software. which include web archive (. If you changed other configuration files.xml. web servers. Note: If you have modified . webapps. After your audit is complete. To review an up-to-date list of environments that are supported by IBM Cognos Business Intelligence products. patches. This might include . size. age. The total size of the applications can have an impact on the time required to complete the upgrade. and . you can create an upgrade plan. Third-party software would include components. .1: Installation and Configuration Guide .war) files and enterprise archive (.wss?uid=swg27037784). v Ensure that the third-party software that is used by IBM Cognos BI is supported on the proposed operating system version.ear) files. Guidelines when upgrading your operating system You might want to consider the following guidelines before you upgrade to a later version of the operating system on the computers where IBM Cognos BI is installed: v Check the IBM Software Compatibility reports (www. Access content from a previous version in the portal You can view content from a previous version of IBM Cognos BI in the new version by enabling multi-version coexistence. and complexity of your applications are important factors to consider when planning the upgrade. To run the two versions you must ensure that you use unique port numbers. see the IBM Software Compatibility reports (www. web server aliases. and webcontent directories. security providers.2. web servers. and databases. directory servers. v Back up your content store database.css files in the configuration.version supports the version of the operating system you are thinking of moving to. templates.ibm. – Changes to other configuration files You must manually change other configuration files during the upgrade. and browsers.com/support/docview. such as database and database drivers.ini files. you must assess the changes that you want to preserve in the upgraded environment. application servers.wss?uid=swg27037784) to ensure that the IBM Cognos BI. The usage.com/support/ docview. v Determine whether you must recompile IBM Cognos BI SDK applications. 62 IBM Cognos Business Intelligence Version 10. database servers. browsers.txt. including information on operating systems. v List the following information about your configuration: – Configuration settings that you enabled in IBM Cognos Configuration Installing the new version of the product in a different location than the existing version lets you compare the settings between the two version. such as operating systems. web servers.

Upgrade IBM Cognos Business Intelligence 63 . Ports and URI settings If you are using Tomcat. Considerations for running multiple versions or instances of IBM Cognos BI on the same computer To have multiple versions or instances of IBM Cognos Business Intelligence on the same computer you must change the configuration to ensure that the versions do not share port numbers or other resources. Installing to a new location allows you to maintain your existing version of the product and run it in addition to the new version of the product. Install and configure a new version of the product Install the new version of the product to a new location. The configuration settings for each version must use different settings for the following configuration properties. 4. This can help you test your new version without affecting your existing version. Upgrade your report specifications. Compare your upgraded content to your existing content to ensure consistency. Install and configure the new version of the product. you must use different port numbers to avoid port conflicts. You can compare the configuration settings between version and compare the appearance and functionality of the reports in both environments to ensure equivalency. Required configuration changes for running multiple versions on the same computer To run multiple versions of IBM Cognos Business Intelligence on the same computer. 2. Move your content to the new version of the product. see How to access content from previous IBM Cognos release from within the IBM Cognos 10 portal on the IBM website (https://www. Upgrade tasks When you upgrade. 3.wss?uid=swg21459041). you perform the following tasks: 1.ibm. Because IBM Cognos BI reserves a port range. ensure that you use an offset of 100 for the ports. The location can be on the same computer as your existing version of the product or on another computer.Enabling multi-version coexistence can help provide a more seamless experience through the upgrade process by staging the upgrade. The versions or instances must be installed in different directories.com/support/docview. at the same time. provide the flexibility to plan an application upgrade to the capacity of your IT department. Change the following ports. And. v Dispatcher URIs for gateway v External dispatcher URI v Internal dispatcher URI v Dispatcher URI for external applications v Content Manager URIs v Local log server port number v Shutdown port number Chapter 4. For more information. You can provide IT with the ability to address business demands for features in the new version. ensure that each installation is distinct.

The default port numbers for Tomcat start at 9300.xml files. you can troubleshoot Java processes by owner. The system. Application pools (Microsoft IIS web server) If you use cognosisap. Ensure that you update the Gateway URI in Cognos Configuration to reflect the names of the virtual directories. you must change the ibmcognos virtual directory for one of the gateways. Content store Use a different content store or schema for each installation. You can use a restored copy of your existing content store as the content store for the newer version of IBM Cognos Business Intelligence. Configuration settings that are the same for multiple versions on the same server Multiple instances or versions of IBM Cognos Business Intelligence running on the same computer use the same resources. the files can be upgraded by the new version of the product. Web server virtual directories To view static content for IBM Cognos Business Intelligence. the virtual directories for the web server must be different for each version. you can use this automatic upgrade feature instead of reapplying the changes manually after upgrading. By replacing the system. If you are installing the product on an application server other than Tomcat. The IBM Cognos BI presentation service supports automatic upgrade of some system. Multiple versions of IBM Cognos can use the same authentication source for both versions.xml files with those from your earlier version of the product. Keep a record of any customizations to ensure that they can be reapplied after upgrading. For example. The automatic upgrade is applied when you start the IBM Cognos service. You can configure identical properties for the namespace. User account that starts the service (optional) Changing the user account might be helpful when you are troubleshooting. Customized configuration files If you manually edited any configuration files. network. ensure that you install the new version to a new profile or a separate instance than your existing version. each gateway must use a separate application pool. If you made many customization changes to system. such as memory. back up these files so that the original version can be restored if necessary. The newer version of the product upgrades the content store when you start the services.xml files. If you have two gateways installed on the same computer. you must reapply the changes. the default virtual directory is http://servername/ibmcognos. Also. When the content store is upgraded you cannot revert the content.xml files for which automatic upgrade is supported are in the following directories: 64 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide . and disk space.dll. If you are installing another version of the product. For example.2. ensure that you do not use the same values for your second version.

the first time you start your IBM Cognos services. If you are using another application server. Click Logging. update the applications. Important: If you are connecting to a backup of your content store. Chapter 4. 2. 8.xml property matches the port number for the other URI properties. Before you begin For the new version of the product. 3. click Environment. 6. you are prompted to upgrade your reports. If you are using Tomcat as the application server. Upgrade IBM Cognos Business Intelligence 65 . Ensure that you have your new content store database in place before you configure the new version of the product. you must configure each instance with unique values for ports. and content store database. 5.xml file location: v In the Explorer window. ensure that you do not use the same content store that is used for your other instance or version of IBM Cognos BI. click Environment > Portal Services. 7. In the Explorer window. and it is better to upgrade them after you have the new version running. ensure that the port number for the Location of applications. and ensure that the Local log server port number is unique. create a content store from a backup of your existing content store. the web server virtual directory. Procedure 1. v In the Properties window. You can upgrade your reports afterwards using IBM Cognos Administration. If you are using Portal Services. Upgrading your reports can take a long time. Ensure that the Gateway URI uses a different virtual directory or alias than your other instance or version of IBM Cognos BI.v c10_location/templates/ps v c10_location/templates/ps/portal v c10_location/templates/ps/qs Configuring a second instance of IBM Cognos BI on one computer To have more than one instance of IBM Cognos Business Intelligence on one computer. Ensure that the port numbers for the following settings do not conflict with your other instance or version of IBM Cognos BI: v Dispatcher URIs for gateway v External dispatcher URI v Internal dispatcher URI v Dispatcher URI for external applications v Content Manager URIs 4. under Data Access > Content Manager. In the Explorer window. For the new instance of IBM Cognos BI. and ensure that the Shutdown port number is unique. If you are upgrading your entire content store. this value is not used. such as WebSphere. you require a new content store. click IBM Cognos. If you are moving your content with deployment archives you can create a blank content store database. start IBM Cognos Configuration.

you must do so with deployment archives. You can upgrade your reports afterwards using IBM Cognos Administration. and then restore the backup to a new content store. or save report specifications. and start IBM Cognos BI. modify. Upgrading your reports can take a long time.9. you must run a script to upgrade the content store before you start the services in IBM Cognos Configuration. You can do so using IBM Cognos Administration after you have started the services. For example. Upgrade your content store IBM Cognos BI upgrades the content store database to the new version of the product when you start the services for the first time. Also. you are prompted to upgrade your reports. ensure that your applications work as expected in the new version. Important: When you use this method. the first time you start your IBM Cognos services. Connect the new version of the product to the content store that you created from the backup in IBM Cognos Configuration. v You can move content by creating deployment archives. If your content store is on DB2 on z/OS. but it does require a new content store database. you must create deployments to move your content.2. changes can introduce unexpected results. It is important to test your applications with the new version of the product before you move them to your production environment. Additionally. This method lets you move specific content. This method maintains all of your security and user preferences. if you have Software Development Kit applications that create. if you are changing your contents store from Microsoft SQL Server to IBM DB2. The process for upgrading your content store to the new version of the product includes the following steps: 1. you are prompted to upgrade your reports. the first time you start your IBM Cognos services. Start your services. Important: When you use this method. Move your content to the new version of the product There are two methods for moving your content: v You can move your entire content store. Sometimes.1: Installation and Configuration Guide . you must ensure you unregister any dispatchers from your previous version of the product. but it can be time consuming for a large content store. This method requires you to make a backup of your existing content store. 2. Make a backup of your existing content store database. 4. Save the configuration. As part of the upgrade process. Create a database from the backup. and it is better to upgrade them after you have the new version running. do not select the option to upgrade your report specifications. If you are changing content store database vendors. The content store is upgraded during the startup process. and the product upgrades the content store to the new version. Upgrading your 66 IBM Cognos Business Intelligence Version 10. You then connect your new version of the product to the restored content store. 3.

Go to the c10_location\configuration\schemas\content\db2zOS directory and open tablespaceUpgrade_db2zOS. Follow the instructions in the script file to replace the placeholder values in the file with the values for your database. Run the script before you save the configuration for the new version. Click More for the dispatchers belonging to your previous version. click Launch. the content store database is upgraded. Before you begin To run the script. In the upper-right corner. you do not need to move your content using deployment archives. and it is better to upgrade them after you have the new version running. Click Configuration. Moving your content with deployment archives involves the following steps: 1. 4. IBM Cognos Administration. run a script that creates new tablespaces and grants Content Manager the rights to use the tablespaces. Save and run the file.reports can take a long time. and then click OK. and then click Dispatchers and Services. Important: If you have moved your content by restoring your existing content store. Click Unregister. and can no longer be used with your older version of the product. 5. Procedure 1. Important: When you connect the new version of the product to the content store you created from the backup. Deployment archives are compressed files that you can then import into your new version of the product. The dispatcher information is removed from the content store. 2. Creating the archive. Open IBM Cognos Connection in your web browser. Upgrade IBM Cognos Business Intelligence 67 . do not select the option to upgrade your report specifications. 3. if you have Software Development Kit applications that create.sql in a text editor. Procedure 1. 2. you must unregister the dispatchers from your previous version. modify. or save report specifications. you must have permission to create tablespaces. 3. Additionally. Unregister previous version dispatchers from your content store: If you use a backup of your existing content store with a new version of the product. This process lets you use the old and new versions of the product at the same time. Upgrading a content store on IBM DB2 on z/OS: To upgrade the content store on DB2 on z/OS. Chapter 4. where each version has its own content store. You can upgrade your reports afterwards using IBM Cognos Administration. Moving your content with a deployment archive To move specific content from your content store you can use deployment archives.

and schedules and what to do with entries when there is a conflict. Enter Name for the archive. 6. and then click Next: v If you want to make any changes to the package or folder in the target . v Under Options. . Click Next. Select the content you want to include in the archive: v To export specific folders and directory content. and click environment. select the packages or folders that you want to export. f. and then click OK. click Select the entire content store. 2. For each package and folder that you export. If you clicked Select public folders and directory content: a. do the following. 7. enter a password to be used when you import the content. 68 IBM Cognos Business Intelligence Version 10. If you clicked Select the entire content store. and click Next. or create one. 3. on the Configuration tab. On the toolbar. Click the Add icon to the Selected entries box. This is useful when you want to test the reports before you make them available in the target environment. click Add. and click OK. 4. to move the selected items c. and click Next. select the options that you want. v To export the entire content store. On the Select the directory content panel. click the Edit icon OK. On the Select the Public folders content panel. You can browse the Public Folders hierarchy and choose the packages and folders that you want. 5. run history. you can also select Include user account information. If you select the entire content store. click Select public folders and directory content. Procedure 1. b. On the Specify the general options panel. select an existing deployment archive from the list. select the check box in the Disable after import column. make your changes. d. On the Select entries panel. click Content Administration.2. Importing the content.1: Installation and Configuration Guide . e. v To restrict access to the package or folder and its entries. Copying the archive to the new version of the product. On the Specify a deployment archive panel. Creating a deployment archive: Use the following task to create a deployment archive. select the options that you want. select whether you want to include the report output versions.2. In IBM Cognos Administration. in the Available Entries box. click the New Export icon 3.

In the Parameter column. Upgrade IBM Cognos Business Intelligence 69 . Click the dispatcher you want. In the Value column. type the following uppercase text: CM. select Save and run once. the existing deployment archive is overwritten. If the name of the new deployment specification matches the name of an existing deployment archive. Under Actions. click the set properties icon. Note: The deployment directory is configurable in IBM Cognos Configuration. 10. If you are using a different location. 9. the location is install_location/deployment. click Edit. By default. Click OK to finish. 5. Configuration objects include dispatchers and configuration folders used to group dispatchers. Including configuration objects when you import a deployment archive of the entire content store: You can include configuration objects when importing an entire content store. 6. Next to ContentManagerService. Results A deployment archive is created in the deployment directory where you installed IBM Cognos BI.If you are typing a new name for the deployment archive. configuration objects are excluded when you import an entire content store. 3. you might want to import the configuration because you have a series of advanced settings for your services that you want from the source environment. Procedure Copy the deployment archives you created from the old_version_install_location/deployment directory to the new_version_install_location/deployment directory. 8. 4. select Now and click Run. on the Configuration tab. ensure that you copy the deployment archives to the appropriate directory. type true. Procedure 1. even though they are included in the export. Chapter 4. 2. 7. For example. By default.DEPLOYMENTINCLUDECONFIGURATION 8. Review the summary information and click Next. In the Value column. Select the Override the settings acquired from the parent entry check box. click Dispatchers and Services. do not use spaces in the name. Click the Settings tab. In IBM Cognos Administration. 9. On the Run with options panel. Copying the deployment archive to your new version: You must manually copy the deployment archives from the instance where they were created to your new instance.

10. Select Upgrade all report specifications to the latest version if you want to upgrade the report specifications during the import. 5. Upgrade your report specifications Report specifications will have changed from one version of IBM Cognos BI to another. 6.1: Installation and Configuration Guide . If you do a partial deployment of specific public folders and directory content. next to the package if you want to change the Tip: Click the edit icon target location for the imported content. You can also perform this task after you import the content. You can either accept the default options set during the export. On the toolbar.Importing a deployment archive: To import the entries. When you redeploy. 70 IBM Cognos Business Intelligence Version 10. select the options that you want. 2. You must upgrade any report specifications created in previous versions of the product. the import wizard shows whether packages and folders exist in the target environment and the date and time that they were last modified. you select from entries that were exported. On the Specify the general options panel. On the Run with options panel. and click Next. and click Next. and click Next. the wizard also shows whether the packages and folders were in the original deployment. or change them. you create an import deployment specification. Under Actions.2. on the Configuration tab. 3. 8. and click Finish. click the new import icon. If your deployment archive is of your entire content store. select the deployment archive that you want to import. b. in IBM Cognos Administration. Type a name for the import and select the folder where you want to save it. Review the summary information. In the Deployment archive box. Procedure 1. and then click Next. You can select options that were included in the deployment archive during the export. do the following: a. For your new version of the product. click Content Administration. 4. When you import. 7. and click Next. You can use this information to help you decide how to resolve conflicts. 9. select the options. select Save and run once. Click Run. Select the content that you want to include in the import. and click OK. type the password entered during the export. Before you begin Ensure that you have copied the deployment archive to the c10_location/ deployment directory for your new version of the product.

2. modify. For information about upgrading report specifications. Select the packages and locations for the report specification you want to upgrade. 4. or save report specifications. v Save and schedule opens the scheduling tool. Use Lifecycle Manager to compare reports between your versions of the product Lifecycle Manager lets you verify your upgraded content by comparing reports in your old environment with the reports in your new version of the product. Click Next. Choose one of the following: v Save and run once opens the run with options page. Before you begin Important: Do not upgrade your report specifications if you have Software Development Kit applications that create. if you want. If you upgrade report specifications by package. all reports in the folder will be upgraded. Type a name for the upgrade task and. Chapter 4. see the IBM Cognos Lifecycle Manager documentation. 6. Click the arrow on the new content maintenance button and then click New Report Upgrade on the toolbar. v Save only allows you to save the upgrade so that you can run it at a later time. see the IBM Cognos Software Development Kit Developer Guide. On the Configuration tab. Upgrade IBM Cognos Business Intelligence 71 . Open IBM Cognos Connection in your web browser. If you are moving content to a new version using deployment archives. You must first update your Software Development Kit applications to comply with the IBM Cognos report specifications schema. you should upgrade the report specifications after you have started the services. In the upper-right corner. Otherwise. you do not have to do it again. 3. If you upgraded the report specifications during the import. 7. you can choose to upgrade the import specifications during the import. your Software Development Kit applications may not be able to access the upgraded report specifications. all reports in the content store that are based on the model in the package will be upgraded. If you upgrade report specifications by folder. Procedure 1. If you moved your content using deployment archive you may have selected the option to upgrade your report specifications. Click Next. click Content Administration. IBM Cognos Administration. a description and screen tip. 5. click Launch.If you are upgrading from a backup of your existing content store. For more information.

1: Installation and Configuration Guide .2.72 IBM Cognos Business Intelligence Version 10.

you must install components on your server and then configure them to work in your environment. or for small production environments. you run the IBM Cognos installation and configuration programs in interactive mode. you can customize the components for use in your environment by changing other settings in IBM Cognos Configuration. Typically. 2013 73 . 2005. using settings that apply to your environment. Run IBM Cognos Configuration in interactive mode the first time. For more information. and then running the configuration tool in silent mode. For uninstallation instructions. You can choose to install server components in silent mode. see Chapter 6. You can automate the configuration of components by exporting the configuration settings from one computer to another as long as the installed components are the same. an X terminal. This is useful when you are setting up a test or evaluation environment. After installation.” on page 119. This is useful when you are setting up a test or evaluation environment. Interactive Mode Unless you intend to complete a silent-mode installation.” on page 413.xml file. © Copyright IBM Corp. and the configuration tool enables you to change default settings.Chapter 5. Silent Mode You can automate the installation of components using response files and running the installation program in silent mode. or for small production environments. You can install all IBM Cognos PowerPlay components on one computer. You can also distribute the installation on different computers. you must install all components that are selected by default in the installation wizard. “Installing and Configuring Server Components on Different Computers. see Chapter 18. Installing and Configuring Product Components on One Computer You can install all IBM Cognos Business Intelligence components on one computer. “Uninstalling IBM Cognos BI. To use IBM Cognos BI. Install Server Components in Interactive Mode For a complete installation. The other option is to edit the cogstartup. or a PC or other system with X server software installed. This means that in a graphical user interface (GUI) the installer prompts you to provide information. install the software from an X Window System workstation. You can also distribute the installation of IBM Cognos PowerPlay on different computers.

Only the components that you choose to install are copied from the disk to your computer. whether you install on a 64-bit server or a 32-bit server. cannot load a 32-bit compiled library in a 64-bit compiled server. The 32-bit mode allows you to run all reports.” on page 59. Some Web servers. If you install IBM Cognos BI on additional or alternate hosts. If you are upgrading IBM Cognos BI in an environment that includes earlier versions of other IBM Cognos BI products. IBM Cognos BI Planning Version 8. all the distributed components must be the same version of IBM Cognos BI. see Chapter 4.To run an interactive-mode installation. If you are upgrading from an earlier version of IBM Cognos BI. is provided in both 32. If you want to use the samples.x. whereas the 64-bit mode allows you to run only reports created for dynamic query mode. The report server component. After you upgrade the 74 IBM Cognos Business Intelligence Version 10. the report server component is set to use the 32-bit mode. Selecting which version you use is done using IBM Cognos Configuration after installation. Stopping the service If you need to stop the IBM Cognos service. 64-bit installations The IBM Cognos BI gateway provides 32-bit libraries. and Metric Designer v any Software Development Kit applications that are running Upgrading your installation If you are upgrading from a previous release of IBM Cognos PowerPlay. or IBM Cognos BI Analysis for Microsoft Excel Version 8.x. In that situation.1: Installation and Configuration Guide . you must install them from the IBM Cognos Business Intelligence Samples disk. you must update location-specific properties in IBM Cognos Configuration. it is important to also stop the following: v applications that are related to the IBM Cognos service. If you are upgrading from a previous release of IBM Cognos products. IBM Cognos Transformer. install the 32-bit version of the IBM Cognos gateway on a 32-bit Web server. “Upgrade IBM Cognos Business Intelligence. you must use the upgrading steps. such as Apache Web Server. IBM Cognos Connection. By default. install the new version of IBM Cognos BI in a separate location from the other IBM Cognos BI product and configure the new version of IBM Cognos BI to operate independently of that product.x. Application samples for your IBM Cognos BI product are on a separate disk. the console attached to your computer must support a Java-based graphical user interface.and 64-bit versions. even on a 64-bit computer.2. such as Framework Manager. IBM Cognos Administration. included with the Application Tier Components. Install the server components Use the installation wizard to select the server components that you want to install and the location on your computer where you want to install them. such as IBM Cognos BI Controller Version 8.

If you are installing components on several computers. ensure that you have administrator privileges for the Windows computer you are installing on. UNIX installations For UNIX operating system installations. All reports. stop the IBM Cognos service. Adobe Reader requires that you configure at least one printer on the operating system where Application Tier Components are installed. files from the disk are temporarily copied to this directory. Before you begin Go to the IBM Software Compatibility reports (www. regardless of the print format that you choose. IBM Cognos BI respects the file mode creation mask (umask) of the account running the installation program. This affects only the installation directories. Verify that you have the required patches installed on your computer before you install the product. the console attached to your UNIX computer must support a Java-based graphical user interface. To run graphical-mode installation. Chapter 5. you must select it in the installation wizard.wss?uid=swg27037784). you need to only install Cognos Content Database once. Printer requirements To ensure that reports print properly on Windows.other product to a compatible version with IBM Cognos BI. It does not affect the file permissions within the directories. If you are installing to a directory with other IBM Cognos BI components. However. such as logs. are sent as temporary PDF files to Adobe Reader for printing. respect the mask. During installation. Procedure 1. 2. Installing and Configuring Product Components on One Computer 75 . Set the JAVA_HOME environment variable to point to the installation location of your Java Runtime Environment (JRE). Installing server components on UNIX or Linux operating systems Use the installation wizard to select the server components that you want to install and the location on your computer where you want to install them.ibm. Also ensure that your computer has a TEMP system variable that points to the directory where you want to store temporary files. Windows installations For Microsoft Windows operating system installations.com/support/ docview. you can install server components using a graphical user interface or by running a silent installation. Cognos Content Database as content store If you want to use Cognos Content Database as your content store. Only the components that you choose to install are copied from the disk to your computer. Also. run-time generated files. you can then configure the two products to operate together. Use umask 022 on the installation directory.

Follow the directions in the installation wizard and copy the required files to your computer. 76 IBM Cognos Business Intelligence Version 10./issetup Note: When you use the issetup command with XWindows. Japanese characters in messages and log files may be corrupted. To start the installation wizard. For example. to run on Linux operating system. such as the one that is provided by IBM. PATH=/usr/sbin/:$PATH export PATH v To start the required NFS daemons and run the daemons in the background. 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 disk from this drive. use the existing JAVA_HOME environment variable. If you are installing in a location with other IBM Cognos BI components. 7. 4.” on page 407). type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the disk. On HP-UX. If installing from a disk. go to the operating system directory and then type . 6. If you are installing on Linux operating systems. If you do not use XWindows.PCK on Solaris). for example ja_JP. When installing in Japanese on UNIX or Linux. and you receive error messages about missing openmotif libraries. To mount the disk on HP-UX. If installing from a download. set the AIXTHREAD_SCOPE environment variable as follows: AIXTHREAD_SCOPE=S This sets the contention scope for user threads to system-wide. type pfs_mount -t rrip <device><mount_dir> -o xlat=unix For example. IBM Cognos BI requires a JVM. which supports more efficient scheduling of user threads. and then start the installation wizard. go to the location where the installation files were downloaded and extracted.An example of the installation location of a Java Runtime Environment is /directory/java/java_version/jre.1: Installation and Configuration Guide . do the following: v Add the pfs_mount directory in your path. mount the disk using Rock Ridge file extensions. On AIX. if you are using a servlet gateway. 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. first set environment variables LANG=C and LC_ALL=C (where C is the language code. “Using an unattended installation and configuration. 3. 8.2. you can use an unattended installation with the issetupnx command. v When the installation is complete. run an unattended installation (see Chapter 17. 5. type bg pfs_mountd and then type bg pfsd v To mount the drive.

LIBPATH v For HP-UX. Some UNIX and Linux Web servers do not support non-ASCII characters in directory names. LD_LIBRARY_PATH v For AIX. When you are prompted about installing non-English product documentation. 9. you can change the installation directory to something like C:\IBM\cognos\c10. Installing and Configuring Product Components on One Computer 77 .sh in the c10_location/bin64 directory. v If you want to see late-breaking information about the product. Alternatively. Only the components that you choose to install are copied from the disk to your computer. you may receive the following error: [Cryptography] 1.NoClassDefFoundError: javax/net/ServerSocketFactory: Related tasks: “Cannot run issetup on Linux operating systems” on page 470 You run issetup to install IBM Cognos BI but you receive the following error message: Installing server components on Windows operating systems Use the installation wizard to select the server components that you want to install and the location on your computer where you want to install them. you can install the product outside of the Program Files (x86) directory. see “Installing translated product documentation” on page 212. In the Finish page of the installation wizard.lang. ensure that you run IBM Cognos Configuration as an Administrator. click View for the appropriate log file. Windows 7. [ ERROR ] java. v Do not configure IBM Cognos BI immediately because you must do other tasks first to ensure that your environment is properly set up. For example. 11. do the following: v If you want to see the log files. click OK to continue. v Click Finish. For more information. select the check box for IBM Cognos Release Notes. You can later configure IBM Cognos BI using IBM Cognos Configuration by typing cogconfig. 10. If you install to this location. the default installation location uses the Program Files (x86) directory. v For Solaris and Linux. Append the c10_location/bin64 directory to the appropriate library path environment variable. SHLIB_PATH Results If you want users to see product documentation in a language other than English. or Windows 2008 computers. For Windows Vista.Install IBM Cognos BI components in a directory that contains only ASCII characters in the path name. Ensure that the IBM Cognos Configuration check box is clear. you must install the Supplementary Language Documentation component in the location where you installed the Gateway components. You must also update your Java security framework (see “Java requirements” on page 43) before you can configure IBM Cognos BI. Otherwise. Chapter 5.

v Go to the location where the installation files were downloaded and extracted and then double-click issetup. click OK to continue. click View for the appropriate log file. Do one of the following: v Insert the IBM Cognos product disk.Procedure 1. stop the IBM Cognos service. Follow the directions in the installation wizard to copy the required files to your computer.exe. When you are prompted about installing non-English product documentation. and double-click issetup. go to the operating system directory. Install IBM Cognos BI components in a directory that contains only ASCII characters in the path name. 4. select the check box for IBM Cognos Release Notes. If you want to use the samples that are available for IBM Cognos BI. Some Windows Web servers do not support non-ASCII characters in directory names. v Click Finish.2. 6.1: Installation and Configuration Guide . you must install the Supplementary Language Documentation component in the location where you installed the Gateway components. In the Finish page of the installation wizard. install the IBM Cognos BI samples. v If you start IBM Cognos Configuration from the installation wizard. 5. you must install each IBM Cognos Metrics Manager component in the same location as each IBM Cognos Business Intelligence component. 3. Install IBM Cognos Metrics Manager If you are installing IBM Cognos Metrics Manager with IBM Cognos Business Intelligence and you want to share resources. You may also want to install Metric Designer (see “Installing and Configuring Metric Designer” on page 192). You can start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu. If you want users to see product documentation in a language other than English. see “Installing translated product documentation” on page 212. 2. If the installation wizard does not open automatically. For more information. The language that you select determines the language of the user interface. All supported languages are installed.exe. If you are installing in a directory with other IBM Cognos BI components. do the following: v If you want to see the log files. 78 IBM Cognos Business Intelligence Version 10. You can change the user interface to any of the installed languages after installation. Select the language to use for the installation. v If you want to see late-breaking information about the product. ensure that you follow the additional tasks in this section to ensure that your environment is properly set up before you start the services.

open IBM Cognos Configuration. Before you begin Ensure that you do the following tasks before installing a Fix Pack. If a fix pack becomes available after your IBM Cognos product has been deployed. To check your version. redeploy the IBM Cognos product to the application server. update the new installation files with any changes from the backup copies of your customized files. and then start the IBM Cognos service. Installing and Configuring Product Components on One Computer 79 . stop it. v If you are using Tomcat. Return the deployed IBM Cognos product to service. 5. IBM Cognos fix packs are installed in the same location as the existing product. before copying the customized files.Installing fix packs IBM provides interim maintenance packages that contain updates to one or more components in your IBM Cognos product. Fix packs are cumulative. or insert the disc if you have one. If required. compare both versions of the files. Fix packs are available for download from IBM Support at http://www. save the configuration.ibm. type the following command . it includes updates from all the previous fix packs. install the fix pack in the same location as the IBM Cognos components. v Back up the directory structure. Procedure 1. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. Chapter 5. 2. 4. v If the IBM Cognos service is running. open the component list file at c10_location\cmplst./issetup 3. If a fix pack is available when you are installing or upgrading your product. Go to the location where the installation files are downloaded. To prevent errors.com/support/us/en/. Install the fix packs that are appropriate for your product version. This validation determines whether you can replace the file. v Back up the content store database v Back up any files that you manually edited. You must install them on computers that have IBM Cognos components installed. Note: Fix packs are not standalone installations. and then start the service. v If you are running the IBM Cognos product on an application server other than Tomcat. you must install it after you install the IBM Cognos components. To start the installation wizard.txt and check the line that starts with C8BISRVR_version=. you must stop the service. When you install the latest fix pack. Installing IBM Cognos fix packs on UNIX or Linux operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product.

on each computer where you install Content Manager. stop it. Doing this allows Content Manager to access the content store database. before copying the customized files. v Back up the content store database v Back up any files that you manually edited. v If you are running the IBM Cognos product on an application server other than Tomcat. IBMCognos fix packs are installed in the same location as the existing product. It does not require the DB2 client to be installed. 3. 2.2. If you have a distributed environment. v If you are using Tomcat. If required. or both. save the configuration. and double-click the issetup. compare both versions of the files. and then start the IBM Cognos service. v If the IBM Cognos service is running.exe file. 5. open IBM Cognos Configuration. Procedure 1. Installing Fix Packs on Windows operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product.1: Installation and Configuration Guide .6. You must perform this procedure on each computer where you install Content Manager. Set up database connectivity for an IBM DB2 content store This procedure describes how to set up database connectivity for a DB2 content store. repeat these steps for all remaining IBM Cognos servers. 4. redeploy the IBM Cognos product to the application server. To prevent errors. 80 IBM Cognos Business Intelligence Version 10. Before you begin Ensure that you do the following tasks before installing a Fix Pack. you may have to install database client software. repeat these steps for all remaining IBM Cognos servers. Return the deployed IBM Cognos product to service. Set up database connectivity for the content store database If you are using a database other than Cognos Content Database or Microsoft SQL Server as the content store. or Java Database Connectivity (JDBC) drivers. v Back up the directory structure. The type 4 driver is considered an independent product. This validation determines whether you can replace the file. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. update the new installation files with any changes from the backup copies of your customized files. If you have a distributed environment. You must use a type 4 Java Database Connectivity (JDBC) driver to connect to your content store if you are using IBM DB2. Insert the fix pack disk for the Windows operating system or go to the location where you downloaded and extracted the files.

1 fix pack 5 or version 9. Important: Do not use a name longer than eight characters and use only letters. 50000 is the default port number that is used by IBM DB2. For example. 5.jar com. Start IBM Cognos Configuration. run the following command: java -cp path\db2jcc.jar. If you are using a different port number. and click Generate DDL. For more information about using a DDL file. 6. see your IBM DB2 documentation.Procedure Copy the following files from DB2_installation\sqllib\java directory to the c10_location\webapps\p2pd\WEB-INF\lib directory: v The universal driver file. If you use the IBM DB2 command-line interface.db2. click Content Store. Procedure 1. localhost:50000. 4.jar v The license file: For DB2 on Linux. and hyphens in the name.jcc. Installing and Configuring Product Components on One Computer 81 .sql is created. The script is created in the c10_location\configuration\schemas\content\db2 directory. type the name for your content store database. What to do next Use this script to create a database in IBM DB2.sql Chapter 5. For DB2 on z/OS. use the driver version from Linux. Right-click Content Store. 3. for the Database name property. ensure you use that value. Type the appropriate values and click OK. 7.5 fix pack 2. 2. Click the Value field next to the User ID and password property and then click the edit icon. use db2jcc_license_cu. enter the name of your computer and port number on which DB2 is running. or Windows version 9. In the Explorer window. Click Details to record the location of the generated DDL file. use db2jcc_license_cisuz. Ensure that the Type is DB2 database. The script file is called a DDL file. The default configuration is for an IBM DB2 database. UNIX. In the Database server and port number field. db2jcc.ibm. numbers.jar. Where.DB2Jcc -version Generating a script file to create a database for a DB2 content store You can generate a script file to automatically create the content store in IBM DB2 on all platforms. The DDL file named createDB. Tip: To check the driver version. In the Properties window. underscores. you can run the script by entering the following command: db2 -tvf createDB. or Windows operating systems. UNIX. under Data Access > Content Manager. If you are connecting to DB2 on z/OS.

4.sql script file and save the file to another location. Connect to the database as a user that has privileges to create and drop tablespaces and to allow execution of SQL statements. The reason for the exception is that when the two parameters are concatenated the character length can be no more than 8. Add a connection statement to the beginning of the script. and annotations. the content store is used for notifications. The ID must not be longer than 2 characters. 2. You can create separate databases for each. For more information. human tasks.sql script file.1: Installation and Configuration Guide . Parameter names and description for the content store tablespace script Parameter name CMSCRIPT_STOGROUP CMSCRIPT_DATABASE CMSCRIPT_CS_ID Description Specifies the name of the storage group. b. There are two exceptions to the character length limit: v CMSCRIPT_CS_ID is no more than 2 characters. v CMSCRIPT_TABLESPACE is no more than 6 characters. For example. connect to databasename. Go to the directory that contains the scripts: c10_location/configuration/schemas/content/db2zOS 3. Use the following table to help you to replace the generic parameters with ones appropriate for your environment. 82 IBM Cognos Business Intelligence Version 10. see the IBM DB2 Information Center. Table 17. About this task Ensure that you use the naming conventions for DB2 on z/OS.2. Make a backup copy of the tablespace_db2zOS. Open the original tablespace_db2zOS. but some might be added in the future.Creating tablespaces for a content store on DB2 for z/OS A database administrator must run scripts to create a set of tablespaces required for the content store database. all names of parameters must start with a letter and the length must not exceed eight characters. Modify the scripts to replace the placeholder parameters with ones that are appropriate for your environment. Specifies the name of the content store database. Specifies the subsystem identification for the content store database. a. Not all of the parameters listed are in the script. By default. For example. Procedure 1.

In the remote access tool. This bufferpool is the 32 KB buffer pool that was created when the database administrator created the content store database on the z/OS system. Parameter names and description for the content store tablespace script (continued) Parameter name CMSCRIPT_TABLESPACE Description Specifies the name of the tablespace that contains all of the base tables in the content store. d. CMSCRIPT_LARGE_BP Specifies the name of the large buffer pool allocated for especially large objects. go to the c10_location/configuration/ schemas/delivery/zosdb2 directory.sql script file and replace the placeholder parameters with values that are appropriate for your environment. Make a copy of the rightsGrant_db2zOS.sql script file and save the file to another location. For example. if you set up your clp.sql script file and store it in another location. For example. b. Make a backup copy of the NC_TABLESPACES. a. Add a connection statement to the beginning of the script. The name cannot be longer than 6 characters. CMSCRIPT_USERNAME Specifies the user account that accesses the content store database. CMSCRIPT_REGULAR_BP Specifies the name of the regular size buffer pool allocated for regular and large objects. Installing and Configuring Product Components on One Computer 83 . type the following command to run the script: db2 -tvf tablespace_db2zOS.sql 6. Save and then run the script. open the original rightsGrant_db2zOS. Grant the IBM Cognos user rights to the tablespaces that were created when you ran the tablespace_db2zOS. Auxiliary tables are not included.Table 17. This bufferpool is the 16 KB buffer pool that was created when the database administrator created the content store database on the z/OS system.sql 7. Ensure that you use the same values that you used when you allocated resources to the buffer pools and user account. db2 -tvf rightsGrant_db2zOS.sql file script: a. For example. Chapter 5. c. 5. Save and run the script.properties file and your DB2 alias in your profile or tcshrc script file. connect to databasename user username using password. To create the notification tablespaces.

Tablespace parameter names and descriptions for the DB2 notification database on z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the notification database. Specifies name of the 32 k buffer pool. Open the HTS2_CREATE_Db2zos. To create the annotations tablespaces. See the script for a complete list of the parameters required. Save and run the script. Specifies the name of the storage group. Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the database. However. Save and run the script.sql d. Table 20. d. go to the c10_location/configuration/ schemas/hts/zosdb2 directory. Make a backup copy of the HTS_tablespaces. you may choose to run it yourself. e. Table 19. c. Specifies the name of the buffer pool.sql script file and save the file to another location.b. 84 IBM Cognos Business Intelligence Version 10. The Job and Scheduling Monitor services will automatically run the script. db2 -tvf NC_TABLESPACES. Save the script. c. Open the original NC_TABLESPACES. go to the c10_location/configuration/ schemas/ans/zosdb2 directory.2. Not all of the parameters listed are in the script.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. Open the NC_CREATE_DB2. See the script for a complete list of the parameters required.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. To create the human tasks tablespaces.sql script file and replace the NCCOG placeholder parameter with the name of the notification database. Save and run the script. For example. 8. Table 18. e. b.1: Installation and Configuration Guide . Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG Description The name of the database. Open the original HTS_TABLESPACES. 9. Specifies the name of the storage group. but might be added in the future. a.sql script file and use the following table to help you to replace the placeholder parameters with ones appropriate for your environment.

See the script for a complete list of the parameters required. Save and run the script. c. b. and can also be downloaded from the Oracle technology Web site.a. Set up database connectivity for an Informix content store This procedure describes how to set up database connectivity for an Informix content store.jar. The name of the storage group. Table 21. you must have ojdbc14. go to the Informix_location/ sqllib/java directory. Make a backup copy of the ANN_TABLESPACES. Open the original ANN_TABLESPACES.jar. The files are available from an Oracle client or server install. Chapter 5.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment.sql script file and save the file to another location. Table 22. Set up database connectivity for an Oracle content store This procedure describes how to set up database connectivity for an Oracle content store. 2. On the computer where Informix is installed. you must have ojdbc5. If you are using Oracle 11g. go to the ORACLE_HOME/jdbc/lib directory. See the script for a complete list of the parameters required. If you are using Oracle 10g. Open the ANS2_CREATE_Db2zos. The name of the 32 k buffer pool.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. Procedure 1. Copy the correct library file for your version of the Oracle client to the c10_location\webapps\p2pd\WEB-INF\lib directory on the computer where Content Manager is installed and where notification is sent to an Oracle database. e. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG Description The name of the database. You must perform this procedure on each computer where you install Content Manager. d. You must perform this procedure on each computer where you install Content Manager. Procedure 1. Save and run the script. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description The name of the database. Installing and Configuring Product Components on One Computer 85 . On the computer where the Oracle client is installed.

You can use the dynamic query mode with the following OLAP data sources: 86 IBM Cognos Business Intelligence Version 10. If the data source is 64-bit. the required software might include database clients. and IBM Cognos Transformer.jar Set up database connectivity for a Sybase content store This procedure describes how to set up database connectivity for a Sybase content store. For IBM Cognos Business Intelligence.2. v the universal driver file. Java/XMLA connectivity optimizes access by providing customized and enhanced MDX for the specific source and version of your OLAP technology and it harnesses the smarts of the OLAP data source. a type 4 JDBC connection is required.jar file to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed and where notification is sent to a Sybase database. Procedure 1. you must use 32-bit data source client libraries and configure the report server to be 32-bit. Copy the jconn3. A type 4 JDBC driver converts JDBC calls directly into the vendor-specific database protocol. You must perform this procedure on each computer where you install Content Manager. db2jcc_license_cisuz. Set up database connectivity for reporting databases To support communication between IBM Cognos Business Intelligence and the data sources. db2jcc. Metric Designer. Depending on the data source and query mode.1: Installation and Configuration Guide . The compatible query mode uses native client and ODBC connections to communicate with data sources. or both. Compatible query mode To run reports that use the compatible query mode. the query database (also known as the reporting database) is only accessed by the reporting engine that runs reports. The reporting engine is installed with Application Tier Components and is also used by Framework Manager. It is written in pure Java and is platform-independent.2. go to the Sybase_location/ jConnect-6/classes directory. For supported OLAP data sources. For supported relational databases. or Java Database Connectivity (JDBC) driver files.jar v the license file. you must install additional software for your data sources on the same computer that hosts the report server. 2. On the computer where Sybase is installed. ensure that you use the 32-bit client libraries to connect to the data source to use the compatibility query mode. Copy the following files to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed. Dynamic query mode Dynamic query mode provides communication to data sources using Java/XMLA connections.

the connectivity libraries. see the IBM Software Compatibility reports (www. see the IBM Cognos Business Intelligence Dynamic Query Guide.com/support/ docview. To review a list of environments supported by the IBM Cognos Business Intelligence. you must also install the client API software on the computer where Framework Manager is installed. Chapter 5. Access OLAP data sources on Windows operating systems To access the relational databases and OLAP data sources for reporting.odbc.v v v v IBM Cognos TM1 SAP Business Information Warehouse (SAP BW) Oracle Essbase Microsoft Analysis Services You can use the dynamic query mode for OLAP over relational (dimensionally-modeled relational) models with the following relational data sources: v IBM DB2 v IBM DB2 for z/OS v v v v Oracle Microsoft SQL Server Teradata Netezza® For more information about the dynamic query mode. If Framework Manager is installed in a separate location from the Application Tier Components. 2. For more information. the reporting engine supports either native database connectivity or ODBC. and their accompanying Driver Manager libraries. you must configure the environment to locate the .ibm.com/support/docview. Installing and Configuring Product Components on One Computer 87 .ini file which contains the references to data source. The software must be installed on the same computer where the Application Tier Components are installed.wss?uid=swg27037784). Install the database API software for your relational databases and OLAP data sources on the computer that hosts the report server (where Application Tier Components are installed).ibm. including the data source versions supported by the dynamic query mode.wss?uid=swg27037784). you must install the client API software that is provided by your data source vendor. including installing the drivers. IBM Software Compatibility reports (www. Procedure 1. Access ODBC data sources on UNIX or Linux operating systems To use an ODBC data source on UNIX or Linux to connect to a supported data source. To review supported ODBC data sources. see “Set variables for data source connections for Framework Manager” on page 187. On MicrosoftWindows operating systems.

the open source iODBC driver manager is provided as part of the IBM Cognos installation. Procedure 1. In a scenario where one ODBC source validates while another fails based on a dependency. you must create connections to the data sources in IBM Cognos Administration. use the following command: odbcinst --version. Using a common . For example. LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH What to do next If you are using multiple ODBC sources on UNIX or Linux operating systems.ini file. Your library path should already contain the c10_location/bin directory. If your database vendor does not supply a driver manager.After configuring for the ODBC connections. review 88 IBM Cognos Business Intelligence Version 10. v On UNIX. The library files are located in the c10_location/bin directory.1: Installation and Configuration Guide . please contact Customer Support. iODBC is provided as part of the IBM Cognos installation. depending on your operating system.2. and ensure you use that version. The following table lists the environment variables for each operating system that must specify the location of the driver manager libraries. you may encounter dependencies of library files with common names but different implementations for both the connectivity and the driver manager. Environment variables for your operating system Operating system AIX Solaris and Linux HP-UX Environment variable LIBPATH LD_LIBRARY_PATH SHLIB_PATH 3. To verify the version you have installed. If your database vendor does not provide a driver manager. Check which version of unixODBC is required for the database you are using. For example. On UNIX operating systems.11 or later before you can set up data source connections. set the library path to include the path the local driver manager. the unixODBC package provides the required driver manager libraries. Create an environment variable to specify the location of the . You must install unixODBC version 2.odbc. you can use unixODBC or iODBC. LIBPATH=/usr/IBM/cognos/bin:$LIBPATH v On Linux. Table 23. For information. export ODBCINI=/usr/local/etc/. see the IBM Cognos Administration and Security Guide.ini may result in having incompatible entries for different driver managers.odbc. To resolve the problem.2.odbc. the unixODBC package provided with the operating system provides the ODBC Driver Manager.ini 2. For example. Set the appropriate library path environment variable to specify the location of the connectivity libraries and Driver Manager for your database. On Linux operating systems.

To point to this 32-bit client. you must manually configure the ARBORPATH and ESSBASEPATH environment variables. ensure that the lines appear as follows: <!--provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"--> <provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"> 6.xml file in an xml or text editor. you must edit the qfs. For Oracle Essbase 11.2. Your installation location might be different. IBM Cognos BI uses these variables to find the Oracle Essbase client location. For Oracle Essbase 11.1. The following example assumes that the client is installed on the C drive. Open the qfs_config. IBM Cognos BI is configured to use Oracle Essbase version 11. if you use Oracle Essbase version 11.1.the structure requirements between the driver managers you are using and try to use syntax that is common between the conflicting driver managers. Configure IBM Cognos Business Intelligence to use Oracle Essbase If you use IBM Cognos Business Intelligence with an Oracle Essbase data source version 11. Procedure 1.2 data source with IBM Cognos Business Intelligence on a UNIX or 64-bit Microsoft Windows operating system. Locate the following lines: <!--provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"--> <provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"> 4. This 64-bit client includes a 32-bit client that IBM Cognos BI uses.1. If you use another supported version of Oracle Essbase. ARBORPATH=C:\Hyperion\EPMSystem11R1\products\Essbase\EssbaseClient-32 ESSBASEPATH=C:\Hyperion\EPMSystem11R1\products\Essbase\EssbaseClient-32 Chapter 5. Go to the c10_location/configuration directory. The ARBORPATH and ESSBASEPATH environment variables are created during the installation of the Oracle Essbase client. 3.config. you must edit a configuration file to inform the IBM Cognos BI server of your version.1. you must manually change the ARBORPATH and ESSBASEPATH environment variables to replace EssbaseClient with EssbaseClient-32. Therefore. By default. change them as follows: <provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"> <!--provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"--> 5. you must install the 64-bit Oracle Essbase client.1. Installing and Configuring Product Components on One Computer 89 .2. Save the file and restart the IBM Cognos service Configuring Oracle Essbase on a UNIX or 64-bit Microsoft Windows operating system If you use an Oracle Essbase version 11. To use Oracle Essbase with IBM Cognos BI on a UNIX or 64-bit Microsoft Windows operating system. no configuration is required if you use this version.xml file for your version. In addition.1.1.1.2. you must install Oracle Foundation Services as well as the Oracle Essbase client. 2.

Windows 7. and have installed the product to the Program Files (x86) directory. start IBM Cognos Configuration as an Administrator.If you use a 32-bit Microsoft Windows operating system with a 32-bit Oracle Essbase client. click Environment. go to the c10_location/bin64 directory and then type the following command: . ensure that the operating environment is properly set up. Start IBM Cognos Configuration. ensure that all environment variables have been set. ensure that you are using a 64-bit version of Java. 2. Before you begin Before starting IBM Cognos Configuration. you are not required to change these environment variables. Procedure 1./cogconfig. On a Microsoft Windows operating system. For example. 90 IBM Cognos Business Intelligence Version 10. do not start IBM Cognos Configuration in the last page of the installation wizard.sh If IBM Cognos Configuration does not open. Ensure that user or service account used to run IBM Cognos has been set up.1: Installation and Configuration Guide . In the Explorer window. For example. Additional setup is required before you can configure IBM Cognos BI. click Start > IBM Cognos Configuration. Start IBM Cognos Configuration Use IBM Cognos Configuration to configure IBM Cognos Business Intelligence components and to start and stop IBM Cognos services if you are using the default Tomcat servlet container. you can start IBM Cognos Configuration in the last page of the installation wizard only if additional setup is not required.unsatisfied link message. copy the Java Database Connectivity (JDBC) drivers to the appropriate location before you start the configuration tool. if you use a database server other than Microsoft SQL or Cognos Content Database for the content store.Lang. If you see a Java. This will ensure that users in different locations can connect to reports and workspaces that are sent by e-mail. For example. ensure that you set the DISPLAY environment variable.unsupportedClassVersionError message. On Microsoft Windows. On UNIX or Linux operating systems. you must update your Java environment. verify that you are using a supported version of Java. By default. On UNIX or Linux operating systems.2. If you see a JAVA. the URI properties specify the localhost. Procedure 1.lang. Configure Environment Properties in IBM Cognos Configuration Specify the server name or an IP address in the URI properties that are used by IBM Cognos Business Intelligence. 2. or Windows 2008 computer. If you are using a Windows Vista.

Procedure 1. 4. If you want to use security in your IBM Cognos BI environment. click Environment. To enable the 64-bit version. Right-click Authentication. do not enable the 64-bit report server. Enable the 64-bit version of report server In a 64-bit installation. The 64-bit version of report server can be used only with packages for which dynamic query mode is enabled. Restart your IBM Cognos services if they are running. click Save. To use the 64-bit version. you can set one instance to use the 32-bit report server. 3. From the File menu. 2. v For all other URI properties. the default cryptographic provider. If you install the 32-bit version of the Application Tier Components or are using a 32-bit computer. Enable Security By default. You can then use routing rules so that report requests for non-dynamic query mode packages are routed to the instance that is running the 32-bit version of report server. For example. For more information about routing rules. click the value to change it. the report server component is provided in both 32-bit and 64-bit versions. 4. Installing and Configuring Product Components on One Computer 91 . change the localhost portion of all URI properties to the name or IP address of your IBM Cognos BI server by doing the following: v For Content Manager URIs. From the File menu. you must install the 64-bit version of the Application Tier Components on a 64-bit computer. see the Administration and Security Guide. 3. and select 64-bit. In the Explorer window. You must use the 32-bit version of report server for packages that do not use dynamic query mode. you must use the 32-bit version of report server. Change the value and then click OK. under Security > Cryptography. Chapter 5. click Save. you must enable it using IBM Cognos Configuration. In the IBM Cognos Configuration Explorer window. set the Password property. If you have multiple Application Tier Components instances in your environment. The default option is 32-bit. 6. 5. Click the Value box for Report server execution mode. if your package is based on IBM Cognos PowerCubes. In the IBM Cognos Configuration Explorer window. click Cognos. click the value and then click the edit icon. IBM Cognos Business Intelligence allows anonymous access. click Security >Authentication > Cognos. Under the Certificate Authority settings property group.3. Click the Value box for Allow Anonymous Access. 2. and click New Resource > Namespace. you must disable anonymous access and configure IBM Cognos BI to use an authentication provider. Procedure 1. Record the password in a secure location. In the Properties window. and select False.

3. From the File menu. v Type the appropriate values and click OK. In the Explorer window. for the Namespace ID property. you can keep the earlier version running with the original data. In the Properties window. under the Authentication component. 2. you can test the connection between Content Manager and the content store. configure IBM Cognos BI to point to a copy of the existing content store database. By using a copy of the original database with the new version. Procedure 1. For example. 6. the data in the content store is automatically upgraded and cannot be used by the earlier version. 5. under Data Access. After you save the configuration and start the IBM Cognos service. you can use the features in the administration portal to back up and archive the data before moving to an enterprise-level database in your production environment. 4. enter the name of your computer and port number on which DB2 is running.2. you must use an enterprise-level database for your content store.4. specify a unique identifier for the namespace. see the topic about deploying the entire content store in the Administration and Security Guide. for the Database name property. 92 IBM Cognos Business Intelligence Version 10. ensure that you specify the same user ID as the value you specified for CMSCRIPT_USERNAME when you created the tablespaces. click Content Store. 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. In the Type list. type a name for your authentication namespace. In the Properties window. If you have been using Cognos Content Database in a test or proof-of-concept system. 5. Setting database connection properties for a DB2 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. click Save. Content Manager uses the database logon to access the content store. 7. After you set the database connection properties. The new authentication provider resource appears in the Explorer window. In the Database server and port number field. Change the logon credentials to specify a valid user ID and password: v Click the Value box next to the User ID and password property and then click the edit button when it appears. In a production environment. click the appropriate namespace type and then click OK. In the location where you installed Content Manager. Content Manager.1: Installation and Configuration Guide . If you are upgrading from an earlier version of IBM Cognos BI. For more information. type the name of the database or the database alias. In the Name box. If you are connecting to a database on DB2 on z/OS. start IBM Cognos Configuration.

you must specify the instance name as a Java Database Connectivity (JDBC) URL property or a data source property. Informix. and then click the edit icon. In the Type box. you must use a different content store for each version. click Test.localhost:50000. Add all of the parameters except CMSCRIPT_USERNAME. Click Add to add the parameters that you used to create the tablespaces. start IBM Cognos Configuration. Content Manager. include the instance name if there are multiple instances of Microsoft SQL Server. you can type localhost\instance1. Oracle. 8. For a Microsoft SQL Server database. Right-click Content Manager. checks the database permissions. a connection to the default instance is created. under Data Access. b. select the type of database and click OK. When a content store is used by a new version of IBM Cognos BI. c. 50000 is the default port number used by DB2. or a named instance as the value for the Database server with port number or instance name property. In the Explorer window. click Local Configuration. 2. type a name for the resource. If no instance name property is specified. If you are connecting to a database on DB2 on z/OS: a. This step deletes the connection to the default resource. 6. Chapter 5. ensure you use that value. To test the connection between Content Manager and the content store database. Database. 3. 7. For example. Content Manager can access only one content store. select Oracle database (Advanced). 4. or Sybase 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. If you are using a different port number. On the computer where you installed Content Manager. Installing and Configuring Product Components on One Computer 93 . 5. For the Database server with port number or instance name property. next to Advanced properties. To connect to a named instance. In the Properties window. Procedure 1. The table is not deleted and is used each time that the test is repeated. Tip: If you want to use an Oracle Net8 keyword-value pair to manage the database connection. 6. provide the values for your database type: v If you use a Microsoft SQL Server database. and creates and populates a table. you can choose to use a port number. type the appropriate values for the Database server with port number or instance name and Database name properties. such as 1433. In the Properties window. and then click New resource. In the Explorer window. Content Manager connects to the database. click inside the Value box. click Save. Setting database connection properties for a Microsoft SQL Server. right-click Content Store and click Delete. From the File menu. from the Actions menu. In the Name box. If you installed more than one version of IBM Cognos BI. it cannot be used by an older version.

for the Database specifier property. IBM Cognos BI uses enterprise-oriented Oracle features to select a listener. you can type localhost\instance1. v If you use a Sybase database. 8. v In the Name column. Use a different user account for each instance of Informix content store database. The logon credentials are immediately encrypted. you must specify the instance name. Content Manager connects to the database. along with the user ID and password. v In the Value . balance connection requests among listeners. click Add. and balance connection requests among dispatchers. automatically reconnect to the database if the connection fails. 10. v If you use an Informix database. v If you use an advanced Oracle database. switch to another listener if the first listener fails. v Type the appropriate values and click OK. type the appropriate values for the Database server and port number and Database name properties. type the Oracle Net8 keyword-value pair for the connection. v In the Properties window. v If you use an Oracle database. If an instance name is not specified. click Save. type the appropriate values for the Database server and port number and SID properties. click Test. click Local Configuration.1: Installation and Configuration Guide . specify a user ID and password: v Click the Value box next to the User ID and password property and then click the edit icon when it appears. The table is not deleted and is used each time that the test is repeated. Here is an example: jdbc:JSQLConnect://localhost\\instance1/user=sa/ more properties as required To connect to a named instance. a connection to the default instance is created. and database name. are used to create a JDBC URL. create the advanced property CMSCRIPT_CS_ID and specify the account under which the instance runs: v In the Explorer window. type CMSCRIPT_CS_ID v In the Value column. type the appropriate values for the Database server and port number and Database name properties.The properties specified for the named instance. type the user ID of the account under which the instance of the content store runs. To test the connection between Content Manager and the content store database. For example. from the Actions menu. 7. 9.Advanced properties dialog box. From the File menu. If you host more than one content store database on an Informix instance. Here is an example: (description=(address=(host=myhost)(protocol=tcp)(port=1521) (connect_data=(sid=(orcl))))) When you select the advanced Oracle database. To configure logon credentials. click the Value column for Advanced properties and then click the edit icon. checks the database permissions. and creates and populates a table.2. 94 IBM Cognos Business Intelligence Version 10.

Test the mail server connections. IBM Cognos Business Intelligence tests the mail server connection. Tip: To be able to open reports that are sent by email. type the appropriate value for the default sender account. Chapter 5. Results If you do not plan to send reports by email. In the Explorer window right-click Notification and click Test. type the host name and port of your SMTP (outgoing) mail server. you are not required. You must also change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. under Data Access. the default account is used and notifications will not work properly. In the Properties window. 2. You can safely ignore the warning.Results Content Manager can now create the required tables in the content store when you start the IBM Cognos service for the first time. Click the Value box next to the Account and password property and then click the edit button when it appears. Otherwise. 3. Tip: To be able to open reports that are sent as links.Account and password dialog box and then click OK. Type the appropriate values in the Value . click Notification. click OK. If the connection properties are not specified correctly. However. In the Explorer window. remove the default information for the Account and password property. When you are prompted for confirmation to leave this property blank. you must change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. 4. consider using an external URI. Tip: If logon credentials are not required for the SMTP server. you cannot start the IBM Cognos services. you must configure a connection to a mail server account. for the SMTP mail server property. Installing and Configuring Product Components on One Computer 95 . you will see a warning message when the mail server connection is tested. Procedure 1. Ensure that the default user name has been removed. Specify a Connection to a Mail Server Account If you want to send reports by email. In the Properties window. or do not want to set up a mail server account immediately. 5. If you have mobile users accessing links remotely. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. 6. ensure that the Gateway URI on report servers and notification servers specifies an accessible Web server hosting IBM Cognos content. when you save the configuration and then you start the services in IBM Cognos Configuration. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report.

If you are upgrading. 2. otherwise you cannot start the IBM Cognos service. Before you start the services. you must start the services. reconfigure the affected properties and then test again. and tests the connections to the content store and other resources. Configuring the web server You must configure your Web server before users can connect to the IBM Cognos BI portal. 5. test the configuration by using the test feature in IBM Cognos Configuration. IBM Cognos Configuration checks the common symmetric keys (CSK) availability. you can change the cogstartup. click Test.xml file in the c10_location/ configuration directory.xml file permissions to ensure that it belongs to the same group as the Web server. Do not start the service until all tests pass. On UNIX and Linux operating systems. Tip: If Test is not available for selection. From the Actions menu. If the test fails. For information. Start IBM Cognos Configuration. It may take a few minutes for the IBM Cognos service to start. in the Explorer window. click Local Configuration. For IBM Cognos BI for reporting.xml file has read permission for others. 3. From the Actions menu.Start the IBM Cognos services To register the IBM Cognos Business Intelligence service so that users can access it through IBM Cognos Connection. 4.2. If you run your Web server under a specific group. a message appears indicating that configuration files were detected and upgraded to the new version. ensure that a user or service account is set up. Ensure that you save your configuration. the account under which the Web server runs must have read access to the cogstartup. This action starts all installed services that are not running and registers the IBM Cognos service on Windows. 96 IBM Cognos Business Intelligence Version 10. tests the namespace configuration. You can test some components individually by right-clicking the component in the Explorer panel and selecting Test. By default the cogstartup. Procedure 1.1: Installation and Configuration Guide . 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. You can then remove the read permission for others. Before you begin Before you begin. click Start. see “Configure a User Account or Network Service Account for IBM Cognos Business Intelligence” on page 52.

sh 32bit v On Windows operating systems.Enable the 32-bit web gateway for a 64-bit installation If you installed the 64-bit version of IBM Cognos BI but are using a 32-bit web server. Chapter 5.x or for IBM HTTP Server 8. Installing and Configuring Product Components on One Computer 97 . type . you can improve performance by changing the gateway from the default CGI gateway. follow the procedure and type . Go to the Webserver_installation/conf directory.x or Apache Server 2. The compiled gateways include: v Microsoft Internet Server Application Programming Interface (ISAPI) for Microsoft Internet Information Services (IIS) v Apache module for Apache Web Server or IBM HTTP Server v Servlet Gateway Java application if you use an application server other than the default Apache Tomcat Use Apache modules on Apache Server or IBM HTTP Server You can use Apache modules for Apache Server 2./copyGateMod. Use compiled gateways for production systems For production systems. Append the c10_location/cgi-bin directory to the appropriate environment variable: v On Solaris or Linux. you must manually move the 32-bit gateway files in your installation directory. Go to the c10_location/cgi-bin.3 and later. Note: If you need to restore the default 64-bit gateway files. LD_LIBRARY_PATH v On HP-UX.0.conf file in an editor.1. SHLIB_PATH and LD_LIBRARY_PATH v On AIX.2. Procedure 1. Ensure that both the server name and web server port number values are specified for the ServerName property. 2.sh 64bit or copyGateMod. type copyGateMod. 4. 3. or 6. Important: You cannot use the Apache modules with the version of Apache Server 2. Type the following command: v On UNIX or Linux operating systems./copyGateMod. The 64-bit gateway files are copied from the cgi-bin/lib64 directory to the cgi-bin directory.bat 32bit Results The 32-bit gateway files are copied from the cgi-bin/lib directory to the cgi-bin directory. If you installed the 32-bit version of IBM Cognos BI. 7. Open the httpd. LIBPATH 2.bat 64bit. Procedure 1. the 32-bit version of the gateway is installed by default.2 that is supplied with Red Hat Enterprise Linux version 5.

ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use.deny Allow from all </Directory> The <Directory> directive is optional. Table 24. 6. v Use the mod2_cognos module for Apache Server 2. 8. To enable the gateway diagnostic page.1.0. 7. Add the following to the end of the load module list: LoadModule cognos_module "c10_location/cgi-bin/mod2_2_cognos. Module suffix for your operating system Operating system Windows Solaris. add the following to the server status reports section: 98 IBM Cognos Business Intelligence Version 10.5. Also. ensure that you use the same value for the ibmcognos part of the ScriptAlias and Alias values as shown in the examples. If you do not use ibmcognos for the ScriptAlias and Alias values.suffix" Where suffix is as listed in the following table. AIX.deny Allow from all </Location> Where module_alias is a name that you can choose. Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration.1: Installation and Configuration Guide .2.x or IBM HTTP Server 8 and 7. Linux ® Suffix dll so Apache modules are provided for different versions of Apache Server or IBM HTTP Server: v Use the mod2_2_cognos module for Apache Server 2. Add the following to the server status reports section: <Location /ibmcognos/cgi-bin/module_alias> SetHandler cognos-handler Order allow.deny Allow from all </Directory> Alias /ibmcognos "c10_location/webcontent" <Directory "c10_location/webcontent"> Options Indexes MultiViews AllowOverride None Order allow.2. HP-UX IA .x and IBM HTTP Server 6. Note: Ensure that you define the /ibmcognos/cgi-bin alias before the /ibmcognos alias. Add the following: ScriptAlias /ibmcognos/cgi-bin "c10_location/cgi-bin" <Directory "c10_location/cgi-bin"> AllowOverride None Options None Order allow.

Start IBM Cognos Configuration. 14. you must create a separate application pool for each product or instance and then associate the aliases for that product or instance to the application pool. 16. 13. In the Gateway URI box. Installing and Configuring Product Components on One Computer 99 . For example.c> CGIBinDir "c10_location/cgi-bin" </IfModule> 10. Save your changes. Add the following to the user directory section: <IfModule mod2_2_cognos. 11. see your web server documentation.<Location /ibmcognos/cgi-bin/diag_module_alias> SetHandler cognos-handler Order allow. On HP-UX. http://host_name:port/ibmcognos/cgi-bin/module_alias.cgi part of the URI to module_alias. In the Explorer panel. Important: If you are using the 32-bit version of the ISAPI gateway. Apache module files are provided for different versions of Apache Server or IBM HTTP Server: v Use mod2_2_cognos.2.c for Apache Server 2. 15.x or IBM HTTP Server 8 and 7. you must enable 32-bit application for the application pool that is used for the IBM Cognos Chapter 5. Results Users can access the server by entering the Apache module URI in their browser. 12. click Local Configuration > Environment. enable searching for SHLIB_PATH by running the following command in the Apache_installation/bin directory: chatr +s enable +b enable httpd Restart the web server.deny Allow from all </Location> Where diag_module_alias is a name that you can choose. 9.x and IBM HTTP Server 6. change the cognos. configure IBM Cognos to use the ISAPI gateway rather that the default CGI gateway. or several instances of the same product.1. For more information about creating an application pool. Use the ISAPI gateway on Microsoft Internet Information Services (IIS) version 7 or 8 If you are using a Microsoft Internet Information Services (IIS) web server.0. v Use mod2_cognos. About this task If you are using Microsoft IIS as your web server and you plan to run more than one IBM Cognos BI product. on one computer. For example.c for Apache Server 2. Save and close the file. http://servername:port/ibmcognos/cgi-bin/module_alias.

2. v If you are using Microsoft Windows 2012 Server. and then click Internet Information Services (IIS) Manager. 4. 100 IBM Cognos Business Intelligence Version 10. If you are using Microsoft Windows 2008 Server. d. Select Internet Information Services if it is not already selected. v If you are using Microsoft Windows 7. in Server Manager. b. c. In the Add Roles and Features Wizard. select the application pool that is used for IBM Cognos. and click Internet Information Services (IIS) Manager. If you are using Microsoft Windows 2012 Server. If you are using Microsoft Windows 8 or 2012 Server. click Programs > Programs and Features. Select Web Server (IIS). Ensure that Common HTTP Features. use the following steps: a. and click Next. Programs and Features is available directly from the Control Panel. Change the value for Enable 32-Bit Applications to True. c. If you are using Microsoft Windows 7 or 8. expand Roles > Web Server (IIS). Click OK. and click Next until you get to the Role Services section of the wizard. f.1: Installation and Configuration Guide . and then right-click your server name. In the Internet Information Services (IIS) Manager console. In the Internet Information Services (IIS) Manager. from theControl Panel.gateway. Procedure 1. 3. under Connections. select IIS. if it is not already installed. If ISAPI extensions is set to Not installed. Expand Application Development. Select your server. Ensure that Common HTTP Features. use the following steps: a. Click Server Manager > Roles > Web Server (IIS). click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. Click Install. from theControl Panel. v If you are using Microsoft Windows 8. or the features you require are enabled. v If you are using Microsoft Windows 2008 Server. select your server name. Expand Internet Information Services > World Wide Web Services. select ISAPI extensions. f. 6. Select ISAPI extensions if it is not already selected. d. Expand Application Development Features. click Role-based or feature-based installation. use the following steps: a. b. or the features you require are enabled. ensure that Common HTTP Features is selected. and click Next. Click Turn Windows features on or off. b. e. and click Advanced Settings. and click Next. In the Microsoft Windows Control Panel. 2. e. If ISAPI extensions is not selected. in Server Manager. select ISAPI extensions and click Add Role Service. 5. c. click Administrative Tools to access the Internet Information Services (IIS) Manager console.

v The application server user account has full access permission for the IBM Cognos installation. 9. If you do not use ibmcognos for the Alias values. v IBM Cognos BI gateway components are installed on the same system as the application server. and under your website.dll d. a. click Local Configuration > Environment. f. Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. In Executable. Expand Sites. 10. Double-click Handler Mappings. Before you begin Ensure the following tasks are complete: v The application server is installed and running on each computer where the servlet gateway is to be installed. 8. b. add the virtual directories as shown in the table: Table 25. v The IBM Cognos BI Application Tier Components and Content Manager are installed and running in the environment. Configure the servlet gateway for an application server If you deploy IBM Cognos to an application server other than Tomcat. Results Users can access the ISAPI gateway by entering http://servername/ibmcognos/ isapi in their web browsers.dll. e. Click OK. Under Actions. 12. type cognosisapi. such as CognosISAPI. 11. Start IBM Cognos Configuration. Click Yes in the dialog box to allow the ISAPI extension. Chapter 5. Select the cgi-bin virtual directory that you created. In Name. change the cognos. click Add Module Mapping. c. you can use the servlet gateway to serve the portal pages rather than using a web server. select IsapiModule. In Request Path. enter the path to the cognosisapi. In the Gateway URI box. enter a name for the entry.dll file. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. In the Explorer panel. For example. enter: C:\Program Files\ibm\cognos\c10\cgi-bin\cognosisapi. Installing and Configuring Product Components on One Computer 101 .7. In Module.cgi part of the URI to cognosisapi.dll. 13.

4. Open the httpd. Check that IBM Cognos components are properly set up. Results You can now access IBM Cognos components using the servlet gateway by entering the gateway URI. Use the CGI gateway on Apache Server or IBM HTTP Server The default gateway configured in IBM Cognos Configuration is the CGI gateway. you deploy the servlet gateway to a different JVM instance than the JVM instances that run the IBM Cognos BI Application Tier Components and Content Manager servlets. The IBM Cognos Servlet Gateway URI is case-sensitive. Use CGI gateways You can use the CGI gateway on IBM HTTP Server. or Microsoft Internet Information Services (IIS) Server. 3. Configure application server properties and deploy IBM Cognos Servlet Gateway. the servlet gateway must be deployed to a separate JVM instance. 7. 3.conf file in an editor. For example. Apache Web Server. Change the application server startup script. if required. 2. if necessary. Configure IBM Cognos Servlet Gateway to run on the application server. To use the CGI gateway. Enable SSL.deny Allow from all </Directory> Alias /ibmcognos "c10_location/webcontent" 102 IBM Cognos Business Intelligence Version 10. Procedure 1. If you plan to run IBM Cognos BI and the IBM Cognos Servlet Gateway on the same application server. Create a separate JVM instance.1: Installation and Configuration Guide . Go to the Webserver_installation/conf directory. Ensure that both the server name and web server port number values are specified for the ServerName property. 6. Procedure 1. if necessary. 4. you must configure aliases for Apache Server or IBM HTTP Server.2. 5.http[s]:host_name:port/ServletGateway. 2. Set environment variables. Add the following: ScriptAlias /ibmcognos/cgi-bin "c10_location/cgi-bin" <Directory "c10_location/cgi-bin"> AllowOverride None Options None Order allow.About this task Instead of routing requests directly to the dispatcher. Doing this type of deployment separates the load for serving static content from the main applications.

If you are using Microsoft Windows 8 or 2012 Server. 3. Installing and Configuring Product Components on One Computer 103 . If CGI is set to Not installed. 4. If you do not use ibmcognos for the ScriptAlias and Alias values. select CGI and click Add Role Service. or several instances of the same product. Restart the web server. use the following steps: Chapter 5. Note: Ensure that you define the /ibmcognos/cgi-bin alias before the /ibmcognos alias. 2.<Directory "c10_location/webcontent"> Options Indexes MultiViews AllowOverride None Order allow. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. see your web server documentation. 6. on one computer. Save and close the file. Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. Click Server Manager > Roles > Web Server (IIS). or the features you require are enabled. For more information about creating an application pool. Ensure that Common HTTP Features. c. Use the CGI gateway on Microsoft Internet Information Services (IIS) version 7 or 8 If you are using Microsoft Internet Information Services (IIS) version 7 or later. use the following task to configure the CGI gateway. Procedure 1. ensure that you use the same value for the ibmcognos part of the ScriptAlias and Alias values as shown in the examples. If you are using Microsoft Windows 2008 Server. About this task If you are using Microsoft IIS as your web server and you plan to run more than one IBM Cognos BI product. use the following steps: a. b. In the Microsoft Windows Control Panel. 5. Results Users can access the portal at http://servername:port/ibmcognos. The CGI gateway is provided for both 32-bit and 64-bit web servers. Programs and Features is available directly from the Control Panel. you must create a separate application pool for each product or instance and then associate the aliases for that product or instance to the application pool.deny Allow from all </Directory> The <Directory> directive is optional. If you are using Microsoft Windows 2012 Server. Also. Click Turn Windows features on or off. click Programs > Programs and Features.

Click OK. 8. v If you are using Microsoft Windows 2008 Server. such as CognosCGI. Under Actions. c. and then click Internet Information Services (IIS) Manager. including the file name. expand Roles > Web Server (IIS). In the Internet Information Services (IIS) Manager console. v If you are using Microsoft Windows 8. and click Next. b. Double-click ISAPI and CGI Restrictions. use the following steps: a. v If you are using Microsoft Windows 2012 Server. For example. Click Install. or the features you require are enabled. from the Control Panel. enter: “C:\Program Files\ibm\cognos\c10\cgi-bin\cognos. expand Sites. d. and click Next.a.1: Installation and Configuration Guide . The file is in the c10_location\cgi-bin directory. If you are using Microsoft Windows 7 or 8. 6. 9. d. If the path includes spaces. ensure that Common HTTP Features is selected. 11. click Role-based or feature-based installation. If CGI is not selected. 12. Select your server.cgi file. Select Web Server (IIS). ensure you use quotation marks around the path. v If you are using Microsoft Windows 7. and click Next until you get to the Role Services section of the wizard. in Server Manager. 7. 5. click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. and under your website. click Administrative Tools to access the Internet Information Services (IIS) Manager console. if it is not already installed. and click Next. add the virtual directories as shown in the table: Table 26. Select Internet Information Services if it is not already selected. f. click Add. Expand Internet Information Services > World Wide Web Services. c.2. Enter the path to the cognos. select IIS. Enter a Description. e. f. Select CGI if it is not already selected. select CGI. from the Control Panel. and click OK. Expand Application Development. under Connections. In the Add Roles and Features Wizard. You must enter the full path. select your server name. Expand Application Development Features. Ensure that Common HTTP Features.cgi” 10. in Server Manager. Under Connections. Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin 104 IBM Cognos Business Intelligence Version 10. and click Internet Information Services (IIS) Manager. e. b. and then right-click your server name. Select Allow extension path to execute.

Results Users can access the CGI gateway by entering http://servername/ibmcognos in their web browsers. Use the CGI gateway on older versions of Microsoft IIS For versions of Microsoft Internet Information Services (IIS) earlier than version 7. Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin Permission Read Execute Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. Procedure Create the virtual directories shown in the following table: Table 27. such as CognosCGI. Chapter 5. Report authors can browse for images to include in reports in a way that is similar to browsing a file system. e.cgi. use these steps to configure the CGI gateway. a. type cognos.Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. Configuring WebDAV to view and browse images To view and browse images in the Report Studio. Leave Executable (optional) blank. and then configure the directory access. c. Installing and Configuring Product Components on One Computer 105 . 15. Select the cgi-bin virtual directory that you created. d. 13. Double-click Handler Mappings. open the httpd. configure Web Distributed Authoring and Versioning (WebDAV) on your web server.conf file in a text editor. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. In the webserver_location/conf directory. enter a name for the entry. you must add directives to your server configuration file. In Request Path. Configuring WebDAV on IBM HTTP Server or Apache server On IBM HTTP Server or Apache server. Procedure 1. In Module. b. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. In Name. Under Actions. select CgiModule. 14. click Add Module Mapping. If you do not use ibmcognos for the ScriptAlias and Alias values. Click OK. If you do not use ibmcognos for the Alias values.

7. DAVLockDB "webserver_location/var/DavLock" Ensure that the directory exists. and then click Install. you must first enable the WebDAV feature. If you are using Microsoft Windows 2012 Server. c. 4. the default location for browsing is http://servername/ibmcognos/samples/images. 5. Restart your web server. users can enter that location.2.deny Allow from all </Directory> 6. 3. and click Next. LoadModule dav_module modules/mod_dav. Programs and Features is available directly from the Control Panel. use the following steps: a. Procedure 1. In the Add Roles and Features Wizard. b.1: Installation and Configuration Guide . 4. click Programs > Programs and Features. Alias /images "path/shared_images" <Directory "path/shared_images"> Dav On Options Indexes MultiViews AllowOverride None Order allow. In the Microsoft Windows Control Panel.so 3. If you are using Microsoft Windows 8 or 2012 Server. 106 IBM Cognos Business Intelligence Version 10.so.so LoadModule dav_fs_module modules/mod_dav_fs. click Role-based or feature-based installation. When users click Browse in the image browser. 2. Report Studio users can add images to their reports. Under Web Server > Common HTTP Features. select WebDAV Publishing. For example. and click Next. d. If you created another location. Create an alias for the directory where your images are stored. b. In the Role Services section. Add Dav On to the <Directory> information for the alias. use the following steps: a. select Add Role Services. Provide a location for the DAVLockDB directive.2. Click Turn Windows features on or off. Save the file. For example. and then configure your web server to access the image location. Results With WebDAV enabled. Click Next. Click Server Manager > Roles > Web Server (IIS).so and modules/mod_dav_fs. Select your server. Configuring WebDAV on Microsoft IIS web servers On Microsoft Internet Information Services (IIS) web servers. Uncomment the directives that load modules/mod_dav. If you are using Microsoft Windows 2008 Server.

v If you are using Microsoft Windows 8. Results With WebDAV enabled. Expand Web Server (IIS) > Web Server > Common HTTP Features. Right-click the directory or virtual directory you added authoring rules to. 16. Click Add Authoring Rule. Click Next > Next. in Server Manager. You can find that user by select the website. expand your web server. v If you are using Microsoft Windows 2008 Server. select IIS. b. 14.5. and select images. For example. users can enter that location. 7. 9. from theControl Panel. and click Edit Permissions. select True for Allow Anonymous Property Queries. and add the appropriate permissions. 8. use the following steps: a. under Connections. select Default Web Site. 13. Under Connections. 12. Click Security. 10. Chapter 5. Click WebDAV Settings. and then right-click your server name. and viewing the properties for the displayed users. and click Internet Information Services (IIS) Manager. Select the directory or virtual directory to which you want to allow WebDAV access. 11. Double-click WebDAV Authoring. v If you are using Microsoft Windows 7. 15. and select your website. in Server Manager. add permissions for the anonymous access user. Report Studio users can add images to their reports. under the ibmcognos virtual directory. Select WebDAV Publishing. click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. v If you are using Microsoft Windows 2012 Server. d. expand samples. Installing and Configuring Product Components on One Computer 107 . Sites. double-clicking Authentication. If you created another location. if you installed the samples and you want to use the default path. and click OK. and select WebDAV Publishing. click Administrative Tools to access the Internet Information Services (IIS) Manager console. the default location for browsing is http://servername/ibmcognos/samples/images. and add an authoring rule for the image files. In the Internet Information Services (IIS) Manager console. If you are using Microsoft Windows 7 or 8. select your server name. and then click Install. Double-click WebDAV Authoring. and then click Internet Information Services (IIS) Manager. c. When users click Browse in the image browser. For example. if you allow anonymous access to your web server. and click Apply. 6. and add the appropriate rules for your environment. Expand Internet Information Services > World Wide Web Services > Common HTTP Features. For example. from theControl Panel. expand Roles > Web Server (IIS). If you have anonymous access enabled. Click Enable WebDAV.

The IBM Cognos Business Intelligence modeling tools create and manage metadata for IBM Cognos BI. these steps are not necessary. your installation is working. You must set up the data source environment only if you installed your modeling tool in a different location from the older version. If the response shows a list of content in Public Folders. Users can run reports in any language. you are not required to set up anything in the data source environment.1: Installation and Configuration Guide . http://host_name:port/p2pd/servlet The default vale for host_name:port is localhost:9300. If you use a Sybase data source. It may take a few minutes for the Web page to open. For example. Open a Web browser. 4. and Metric Designer creates and manages metadata required for the scorecarding functions. there are several things you must think about or do when you set up the data source environment for Framework Manager or IBM Cognos BI Transformer or set up the import source environment for Metric Designer. Set variables for data source connections Use this procedure to set up variables for data source connections for Framework Manager or IBM Cognos Transformer or to set up the import source environment for Metric Designer. you can test the installation by connecting to the IBM Cognos BI portal. 3. Test that Content Manager is running by typing the Content Manager URIs value from IBM Cognos Configuration. Test the gateway by typing the Gateway URI value from IBM Cognos Configuration in your Web browser. For example. If you see the Welcome page in the IBM Cognos BI portal. 108 IBM Cognos Business Intelligence Version 10. the dispatcher is available. After you have completed the configuration and started the services. Framework Manager creates and manages metadata for the reporting functions. 2. Users operating in different languages can connect to an MSAS 2005 data source from the same instance of IBM Cognos BI. Test the availability of the dispatcher by typing the Internal dispatcher URI value from IBM Cognos Configuration. If you upgraded. Modelers must create a separate package for each language. Because metadata is derived from data sources in multi-platform or multilingual environments.Test the Installation and Configuration You can test your configuration settings by running the test feature as you configure IBM Cognos Business Intelligence. Commonly. these things depend on the other technology you use for your data or import source.2. http://host_name:port/p2pd/servlet/dispatch The default vale for host_name:port is localhost:9300. Procedure 1. IBM Cognos BI Transformer creates and manages metadata for PowerCubes.

configure the following authorization objects so that the modeling tool can retrieve metadata.Before you begin Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. No settings are required for SAP BW. Installing and Configuring Product Components on One Computer 109 . which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory if you installed a 64-bit Oracle client. SU_USER. If you are using Oracle 11g.jar.jar. see the DB2 documentation. SUGU. Set the Name of RFC to be protected field to SYST. Where default values are specified. RS_UNIFICATION. Error messages. date. 2. RSOB. For Oracle. For SAP BW. If you are using Oracle 10g. you must install the additional fonts from the Supplementary Language Documentation disk. For Oracle. SDTX. add $ORACLE_HOME/lib to your LD_LIBRARY_PATH variable. ensure that the 32-bit Oracle libraries are in the library search path. RSAB. set the DB2CODEPAGE environment variable to a value of 1252. Set the Authorization Group field to &NC&. create an authorization group and assign the table RSHIEDIR to it. sort order.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. v For DB2. you may want to modify the values on the SAP system. RFC1. copy the correct library file for your version of the Oracle client from ORACLE_HOME/jdbc/lib to the c10_location\webapps\p2pd\WEB-INF\lib directory. 3. v S_TABU_DIS Set the Activity field to 03.character_set Examples are: NLS_LANG = AMERICAN_AMERICA. set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager or Metric Designer and the IBM Cognos BI server are installed by typing the following command: NLS_LANG = language_territory. monetary. Note: &NC& represents any table that does not have an authorization group. you must have ojdbc14. For Japanese and Korean currency symbols to appear correctly. The new authorization group restricts the user's access to the Chapter 5. Set the environment variable for multilingual support: v For Oracle. 4. Set the Type of RFC object to be protected field to FUGR. time. v S_RFC Set the Activity field to 16. numeric. When you set the load library paths. you must have ojdbc5. Procedure 1. and calendar conventions automatically adapt to the native language and locale.UTF8 NLS_LANG = JAPANESE_JAPAN. For more information about whether to use this optional environment variable. For security reasons. SAP support only a single code page on non-Unicode SAP BW systems.

2.” on page 219) to work in your environment. v S_USER_GRP Set the Activity field to 03. Creating a metric store database You must create a metric store database using Oracle. Microsoft SQL Server. you must create an alias to the metric store in the Application Tier Components location. v S_RS_HIER Set the Activity field to 71. Create the authorization group as a customization in the SAP system. you must configure the IBM Cognos BI components (see Chapter 9. For more information about SAP BW authorization objects. Set the Type of reporting components field to the default value.1: Installation and Configuration Guide . Set the InfoCube sub-object field to the values DATA and DEFINITION. You cannot use Cognos Content Database as a metric store database. v S_RS_COMP Set the Activity field to the default value. Results After you complete these tasks. Set the Info Cube field to the value: InfoCube Technical Name. Set the User group in user master main field to the default value. A metric store also contains scorecarding application settings. or DB2. 05. Set the Name (ID) of reporting components field to the default value. v S_RS_COMP1 Set the Activity field to the default value. Set the Type of reporting components field to the default value. Set the Version field to Hierarchy Version. 110 IBM Cognos Business Intelligence Version 10. Set the Owner (Person Responsible) field to the default value.table only. Set the InfoObject field to InfoObject Technical Name. Although you run the command to create the metric store from the location where the Application Tier Components are installed. Set the Info Area field to InfoArea Technical Name. you can specify a different location for the metric store in the command parameters. A metric store is a database that contains content for metric packages. Set the Name (ID) of reporting components field to the default value. such as user preferences. If the metric store is on a different computer from the Application Tier Components. Set the Hierarchy Name field to Hierarchy Name. Set the Info Area field to InfoArea Technical Name. Set the InfoCube field to InfoCube Technical Name. see Transaction SU03. which is needed by the modeling tool. “Configuration options. v S_RS_ICUBE Set the Activity field to 03.

Create a metric store database in IBM DB2 Use this procedure to create a metric store using an IBM DB2 database. In the Application Tier Components location.cmd script by typing the following command: On a Microsoft Windows operating system. Installing and Configuring Product Components on One Computer 111 . v CREATETAB v v v v BINDADD CONNECT IMPLICIT_SCHEMA LOAD Create a metric store database in Microsoft SQL Server Use this procedure to create a metric store using a Microsoft SQL Server database. in the c10_location/ configuration/schemas/cmm/db2 directory.db2 script is invoked by the cmm_create_db. The password for the user_name value. The initializedb. The user ID with permissions to create the database. The database alias name. Values for cmm_create_db script Value dbinstance user_name Setting The DB2 instance name where the database will be created.cmd script and defines the buffer pools and tablespaces. For example. The name must have a maximum of 8 characters. The user account must have the following privileges. To ensure the security and integrity of databases. Table 28. The name of the database that will be created. password dbname drive/path dbalias Note: Your database administrator can review the scripts to ensure they suit your environment. Chapter 5. Determine which user account IBM Cognos Metrics Manager will use to access the database. run the cmm_create_db. the drive on which the database objects will be created. On Windows. 2. The user ID must have SYSADM or SYSCTRL privileges. and it cannot start with a number. On UNIX. C. it is also important to protect them from unauthorized or inappropriate access. This value is optional.Your database administrator must back up IBM Cognos Business Intelligence databases regularly because they contain the IBM Cognos data. the path where the database objects will be created. type cmm_create_db. Procedure 1. and must have DBADM privileges to create the schema.sh dbinstance user_name password dbname path dbalias Use the values from the following table in your command. type cmm_create_db dbinstance user_name password dbname drive dbalias On a UNIX operating system.

The user account must be the database owner (dbo) or aliased to the database owner.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. numeric. The user created by the script and given database owner permissions. database_name user_name The name of the database that will be created. You must use a valid Oracle database username with the following permissions granted: 112 IBM Cognos Business Intelligence Version 10. Error messages. run the cmm_create_db. The password for the username. password user_to_create Create an metric store database in Oracle Use this procedure to create a metric store using a new Oracle database.2. The user ID must also have a default language of English. Determine which user account IBM Cognos Metrics Manager will use to access the database. In the Application Tier Components location. sort order. If there are multiple instances of Microsoft SQL Server. The user ID must have permission to create the database.character_set Examples are: v NLS_LANG = AMERICAN_AMERICA.1: Installation and Configuration Guide . 2. Values for cmm_create_db script Value host_name Setting The name of the computer where the database will be created. 3. specify host_name\instance_name. such as the sa user. This value is optional. Procedure 1. and calendar conventions automatically adapt to the native language and locale. This information is one of the parameters you can use when you run the command to create the database. Determine which user account IBM Cognos Metrics Manager will use to access the database. time.Procedure 1. date. 2. Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command: NLS_LANG = language_territory. Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX. This information is one of the parameters you can use when you run the command to create the database. monetary. The user ID with permissions to create the database. in the c10_location/ configuration/schemas/cmm/sqlserver directory. Table 29.cmd script by typing the following command: path_to_script cmm_create_db host_name database_name user_name password [user_to_create] Use the values from the following table in your command.UTF8 v NLS_LANG = JAPANESE_JAPAN.

numeric. date. For example. Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX. Table 30. Error messages. Procedure 1. sort order. and CREATE SESSION v EXECUTE on DBMS_LOCK and DBMS_UTILITY packages The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role. CREATE TYPE. CREATE VIEW. Determine which user account IBM Cognos Metrics Manager will use to access the database. 2. This value is optional.v CREATE TABLE. monetary. c10_location/configuration/schemas/cmm/ oracle The SID for the new database that will be created. CREATE SEQUENCE. CREATE TRIGGER. The path where the data files will be created. run the cmm_create_db. and calendar conventions automatically adapt to the native language and locale. CREATE PROCEDURE. 3. 4. sid path database_version user_to_create Create a metric store database in Oracle using an existing database Use this procedure to create a metric store using an existing Oracle database. You must use a valid Oracle database username with the following permissions granted: Chapter 5. The user created by the script and given database owner permissions. time. You must grant these permissions only.character_set Examples are: v NLS_LANG = AMERICAN_AMERICA.cmd script by typing the following command: path_to_script cmm_create_db sid path database_version [user_to_create] Use the values from the following table in your command. the metric store will not initialize. Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command: NLS_LANG = language_territory. In the Application Tier Components location.UTF8 v NLS_LANG = JAPANESE_JAPAN. For example.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. Values for cmm_create_db script Value path_to_script Setting The path to the script. If you grant fewer or more privileges. Installing and Configuring Product Components on One Computer 113 . The version of Oracle software that is installed. oracle9 or oracle10. in the c10_location/ configuration/schemas/cmm/oracle directory.

DB2Jcc -version If the directory contains a db2java. create a new database and specify AL32UTF8 for the database character set parameters.ibm. CREATE VIEW. Set up the database client for an Oracle metric store Use this procedure to setup the database client for an Oracle metric store. Determine if the database is Unicode. and CREATE SESSION v EXECUTE on DBMS_LOCK and DBMS_UTILITY packages. If the metric store is on a different computer from the Application Tier Components. db2jcc_license_cu.db2. run the following command: java -cp path\db2jcc.jar v the license file. Copy the following files from DB2_installation/sqllib/java directory to the c10_location/webapps/p2pd/WEB-INF/lib directory. CREATE TRIGGER.v CREATE TABLE. use the IBM DB2 command line interface. The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role.jar Tip: To check the driver version. configure a database alias to the metric store by running the IBM DB2 Client Configuration Assistant.jar or db2java. CREATE TYPE. v the universal driver file. Set up the database client for an IBM DB2 metric store Use this procedure to setup the database client for an IBM DB2 metric store. If you grant fewer or more privileges. 4. The cmm_create_db. CREATE SEQUENCE.zip file. the metric store name automatically becomes the alias. Setting up the database client for the Metric Store If you are using a database other than Microsoft SQL as a metric store. You must grant these permissions only. delete the file. you must install database client software and Java Database Connectivity (JDBC) drivers on each computer where you install the Application Tier Components for Cognos Metrics Manager.1: Installation and Configuration Guide .jcc. Procedure 1. Install the IBM DB2 client software on the Application Tier Components computer. Note: If the metric store database and the Application Tier Components are on the same computer. 3.cmd script mentioned in “Create a metric store database in IBM DB2” on page 111 creates a database with AL32UTF8 character encoding. the metric store will not initialize. 2. On a UNIX or Linux operating system. Doing this allows Application Tier Components to access the metric store database.2. db2jcc. CREATE PROCEDURE. 114 IBM Cognos Business Intelligence Version 10. 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.jar com.

you must create at least one metric package using the New Metric Package wizard. A metric package contains connection information. including the start and end dates of the fiscal year. For a new metric store. You open the New Metric Package wizard from the toolbar in IBM Cognos Connection. 3. click the New metric package button . Note: If you are using Oracle 11g. and metric management tasks for that application. On the computer where the Oracle client is installed. Before you begin To create metric packages. Use the wizard to define the metric package name and the data source connection to the metric store. Set up the database client for a Microsoft SQL Server metric store Use this procedure to setup the database client for a Microsoft SQL Server metric store. install a 64-bit Oracle client. 4. A metric package is an IBM Cognos Connection representation of a Metric Studio application. Procedure 1. you must have execute permissions for the Metric Studio Administration secured feature and traverse permission for the Administration secured function. go to the ORACLE_HOME/jdbc/lib directory. 2. Install the bcp utility on every Windows computer where Application Tier Components for IBM Cognos Metrics Manager are installed. you must also install a 32-bit client. 3. Install the SQL Loader utility on the computer where Application Tier Components are installed. 2. 2.jar to the c10_location/webapps/p2pd/WEB-INF/lib directory on the computer where Application Tier Components are installed. Click New data source. If you are using a 64-bit installation. Note: Ensure you copy the jar file from the 64-bit client if you have installed the 64-bit Metrics Manager. and click Next. Create a metric package Before users can use Metric Studio. The driver is available from an Oracle client or server installation. reports. Procedure 1. Chapter 5. Type a name and description for the Metric Studio application to represent this metric package. Add the location of the bcp utility to the path environment variable. Copy ojdbc5. The metric package content is stored in a metric store. Installing and Configuring Product Components on One Computer 115 . you also provide the information necessary to initialize the database. and can also be downloaded from the Oracle Web site.Procedure 1. In IBM Cognos Connection.

Enter the name of the database as defined in the IBM DB2 client. Select User ID. Select the Password and Create a signon that the Everyone group can use check boxes. In the Type box. b. Type a name and description for the data source connection for the metric store that contains the content for this metric package. port number. v If you are using a Microsoft SQL Server database: a. If you are using AIX. configure a JDBC connection for data source by adding the server name. port number. click Test the connection. and specifying the required values for the server name. Specify the information required for your database type. b.1: Installation and Configuration Guide . For example. and type the user ID and password of the user account with access to the database. Select Open this package with Metric Studio after closing the wizard and then click Finish. a JDBC connection is required. Click the new data source and click Next. 6.4. 116 IBM Cognos Business Intelligence Version 10. and click Next. d. Select the isolation level. When you see the page that summarizes the data source details and the metric store settings. For information about collation sequences. 9. 7. 10. Select the Password and Create a signon that the Everyone group can use check boxes. ensure the value that you enter is the same as the collation sequence specified when the database was created. Select the Password and Create a signon that the Everyone group can use check boxes. 11. If you want to provide one. and Oracle service ID in the appropriate fields. Select Signons. d. a JDBC connection is required. Enter the name of the database server. b. c. 8. v If you are using an IBM DB2 database: a. Select User ID. The user account must have the default language set to English. d. Click Next and then click Finish. If you are using AIX. and click Next. Tip: To test whether the parameters are correct.2. and database name in the appropriate fields. 5. server_name or server_name\instance_name if there are multiple instances of Microsoft SQL Server. If you are not using the default port number 1433. and type the user ID and password of the user account with access to the database. configure a JDBC connection for data source by adding a connection type of Service ID. see the database documentation. Optionally. c. use server_name. click the database type. v If you are using an Oracle database: a. Click Next and follow the prompts to provide the information necessary to initialize the database. Type the database name. c. a collation sequence is not required. Optionally. click Initialize. and type the user ID and password of the user account with access to the database. Enter the connection string. In most cases.port.

Installing and Configuring Product Components on One Computer 117 . Chapter 5.Results Metric Studio opens. and the new metric package appears in IBM Cognos Connection.

118 IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide .

you must update location-specific properties in IBM Cognos Configuration. such as Apache Web Server. Installing and Configuring Server Components on Different Computers Use the installation wizard to select the server components that you want to install and the location on your computer where you want to install them. the sequence is important. IBM Cognos Connection. you must use the upgrading steps. such as Framework Manager. 2013 119 . all the distributed components must be the same version of IBM Cognos BI. Only the components that you choose to install are copied from the disk to your computer. If you are upgrading from an earlier version of IBM Cognos BI. and then the active Content Manager. whether you install on a 64-bit server or a 32-bit server. If you are installing IBM Cognos Metrics Manager. you must create the metric store database and at least one metric package. or on the same computer.Chapter 6. The server components include the following: v Content Manager v Application Tier Components v Gateway You can install each component on a separate computer. install them in the same installation location to avoid conflicts among ports and other default settings. IBM Cognos Transformer. and Metric Designer v any Software Development Kit applications that are running Upgrading your installation If you are upgrading from a previous release of IBM Cognos PowerPlay. “Upgrade IBM Cognos Business Intelligence. Stopping services sequence If you need to stop services in a distributed environment. followed by the standby Content Manager. see Chapter 4. Some Web servers. If you install IBM Cognos BI on additional or alternate hosts. 2005. It is important to also stop the following: v applications that are related to the IBM Cognos service. IBM Cognos Administration. If you plan to install two or more components on the same computer. If you are upgrading from a previous release of IBM Cognos products. You must install the gateway on a computer that is also running a Web server. 64-bit installations The IBM Cognos BI gateway provides 32-bit libraries. © Copyright IBM Corp. Stop the IBM Cognos service for Application Tier Components first.” on page 59.

install the 32-bit version of the IBM Cognos gateway on a 32-bit Web server.x. even on a 64-bit computer.cannot load a 32-bit compiled library in a 64-bit compiled server. In that situation. To run graphical-mode installation. If you are upgrading IBM Cognos BI in an environment that includes earlier versions of other IBM Cognos BI products. Cognos Content Database as content store If you want to use Cognos Content Database as your content store. Also. The 32-bit mode allows you to run all reports. respect the mask. such as logs. the console attached to your UNIX computer must support a Java-based graphical user interface. you need to only install Cognos Content Database once. It does not affect the file permissions within the directories. Selecting which version you use is done using IBM Cognos Configuration after installation. included with the Application Tier Components. During installation. install the new version of IBM Cognos BI in a separate location from the other IBM Cognos BI product and configure the new version of IBM Cognos BI to operate independently of that product. you can install server components using a graphical user interface or by running a silent installation. you must select it in the installation wizard. After you upgrade the other product to a compatible version with IBM Cognos BI. whereas the 64-bit mode allows you to run only reports created for dynamic query mode. you can then configure the two products to operate together.and 64-bit versions. IBM Cognos BI respects the file mode creation mask (umask) of the account running the installation program. is provided in both 32. This affects only the installation directories. 120 IBM Cognos Business Intelligence Version 10. the report server component is set to use the 32-bit mode.x. run-time generated files. UNIX installations For UNIX operating system installations.1: Installation and Configuration Guide . However. All reports. Windows installations For Microsoft Windows operating system installations. Printer requirements To ensure that reports print properly on Windows. The report server component. Adobe Reader requires that you configure at least one printer on the operating system where Application Tier Components are installed. files from the disk are temporarily copied to this directory. Use umask 022 on the installation directory. such as IBM Cognos BI Controller Version 8. Also ensure that your computer has a TEMP system variable that points to the directory where you want to store temporary files. ensure that you have administrator privileges for the Windows computer you are installing on. IBM Cognos BI Planning Version 8. are sent as temporary PDF files to Adobe Reader for printing. By default. If you are installing components on several computers. or IBM Cognos BI Analysis for Microsoft Excel Version 8. regardless of the print format that you choose.2.x.

Installing and Configuring Server Components on Different Computers 121 . You must configure the gateway component last so that cryptographic keys are shared and secure communication can take place among the three components. Chapter 6. then Application Tier Components and then gateways. Configure and start the services in at least one location where you installed Content Manager before you configure other server components. The following diagram shows the sequence of the installation process for distributed components.Installation sequence for server components In a distributed installation. We recommend that you install and configure all server components before you install Microsoft Windows operating system components. the sequence in which you configure components is important. After planning and preparing your environment. install and configure Content Manager components. The server specified for the external dispatcher URI property on the gateway computer must be the last server component that you start. After server components are installed. you install and configure Framework Manager.

which involves installing one or more instances of each of the required server components (gateway. Do a basic installation first. such as configuring distributed components to communicate with each other.1: Installation and Configuration Guide . Distributed installation process workflow Recommendation .2. to get your distributed environment running before you customize your settings. Perform only the required configuration tasks. there are many different installation and configuration options that you can do to customize IBM Cognos BI so that it fits into your corporate infrastructure.Figure 9. Application Tier Components and Content Manager) and installing Framework Manager. 122 IBM Cognos Business Intelligence Version 10.Install and Configure the Basic Installation for Distributed Installations When you do a distributed installation.

The Content Manager computers must know the location of the content store. you must install components on your server and then configure them to work in your environment. and the configuration tool enables you to change default settings. and you can install Content Manager in a separate location than other components to enhance performance.xml file. To run an interactive-mode installation. using settings that apply to your environment. the location of other Content Manager components. You can choose to install server components in silent mode. you can add optional components and customize your configuration settings to better suit your business intelligence needs. The simplest and quickest way to get IBM Cognos BI running in your environment is ensuring that a basic installation works in your environment. install the software from an X Window System workstation. Installing and Configuring Server Components on Different Computers 123 . Installing and Configuring Content Manager You can install more than one Content Manager to ensure failover. Interactive Mode Unless you intend to complete a silent-mode installation. You must configure and then start the services on at least one computer where you installed Content Manager before you configure other server components or Framework Manager. This means that in a graphical user interface (GUI) the installer prompts you to provide information. Install Server Components in Interactive Mode For a complete installation. The sequence in which you configure computers is important. the console attached to your computer must support a Java-based graphical user interface. Run IBM Cognos Configuration in interactive mode the first time. an X terminal. you run the IBM Cognos installation and configuration programs in interactive mode. For more information.Later. You can automate the configuration of components by exporting the configuration settings from one computer to another as long as the installed components are the same. and the database that is used for notification. see “Installation sequence for server components” on page 121. or a PC or other system with X server software installed. and then running the configuration tool in silent mode. Chapter 6. Silent Mode You can automate the installation of components using response files and running the installation program in silent mode. The other option is to edit the cogstartup. Typically.

When the active Content Manager fails. It does not affect the file permissions within the directories. running and accessible before you configure other computers in your IBM Cognos environment. or where Content Manager is located in a separate location. We recommend umask 022 on the installation directory.In a distributed installation. each on a different computer. This ensures that the certificate authority service. This ensures that the certificate authority service. Rules for configuring In an installation where you have more than one Content Manager components. One Content Manager computer is active and one or more Content Manager computers are on standby. unsaved session data is lost. see the Administration and Security Guide. The standby Content Manager computers are for failover protection. For example. users may be prompted to log on. Also. see “Active and Standby Content Manager Components” on page 125. When another Content Manager becomes active. configure IBM Cognos BI to use compiled gateways instead of the default CGI gateway. a standby Content Manager computer becomes active and requests are directed to it. IBM Cognos BI respects the file mode creation mask (umask) of the account running the installation program. 124 IBM Cognos Business Intelligence Version 10. If the active Content Manager computer is not available because of a software or hardware failure.2. performance may be affected after failover. which is installed with Content Manager. For information about activating a Content Manager service. see “Installation sequence for server components” on page 121. or use ISAPI for IIS.1: Installation and Configuration Guide . For information about the sequence of the installation process for distributed components. at least one of the computers where you install Content Manager must be configured. at least one of the one Content Manager must be configured. Otherwise. using IBM Cognos Administration. Your installation may include more than one Content Manager. is available to issue certificates to other computers. is available to issue certificates to other IBM Cognos computers. use Apache Module for Apache Server or for IBM HTTP Server. You can designate another Content Manager computer as default active. the first Content Manager computer that you start becomes the default active Content Manager. respect the mask. Permissions You can install using either root or non-root authority. Rules for active Content Manager If you are installing multiple Content Manager components. However. run-time generated files. which is installed with Content Manager. This affects only the installation directories. running and accessible before you configure other components in your environment. such as logs. For information about active and standby Content Manager components. In installations with multiple Content Managers.

Installing and Configuring Server Components on Different Computers 125 . If you are installing components on several computers. the first Content Manager installed with IBM Cognos BI is the active one. If a dispatcher can no longer reach Content Manager. By default. When IBM Cognos BI is started. some features in IBM Cognos BI are new and may require configuration. from the active Content Manager. you need to only install Cognos Content Database once. However. This failover mechanism works because dispatchers and the active Content Manager routinely communicate with each other. The other installations of Content Manager remain in standby mode for continuing failover support. clear all components except Content Manager. Cognos Content Database If you want to use the Cognos Content Database as your content store. you must install Content Manager on a computer that supports IBM Cognos Series 7. use the disk for your operating system. such as the common symmetric key (used to encrypt and decrypt data). In the installation wizard. must select it in the installation wizard. which becomes the active Content Manager. you must ensure that the system clocks on the Content Manager computers are synchronized for successful failover between Content Managers. Active and Standby Content Manager Components You can install any number of installations of Content Manager. Chapter 6. a standby Content Manager becomes active and requests are directed to it. Install the Content Manager components To install Content Manager. The standby Content Managers retrieve cryptographic settings. If the active Content Manager is not available because of a software or hardware failure. unsaved session data is lost. although only one is active at any time. the dispatcher signals a standby Content Manager. If you are installing multiple Content Managers. These other Content Manager installations enter standby mode. the default Content Manager locks the content store from access by all other installations of Content Manager.Upgrading If you are upgrading from ReportNet or an earlier version of IBM Cognos BI. The other installations each act as a standby Content Manager. An IBM Cognos BI server administrator can change the default Content Manager and the active Content Manager at any time. When another Content Manager becomes active. When the active Content Manager fails. you can use the existing configuration data. users may be prompted to log on. The standby Content Manager components are for failover protection. PowerCubes If you plan to install IBM Cognos Transformer and you will be using PowerCubes that are secured against an IBM Cognos Series 7 namespace.

To mount the disk on HP-UX.2. For example. If installing from a download. type pfs_mount -t rrip <device><mount_dir> -o xlat=unix For example.1: Installation and Configuration Guide . 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. which supports more efficient scheduling of user threads.wss?uid=swg27037784). go to the location where the installation files were downloaded and extracted. If you are installing in a location with other IBM Cognos BI components. 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 disk from this drive. 2. On AIX. v When the installation is complete. use the existing JAVA_HOME environment variable. Procedure 1. do the following: v Add the pfs_mount directory in your path. 4.com/support/ docview. stop the IBM Cognos service. 126 IBM Cognos Business Intelligence Version 10. If installing from a disk. such as the Java that is provided by IBM. PATH=/usr/sbin/:$PATH export PATH v To start the required NFS daemons and run the daemons in the background. type bg pfs_mountd and then type bg pfsd v To mount the drive. Before you begin Go to the IBM Software Compatibility reports (www. On HP-UX. Set the JAVA_HOME environment variable to point to the installation location of your Java Runtime Environment (JRE). set the AIXTHREAD_SCOPE environment variable as follows: AIXTHREAD_SCOPE=S This sets the contention scope for user threads to system-wide. An example of the installation location of a Java Runtime Environment is /directory/java/java_version/jre. if you are using a servlet gateway. 3. 5. IBM Cognos BI requires a JVM. type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the disk. 6. If you are installing to a directory with other IBM Cognos BI components.ibm.Installing Content Manager on UNIX or Linux operating systems Use the following procedure to install Content Manager on a UNIX or Linux operating system. to run on a Linux operating system. Verify that you have the required patches installed on your computer before you install the product. mount the disk using Rock Ridge file extensions.

To start the installation wizard. v Do not configure IBM Cognos BI immediately because you must do other tasks first to ensure that your environment is properly set up. 9. run an unattended installation Chapter 17. the default installation location uses the Program Files (x86) directory.sh in the c10_location/bin64 directory. Windows 7.7. go to the operating system directory and then type . SHLIB_PATH Installing Content Manager on Windows operating systems Use the following procedure to install Content Manager on a Microsoft Windows operating system. click View for the appropriate log file. also select Cognos Content Database. and you receive error messages about missing openmotif libraries. do the following: v If you want to see the log files. “Using an unattended installation and configuration. you can use an unattended installation with the issetupnx command. In the Finish page of the installation wizard. 10. v When selecting components. LIBPATH v For HP-UX. If you are installing on Linux operating systems. You can later configure IBM Cognos BI using IBM Cognos Configuration by typing cogconfig. When installing in Japanese on UNIX or Linux. Append the c10_location/bin64 directory to the appropriate library path environment variable. v For Solaris and Linux. Installing and Configuring Server Components on Different Computers 127 . or Windows 2008 computers. Ensure that the IBM Cognos Configuration check box is clear. consider the following: Install Content Manager in a directory that contains only ASCII characters in the path name. 8. LD_LIBRARY_PATH v For AIX. v If you want to see late-breaking information about the product. Follow the directions in the installation wizard and copy the required files to your computer. If you install to this location. Japanese characters in messages and log files may be corrupted. and then start the installation wizard. v Click Finish. If you want to use the pre configured database.” on page 407. Some UNIX and Linux Web servers do not support non-ASCII characters in directory names. for example ja_JP. v When selecting the directory. you must install IBM Cognos BI in a different directory.PCK on Solaris). If you are installing IBM Cognos BI on a computer that has an earlier version of IBM Cognos BI and you want to keep the earlier version. select the check box for IBM Cognos Release Notes. clear all components except Content Manager. ensure that you run IBM Cognos Configuration as an Administrator. first set environment variables LANG=C and LC_ALL=C (where C is the language code. Chapter 6. If you do not use XWindows. For Windows Vista./issetup Note: When you use the issetup command with XWindows.

you must install IBM Cognos BI in a different directory. The language that you select determines the language of the user interface.wss?uid=swg27037784). select the check box for IBM Cognos Release Notes. consider the following: Install Content Manager in a directory that contains only ASCII characters in the path name. you can change the installation directory to something like C:\IBM\cognos\c10.ibm. v If you start IBM Cognos Configuration from the installation wizard. Verify that you have the required patches installed on your computer before you install the product. If you are installing IBM Cognos BI on a computer that has an earlier version of IBM Cognos BI and you want to keep the earlier version.exe. and double-click issetup. also select Cognos Content Database. If you are installing to a directory with other IBM Cognos BI components. do the following: v If you want to see the log files. Your scorecarding product can use the same Content Manager that is installed for the IBM Cognos BI server.2. you can install the product outside of the Program Files (x86) directory. click View for the appropriate log file. stop the IBM Cognos service. Procedure 1. 5. v Click Finish. ensure that you follow the additional tasks in this section to ensure that your environment is properly set up before you start the services.com/support/ docview. 2. Install Content Manager for IBM Cognos Metrics Manager If you are installing IBM Cognos Metrics Manager with the IBM Cognos BI server and you want to share resources. Some Microsoft Windows operating system Web servers do not support non-ASCII characters in directory names. Do one of the following: v Insert the IBM Cognos product disk. Follow the directions in the installation wizard to copy the required files to your computer. You can start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu.1: Installation and Configuration Guide . If the installation wizard does not open automatically. v Go to the location where the installation files were downloaded and extracted and then double-click issetup. clear all components except Content Manager. For example. v When selecting the directory. If you want to use the pre configured database. You can change the user interface to any of the installed languages after installation. 4. Select the language to use for the installation. v When selecting components. Before you begin Go to the IBM Software Compatibility reports (www. go to the operating system directory. v If you want to see late-breaking information about the product. If you 128 IBM Cognos Business Intelligence Version 10. All supported languages are installed. it is not necessary to install Content Manager from the IBM Cognos Metrics Manager disk. In the Finish page of the installation wizard. 3.Alternatively.exe.

IBMCognos fix packs are installed in the same location as the existing product. This validation determines whether you can replace the file. Insert the fix pack disk for the Windows operating system or go to the location where you downloaded and extracted the files. Before you begin Ensure that you do the following tasks before installing a Fix Pack. you must install it after you install the IBM Cognos components. 2. Installing Fix Packs on Windows operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product. stop it. v If the IBM Cognos service is running. Installing fix packs IBM provides interim maintenance packages that contain updates to one or more components in your IBM Cognos product. Installing and Configuring Server Components on Different Computers 129 . v Back up the content store database v Back up any files that you manually edited. You must install them on computers that have IBM Cognos components installed. update the new installation files with any changes from the backup copies of your customized files. compare both versions of the files. 4. If required. Install the fix packs that are appropriate for your product version. You may also want to install Metric Designer (see “Installing and Configuring Metric Designer” on page 192). If a fix pack becomes available after your IBM Cognos product has been deployed. install Content Manager for IBM Cognos Metrics Manager in a different location from Content Manager for the IBM Cognos BI server. Chapter 6. When you install the latest fix pack. before copying the customized files. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. open the component list file at c10_location\cmplst. Fix packs are available for download from IBM Support at http://www. Fix packs are cumulative.ibm. 3. If a fix pack is available when you are installing or upgrading your product.want your scorecarding product to operate independently of the IBM Cognos BI server. you must stop the service.com/support/us/en/. v If you are using Tomcat. save the configuration. and then start the IBM Cognos service.txt and check the line that starts with C8BISRVR_version=. Procedure 1. To check your version. and double-click the issetup. v Back up the directory structure.exe file. Return the deployed IBM Cognos product to service. Note: Fix packs are not standalone installations. and then start the service. it includes updates from all the previous fix packs. install the fix pack in the same location as the IBM Cognos components. To prevent errors. open IBM Cognos Configuration.

You must use a type 4 Java Database Connectivity (JDBC) driver to connect to your content store if you are using IBM DB2. and then start the IBM Cognos service. 130 IBM Cognos Business Intelligence Version 10. before copying the customized files. redeploy the IBM Cognos product to the application server.2. on each computer where you install Content Manager. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. 6. 4. This validation determines whether you can replace the file. or insert the disc if you have one. Installing IBM Cognos fix packs on UNIX or Linux operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product. 5. stop it. Doing this allows Content Manager to access the content store database. Set up database connectivity for the content store database If you are using a database other than Cognos Content Database or Microsoft SQL Server as the content store. update the new installation files with any changes from the backup copies of your customized files./issetup 3. Go to the location where the installation files are downloaded. type the following command . IBM Cognos fix packs are installed in the same location as the existing product. Set up database connectivity for an IBM DB2 content store This procedure describes how to set up database connectivity for a DB2 content store. To start the installation wizard. 5. v If the IBM Cognos service is running. If required. 2. or both. Return the deployed IBM Cognos product to service.v If you are running the IBM Cognos product on an application server other than Tomcat. or Java Database Connectivity (JDBC) drivers. redeploy the IBM Cognos product to the application server. v If you are running the IBM Cognos product on an application server other than Tomcat. Procedure 1. save the configuration. repeat these steps for all remaining IBM Cognos servers. v Back up the content store database v Back up any files that you manually edited. you may have to install database client software. Before you begin Ensure that you do the following tasks before installing a Fix Pack. open IBM Cognos Configuration. If you have a distributed environment. repeat these steps for all remaining IBM Cognos servers. compare both versions of the files. If you have a distributed environment.1: Installation and Configuration Guide . v If you are using Tomcat. To prevent errors. v Back up the directory structure. You must perform this procedure on each computer where you install Content Manager.

you can run the script by entering the following command: Chapter 6. In the Explorer window.db2. If you are using a different port number.5 fix pack 2. db2jcc. and click Generate DDL. In the Properties window. 7.jar com. Procedure Copy the following files from DB2_installation\sqllib\java directory to the c10_location\webapps\p2pd\WEB-INF\lib directory: v The universal driver file. The script file is called a DDL file. Ensure that the Type is DB2 database. for the Database name property. or Windows operating systems. The default configuration is for an IBM DB2 database. Right-click Content Store. 4. 3. Click the Value field next to the User ID and password property and then click the edit icon.jar. Start IBM Cognos Configuration. use the driver version from Linux. In the Database server and port number field. UNIX. It does not require the DB2 client to be installed. Tip: To check the driver version. ensure you use that value. Click Details to record the location of the generated DDL file. For DB2 on z/OS. 2. If you use the IBM DB2 command-line interface. Important: Do not use a name longer than eight characters and use only letters. numbers. use db2jcc_license_cu. Where. What to do next Use this script to create a database in IBM DB2. For more information about using a DDL file. 5. type the name for your content store database. Procedure 1. The script is created in the c10_location\configuration\schemas\content\db2 directory. localhost:50000. see your IBM DB2 documentation.jar v The license file: For DB2 on Linux. If you are connecting to DB2 on z/OS.sql is created. For example. 6.1 fix pack 5 or version 9. UNIX. click Content Store.The type 4 driver is considered an independent product. Installing and Configuring Server Components on Different Computers 131 . 50000 is the default port number that is used by IBM DB2. or Windows version 9. and hyphens in the name.jar. Type the appropriate values and click OK.DB2Jcc -version Generating a script file to create a database for a DB2 content store: You can generate a script file to automatically create the content store in IBM DB2 on all platforms. enter the name of your computer and port number on which DB2 is running. run the following command: java -cp path\db2jcc. The DDL file named createDB. use db2jcc_license_cisuz. under Data Access > Content Manager.ibm. underscores.jcc.

Not all of the parameters listed are in the script. v CMSCRIPT_TABLESPACE is no more than 6 characters. Table 31. the content store is used for notifications.sql Creating tablespaces for a content store on DB2 for z/OS: A database administrator must run scripts to create a set of tablespaces required for the content store database. About this task Ensure that you use the naming conventions for DB2 on z/OS.2. b. For more information. Open the original tablespace_db2zOS. Parameter names and description for the content store tablespace script Parameter name CMSCRIPT_STOGROUP CMSCRIPT_DATABASE CMSCRIPT_CS_ID Description Specifies the name of the storage group. but some might be added in the future. You can create separate databases for each. Go to the directory that contains the scripts: c10_location/configuration/schemas/content/db2zOS 3. For example. The reason for the exception is that when the two parameters are concatenated the character length can be no more than 8. There are two exceptions to the character length limit: v CMSCRIPT_CS_ID is no more than 2 characters. human tasks. Make a backup copy of the tablespace_db2zOS. connect to databasename. all names of parameters must start with a letter and the length must not exceed eight characters. By default.sql script file and save the file to another location.1: Installation and Configuration Guide . Add a connection statement to the beginning of the script.sql script file. 2. 132 IBM Cognos Business Intelligence Version 10. Connect to the database as a user that has privileges to create and drop tablespaces and to allow execution of SQL statements. The ID must not be longer than 2 characters. Modify the scripts to replace the placeholder parameters with ones that are appropriate for your environment. 4. Use the following table to help you to replace the generic parameters with ones appropriate for your environment. a.db2 -tvf createDB. see the IBM DB2 Information Center. Specifies the subsystem identification for the content store database. Procedure 1. For example. and annotations. Specifies the name of the content store database.

sql script file and replace the placeholder parameters with values that are appropriate for your environment. Make a copy of the rightsGrant_db2zOS. open the original rightsGrant_db2zOS. if you set up your clp. Auxiliary tables are not included. Make a backup copy of the NC_TABLESPACES. In the remote access tool. c.sql 6.sql script file and save the file to another location. CMSCRIPT_LARGE_BP Specifies the name of the large buffer pool allocated for especially large objects. For example. Installing and Configuring Server Components on Different Computers 133 . go to the c10_location/configuration/ schemas/delivery/zosdb2 directory. Save and then run the script. CMSCRIPT_USERNAME Specifies the user account that accesses the content store database. For example.properties file and your DB2 alias in your profile or tcshrc script file. b. Grant the IBM Cognos user rights to the tablespaces that were created when you ran the tablespace_db2zOS. Save and run the script.sql 7. CMSCRIPT_REGULAR_BP Specifies the name of the regular size buffer pool allocated for regular and large objects. Add a connection statement to the beginning of the script. 5. a. This bufferpool is the 32 KB buffer pool that was created when the database administrator created the content store database on the z/OS system.sql script file and store it in another location.sql file script: a. Parameter names and description for the content store tablespace script (continued) Parameter name CMSCRIPT_TABLESPACE Description Specifies the name of the tablespace that contains all of the base tables in the content store. For example. d. connect to databasename user username using password. Chapter 6. db2 -tvf rightsGrant_db2zOS. To create the notification tablespaces. This bufferpool is the 16 KB buffer pool that was created when the database administrator created the content store database on the z/OS system. The name cannot be longer than 6 characters.Table 31. Ensure that you use the same values that you used when you allocated resources to the buffer pools and user account. type the following command to run the script: db2 -tvf tablespace_db2zOS.

For example. To create the annotations tablespaces. a. go to the c10_location/configuration/ schemas/hts/zosdb2 directory. Open the NC_CREATE_DB2. go to the c10_location/configuration/ schemas/ans/zosdb2 directory. Save the script. but might be added in the future.sql d. d. Table 34.sql script file and save the file to another location.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. c.2. db2 -tvf NC_TABLESPACES. Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG Description The name of the database.sql script file and replace the NCCOG placeholder parameter with the name of the notification database. See the script for a complete list of the parameters required. Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the database. 8. Save and run the script. e. 9. However. Tablespace parameter names and descriptions for the DB2 notification database on z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the notification database. See the script for a complete list of the parameters required. Specifies the name of the storage group. Open the original HTS_TABLESPACES. Specifies the name of the storage group. Save and run the script. Open the HTS2_CREATE_Db2zos. Specifies name of the 32 k buffer pool.sql script file and use the following table to help you to replace the placeholder parameters with ones appropriate for your environment. The Job and Scheduling Monitor services will automatically run the script. Table 32. Table 33. Specifies the name of the buffer pool. c.b. Save and run the script. e. Not all of the parameters listed are in the script.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. 134 IBM Cognos Business Intelligence Version 10. To create the human tasks tablespaces. Make a backup copy of the HTS_tablespaces. you may choose to run it yourself.1: Installation and Configuration Guide . Open the original NC_TABLESPACES. b.

a. go to the ORACLE_HOME/jdbc/lib directory. Copy the following files to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed. If you are using Oracle 11g. 2.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. Table 35. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description The name of the database. you must have ojdbc14. On the computer where the Oracle client is installed. go to the Informix_location/ sqllib/java directory. Open the original ANN_TABLESPACES. Open the ANS2_CREATE_Db2zos. The files are available from an Oracle client or server install. Chapter 6. Set up database connectivity for an Informix content store This procedure describes how to set up database connectivity for an Informix content store.sql script file and save the file to another location. You must perform this procedure on each computer where you install Content Manager. c. and can also be downloaded from the Oracle technology Web site. you must have ojdbc5. 2.jar. Save and run the script. e. Procedure 1. The name of the 32 k buffer pool. You must perform this procedure on each computer where you install Content Manager. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG Description The name of the database. Installing and Configuring Server Components on Different Computers 135 . Save and run the script.jar. d. See the script for a complete list of the parameters required.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. The name of the storage group. See the script for a complete list of the parameters required. Copy the correct library file for your version of the Oracle client to the c10_location\webapps\p2pd\WEB-INF\lib directory on the computer where Content Manager is installed and where notification is sent to an Oracle database. b. Make a backup copy of the ANN_TABLESPACES. Table 36. Set up database connectivity for an Oracle content store This procedure describes how to set up database connectivity for an Oracle content store. On the computer where Informix is installed. Procedure 1. If you are using Oracle 10g.

2. Additional setup is required before you can configure IBM Cognos BI. copy the Java Database Connectivity (JDBC) drivers to the appropriate location before you start the configuration tool. Before you begin Before starting IBM Cognos Configuration.1: Installation and Configuration Guide . Start IBM Cognos Configuration Use IBM Cognos Configuration to configure IBM Cognos Business Intelligence components and to start and stop IBM Cognos services if you are using the default Tomcat servlet container.sh If IBM Cognos Configuration does not open.lang. On Microsoft Windows./cogconfig.Lang. Ensure that user or service account used to run IBM Cognos has been set up.unsupportedClassVersionError message. ensure that you set the DISPLAY environment variable. do not start IBM Cognos Configuration in the last page of the installation wizard. go to the c10_location/bin64 directory and then type the following command: . For example.jar Set up database connectivity for a Sybase content store This procedure describes how to set up database connectivity for a Sybase content store. If you see a Java.v the universal driver file. Procedure 1. you must update your Java environment. On the computer where Sybase is installed. Copy the jconn3. For example.unsatisfied link message.jar file to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed and where notification is sent to a Sybase database. You must perform this procedure on each computer where you install Content Manager. 2. if you use a database server other than Microsoft SQL or Cognos Content Database for the content store. On a Microsoft Windows operating system. ensure that the operating environment is properly set up. start IBM Cognos Configuration as an Administrator. db2jcc_license_cisuz. verify that you are using a supported version of Java. 136 IBM Cognos Business Intelligence Version 10. db2jcc.2. For example. Windows 7. If you see a JAVA. go to the Sybase_location/ jConnect-6/classes directory. and have installed the product to the Program Files (x86) directory. If you are using a Windows Vista. click Start > IBM Cognos Configuration. or Windows 2008 computer. you can start IBM Cognos Configuration in the last page of the installation wizard only if additional setup is not required.jar v the license file. ensure that all environment variables have been set. ensure that you are using a 64-bit version of Java. On UNIX or Linux operating systems. On UNIX or Linux operating systems. Procedure 1.

click Local Configuration. start IBM Cognos Configuration. 6. If you are connecting to a database on DB2 on z/OS. for the Database name property. In the Properties window. Procedure 1. ensure you use that value. you must use an enterprise-level database for your content store. and then click the edit icon. For example. next to Advanced properties. Add all of the parameters except CMSCRIPT_USERNAME. If you have been using Cognos Content Database in a test or proof-of-concept system. you can use the features in the administration portal to back up and archive the data before moving to an enterprise-level database in your production environment. enter the name of your computer and port number on which DB2 is running. In the Explorer window. If you are using a different port number. After you set the database connection properties. you can keep ReportNet or the earlier version running with the original data. b. type the name of the database or the database alias. click inside the Value box. click Content Store. 5. For more information. In a production environment. Setting database connection properties for a DB2 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. under Data Access. In the Explorer window. see the topic about deploying the entire content store in the Administration and Security Guide. Ensure that you used one of the supported database servers to create the content store. After you save the configuration and start the IBM Cognos service. Click Add to add the parameters that you used to create the tablespaces.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. Chapter 6. the data in the content store is automatically upgraded and cannot be used by the earlier version. you can test the connection between Content Manager and the content store. In the Properties window. Content Manager uses the database logon to access the content store. In the Database server and port number field. If you are connecting to a database on DB2 on z/OS: a. Content Manager. 50000 is the default port number used by DB2. c. Change the logon credentials to specify a valid user ID and password: v Click the Value box next to the User ID and password property and then click the edit button when it appears. 4. 2. v Type the appropriate values and click OK. By using a copy of the original database with the new version. If you are upgrading from ReportNet or an earlier version of IBM Cognos BI. In the location where you installed Content Manager. localhost:50000. 3. Installing and Configuring Server Components on Different Computers 137 . configure IBM Cognos BI to point to a copy of the existing content store database. ensure that you specify the same user ID as the value you specified for CMSCRIPT_USERNAME when you created the tablespaces.

Informix. Change the logon credentials to specify a valid user ID and password: v Click the Value box next to the User ID and password property and then click the edit icon when it appears. Oracle. To test the connection between Content Manager and the content store database. 6. To add the parameters that you used to create the tablespaces. Setting Database Connection Properties for a DB2 Content Store on z/OS You must specify the database server information to ensure that Content Manager can connect to the database you use for the content store. click Test. type a value.2. Setting database connection properties for a Microsoft SQL Server. type the name of the database or the database alias. for the Database server and port number property. To test the connection between Content Manager and the content store database.7. 2. In the Explorer window. Procedure 1. start IBM Cognos Configuration. 138 IBM Cognos Business Intelligence Version 10. and then click the edit icon. The Value . 9. right-click Content Store and click Delete. click Save. click Add. Content Manager connects to the database. From the File menu. In the Explorer window. for the Database name property. from the Actions menu. 2. click Save. Ensure that you specify the same user ID as the value you specified for CMSCRIPT_USERNAME when you created the tablespaces. and creates and populates a table. click inside the Value box.Advanced properties dialog box appears. click Local Configuration. 3. From the File menu. under Data Access. In the location where you installed Content Manager. The table is not deleted and is used each time that the test is repeated. 4. start IBM Cognos Configuration. checks the database permissions. On the computer where you installed Content Manager. 8. This tests the connection between Content Manager and the content store database. next to Advanced properties. Content Manager. 10. All of the parameters except CMSCRIPT_USERNAME are added. click Content Store. under Data Access. click Test. In the Properties window.1: Installation and Configuration Guide . 5. Content Manager. v Type the appropriate values and click OK. from the Actions menu. 7. In the Properties window. 8. The logon credentials are immediately encrypted. Procedure 1. using host:port syntax. To use a type 4 JDBC connection. In the Explorer window. or Sybase 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.

switch to another listener if the first listener fails. type the appropriate values for the Database server and port number and Database name properties. a connection to the default instance is created. To configure logon credentials. and database name. For example. it cannot be used by an older version. v If you use a Sybase database. v If you use an Informix database. select Oracle database (Advanced). and balance connection requests among dispatchers. you must use a different content store for each version. you can choose to use a port number. For example. The properties specified for the named instance. you must specify the instance name as a Java Database Connectivity (JDBC) URL property or a data source property. type the Oracle Net8 keyword-value pair for the connection. you can type localhost\instance1. Database. Here is an example: jdbc:JSQLConnect://localhost\\instance1/user=sa/ more properties as required To connect to a named instance. 5. type the appropriate values for the Database server with port number or instance name and Database name properties. are used to create a JDBC URL.This step deletes the connection to the default resource. In the Properties window. Right-click Content Manager. provide the values for your database type: v If you use a Microsoft SQL Server database. for the Database specifier property. automatically reconnect to the database if the connection fails. 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 BI uses enterprise-oriented Oracle features to select a listener. To connect to a named instance. For the Database server with port number or instance name property. type a name for the resource. When a content store is used by a new version of IBM Cognos BI. type the appropriate values for the Database server and port number and SID properties. If no instance name property is specified. Content Manager can access only one content store. specify a user ID and password: Chapter 6. or a named instance as the value for the Database server with port number or instance name property. 3. such as 1433. and then click New resource. If an instance name is not specified. If you installed more than one version of IBM Cognos BI. v If you use an Oracle database. 4. Tip: If you want to use an Oracle Net8 keyword-value pair to manage the database connection. a connection to the default instance is created. along with the user ID and password. type the appropriate values for the Database server and port number and Database name properties. In the Type box. 7. you must specify the instance name. 6. For a Microsoft SQL Server database. select the type of database and click OK. v If you use an advanced Oracle database. balance connection requests among listeners. Installing and Configuring Server Components on Different Computers 139 . include the instance name if there are multiple instances of Microsoft SQL Server. you can type localhost\instance1. In the Name box.

” on page 331). type the user ID of the account under which the instance of the content store runs. or change global settings (see “Changing Global Settings” on page 272). and the database that is used for notification. 140 IBM Cognos Business Intelligence Version 10. After installing Content Manager on the computers you are using for failover protection. The table is not deleted and is used each time that the test is repeated. click Save. click the Value column for Advanced properties and then click the edit icon. click Local Configuration. To test the connection between Content Manager and the content store database. checks the database permissions. you must configure Content Manager on those computers. such as the Application Tier Components computer and gateway computers. create the advanced property CMSCRIPT_CS_ID and specify the account under which the instance runs: v In the Explorer window. v In the Name column. click Test. If you host more than one content store database on an Informix instance. the other Content Manager computers. you can configure IBM Cognos BI components to use an authentication provider (see Chapter 13. If the connection properties are not specified correctly. v In the Properties window. enable and disable services (see “Enable and Disable Services” on page 233) on the Content Manager computers. and creates and populates a table. Content Manager connects to the database.v Click the Value box next to the User ID and password property and then click the edit icon when it appears. You can then perform the required configuration tasks on other computers. From the File menu. you must list all Content Manager URIs on each Content Manager computer. you cannot start the IBM Cognos services. type CMSCRIPT_CS_ID v In the Value column. v Type the appropriate values and click OK.Advanced properties dialog box. the certificate authority service is available to issue certificates to other computers.1: Installation and Configuration Guide . you can continue to configure the Content Manager computers by changing the default property settings (see “Changing Default Configuration Settings” on page 222) so that they better suit your environment. The logon credentials are immediately encrypted. “Configuring IBM Cognos Components to Use an Authentication Provider. Use a different user account for each instance of Informix content store database. Results Content Manager can now create the required tables in the content store when you start the IBM Cognos service for the first time. Configure Environment Properties for Content Manager Computers The Content Manager computers must know the location of the content store. After you complete the required configuration tasks and start the IBM Cognos BI service. For example. 8. 10. v In the Value . Otherwise. If you installed more than one Content Manager. 9.2. from the Actions menu. click Add.

v In the blank row of the table. start IBM Cognos Configuration. In the Explorer window. v In the blank row of the table. Configuring the active Content Manager The Content Manager computers must know the location of the content store. click Save. start IBM Cognos Configuration. From the File menu. In the Explorer window. and then click the edit button. and the database that is used for notification. Specify the URIs for the other Content Manager computers: v In the Value . In the Properties window. Do not delete the first value in the table.Note that if you change global settings on one Content Manager computer. under Security. you must make the same changes on the other Content Manager computers. and the database that is used for notification. You must include all Content Manager URIs in the list. In the Properties window. 7. Installing and Configuring Server Components on Different Computers 141 .Content Manager URIs dialog box. v Click OK. On the Content Manager computer that you want to designate as the default active Content Manager. click Cryptography. 2. Configuring standby Content Managers The Content Manager computers must know the location of the content store. This value identifies the local Content Manager computer and is required. Specify the URIs for the other Content Manager computers: v In the Value . 5. In the Explorer window. set Store symmetric key locally to True. Replace the localhost portion of the URI with a host name or IP address.Content Manager URIs dialog box. click Environment. click Add. 4. This value identifies the local Content Manager computer and is required. In the Properties window. 4. 3. 6. 5. click the value for Content Manager URIs and then click the edit button. Tip: Use the computer with the highest processor speed for the default active Content Manager. 3. All URI properties must use the the same format: all host names or all IP addresses. On the standby Content Manager computer. Procedure 1. click Environment. Ensure that you already configured the Environment properties on at least one Content Manager computer and that IBM Cognos BI components are running on that computer. click the value for Content Manager URIs. click and then type the full URI of the Content Manager computer. the other Content Manager computers. Do not delete the first value in the table. 2. click and then type the full URI of the Content Manager computer. the other Content Manager computers. Chapter 6. click Add. under CSK settings. Procedure 1. v Repeat the previous two bulleted steps for each URI to be added.

In the Explorer window. type the appropriate value for the default sender account. the default account is used and notifications will not work properly. You must also change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. Tip: If logon credentials are not required for the SMTP server. 5. Type the appropriate values in the Value . 2. Ensure that the values for all of the properties match what you configured on the default active Content Manager computer. 10. In the Explorer window. click OK.1: Installation and Configuration Guide . Ensure that the default user name has been removed. ensure that the Gateway URI on report servers and notification servers specifies an accessible Web server hosting IBM Cognos content. click Save.Account and password dialog box and then click OK. From the File menu. you must configure a connection to a mail server account. you must change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. If you have mobile users accessing links remotely. under Data Access > Content Manager. under Security > Cryptography. Otherwise. v Repeat the previous two bulleted steps for each URI to be added. click Content Store. consider using an external URI. 9. 3. for the SMTP mail server property. 8. 4. Ensure that all cryptographic settings match what you configured on the default active Content Manager computer. Specify a Connection to a Mail Server Account If you want to send reports by email. 6. Click the Value box next to the Account and password property and then click the edit button when it appears. v Click OK. Procedure 1. In the Properties window. You must include all Content Manager URIs in the list. When you are prompted for confirmation to leave this property blank. Tip: To be able to open reports that are sent as links. 7.Replace the localhost portion of the URI with a host name or IP address. Tip: To be able to open reports that are sent by email.2. click Notification. All URI properties must use the the same format: all host names or all IP addresses. under Data Access. In the Explorer window. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. the default cryptographic provider. In the Properties window. click Cognos. type the host name and port of your SMTP (outgoing) mail server. remove the default information for the Account and password property. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. 142 IBM Cognos Business Intelligence Version 10.

However. Before you begin Ensure that user or service account is set up. Start IBM Cognos Configuration. IBM Cognos Configuration checks the common symmetric keys (CSK) availability. Right-click Authentication. otherwise you cannot start the IBM Cognos service. Procedure 1. for the Namespace ID property. 3. 7. Enable Security By default. and click New Resource > Namespace. In the IBM Cognos Configuration Explorer window. In the Properties window. click Test. you can start the Content Manager computer. click Security >Authentication > Cognos. From the File menu. Start Content Manager After you have set the database connection properties for the content store. specify a unique identifier for the namespace. and select False. 2. In the Explorer window right-click Notification and click Test. Chapter 6. 3. tests the namespace configuration. Installing and Configuring Server Components on Different Computers 143 . click the appropriate namespace type and then click OK. you must disable anonymous access and configure IBM Cognos BI to use an authentication provider. or do not want to set up a mail server account immediately. Ensure that you save your configuration. a message appears indicating that configuration files were detected and upgraded to the new version. Test the mail server connections. Click the Value box for Allow Anonymous Access. You can safely ignore the warning. see “Configure a User Account or Network Service Account for IBM Cognos Business Intelligence” on page 52. The new authentication provider resource appears in the Explorer window. In the Name box. and tests the connections to the content store and other resources. IBM Cognos Business Intelligence allows anonymous access.6. In the Type list. type a name for your authentication namespace. 4. 6. For information. when you save the configuration and then you start the services in IBM Cognos Configuration. If you are upgrading. If you want to use security in your IBM Cognos BI environment. click Save. 2. From the Actions menu. you will see a warning message when the mail server connection is tested. 5. Results If you do not plan to send reports by email. IBM Cognos Business Intelligence tests the mail server connection. under the Authentication component. Procedure 1. you are not required.

However. This action starts all installed services that are not running and registers the IBM Cognos service on Windows. It may take a few minutes for the IBM Cognos service to start. depending on your environment. IBM Cognos BI uses the existing configuration data for the Application Tier Components computers. Do not start the service until all tests pass. click Start. 144 IBM Cognos Business Intelligence Version 10. if required Create a metric package Install the Application Tier Components You can install Application Tier Components on one or more computers. if available __ v Set up database connectivity for the reporting database __ v Start IBM Cognos Configuration __ v Configure environment properties for Application Tier computers __ v Start the Application Tier components __ v __ v __ v __ v Test the Application Tier components Create the metric store database Set up the database client for the metric store.2. Perform the following tasks to install and configure the Application Tier Components: __ v Install the Application Tier Components __ v Install Application Tier Components for IBM Cognos Metrics Manager.Tip: If Test is not available for selection. You can test some components individually by right-clicking the component in the Explorer panel and selecting Test. if required __ v Install fix packs. From the Actions menu. Open a Web browser. If the test fails. http://host_name:port/p2pd/servlet The default value for host_name:port is localhost:9300. Test that Content Manager is running by typing the URI for the active Content Manager.1: Installation and Configuration Guide . Test the Content Manager Installation You can test the installation using a Web browser. For example. if you installed the Application Tier Components in a new location. 4. 5. reconfigure the affected properties and then test again. If you are upgrading from ReportNet or an earlier version of IBM Cognos BI. click Local Configuration. Installing and Configuring Application Tier Components You can install the Application Tier Components on different computers or on the same computer. Procedure 1. Content Manager is available when the State value is Running. 2. in the Explorer window. you must configure the environment properties.

Installing the Application Tier Components on UNIX or Linux operating systems You can install Application Tier Components on one or more computers. the report server component is set to use the 32-bit mode. included with the Application Tier Components. to run on a Linux operating system.and 64-bit versions.ibm. regardless of the print format that you choose. Printer Requirements To ensure that reports print properly on a Microsoft Windows operating system. such as the Java that is provided by IBM. 64-bit Installations The report server component.wss?uid=swg27037784). Before you begin Go to the IBM Software Compatibility reports (www. Adobe Reader requires that you configure at least one printer on the operating system where Application Tier Components are installed. stop the IBM Cognos service. if you are using a servlet gateway. set the AIXTHREAD_SCOPE environment variable as follows: AIXTHREAD_SCOPE=S This sets the contention scope for user threads to system-wide. By default. If you are installing in a location with other IBM Cognos BI components. 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. is provided in both 32. The 32-bit mode allows you to run all reports. Installing and Configuring Server Components on Different Computers 145 . Procedure 1. Selecting which version you use is done using IBM Cognos Configuration after installation. 4. are sent as temporary PDF files to Adobe Reader for printing. which supports more efficient scheduling of user threads. depending on your environment. 3. If you are installing to a directory with other IBM Cognos BI components.com/support/ docview. IBM Cognos BI requires a JVM. whereas the 64-bit mode allows you to run only reports created for dynamic query mode. even on a 64-bit computer. use the existing JAVA_HOME environment variable. An example of the installation location of a Java Runtime Environment is /directory/java/java_version/jre. 2. Set the JAVA_HOME environment variable to point to the installation location of your Java Runtime Environment (JRE). On AIX. All reports.Ensure that the computer where you installed the active Content Manager is configured and available before you configure Application Tier Components computers. Verify that you have the required patches installed on your computer before you install the product. Chapter 6.

9. for example ja_JP. run an unattended installation (see “Use a response file from an installation on another computer” on page 408). Japanese characters in messages and log files may be corrupted. type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the disk. Ensure that the IBM Cognos Configuration check box is clear. Follow the directions in the installation wizard and copy the required files to your computer. When installing in Japanese on UNIX or Linux.5. select the check box for IBM Cognos Release Notes. 6. and you receive error messages about missing openmotif libraries. you can use an unattended installation with the issetupnx command. and then start the installation wizard.2. To start the installation wizard. v When the installation is complete. You can later configure IBM Cognos BI using IBM Cognos Configuration by typing cogconfig. Some UNIX and Linux Web servers do not support non-ASCII characters in directory names.1: Installation and Configuration Guide . v When selecting components. do the following: v If you want to see the log files. go to the location where the installation files were downloaded and extracted. clear all components except Application Tier Components.sh in the c10_location/bin64 directory. For example. consider the following: Install Application Tier Components in a directory that contains only ASCII characters in the path name.PCK on Solaris). v Do not configure IBM Cognos BI immediately because you must do other tasks first to ensure that your environment is properly set up. 8. click View for the appropriate log file. If installing from a disk. go to the operating system directory and then type . 7. 146 IBM Cognos Business Intelligence Version 10. If installing from a download. In the Finish page of the installation wizard. If you are installing on Linux operating systems./issetup Note: When you use the issetup command with XWindows. PATH=/usr/sbin/:$PATH export PATH v To start the required NFS daemons and run the daemons in the background. mount the disk using Rock Ridge file extensions. v When selecting the directory. do the following: v Add the pfs_mount directory in your path. type pfs_mount -t rrip <device><mount_dir> -o xlat=unix For example. type bg pfs_mountd and then type bg pfsd v To mount the drive. v If you want to see late-breaking information about the product. To mount the disk on HP-UX. first set environment variables LANG=C and LC_ALL=C (where C is the language code. If you do not use XWindows. 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 disk from this drive.

v Click Finish. the default installation location uses the Program Files (x86) directory. v When selecting components. select the check box for IBM Cognos Release Notes. or Windows 2008 computers. Chapter 6. v For Solaris and Linux. and double-click issetup. v When selecting the directory. you can install the product outside of the Program Files (x86) directory. If the installation wizard does not open automatically. Select the language to use for the installation. ensure that you follow the additional tasks in this section to ensure that your environment is properly set up before you start the services. SHLIB_PATH Installing the Application Tier Components on Windows operating system You can install Application Tier Components on one or more computers. stop the IBM Cognos service. 3. The language that you select determines the language of the user interface. v Click Finish. you can change the installation directory to something like C:\IBM\cognos\c10. In the Finish page of the installation wizard. 4. For Windows Vista. do the following: v If you want to see the log files. Some Web servers do not support non-ASCII characters in directory names. v Go to the location where the installation files were downloaded and extracted and then double-click issetup. You can change the user interface to any of the installed languages after installation. consider the following: Install Application Tier Components in a directory that contains only ASCII characters in the path name. Procedure 1. 2. You can start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu. Alternatively.exe. v If you start IBM Cognos Configuration from the installation wizard. v If you want to see late-breaking information about the product. 10. 5. Follow the directions in the installation wizard and copy the required files to your computer. For example. If you are installing to a directory with other IBM Cognos BI components. Installing and Configuring Server Components on Different Computers 147 . Windows 7. All supported languages are installed. Do one of the following: v Insert the IBM Cognos product disk. clear all components except Application Tier Components. click View for the appropriate log file.exe. Append the c10_location/bin64 directory to the appropriate library path environment variable. go to the operating system directory. depending on your environment. If you install to this location. LD_LIBRARY_PATH v For AIX. LIBPATH v For HP-UX. ensure that you run IBM Cognos Configuration as an Administrator.

txt and check the line that starts with C8BISRVR_version=. and double-click the issetup.exe file. When you install the latest fix pack. you must install it after you install the IBM Cognos components. Procedure 1. it includes updates from all the previous fix packs. v If the IBM Cognos service is running. v Back up the directory structure. Insert the fix pack disk for the Windows operating system or go to the location where you downloaded and extracted the files.2. Installing Fix Packs on Windows operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product. and then start the service. 2. You must install them on computers that have IBM Cognos components installed. 148 IBM Cognos Business Intelligence Version 10. If you want your scorecarding product to operate independently of the IBM Cognos BI server.com/support/us/en/. v Back up the content store database v Back up any files that you manually edited.1: Installation and Configuration Guide . you must install the Application Tier Components for IBM Cognos Metrics Manager in the same location as the Application Tier Components for the IBM Cognos BI server. Before you begin Ensure that you do the following tasks before installing a Fix Pack. open the component list file at c10_location\cmplst. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. Fix packs are cumulative. To check your version.ibm. If a fix pack is available when you are installing or upgrading your product.Install Application Tier Components for IBM Cognos Metrics Manager If you are installing IBM Cognos Metrics Manager with the IBM Cognos BI server and you want to share resources. Installing fix packs IBM provides interim maintenance packages that contain updates to one or more components in your IBM Cognos product. If a fix pack becomes available after your IBM Cognos product has been deployed. Note: Fix packs are not standalone installations. IBMCognos fix packs are installed in the same location as the existing product. install the Application Tier Components for IBM Cognos Metrics Manager in a different location from the Application Tier Components for the IBM Cognos BI server. install the fix pack in the same location as the IBM Cognos components. Install the fix packs that are appropriate for your product version. You may also want to install Metric Designer (see “Installing and Configuring Metric Designer” on page 192). Fix packs are available for download from IBM Support at http://www. you must stop the service. stop it.

open IBM Cognos Configuration. Installing and Configuring Server Components on Different Computers 149 . This validation determines whether you can replace the file. Return the deployed IBM Cognos product to service. repeat these steps for all remaining IBM Cognos servers. redeploy the IBM Cognos product to the application server. compare both versions of the files. Depending on the data source and query mode. the required software might include database clients. Return the deployed IBM Cognos product to service. before copying the customized files. v If the IBM Cognos service is running. Procedure 1. save the configuration. 4. v If you are running the IBM Cognos product on an application server other than Tomcat. redeploy the IBM Cognos product to the application server. update the new installation files with any changes from the backup copies of your customized files. Go to the location where the installation files are downloaded. or insert the disc if you have one. If required. you must install additional software for your data sources on the same computer that hosts the report server. 2. IBM Cognos fix packs are installed in the same location as the existing product. open IBM Cognos Configuration. and then start the IBM Cognos service. If required. compare both versions of the files. 6. or both./issetup 3. before copying the customized files. and then start the IBM Cognos service. Before you begin Ensure that you do the following tasks before installing a Fix Pack. If you have a distributed environment. To prevent errors. stop it. or Java Database Connectivity (JDBC) driver files. 5. type the following command . v Back up the directory structure. v If you are running the IBM Cognos product on an application server other than Tomcat. save the configuration. Set up database connectivity for reporting databases To support communication between IBM Cognos Business Intelligence and the data sources. update the new installation files with any changes from the backup copies of your customized files.3. v If you are using Tomcat. If you have a distributed environment. This validation determines whether you can replace the file. 5. v If you are using Tomcat. To prevent errors. repeat these steps for all remaining IBM Cognos servers. v Back up the content store database v Back up any files that you manually edited. 4. Chapter 6. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. To start the installation wizard. Installing IBM Cognos fix packs on UNIX or Linux operating systems Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product.

To review a list of environments supported by the IBM Cognos Business Intelligence. ensure that you use the 32-bit client libraries to connect to the data source to use the compatibility query mode. Dynamic query mode Dynamic query mode provides communication to data sources using Java/XMLA connections. Java/XMLA connectivity optimizes access by providing customized and enhanced MDX for the specific source and version of your OLAP technology and it harnesses the smarts of the OLAP data source. see the IBM Cognos Business Intelligence Dynamic Query Guide. Metric Designer.For IBM Cognos Business Intelligence.1: Installation and Configuration Guide . including the data source versions supported by the dynamic query mode. If the data source is 64-bit. A type 4 JDBC driver converts JDBC calls directly into the vendor-specific database protocol. For supported relational databases.wss?uid=swg27037784). Compatible query mode To run reports that use the compatible query mode. The reporting engine is installed with Application Tier Components and is also used by Framework Manager.2. You can use the dynamic query mode with the following OLAP data sources: v IBM Cognos TM1 v SAP Business Information Warehouse (SAP BW) v Oracle Essbase v Microsoft Analysis Services You can use the dynamic query mode for OLAP over relational (dimensionally-modeled relational) models with the following relational data sources: v IBM DB2 v IBM DB2 for z/OS v Oracle v Microsoft SQL Server v Teradata v Netezza For more information about the dynamic query mode. It is written in pure Java and is platform-independent.ibm. 150 IBM Cognos Business Intelligence Version 10. and IBM Cognos Transformer.com/support/ docview. including installing the drivers. the query database (also known as the reporting database) is only accessed by the reporting engine that runs reports. see the IBM Software Compatibility reports (www. The compatible query mode uses native client and ODBC connections to communicate with data sources. you must use 32-bit data source client libraries and configure the report server to be 32-bit. For supported OLAP data sources. a type 4 JDBC connection is required.

If Framework Manager is installed in a separate location from the Application Tier Components.ibm.ini 2. Create an environment variable to specify the location of the . Procedure 1. see the IBM Cognos Administration and Security Guide. On Linux operating systems. Procedure 1. For example.ini file which contains the references to data source. depending on your operating system. Install the database API software for your relational databases and OLAP data sources on the computer that hosts the report server (where Application Tier Components are installed). To verify the version you have installed.ini file. Set the appropriate library path environment variable to specify the location of the connectivity libraries and Driver Manager for your database. Access ODBC data sources on UNIX or Linux operating systems To use an ODBC data source on UNIX or Linux to connect to a supported data source. The software must be installed on the same computer where the Application Tier Components are installed. IBM Software Compatibility reports (www.odbc. To review supported ODBC data sources. On MicrosoftWindows operating systems.2. Installing and Configuring Server Components on Different Computers 151 . After configuring for the ODBC connections. Chapter 6. you must install the client API software that is provided by your data source vendor.com/support/docview. the reporting engine supports either native database connectivity or ODBC. the open source iODBC driver manager is provided as part of the IBM Cognos installation.Access OLAP data sources on Windows operating systems To access the relational databases and OLAP data sources for reporting. you must create connections to the data sources in IBM Cognos Administration. You must install unixODBC version 2. For information. On UNIX operating systems.odbc. The following table lists the environment variables for each operating system that must specify the location of the driver manager libraries. and ensure you use that version. If your database vendor does not supply a driver manager. use the following command: odbcinst --version. export ODBCINI=/usr/local/etc/. the connectivity libraries. Check which version of unixODBC is required for the database you are using. and their accompanying Driver Manager libraries.wss?uid=swg27037784).11 or later before you can set up data source connections. you must also install the client API software on the computer where Framework Manager is installed. see “Set variables for data source connections for Framework Manager” on page 187. the unixODBC package provided with the operating system provides the ODBC Driver Manager. you can use unixODBC or iODBC. you must configure the environment to locate the . 2. For more information.odbc.

2. if you use Oracle Essbase version 11. you must install Oracle Foundation Services as well as the Oracle Essbase client.xml file in an xml or text editor. To resolve the problem.Table 37. no configuration is required if you use this version.config. the unixODBC package provides the required driver manager libraries. Go to the c10_location/configuration directory.1. you must edit the qfs.1.odbc.ini may result in having incompatible entries for different driver managers. For example. In addition. Using a common . change them as follows: <provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"> <!--provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"--> 152 IBM Cognos Business Intelligence Version 10. Locate the following lines: <!--provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"--> <provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"> 4.1. you must edit a configuration file to inform the IBM Cognos BI server of your version. iODBC is provided as part of the IBM Cognos installation. Therefore. In a scenario where one ODBC source validates while another fails based on a dependency. 3. IBM Cognos BI is configured to use Oracle Essbase version 11. set the library path to include the path the local driver manager. If you use another supported version of Oracle Essbase. please contact Customer Support. Open the qfs_config.1.2. The library files are located in the c10_location/bin directory. Your library path should already contain the c10_location/bin directory. review the structure requirements between the driver managers you are using and try to use syntax that is common between the conflicting driver managers. LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH What to do next If you are using multiple ODBC sources on UNIX or Linux operating systems. For Oracle Essbase 11. Configure IBM Cognos Business Intelligence to use Oracle Essbase If you use IBM Cognos Business Intelligence with an Oracle Essbase data source version 11. LIBPATH=/usr/IBM/cognos/bin:$LIBPATH v On Linux.1.xml file for your version. you may encounter dependencies of library files with common names but different implementations for both the connectivity and the driver manager. Environment variables for your operating system Operating system AIX Solaris and Linux HP-UX Environment variable LIBPATH LD_LIBRARY_PATH SHLIB_PATH 3. If your database vendor does not provide a driver manager.2. Procedure 1.1.1: Installation and Configuration Guide .2. v On UNIX. By default. For example.

click Start > IBM Cognos Configuration. you must update your Java environment. This 64-bit client includes a 32-bit client that IBM Cognos BI uses.5. Before you begin Before starting IBM Cognos Configuration. ensure that the lines appear as follows: <!--provider name="DB2OlapODP" libraryName="essodp111" connectionCode="DO"--> <provider name="DB2OlapODP" libraryName="essodp1112" connectionCode="DO"> 6. On Microsoft Windows. IBM Cognos BI uses these variables to find the Oracle Essbase client location. do not start IBM Cognos Configuration in the last page of the installation wizard. The ARBORPATH and ESSBASEPATH environment variables are created during the installation of the Oracle Essbase client. if you use a database server other than Microsoft SQL or Cognos Content Database for the content store.2. For example. ARBORPATH=C:\Hyperion\EPMSystem11R1\products\Essbase\EssbaseClient-32 ESSBASEPATH=C:\Hyperion\EPMSystem11R1\products\Essbase\EssbaseClient-32 If you use a 32-bit Microsoft Windows operating system with a 32-bit Oracle Essbase client. you can start IBM Cognos Configuration in the last page of the installation wizard only if additional setup is not required. you must manually configure the ARBORPATH and ESSBASEPATH environment variables. For example. For example. Installing and Configuring Server Components on Different Computers 153 . On UNIX or Linux operating systems. The following example assumes that the client is installed on the C drive.1. ensure that the operating environment is properly set up. you must manually change the ARBORPATH and ESSBASEPATH environment variables to replace EssbaseClient with EssbaseClient-32. you must install the 64-bit Oracle Essbase client. Additional setup is required before you can configure IBM Cognos BI. copy the Java Database Connectivity (JDBC) drivers to the appropriate location before you start the configuration tool. Your installation location might be different. Procedure 1. Save the file and restart the IBM Cognos service Configuring Oracle Essbase on a UNIX or 64-bit Microsoft Windows operating system If you use an Oracle Essbase version 11. For Oracle Essbase 11. ensure that all environment variables have been set. To use Oracle Essbase with IBM Cognos BI on a UNIX or 64-bit Microsoft Windows operating system. To point to this 32-bit client. Ensure that user or service account used to run IBM Cognos has been set up. On a Microsoft Windows operating system. Chapter 6. you are not required to change these environment variables. Start IBM Cognos Configuration Use IBM Cognos Configuration to configure IBM Cognos Business Intelligence components and to start and stop IBM Cognos services if you are using the default Tomcat servlet container.1.2 data source with IBM Cognos Business Intelligence on a UNIX or 64-bit Microsoft Windows operating system.

Windows 7. In the Properties window. you must list all Content Manager URIs on each Application Tier Components computer. For more information. click Environment. or Windows 2008 computer. change the localhost portion of the Content Manager URIs property to the name of any Content Manager computer. This will ensure that users in different locations can connect to reports and workspaces that are sent by email. Change the localhost portion of the remaining URI properties to the name or IP address of your IBM Cognos BI server.If you are using a Windows Vista. go to the c10_location/bin64 directory and then type the following command: . 2.Content Manager URIs dialog box. 3. In the Explorer window. On UNIX or Linux operating systems.1: Installation and Configuration Guide . If you see a JAVA.Lang. start IBM Cognos Configuration as an Administrator. click and then type the full URI of the Content Manager computer.unsatisfied link message.lang. All URI properties must use the the same format: all host names or all IP addresses. Configure Environment Properties for Application Tier Components Computers If you install the Application Tier Components component on a different computer than Content Manager. If you see a Java. 5. click Add. and have installed the product to the Program Files (x86) directory. verify that you are using a supported version of Java. v In the blank row of the table. Specify the URIs for the remaining Content Manager computers: v In the Value . 154 IBM Cognos Business Intelligence Version 10. You must include all Content Manager URIs in the list. v Repeat the previous two bulleted steps for each URI to be added.2. Change the localhost portion of the Gateway URI property to the name of the computer on which you plan to install the gateway component. The Application Tier Components computer must use the same notification database that the Content Manager computers use./cogconfig. Start IBM Cognos Configuration.sh If IBM Cognos Configuration does not open. ensure that you are using a 64-bit version of Java. v Click OK. 6. The distributed components can then communicate with each other. Replace the localhost portion of the URI with a host name or IP address. If you installed more than one Content Manager. ensure that you set the DISPLAY environment variable. The Application Tier Components computer must know the location of the Content Manager computers and the notification database to use for job and schedule information. you must configure the Application Tier Components computer so that it knows the location of Content Manager. 2. see “Change the notification database” on page 247. Procedure 1.unsupportedClassVersionError message. 4.

9. and have installed the reporting Application Tier Components in another instance. 8. Installing and Configuring Server Components on Different Computers 155 . under Security > Cryptography. you can disable many of the common services on your Metrics Manager Application Tier Components instance. Metrics Manager Application Tier Components instance with BI components Procedure 1. Figure 10. click Save. set the Password property to match what you configured on the default active Content Manager computer.7. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer. From the File menu. you have installed Content Manager as a separate instance. Under the Certificate Authority settings property group. open IBM Cognos Configuration. In the Explorer window. click Cognos. Chapter 6. For the instance where you have only the Metrics Manager Application Tier Components installed. Configure a Metrics Manager only Application Tier Components instance If you are installing the Metrics Manager Application Tier Components in a separate instance from your BI Application Tier Components. If you add a Metrics Manager Application Tier Components instance. 10. the default cryptographic provider. you do not need to duplicate all of the services required for the reporting Application Tier Components. For example.

2. you can continue to use the same data sources. you can set one instance to use the 32-bit report server. From the File menu. You must use the 32-bit version of report server for packages that do not use dynamic query mode. under Local Configuration > Environment. Enable the 64-bit version of report server In a 64-bit installation. 3. and select 64-bit. and restart the services for this instance. 156 IBM Cognos Business Intelligence Version 10. Click the Value box for Report server execution mode. You can then use routing rules so that report requests for non-dynamic query mode packages are routed to the instance that is running the 32-bit version of report server. Note that if you are upgrading. click IBM Cognos service. Save your settings. click Environment. 4. you must install the 64-bit version of the Application Tier Components on a 64-bit computer. In the Explorer window. For example. Restart your IBM Cognos services if they are running. 3. you must enable it using IBM Cognos Configuration. the report server component is provided in both 32-bit and 64-bit versions. if your package is based on IBM Cognos PowerCubes. click Save. For more information about routing rules.2. and have a package that references an available data source. you must use the 32-bit version of report server. you must install and configure the server components. The 64-bit version of report server can be used only with packages for which dynamic query mode is enabled. Set the following services to True: v Data integration service v Delivery service v Dispatcher service v Metadata service v Metric Manager service The remaining services can be set to False. The default option is 32-bit. To use the 64-bit version. If you install the 32-bit version of the Application Tier Components or are using a 32-bit computer. Before you begin To use IBM Cognos BI for reporting. In the IBM Cognos Configuration Explorer window. Start the Application Tier Components After you have configured the environment properties. To enable the 64-bit version. do not enable the 64-bit report server. you can start the services on the Application Tier Components computer.2. 4.1: Installation and Configuration Guide . start the IBM Cognos service. Procedure 1. see the Administration and Security Guide. If you have multiple Application Tier Components instances in your environment.

see “Configure a User Account or Network Service Account for IBM Cognos Business Intelligence” on page 52. You cannot use Cognos Content Database as a metric store database. Procedure 1. http://host_name:port/p2pd/servlet/dispatch The default value for host_name:port is localhost:9300. click Start. This action starts all installed services that are not running and registers the IBM Cognos service on Windows. For example. 2. click Local Configuration. click Test. A metric store is a database that contains content for metric packages. For information. a message appears indicating that configuration files were detected and upgraded to the new version. such as user preferences. Chapter 6. If the metric store is on a different computer from the Application Tier Components. otherwise you cannot start the IBM Cognos service. From the Actions menu. Creating a metric store database You must create a metric store database using Oracle. Test the Application Tier Components You can test the installation using a Web browser. or DB2. 4. If the test fails. Tip: If Test is not available for selection. reconfigure the affected properties and then test again. A metric store also contains scorecarding application settings. From the Actions menu. IBM Cognos Configuration checks the common symmetric keys (CSK) availability. Although you run the command to create the metric store from the location where the Application Tier Components are installed. you can specify a different location for the metric store in the command parameters. Open a Web browser. 5. Test the availability of the dispatcher by typing the External dispatcher URI value from IBM Cognos Configuration. Procedure 1. tests the namespace configuration. Microsoft SQL Server. Installing and Configuring Server Components on Different Computers 157 . you must create an alias to the metric store in the Application Tier Components location. Ensure that you save your configuration. in the Explorer window. If you are upgrading.Ensure that user or service account is set up. It may take a few minutes for the IBM Cognos service to start. Do not start the service until all tests pass. 3. You can test some components individually by right-clicking the component in the Explorer panel and selecting Test. and tests the connections to the content store and other resources. 2. The dispatcher is available when IBM Cognos Connection appears but displaying no graphics or images. Start IBM Cognos Configuration.

This value is optional. Table 38. The user ID with permissions to create the database. The user ID must have SYSADM or SYSCTRL privileges. the path where the database objects will be created. and must have DBADM privileges to create the schema. run the cmm_create_db. On UNIX. the drive on which the database objects will be created. in the c10_location/ configuration/schemas/cmm/db2 directory. type cmm_create_db. and it cannot start with a number. The name must have a maximum of 8 characters.Your database administrator must back up IBM Cognos Business Intelligence databases regularly because they contain the IBM Cognos data. The password for the user_name value. 2. it is also important to protect them from unauthorized or inappropriate access. The initializedb. v CREATETAB v v v v BINDADD CONNECT IMPLICIT_SCHEMA LOAD Create a metric store database in Microsoft SQL Server Use this procedure to create a metric store using a Microsoft SQL Server database. Procedure 1.db2 script is invoked by the cmm_create_db. Determine which user account IBM Cognos Metrics Manager will use to access the database. type cmm_create_db dbinstance user_name password dbname drive dbalias On a UNIX operating system. 158 IBM Cognos Business Intelligence Version 10.cmd script by typing the following command: On a Microsoft Windows operating system. Values for cmm_create_db script Value dbinstance user_name Setting The DB2 instance name where the database will be created. On Windows. To ensure the security and integrity of databases. The database alias name. The user account must have the following privileges. Create a metric store database in IBM DB2 Use this procedure to create a metric store using an IBM DB2 database. password dbname drive/path dbalias Note: Your database administrator can review the scripts to ensure they suit your environment. For example.cmd script and defines the buffer pools and tablespaces. The name of the database that will be created.sh dbinstance user_name password dbname path dbalias Use the values from the following table in your command. C.1: Installation and Configuration Guide .2. In the Application Tier Components location.

Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command: NLS_LANG = language_territory.UTF8 v NLS_LANG = JAPANESE_JAPAN.character_set Examples are: v NLS_LANG = AMERICAN_AMERICA. 3. Determine which user account IBM Cognos Metrics Manager will use to access the database. The user ID with permissions to create the database. The user ID must have permission to create the database. in the c10_location/ configuration/schemas/cmm/sqlserver directory. sort order. numeric.cmd script by typing the following command: path_to_script cmm_create_db host_name database_name user_name password [user_to_create] Use the values from the following table in your command. and calendar conventions automatically adapt to the native language and locale. This value is optional. monetary.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. Determine which user account IBM Cognos Metrics Manager will use to access the database. 2. This information is one of the parameters you can use when you run the command to create the database. password user_to_create Create an metric store database in Oracle Use this procedure to create a metric store using a new Oracle database. Table 39. The user account must be the database owner (dbo) or aliased to the database owner. In the Application Tier Components location. The user created by the script and given database owner permissions. Error messages. time. You must use a valid Oracle database username with the following permissions granted: Chapter 6. Installing and Configuring Server Components on Different Computers 159 . This information is one of the parameters you can use when you run the command to create the database. Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX. run the cmm_create_db.Procedure 1. database_name user_name The name of the database that will be created. specify host_name\instance_name. such as the sa user. The password for the username. If there are multiple instances of Microsoft SQL Server. 2. date. Procedure 1. The user ID must also have a default language of English. Values for cmm_create_db script Value host_name Setting The name of the computer where the database will be created.

time. You must use a valid Oracle database username with the following permissions granted: v CREATE TABLE. CREATE TYPE. sort order.cmd script by typing the following command: path_to_script cmm_create_db sid path database_version [user_to_create] Use the values from the following table in your command. The path where the data files will be created. CREATE SEQUENCE. c10_location/configuration/schemas/cmm/ oracle The SID for the new database that will be created. This value is optional.1: Installation and Configuration Guide . For example. In the Application Tier Components location. CREATE PROCEDURE. and CREATE SESSION 160 IBM Cognos Business Intelligence Version 10. CREATE VIEW. monetary. run the cmm_create_db. Values for cmm_create_db script Value path_to_script Setting The path to the script. CREATE SEQUENCE. CREATE TRIGGER. Procedure 1. CREATE VIEW. 2. CREATE TRIGGER. Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX. CREATE TYPE. in the c10_location/ configuration/schemas/cmm/oracle directory. If you grant fewer or more privileges.character_set Examples are: v NLS_LANG = AMERICAN_AMERICA. Error messages.2. the metric store will not initialize. date. Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command: NLS_LANG = language_territory. and CREATE SESSION v EXECUTE on DBMS_LOCK and DBMS_UTILITY packages The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role. CREATE PROCEDURE. and calendar conventions automatically adapt to the native language and locale. 3. Determine which user account IBM Cognos Metrics Manager will use to access the database.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI.v CREATE TABLE. 4. numeric. The user created by the script and given database owner permissions. The version of Oracle software that is installed. sid path database_version user_to_create Create a metric store database in Oracle using an existing database Use this procedure to create a metric store using an existing Oracle database. For example. Table 40. You must grant these permissions only.UTF8 v NLS_LANG = JAPANESE_JAPAN. oracle9 or oracle10.

Examples where a deployment location does not need to be manually defined v single server with Content Manager + Application Tier Components + Gateway v multiple servers. Installing and Configuring Server Components on Different Computers 161 . 4. 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. The deployment location is selected when a metric package is created. then to avoid the potential for errors. create a new database and specify AL32UTF8 for the database character set parameters. Chapter 6. you must manually define a deployment location for Metric Studio. You must manually define a deployment location for Metric Studio in the following situations: v if you installed more than one metric server v if your metric server is separate from Content Manager If you have just one metric server and it is on the same computer as Content Manager.cmd script mentioned in “Create a metric store database in IBM DB2” on page 111 creates a database with AL32UTF8 character encoding. delete all but one location. If the deployment location file contains multiple deployment locations. where Server A = Content Manager + Application Tier Components Server B = Gateway Examples where a deployment location must be manually defined v multiple servers. Manually define the deployment location for Metric Studio If you are using IBM Cognos Metrics Manager in a distributed installation. You must grant these permissions only. The same deployment location must be used for every metric package. The cmm_create_db. Important: Create just one deployment location folder. where Server A = Content Manager Server B = Application Tier Components Server C = Gateway v multiple servers. where Server A = Content Manager + Application Tier Components Server B = Application Tier Components Server C = Application Tier Components Server D = Gateway The deployment location must be defined on every metric server computer (where Application Tier Components are installed). IBM Cognos Metrics Manager is automatically configured with a deployment location. The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role. Determine if the database is Unicode.v EXECUTE on DBMS_LOCK and DBMS_UTILITY packages. If you grant fewer or more privileges. the metric store will not initialize.

select: <DeploymentLocation> <name>windows share</name> <value>\\winserver\deployment location</value> </DeploymentLocation> 3. If IBM Cognos BI is deployed to an application server other than Tomcat. Doing this allows Application Tier Components to access the metric store database. If the metric store is on a different computer from the Application Tier Components. Set the deployment location value: v On UNIX or Linux operating systems. Select the applicable section: v On UNIX or Linux operating systems. 162 IBM Cognos Business Intelligence Version 10.2. On the metric server computer where the Application Tier Components are installed. Setting up the database client for the Metric Store If you are using a database other than Microsoft SQL as a metric store. Procedure 1.xml in a text editor. create a shared folder that will serve as the deployment location. Copy the selected section after the line: DELETE this line to remove the xml comment tag --> 4. v On Windows operating systems. Set up the database client for an IBM DB2 metric store Use this procedure to setup the database client for an IBM DB2 metric store.1: Installation and Configuration Guide . 2. The folder must be accessible to all of the metric server computers. replace \\winserver\deployment location with the UNC path to the shared folder. ensure that the location is an absolute path. configure a database alias to the metric store by running the IBM DB2 Client Configuration Assistant. 2. and open deployment_locations. you must install database client software and Java Database Connectivity (JDBC) drivers on each computer where you install the Application Tier Components for Cognos Metrics Manager. replace /mount/deployment with the NFS mounted path to the shared folder.Before you begin Before you define the deployment location for Metric Studio. Note: If the metric store database and the Application Tier Components are on the same computer. select: <DeploymentLocation> <name>Unix Mount</name> <value>/mount/deployment</value> </DeploymentLocation> v On Windows operating systems. Procedure 1. use the IBM DB2 command line interface. 5. Save and close the file. the metric store name automatically becomes the alias. go to c10_location/configuration directory. Install the IBM DB2 client software on the Application Tier Components computer. On a UNIX or Linux operating system.

you must also install a 32-bit client.zip file.jar or db2java. reports. On the computer where the Oracle client is installed. If you are using a 64-bit installation. 4. Set up the database client for a Microsoft SQL Server metric store Use this procedure to setup the database client for a Microsoft SQL Server metric store. A metric package contains connection information. 2.jcc. db2jcc. 3. You open the New Metric Package wizard from the toolbar in IBM Cognos Connection.jar to the c10_location/webapps/p2pd/WEB-INF/lib directory on the computer where Application Tier Components are installed. Note: If you are using Oracle 11g. go to the ORACLE_HOME/jdbc/lib directory. Copy ojdbc5. Chapter 6. db2jcc_license_cu. Use the wizard to define the metric package name and the data source connection to the metric store.jar Tip: To check the driver version. Install the bcp utility on every Windows computer where Application Tier Components for IBM Cognos Metrics Manager are installed. Procedure 1. run the following command: java -cp path\db2jcc. Note: Ensure you copy the jar file from the 64-bit client if you have installed the 64-bit Metrics Manager. Add the location of the bcp utility to the path environment variable. 2.db2. Procedure 1. The metric package content is stored in a metric store. Create a metric package Before users can use Metric Studio. and can also be downloaded from the Oracle Web site. install a 64-bit Oracle client. Install the SQL Loader utility on the computer where Application Tier Components are installed.DB2Jcc -version If the directory contains a db2java. The driver is available from an Oracle client or server installation. For a new metric store. including the start and end dates of the fiscal year.jar v the license file. Installing and Configuring Server Components on Different Computers 163 . you also provide the information necessary to initialize the database.jar com. Copy the following files from DB2_installation/sqllib/java directory to the c10_location/webapps/p2pd/WEB-INF/lib directory.3. and metric management tasks for that application. v the universal driver file. you must create at least one metric package using the New Metric Package wizard. A metric package is an IBM Cognos Connection representation of a Metric Studio application. Set up the database client for an Oracle metric store Use this procedure to setup the database client for an Oracle metric store. delete the file.ibm.

and Oracle service ID in the appropriate fields. and type the user ID and password of the user account with access to the database. If you want to provide one. and click Next. Enter the name of the database server. v If you are using an Oracle database: a. c. a JDBC connection is required. b. For example. Type a name and description for the Metric Studio application to represent this metric package. Click New data source. 2. and type the user ID and password of the user account with access to the database. In the Type box.1: Installation and Configuration Guide . you must have execute permissions for the Metric Studio Administration secured feature and traverse permission for the Administration secured function. Select User ID. Select Signons. d. a collation sequence is not required. v If you are using an IBM DB2 database: a. b. The user account must have the default language set to English. Procedure 1. Enter the connection string. Optionally. and database name in the appropriate fields.port. 6. configure a JDBC connection for data source by adding a connection type of Service ID. Enter the name of the database as defined in the IBM DB2 client. Type a name and description for the data source connection for the metric store that contains the content for this metric package. configure a JDBC connection for data source by adding the server name. click the database type. c. b. If you are using AIX. Optionally. and click Next. d. and click Next. In most cases.Before you begin To create metric packages. In IBM Cognos Connection. Select the Password and Create a signon that the Everyone group can use check boxes. Type the database name. server_name or server_name\instance_name if there are multiple instances of Microsoft SQL Server. v If you are using a Microsoft SQL Server database: a. Specify the information required for your database type. Select the Password and Create a signon that the Everyone group can use check boxes. c. port number. Select the isolation level. ensure the value that you enter is the same as the collation sequence 164 IBM Cognos Business Intelligence Version 10. d. a JDBC connection is required. Select the Password and Create a signon that the Everyone group can use check boxes. If you are not using the default port number 1433. 7. click the New metric package button . and specifying the required values for the server name. If you are using AIX. 5. 3. 4.2. use server_name. and type the user ID and password of the user account with access to the database. Select User ID. port number.

specified when the database was created. For information about collation sequences, see the database documentation. Tip: To test whether the parameters are correct, click Test the connection. 8. Click Next and then click Finish. 9. Click the new data source and click Next. 10. Click Next and follow the prompts to provide the information necessary to initialize the database. When you see the page that summarizes the data source details and the metric store settings, click Initialize. 11. Select Open this package with Metric Studio after closing the wizard and then click Finish.

Results
Metric Studio opens, and the new metric package appears in IBM Cognos Connection.

Installing and Configuring the Gateway
You can install the gateway on one or more computers, depending on your environment. If you have a Web farm, you may want to install an IBM Cognos BI gateway on each Web server. Using multiple Web servers to manage incoming requests provides better service. If you install only the gateway component on the same computer as the Web server, your Web server manages the core Web services and does not process user requests. This separation of processing may be required if you have a network firewall between the Web server and your other server components. If you plan to install IBM Cognos Metrics Manager and share resources with the IBM Cognos BI gateway, install the gateway on a 32-bit system. For more information, see “Install the Gateway for IBM Cognos Metrics Manager” on page 168. Ensure that the computer where you installed the active Content Manager is configured and available before you configure gateway computers. Perform the following steps to install and configure the gateway: v Install the gateway components v Install the gateway for IBM Cognos Metrics Manager components, if necessary v Install fix packs, if available v Start IBM Cognos Configuration v Configure environment and security properties for the gateway v Configure your Web server v Test the gateway installation

64-bit Installations
The IBM Cognos BI gateway provides 32-bit libraries, whether you install on a 64-bit server or a 32-bit server. Some Web servers, such as Apache Web Server, cannot load a 32-bit compiled library in a 64-bit compiled server. In that situation, install the 32-bit version of the IBM Cognos gateway on a 32-bit Web server.

Chapter 6. Installing and Configuring Server Components on Different Computers

165

Installing the gateway components on UNIX or Linux operating systems
You can install the gateway on one or more computers, depending on your environment. If you have a Web farm, you may want to install an IBM Cognos BI gateway on each Web server.

Before you begin
Go to the IBM Software Compatibility reports (www.ibm.com/support/ docview.wss?uid=swg27037784). Verify that you have the required patches installed on your computer before you install the product.

Procedure
1. If you are installing to a directory with other IBM Cognos BI components, stop the IBM Cognos service. 2. 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. IBM Cognos BI requires a JVM, such as the Java that is provided by IBM, to run on a Linux operating system. If you are installing in a location with other IBM Cognos BI components, use the existing JAVA_HOME environment variable. 3. 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. 4. On AIX, if you are using a servlet gateway, set the AIXTHREAD_SCOPE environment variable as follows: AIXTHREAD_SCOPE=S This sets the contention scope for user threads to system-wide, which supports more efficient scheduling of user threads. 5. If installing from a download, go to the location where the installation files were downloaded and extracted. 6. If installing from a disk, mount the disk using Rock Ridge file extensions. To mount the disk on HP-UX, do the following: v Add the pfs_mount directory in your path. For example, PATH=/usr/sbin/:$PATH export PATH v To start the required NFS daemons and run the daemons in the background, type bg pfs_mountd and then type bg pfsd v 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 disk from this drive.

166

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

v When the installation is complete, type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the disk. 7. To start the installation wizard, go to the operating system directory and then type ./issetup Note: When you use the issetup command with XWindows, Japanese characters in messages and log files may be corrupted. When installing in Japanese on UNIX or Linux, first set environment variables LANG=C and LC_ALL=C (where C is the language code, for example ja_JP.PCK on Solaris), and then start the installation wizard. If you do not use XWindows, run an unattended installation (see Chapter 17, “Using an unattended installation and configuration,” on page 407). If you are installing on Linux operating systems, and you receive error messages about missing openmotif libraries, you can use an unattended installation with the issetupnx command. 8. Follow the directions in the installation wizard and copy the required files to your computer. v When selecting the directory, consider the following: Install Gateway components in a directory that contains only ASCII characters in the path name. Some UNIX and Linux Web servers do not support non-ASCII characters in directory names. v When selecting components, clear all components except Gateway. 9. In the Finish page of the installation wizard, do the following: v If you want to see the log files, click View for the appropriate log file. v If you want to see late-breaking information about the product, select the check box for IBM Cognos Release Notes. v Do not configure IBM Cognos BI immediately because you must do other tasks first to ensure that your environment is properly set up. Ensure that the IBM Cognos Configuration check box is clear. You can later configure IBM Cognos BI using IBM Cognos Configuration by typing cogconfig.sh in the c10_location/bin64 directory. v Click Finish. 10. Append the c10_location/bin64 directory to the appropriate library path environment variable. v For Solaris and Linux, LD_LIBRARY_PATH v For AIX, LIBPATH v For HP-UX, SHLIB_PATH

What to do next
If you want users to see product documentation in a language other than English, you must install the Supplementary Language Documentation component in the location where you installed the Gateway components. For more information, see “Installing translated product documentation” on page 212.

Installing the gateway components on Windows operating systems
You can install the gateway on one or more computers, depending on your environment. If you have a Web farm, you may want to install an IBM Cognos BI gateway on each Web server.
Chapter 6. Installing and Configuring Server Components on Different Computers

167

Procedure
1. If you are installing to a directory with other IBM Cognos BI components, stop the IBM Cognos service. 2. Do one of the following: v Insert the IBM Cognos product disk. If the installation wizard does not open automatically, go to the operating system directory, and double-click issetup.exe. v Go to the location where the installation files were downloaded and extracted and then double-click issetup.exe. 3. Select the language to use for the installation. The language that you select determines the language of the user interface. All supported languages are installed. You can change the user interface to any of the installed languages after installation. 4. Follow the directions in the installation wizard to copy the required files to your computer. v When selecting the directory, consider the following: Install Gateway components in a directory that contains only ASCII characters in the path name. Some Microsoft Windows operating system Web servers do not support non-ASCII characters in directory names. v When selecting components, clear all components except Gateway. 5. In the Finish page of the installation wizard, do the following: v If you want to see the log files, click View for the appropriate log file. v If you want to see late-breaking information about the product, select the check box for IBM Cognos Release Notes. v If you want to start IBM Cognos Configuration now, select Start IBM Cognos Configration. You can also start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu. v Click Finish.

What to do next
If you want users to see product documentation in a language other than English, you must install the Supplementary Language Documentation component in the location where you installed the Gateway components. For more information, see “Installing translated product documentation” on page 212.

Install the Gateway for IBM Cognos Metrics Manager
If you are installing IBM Cognos Metrics Manager with the IBM Cognos BI server and you want to share resources, you must install the Gateway for IBM Cognos Metrics Manager in the same location as the Gateway for the IBM Cognos BI server. If you want your scorecarding product to operate independently of the IBM Cognos BI server, install the Gateway for IBM Cognos Metrics Manager in a different location from the Gateway for the IBM Cognos BI server. You may also want to install Metric Designer (see “Installing and Configuring Metric Designer” on page 192).

168

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Installing fix packs
IBM provides interim maintenance packages that contain updates to one or more components in your IBM Cognos product. If a fix pack is available when you are installing or upgrading your product, you must install it after you install the IBM Cognos components. If a fix pack becomes available after your IBM Cognos product has been deployed, you must stop the service, install the fix pack in the same location as the IBM Cognos components, and then start the service. Fix packs are cumulative. When you install the latest fix pack, it includes updates from all the previous fix packs. Fix packs are available for download from IBM Support at http://www.ibm.com/support/us/en/. Note: Fix packs are not standalone installations. You must install them on computers that have IBM Cognos components installed. Install the fix packs that are appropriate for your product version. To check your version, open the component list file at c10_location\cmplst.txt and check the line that starts with C8BISRVR_version=.

Installing IBM Cognos fix packs on UNIX or Linux operating systems
Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product. IBM Cognos fix packs are installed in the same location as the existing product.

Before you begin
Ensure that you do the following tasks before installing a Fix Pack. v If the IBM Cognos service is running, stop it. v Back up the directory structure. v Back up the content store database v Back up any files that you manually edited.

Procedure
1. Go to the location where the installation files are downloaded, or insert the disc if you have one. 2. To start the installation wizard, type the following command ./issetup 3. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. 4. If required, update the new installation files with any changes from the backup copies of your customized files. To prevent errors, before copying the customized files, compare both versions of the files. This validation determines whether you can replace the file. 5. Return the deployed IBM Cognos product to service. v If you are using Tomcat, open IBM Cognos Configuration, save the configuration, and then start the IBM Cognos service. v If you are running the IBM Cognos product on an application server other than Tomcat, redeploy the IBM Cognos product to the application server. 6. If you have a distributed environment, repeat these steps for all remaining IBM Cognos servers.
Chapter 6. Installing and Configuring Server Components on Different Computers

169

Installing Fix Packs on Windows operating systems
Fix packs are product updates that contain cumulative code fixes that were made since the last release of the product. IBMCognos fix packs are installed in the same location as the existing product.

Before you begin
Ensure that you do the following tasks before installing a Fix Pack. v If the IBM Cognos service is running, stop it. v Back up the directory structure. v Back up the content store database v Back up any files that you manually edited.

Procedure
1. Insert the fix pack disk for the Windows operating system or go to the location where you downloaded and extracted the files, and double-click the issetup.exe file. 2. Follow the directions in the installation wizard to install the fix pack files to the same location as the existing IBM Cognos components. 3. If required, update the new installation files with any changes from the backup copies of your customized files. To prevent errors, before copying the customized files, compare both versions of the files. This validation determines whether you can replace the file. 4. Return the deployed IBM Cognos product to service. v If you are using Tomcat, open IBM Cognos Configuration, save the configuration, and then start the IBM Cognos service. v If you are running the IBM Cognos product on an application server other than Tomcat, redeploy the IBM Cognos product to the application server. 5. If you have a distributed environment, repeat these steps for all remaining IBM Cognos servers.

Start IBM Cognos Configuration
Use IBM Cognos Configuration to configure IBM Cognos Business Intelligence components and to start and stop IBM Cognos services if you are using the default Tomcat servlet container.

Before you begin
Before starting IBM Cognos Configuration, ensure that the operating environment is properly set up. For example, ensure that all environment variables have been set. On a Microsoft Windows operating system, you can 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 or Cognos Content Database for the content store, copy the Java Database Connectivity (JDBC) drivers to the appropriate location before you start the configuration tool. On UNIX or Linux operating systems, do not start IBM Cognos Configuration in the last page of the installation wizard. Additional setup is required before you can configure IBM Cognos BI. For example, you must update your Java environment.

170

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Ensure that user or service account used to run IBM Cognos has been set up.

Procedure
1. On Microsoft Windows, click Start > IBM Cognos Configuration. If you are using a Windows Vista, Windows 7, or Windows 2008 computer, and have installed the product to the Program Files (x86) directory, start IBM Cognos Configuration as an Administrator. 2. On UNIX or Linux operating systems, go to the c10_location/bin64 directory and then type the following command: ./cogconfig.sh If IBM Cognos Configuration does not open, ensure that you set the DISPLAY environment variable. If you see a JAVA.Lang.unsatisfied link message, verify that you are using a supported version of Java. If you see a Java.lang.unsupportedClassVersionError message, ensure that you are using a 64-bit version of Java.

Configure Environment and Security Properties for Gateway Computers
If you install the gateway component on a different computer than Content Manager or Application Tier Components, you must configure the gateway computer so that it knows the location of a dispatcher. A dispatcher is installed on every Content Manager and Application Tier Components computer. Configure the gateway to use the dispatcher on an Application Tier Components computer. For failover protection, you can configure more than one dispatcher for a gateway computer. When multiple dispatchers are configured, requests are normally routed to the first dispatcher in the list. If this dispatcher becomes unavailable, the gateway determines the next functioning dispatcher on the list and routes requests there. The primary dispatcher status is monitored by the gateway, and requests are routed back to this component when it returns to service. After you do the required configuration tasks, the gateway computer can work in your environment.

Before you begin
Ensure that the computers where you installed Content Manager are configured and the default active Content Manager computer is available before you configure gateway computers.

Procedure
1. Start IBM Cognos Configuration. 2. In the Explorer window, click Environment. 3. In the Properties window, under Gateway Settings, specify the values for Dispatcher URIs for the gateway: v Click in the value column. v Click the edit button. v Change the localhost portion of the URI to the name or IP address of an Application Tier Components computer. This will ensure that users in different locations can connect to reports and workspaces that are sent by email.
Chapter 6. Installing and Configuring Server Components on Different Computers

171

Tip: If you want to send requests to the dispatcher from an Software Development Kit application or an IBM Cognos BI modeling tool that is outside of a network firewall, connect to a dedicated gateway that is configured to connect to the dispatcher using the internal dispatcher URI for your environment (for example, http://localhost:9300/p2pd/servlet/ dispatch). For security reasons, the default setting for the Dispatcher URI for gateway property prevents the dispatcher from accepting requests for an Software Development Kit application or modeling tool that is outside the firewall. Ensure that you configure appropriate security for this dedicated gateway, such as SSL (see “Configuring the SSL protocol for IBM Cognos components” on page 257). Do not change your main gateway to use the internal dispatcher URI. Doing so will reduce the security of the IBM Cognos BI portal and studios. For more information about the modeling tool and network firewalls, see “Firewall considerations” on page 24. v If you want to add another URI, click Add and change the localhost portion of the new URI to the name or IP address of another Application Tier Components computer. Tip: If you want to use the dispatcher on a standby Content Manager computer, ensure that you add it after you add the Application Tier Components computers. If you add the dispatcher from the active Content Manager computer, ensure that it is last in the list. v After you specify all the URIs, click OK. 4. In the Explorer window, under Security > Cryptography, click Cognos, the default cryptographic provider. 5. Under the Certificate Authority settings property group, set the Password property to match what you configured on the default active Content Manager computer. 6. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer. 7. Test that the symmetric key can be retrieved. In the Explorer window, right-click Cryptography and click Test. IBM Cognos BI components check the common symmetric keys (CSK) availability. 8. From the File menu, click Save.

Configuring the web server
You must configure your Web server before users can connect to the IBM Cognos BI portal. For IBM Cognos BI for reporting, 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. On UNIX and Linux operating systems, the account under which the Web server runs must have read access to the cogstartup.xml file in the c10_location/ configuration directory. By default the cogstartup.xml file has read permission for others. If you run your Web server under a specific group, you can change the cogstartup.xml file permissions to ensure that it belongs to the same group as the Web server. You can then remove the read permission for others.

172

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Enable the 32-bit web gateway for a 64-bit installation
If you installed the 64-bit version of IBM Cognos BI but are using a 32-bit web server, you must manually move the 32-bit gateway files in your installation directory. If you installed the 32-bit version of IBM Cognos BI, the 32-bit version of the gateway is installed by default.

Procedure
1. Go to the c10_location/cgi-bin. 2. Type the following command: v On UNIX or Linux operating systems, type ./copyGateMod.sh 32bit v On Windows operating systems, type copyGateMod.bat 32bit

Results
The 32-bit gateway files are copied from the cgi-bin/lib directory to the cgi-bin directory. Note: If you need to restore the default 64-bit gateway files, follow the procedure and type ./copyGateMod.sh 64bit or copyGateMod.bat 64bit. The 64-bit gateway files are copied from the cgi-bin/lib64 directory to the cgi-bin directory.

Use compiled gateways for production systems
For production systems, you can improve performance by changing the gateway from the default CGI gateway. The compiled gateways include: v Microsoft Internet Server Application Programming Interface (ISAPI) for Microsoft Internet Information Services (IIS) v Apache module for Apache Web Server or IBM HTTP Server v Servlet Gateway Java application if you use an application server other than the default Apache Tomcat Use Apache modules on Apache Server or IBM HTTP Server: You can use Apache modules for Apache Server 2.2.x or Apache Server 2.0.x or for IBM HTTP Server 8, 7, or 6.1. Important: You cannot use the Apache modules with the version of Apache Server 2.2 that is supplied with Red Hat Enterprise Linux version 5.3 and later. Procedure 1. Append the c10_location/cgi-bin directory to the appropriate environment variable: v On Solaris or Linux, LD_LIBRARY_PATH v On HP-UX, SHLIB_PATH and LD_LIBRARY_PATH v On AIX, LIBPATH 2. Go to the Webserver_installation/conf directory. 3. Open the httpd.conf file in an editor. 4. Ensure that both the server name and web server port number values are specified for the ServerName property.
Chapter 6. Installing and Configuring Server Components on Different Computers

173

5. Add the following to the end of the load module list: LoadModule cognos_module "c10_location/cgi-bin/mod2_2_cognos.suffix" Where suffix is as listed in the following table.
Table 41. Module suffix for your operating system Operating system Windows Solaris, AIX, HP-UX IA, Linux Suffix dll so

Apache modules are provided for different versions of Apache Server or IBM HTTP Server: v Use the mod2_2_cognos module for Apache Server 2.2.x or IBM HTTP Server 8 and 7. v Use the mod2_cognos module for Apache Server 2.0.x and IBM HTTP Server 6.1. 6. Add the following:
ScriptAlias /ibmcognos/cgi-bin "c10_location/cgi-bin" <Directory "c10_location/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> Alias /ibmcognos "c10_location/webcontent" <Directory "c10_location/webcontent"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory>

The <Directory> directive is optional. Note: Ensure that you define the /ibmcognos/cgi-bin alias before the /ibmcognos alias. Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. If you do not use ibmcognos for the ScriptAlias and Alias values, ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. Also, ensure that you use the same value for the ibmcognos part of the ScriptAlias and Alias values as shown in the examples. 7. Add the following to the server status reports section:
<Location /ibmcognos/cgi-bin/module_alias> SetHandler cognos-handler Order allow,deny Allow from all </Location>

Where module_alias is a name that you can choose. 8. To enable the gateway diagnostic page, add the following to the server status reports section:

174

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

For more information about creating an application pool. click Local Configuration > Environment. Important: If you are using the 32-bit version of the ISAPI gateway. For example. In the Gateway URI box. In the Explorer panel.cgi part of the URI to module_alias. 15. Results Users can access the server by entering the Apache module URI in their browser. 14. see your web server documentation. you must enable 32-bit application for the application pool that is used for the IBM Cognos Chapter 6.0. Apache module files are provided for different versions of Apache Server or IBM HTTP Server: v Use mod2_2_cognos. you must create a separate application pool for each product or instance and then associate the aliases for that product or instance to the application pool.c> CGIBinDir "c10_location/cgi-bin" </IfModule> 10. Save and close the file. v Use mod2_cognos. http://servername:port/ibmcognos/cgi-bin/module_alias.c for Apache Server 2.2. Add the following to the user directory section: <IfModule mod2_2_cognos. or several instances of the same product. Start IBM Cognos Configuration. Installing and Configuring Server Components on Different Computers 175 . 13. 16.x or IBM HTTP Server 8 and 7. Use the ISAPI gateway on Microsoft Internet Information Services (IIS) version 7 or 8: If you are using a Microsoft Internet Information Services (IIS) web server. On HP-UX. configure IBM Cognos to use the ISAPI gateway rather that the default CGI gateway. About this task If you are using Microsoft IIS as your web server and you plan to run more than one IBM Cognos BI product.c for Apache Server 2.x and IBM HTTP Server 6.deny Allow from all </Location> Where diag_module_alias is a name that you can choose. For example. enable searching for SHLIB_PATH by running the following command in the Apache_installation/bin directory: chatr +s enable +b enable httpd Restart the web server.<Location /ibmcognos/cgi-bin/diag_module_alias> SetHandler cognos-handler Order allow. 11. 9. 12. on one computer. change the cognos. Save your changes.1. http://host_name:port/ibmcognos/cgi-bin/module_alias.

and click Next. expand Roles > Web Server (IIS). 3. in Server Manager. and click Internet Information Services (IIS) Manager. d. use the following steps: a. If you are using Microsoft Windows 7 or 8. In the Add Roles and Features Wizard. and click Next until you get to the Role Services section of the wizard. f. In the Microsoft Windows Control Panel. Change the value for Enable 32-Bit Applications to True. If you are using Microsoft Windows 2012 Server. In the Internet Information Services (IIS) Manager console. f. from theControl Panel. b. and click Next. under Connections. and click Next. Ensure that Common HTTP Features. Select ISAPI extensions if it is not already selected. e. Programs and Features is available directly from the Control Panel. Click Server Manager > Roles > Web Server (IIS). if it is not already installed. from theControl Panel. 5.1: Installation and Configuration Guide . use the following steps: a. v If you are using Microsoft Windows 8. e. and click Advanced Settings. Expand Internet Information Services > World Wide Web Services. c. Select your server. Expand Application Development.gateway. and then click Internet Information Services (IIS) Manager. Expand Application Development Features. click Programs > Programs and Features. If ISAPI extensions is set to Not installed.2. Click Turn Windows features on or off. and then right-click your server name. click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. use the following steps: a. select the application pool that is used for IBM Cognos. select ISAPI extensions and click Add Role Service. c. If you are using Microsoft Windows 8 or 2012 Server. 176 IBM Cognos Business Intelligence Version 10. Click OK. In the Internet Information Services (IIS) Manager. 2. If you are using Microsoft Windows 2008 Server. b. select your server name. in Server Manager. or the features you require are enabled. 6. v If you are using Microsoft Windows 7. Procedure 1. or the features you require are enabled. Select Internet Information Services if it is not already selected. select IIS. v If you are using Microsoft Windows 2008 Server. click Role-based or feature-based installation. click Administrative Tools to access the Internet Information Services (IIS) Manager console. ensure that Common HTTP Features is selected. b. select ISAPI extensions. Click Install. 4. Select Web Server (IIS). v If you are using Microsoft Windows 2012 Server. If ISAPI extensions is not selected. Ensure that Common HTTP Features. d. c.

10. click Local Configuration > Environment. 8. v The IBM Cognos BI Application Tier Components and Content Manager are installed and running in the environment.dll. you can use the servlet gateway to serve the portal pages rather than using a web server. 13. f. enter a name for the entry.dll file. If you do not use ibmcognos for the Alias values. type cognosisapi. Chapter 6. change the cognos. v IBM Cognos BI gateway components are installed on the same system as the application server. Select the cgi-bin virtual directory that you created. click Add Module Mapping. v The application server user account has full access permission for the IBM Cognos installation. a. In Name. In the Gateway URI box. Start IBM Cognos Configuration. Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. In Executable.dll d. enter: C:\Program Files\ibm\cognos\c10\cgi-bin\cognosisapi.cgi part of the URI to cognosisapi.dll. add the virtual directories as shown in the table: Table 42. enter the path to the cognosisapi. c. b. Click OK. e. In the Explorer panel. For example. 9. Configure the servlet gateway for an application server: If you deploy IBM Cognos to an application server other than Tomcat. select IsapiModule. 12.7. and under your website. In Request Path. Double-click Handler Mappings. Before you begin Ensure the following tasks are complete: v The application server is installed and running on each computer where the servlet gateway is to be installed. Under Actions. Click Yes in the dialog box to allow the ISAPI extension. such as CognosISAPI. Expand Sites. Results Users can access the ISAPI gateway by entering http://servername/ibmcognos/ isapi in their web browsers. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. Installing and Configuring Server Components on Different Computers 177 . 11. In Module.

2. Set environment variables. Results You can now access IBM Cognos components using the servlet gateway by entering the gateway URI. Procedure 1. 4. 6. Use CGI gateways You can use the CGI gateway on IBM HTTP Server. To use the CGI gateway. 3. Open the httpd.deny Allow from all </Directory> Alias /ibmcognos "c10_location/webcontent" 178 IBM Cognos Business Intelligence Version 10. Add the following: ScriptAlias /ibmcognos/cgi-bin "c10_location/cgi-bin" <Directory "c10_location/cgi-bin"> AllowOverride None Options None Order allow. the servlet gateway must be deployed to a separate JVM instance. 5. 7.1: Installation and Configuration Guide . Configure IBM Cognos Servlet Gateway to run on the application server. Doing this type of deployment separates the load for serving static content from the main applications. Configure application server properties and deploy IBM Cognos Servlet Gateway. Enable SSL. Apache Web Server. if necessary. 4. If you plan to run IBM Cognos BI and the IBM Cognos Servlet Gateway on the same application server. Change the application server startup script.conf file in an editor. or Microsoft Internet Information Services (IIS) Server. 3. Check that IBM Cognos components are properly set up. Go to the Webserver_installation/conf directory. if required. 2. Use the CGI gateway on Apache Server or IBM HTTP Server: The default gateway configured in IBM Cognos Configuration is the CGI gateway.http[s]:host_name:port/ServletGateway. Procedure 1. Create a separate JVM instance. The IBM Cognos Servlet Gateway URI is case-sensitive. Ensure that both the server name and web server port number values are specified for the ServerName property.2. you must configure aliases for Apache Server or IBM HTTP Server. For example. you deploy the servlet gateway to a different JVM instance than the JVM instances that run the IBM Cognos BI Application Tier Components and Content Manager servlets. if necessary.About this task Instead of routing requests directly to the dispatcher.

If you are using Microsoft Windows 2012 Server. For more information about creating an application pool. ensure that you use the same value for the ibmcognos part of the ScriptAlias and Alias values as shown in the examples. Results Users can access the portal at http://servername:port/ibmcognos. If you do not use ibmcognos for the ScriptAlias and Alias values. If CGI is set to Not installed. or several instances of the same product. If you are using Microsoft Windows 8 or 2012 Server. or the features you require are enabled. c. Note: Ensure that you define the /ibmcognos/cgi-bin alias before the /ibmcognos alias. 5. Installing and Configuring Server Components on Different Computers 179 . you must create a separate application pool for each product or instance and then associate the aliases for that product or instance to the application pool. on one computer. Use the CGI gateway on Microsoft Internet Information Services (IIS) version 7 or 8: If you are using Microsoft Internet Information Services (IIS) version 7 or later. 3. In the Microsoft Windows Control Panel. About this task If you are using Microsoft IIS as your web server and you plan to run more than one IBM Cognos BI product. see your web server documentation.deny Allow from all </Directory> The <Directory> directive is optional. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use.<Directory "c10_location/webcontent"> Options Indexes MultiViews AllowOverride None Order allow. Restart the web server. Also. 6. 4. 2. use the following steps: a. Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. Ensure that Common HTTP Features. use the following task to configure the CGI gateway. The CGI gateway is provided for both 32-bit and 64-bit web servers. use the following steps: Chapter 6. select CGI and click Add Role Service. Procedure 1. Save and close the file. Programs and Features is available directly from the Control Panel. If you are using Microsoft Windows 2008 Server. Click Turn Windows features on or off. Click Server Manager > Roles > Web Server (IIS). click Programs > Programs and Features. b.

Expand Internet Information Services > World Wide Web Services. from the Control Panel. from the Control Panel. f. Double-click ISAPI and CGI Restrictions. in Server Manager. click Role-based or feature-based installation. 7. and click Next until you get to the Role Services section of the wizard. including the file name. The file is in the c10_location\cgi-bin directory. and click Internet Information Services (IIS) Manager. Select Allow extension path to execute. e. click Administrative Tools to access the Internet Information Services (IIS) Manager console. Select CGI if it is not already selected. in Server Manager. Select Internet Information Services if it is not already selected. Under Connections.a. select IIS. and click Next. use the following steps: a. and click Next. c. In the Add Roles and Features Wizard. v If you are using Microsoft Windows 8. Click Install. You must enter the full path. click Add. under Connections. expand Sites. v If you are using Microsoft Windows 2012 Server. 11.1: Installation and Configuration Guide . Select Web Server (IIS). ensure that Common HTTP Features is selected. and then click Internet Information Services (IIS) Manager. Click OK. Enter the path to the cognos. and click Next. Enter a Description. add the virtual directories as shown in the table: Table 43. b. click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. 12. Under Actions. If you are using Microsoft Windows 7 or 8. 8. d. 9. and under your website. 5.cgi” 10. expand Roles > Web Server (IIS). f. and then right-click your server name. c. ensure you use quotation marks around the path. enter: “C:\Program Files\ibm\cognos\c10\cgi-bin\cognos. Ensure that Common HTTP Features.2. 6. If the path includes spaces. Select your server. select CGI. Expand Application Development. select your server name. Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin 180 IBM Cognos Business Intelligence Version 10. For example. such as CognosCGI. and click OK. b. In the Internet Information Services (IIS) Manager console. If CGI is not selected. e. if it is not already installed.cgi file. or the features you require are enabled. Expand Application Development Features. v If you are using Microsoft Windows 7. v If you are using Microsoft Windows 2008 Server. d.

you must add directives to your server configuration file. Procedure Create the virtual directories shown in the following table: Table 44. Double-click Handler Mappings. 13. and then configure the directory access. In Request Path. enter a name for the entry. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use.Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. If you do not use ibmcognos for the Alias values. Use the CGI gateway on older versions of Microsoft IIS: For versions of Microsoft Internet Information Services (IIS) earlier than version 7. b. Results Users can access the CGI gateway by entering http://servername/ibmcognos in their web browsers. such as CognosCGI. Under Actions. Click OK. Select the cgi-bin virtual directory that you created. 15. configure Web Distributed Authoring and Versioning (WebDAV) on your web server. Configuring WebDAV on IBM HTTP Server or Apache server: On IBM HTTP Server or Apache server. If you do not use ibmcognos for the ScriptAlias and Alias values. a. Configuring WebDAV to view and browse images To view and browse images in the Report Studio. Report authors can browse for images to include in reports in a way that is similar to browsing a file system. Leave Executable (optional) blank. Installing and Configuring Server Components on Different Computers 181 . Required virtual directories Alias ibmcognos ibmcognos/cgi-bin Location c10_location/webcontent c10_location/cgi-bin Permission Read Execute Important: ibmcognos is the default value that is used in the Gateway URI and Controller URI for gateway values in IBM Cognos Configuration. click Add Module Mapping. e. In Module. type cognos.cgi. Chapter 6. 14. c. In Name. select CgiModule. ensure that you change the Gateway URI and Controller URI for gateway values to match the values you use. d. use these steps to configure the CGI gateway.

7. 2. In the Microsoft Windows Control Panel. 4. 5. When users click Browse in the image browser. open the httpd.2. Report Studio users can add images to their reports. LoadModule dav_module modules/mod_dav. If you are using Microsoft Windows 2012 Server.Procedure 1. Click Next.1: Installation and Configuration Guide . b. Save the file. use the following steps: a. you must first enable the WebDAV feature. If you are using Microsoft Windows 2008 Server. and then configure your web server to access the image location. use the following steps: 182 IBM Cognos Business Intelligence Version 10. In the webserver_location/conf directory.so LoadModule dav_fs_module modules/mod_dav_fs. If you are using Microsoft Windows 8 or 2012 Server. If you created another location. 3. select WebDAV Publishing. d. Click Turn Windows features on or off.conf file in a text editor. c.deny Allow from all </Directory> 6. Click Server Manager > Roles > Web Server (IIS). 2.so 3. Provide a location for the DAVLockDB directive. In the Role Services section. Restart your web server. DAVLockDB "webserver_location/var/DavLock" Ensure that the directory exists. users can enter that location. Under Web Server > Common HTTP Features.so and modules/mod_dav_fs. 4. and then click Install. For example. Alias /images "path/shared_images" <Directory "path/shared_images"> Dav On Options Indexes MultiViews AllowOverride None Order allow. Add Dav On to the <Directory> information for the alias. For example. select Add Role Services. Results With WebDAV enabled. Programs and Features is available directly from the Control Panel. click Programs > Programs and Features. Configuring WebDAV on Microsoft IIS web servers: On Microsoft Internet Information Services (IIS) web servers. the default location for browsing is http://servername/ibmcognos/samples/images.so. Procedure 1. Uncomment the directives that load modules/mod_dav. Create an alias for the directory where your images are stored.

When users click Browse in the image browser. click Role-based or feature-based installation. expand samples. Under Connections. and add an authoring rule for the image files. if you installed the samples and you want to use the default path. and then right-click your server name. 6. Double-click WebDAV Authoring. Click Security. and then click Install. 11. select your server name. and select images. v If you are using Microsoft Windows 2008 Server. from theControl Panel. Click Next > Next. 14. 9. Sites. and add the appropriate permissions. Double-click WebDAV Authoring. For example. and click OK. expand Roles > Web Server (IIS). 16. If you are using Microsoft Windows 7 or 8. from theControl Panel. b. Select the directory or virtual directory to which you want to allow WebDAV access. In the Internet Information Services (IIS) Manager console. c. d. click Administrative Tools to access the Internet Information Services (IIS) Manager console. and viewing the properties for the displayed users. For example. double-clicking Authentication. 7. Right-click the directory or virtual directory you added authoring rules to. Results With WebDAV enabled. 15. 13. add permissions for the anonymous access user. Click Add Authoring Rule.a. 5. the default location for browsing is Chapter 6. 8. b. in Server Manager. and click Next. use the following steps: a. and click Edit Permissions. v If you are using Microsoft Windows 7. under Connections. and click Apply. v If you are using Microsoft Windows 8. and add the appropriate rules for your environment. Select your server. Select WebDAV Publishing. Installing and Configuring Server Components on Different Computers 183 . in Server Manager. v If you are using Microsoft Windows 2012 Server. 10. and then click Internet Information Services (IIS) Manager. click System and Security > Administrative Tools to access the Internet Information Services (IIS) Manager console. 12. expand your web server. In the Add Roles and Features Wizard. and click Next. You can find that user by select the website. select True for Allow Anonymous Property Queries. under the ibmcognos virtual directory. select IIS. Click Enable WebDAV. Report Studio users can add images to their reports. and click Internet Information Services (IIS) Manager. If you have anonymous access enabled. For example. and select WebDAV Publishing. select Default Web Site. Click WebDAV Settings. Expand Web Server (IIS) > Web Server > Common HTTP Features. if you allow anonymous access to your web server. Expand Internet Information Services > World Wide Web Services > Common HTTP Features. and select your website.

Ensure that your Web server is running.2. 184 IBM Cognos Business Intelligence Version 10. type the Gateway URI from IBM Cognos Configuration. Procedure 1.http://servername/ibmcognos/samples/images. http://host_name:port/ibmcognos The Welcome page of the IBM Cognos BI portal appears. Open a Web browser. 2. If you created another location.1: Installation and Configuration Guide . 3. For example. Test the Gateway You can test the installation using a Web browser. users can enter that location. In your address box.

Installing Framework Manager in directory that has an apostrophe in the path name may result in the help not opening properly. Install and configure all IBM Cognos BI server components before you install Framework Manager. All required files are copied to one computer. or if you install Framework Manager on a separate computer from IBM Cognos BI. you are prompted to do so during the installation.” on page 413. If you are not an administrator. Also. you must open them in the new version of Framework Manager. Install and Configure Modeling Tools for Reporting and Scorecarding After you install and configure IBM Cognos Business Intelligence server components. you can configure Framework Manager to use an external source control system. close all programs that are currently running to ensure that the installation program copies all the required files to your computer. you can install and configure the following modeling components for reporting and scorecarding: __ v __ v Framework Manager Metric Designer Installing and Configuring IBM Cognos Framework Manager You can install IBM Cognos Framework Manager. 2005. you must first uninstall the older version of Framework Manager. © Copyright IBM Corp. Default settings are used for the configuration. Before you install Framework Manager. see Chapter 18. ensure that you have administrator privileges for the Windows computer you are installing on. “Uninstalling IBM Cognos BI. the metadata modeling tool for IBM Cognos Business Intelligence for reporting. you can use the same models and projects that you used with the older version. 2013 185 . For more information. You can change these default settings if necessary. ask your system administrator to add you to the Administrator group on your computer. If you are upgrading Framework Manager from an older version. If you are installing the modeling tool in the same directory as IBM Cognos BI and do not stop the IBM Cognos services. Some servers do not support non-ASCII characters in directory names. or on a different computer. Install in a directory that contains only ASCII characters in the path name. on the same computer as other IBM Cognos BI components. and secure different versions of your metadata. If you upgraded from an older version of Framework Manager. share.Chapter 7. For more information. Administrator privileges are also required for the account that is used to run Framework Manager. To help you manage. see the section about using external repository control in the Framework Manager User Guide. To upgrade existing projects.

You can also change them by editing the cogstartup.cgi http://localhost:9300/ p2pd/servlet/dispatch 9362 Description The URI to the IBM Cognos BI gateway The URI to the dispatcher The port used by the local log server Dispatcher URI for external applications Log Server Port After installation.System Requirements for Framework Manager Before you install Framework Manager. 186 IBM Cognos Business Intelligence Version 10. Default settings for Framework Manager Component Gateway Default http://localhost:80/ ibmcognos/cgi-bin/ cognos.2. you must install Cognos Framework Manager on a Windows computer. DB2. For more information. Default Settings for Framework Manager The following table lists the default settings for the IBM Cognos BI ports and URIs that are used by Framework Manager. you can configure Framework Manager to use an external source control system. see the section about using external repository control in the Framework Manager User Guide.xml file in the c10_location\configuration directory. Microsoft SQL drivers are installed with IBM Cognos BI by default) Database connectivity set up Other Microsoft Data Access Component (MDAC) 2. System requirement for Framework Manager Requirement Operating system RAM Specification Windows Minimum: 512 MB Optimal: 1 GB Disk space Database Minimum: 500 MB of free space on the drive that contains the temporary directory used by IBM Cognos BI Database client software installed on the same computer as Framework Manager (Oracle. Table 46. Table 45. The size of your models determines the hardware requirements.6 or later for use with product samples To help you manage. such as disk space.1: Installation and Configuration Guide . and secure different versions of your metadata. share. ensure that the Windows computer meets IBM Cognos BI software and hardware requirements. The following table lists the minimum hardware and software requirements to run Framework Manager. Installing Framework Manager For a complete installation of IBM Cognos Business Intelligence. or Sybase only. you can use the configuration tool to change the default settings.

Commonly. The language that you select determines the language of the user interface. Framework Manager creates and manages metadata for the reporting functions. If you install it on a 32-bit operating system. v Go to the location where the installation files were downloaded and extracted and then double-click the issetup. you cannot install it to the same location as the 64-bit IBM Cognos BI server components. 6.exe file. Secure the installation directory from unauthorized access. Install and Configure Modeling Tools for Reporting and Scorecarding 187 . your installation includes only the English version of the guide. You can choose to configure Cognos Framework Manager later by starting the configuration tool from the Windows Start menu. 3. When notified with an information message about installing the Supplementary Languages Documentation. You can change the user interface to any of the installed languages after installation. Follow the directions in the installation wizard to copy the required files to your computer. select Start IBM Cognos Configuration to configure Cognos Framework Manager immediately. You can change these default settings during the installation or later. these things depend on the other technology you use for your data or import source. What to do next Default settings are used for the configuration. Set variables for data source connections for Framework Manager The IBM Cognos BI modeling tools create and manage metadata. Start the installation program. Select the language to use for the installation. click OK The Supplementary Languages Documentation contains translated versions of Guidelines for Modeling Metadata. 2. to better suit your environment. v Insert the product disk. All supported languages are installed. On the last page of the installation wizard. there are several things you must think about or do when you set up the data source environment for Framework Manager. 4. 7. stop the IBM Cognos service. go to the operating system directory. Chapter 7. Because metadata is derived from data sources in multi-platform or multilingual environments. You must install it to another location. you can install it to the same location as the 32-bit IBM Cognos BI server components or in another location.exe file. If the installation wizard does not open automatically. install the contents of the disk. If required. and double-click the issetup. Procedure 1. 5. If you install it on a 64-bit operating system. If you want this guide available in languages in addition to English. This step is only required if you are installing to the same location where the 32-bit IBM Cognos BI server components are installed and you want to install Framework Manager to the same location. Otherwise.Framework Manager is a 32-bit application.

If you upgraded from an older version of Framework Manager. SUGU. RFC1.2. RSOB. add $ORACLE_HOME/lib to your LD_LIBRARY_PATH variable. Error messages. set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager or Metric Designer and the IBM Cognos BI server are installed by typing the following command: NLS_LANG = language_territory. SDTX. configure the following authorization objects so that the modeling tool can retrieve metadata. sort order. set the DB2CODEPAGE environment variable to a value of 1252. Users operating in different languages can connect to an MSAS 2005 data source from the same instance of IBM Cognos BI. If you use a Sybase data source. No settings are required for SAP BW. see the DB2 documentation. you may want to modify the values on the SAP system. RS_UNIFICATION. these steps are not necessary. For more information about whether to use this optional environment variable. When you set the load library paths. Set the Name of RFC to be protected field to SYST. Set the environment variable for multilingual support: v For Oracle. 3. and calendar conventions automatically adapt to the native language and locale. numeric. which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory if you installed a 64-bit Oracle client. 2. Where default values are specified. ensure that the 32-bit Oracle libraries are in the library search path. see the IBM Cognos Administration and Security Guide.character_set Examples are: NLS_LANG = AMERICAN_AMERICA. For Japanese and Korean currency symbols to appear correctly. For Oracle.UTF8 NLS_LANG = JAPANESE_JAPAN. Modelers must create a separate package for each language. For SAP BW. SU_USER. RSAB. For more information about data source connections. Perform the following steps in the location where you installed Framework Manager. time. date. You must set up the data source environment only if you installed Framework Manager in a different location from the older version. you are not required to set up anything in the data source environment. monetary. Procedure 1. v For DB2. you must install the additional fonts from the Supplementary Language Documentation disk.1: Installation and Configuration Guide . Users can run reports in any language.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. SAP support only a single code page on non-Unicode SAP BW systems. Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. v S_RFC Set the Activity field to 16. 188 IBM Cognos Business Intelligence Version 10.

you must configure it to communicate with the other components. For security reasons. Set the InfoObject field to InfoObject Technical Name. Set the InfoCube sub-object field to the values DATA and DEFINITION. The new authorization group restricts the user's access to the table only. see Transaction SU03. v S_RS_HIER Set the Activity field to 71. v S_RS_COMP1 Set the Activity field to the default value. create an authorization group and assign the table RSHIEDIR to it. Install and Configure Modeling Tools for Reporting and Scorecarding 189 . v S_RS_COMP Set the Activity field to the default value. Set the Name (ID) of reporting components field to the default value. Environment Properties for Framework Manager Computers When you install Framework Manager on a different computer from the non-modeling components of IBM Cognos BI. no configuration is required if you v configure your Web server using the default virtual directories v use the default ports v use the default resources Chapter 7.Set the Type of RFC object to be protected field to FUGR. If you install Framework Manager on the same computer as the non-modeling components of IBM Cognos BI. v S_TABU_DIS Set the Activity field to 03. Set the Version field to Hierarchy Version. Set the Info Area field to InfoArea Technical Name. Set the Type of reporting components field to the default value. Note: &NC& represents any table that does not have an authorization group. Set the InfoCube field to InfoCube Technical Name. Set the User group in user master main field to the default value. v S_USER_GRP Set the Activity field to 03. Set the Hierarchy Name field to Hierarchy Name. Set the Owner (Person Responsible) field to the default value. Set the Authorization Group field to &NC&. Set the Info Area field to InfoArea Technical Name. 05. which is needed by the modeling tool. v S_RS_ICUBE Set the Activity field to 03. Create the authorization group as a customization in the SAP system. For more information about SAP BW authorization objects. Set the Info Cube field to the value: InfoCube Technical Name. Set the Type of reporting components field to the default value. Set the Name (ID) of reporting components field to the default value.

v use the default cryptographic settings If IBM Cognos BI was installed in more than one location. click Environment. Configuring Framework Manager inside the network firewall Use the following steps to set up communication between Framework Manager and the other IBM Cognos Business Intelligence components when Framework Manager is inside a network firewall. Installations with a Firewall When the modeling tool is outside a network firewall that protects the Application Tier Components. communication issues with the dispatcher can arise. use the following syntax: http://host_name:port/ibmcognos/cgi-bin/module_alias v If server has been configured to use the servlet gateway. For more information about configuring the dedicated gateway computer.2. use the following syntax: http[s]://host_name:port/context_root/servlet/Gateway 190 IBM Cognos Business Intelligence Version 10. you can install the modeling tool in the same architectural tier as the Application Tier Components or you can install and configure a gateway that is dedicated to modeling tool communications. To avoid communication issues. For more information about the modeling tool and network firewalls. This ensures that the certificate authority service issues a certificate to the Framework Manager computer.cgi with cognosisapi. ensure that all URIs point to the correct version of IBM Cognos BI. On the computer where you installed Framework Manager. 2. In the Explorer window. in the Gateway URI box. see “Firewall considerations” on page 24. Framework Manager must be configured to use the same version of IBM Cognos BI. see “Configure Environment and Security Properties for Gateway Computers” on page 171. 3. The steps in this topic describe how to configure the modeling tool computer when the computer is inside or outside of the network firewall. v If your web server has been configured to use Apache modules. start IBM Cognos Configuration. v If your web server has been configured for the ISAPI gateway. Prerequisites Ensure that the IBM Cognos service on at least one Content Manager computer is running. replace cognos. type the appropriate value.1: Installation and Configuration Guide . Ensure that the Web server is configured and running .dll. You must also set up the data sources before you configure Framework Manager. Procedure 1. In the Properties window.

Change the localhost portion of the Gateway URI to either the IP address or the host name of the dedicated gateway server. type the appropriate value for the server you are using as the dedicated gateway. Specify the value for the Dispatcher URI for external applications by typing the URI of the internal dispatcher on the server where Application Tier Components are installed. In the Explorer window. for the Password property. Ensure that you change the host name in the URI from localhost. Change the host name portion of the Gateway URI from localhost to either the IP address or the host name of the computer where the Gateway component is installed. 7. the default cryptographic provider. Set up a dedicated gateway for Framework Manager. 8. Under the Certificate Authority settings property group. click Cognos. From the File menu. the default cryptographic provider. 9. type the same password you configured on the default active Content Manager computer. Procedure 1. v If your web server has been configured for the ISAPI gateway. 10. under Cryptography. type the same password you configured on the default active Content Manager computer. change the Dispatcher URIs for gateway property to the URI of the dispatcher on the server where Application Tier Components are installed. Configuring Framework Manager outside the network firewall Use the following steps to set up communication between Framework Manager and the other IBM Cognos Business Intelligence components when Framework Manager uses a dedicated gateway and is outside the network firewall.4. From the File menu. under Cryptography. This value will be the same as the Internal dispatcher URI property on your Application Tier Components computer. start IBM Cognos Configuration. Specify the value for the Dispatcher URI for external applications by typing the URI of the server where Application Tier Components are installed. 6. Install and Configure Modeling Tools for Reporting and Scorecarding 191 . 4. Chapter 7. 7. On the dedicated gateway. In the Explorer window. This value will be the same as the Internal dispatcher URI property on your Application Tier Components computer. In the Properties window. for the Password property. On the computer where you installed Framework Manager. replace cognos.cgi with cognosisapi. use the following syntax: http[s]://host_name:port/context_root/servlet/Gateway 6. 3. click Environment. In the Explorer window. click Save. click Save.dll. use the following syntax: http://host_name:port/ibmcognos/cgi-bin/module_alias v If server has been configured to use the servlet gateway. 5. in IBM Cognos Configuration. Under the Certificate Authority settings property group. in the Gateway URI box. 5. 8. v If your web server has been configured to use Apache modules. click Cognos. 2.

System Requirements for Metric Designer Before you install Metric Designer. click Programs > IBM Cognos 10 > Framework Manager. The following table lists the minimum hardware and software requirements to run Metric Designer. from the Start menu. you can use the same extracts and projects that you used with the older version. you may want to change these default settings if existing conditions make the default choices inappropriate. your installation is working. you must open them in the new version of Metric Designer and redefine the data source connections and other references.1: Installation and Configuration Guide . It must be installed on a 32-bit Microsoft Windows operating system computer. You may be prompted to upgrade if the model schema version is older than the currently supported version. On Microsoft Windows 8 or Windows 2012 Server.Results Framework Manager is configured to communicate with the other components of IBM Cognos BI.0 or later. such as disk space. System requirements for Metric Designer Requirement Operating system Specification Windows (design interface) UNIX operating system (engine only): Sun Solaris HP-UX IBM AIX 192 IBM Cognos Business Intelligence Version 10. If you installed Framework Manager on a Microsoft Windows Vista operating system computer. Table 47. double-click the Framework Manager icon on the Start panel. If you upgraded from Metrics Manager version 2. or on a different computer. on the same computer as IBM Cognos BI components. If you see the Welcome page of Framework Manager. ensure that the Windows computer meets IBM Cognos BI software and hardware requirements. To upgrade existing projects. you must update file location properties on Windows Vista computers. Metric Designer is available as a 32-bit installation only. All required files are copied to one computer. Installing and Configuring Metric Designer You can install Metric Designer. Procedure To start Framework Manager. the metadata modeling tool for IBM Cognos Metrics Manager.2. or if you installed IBM Cognos BI on a different computer. Test the Framework manager installation You can test your configuration by starting the application and creating a project. The size of the your models determines the hardware requirements. However. Default settings are used for the configuration.

Install Metric Designer Use the following steps to install Metric Designer. If you are not an administrator. You can also change them by editing the cogstartup. Default Settings for Metric Designer The following table lists the default settings for the ports and URIs that are used by Metric Designer. you are prompted to do so during the installation. ask your system administrator to add you to the Administrator group on your computer. __ v Configure environment properties for Metric Designer.cgi http://localhost:9300/ p2pd/servlet/dispatch Description The URI to the gateway Dispatcher URI for external applications The URI to the dispatcher After installation. Framework Manager packages.6 or later for use with product samples To install and configure Metric Designer. If you are installing the modeling tool in the same directory as IBM Cognos BI and do not stop the IBM Cognos services. install Metric Designer to extract the data.xml file in the c10_location\configuration directory. including cubes. Default settings for Metric Designer Component Gateway Default http://localhost:80/ ibmcognos/cgi-bin/ cognos. System requirements for Metric Designer (continued) Requirement RAM Specification Minimum: 512 MB Optimal: 1 GB Disk space Other Minimum: 500 MB of free space on the drive that contains the temporary directory Microsoft Data Access Component (MDAC) 2. follow these steps: __ v Install Metric Designer Components. Chapter 7. Install and Configure Modeling Tools for Reporting and Scorecarding 193 . __ v Set up the import source environment for Metric Designer __ v Test the Metric Designer installation Related concepts: “Distributing Metric Designer components” on page 28 For Metric Studio. or Impromptu Query Definitions (. Ensure that you have administrator privileges for the Microsoft Windows computer you are installing on.iqd files). if you want to define and load metrics from relational and dimensional data sources. Table 48. you can use IBM Cognos Configuration to change the default settings. __ v Set up the database client for the metric store.Table 47.

If you are installing in a directory with other IBM Cognos BI components. Procedure 1. 2. v Click Finish. You should also install and configure the target application where you will load data or metadata. 3. 5. Results To ensure the security and integrity of IBM Cognos BI. go to the operating system directory. and double-click issetup. do the following: v If you want to see the log files. other IBM Cognos BI components must be installed and configured. Some servers do not support non-ASCII characters in directory names.exe. clear the check box. stop the IBM Cognos service. Set up the database client for an IBM DB2 metric store Use this procedure to setup the database client for an IBM DB2 metric store. v Go to the location where the installation files were downloaded and extracted and then double-click issetup. and Metric Designer must be installed. If the installation wizard does not open automatically. it is important to protect the installation directory from unauthorized or inappropriate access. you can select Start IBM Cognos Configuration to configure Metric Designer. close all programs that are currently running to ensure that the installation program copies all the required files to your computer. If the server components are not configured.Install in a directory that contains only ASCII characters in the path name. Before you configure Metric Designer. Select the language to use to run the installation wizard. 194 IBM Cognos Business Intelligence Version 10. Doing this allows Metric Designer to access the metric store database. Doing this allows Metric Designer to access the metric store database. 4. v If the server components are configured. you must install database client software and Java Database Connectivity (JDBC) drivers on each computer where you install Metric Designer. v If you want to see late-breaking information about the product. Follow the directions in the installation wizard to copy the required files to your computer. Before you begin Before you install Metric Designer. Setting up the database client for the Metric Store If you are using a database other than Microsoft SQL as a metric store. Do one of the following: v Insert the Metric Designer disk.1: Installation and Configuration Guide .2.exe. In the Finish page of the installation wizard. click View for the appropriate log file. select the check box for IBM Cognos Release Notes. You can start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu.

Install the SQL Loader utility on the Metric Designer computer. Configuring Metric Designer If you install Metric Designer on a different computer than your IBM Cognos servers. db2jcc_license_cu. the metric store name automatically becomes the alias. v the universal driver file. Installations with a Firewall When the modeling tool is outside a network firewall that protects the Application Tier Components. delete the file. Procedure Install the bcp utility on the Metric Designer computer.jcc. Note: If the metric store database and Metric Designer are on the same computer. For more information about the modeling tool and network firewalls. To avoid communication issues. you must set up the database driver and utility on the Metric Designer computer. you must set up the database utility on the Metric Designer computer. communication issues with the dispatcher can arise. If the metric store is on a different computer.jar Tip: To check the driver version. Set up the database client for a Microsoft SQL Server metric store If you use a Microsoft SQL Server database for the metric store. go to the ORACLE_HOME/jdbc/lib directory. Copy ojdbc5.ibm.db2. run the following command: java -cp path\db2jcc. you can install the modeling tool in the same architectural tier as the Application Tier Components or you can install and configure a gateway that is dedicated to modeling tool communications. Chapter 7. Procedure 1.zip file. On the computer where the Oracle client is installed. 3. Copy the following files from DB2_installation/sqllib/java directory to the c10_location/webapps/p2pd/WEB-INF/lib directory. 2.DB2Jcc -version If the directory contains a db2java. Install the IBM DB2 client software on your Metric Designer computer. you must configure it to communicate with the IBM Cognos servers. see “Firewall considerations” on page 24. 2. and can also be downloaded from the Oracle Web site.jar to the c10_location/webapps/p2pd/WEB-INF/lib directory on the computer where Metric Designer is installed. db2jcc. The driver is available from an Oracle client or server installation.Procedure 1.jar v the license file.jar com. configure a database alias to the metric store by running the IBM DB2 Client Configuration Assistant. Install and Configure Modeling Tools for Reporting and Scorecarding 195 . 3.jar or db2java. Set Up the Database Client for an Oracle Metric Store If you use an Oracle database for the metric store.

Users can run reports in any language. use the following syntax: http[s]://host_name:port/context_root/servlet/Gateway 4. On the computer where you installed Metric Designer. Users operating in different languages can connect to an MSAS 2005 data source from the same instance of IBM Cognos BI. In the Properties window. Results Metric Designer is configured to communicate with other IBM Cognos BI components. Commonly.2. there are several things you must think about or do when you set up the import source environment for Metric Designer. see the IBM Cognos Administration and Security Guide. Procedure 1. For more information about configuring the dedicated gateway computer. start IBM Cognos Configuration. Change the host name portion of the Gateway URI from localhost to either the IP address or the host name of the computer where the Gateway component is installed. 2. Metric Designer creates and manages metadata required for the scorecarding functions.1: Installation and Configuration Guide . Specify the value for the Dispatcher URI for external applications by typing the URI of the server where Application Tier Components are installed.cgi with cognosisapi.The steps in this topic describe how to configure the modeling tool computer when the computer is inside or outside of the network firewall. Modelers must create a separate package for each language. Because metadata is derived from data sources in multi-platform or multilingual environments. This value will be the same as the Internal dispatcher URI property on your Application Tier Components computer. 5. in the Gateway URI box. these things depend on the other technology you use for your data or import source. replace cognos. click Environment.dll. 6. Configure Metric Designer Use the following steps to configure Metric Designer for communication with the IBM Cognos servers. use the following syntax: http://host_name:port/ibmcognos/cgi-bin/module_alias v If server has been configured to use the servlet gateway. Set variables for your import sources for Metric Designer The IBM Cognos BI modeling tools create and manage metadata. In the Explorer window. type the appropriate value: v If your web server has been configured for the ISAPI gateway. From the File menu. click Save. v If your web server has been configured to use Apache modules. 3. For more information about data source connections. see “Configure Environment and Security Properties for Gateway Computers” on page 171. 196 IBM Cognos Business Intelligence Version 10.

Install and Configure Modeling Tools for Reporting and Scorecarding 197 . the 32-bit libraries are in the ORACLE_HOME/lib32 directory. which is usually the ORACLE_HOME/lib directory. Create the authorization group as a customization in the SAP system. RSOB. time. For Oracle. Use the following steps to set up Metric Designer for Oracle. you must install the additional fonts from the Supplementary Language Documentation disk. v S_TABU_DIS Set the Activity field to 03. Set the Authorization Group field to &NC&. set the DB2CODEPAGE environment variable to a value of 1252. Note: &NC& represents any table that does not have an authorization group. and calendar conventions automatically adapt to the native language and locale. Error messages. numeric. No settings are required for SAP BW. Where default values are specified. Set the environment variable for multilingual support: v For Oracle. monetary.UTF8 NLS_LANG = JAPANESE_JAPAN. Set the Name of RFC to be protected field to SYST. Procedure 1. add $ORACLE_HOME/lib to your LD_LIBRARY_PATH variable. see “Installing additional language fonts” on page 213. For more information about whether to use this optional environment variable. When you set the load library paths. which is needed by the modeling tool. RFC1. v For DB2. Chapter 7. SDTX. If you installed the 64-bit Oracle 10g client. sort order. For Japanese and Korean currency symbols to appear correctly.character_set Examples are: NLS_LANG = AMERICAN_AMERICA. RSAB. SUGU. you may want to modify the values on the SAP system. 3. For security reasons. create an authorization group and assign the table RSHIEDIR to it. For SAP BW. For more information. v S_RFC Set the Activity field to 16. RS_UNIFICATION. DB2. The new authorization group restricts the user's access to the table only. date. or SAP BW import sources. see the DB2 documentation. SU_USER. Set the Type of RFC object to be protected field to FUGR. set the NLS_LANG (National Language Support) environment variable on each computer where Metric Designer or the Application Tier Components for IBM Cognos Metrics Manager are installed by typing the following command: NLS_LANG = language_territory. configure the following authorization objects so that the modeling tool can retrieve metadata.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI.Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. SAP support only a single code page on non-Unicode SAP BW systems. ensure that the 32-bit Oracle libraries are in the library search path. 2.

information about SAP BW authorization objects. Set the Hierarchy Name field to Hierarchy Name. Set the Name (ID) of reporting components field to the default value. Info Area field to InfoArea Technical Name. Set the Version field to Hierarchy Version. InfoCube sub-object field to the values DATA and DEFINITION. Set the Info Cube field to the value: InfoCube Technical Name. Set the Info Area field to InfoArea Technical Name.2. 198 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide . If you see the Welcome page of Metric Designer. Set the User group in user master main field to the default value.v S_USER_GRP Set the Activity field to 03. v S_RS_HIER Set the Activity field to 71. On Microsoft Windows 8 or Windows 2012 Server. Procedure To start Metric Designer. see Transaction Test the Metric Designer installation You can test your configuration by starting the application and creating a project. 05. Set the Name (ID) of reporting components field to the default value. v S_RS_ICUBE Set the Activity field to 03. v S_RS_COMP Set the Activity field to the default value. Set the Type of reporting components field to the default value. Set the Owner (Person Responsible) field to the default value. Set the InfoObject field to InfoObject Technical Name. click Programs > IBM Cognos 10 > Metric Designer. your installation is working. Set the Set the Set the For more SU03. from the Start menu. InfoCube field to InfoCube Technical Name. Set the Type of reporting components field to the default value. v S_RS_COMP1 Set the Activity field to the default value. double-click the Metric Designer icon on the Start panel.

Install and configure optional components Optional components provide extended functionality for users. You can install IBM Cognos Transformer on the same computer as IBM Cognos Series 7 Transformer. Transformer can be made available more easily for business specialists who want to design models and build PowerCubes for their own use. v IBM Cognos Transformer v Translated Product Documentation v Additional fonts for Japanese and Korean currency symbols v IBM Cognos BI for Microsoft Office IBM Cognos Transformer You can install IBM Cognos Transformer. You can change these default settings if necessary. 32-bit components are installed to /ibm/cognos/c10. v IBM Cognos Transformer client This component must be installed on a Windows computer. 2005.Chapter 8. It must be on a 32-bit system or in a separate directory from 64-bit IBM Cognos components on a 64-bit system. Tasks to Install and Configure IBM Cognos Transformer To install and configure IBM Cognos Transformer. you can install the following optional components. perform these tasks: __ v Install IBM Cognos Transformer __ v Review default settings __ v __ v © Copyright IBM Corp. but in a separate directory from 64-bit IBM Cognos BI components. Default settings are used for the configuration. on the same computer as other IBM Cognos BI components. downloadable installation program from a corporate or secured portal. IT departments can provide business specialists or Transformer modelers with a Web-based. The installation requirements are as follows: v UNIX and Linux operating system utility for building PowerCubes This component can be installed on a 64-bit system. 2013 Configure IBM Cognos Transformer Set up the data source environment for Transformer 199 . or on a different computer. For example. IBM Cognos Transformer and 64-bit Systems IBM Cognos Transformer is only available in a 32-bit version. For example. allowing for easy distribution of the installation files. 64-bit components are installed to /ibm/cognos/c10_64 by default. or if you install IBM Cognos Transformer on a separate computer from IBM Cognos BI. After you install and configure IBM Cognos Business Intelligence server components and modeling tools. the metadata modeling tool for creating PowerCubes for use with IBM Cognos BI.

xml file. Before you install IBM Cognos Transformer. Models that contain an IQD data source are not supported on Linux. All components are installed in both environments and you then use the features and tools that are appropriate for each environment. such as disk space. System Requirements for IBM Cognos Transformer Before you install IBM Cognos Transformer. You must install and configure all IBM Cognos BI server components before you install IBM Cognos Transformer. All available languages are installed. Related concepts: “Distributing Transformer components” on page 26 Transformer can be installed on a computer that contains other IBM Cognos BI components or on a computer that is separate from other IBM Cognos BI components. close all programs that are currently running to ensure that the installation program copies all the required files to your computer.__ v Test the IBM Cognos Transformer installation Install IBM Cognos Transformer You install Transformer if you plan to create PowerCubes for use with IBM Cognos BI. The size of your PowerCubes determines the hardware requirements. You then build cubes on your UNIX or Linux computer. ensure that the computer meets IBM Cognos BI software and hardware requirements. the installation of IBM Cognos Transformer is not complete until you also install IBM Cognos Transformer on a computer with a Microsoft Windows operating system. if you do not have Administrator privileges on the computer and you make changes to the cogtr.1: Installation and Configuration Guide . ask your system administrator to add you to the Administrator group on your computer. Some servers do not support non-ASCII characters in directory names. For example. the updated file is saved by default to a Virtual Store directory and not to the c10_location/configuration directory. If you are not an administrator. If you are installing on Windows. ensure that you have administrator privileges for the Windows computer you are installing on. Install in a directory that contains only ASCII characters in the path name. Transformer can be used as a standalone product or it can be configured to communicate with other IBM Cognos BI components. The language that you select in the installation wizard determines the language of the user interface for both the installation wizard and for IBM Cognos Transformer. With a UNIX or Linux operating system.2. When installed separately. Note: When Transformer is installed on Windows Vista. the IBM Cognos Transformer client provides a graphical user interface for designing models on Windows computers. 200 IBM Cognos Business Intelligence Version 10. The following table lists the minimum hardware and software requirements to run IBM Cognos Transformer.

type pfs_mount -t rrip <device><mount_dir> -o xlat=unix For example. 3./issetup 4. If installing from a disk. 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 disk from this drive. System requirements for Transformer Requirement Operating system Specification Windows UNIX: Sun Solaris. v When the installation is complete. go to the operating system directory and then type . mount the IBM Cognos Transformer modeling disk using Rock Ridge file extensions. 2. go to the location where the installation files were downloaded and extracted. For example. do the following: v Add the pfs_mount directory in your path. IBM AIX Linux RAM Minimum: 512 MB Optimal: 4 GB Disk space Minimum: 500 MB of free space on the drive that contains the temporary directory used by IBM Cognos BI Database client software installed on the same computer as IBM Cognos Transformer Database connectivity set up Other Microsoft Data Access Component (MDAC) 2. type bg pfs_mountd and then type bg pfsd v To mount the drive. To mount the disk on HP-UX. HP-UX. Procedure 1.6 or later for use with product samples Data source Installing IBM Cognos Transformer on UNIX or Linux operating systems Use the following steps to install IBM Cognos Transformer on UNIX or Linux operating systems. type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the disk. PATH=/usr/sbin/:$PATH export PATH v To start the required NFS daemons and run the daemons in the background. Install and configure optional components 201 . To start the installation wizard. Select the language to use for the installation.Table 49. If installing from a download. Chapter 8.

Tip: The Series 7 IQD Bridge component is not supported on Linux and HP-UX Itanium. 4. click OK to continue.The language that you select in the installation wizard determines the language of the user interface for both the installation wizard and for IBM Cognos Transformer. The language that you select in the installation wizard determines the language of the user interface for both the installation wizard and for IBM Cognos Transformer. click View for the appropriate log file. You can later configure Transformer using IBM Cognos Configuration by typing cogconfig. select the check box for IBM Cognos Release Notes. When you are prompted about installing non-English product documentation. and double-click issetup. v If you want to see late-breaking information about the product. Follow the directions in the installation wizard and copy the required files to your computer.sh in thec10_location/bin64directory. 2. 202 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide . When you are prompted about installing non-English product documentation. Select the language to use for the installation. v Click Finish. In the Finish page of the installation wizard. Do one of the following: v Insert the IBM Cognos Transformer modeling disk. 8. v Do not configure Transformer immediately because you must do other tasks first to ensure that your environment is properly set up. 3. click OK to continue. Ensure that the IBM Cognos Configuration check box is clear. The man page for IBM Cognos Transformer is accessible in UNIX by typing cogtr man from the c10_location/bin64 directory. 7. do the following: v If you want to see the log files. v Go to the location where the installation files were downloaded and extracted and then double-click issetup.exe. 5. do the following: v If you want to see the log files.html document provides the syntax for UNIX command line options that are supported by IBM Cognos Transformer.exe. 6. Follow the directions in the installation wizard to copy the required files to your computer.html The cogtr_a. In the Finish page of the installation wizard. Create a MANPATH environment variable and configure it with the following value: /c10_location/webcontent/documentation/en/cogtr_a. If the installation wizard does not open automatically. All available languages are installed. Procedure 1. go to the operating system directory.2. All available languages are installed. Installing IBM Cognos Transformer on Windows operating systems Use the following steps to install IBM Cognos Transformer on Microsoft Windows operating systems. click View for the appropriate log file. 5.

You can also change them by editing the cogstartup. communication issues with the dispatcher can arise. Default settings for Transformer Component Gateway Default http://localhost:80/ ibmcognos/cgi-bin/ cognos. Chapter 8. v Click Finish. ensure that all URIs point to the correct version of IBM Cognos BI. The instructions in this topic are for the installer or administrator. you can install the modeling tool in the same architectural tier as the Application Tier Components or you can install and configure a gateway that is dedicated to modeling tool communications. Install and configure optional components 203 . You can start IBM Cognos Configuration using the IBM Cognos Configuration shortcut from the Start menu.xml file in the c10_location\configuration directory. Transformer must be configured to use the same version of IBM Cognos BI. v Do not configure Transformer immediately because you must do other tasks first to ensure that your environment is properly set up. For more information about the modeling tool and network firewalls.cgi http://localhost:9300/ p2pd/servlet/dispatch Description The URI to the IBM Cognos BI gateway The URI to the dispatcher Dispatcher URI for external applications After installation. If you are the Transformer modeler or business specialist who wants to download and use Transformer. select the check box for IBM Cognos Release Notes. Installations with a Firewall When the modeling tool is outside a network firewall that protects the Application Tier Components. For more information. Communication between Transformer and Business Intelligence components You must configure IBM Cognos Transformer to communicate with the other IBM Cognos BI components. If you are using a gateway that is dedicated to the modeling tool. To avoid communication issues. you can use the configuration tool to change the default settings. see “Installing and Configuring the Gateway” on page 165. Ensure that the IBM Cognos Configuration check box is clear.v If you want to see late-breaking information about the product. see “Firewall considerations” on page 24. you must also configure the gateway computer. Default Settings for IBM Cognos Transformer The following table lists the default settings for the IBM Cognos BI ports and URIs that are used by IBM Cognos Transformer. Table 50. The steps in this topic describe how to configure the modeling tool computer. see “Deploying IBM Cognos Transformer for Modelers” on page 211 If IBM Cognos BI was installed in more than one location.

start IBM Cognos Configuration.dll.2. 2. v If your web server has been configured to use Apache modules. This value will be the same as the Internal dispatcher URI property on your Application Tier Components computer. In the Properties window. If you install IBM Cognos Transformer on the same computer as the non-modeling components of IBM Cognos BI. no configuration is required if you v configure your Web server using the default virtual directories v use the default ports v use the default resources v use the default cryptographic settings Before you begin Install and configure IBM Cognos BI components before you configure IBM Cognos Transformer. Change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. 204 IBM Cognos Business Intelligence Version 10. Procedure 1. click Environment. use the following syntax: http[s]://host_name:port/context_root/servlet/Gateway 4. Specify the value for the Dispatcher URI for external applications by typing the URI of the server where Application Tier Components are installed. in the Gateway URI box. v If your web server has been configured for the ISAPI gateway. On the computer where you installed IBM Cognos Transformer. click Save. Log on as an administrator.1: Installation and Configuration Guide . This ensures that the certificate authority service issues a certificate to the IBM Cognos Transformer computer. update your file location properties: a.cgi with cognosisapi. 6. You must first install and configure Content Manager and then start the IBM Cognos service on at least one Content Manager computer before you configure IBM Cognos Transformer. IBM Cognos Transformer is configured to communicate with the other components of IBM Cognos BI. or if any IBM Cognos BI component is installed on a Windows Vista computer. replace cognos. 3. In the Explorer window. 5. From the File menu. 7. If you installed Transformer on a Windows Vista computer. type the appropriate value.Configure IBM Cognos Transformer computers You must configure IBM Cognos Transformer to communicate with other IBM Cognos BI components. Ensure that the Web server is configured and running. ensure that the database client is installed on the computer where Transformer is installed. To support the use of IBM Cognos BI data sources (including packages and reports) in Transformer. use the following syntax: http://host_name:port/ibmcognos/cgi-bin/module_alias v If server has been configured to use the servlet gateway.

.b. Users operating in different languages can connect to an MSAS 2005 data source from the same instance of IBM Cognos BI. you must install the additional fonts from the Supplementary Language Documentation disk. Save the file. Data Sources and Transformer The IBM Cognos BI modeling tools create and manage metadata. see the Administration and Security Guide. Modelers must create a separate package for each language. see “Installing additional language fonts” on page 213. with the same environment variable and root directory as you use for file locations on the other IBM Cognos BI computers.sample in a text editor. Locate all values that use a relative path.”.xml. IBM Cognos Transformer creates and manages metadata for PowerCubes. you must create a separate IBM Cognos BI instance for each language. open cs7g. these things depend on the other technology you use for your data or import source. Install and configure optional components 205 . Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. open cogtr. “. Add the locations for your IBM Cognos Series 7 data sources to the file.ini in a text editor. In the c10_location\CS7Gateways\bin directory. d. “. these steps are not necessary. Commonly. Users can run reports in any language. Transformer can be used as a standalone product or it can be configured to communicate with other IBM Cognos BI components. For more information. Save the file as cogtr. Related concepts: “Distributing Transformer components” on page 26 Transformer can be installed on a computer that contains other IBM Cognos BI components or on a computer that is separate from other IBM Cognos BI components. Replace the relative path element. Changes are applied the next time you open Transformer. When installed separately. c. Set Up the Data Source Environment for Transformer Use these steps to set up Oracle or SAP BW data sources for IBM Cognos Transformer. h. In the c10_location\configuration directory. f.\directory”. If users operating in different languages will be connecting to a Microsoft Analysis Services (MSAS) 2000 data source. Set the environment variable for multilingual support: Chapter 8. Because metadata is derived from data sources in multi-platform or multilingual environments. For Japanese and Korean currency symbols to appear correctly.. For more information about data source connections. g. If you use a Sybase data source. e.xml. there are several things you must think about or do when you set up the data source environment for IBM Cognos Transformer. Procedure 1.

see the DB2 documentation. Set the Info Area field to InfoArea Technical Name. which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory if you installed a 64-bit Oracle client. For SAP BW. time. When you set the load library paths. Where default values are specified. SDTX. Error messages. date. RFC1.2. RSOB. Note: &NC& represents any table that does not have an authorization group. SAP support only a single code page on non-Unicode SAP BW systems. For more information about whether to use this optional environment variable. add $ORACLE_HOME/lib to the library path. 3. v S_TABU_DIS Set the Activity field to 03. set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager or Metric Designer and the IBM Cognos BI server are installed by typing the following command: NLS_LANG = language_territory. Set the Name of RFC to be protected field to SYST. v S_RS_COMP1 206 IBM Cognos Business Intelligence Version 10. Set the Type of reporting components field to the default value. create an authorization group and assign the table RSHIEDIR to it. configure the following authorization objects so that the modeling tool can retrieve metadata. Create the authorization group as a customization in the SAP system. monetary. The new authorization group restricts the user's access to the table only. v S_RS_COMP Set the Activity field to the default value. 05. sort order. RSAB. No settings are required for SAP BW. v For DB2. set the DB2CODEPAGE environment variable to a value of 1252. Set the Info Cube field to the value: InfoCube Technical Name. numeric. 2. RS_UNIFICATION. Set the Type of RFC object to be protected field to FUGR. you may want to modify the values on the SAP system. v S_USER_GRP Set the Activity field to 03.v For Oracle. SUGU. For Oracle. Set the Authorization Group field to &NC&. ensure that the 32-bit Oracle libraries are in the library search path. For security reasons. and calendar conventions automatically adapt to the native language and locale. SU_USER.UTF8 The value of the variable determines the locale-dependent behavior of IBM Cognos BI. Set the Name (ID) of reporting components field to the default value.character_set Examples are: NLS_LANG = AMERICAN_AMERICA.1: Installation and Configuration Guide . Set the User group in user master main field to the default value.UTF8 NLS_LANG = JAPANESE_JAPAN. v S_RFC Set the Activity field to 16. which is needed by the modeling tool.

Microsoft changed the structure of user directories. Set the Name (ID) of reporting components field to the default value. Set the InfoCube field to InfoCube Technical Name. double-click the IBM Cognos Transformer icon on the Start panel. For more information about SAP BW authorization objects. Procedure To start IBM Cognos Transformer. Test your Transformer installation You can test your configuration by starting the application and creating a model. Set the InfoObject field to InfoObject Technical Name. Set the Owner (Person Responsible) field to the default value. click Programs > IBM Cognos 10 > IBM Cognos Transformer. see Transaction SU03.Set the Activity field to the default value. v S_RS_ICUBE Set the Activity field to 03. your installation is working. Set the Type of reporting components field to the default value. you must edit the default preferences settings. you must change the default preferences to a common location Chapter 8. If you want all users to have the same default directories.exe file in the c10_location\bin directory. To start IBM Cognos Transformer manually.samples file as a template. If you see the Transformer window. Install and configure optional components 207 . you can perform these tasks: v Create a network installation location for Transformer modelers v Export configuration data for Transformer modelers v Deploy IBM Cognos BI Transformers for modelers Update Default Preferences for Windows Vista With security enhancements in Windows Vista. v S_RS_HIER Set the Activity field to 71.samples file as a templateUpdate default preferences for Windows Vista v If you want to use Transformer models from IBM Cognos Series 7 and you want to continue to use IQD data sources. Set the Hierarchy Name field to Hierarchy Name.xml. Set the Version field to Hierarchy Version. from the Start menu. you can perform these tasks: v If you installed Transformer on a Windows Vista computer. and you plan to use the cogtr. double-click the cogtr. If you want to use the cogtr. On Microsoft Windows 8 or Windows 2012 Server. Set the InfoCube sub-object field to the values DATA and DEFINITION. Set the Info Area field to InfoArea Technical Name.Add IBM Cognos Series 7 Data Sources to the Transformer To make Transformer available for modelers to install and use. Additional configuration tasks for IBM Cognos Transformer After you install Transformer.xml.

. delete the preferences specified in step 3 from the file. The changes are applied the next time you open Transformer. change the directories to a location to which all users have read and write access..2..to which users have access.\logs"/> v <Preference Name="ModelSaveDirectory" Type="string" Value=". The directories to change are as follows: v <Preference Name="CubeSaveDirectory" Type="string" Value=". In the c10_location\configuration directory. Temporary files location property 5. you must add the location of your IBM Cognos Series 7 data sources to the Transformer gateway file. under Environment. 2.sample in a text editor in elevated mode by right-clicking on the text editor and selecting Run as Administrator.\temp"/> 4.1: Installation and Configuration Guide .\temp"/> v <Preference Name="LogFileDirectory" Type="string" Value=".\temp"/> v <Preference Name="DataSourceDirectory" Type="string" Value=". If you want users to have the Windows Vista directories..xml. The Windows Vista default directories for Transformer are v CubeSaveDirectory Documents\Transformer\PowerCubes v DataSourceDirectory In IBM Cognos Configuration. 3..xml. If you want users to have the Windows Vista default directories. Change other settings as required. 208 IBM Cognos Business Intelligence Version 10. Temporary files location property v LogFileDirectory Documents\Transformer\Logs v ModelSaveDirectory Documents\Transformer\Models v ModelWorkDirectory In IBM Cognos Configuration.. If you want all users to have the same default directories. you can delete the default preferences for the directories. 6. see “Deploying IBM Cognos Transformer for Modelers” on page 211 Procedure 1. Add IBM Cognos Series 7 Data Sources to Transformer If you plan to use Transformer models and data sources from IBM Cognos Series 7. If you are the Transformer modeler or business specialist who wants to download and use Transformer. Save the file as cogtr. open cogtr. Data files location property v DataWorkDirectory In IBM Cognos Configuration.\temp"/> v <Preference Name="DataWorkDirectory" Type="string" Value=". The instructions in this topic are for the installer or administrator. under Environment.\temp"/> v <Preference Name="ModelWorkDirectory" Type="string" Value=". Log on as the administrator. under Environment.

The instructions in this topic are for the installer or administrator. If you are the Transformer modeler or business specialist who wants to download and use Transformer. Log on as the administrator. v Modelers must have privileges to create a data source in IBM Cognos Administration. Modelers do not need direct access to IBM Cognos Administration. Modelers can transfer models and execute cube builds using scripts. Add the locations for your IBM Cognos Series 7 data sources to the file. Create a Network Installation Location for Transformer Modelers Your organization may have specialized business or power users who want to build PowerCubes that are modeled on a combination of corporate and personal data sources. For more information. In the c10_location/CS7Gateways/bin directory. on the Transformer computers that are used to access IBM Cognos BI data sources or IBM Cognos Series 7 IQD data sources. see “Deploying IBM Cognos Transformer for Modelers” on page 211 Procedure 1. see the Administration and Security Guide. If you are the Transformer modeler or business specialist who wants to download and use Transformer.The instructions in this topic are for the installer or administrator. where modelers can run the file to launch the IBM Cognos Transformer installation wizard. see “Deploying IBM Cognos Transformer for Modelers” on page 211 Before you begin Before you make the installation file available to Transformer modelers. open cs7g. Install and configure optional components 209 . Modelers can also use automated methods to build PowerCubes. 3. exit the wizard. 2. You can provide modelers with a secured folder in IBM Cognos Connection in which to publish PowerCube packages.ini in a text editor. They can create and update data sources by using Transformer or command line tools. If the Welcome page of the installation wizard appears. open it in elevated mode by right-clicking on the text editor and selecting Run as Administrator. The changes are applied the next time you open Transformer. An installer or administrator can download an executable file to a Web or LAN location. 2. This location must also be accessible to the IBM Cognos service and can be a secured share on a LAN. Save the file. On Windows Vista. v To build PowerCubes on a specific Transformer server. other resources and permissions must be set up: v Database client software is installed. Insert the disk for IBM Cognos Transformer modeling product. Chapter 8. or available for modelers to install. These users may want to do their own analysis of the data for their line of business or a small group of users. v Modelers must have access to a location in which to store the PowerCube after building it. Procedure 1. modelers should have FTP privileges to transfer models and execute privileges to build cubes on that server. 4.

Procedure 1. On the disk. 5. The modelers can copy the exported configuration file to their Transformer installation directory and then run the command to configure the Transformer computer silently.xml file from the source computer to the same Web or LAN location as the Transformer installation file. Copying updated Transformer configuration files: If you updated certain configuratoin files. Configuration Data for Transformer Modelers If you want to make the Transformer installation file available to Transformer modelers. 6.xml file is c10_location/configuration. In the File name box. see “Deploying IBM Cognos Transformer for Modelers” on page 211 If you updated the coglocale. locate and open the folder.xml. Rename the exported file to cogstartup. copy the coglocale. In IBM Cognos Configuration.xml file from the source computer to the same Web or LAN location as the Transformer installation file. Click Save.3. locate the C8transformerinstall. you must copy them to the same location as the Transformer installation file. the modelers will need the dispatcher and encryption settings to configure Transformer on their local computer.2. 2. Copy the file to a secure location to which your Transformer modelers have access. If you are the Transformer modeler or business specialist who wants to download and use Transformer. click Export as. If you changed the global configuration on the source computer. Copy the exported cogstartup.1: Installation and Configuration Guide . If you want to export the current configuration to a different folder. Ensure that the folder is protected from unauthorized or inappropriate access. To export the configuration. the source computer must have the same IBM Cognos BI components as the Transformer modeler computers “Communication between Transformer and Business Intelligence components” on page 203. The instructions in this topic are for the installer or administrator. If some modelers will be installing on Windows Vista. Exporting the Transformer configuration: Use IBM Cognos Configuration to export the configuration from one Transformer computer for use with all other Transformer computers. We suggest creating separate folders on the Web or LAN location for Windows and Windows Vista. 7. cogtr.ini files on the Transformer computer. you must copy these files to the Web or LAN location so that Transformer modelers can download them to their computer. 210 IBM Cognos Business Intelligence Version 10. in the Look in box. or cs7g. You can export the configuration from one Transformer computer for use with all other Transformer computers. 4. The default location of the coglocale.xml. you must create an export file from a Windows Vista computer.exe file. 4. type a name for the configuration file. from the File menu. 3.

xml.html The cogtr_a. follow the steps to install Transformer.ini file. copy it from the c10_location/CS7Gateways/bin directory to the same Web or LAN location as the Transformer installation file. In the Finish page of the wizard. Configuring Transformer: As a business specialist or Transformer modeler. The man page for IBM Cognos Transformer is accessible in UNIX by typing cogtr man from the c10_location/bin directory. To support the use of IBM Cognos BI data sources (including packages and reports) in Transformer. Chapter 8. you must now deploy Transformer so that you can build PowerCubes and publish them to selected users or groups. If you updated the cs7g. 2. Follow the directions in the installation wizard and copy the required files to your computer. Procedure 1. select View the Release Notes and then click Finish. To configure Transformer so that it can communicate with the IBM Cognos BI dispatcher. From the Web or LAN location that the administrator provided. follow the steps to configure Transformer. The contents are expanded to the Documents and Settings\username\Local settings\Temp directory and then the Transformer installation wizard opens. 2. 3. use the following steps to install Transformer from the Web or LAN location that the administrator provided. If you have not completed the installation. run the C8transformerinstall.html document provides the syntax for UNIX command line options that are supported by IBM Cognos Transformer. Deploying IBM Cognos Transformer for Modelers If you are the business specialist or Transformer modeler. copy it from the c10_location/configuration directory to the same Web or LAN location as the Transformer installation file.Procedure 1.exe file. Go to the same Web or LAN location as the Transformer installation file. 4. ensure that the database client is installed on the Transformer computer. Tip: The Series 7 IQD Bridge component is not supported on Linux and HP-UX Itanium. Create a MANPATH environment variable and configure it with the following value: /c10_location/webcontent/documentation/en/cogtr_a. Installing Transformer: As a business specialist or Transformer modeler. Install and configure optional components 211 . Procedure 1. use the following steps to configure Transformer. If you updated the cogtr.

After Transformer is installed and running successfully. In the location where the Gateway component is installed.xml. If an . type . mount the disk using Rock Ridge file extensions. 7. the installation wizard starts automatically from the product disk.2.1: Installation and Configuration Guide . and starts the IBM Cognos services. Installing translated product documentation The product installation includes a limited set of translated documentation for some languages. To test IBM Cognos Transformer. v your software environment is supported Procedure 1. 6. generates digital certificates. On UNIX or Linux operating systems./issetup Note: When you use the issetup command with XWindows. copy them to the Transformer_location\configuration directory. ensure that: v IBM Cognos BI is installed and configured correctly v adequate disk space is available to install supplementary language documentation You need at least 220 MB of disk space. you must install it from IBM Cognos BI Supplementary Language Documentation. 212 IBM Cognos Business Intelligence Version 10./cogconfig. 5.2.bat -s IBM Cognos Configuration applies the configuration settings specified in the local copy of cogstartup. copy it to the Transformer_location\CS7Gateways\bin directory. 4. click Programs > IBM Cognos 10 > Transformer. If you see the Transformer window. 3. delete the installation files that were extracted from the installation file. On Windows. insert the IBM Supplementary Language Documentation disk or go to the directory where the installation files were downloaded and extracted. Go to the Transformer_location\bin directory. 2. where Transformer_location is the directory where you installed Transformer. if no Welcome page appears. To access a complete set of translated documentation. If any .xml files are present. from the Start menu. Japanese characters may be corrupted. The default location is C:\Program Files\Cognos\c10. Type the configuration command: . such as installation guides and release notes.exe file. v On UNIX or Linux. your installation is working. encrypts credentials. double-click the issetup. Before you begin Before installing the Supplementary Language Documentation. go to the operating system directory and do the following: v On Windows. To manually start the installation wizard.ini file is present.

Start the installation wizard by typing the following command: v On Windows. you must install additional fonts from the IBM Cognos BI Supplementary Language Documentation disk. Japanese characters may be corrupted. for example in file paths.3. On UNIX or Linux operating systems. Install and configure optional components 213 . ensure that following conditions are met: v IBM Cognos is installed and configured correctly. Some Web servers do not support non-ASCII characters in directory names. Procedure 1. ensure that the new location is added to the Physical fonts location property value. The supplementary languages documentation components is selected by default. Go to the directory on the disk that is appropriate for your operating system. . Install in a directory that contains only ASCII characters in the path name. Follow the instructions in the installation wizard to copy the required files to the same location where you installed gateway components for IBM Cognos BI. 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. 4. 2. issetup v On UNIX or Linux. Install in a directory that contains only ASCII characters in the path name. However. clear IBM Cognos Business Intelligence Supplementary Languages Documentation. When you are prompted to select components. In the location where Application Tier Components are installed. This font location is defined in the Physical fonts location property value in IBM Cognos Configuration under Environment. The Unicode code point “U+005C” is officially assigned to the backslash. Follow the instructions in the installation wizard to copy the required files to the same location where you installed Application Tier Components. 3. v There is adequate disk space available to install additional fonts./issetup Note: When you use the issetup command with XWindows. Some Web servers do not support non-ASCII characters in directory names. Choose the option you want in the Finish page of the installation wizard. These fonts are copied to the c10_location/bin/fonts directory. Before you begin Before installing the additional fonts. expand Additional Language Fonts. mount the disk using Rock Ridge file extensions. and then select the font. You need at least 220 MB of disk space. 4. v Your software environment is supported. you can install the “Andale WT J” and “Andale WT K” fonts. Installing additional language fonts To add support for the Japanese Yen or Korean Won character. in Japan and Korea. Chapter 8. insert the IBM Cognos BI Supplementary Language Documentation disk. If you move the fonts to another location. To accommodate this.

arial. helvetica. If you prefer to use other fonts on your server. Results After you install the additional fonts.pg .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. Procedure 1.pp { font-family: Gulim. Choose the option you want in the Finish page of the installation wizard.pp { font-family: ’MS UI Gothic’. Enable one of the following sections and modify it as shown in the following example: /* For Japanese: */ .2. 5. sans-serif.” Configure support for Japanese Yen and Korean Won characters For Japanese and Korean currency characters to display correctly. . 214 IBM Cognos Business Intelligence Version 10. Save the GlobalReportStyles. For PDF output and charts. arial. Open the GlobalReportStyles. you must define the additional fonts in the global style sheet. ’Andale WT K’ .css style sheet is located in the c10_location\bin directory. 3. you must install them from the IBM Cognos BI Supplementary Language Documentation disk. Restart the IBM Cognos BI server. Tahoma.1: Installation and Configuration Guide . Tahoma. You must repeat this procedure following an upgrade. 4. The GlobalReportStyles. helvetica. /* For Korean: */ . Before you begin Before you configure these fonts. this process occurs on the server where all fonts on the server that generates the report can be used. see “Configure support for Japanese Yen and Korean Won characters. } ’Andale WT J’ .pg. you can insert them into the list. geneva. Results Any changes that you make to the style sheet are overwritten if you upgrade IBM Cognos BI.css style sheet in a text editor. geneva. you must configure support for them. sans-serif. } The PDF generator uses the first available font on the server and includes all the characters in the string to be displayed. 2. For more information.css file.

For more information about gateway mappings and report size limits. except for IBM Cognos BI Metrics Manager. You can give users the installation disk that is included with IBM Cognos BI PowerPlay or you can copy the files from the disk to a central location on the LAN or a Web site. you can make the client files available for users to install or you can install the client on the user computers.exe file v the CognosOfficeSetup. Copy IBM Cognos BI for Microsoft Office Client Files to a Central LAN Location Before users can deploy IBM Cognos BI for Microsoft Office to their computer. depending on your environment. Enable secure sockets layer support. you must define a password for the Chapter 8. if required. Deploy IBM Cognos BI for Microsoft Office to client environments. Enable anonymous access.IBM Cognos BI for Microsoft Office IBM Cognos BI for Microsoft Office is available for deployment with all IBM Cognos BI products. if required. Enable SSL Support for the HTTPS Interface to PowerPlay If your environment includes IBM Cognos Series 7 PowerPlay Enterprise Server and you are using the HTTPS interface to access PowerPlay. Procedure From the IBM Cognos BI for Microsoft Office disk or a directory where the installation files were downloaded and extracted. You can also configure the size of report that can be imported from IBM Cognos BI to IBM Cognos BI for Microsoft Office. copy the following components to the LAN location: v the KB908002 folder v the setup. you must enable Secure Sockets Layer (SSL) support. Use the following checklist to configure IBM Cognos BI for Microsoft Office: __ v __ v __ v __ v Copy IBM Cognos BI for Microsoft Office files to the LAN for deployment. they need access to the installation files. if required. see the Administration and Security Guide. IBM Cognos BI for Microsoft Office is available as a 32-bit installation only. Install and configure optional components 215 .msi file Results Users can then run the setup. you can configure gateway mappings so that IBM Cognos BI for Microsoft Office users can access PowerPlay reports that reside on a PowerPlay server. It must be installed on a 32-bit Windows computer. To enable SSL support for the PowerPlay gateway and the IBM Cognos BI dispatcher.exe file from the LAN location to deploy IBM Cognos BI for Microsoft Office. To configure and deploy IBM Cognos BI for Microsoft Office. To deploy IBM Cognos BI for Microsoft Office with PowerPlay.

IBM Cognos for Microsoft Office Client is available as a 32-bit installation only. 2. v Install the CA certificate for secure sockets layer support.NET Framework. 216 IBM Cognos Business Intelligence Version 10. Microsoft Office Word.NET Framework and the required updates are downloaded and installed by the setup file when you install IBM Cognos for Microsoft Office. Microsoft . From the File menu. see the IBM Cognos for Microsoft Office Installation Guide. anonymous access must be enabled for portal users to access IBM Cognos BI for Microsoft Office documents that are based on PowerPlay reports. and Microsoft Office PowerPoint.ibm. start IBM Cognos Configuration.wss?uid=swg27037784). a second PowerPlay gateway can be used to provide anonymous access for IBM Cognos BI for Microsoft Office. 4. If necessary. Enable Anonymous Access for PowerPlay When using single signon with Microsoft Internet Information Services (IIS).1: Installation and Configuration Guide .com/support/ docview. Use the following checklist to guide you through the deployment process: v Install . For more information. if required. On each computer where Content Manager is installed. click Save. Deploying IBM Cognos for Microsoft Office to Client Computers IBM Cognos for Microsoft Office uses Microsoft . click Cognos. see “Configuring the SSL protocol for IBM Cognos components” on page 257. Set Macro Security Level for Microsoft Office XP For Microsoft Office XP applications to run IBM Cognos for Microsoft Office. You must set this for Microsoft Office Excel. if required. For more information. see the IBM Software Compatibility reports (www. After IBM Cognos BI is installed and configured.2. you can install IBM Cognos for Microsoft Office on client workstations. Deploying IBM Cognos for Microsoft Office Client IBM Cognos for Microsoft Office is available for installation with IBM Cognos BI components. The setup file must be run on all user computers. In the Properties window. under Security > Authentication.IBM Cognos BI key store and then create and store the Web server Certificate Authority (CA) certificate in the IBM Cognos BI key store. In the Explorer window. It must be installed on a 32-bit Windows computer. For a list of supported versions of Microsoft . click the box next to the Allow anonymous access property and then click True. For more information about installing IBM Cognos for Microsoft Office. Procedure 1.NET Framework and IBM Cognos for Microsoft Office. 3.NET Framework to allow users to interact with server-based components. you must set your macro security level to an appropriate level. see the topic about specifying gateway mappings in the Administration and Security Guide. v Set the macro security level for Microsoft office XP.

Procedure 1. 3. Open your Microsoft Office XP application. 5. From the Tools menu. Click Finish. Retrieve the CA certificate from your administrator. Click Browse. Click Place all certificates in the following store. click Install Certificate. The file has a . 4. and then click Security.cer file. Double-click the . click Trusted Root Certification Authorities.cer extension. and then click Next. 2. Install and configure optional components 217 . and then click Next. click Macros. 2. Choose whether to change the security level or the trusted publishers. and then click OK v On the Trusted Publishers tab. click Medium or Low. 3. v On the Security Level tab. The CA certificate is required for secure sockets layer (SSL) support. Chapter 8. and then click OK. select Trust all installed add-ins or templates. you must install a certificate issued by a certificate authority (CA). Procedure 1. Install the CA Certificate for the HTTPS Interface to Series 7 PowerPlay If your environment includes IBM Cognos Series 7 PowerPlay Enterprise Server and you are using the HTTPS (https://) interface to access Series 7 PowerPlay.

1: Installation and Configuration Guide .218 IBM Cognos Business Intelligence Version 10.2.

However. you can change these default settings if existing conditions make the default choices inappropriate. see the Administration and Security Guide. You can change the Java version in situations where you want to use IBMCognos BI components with an application server that requires a specific JRE version or you already use a JRE version with other applications. if the console attached to the UNIX or Linux computer on which you are installing IBM Cognos components does not support a Java-based graphical user interface you must manually edit the cogstartup. you can change the configuration for your environment. © Copyright IBM Corp. you can configure features for IBM Cognos Application Firewall or specify the amount of resources that IBM Cognos components use. For all Microsoft Windows operating system and most UNIX and Linux operating system installations. 2005. For example. For more information about tuning server performance. and then run IBM Cognos Configuration in silent mode. such as using an authentication provider and then enabling single signon for the database connection and the users.xml file in the c10_location/configuration directory. use IBM Cognos Configuration to configure your settings. Back up existing IBMCognos data and encryption keys. Update the Java environment. 2013 219 . If you use a load-balancing scheme in your environment. if required. 2. Changing the version of Java used by IBM Cognos BI components IBM Cognos Business Intelligence components require a Java Runtime Environment (JRE) to operate. or to better suit your environment. Configuration options After you install and configure IBM Cognos components. Use the following steps to change the Java version: 1. you can change settings to improve performance. However. Use these optional configuration tasks to customize your configuration so that IBM Cognos components easily integrate into your existing environment. You can configure IBM Cognos components to use other resources. Initially. you can deliver IBM Cognos content using another portal by configuring Portal Services. For example. default property settings are used to configure the components.Chapter 9. Also. you can balance requests among dispatchers by changing their processing capacity or by setting the minimum and maximum number of processes and connections.

New cryptographic keys must be created using the same JVM that the application server uses. v cryptographic keys by saving them to an alternate location. from the File menu. You must also back up existing IBM Cognos information if you must change the JVM you are using. When naming the file. you may be required to update your version of Java or set a JAVA_HOME environment variable. 2. Before configuring IBM Cognos BI components to run on the new application server or JVM.xml. it is important to back up the previous keys. Back up existing IBM Cognos information You must back up existing IBM Cognos information if IBM Cognos Business Intelligence components are running on an application server (including Tomcat) and you are changing to an application server that ships with its own JVM. Any encrypted data is decrypted during the export. In IBM Cognos Configuration. use a name such as decrypted. Depending on your security policy requirements. Note: You must back up existing IBM Cognos information within the working environment prior to upgrade. To ensure the security and integrity of your IBM Cognos data. 3. encryptkeypair or signkeypair. configuration information. If data exists in the content store. you may also have to install the unrestricted Java Cryptography Extension (JCE) policy file. stop the IBM Cognos service and close IBM Cognos Configuration. Export the data to a directory that is protected from unauthorized or inappropriate access because passwords are stored in plain text. shut down IBM Cognos BI in your environment. For more information. look in the c10_location/ configuration directory.Related concepts: “Java requirements” on page 43 To support the cryptographic services in IBM Cognos Business Intelligence.2. start the IBM Cognos service and export the entire content store using the Deployment tool. you must back up v content store data by creating a deployment export. click Export As and save the configuration information in a decrypted format. You are prompted to acknowledge that the export is an unsecure operation. v If you use an application server other than Tomcat. and cryptographic keys to a directory that is protected from unauthorized or inappropriate access. Procedure 1. Because these keys can be created only if the previous keys are deleted. v configuration information by exporting it. 220 IBM Cognos Business Intelligence Version 10. Tip: To check if any cryptographic keys exist. back up the content store. Stop the IBM Cognos service: v If you use Tomcat. Cryptographic keys exist if this directory includes the following subdirectories: csk. see the topic about creating an export deployment specification in the IBM Cognos Business Intelligence Administration and Security Guide.1: Installation and Configuration Guide .

In the c10_location/configuration directory. The files are v c10_location/configuration/cogstartup. and signkeypair.xml file with the file that contains the data exported from IBM Cognos Configuration (for example. For example. If you require a wider range of cryptographic algorithms and cipher suites than are shown in IBM Cognos Configuration. The information in this file will be automatically re-encrypted using new cryptographic keys when you save the configuration in IBM Cognos Configuration.com/support/docview.wss?uid=swg27037784).xml). if you do not have a JAVA_HOME variable. To verify that your JRE is supported.prefs files and the three directories: csk. Chapter 9. Change your Java version You can change the Java version in situations where you want to use IBM Cognos BI components with an application server that requires a specific JRE version or you already use a JRE version with other applications.xml v c10_location/configuration/caSerial v c10_location/configuration/cogconfig. Back up any existing cryptographic keys by saving the appropriate files and directories to an alternate location that is secure. Delete the caSerial and cogconfig. Unrestricted JCE Policy File JREs include a restricted policy file that limits you to certain cryptographic algorithms and cipher suites. the file must use the name cogstartup.prefs v c10_location/configuration/coglocale. v You are installing on Microsoft Windows operating systems and you want to use your own Java or a Java bundled with other software. On Microsoft Windows operating systems.4.xml. Configuration options 221 . you can download and install the unrestricted JCE policy file. Click the link for your version of Cognos BI and locate the Java Run Time Libraries information. encryptkeypair. the JRE files that are provided with the installation are used. decrypted. Ensure that the JRE version is supported by IBM Cognos products.ibm. You change Java versions by setting the JAVA_HOME environment variable.xml The directories are v c10_location/configuration/csk v c10_location/configuration/encryptkeypair v c10_location/configuration/signkeypair 5. 6. JAVA_HOME Set a JAVA_HOME environment variable if: v You are installing on a UNIX or Linux operating systems. go to the IBM Software Compatibility reports (www. Replace the c10_location/configuration/cogstartup. if you are installing IBM Cognos BI on WebSphere Application Server.

The documentation is available in the c10_location/derby10. Changing Default Configuration Settings When you install IBM Cognos components.ibm.1. Change this user ID and password. or test the installation. you can configure Portal Services. ensure that you configured all computers where you installed Content Manager before you change default configuration settings on other IBM Cognos computers.2.com/webapp/iwm/web/ preLogin. Administration tasks for Cognos Content Database are performed using a utility named ij.1: Installation and Configuration Guide . For Metric Studio. For example. If you have any reason not to use these default values. the unrestricted JCE policy file is available on the IBM website (https://www14.do?source=jcesdk). If you change the value of a property. For distributed installations.2. 222 IBM Cognos Business Intelligence Version 10. such as a port is being used by another process. see the Apache Derby documentation. you must save the configuration and then restart the IBM Cognos service to apply the new settings to your computer. For information about this utility. Change this user ID and password. you can v change the default user and password for Cognos Content Database v change a URI v configure cryptographic settings v configure IBM Cognos components to use IBM Cognos Application Firewall v v v v v configure temporary file properties configure the gateway to use a namespace enable and disable services configure fonts change the default font for reports v save report output to a file system v change the location of map charts for Report Studio v change the notification database After you change the default behavior of IBM Cognos components to better suit your IBM Cognos environment. Changing the default user password If you install Cognos Content Database. the default database that is created is given a user ID and password. you can install and configure Framework Manager.For Java that is provided by IBM. configure an authentication provider. the installation uses default configuration settings.software. the default database that is created is given a user ID and password. use IBM Cognos Configuration to change the value. For IBM Cognos BI.1/docs directory where you installed Cognos Content Database. you can install and configure Metric Designer. Change Default User and Password for Cognos Content Database If you install Cognos Content Database.

Configuration options 223 . 6. is still part of the list of users with full access.password=cognos'. the default database that is created is given a user ID and password. 2.cognos'. 3. 5. Close the ij utility by typing the following command: disconnect. go to the c10_location/derby10.bat or ij. If you changed the port number from the default 1527. The new password must be used for the next connection to the database. Connect to the default database by typing the following ij utility command: connect 'jdbc:derby://localhost:1527/cm.SYSCS_SET_DATABASE_PROPERTY('derby. Removing a user If you have user accounts that you are no longer using for Cognos Content Database. The database name is case sensitive. 2.1.'cognos. Create a new user by typing the following ij utility command: CALL SYSCS_UTIL. Close the ij utility by typing the following command: disconnect. 3. If you changed the port number from the default 1527. 4.NewUser'.SYSCS_SET_DATABASE_PROPERTY ('derby. NewUser').1/bin directory. Start the ij utility using the ij.Procedure 1. The database name is case sensitive.database. The ij utility is a command line utility for creating and managing Cognos Content Database. The default database is named cm. go to the c10_location/derby10.ksh script file.fullAccessUsers'.SYSCS_SET_DATABASE_PROPERTY('derby. you can remove them. The default database is named cm. Change the default password for the cognos user by typing the following ij utility command: CALL SYSCS_UTIL. The property that you are changing.2. Start the ij utility using the ij. cognos.1/bin directory. use the correct port number for your Cognos Content Database. the list of users. In this step. 5. 'NewPassword'). On the computer where you installed Cognos Content Database. you are including the new user in the list of users with full access. 'NewUserPassword').password=cognos'. The default user. is a comma-delimited field.user.user=cognos.1. Creating a new user and password If you install Cognos Content Database. Procedure 1.2.user=cognos.bat or ij. Connect to the default database by typing the following ij utility command: connect 'jdbc:derby://localhost:1527/cm. use the correct port number for your Cognos Content Database.ksh script file. 4. Change this user ID and password. You can remove the cognos user. Chapter 9. On the computer where you installed Cognos Content Database. Give the new user full access to the database by typing the following ij utility command: CALL SYSCS_UTIL.user.

SYSCS_SET_DATABASE_PROPERTY ('derby. 3.Procedure 1. Example: http or https 224 IBM Cognos Business Intelligence Version 10.2. or dispatcher URI protocol://host_name_or_IP:port/context_root/alias_path v 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 The elements are described in the following table: Table 51. On the computer where you installed Cognos Content Database. removes the default cognos user and keeps the new user that you just created. 4. the previous command.ksh script file. Close the ij utility by typing the following command: disconnect. 2.1: Installation and Configuration Guide . Port and URI Settings You can change certain elements in a URI depending on your environment.SYSCS_SET_DATABASE_PROPERTY('derby. For example. type the following ij utility command and omit the user password: CALL SYSCS_UTIL. Dispatcher URI for external applications.bat or ij.user=NewUser. You omit the user name from the list of users with full access.cognos'. which also removes the user from the database.fullAccessUsers'. 'NewUser'). 5.database. Start the ij utility using the ij.1. An IBM Cognos URI contains the following elements: v For a Content Manager URI. Connect to the default database by typing the following ij utility command: connect 'jdbc:derby://localhost:1527/cm.1/bin directory. v To remove a user from the database. This command removes the password for the default cognos user. ''). either Hyper Text Transfer Protocol or Hyper Text Transfer Protocol (Secure).user. password=NewUserPassword'. type the following ij utility command: CALL SYSCS_UTIL. go to the c10_location/derby10.2. Choose the kind of user that you want to remove: v To remove a user from the list of users with full access. IBM Cognos URI elements and descriptions Element protocol Description Specifies the protocol used to request and transmit information.

ensure that host names can be resolved to IP addresses by all servers in the environment. You can use an IP address. For example.cgi If you are using collaboration with IBM Connections. the virtual directory is ibmcognos/cgi-bin. then the default gateway application would be cognos. or a fully qualified domain name.cgi. The domain must be included in order for Chapter 9.Table 51. if your computer is named MyComputer and your domain is MyCompanyName. ensure that you include the full domain for all hostname entries in IBM Cognos Configuration.0. Configuration options 225 . Example: ibmcognos/ gateway application Specifies the name of the Cognos gateway application that is used. The default port for Tomcat is 9300. The default port for a Web server is 80. For example. a computer name. Example: p2pd alias path Used by the application server to route a request to the correct component within a Web application.cgi. Example: cognos.com. The alias path must not be modified or IBM Cognos components will not function properly. if you are accessing IBM Cognos components using a Common Gateway Interface (CGI).168.com. then for the host_name_or_IP value. in the default Gateway URI of http://localhost:80/ibmcognos/cgi-bin/cognos.MyCompanyName. In a distributed installation. For example. Example: 9300 or 80 context root Used by Tomcat or an application server to determine the context of the application so that the request can be routed to the correct Web application for processing. Example: servlet/dispatch virtual directory Used by the Web server to map a virtual directory or alias to a physical location. IBM Cognos URI elements and descriptions (continued) Element host name or IP Description Specifies the identity of the host on the network. use MyComputer. In a mixed environment of UNIX and Microsoft Windows operating system servers. you must change the localhost element of a URI. Example: localhost or 192.1 or [2001:0db8:0000:0000:0000:148:57ab]:80 port Specifies the port on which the host system listens for requests.

click the appropriate group or component: v To change an element for the dispatcher. ensure that you specify the new port number when you configure remote computers that use the dispatcher. 226 IBM Cognos Business Intelligence Version 10. IBM Cognos computers communicate with Content Manager to establish trust and obtain some cryptographic keys from Content Manager. click the Value box next to the URI property that you want to change. Configuring Cryptographic Settings IBM Cognos components require a cryptographic provider. In addition. the symmetric key should only be stored on computers where Content Manager has been installed. If you delete the default cryptographic provider. From the File menu. you must configure another provider to replace it. Because the change affects all the URIs that are based on the local dispatcher. Select the element and type the new information. Change a Port or URI Setting Use the following procedure to change URI properties in IBM Cognos Configuration. under Environment. you must delete the cryptographic keys on the other IBM Cognos computers. Also. 2. v If you change the dispatcher port in the dispatcher URI. 4. Content Manager. otherwise they will not run. You can configure the following cryptographic settings: v general cryptographic settings v settings for the default cryptographic provider v settings for a cryptographic provider in an Entrust security infrastructure Configure General Cryptographic Settings In a distributed installation. or Software Development Kit services on this system. You must then save the configuration on each computer so that they obtain the new cryptographic keys from Content Manager. For more information. Procedure 1. see “Allow access to IBM Connections from IBM Cognos BI” on page 326. change the value of the internal dispatcher URI property.IBM Connections to allow access. you must change the URIs of all local components. all IBM Cognos components in a distributed installation must be configured with the same cryptographic provider settings. in a distributed environment. click Save.2. click Environment. Tips: v To change the port used by the local dispatcher. click Logging. such as by changing application servers or reinstalling Content Manager. In the Properties window. 5. 3. Start IBM Cognos Configuration. If you change the cryptographic keys in Content Manager. v To change an element for the local log server. In the Explorer window.1: Installation and Configuration Guide .

Procedure 1. Results After you configure the cryptographic settings.You can configure the following general cryptographic settings: v common symmetric key store (CSK) properties The CSK is used by IBM Cognos to encrypt and decrypt data. Test the cryptographic provider on a gateway computer only. When Store symmetric key locally is False. under SSL Settings. 5. change Use mutual authentication to True. change the default values by clicking the Value box and then selecting the appropriate value: v On computers that do not contain Content Manager. In the Explorer window. v secure sockets layer (SSL) settings These include mutual authentication and confidentiality. under CSK settings. The Common symmetric key store location property is ignored. In the Explorer window. change Store symmetric key locally to False. In the Properties window. 4. for the Digest algorithm property. Chapter 9. v advanced algorithm settings These include signing and digest algorithms. v If you want to change the digest algorithm. Configure Settings for the Default Cryptographic Provider You can configure some cryptographic settings for the cryptographic provider. 2. Start IBM Cognos Configuration. v encryption key store properties The encryption key pair includes the private key used to encrypt data and the public key used to decrypt data. Do not change the Use confidentiality setting. under Security. From the File menu. the key is retrieved from Content Manager when required. 3. Configuration options 227 . if you do not want to store the CSKs locally. IBM Cognos components check the availability of the symmetric key. v If you want the computers at both ends of a transmission to prove their identity. passwords in your configuration and any data you create are encrypted. select another value. click Cryptography. The configurable settings include the following: v algorithms and ciphersuites v identity name settings v 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. v certificate authority settings These include properties for the provided certificate authority (CA) or a third-party CA. right-click Cryptography and click Test. click Save.

do?source=jcesdk).software.Procedure 1.ibm. 3. The value of a confidentiality algorithm determines how data is encrypted by IBM Cognos components. 228 IBM Cognos Business Intelligence Version 10. The availability of confidentiality algorithms can change if there are changes to your environment. go to the c10_location/bin64/jre/version/ lib/ext directory. Confidentiality algorithm or PDF Confidentiality algorithm. go to the c10_location/bin/jre/version/lib/ext. v To use another certificate authority. change Encryption key store location to the new location. v To change the location of the signing keys. 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. 5. Cryptography. v To adjust the cipher suites.1: Installation and Configuration Guide .to 56-bit range with cipher suites in the 128. under Security. under Supported ciphersuites. download and install the unrestricted Java Cryptography Extension (JCE) policy file. v To configure the confidentiality algorithm. click in the Value . 4. change the properties as needed.com/webapp/ iwm/web/preLogin. If you are using 64-bit components. this may affect the availability of confidentiality algorithms. To ensure that the available algorithms and cipher suites are shown in IBM Cognos Configuration. the unrestricted JCE policy file can be downloaded from Unrestricted JCE policy files (https://www14. change the Signing key store location property to the new location. under Certificate Authority settings. click Cognos. if your Java Runtime Environment (JRE) has changed or if you have installed other cryptographic software on the computer. 2. If you have made changes to a computer. you must also download and install the unrestricted Java Cryptograph Extension (JCE) policy file for your JRE to ensure that all available algorithms and cipher suites are shown in IBM Cognos Configuration. change Use third party CA to True. In the Properties window.jar to JRE_location/lib/ext. If you are using a JRE other than the one provided with IBM Cognos server.to 168-bit range. under Encryption key settings. 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. In the Explorer window.2. 6. under Signing key settings. column and then click the edit icon Remove the cipher suites that are not applicable and move the remaining cipher suites up or down in the list so that the cipher suites in the highest range are higher in the list. under the appropriate property. Copy bcprov-jdkversion. For Java that IBM provides. such as upgraded the JRE or installed software that has upgraded the JRE. Do not mix cipher suites in the 40. For example. If you are using a JRE other than one IBM provides. click in the Value column and then select the algorithm from the drop-down list. Start IBM Cognos Configuration. v To change the location of the encryption keys.

From the File menu. Ensure that the following files from IBM Cognos and Entrust exist in the location where the JRE is installed: v From the Entrust Authority Security Toolkit that you download from Entrust. For Java that IBM provides. 7. 7. Before you begin Ensure that the key store passwords match the one in your Entrust Profile (EPF).jar file. under the Security group. see “Configuring IBM Cognos components to use another certificate authority” on page 252.com/webapp/iwm/web/ preLogin. For more information. If you are using a JRE other than the one provided with IBM Cognos server. To prevent gateway errors. 5. 3.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. under the Security group and the Cryptography component. Configuration options 229 . copy the . configure IBM Cognos components to use the CA. In the Explorer window. 4. click Cryptography. download and install the unrestricted Java Cryptography Extension (JCE) policy file. Configure Cryptographic Provider Settings in an Entrust Security Infrastructure To configure encryption in an Entrust security infrastructure. to JRE_location/lib/ ext.jar. such as enttoolkit. under Advanced algorithm settings. If you are using 64-bit components. 6.epf file and read permission to the Entrust . In the Properties window.do?source=jcesdk). Copy bcprov-jdkversion. right-click the IBM Cognos resource. 2. click Save. and click Delete.software. Procedure 1. Start IBM Cognos Configuration.ual file.jar to JRE_location/lib/ext. 8. In the Explorer window. the unrestricted JCE policy file can be downloaded from Unrestricted JCE policy files (https://www14. To ensure that all available algorithms and cipher suites are shown in IBM Cognos Configuration. you replace the default cryptographic provider in IBM Cognos Configuration with a provider that you configure for Entrust and then you update security files in your IBM Cognos environment. go to the c10_location/bin/jre/version/lib/ext. change the Digest algorithm to the appropriate message digest or secure hash algorithm for your security policy. ensure that the Internet Guest Account has read and write permission to the Entrust . see “Configuring IBM Cognos components to use another certificate authority” on page 252. go to the c10_location/bin64/jre/ version/lib/ext directory. For more information. Results If you use another Certificate Authority (CA) server.ibm. Chapter 9.

Under the Security group. which must match the one in your Entrust Profile (EPF). Identity file password Confidentiality algorithm PDF Confidentiality algorithm Supported ciphersuites Signing Key Store Location Encryption Key Store Location Important: Record your passwords in a secure location. 230 IBM Cognos Business Intelligence Version 10. IBM Cognos Application Firewall protects IBM Cognos Web products from malicious data. enter the appropriate values. From the File menu. click Save. type a name for the encryption service you are creating. In the Type field. In the Resource Properties window. The level of encryption that is required to comply with your security policy. 11. 13. The distinguished name associated with the profile of the Entrust identity. IBM Cognos Application Firewall may modify these HTTP and XML requests. IBM Cognos Application Firewall IBM Cognos Application Firewall analyzes and validates HTTP and XML requests before they are processed by IBM Cognos servers.epf).9. and then click OK.ini). and click New resource > Provider. The most common forms of malicious data are buffer overflows and cross-site scripting (XSS) attacks. 14. 15. The encryption algorithm to use when encrypting PDF data. The Entrust Profile password. 12. The cipher suites that are supported in your security environment. 10. Remove the ones that are not applicable and rearrange the remaining cipher suites from highest to lowest. Resource properties appear in the properties window. right-click Cryptography. Cryptography property values and descriptions Property INI file location Identity file distinguished name (DN) Identity file location Use Entrust Server Login Description The location of the Entrust initialization file (. Click the branch you created. The location of the key store that contains encryption key pairs. Update to Entrust Java Toolkit 7. The location of the key store that contains the signing key pairs. either through script injection in valid pages or redirection to another Web site. The parameter that controls whether users must enter a password to log on to the Entrust PKI. A branch with the name you assigned appears under Cryptography. The location of the Entrust identity profile file (. In the Name field. and click Entrust. This ensures that the most secure cipher suite is used first.2 SP2 Patch 170072.2.1: Installation and Configuration Guide . click the arrow. as listed in the following table: Table 52.

By default. where protocol is http or https and host is validated against the valid domain list v URLs relative to the Web installation directory in the format /Web_installation_root/. Important: The IBM Cognos Application Firewall is an essential component of IBM Cognos security. If you are using the collaboration features with IBM Connections.back( ) parent.close( ) JavaScript:history. 2. including the following (all case insensitive) about:blank JavaScript:window. All Cognos Application Firewall settings must be the same for all computers where IBM Cognos Application Tier Components are installed within a distributed environment. In the Explorer window. and port number on which IBM Connections is running to the Valid domains and hosts property for the Cognos Application Firewall.* where Web_installation_root is the gateway Web directory.gif v specific allowed URLs. For example. you can change settings for other XSS tool support. you must add the host name. 3. and you can add host and domain names to the IBM Cognos list of valid names. Configuration options 231 .close( ) JavaScript:parent.log file. set the appropriate values.You can track firewall activity by checking the log file. By default. Procedure 1. based on the ibmcognos alias that you configured on your Web server. helping to provide protection against penetration Chapter 9. The following types of URLs are accepted by Cognos Application Firewall validation: v fully qualified (absolute) URLs in the format protocol://host:port/path. domain. which contains rejected requests. For example. In each location where IBM Cognos BI Application Tier Components are installed. log messages are stored in the c10_location/logs/ cogserver. start IBM Cognos Configuration. /ibmcognos/ps/portal/images/action_delete. In the Properties window. unexpected behavior and product errors may result. for the Enable CAF validation property. click IBM Cognos Application Firewall. IBM Cognos Application Firewall is enabled.cancelErrorPage( ) doCancel( ) Configure IBM Cognos Components to Use IBM Cognos Application Firewall Using IBM Cognos Configuration. under Security. if Cognos Application Firewall is disabled on some computers and enabled on others.

add the hostnames of the IBM Cognos Series 7 gateway servers to the list. you would add myserver. Encrypt Temporary File Properties Temporary files are used in IBM Cognos BI to store recently viewed reports and to store data used by the services during processing. in the Properties window.2. click Add. Disabling the IBM Cognos Application Firewall will remove this protection. For example. Restart the services. click the value and then click the . use a wildcard character at the begining of the domain name. 232 IBM Cognos Business Intelligence Version 10. Under normal circumstances.Valid domains or hosts dialog box. The default characters that are prohibited include >. 5. You must include the domains from all hyperlinks that are added in IBM Cognos Connection. <. domain. 4. Add host and domain names to the IBM Cognos list of valid names: v For the Valid domains and hosts property. edit icon v In the Value . see the topic about creating a URL in the IBM Cognos Business Intelligence Administration and Security Guide. *. IBM Cognos Application Firewall validates domain and host names to protect URLs that are created. you must add the host. For more information. To allow a domain and all its sub-domains.mycompany. v Click OK. IBM Cognos Application Firewall considers domain names derived from the environment configuration properties to be safe domain names. and your domain is mycompany.com:9080. do not disable the IBM Cognos Application Firewall.com. v In the blank row of the table. change the value to True. You can change the location of the temporary files and you can choose to encrypt their content. Tip: If you are using drill-through from IBM Cognos Series 7 to reports in IBM Cognos BI. where 9080 is the IBM WebSphere port number on which IBM Connections is running. v Repeat the previous two bulleted steps for each name to be added. and '. if you installed IBM Connections on a computer named myserver. For example. Adding names to the list of valid names and hosts is useful when you need to redirect requests to non-IBM Cognos computers using the Back or Cancel functions or when using drill-through to different IBM Cognos product installations. By default.1: Installation and Configuration Guide . and port number for the IBM WebSphere profile where you have installed IBM Connections.mycompany. If you are using another XSS tool that checks for specific characters in GET request parameters.vulnerabilities. 6. By default. 7. click and then type the host or domain name. IBM Cognos components store temporary files in the c10_location\temp directory and the files are not encrypted. Save the configuration.com If you are using the collaboration features with IBM Connections. for the Is third party XSS checking enabled property.

specify the new location.For optimum security. set the Encrypt temporary files property to True. 3. 4. the default values are true. 4. type the Namespace ID of the namespace that you want to use. you can configure the gateway to connect to one namespace. 2. 2. start IBM Cognos Configuration. In the Properties window. or if anonymous access is enabled and IBM Cognos components use one namespace. On the computer where the gateway is located. if you have two Web servers. you can configure each Web server to use a different namespace. click Environment. In the Explorer window. Chapter 9. deny all access to the temp directory. 3. for the Temporary files location property. click Environment. Enable and Disable Services In a distributed installation. click Save. Note: The default values for dispatcher service and presentation service are false on computers that only have Content Manager installed. Requests are only sent to dispatchers where a given service is enabled. Procedure 1. read-write privileges Configure the Gateway to Use a Namespace If IBM Cognos components use multiple namespaces. From the File menu. For example. you can send certain types of requests to specific computers by enabling or disabling the installed services. Configuration options 233 . full control privileges v on UNIX or Linux operating systems. in the Value box next to the Gateway namespace property. Procedure 1. If you require the content of temporary files to be encrypted. To dedicate a computer in a distributed installation to processing Metric Studio application requests. except for the service account used to start the IBM Cognos services. For example: v on Microsoft Windows operating systems. Ensure that the user account under which IBM Cognos BI components run have the appropriate privileges to the temporary files location. Start IBM Cognos Configuration. Restart your Web server. Read and write permissions are required for the service account. In the Explorer window. you can disable the presentation service on an Application Tier Components computer. 5. disable the Data Integration Service on the computer. For example. to dedicate a computer to running and distributing reports. Users logged onto the Web server where the gateway is located are not prompted to choose an authentication source. In the Properties window. you can disable appropriate services on each computer to get the distributed configuration you require. 5. If you installed all components on several computers. On all other types of installations.

3.Disabling a service prevents the service from loading into memory. you must install a font that supports GB18030-2000. the dispatcher-related services are disabled.2. Click the appropriate state for the services: v To disable the service. fonts must be available where the report or chart is rendered. under Environment. If you disable the dispatcher service. Start IBM Cognos Configuration. Map the new font to the physical font name. On operating systems other than Windows. support is provided for the GB18030-2000 character set in the SimSun-18030 font that is provided by Microsoft. In the Properties window.1: Installation and Configuration Guide . v To enable the service. __ v Add the font to the list of supported fonts. If a requested font is not available. all services are enabled. IBM Cognos components substitute a different font. The service does not run until you enable it. 4. click False. 5. if required. When disabled. click Save. which is used in the encoding of Simplified Chinese locales. the fonts must be installed on the IBM Cognos server. click True. In the Explorer window. IBM Cognos components also use fonts to render charts used in PDF and HTML reports. Configuring fonts IBM Cognos components use fonts to render PDF reports on the IBM Cognos server. To show output correctly. By default. 2. click IBM Cognos services. click the Value next to the service that you want to disable or enable. If a requested font is not available. From the File menu. services do not start and therefore do not consume resources. Procedure 1. 234 IBM Cognos Business Intelligence Version 10. Enabling and disabling services Use the following procedure to disable selected services on components in a distributed installation. For charts and PDF reports. Considerations to support Simplified Chinese IBM Cognos BI products support the GB18030-2000 character set. the browser substitutes a different font. If you install on Microsoft Windows. Only dispatcher services that are enabled can process requests. __ v __ v Specify the file location of the new font. Use the following checklist if you want to use a new font in your reports. Because HTML reports are rendered on a browser. the required fonts must be installed on the computer of each IBM Cognos user who views the report.

On each Content Manager computer. 6. Chapter 9. Specify the Location of Available Fonts You must specify the installation location of all fonts. From the File menu. Configuration options 235 . In the Properties window. for the Physical fonts locations property. which are available on all IBM Cognos server computers. must be installed on all IBM Cognos computers in your environment. You map fonts on each computer where the Application Tier Components are installed. separate each path by a semicolon (. 2. 4. start IBM Cognos Configuration.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. they also use the fonts installed in the Windows font directory. you must map the global font to an installed. click Save. click the box next to the font name and then click Remove. Map Supported Fonts to Installed Fonts You can substitute global fonts. 5. Results If a global font is not installed on all IBM Cognos computers. From the Actions menu. Click the Fonts tab. If you are using an application server other than Tomcat. Procedure 1. including fonts that you add to the list of supported fonts. click Edit Global Configuration. By default. click Environment. specify the location of the fonts. physical font. If there are multiple font paths. which are not installed on the computer. Procedure 1. Click Add. If IBM Cognos components are installed on a Microsoft Windows operating system computer. On each Application Tier Components computer. By default. the list of fonts consists of fonts installed in the c10_location\bin\fonts directory of the IBM Cognos computer. start IBM Cognos Configuration. Tip: To remove a font from the list of supported fonts. 2. including new fonts that you add. All global fonts. click Save. for physical fonts. You specify the font location on all computers where Application Tier Components are installed.). In the Explorer window. IBM Cognos components use a set of global fonts. 3. From the File menu. For example: c10_location/bin/fonts. 3. type the fully qualified path to the font location. In the Supported Font Name box. 4. You can also remove fonts. type the font name and then click OK.

Procedure 1.For example. you must specify the installation location of the fonts. The font then becomes the default for all computers in your installation. You change the default font on the computer where Content Manager is installed. and then click the edit icon The Value . Click Add. For more information. set the default font to SimSun-GB18030. if required. property. No mapping is required if you add a font to the supported font list that is installed on IBM Cognos computers. On each Application Tier Components computer. click Search Now and then click a font name from the results. select the check box next to the font and click Remove. click the edit icon . you add a font to the list of supported fonts that is not installed on the IBM Cognos computer. Click OK. 6. Click the Physical Font Name box. In the Physical Font Name dialog box. you must specify the location of the font. In the Properties window. type it. However. see the Query Studio User Guide or the Report Studio User Guide. In the Global Font Name box. click Save. 2. 4.Physical fonts map dialog box appears. Repeat steps 4 to 7 for each global font that requires mapping.1: Installation and Configuration Guide . 7. Otherwise. Tip: To remove a font. type the name of the font you added to the supported font list.2. 3. You change the font used for PDF reports using IBM Cognos Configuration. click Environment. If you know the physical font name. Results Now. You can specify which font to use as a substitute. start IBM Cognos Configuration. Change the default font for PDF reports You can change the default font that IBM Cognos BI components use for PDF reports. 10. 9. From the File menu. such as Helvetica-PDF. 236 IBM Cognos Business Intelligence Version 10. If you want to print reports faster by using the built-in PDF fonts. 8. You can also select one of the built-in PDF fonts for a text object in Report Studio or Query Studio. Ensure that the default font is installed on all computers in your IBM Cognos installation. you can map a global font such as Arial to one of the built-in PDF fonts. click the Value box next to the Physical fonts map . 5. In the Explorer window. To ensure that GB18030 characters are displayed correctly in PDF reports. You see this default font when you open a report. using the following steps.

3. specify the new path in the font paths box. The license information is stored in the font itself and is read by IBM Cognos BI. Click the General tab. If you are not using the default fonts directory or if you want to add a path to an additional directory. Click OK. If you are confident that the fonts used in reports are available on users' computers. Fonts must be either embedded in the report or installed on the user's computer. click Edit Global Configuration. 6. In the Explorer window. This substitution may cause changes in the presentation of the report or some characters may not be displayed. 2. and then . Tip: Click Search Now to get a list of the available fonts in the specified path or paths. under Font Settings. 7. In the Value box. IBM Cognos BI embeds required fonts in reports by default. start IBM Cognos Configuration. scroll to the font name. If a font is not available in either of these locations. On the Content Manager computer. From the Actions menu. 5. IBM Cognos BI embeds only the characters (also called glyphs) used in the report rather than all characters in the font set. Configuration options 237 . using an embedded fonts list in IBM Cognos Configuration. 2. all the fonts used in that report must be available. click the value for Fonts to embed (Batch report service) or Fonts to embed (Report service). From the File menu.Procedure On each Content Manager computer. Procedure 1. 4. click the edit icon 4. 3. click Save. Adobe Reader tries to substitute an appropriate font. you can limit or eliminate embedded fonts to reduce the size of PDF reports. On all Application Tier Components computers. In the Properties window. To ensure that PDF reports appear correctly in Adobe Reader. scroll to the font name and click the Always check box. 6. To minimize the file size. 1. IBM Cognos BI does not embed the font with any reports. type the font you want to use as the default for reports. Configure Embedded Fonts for PDF Reports When a PDF report opens in Adobe Reader. For a font that will always be available on users' computers. in the Fonts to Embed in PDF Reports dialog box. For a font that may not always be available on the users' computers. Chapter 9. ensure that the installation location of the default font is specified in the Physical fonts locations property (under Environment in the Explorer window) or that the font is in the Windows font directory. IBM Cognos BI embeds fonts only if they are licensed for embedding. Adobe Reader picks up the font from the user's computer when the report is opened. When limiting fonts. and click the Never check box. click Environment. you specify whether a font is always or never embedded. for Default font. start IBM Cognos Configuration. 5.

This is how most report output files are saved. In the Global Configuration window. For example. On the Content Manager computer. see the topic about setting a file location for report output saved outside of IBM Cognos BI. such as \\servername\directory. Saved Report Output By default. For information. report output files are saved in the content store. Results The administrator must now configure the file location. Procedure 1. To confirm that the correct location will be used. start IBM Cognos Configuration. click Save. 4. click Test. see the topic about setting a file location for report output saved outside of IBM Cognos BI.1: Installation and Configuration Guide . For more information. click the General tab. 7. 7. Windows UNC names. in a distributed installation on Microsoft Windows. 3. the URI must be formatted as follows: file://\\servername\directory Tip: Ensure that you do not use a mapped drive when running Cognos as a Microsoft Windows service. Click OK. Create a directory for your file system. 238 IBM Cognos Business Intelligence Version 10. Saved files are not managed by IBM Cognos BI.IBM Cognos BI embeds the font with all reports that use it. you can then share the report output with external applications or people who don't have IBM Cognos BI. an archive folder such as \\servername\directory could be used. a descriptor file with an _descr extension is also saved. 8. Save Report Output Outside IBM Cognos BI If you configure a file system location that is outside of IBM Cognos BI. If you use this option. in the IBM Cognos Business Intelligence Administration and Security Guide. The file:// portion of the URI is required. 5. If so. Tip: Ensure that the directory is accessible to users and separate from the installation directory. An administrator must then set the file location in IBM Cognos Administration. Click OK. you must first configure a root directory in IBM Cognos Configuration. in the IBM Cognos Business Intelligence Administration and Security Guide. 2. From the Actions menu. For Archive Location File System Root. You have the option of saving a copy of the report output in another file location that is outside or inside IBM Cognos BI. click Edit Global Configuration. From the File menu.2. To use this feature. can be used. Adobe Reader uses the embedded font when the report is opened. type a URI using the format file://directory where directory is the directory that you created in step 1. 6.

5. For information. Chapter 9. the location of the temporary session cache on the report file system is c10_location/temp/Session. Changing the Location of Temporary Report Output When users run interactive reports. in the IBM Cognos Business Intelligence Administration and Security Guide. Results The administrator must now configure the file location using the CM. start IBM Cognos Configuration. 6. Create a directory for your file system. Tip: Ensure that the directory is accessible to authorized users only. Procedure 1. click True. To configure whether the temporary report output is stored in Content Manager or in the local report file system. 2. click Data Access > Content Manager. click Test. The Session directory is created by the report server when the first request from a user session is received. To test the connection to the report output directory. You can change the location of the temporary session cache to a remote computer such as a shared directory on a Microsoft Windows based system or a common mounted directory on a UNIX or Linux based system.OutPutLocation parameter in IBM Cognos Administration. see the topic about setting a file location for report output saved inside IBM Cognos BI. Configuration options 239 . On the computer where Application Tier Components are installed. 3. On the Content Manager computer. 4. see the topic about storing user session files on a local report file system in the IBM Cognos Business Intelligence Administration and Security Guide. in the IBM Cognos Business Intelligence Administration and Security Guide. see the topic about setting a file location for report output saved inside IBM Cognos BI.OutPutLocation parameter. the file system must have third-party encryption. For more information. By default. because files that are saved in the Content Store may be deleted regularly due to retention rules. To protect the security of the report output when using this feature. For the Save report outputs to a file system property. the report output is stored in Content Manager or in a temporary session cache in the local report file system. you must first enable the Save report outputs to a file system property in IBM Cognos Configuration. start IBM Cognos Configuration. from the Actions menu. To use this feature.Save Report Output Inside IBM Cognos BI If you configure a file system location that is inside IBM Cognos BI. From the File menu. click Save. An administrator must then configure the file location using the CM. you can then use the report output again. In the Explorer window. This may also be useful for archive purposes. Procedure 1.

6. By default. then click the edit icon 4. click Environment. start IBM Cognos Configuration. In the Properties window. and . 240 IBM Cognos Business Intelligence Version 10. click Environment. click Save. In the Properties window. In the Explorer window. v Provide the user account that runs the IBM Cognos service with read and write access to the file location. On the Application Tier Components computer.2. . see the Map Manager Installation and User Guide. 2. 5. Change the Location of Map Charts for Report Studio IBM Cognos BI comes with a set of sample map charts that you can use in Report Studio. From the File menu. Click the edit button 5. the temporary report output is now stored in the new location. In the Explorer window. and then click Select. Procedure 1. 3. In the Select Folder dialog box.2. You can change the location of the map charts by using IBM Cognos Configuration. For information about using custom maps from other sources. Using an external object store for report output reduces the size of the content store and provides performance improvements for Content Manager. click the value for Temporary files location. see the Report Studio User Guide. Before you begin Ensure that you do the following before you create an external object store connection. use the Save in box to locate the computer and directory. click Save. When a user runs an interactive report session. the map charts are stored in the c10_location/maps directory on the Application Tier Components computer.1: Installation and Configuration Guide . 4. From the File menu. Use an external object store for report output You can configure Content Manager to store report output to a local drive or network share by defining an external object store. Report output is available through IBM Cognos Connection and IBM Cognos SDK. In the Select Folder window. click the value for Map files location. 3. navigate to the directory you want and then click Select. For more information about using map charts. but the report output is not stored in the content store database. v Provide Content Manager computers with access to the file location of the external object store.

Procedure 1. IBM Cognos Configuration verifies access to the external object store file location. Click the name for the repository. and then click New resource > External Object Store. such as file:///. essentially the repository service. If they do not have read access. Configuration options 241 . 3. Examples of URI values File system Windows URI value file:///c:/file-system-path file://host/share/file-system-path UNIX or Linux file:///file-system-path Note: Relative paths. and when the URI values window opens. You can have only one external object store./file-system-path and drive mappings are not supported.v Create the content store. Verify access to the external object store Use IBM Cognos Configuration to verify that IBM Cognos components can connect to the external object store. where file-system-path is the full path to an existing file location. Chapter 9. requests are routed to the active Content Manager. right-click the name of your external object store connection. To improve performance when reading outputs. In the Explorer window.Resource Properties window. Table 53. 4. In the New Resource . 5. click inside the value field. You can also test this connection by right-clicking Local Configuration and selecting Test. and click OK. should have read access to the file system location. From Explorer > Data Access. type the path to your file system location. 2.. click edit. In a distributed installation. type a unique name for your file system repository. Start IBM Cognos Configuration. In the External Object Store . Restart the IBM Cognos service. all Content Managers must have read and write access to the file system location. 3. Start IBM Cognos Configuration. Procedure 1.External Object Store window. right-click the name of your Content Store. under Data Access > Content Manager. Click Test. 2. Application Tier Components. 6.

1: Installation and Configuration Guide . and object_3. 242 IBM Cognos Business Intelligence Version 10. object_4. you must perform the following tasks: 1. you associate the tenancy information to specific multitenancy properties. Use hierarchies to determine tenancy information One way to determine tenancy information is to reuse the node structure information within a hierarchy. To configure multitenancy.2. the users would have access to the following objects: v Users belonging to Tenant 1 can access object_1. v Users belonging to Tenant 2 can access object_3. “Identify tenancy information” 2. To identify tenancy information. “Enabling multitenancy” on page 244 Identify tenancy information Before you can modify your configuration for multitenant applications. Figure 11. or you can use the properties associated with user objects. you need to identify how tenancy information (grouping) is determined in your environment for the individual users. The following diagram shows how the Cognos BI multitenancy capabilities isolate access to objects in your content store. Multitenancy properties that you specify for a specific namespace override any multitenancy properties that you set globally. Then. You can also create custom code that is invoked during the user authentication process. object_5.Configuring multitenancy settings Before you can use IBM Cognos multitenancy. object_2. you can use the position of a user within a hierarchy. Users can access only the objects that they are authorized to access within each tenant grouping. Tip: The system administrator can access all objects in the content store. Content store configured to use the Cognos BI multitenancy capabilities In this example. you must modify configuration settings in your IBM Cognos Business Intelligence installation. and object_6.

When reusing the node structure information. you could specify: multitenancy. which represents the hierarchical path to a user account in the form of an array. Use object attributes to determine tenancy information If you cannot use the node structure hierarchy to determine the tenancy information. For example. where locale is based on the mapping in the namespace configuration.TenantPattern advanced property as follows: multitenancy.TenantPattern = ~/parameters/parameter_name In this example.ITenantProvider property as follows: multitenancy. you might need to join data from multiple authentication sources. In such cases. set the multitenancy. Ancestors attribute mapped to hierarchy information Ancestors information ancestors[0] ancestors[1] ancestors[2] Hierarchy Directory node Namespace ID Tenant grouping. set the multitenancy. you can use specific object attributes from your authentication provider.TenantPattern = ~/ancestors[2]/searchPath/objectId. v searchPath/objectID. or from an authentication source and a relational database. if the departmentNumber attribute of an LDAP user object identifies the user’s tenant. you create a custom Java class using the IBM Cognos Software Development Kit and specify its name during the BI configuration. you could specify: multitenancy. For example. In this scenario. you must create a custom class that is invoked during the user authentication process to determine the tenancy information.ITenantProvider = custom_class_name Chapter 9. the name is the title of the object. such as folders base DN organizational units LDAP example For example. the following ancestors qualifiers can return tenancy information: v name/locale.TenantPattern = ~/ancestors[2]/defaultName Note: In addition to defaultName.TenantPattern advanced property to the following value: multitenancy. set the multitenancy.TenantPattern = ~/ancestors[2]/name/EN-ca. For example. This method requires that you also identify any additional properties to be queried during the user authentication process. If no locale is given. if users are stored in an LDAP directory and tenants are directly under the base Distinguished Name (DN) as organizational units. you must also set the following LDAP custom property: parameter_name = departmentNumber Use custom code to determine tenancy information When the tenancy information cannot be obtained through a hierarchy or a user attribute. For example. you can use the information provided by the ancestors user attribute. The following table shows how you could map the ancestors attribute to a hierarchy to identify the tenancy information: Table 54. Configuration options 243 .

IBM Cognos Software Development Kit includes a sample custom class to determine tenancy information. or update the CLASSPATH environment variable to include the path to these files. If a namespace is not configured to use multitenancy.1: Installation and Configuration Guide . Enabling multitenancy To enable Cognos multitenancy capabilities. under Security. you set advanced authentication properties on all the computers where the Content Manager is configured. com.example. v Compile any required custom Java class files into JAR files and either place them into the c10_location/webapps/p2pd/WEB-INF/lib directory along with any associated files. 3. For more information.Class. such as a department number (departmentNumber). Click Add. You can find the sample files in the c10_location\sdk\java\AuthenticationProvider\ MultiTenancyTenantProviderSample directory. the tenant IDs in all namespaces must be unique. v To configure the tenancy information for one namespace: In the Explorer window. Add the multitenancy properties that you need. you must also set the MultiDomainTree advanced property to true to map tenants to domains.2. see “Identify tenancy information” on page 242. use the following steps: v To configure the tenancy information for all namespaces: In the Explorer window. Procedure 1. then policies and permissions for objects are used to determine who can access the objects. Set the following advanced property: 244 IBM Cognos Business Intelligence Version 10. you could set the following property: multitenancy. 2. you would follow these steps: a.where custom_class_name represents the name of your custom class. If multitenancy is applied to multiple namespaces. Click the namespace that you want to configure. To configure tenancy settings globally or for individual namespaces. The following scenarios illustrate possible combinations of the multitenancy properties: v To use hierarchy information. 5. under Security. 4. v To use specific object attributes from your authentication provider. and then restart the IBM Cognos service. Before you begin v Identify how tenant information is determined for individual users in your environment. for example. Click the Edit button in the Value column for Advanced properties. This is required only if using custom Java authentication provider.TenantPattern = ~/ancestors[2]/defaultName Note: If you use Active Directory namespaces. Open IBM Cognos Configuration. v Determine whether you must apply the multitenancy settings to all configured namespaces or to individual namespaces. click Authentication. Multitenancy properties for a specific namespace override any multitenancy properties that are set globally. click Authentication.

Restart the IBM Cognos service for the changes to take effect. 7.ITenantProvider = custom_class_name 6. 6. Test the changes. The decision to disable multitenancy must be carefully considered. 4. From the File menu. 2. you must remove all multitenancy advanced authentication properties on all computers where Content Manager is configured. v To disable tenancy settings for one namespace: In the Explorer window. Click OK. To track tenant activities. 3. Important: To disable multitenancy.multitenancy. Open IBM Cognos Configuration. If all tenant IDs are not removed after disabling multitenancy. and click Test. and click Test. In the Explorer window. Chapter 9. see the Administration and Security Guide. A message showing that multitenancy is enabled appears in the Details window and is written to the cogserver. Disabling multitenancy To disable multitenancy. 5. Click the Edit button in the Value column for Advanced properties. where custom_class_name represents the name of a Java class that you created. you can use a logging database. Important: If multitenancy properties are set globally and individually. Configuration options 245 . you would set the following property: multitenancy. under Security. all tenant IDs must be removed from all objects in the content store. 9. To fully understand the multitenancy features. click Authentication. Test the changes. click Save.log file.TenantPattern = ~/parameters/parameter_name b. the properties for a specific namespace override any global multitenancy properties. right-click Authentication. Procedure 1. 7. Select the multitenancy properties that you want to remove. To disable tenancy settings that are set globally or to specific namespaces. 8. Click the Remove button. For more information. use the following steps: v To disable the tenancy settings for all namespaces: In the Explorer window. right-click Authentication. the system administrator must set the tenancy information for the objects in the content store. Click the namespace that you want to configure. What to do next After multitenancy is enabled. under Security. click Authentication. Set the following namespace custom property: parameter_name = departmentNumber v To use a custom Java class. In the Explorer window. Click OK. test the system before enabling multitenancy in a production environment. the application behavior is unpredictable.

the default queue is used. changes the Format to PDF. Specifies the height of the page in points. selects Print the Report from the Delivery section. Procedure 1. From the File menu. problems might occur when printing to a UNIX or Linux print server. The rsprintpdf. HP-UX.sh file. for example letter or A4 paper size. Customizing Server-side Printing for UNIX and Linux Platforms The way in which the IBM Cognos Connection portal handles server printing can differ depending on your platform.sh script by the server process as command line options. and without the -m option.sh file located in the c10_location/bin directory.sh file should not be configured for Microsoft Windows operating system print servers. 9. If no orientation is specified. In a text editor. Restart the IBM Cognos service.8. the system administrator must review and update the policies on objects and then update the tenancy to public. Option -p Name printer Description Specifies the print queue. Specifies the media size of the output.2. If no media. The information is passed to the rsprintpdf. click Save. If no print queue is specified. What to do next After multitenancy is disabled. portrait orientation is used. for example AIX. the default paper tray is used.1: Installation and Configuration Guide . or it might appear cropped or incorrectly orientated. For this reason. The output might not be generated. 2. Open the rsprintpdf. and then specifies additional formats through advanced options such as Landscape orientation. It is valid only if specified with the -w option. customize the section that is specific to your print server's platform. or no height or width are specified. 3. -o orientation -m media -h height 246 IBM Cognos Business Intelligence Version 10. When a user selects Run with Options. Use the following information for customization. you can customize the way in which the IBM Cognos Connection portal handles the printing of PDF format reports for UNIX and Linux platforms by configuring the rsprintpdf. A4 paper size or a Time and Mode to run the report. for example landscape or portrait. Specifies the page orientation for a file. or Linux. For custom page sizes.

Use the following checklist to help you help you set up the notifications database in DB2 on z/OS. the notification server uses the same database that Content Manager uses for the content store. The default filename for the log file is rsprintpdf. Configuration options 247 . and without the -m option. To ensure a successful installation. use the same procedure that was used to create the content store database. you cannot generate a script to create the notification database in the same way as you can the content store. You can use the same procedure as to set the connectivity for the content store database. use the following guidelines when creating the notification database. storage group. -L log file 4. or Sybase. Note: If you are using DB2. __ v Create a database instance. Oracle. Microsoft SQL Server.” v Setting up the database connectivity. For DB2.sh file in case it should be overwritten by a future software upgrade.log. Change the notification database By default. It is valid only if specified with the -h option. Specifies the width of the page in points. Tip: Keep a copy of the rsprintpdf. Suggested settings for creating a notification database on DB2 on z/OS The database you create for the notification database must contain the specified configuration settings. Use the instructions in “Change the Connection Properties for the Notification Database” on page 249. and a user account for the notification database. Specifies a path to a user-specified file for logging error messages. Chapter 9. You can use a separate database for notification in situations where you run large volumes of batch reports and email. Use the instructions in “Guidelines for creating the content store” on page 45.errors. use the instructions in “Suggested settings for creating a notification database on DB2 on z/OS. For DB2 on z/OS. v Changing the connection properties for the notification database.Option -w Name width Description For custom page sizes. Using a separate database for notification involves the following tasks: v Creating a notification database. “Set up database connectivity for the content store database” on page 80.

For more information. Not all of the parameters listed are in the script. __ v Administrators must run a script to create tablespaces to hold Large Objects and other data for the notification database to use the tablespaces. Open the original NC_TABLESPACES. all names of parameters must start with a letter and the length must not exceed 6 characters. The scripts 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 for z/OS.sql script file and save the file to another location. Tablespace parameter names and descriptions for the DB2 notification database on z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the notification database. see “Creating tablespaces for a notification database on DB2 for z/OS.sql script file and use the following table to help you to replace the placeholder parameters with ones appropriate for your environment. Connect to the database as a user with privileges to create and drop tablespaces and to allow execution of SQL statements. 248 IBM Cognos Business Intelligence Version 10. For information about running the script. To create the notification tablespaces.” __ v Your database administrator must back up IBM Cognos BI databases regularly because they contain the IBM Cognos data. a. see the IBM DB2 Information Center. Make a backup copy of the NC_TABLESPACES. For example. a database administrator must run scripts to create a set of tablespaces required for the notification database. To ensure the security and integrity of databases. protect them from unauthorized or inappropriate access.sql script file and replace the NCCOG placeholder parameter with the name of the notification database. 2. __ v Ensure you reserve a buffer pool with a page size of 32 k. db2 -tvf NC_TABLESPACES. Table 55. Open the NC_CREATE_DB2.A user must have permissions to create and delete tables in the database.1: Installation and Configuration Guide . Creating tablespaces for a notification database on DB2 for z/OS If you are using DB2 for z/OS. c. Procedure 1. Specifies the name of the buffer pool.sql d.2. b. but might be added in the future. For example. and a second one with a page size of 4 k for the database instance. go to the c10_location/configuration/ schemas/delivery/zosdb2 directory. IBM Cognos BI uses the credentials of the user account to communicate with database server. Specifies the name of the storage group. Save and run the script.

set up the content store to use a supported database that can be secured and tuned for performance. Test the notification. v Click OK. Save the script. 4. the schedules will be replicated in the tables of the new notification database. Results Ensure that the values used to identify the notification database resource are the same on all Content Manager and Application Tier Components computers. you do not have to edit the values in the Properties window. 6. 5. enter the values for the notification database resource. This tests the database connection and the mail server connection. Create a New Content Store Using Cognos Content Database Use the following steps to create another content store database using the Cognos Content Database. In the Properties window. v Select the type of database from the pull-down menu. Configuration options 249 . From the File menu. Chapter 9. When moving to a production environment with your IBM Cognos product. Identify the database that is used for notification: v In the Explorer window. In each location where Content Manager or Application Tier Components is installed. In the Explorer window right-click Notification and click Test. However. The Job and Scheduling Monitor services will automatically run the script. click Notification. Before you begin Only use Cognos Content Database for test or demonstration purposes. you must configure IBM Cognos components to use the new database. click Save. Procedure 1. under Data Access. This might be required if you install more than one instance of your IBM Cognos product in the test location and you want to run the instances separately. Change the Connection Properties for the Notification Database After you create a separate database for notification. you may choose to run it yourself. start IBM Cognos Configuration. 3. To use the default notification database.e. Cognos Content Database gets a test system running quickly. You must configure all Content Managers and Application Tier Components to use the same notification database. right-click Notification and select New resource > Database. If you have been using the content store database for notification. 2. In the Explorer window. v Type a name for the database resource.

use the ij.2. In the location where you installed the new instance of Cognos Content Database. The database files are located in the c10_location\contentstore directory.1 trust stores that are used for SSL communications include only certificates that are qualified for the NIST SP800-131a standard. You can add non-NIST SP800-131a standards and you can also remove the non-NIST SP800-131a standards you have added. and password for the new content store.create=true.1 trust stores includes only certificate authority (CA) certificates that are qualified for the NIST SP800-131a standard.password=cognos2'. you must add these certificates to the trust store individually. Restore non-NIST SP800-131a standard certificates to IBM Cognos trust stores By default. 2.1/bin directory.user=username. disconnect by using the following command: disconnect.bat or ij.1: Installation and Configuration Guide . in the c10_location/derby10. do the following: v Install the additional instance of your IBM Cognos wsproduct in a separate directory on the same computer. Ensure that you use a different name. you would type connect 'jdbc:derby://localhost:1527/ contentstore2. Procedure 1.Before you create the new content store. user. If you change the Signing key store password. the IBM Cognos version 10. such as SHA1 or 1024-bit CA certificates. v Create a new user and password for the new content store database. Change the security standard compliance for IBM Cognos trust stores By default. ensure you use the password that you set. Ensure that you select Cognos Content Database on the Component Selection page of the installation wizard. Or. You can change the certificates available to you by using the ThirdPartyCertificateTool. If you use other certificates. Use the following syntax: connect 'jdbc:derby://host:port/db_name. Note: The examples in this task use the default password.2.2. password=password'.1.ksh script to create a new database. For example. and the Certificate Authority key store password in IBM Cognos Configuration. When you are finished with the ij utility. 250 IBM Cognos Business Intelligence Version 10.2. you add these certificates from the trust store of the JRE you are using with the ThirdPartyCertificateTool restore command. The database name is case-sensitive. to create a database named contentstore2 on the localhost computer on port number 1527 as a user named cognos2 with a password of cognos2. the Encryption key store password. the IBM Cognos version 10.user=cognos2.create=true. NoPassWordSet.

type ThirdPartyCertificateTool... and the Certificate Authority key store password in IBM Cognos Configuration. Procedure 1. Note: The examples in this task use the default password. For example./configuration -p NoPassWordSet On Windows operating systems.sh -R -D .sh -N -D . Before you begin On UNIX or Linux operating systems. Configuration options 251 . type ThirdPartyCertificateTool. ThirdPartyCertificateTool. NoPassWordSet... you can remove those certificates with the ThirdPartyCertificateTool.bat -R -D . you can run the tool with -java:local to use the JRE that is provided with the installation.. the Encryption key store password. type ThirdPartyCertificateTool. you can run the tool with -java:local to use the JRE that is provided with the installation.bat -java:local -R -D . 2. For example. On Microsoft Windows installations.. ThirdPartyCertificateTool. such as SHA1 or 1024-bit CA certificates. ensure that you set a JAVA_HOME environment variable before you use the ThirdPartyCertificateTool./configuration -p NoPassWordSet On Windows operating systems.bat -java:local -N -D .. 2. On Microsoft Windows installations. Procedure 1. Restore the non-NIST SP800-131a standard certificates by typing the following command: On UNIX or Linux operating systems.\configuration -p NoPassWordSet Chapter 9. ensure that you set a JAVA_HOME environment variable before you use the ThirdPartyCertificateTool. type ThirdPartyCertificateTool. If you change the Signing key store password. Go to the c10_location\bin directory. Type the following command: On UNIX or Linux operating systems. ensure you use the password that you set.\configuration -p NoPassWordSet Remove non-NIST SP800-131a standard certificates from the IBM Cognos trust stores If you have added non-NIST SP800-131a certificates to the IBM Cognos trust stores. Go to the c10_location\bin directory.bat -N -D ..Before you begin On UNIX or Linux operating systems.

For more information about that process. such as iPlanet or Microsoft. Operation modifiers Command -s -e -T Table 58. The following tables list the options for this command-line tool. RSA is the default value. Directory location Description Work with the signing identity Work with the encryption identity Work with the trust store (only with -i) Description Creates a CSR Imports a certificate The sample values from the following table are used: 252 IBM Cognos Business Intelligence Version 10. IBM Cognos BI components use their own certificate authority (CA) service to establish the root of trust in the IBM Cognos security infrastructure. 2.Configuring IBM Cognos components to use another certificate authority By default. “Create certificate signing request (CSR) files” on page 253. However.1: Installation and Configuration Guide . Information flags Command -d -r -t -p -a -D Description DN to use for certificate CSR or certificate file location (depends on mode) Certificate authority certificate file (only with -i) Key store password Key pair algorithm: either RSA or DSA. “Configure IBM Cognos BI Components to use certificates generated by your CA” on page 256. you must use the following process: 1. Main operation mode Command -c -i Table 57. Part of this task requires you to submit the CSRs to your certificate authority and generate the certificates. you can configure IBM Cognos components to use a certificate from another certificate authority. Some tasks use a command-line tool named ThirdPartyCertificateTool. To use another CA certificate. “Import the CA certificates into IBM Cognos components” on page 255 3. Table 56.2. see your CA documentation.

type Chapter 9. 3.Table 59. Note: The examples in this task use the default password. Back up the cogstartup. Back up your key data: a. If you change the Signing key store password. c.O=MyCompany. Configuration options 253 . The CA uses these files to produce a signing certificate. Create the certificate signing request for the signing keys by typing the following command: On UNIX or Linux operating systems.xml file to a secure location. Sample values Property Signing certificate distinguished name (DN) Value A unique value. and Certificate Authority key store password.O=MyCompany. Encryption key store password. Create certificate signing request (CSR) files To obtain a certificate from a certificate authority (CA). NoPassWordSet. you can run the tool with -java:local to use the JRE that is provided with the installation. and a CA certificate that you import into your keystores. formatted as: CN=EncryptCert. On Microsoft Windows installations. ensure you use the passwords that you set.C=CA Key store password The default password: NoPassWordSet This value must match the passwords in IBM Cognos Configuration under Security > Cryptography > Cognos. formatted as: CN=SignCert. and the Certificate Authority key store password in IBM Cognos Configuration. Procedure 1. Go to the c10_location\bin directory. b. the Encryption key store password.C=CA Encryption certificate DN A unique value. Back up the contents of the following directories to a secure location: v v c10_location\configuration\signkeypair c10_location\configuration\encryptkeypair 2. an encryption certificate. ThirdPartyCertificateTool. If you change the default values for Signing key store password. For example. you must first generate certificate signing request (CSR) files for the signing keys and encryption keys from the IBM Cognos keystores.bat -java:local -c -s -d . ensure that you set a JAVA_HOME environment variable before you use the ThirdPartyCertificateTool. Go to the c10_location\configuration directory. ensure you use the password that you set... Before you begin On UNIX or Linux operating systems.

C=CA" -r encryptRequest.csr file to the c10_location\bin directory. The command creates the jSignKeystore file in the signkeypair directory.csr and encryptRequest. The certificate authority produces a signing key certificate. The attributes that are used reflect a hierarchical structure in your organization. The password that you enter for this key must be used again when import the certificate and again in IBM Cognos Configuration./configuration/encryptkeypair -p NoPassWordSet On Windows. 6.csr -D .sh -c -e -d "CN=EncryptCert.C=CA" -r encryptRequest. Input the signRequest. 4.. You can safely ignore any warnings about logging. stores it in the keystore. and exports the signRequest.2. and exports the encryptRequest. The attributes that are used reflect a hierarchical structure in your organization.C=CA" -r signRequest. The password that you enter for this key must be used again when import the certificate and again in IBM Cognos Configuration. type ThirdPartyCertificateTool. The command creates the jEncKeystore file in the encryptkeypair directory. and a CA certificate.csr files to a directory that is accessible by your certificate authority./configuration/signkeypair -p NoPassWordSet On Microsoft Windows operating system. type ThirdPartyCertificateTool.O=MyCompany. an encryption key certificate. and generate the certificates. sets the specified password. 5.sh -c -s -d "CN=SignCert.bat -c -s -d "CN=SignCert. sets the specified password. You can safely ignore any warnings about logging.\configuration\signkeypair -p NoPassWordSet The distinguished name (DN) value in the command ("CN=SignCert.\configuration\encryptkeypair -p NoPassWordSet The distinguished name (DN) value in the command ("CN=SignCert. creates a keypair. creates a keypair.C=CA") uniquely identifies the IBM Cognos installation.bat -c -e -d "CN=EncryptCert.csr and encryptRequest.ThirdPartyCertificateTool.csr files into the certificate authority.O=MyCompany. type ThirdPartyCertificateTool. Copy the signRequest.O=MyCompany. Important: The certificates that are generated by your CA must be PEM (Base-64 encoded ASCII) format.O=MyCompany. stores it in the keystore.C=CA") uniquely identifies the IBM Cognos installation...csr -D .csr -D .O=MyCompany. 254 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide .csr file to the c10_location\bin directory. Results You can now import the generated certificates into your IBM Cognos components in the following task. Create the certificate signing request for the encryption keys by typing the following command: On UNIX or Linux.O=MyCompany.csr -D ..C=CA" -r signRequest.

type ThirdPartyCertificateTool. the Application Tier Components.\configuration\signkeypair -p NoPassWordSet -t ca. Configuration options 255 . Procedure 1. Import the encryption certificate into the IBM Cognos encryption key store by typing the following command: On UNIX or Linux operating systems. ThirdPartyCertificateTool.cer. On Microsoft Windows installations.cer Important: Ensure you use the password that you entered when you exported the signing key in the previous task.sh -i -s -r signCertificate.bat -i -s -r signCertificate. 2. The command reads the signCertificate.cer.. For example.cer -D . type ThirdPartyCertificateTool. ensure that you set a JAVA_HOME environment variable before you use the ThirdPartyCertificateTool. 3. You can safely ignore any warnings about logging. 5. NoPassWordSet.cer On Windows operating systems. If you change the Signing key store password. you can run the tool with -java:local to use the JRE that is provided with the installation. type Chapter 9. and ca. you must import them to your IBM Cognos components.cer. You must import the certificates on each computer where you have IBM Cognos components installed.cer files in the c10_location\bin directory and imports the certificates from both files into the jSignKeystore file in the signkeypair directory using the specified password.cer files to the c10_location/bin directory. including Content Manager.cer -D . Before you begin On UNIX or Linux operating systems... and the modeling components./configuration/signkeypair -p NoPassWordSet -t ca. type ThirdPartyCertificateTool.cer.cer and ca. Create a copy of the signing certificate file and name it signCertificate. Import the signing certificate into the IBM Cognos signing key store by typing the following command: On UNIX or Linux operating systems. 4. and the Certificate Authority key store password in IBM Cognos Configuration. the gateway.. the Encryption key store password. Create a copy of the encryption certificate and name it encryptCertificate..cer.cer On Windows operating systems. Create a copy of the root CA certificate and name it ca. Copy the signCertificate. 6.sh -i -e -r encryptCertificate./configuration/encryptkeypair -p NoPassWordSet -t ca. encryptCertificate.Import the CA certificates into IBM Cognos components After you obtain the certificates from the CA.cer -D . ensure you use the password that you set. Note: The examples in this task use the default password.bat -java:local -c -s -d .

\configuration\ signkeypair -p NoPassWordSet The command reads the ca. 4. Configure IBM Cognos BI Components to use certificates generated by your CA After you import the CA certificates.cer -D . You can safely ignore any warnings about logging. you do not have to change the path. click Cognos. When you set this property to true. and enter the path for the Encryption key store location. and the Certificate Authority key store password in IBM Cognos Configuration.bat -i -T -r ca. Procedure 1.. Click the Value box next to Use third party CA. type ThirdPartyCertificateTool. 256 IBM Cognos Business Intelligence Version 10.sh -i -T -r ca. all properties for the certificate authority and identity name are ignored.1: Installation and Configuration Guide .ThirdPartyCertificateTool. 7. you do not have to change the path. If you used the same values in the examples in the previous tasks. Note: Ensure that the key store locations and passwords in IBM Cognos Configuration match the ones that you typed in the command-line tool. 3. For example. Enter the password that you used for the signing key in Signing key store password. type ThirdPartyCertificateTool. The command reads the encryptCertificate.cer -D . 5.2. Import the CA certificate into the IBM Cognos trust store by typing the following command: On UNIX or Linux operating systems. ensure you use the password that you set.cer files in the c10_location\bin directory and imports the certificates from both files into the jEncKeystore file in the encryptkeypair directory using the specified password. if you change the Signing key store password. Enter the Certificate Authority key store password. the Encryption key store password.cer and ca. 2. and enter the path for the Signing key store location. under Security > Cryptography. Results You can now configure your IBM Cognos components to use your CA certificates. Start IBM Cognos Configuration.\configuration\encryptkeypair -p NoPassWordSet -t ca.cer Important: Ensure you use the password that you entered when you exported the encryption key in the previous task. and select True. Enter the password that you used for the encryption key in Encryption key store password. 6./configuration/ signkeypair -p NoPassWordSet On Windows operating systems.bat -i -e -r encryptCertificate. If you used the same values in the examples in the previous tasks.cer file and imports the contents into the jCAKeystore file in the signkeypair directory using the specified password. you use IBM Cognos Configuration to configure each computer where an IBM Cognos component is installed to use the certificate.cer -D .. In the Explorer window..

Add a computer to an installation If you add a computer to an SSL-enabled environment. Chapter 9. you can use SSL for internal connections. the trust to the SSL certificates is inherited from the existing components. Configure SSL for IBM Cognos components For IBM Cognos components. Configuring the SSL protocol for IBM Cognos components You can use the Secure Sockets Layer (SSL) protocol for communication between IBM Cognos components in single server and distributed installations. Configuration options 257 . Click File > Save. or both. If you configure SSL for internal connections only. you must configure two dispatcher URIs. After you save the configuration with SSL settings.xml file. Restart your IBM Cognos services. 8. you will be prompted to temporarily accept trust for a certificate when you save the configuration. if you are not currently using SSL. IBM Cognos components on the local computer will communicate using this protocol. you must stop the service before changing the protocol to https. Single computer installations In a single computer installation. Tomcat connectors If the internal dispatcher URI is prefixed with http but the external dispatcher URI is prefixed with https. Distributed installations In distributed installation. you can restart the services. If the internal and external dispatcher URIs use different protocols or ports. HTTP requests. both the non-SSL Coyote HTTP/1.7. If you add the component to a different location on the same computer but to an environment already configured for SSL. or vice versa. Add a component to a computer If you add a component to an installation that has already been configured for SSL. the internal dispatcher port is accessible only to the components on the local computer. The internal dispatcher URI must also specify localhost. Accepting the temporary certificate will allow permanent trust to be established with the existing components. Accepting the temporary certificate will allow permanent trust to be established with the existing components. external connections.1 and SSL Coyote HTTP/1.1 connectors are enabled in the server. Therefore. The dispatcher listens for secure connections on a different port than for remote. you must first configure the default active Content Manager computer to use the SSL protocol and start the services on that computer before you configure the Application Tier and gateway components to use SSL. you will be prompted to temporarily accept trust for a certificate when you save the configuration.

the dispatcher can use the same port for internal and external connections. communications from remote IBM Cognos components to the local computer will use the SSL protocol. The port numbers in the two dispatcher URIs must be different. click Environment. Similarly. enter the same URI for both the Internal dispatcher URI. if you do not use SSL for local or remote communication. Procedure 1. 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. Enter https and a port number for SSL communication. enter https and a port number for SSL communication in the External dispatcher URI and Dispatcher URI for external applications properties. leave http as the protocol and use the default or another available port number. Start IBM Cognos Configuration. v If you have installed the gateway on a separate computer. type the appropriate values for the URI values: v To configure SSL for internal connections only. the Internal dispatcher URI property must specify localhost. enter https and a port number for SSL communication in the Internal dispatcher URI property. in IBM Cognos Configuration on the gateway computer. This applies to both SSL and non-SSL connections.1: Installation and Configuration Guide . and Dispatcher URI for external applications properties. HTTP requests. For the Internal dispatcher URI property.2. see “Configuring IBM Cognos components to use another certificate authority” on page 252. External dispatcher URI. enter https and the port number for SSL communication in the Dispatcher URIs for gateway property. You must configure the dispatcher to listen for secure. v Additionally. remote requests on a different port than local. If you want to use certificates managed by another service. you can enter https and a port number for SSL communication in the Content Manager URI property. For the External dispatcher URI and Dispatcher URI for external applications properties. 3. 258 IBM Cognos Business Intelligence Version 10. In the Properties window. If you configure SSL for all connections. 2. By default. In distributed installation. the dispatcher can use the same port for all communications. If you use Tomcat. IBM Cognos BI components use an internal certificate authority (CA) to establish the root of trust in the IBM Cognos security infrastructure. The port number in the two dispatcher URIs must be different.If you configure SSL for external connections only. leave http as the protocol and use the default or another available port number. you must first configure the default active Content Manager computer to use the SSL protocol and start the services on that computer before you configure the Application Tier Components computer. and you are using SSL for external connections. If you use Tomcat. In the Explorer window. v To configure SSL for external connections only. v To configure SSL for all connections. the Internal dispatcher URI property must specify localhost.

4. For information on updating the server trust store. If you want the connection between IBM Cognos servers and the other server to be mutually authenticated. Ensure that the CA certificate is in Base-64 encoded X. 2. you do not have to set up shared trust between IBM Cognos server and other servers. the browsers automatically prompt users to update their trust stores. In a distributed environment. Restart your services. Configuration options 259 . Procedure 1.sh -T -i -r CA_certificate_file -k c10_location/configuration/signkeypair/jCAKeystore -p NoPasswordSet Chapter 9. type the following: ThirdPartyCertificateTool. If you have configured IBM Cognos components to use another certificate authority (CA). copy the certificate from the certificate authority to the IBM Cognos server. Import the CA certificate by typing the following command: v On UNIX or Linux operating systems. start the services on the Content Manager computer first.bat -E -T -r destination_file -k c10_location\configuration\signkeypair\jCAKeystore -p NoPasswordSet 3. Copy the certificate from your certificate authority to a secure location on the IBM Cognos server. Go to the c10_location/bin directory. type ThirdPartyCertificateTool.sh -E -T -r destination_file -k c10_location/configuration/signkeypair/jCAKeystore -p NoPasswordSet v On Microsoft Windows operating systems. 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. Copying the CA certificate to IBM Cognos servers After copying the IBM Cognos certificate to the other servers. you must add the IBM Cognos certificate to the trust store on the other servers. see the documentation for your server. 5. Import the certificate to the trust store on your server. Procedure 1. followed by the services on the Application Tier Components computers. you must also copy the certificate from your certificate authority to the trust store for IBM Cognos servers. Note: If you use browsers to connect to IBM Cognos components. Extract the IBM Cognos certificate by typing the following command: v On UNIX or Linux operating systems. From the File menu.509 format. click Save. 2. type ThirdPartyCertificateTool. Copying the IBM Cognos certificate to another server The first task in adding the IBM Cognos certificate to the trust store on other servers is to copy the certificate to the server.

click the Value column for the Supported ciphersuites property. At least one of the selected cipher suites between the client and server platforms must match. You can eliminate cipher suites that do not meet your requirements and then assign a priority. Start IBM Cognos Configuration. click the check box and then click Remove. v To remove a cipher suite from the Current values list. v To move a cipher suite up or down in the Current values list. 3. click the check box and then click the up or down arrows. type ThirdPartyCertificateTool. click the check box in the Available values list and then click Add. Configure IBM Cognos for SSL enabled Web servers If you are using secure sockets layer (SSL) on your Web server. Click the edit icon v To move a cipher suite to the Current values list.2. this may affect the supported cipher suites available on that computer. and key exchange algorithms. you must change the Gateway URI values in IBM Cognos Configuration to be able to access the portal. The selected cipher suites are presented in priority sequence for the client and server sides of the negotiation. or preference.bat -T -i -r CA_certificate_file -k c10_location\configuration\signkeypair\jCAKeystore -p NoPasswordSet Select and rank cipher suites for Secure Socket Layer An SSL connection begins with a negotiation in which the client and server present a list of supported cipher suites in a priority sequence. you must obtain a Web server certificate signed by a Certificate Authority (CA) and install it into your Web server. A cipher suite provides the quality of protection for the connection. . If you no longer have a supported cipher suite that matches the other computers in your environment. To enable SSL on your Web server. you may have to change the JRE on the computer to match the other computers in your environment. authentication. In the Properties window. 6. 4. 5. such as upgraded the JRE or installed software that has upgraded the JRE. It contains cryptographic.v On Microsoft Windows operating systems. because self-signed certificates will not be trusted by IBM 260 IBM Cognos Business Intelligence Version 10. If you have made changes to a computer. and depends on the Java Runtime Environment (JRE) or whether you have other cryptographic software installed on the computer.1: Installation and Configuration Guide . The SSL protocol selects the highest priority suite that the client and the server both support. The certificate must not be self-signed. 2. Procedure 1. click Cryptography > Cognos. Click OK. From the File menu. In the Explorer window. The list of supported cipher suites is dynamically generated on each computer. hash. A list of supported cipher suites for SSL is provided. click Save. to the remaining cipher suites.

are disabled. and indicators for fatal errors. 3. log messages provide information about the status of components and a high-level view of important events. v During planning. the default port number for SSL connections is usually 443. and change the Gateway URI value from http to https. If your application requires secure authentication.Cognos components. For more information about using certificates with your Web server. Audit logs. To avoid being prompted by a security alert for each new session. change the port number to the SSL port number defined for your Web server. These certificates are not provided with IBM Cognos products. Configure your Web server for SSL and start the Web server. Under Local Configuration. Because the log server uses a different port from the other IBM Cognos BI components. On each computer where the Application Tier Components or Framework Manager are installed. determine the logging configuration that is suitable for your environment. Save your configuration. provide information about user and report activity. which are available from a logging database. start IBM Cognos Configuration. such as the dispatcher. Related tasks: “Set up security for a Google OneBox sample module” on page 419 By default. Google OneBox applications are open and anonymous. Procedure 1. install the certificate into one of your Web browser's certificate stores. log messages can provide information about attempts to start and stop services. Configuring a Repository for Log Messages The BI Bus protocol includes log message processing. and restart your services. For example. A local log server is installed in the c10_location/logs folder on every IBM Cognos BI computer that contains Content Manager or Application Tier Components. In the Gateway URI value. you should be prompted to install a certificate. Results When you access the portal using https://servername:443/ibmcognos. an important diagnostic tool for investigating the behavior of IBM Cognos BIs. see your Web server documentation. To enable users to access the IBM Cognos portal using SSL. The following workflow shows the tasks that are required to prepare for logging. you must configure the Google Search Appliance (GSA) and your IBM Cognos installation appropriately. it continues to process events even if other services on the local computer. For example. The IBM Cognos services on each computer send information about errors and events to a local log server. such as Chapter 9. 5. In addition to error messages. click Environment. 4. Configuration options 261 . For example. completion of processing requests. you must change the Gateway URI values in IBM Cognos Configuration for each computer where the Application Tier Components and Framework Manager are installed. 2. evaluate various log message repositories.

see the IBM Cognos Business Intelligence Administration and Security Guide. make the appropriate configuration changes on both IBM Cognos BI computers. Oracle. 262 IBM Cognos Business Intelligence Version 10. You can also send only audit logging information to a database. you cannot generate a script to create the notification database in the same way as you can the content store. specify the level of detail to log to focus messages on the information that is relevant in your organization. For information about planning. Creating a logging database involves the following tasks: v Create a logging database.1: Installation and Configuration Guide . You must also create a logging database if you plan to collect audit logs. v During configuration. or Sybase. For information about using log messages to solve problems and resolving logging-related issues. Use the following checklist to help you set up the logging database on DB2 on z/OS. Use the instructions in “Log message repositories” on page 265. __ v Create a database instance. such as methods available for protecting log files from system failures and user tampering. Note: If you are using DB2. v When setting up logging. such as the UNIX or Linux syslog or the Windows NT Event log. use the instructions in “Suggested settings for creating a logging database on DB2 on z/OS . Suggested settings for creating a logging database on DB2 on z/OS The database you create must contain the specified configuration settings. see the IBM Cognos Business Intelligence Architecture and Deployment Guide. If communication between a local log server and a remote log server must be secured. Microsoft SQL Server. define the startup properties for logging. such as user-specific logging. storage group. For DB2 on z/OS. use the same procedure that was used to create the content store database. Guidelines for creating a logging database You can create a database to store log messages. in addition to the local log file.” v Set up the database connectivity. Use the instructions in “Database connectivity for the logging database” on page 264. IBM Cognos uses the credentials of the user account to communicate with the database server. For DB2. Consider security. see the IBM Cognos Business Intelligence Troubleshooting Guide. such as connection settings for databases.remote log servers and log files. Use the instructions in “Guidelines for creating the content store” on page 45.2. and a user account for the content store. For information about setting up logging. Audit reports may also be set up to track user and report activity. v Specify the log messages repository. You can also enable certain logging features. __ v Log on to the z/OS system as a user with administrator privileges on DB2 on z/OS.

Open the LS_tablespace_db2zOS. 2. The name of the tablespace that contains the base tables in the logging database. This tablespace is not for Auxiliary tables. but may be added in the future. 4. The name of the 8 k buffer pool that is allocated for regular objects. 3. The name of the storage group. Go to the c10_location/configuration/schemas/logging/db2zos directory. Connect to the database as a user with privileges to create and drop tablespaces and to allow execution of SQL statements.__ v Ensure that you allocate a buffer pool with a page size of 8 KB for the database instance. IPFSCRIPT_BP IPFSCRIPT_USERNAME Not all of the parameters listed are in the script. Save and run the script. IPFSCRIPT_LS_ID The instance identifier for the audit database. administrators must run a tablespace script to create tablespaces to hold large objects and other data for the logging database. Chapter 9. all names of parameters must start with a letter and the length must not exceed 6 characters. For information about running the tablespace script.” Create tablespaces for a logging database on DB2 on z/OS If you are using DB2 on z/OS. 5. Ensure that you use the name convention for DB2 on z/OS. Grant the IBM Cognos user rights to the tablespaces that were created when you ran the script file: v Open the LS_rightsGrant_db2zOS.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. Tablespace parameter names and descriptions for a logging database on DB2 on z/OS Parameter Name IPFSCRIPT_DATABASE IPFSCRIPT_STOGROUP IPFSCRIPT_TABLESPACE Description The name of the logging database. see the IBM DB2 Information Center. The user account that accesses the logging database. Procedure 1. Configuration options 263 . see “Create tablespaces for a logging database on DB2 on z/OS. For more information. Table 60. a database administrator must run a script to create a set of tablespaces required for the logging database. __ v For a logging database on DB2 on z/OS. and then grant user rights to the table. v Replace the parameter values with those that are appropriate for your environment. For example. This value must not be longer than two characters.sql script file. The script must be modified to replace the placeholder parameters with ones that are appropriate for your environment.

Informix Dynamic Server. Sybase.1 fix pack 5 or version 9.5 fix pack 2. use db2jcc_license_cisuz. DB2. If you are connecting to DB2 on z/OS.jar com.jar file is installed to the appropriate location by default. For DB2 on z/OS. additional steps are required to set up the database client if you use Oracle. Microsoft SQL Server If you use a Microsoft SQL Server database. Results The logging database is created.Tip: Ensure you use the same values that you used when you created the buffer pools and user account.DB2Jcc -version 264 IBM Cognos Business Intelligence Version 10.1 fix pack. For Oracle.jcc.db2. the JSQLConnect. or Windows version 9. Set up database connectivity for a DB2 logging 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. run the following command: java -cp path\db2jcc. which then sends messages to the logging database. Tip: To check the driver version. You cannot use Cognos Content Database as a logging database. the local log server on an Application Tier Component computer may send log messages to a remote log server. The only additional step is to ensure that the Microsoft SQL Server uses TCP/IP connectivity.42 for a Linux. UNIX. or Sybase as the database server. Database connectivity for the logging database After you create a database for audit logs. You must set up the JDBC driver on the Content Manager computer. Procedure Copy the following files from DB2_installation\sqllib\java directory to the c10_location\webapps\p2pd\WEB-INF\lib directory: v The universal driver file.jar. UNIX. unless you are using the same type of database for the log messages as you use for the content store.5 fix pack 2. use the driver version from Linux.2. the appropriate JDBC driver and/or database client software is required only on the Application Tier Components computer with the remote log server that connects to the logging database.jar.ibm.7 for a Linux or UNIX operating system. or for a Microsoft Windows operating system version 9. v Save and run the LS_rightsGrant_db2zOS. and DB2. or JCC 3.jar v The license file: For DB2 on Linux. The driver version must be at least JCC 3. or for a Microsoft Windows operating system version 9. use db2jcc_license_cu.sql script. UNIX operating system.1: Installation and Configuration Guide . In a distributed environment. or Windows operating systems. db2jcc.

On the computer where Sybase is installed. Set up database connectivity for an Informix logging 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.jar file to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed and where notification is sent to a Sybase database. unless you are using the same type of database for the log messages as you use for the content store. You can specify one or more repositories where the local log server sends log messages. you must have ojdbc5. 2. go to the Sybase_location/ jConnect-6/classes directory. unless you are using the same type of database for the log messages as you use for the content store. Configuration options 265 . Procedure 1. unless you are using the same type of database for the log messages as you use for the content store. Log message repositories A local log server is automatically installed when you install Content Manager or the Application Tier Components. Copy the correct library file for your version of the Oracle client to the c10_location\webapps\p2pd\WEB-INF\lib directory on the computer where Content Manager is installed and where notification is sent to an Oracle database. go to the Informix_location/ sqllib/java directory.jar. 2. The files are available from an Oracle client or server install. db2jcc.jar. db2jcc_license_cisuz.jar Set up database connectivity for a Sybase logging database You must set up the JDBC driver on all Application Tier Components computers with a connection to the logging database. go to the ORACLE_HOME/jdbc/lib directory. you must have ojdbc14. On the computer where the Oracle client is installed. and can also be downloaded from the Oracle technology Web site. Copy the following files to the c10_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed. Procedure 1. v the universal driver file. On the computer where Informix is installed. If you are using Oracle 10g.Set up database connectivity for an Oracle logging database You must set up the JDBC driver on all Application Tier Components computers with a connection to the logging database. Chapter 9. Procedure 1. You must also set up the JDBC driver on the Content Manager computer. You must also set up the JDBC driver on the Content Manager computer. 2. If you are using Oracle 11g. Copy the jconn3.jar v the license file.

If this folder does not exist. You can also configure more than one repository for log messages. it is created automatically. Linux. you can configure the log server on each IBM Cognos computer to send log messages to a single remote 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. an automatic recovery process moves all log information to the remote log server and deletes the local log files. When the remote log server becomes available. IBM Cognos components create the required tables and table fields. IBM Cognos attempts to automatically create the cognos. Saving log messages to a file The log server is configured by default to send log messages to the c10_location/logs/cogserver. and restart the IBM Cognos service. and then configure properties for the specific repository. Audit logs provide information about user and report activity. you must ensure the path to the log file exists before starting the IBM Cognos service. IBM Cognos attempts to automatically create this file on startup. Before you begin Before you specify a database as a repository. in addition to the default log file.2.log file.Sending log messages to a remote log server In a distributed installation. or Windows You can configure a type of repository for the log messages. You can configure the log server to send log messages to a different file. if you configure the log server to send messages to the /usr/lpp/logfiles/cognos. For example. These recovery files have timestamp information in their file names. If the default log file does not exist when the IBM Cognos service starts. You can test the connection to the logging database before you restart the IBM Cognos service. which acts as a common log server. If the remote log server becomes unavailable. Specify the Log Messages Repository for DB2 on UNIX. Saving log messages to a database The log server can also send audit logs to a database on the same or another computer. the default log file is not used as a backup.log file in the /usr/lpp/logfiles folder.1: Installation and Configuration Guide . After you configure IBM Cognos components to send messages to a logging database.log file and no log messages can be recorded in it.log file. If you configure a different log file. The logging database has the same configuration and user account requirements as the content store database. log messages are redirected to recovery files on the local computer in the c10_location/logs/recovery/remote directory. If the location for the configured log file is different from the c10_location/logs directory. ensure that you __ v created the logging database __ v set up the database client 266 IBM Cognos Business Intelligence Version 10. Note that these log messages are not recorded in the default log file. and are not readable like regular log files. Although IBM Cognos automatically creates the default log file even when another log file is configured. IBM Cognos does not create the cognos.

7. type the appropriate values for the mandatory and optional properties. v In the Type list. In the Explorer window. Keep the default value of 10. set the Enable SSL property to True. If the repository is a database. Change the number of threads available to the local log server 4. use the following table to help set the log server properties. type the name of the repository. in the Properties window. click Logging. However. Configuration options 267 . specify the type of database and its properties. In the Properties window. If the Internal dispatcher URI of the repository computer is configured to use SSL. and click New resource > Database. in the Explorer window. If the repository is a file. Table 61. under Environment. if you have a high number of log messages.Procedure 1. TCP is always used for communication between a local log server and a remote log server. 9. In the Name box. For a Microsoft SQL Server database. On the computer where you installed Content Manager or the Application Tier Components. v In the Name box. the risk of losing a local TCP connection is low. start IBM Cognos Configuration. In the Explorer window. in the Properties window. as follows: v Right-click the database name. under Environment. Chapter 9. click the type of repository and then click OK. UDP provides faster communication with a lower risk of lost connections than TCP. and click New resource > Destination. 8. You must later specify the log messages repository when you configure the remote log server. 5. The range is between 1 and 20. Include the port number if you use nondefault ports. Include the instance name if there are multiple instances of Microsoft SQL Server. under Logging. 2. Log server properties Task Use TCP between IBM Cognos components on a computer and its local log server Action Set the Enable TCP property to True. If the repository is a remote log server. in the Properties window. click the type of database and then click OK. type the appropriate values for the mandatory and optional properties. you can choose to use a port number. v In the Properties window. type the appropriate values for the mandatory and optional properties. you can allocate more threads to improve performance. Type the value in the Local log server worker threads property. such as 1433. 3. However. or a named instance as the value for the Database server with port number or instance name property. In the Type list. right-click Logging. type the name of the repository. 6.

right-click Logging and click Test. under Environment. along with the user ID and password. In the Explorer window. and database name. Specify the Log Messages Repository for DB2 on z/OS You can configure a type of repository for the log messages. a connection to the default instance is created. Here is an example: jdbc:JSQLConnect://localhost\\instance1/user=sa/more properties as required v Test the connection to the new database. From the File menu. You can also configure more than one repository for log messages. IBM Cognos components create the required tables and fields in the database that you created. configure and start the remote log server. you can type localhost\instance1. 3. 13.1: Installation and Configuration Guide . use the following table to help set the log server properties. you can use IBM Cognos components to run log reports from the database. click Save. Results If the repository was a remote log server. 268 IBM Cognos Business Intelligence Version 10. From the File menu. If the repository was a database. Then restart the IBM Cognos service on the local computer. Procedure 1. see the IBM Cognos Business Intelligence Administration and Security Guide. 11. IBM Cognos components connect to the database. Note that the properties specified for the named instance. click Logging. To connect to a named instance. which controls the amount of detail and type of messages that are sent to a log file or database. You can also set the logging level. IBM Cognos components test all the databases. click IBM Cognos services > IBM Cognos. Repeat steps 5 to 10 for each repository to which you want the log server to send messages. For example. In the Explorer window. start IBM Cognos Configuration. In the Explorer window. For instructions. are used to create a JDBC URL. 12. In the Properties window. you must specify the instance name as a JDBC URL property or a data source property. click Restart.10. On the computer where you installed Content Manager or the Application Tier Components. and then configure properties for the specific repository. If no instance name property is specified. If you selected a database as the repository. 2. under Environment.2. If you configured more than one database for logging messages.

In the Name box. Test the connection to the new database. In the Type list. 14.Table 62. In the Type list. 4. Click Add. In the Properties window. right-click Logging and click Test. 5. you can allocate more threads to improve performance. In the Explorer window. 6. click Local Configuration. Configuration parameter names and values Parameter Name IPFSCRIPT_CREATE_IN Value The base tables location. click Save. Chapter 9.baseTablespaceName IPFSCRIPT_STOGROUP IPFSCRIPT_DATABASE IPFSCRIPT_LS_ID The name of the storage group. type the name of the repository. box. under Logging. and the z/OS Database name. UDP provides faster communication with a lower risk of lost connections than TCP. type the Database server and port number. and click New resource > Database. 12.sql script file “Create tablespaces for a logging database on DB2 on z/OS” on page 263. TCP is used for communication between a local log server and a remote log server. click Database and then click OK. The instance identifier for the audit database. This value must not be longer than two characters. Log server properties Task Use TCP between IBM Cognos components on a computer and its local log server Action Set the Enable TCP property to True. From the File menu. type the name of the repository. 7. databaseName. click inside the Value . In the Explorer window. and then click the edit icon 13. 15. User ID and password. For example. The range is between 1 and 20. Keep the default value of 10. under Environment. next to Advanced properties. 9. The name of logging database. 10. and click New resource > Destination. Ensure that the User ID is the same as the value you specified for the IPFSCRIPT_USERNAME parameter in the LS_tablespace_db2zOS. 8. In the Explorer window. In the Explorer window. 11. right-click the database name. under Environment. and then add the configuration parameter names and values from the following table: Table 63. In the Name box. Change the number of threads available to the local log server Type the value in the Local log server worker threads property. However. click DB2 database and then click OK. Configuration options 269 . if you have a high number of log messages. right-click Logging. In the Properties window.

In the Properties window. create the advanced property IPFSCRIPTIDX and specify the account under which the instance runs: v In the Explorer window. click Local Configuration. if you have a high number of log messages. v In the Name column. right-click Logging. Specify the Log Messages Repository for Informix You can configure a type of repository for the log messages. 9. In the Explorer window. type IPFSCRIPTIDX 270 IBM Cognos Business Intelligence Version 10. click the Value column for Advanced properties . 4. right-click the database name. User ID and password. If you have multiple instances of an Informix logging database. under Logging. UDP provides faster communication with a lower risk of lost connections than TCP. under Environment. click Database and then click OK.2. In the Properties window. In the Name box. The range is between 1 and 20. In the Explorer window. and click New resource > Destination. In the Type list. Keep the default value of 10. use the following table to help set the log server properties. 8. type the values for Database server and port number. v In the Properties window. click Informix Dynamic Server database and then click OK.IBM Cognos components connect to the database. Table 64. 10. However. Log server properties Task Use TCP between IBM Cognos components on a computer and its local log server Action Set the Enable TCP property to True. under Environment. If you configured more than one database for logging messages. and click New resource > Database. you can allocate more threads to improve performance. TCP is used for communication between a local log server and a remote log server. In the Name box. IBM Cognos components test all the databases. 2.1: Installation and Configuration Guide .Advanced properties dialog box. type the name of the repository. In the Type list. and then configure properties for the specific repository. click Add. In the Explorer window. and Database name. Change the number of threads available to the local log server Type the value in the Local log server worker threads property. You can also configure more than one repository for log messages. 7. Procedure 1. 6. type the name of the repository. and then click the edit icon v In the Value . 5. click Logging. 3.

In the Explorer window. 4. Configuration options 271 . Configure JMX Connection Information using IBM Cognos Configuration You configure Java Management Extensions (JMX) connection information in IBM Cognos Configuration by specifying a cookie value and then setting the JMX port and credentials. To enable user-specific logging. under Environment. Chapter 9. using the port specified in External JMX port. start IBM Cognos Configuration. see the topic about using logging to diagnose a problem for a specific user in the IBM Cognos Business Intelligence Administration and Security Guide. After enabling user-specific logging for IBM Cognos components. You must install Oracle Java SE Development Kit or Java Software Development Kit for IBM before you can enable user-specific logging. After you complete the diagnosis. Enabling User-specific Logging When diagnosing problems. you can temporarily set logging to track one or more specific users instead of all users at once. Test the connection to the new database. type an available port number. Use a different user account for each instance of Informix logging database. v Repeat in every instance of IBM Cognos Configuration that uses an instance of an Informix logging database. Save the configuration. IBM Cognos components test all the databases. On the computer where Content Manager is installed. Then you configure JMX connection information in a deployment properties file. In the Explorer window. configure the JMX properties under Dispatcher Settings: v For External JMX port. right-click Logging and click Test. click Environment. click Save. v For External JMX credential. In the Properties window. From the File menu. The user ID and password ensure that only an authorized user can connect to the Java environment to specify the user or users to be logged. type the user ID of the account under which the instance of the logging database runs. IBM Cognos components connect to the database. 12. click the edit icon type a user ID and password. enable logging for a specific user by using the Remote Process service for JMX. If you configured more than one database for logging messages. For information. you can resume normal logging. 11. in the Value column. you use IBM Cognos Configuration to configure connection information for Java Management Extensions (JMX) a technology that supplies tools to manage and monitor applications and service-oriented networks. Procedure 1. and then click OK. 2.v In the Value column. 3.

open the p2pd.properties file located at c10_location/webapps/p2pd/WEB-INF.Configure JMX Connection Information in a Deployment Properties File To support the Java Management Extensions (JMX) settings on your application server. Changing Global Settings By default. That means that all expanded locales conform to a language and regional code setting.deploy_defaults. you must make the same changes on the other Content Manager computers. specify the JMX port in the p2pd deployment properties file. 272 IBM Cognos Business Intelligence Version 10. Results IBM Cognos now supports logging for one or more specific users. you can remove the language from the list.deploy_defaults.2. which may come from different sources and in various formats. Each computer has a default system locale and one user locale per user. For more information.1: Installation and Configuration Guide . If you change global settings on one Content Manager computer. 4. Procedure 1. In a text editor. If you change the user interface language of the product. Restart the services for IBM Cognos. The user locales may be different from the default system locale.properties file. You change global settings v to customize language support for the user interface v v v v v v v v to customize currency support to customize content locale support to to to to to to map the language used in the product user interface map content locales add fonts to your IBM Cognos environment customize the default time zone change the encoding for email messages customize cookie settings Customize Language Support to the User Interface Use the Product Locales table to add or remove the user interface language support. IBM Cognos components ensure that all locales. see the topic about using logging to diagnose a problem for a specific user in the IBM Cognos Business Intelligence Administration and Security Guide. see “Installing translated product documentation” on page 212. For example. Uncomment the rmiregistryport line and set the value to the External JMX port that you configured in IBM Cognos Configuration. 3. If you want users to see product documentation in a language other than English. you must install the Supplementary Language Documentation. data is not affected. For more information. if you do not require a German user interface. use a normalized form. 2. Save the p2pd.

7. you must configure support so that Japanese Yan and Korean Won characters display correctly. Currencies are identified by their ISO 4217 currency code. Customizing Currency Support If you require additional currencies or want to remove some from the user interface. From the Actions menu. 8. you must install the additional fonts from the Supplementary Language Documentation disk. 2. In addition. you can update the list of supported currencies in the Currencies table.xml file in the c10_location/bin directory.Before you begin Ensure that you install the appropriate fonts to support the character sets and currency symbols you use. Add Currencies to the User Interface You can add supported or unsupported currencies to the user interface. you must install a font that contains that character. type the language portion of a locale. you must install the additional fonts from the Supplementary Language Documentation disk. start IBM Cognos Configuration. All supported locales are displayed. Repeat steps 3 to 5 for other language support that you want to add. In the second column. From the File menu. Click the Product Locales tab. Click Add. Ensure that you install the appropriate fonts to support the currency symbols you use. select the check box next to the Supported Locale and then click Remove. to display the Indian currency symbol (rupee) correctly. start IBM Cognos Configuration. you must manually add it to the i18n_res. Adding currencies to the IBM Cognos environment does not guarantee that your computer has a font with the required characters to display the currency. If you add a currency code that is not supported by IBM Cognos. For example. The complete list of supported currencies that can be added are listed in the i18n_res. Procedure 1. 5. On each Content Manager computer. On each Content Manager computer. For Japanese and Korean currency symbols to appear correctly. Tip: To remove support. If you use Japanese or Korean currencies. By default IBM Cognos components show only a subset of supported currencies in the user interface.xml file in the c10_location/bin directory. click Edit Global Configuration. Procedure 1. Copy this file to each IBM Cognos computer in your installation. Chapter 9. You add unsupported currencies to the i18n_res. You add supported currencies in IBM Cognos Configuration. 3. 3.xml file that is provided in IBM Cognos. Configuration options 273 . Click the Currencies tab. 6. 2. for Japanese and Korean currency symbols to appear correctly. 4. click Edit Global Configuration. click Save. Click OK. From the Actions menu.

click Save. 6. For Japanese and Korean currency symbols to appear correctly. 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. All supported locales are displayed. Click the Content Locales tab. By default. you must install the additional fonts from the Supplementary Language Documentation disk. Usually the value you add is a three-letter alphabetic code. 274 IBM Cognos Business Intelligence Version 10. 7. Ensure that you install the appropriate fonts to support the character sets and currency symbols you use.4.1: Installation and Configuration Guide . 2. v To add language support for report data and metadata. type an appropriate value. From the Actions menu. data or metadata in their preferred language. select the check box next to the supported item and then click Remove. 7. select the check box next to the supported item and then click Remove. Repeat steps 3 to 5 for other types of support that you want to add. In the second column. 6. you can add partial locales (language) or complete locales (language-region) to the Content Locales table. The first two characters are letters representing the ISO 3166 country or region code for the country or region the currency is from. click Edit Global Configuration. content locale overrides product locale in the portal for some content. Click Add. you can remove it from the list. In the second column. 4. 5. digits are not supported. Procedure 1. Repeat steps 3 to 5 for each additional locale that you want to support. This way. 5. From the File menu. type a complete locale (language-region) setting. start IBM Cognos Configuration. or specific to their region. Tip: To remove support. Tip: To remove support. v To add support specific to a region. or in different locales. The additional letter represents the first letter of the currency. You must leave at least one content locale in the list for the Application Tier Components to operate. The value you add must comply with ISO 4217 codes for the representation of currencies and formats. Click Add. From the File menu. type an appropriate value.2. it is rendered to users based on their user locale. On each Content Manager computer. Before you begin If a locale is not required. click Save. type a partial local (language) setting. 3. if content is available in different languages. If you view reports in Thai language. Customize content locale support To ensure users see reports.

or French France (fr-fr). Because the user's locale is fr-ca. not fr. for example Vietnamese. You can also map a user's preferred language to another language if content is not available in the user's preferred language. The user will see the report in the locale setting that IBM Cognos chooses. English United States (en-us). For example. Therefore. such as English Canada (en-ca). Next. such as French (fr). such as en-us (English-United States) and fr-fr (French-France). This way. IBM Cognos 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 maps the user's locale to a normalized locale configured on the Content Locale Mapping tab. In this case. 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). First. in a multilingual database. IBM Cognos uses the mapped value to see if the report is available in fr. but is available in French and German. For example. IBM Cognos maps each locale to en. 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. Example 1 A report is available in Content Manager in two locales. By default. Configuration options 275 . IBM Cognos chooses which locale to use. rather than being available in different locales. en-us becomes en and fr-fr becomes fr. Spanish (es) and English (en). IBM Cognos uses the locale mapping to determine which report the user sees. you can use the Content Mappings table to map the preferred language (Vietnamese) to another language (French or German). the user having the user locale fr-ca will see the report saved with the locale fr-fr. but the user locale is set to fr-ca (French-Canadian). the report is available in en-us and fr-fr. For example. if a report or scorecard is not available in a preferred language. Example 2 The user's locale and the report locales all map to the same language. Because both report and the user locale maps to fr. you see the report or scorecard in the mapped language. it is mapped to fr. The following examples show the method that IBM Cognos components use to determine which report or scorecard the user sees if the multiple language versions are available. IBM Cognos maps each of the available reports to a normalized locale. Chapter 9. data is usually available in different languages. the Content Locale Mappings table includes locales that do not contain the region.Content Locales Use the Content Locale Mappings table to map user locales to a complete (language-region) or partial (language) locale.

you may want to configure a mapping. For example. By default. in the Locale Mapping box. 276 IBM Cognos Business Intelligence Version 10. followed by a dash (-) and an asterisk (*). Repeat steps 3 to 5 for other mappings you want to do. Click Add. 3. 7. if a report is available in en-us (English-United States) and fr-fr (French-France). You can also map a user's preferred language to another language if content is not available in the user's preferred language. You can ensure that all regions for a locale use the same language. For example. type de* in the Key box and type in the Locale Mapping box. From the File menu. click Save. type the language portion of the locale.1: Installation and Configuration Guide . type fr-* v To ensure a user locale (language-region) sees content in a specific language. type the user locale: v To ensure all regions for a user locale see content in a specific language. 5. 6. Procedure 1. Map Content Locales Use the Content Locale Mappings table to map user locales to a complete (language-region) or partial (language) locale. In the Key box. Click the Content Locale Mapping tab. 4. the user sees the product interface in the language that matches the language setting of the user locale. click Edit Global Configuration. type the language portion of the locale.2. if you want all the German keys to use the German locale. 2. For example. type the locale.Example 3 The report and the user locales do not map to a common language. For example. start IBM Cognos Configuration. complete locale (language-region) uses a particular language. type the complete locale. 8. type fr-ch v To map a preferred language to another language. In this case. or that a specific. but the user locale is es-es (Spanish-Spain). type zh Tip: To specify the locale to use for a range of keys. IBM Cognos chooses the language. 9. use the wildcard character (*) with the Key value and then. On each Content Manager computer. From the Actions menu. For example. In the Locale Mapping box. Click OK. User locales specified in the Key box will see content in this language. 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. type the preferred language portion of the locale. IBM Cognos chooses the language.

type the preferred language portion of the locale. From the Actions menu. 7. 3. Click the Product Locale Mappings tab. you can view the list of acceptable time zones by opening IBM Cognos Configuration on the Windows computer where Framework Manager is installed. 3. click Edit Global Configuration. click the General tab. use the wildcard character (*) for the Key value and then. From the File menu. type the language portion of the locale. in the Locale Mapping box type the locale. type es-es v To map a preferred language to another language. 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. 4. For example. see the IBM Cognos Business Intelligence Administration and Security Guide. 2. click Save. type zh Tip: To specify which locale to use as the default. users in IBM Cognos Connection use this time zone if they set their preferences for the default time zone. User locales specified in the Key box will see content in this language. All scheduled activities in IBM Cognos are set using this time zone. For more information about setting user preferences in IBM Cognos Connection. Repeat steps 3 to 5 for other mappings you want to do. start IBM Cognos Configuration. In the Locale Mapping box. Click Add.Procedure 1. Content Manager is configured to use the time zone of your operating system by default. In the Global Configuration window. 2. From the Actions menu. Procedure 1. Click OK. 6. click Edit Global Configuration. In the Key box. For example. type the language portion of the locale. In addition. 5. On each Content Manager computer. For example. type the complete locale. Start IBM Cognos Configuration. For UNIX installations that do not support a Java-based graphical user interface. 8. 9. type the user locale: v To ensure all regions for a locale see the user interface in a specific language. 4. type es-* v To ensure a complete locale (language-region) see the user interface in a specific language. 5. Chapter 9. click Save. From the File menu. followed by a dash (-) and an asterisk (*). Click the Value column for Server time zone and select another time zone from the list. Configuration options 277 .

Shift-JIS). you can change the email encoding to a value that works on all your email clients (for example.2.Encoding for Email Messages By default. click the General tab. In the Global Configuration window. 2. From the Actions menu. 278 IBM Cognos Business Intelligence Version 10. Start IBM Cognos Configuration. attachment names. Procedure 1. IBM Cognos components use UTF-8 encoding in emails. If so. The encoding values are shown in the following table: Table 65. This value sets the default encoding used by the delivery service in this instance for all email messages. Supported encoding values Character set UTF-8 Western European (ISO 8859-1) Western European (ISO 8859-15) Western European (Windows-1252) Central and Eastern European(ISO 8859-2) Central and Eastern European (Windows-1250) Cyrillic (ISO 8859-5) Cyrillic (Windows-1251) Turkish (ISO 8859-9) Turkish (Windows-1254) Greek (ISO 8859-7) Greek (Windows-1253) Japanese (EUC-JP) Japanese (ISO-2022-JP) Japanese (Shift-JIS) Traditional Chinese (Big5) Simplified Chinese (GB-2312) Korean (EUC-KR) Korean (ISO 2022-KR) Korean (KSC-5601) Thai (Windows-874) Thai (TIS-620) Supported encoding value utf-8 iso-8859-1 iso-8859-15 windows-1252 iso-8859-2 windows-1250 iso-8859-5 windows-1251 iso-8859-9 windows-1254 iso-8859-7 windows-1253 euc-jp iso-2202-jp shift_jis big5 gb2312 euc-kr ISO 2022-KR ksc_5601 windows-874 tis-620 Change Encoding for Email Messages You can change the email encoding to a value that works on all your email clients. You may have older email clients or send email from IBM Cognos to cell phones and PDAs that do not recognize UTF-8. 3. The specified encoding affects the entire message. including the subject. attachments. and plain or HTML body text. Each instance of IBM Cognos that has an available delivery service must be changed. ISO-8859-1. click Edit Global Configuration.1: Installation and Configuration Guide .

4. and IBM Cognos components then cannot set cookies. Customize Cookie Settings Use IBM Cognos Configuration to customize the cookie domain.org .net.name1. 4. 5. path. Click the General tab. To set the correct value for the cookie domain. . The usual symptom of this problem is that users are repeatedly prompted to log on. In most network configurations.suffix (three dots) Example: .mil. see the IBM Cognos Business Intelligence Administration and Security Guide. use the format and value that represents the widest coverage for the host. Cookie settings Host computer or server Format for domain computer or server name (no dots) Example: mycompany suffix is .nz Additionally. configure the cookie domain. you may need to modify the settings that IBM Cognos components use to create cookies. You can use IBM Cognos Configuration to customize the cookie domain. 3. click Edit Global Configuration. path. Scroll to the desired setting and click it.co. . Table 66.com.name.gov. 6. . click Save. Cookie Settings Based on the requirements of your IBM Cognos environment. . HTTP requests pass through intermediaries such as proxy servers and firewalls as they travel from the browser to IBM Cognos components. Click the Value column for the Email Encoding property. To avoid this problem. and secure flag. IBM Cognos components determine the cookie domain from the HTTP request submitted by the client. and secure flag. or . Click in the Value column under Cookie Settings for each property that you want to change and specify the new value. for security.com other . Some intermediaries modify the information that IBM Cognos components use to calculate the cookie domain. For more information about this attribute. administrators can set the HTTPOnly attribute to block scripts from reading or manipulating the CAM passport cookie during a user's session with their web browser. On each Content Manager computer. Procedure 1. From the File menu. Chapter 9. Configuration options 279 .suffix (two dots) Example: .travelinfo.int.mycompany. 2. which is typically a Web browser. start IBM Cognos Configuration. as listed in the following table.edu.name2. From the Actions menu. .

0. click Save. However. all outgoing IBM Cognos 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. the dispatcher derives the domain from the host name of the request. Change the IP Address Version IBM Cognos supports two IP address versions: IPv4 and IPv6. click Environment. 4. 2. Procedure 1. all outgoing IBM Cognos connections on that computer are established using IPv4 and the dispatcher accepts only incoming IPv4 connections.168. IPv4 uses 32-bit IP addresses and IPv6 uses 128-bit IP addresses. it has precedence over this setting and communication takes place using IPv4. Close IBM Cognos Configuration. On Windows.If you leave the Domain property blank. 5. 5.2. Setting the IP version Use IBM Cognos Configuration to select the IP version. By default IPv4 is employed. You can specify the option each time you open IBM Cognos Configuration from the command line.1:80 v IPv6: [2001:0db8:0000:0000:0000:148:57ab]:80 In IBM Cognos Configuration. Hostnames specified within a URI are resolved based on the value of the IP Version for Host Name Resolution property. From the File menu. if a URI has been specified with a numeric address. 3. you must start IBM Cognos Configuration with the -ipv6 option. The setting applies only to the computer where it is set. Manually configuring IBM Cognos Configuration to start with the IPv6 option You can manually configure IBM Cognos Configuration to use the IPv6 option by specifying the option in the start command.1: Installation and Configuration Guide . In the Explorer window. For IBM Cognos Configuration to accept IPv6 addresses in the local URI properties. Click OK. Start IBM Cognos Configuration. For example: v IPv4: 192. If you selectUse IPv4 addresses. you can select IPv4 or IPv6 for IBM Cognos communication using the IP Version for Host Name Resolution property. If you select Use IPv6 addresses. you can set the option permanently by adding the option to the Start menu shortcut. 280 IBM Cognos Business Intelligence Version 10. Click the Value box for IP Version for Host Name Resolution and click Use IPv4 addresses or Use IPv6 addresses.

sh -ipv6 3. type "c10_location\bin\cogconfigw. The total number of high-affinity connections that are available for indexing must be equal to the number of CPUs that are available on the servers that host the index update service. 2. as required. Configuring IBM Cognos Configuration to always start with the IPv6 option on Windows You can configure IBM Cognos Configuration to always use the IPv6 option on Microsoft Windows operating systems by setting the option in the Start menu shortcut. __ v Add IBM OmniFind® Enterprise Edition search functionality to IBM Cognos applications. as follows: v On Windows. Properties. __ v Configure scalability for index search. type . you must configure the indexing services and create at least one index. Configuration options 281 . On the Shortcut tab. select Programs > IBM Cognos 10. data collection puts an extra load on the batch report service. you can integrate IBM Cognos content in Google search results. To use index search. and then right-click IBM Cognos Configuration./cogconfig. Edit the URI properties that use IPv6 format. see “IBM Cognos Application Firewall” on page 230. and then from the File menu. If a search result includes a URL. click Save. If you use the Google Search Appliance for enterprise search. Configuring IBM Cognos Index Search Index search capability is included with your IBM Cognos Business Intelligence server product as the default search capability. the URL must be in a trusted domain before users can access it.Procedure 1. type cogconfig. Chapter 9. For more information. From the Start menu. 2. specify the values. plan and scale the batch report services appropriately. __ v Enable the index services for a distributed installation. Important: When an index is created. For more information.bat -ipv6 v On UNIX or Linux. in the Target box. if required. see “Configuring the IBM Cognos OneBox Components” on page 418. __ v Create at least one index.exe -ipv6" 3. Start IBM Cognos Configuration by including the IPv6 option in the command. Click OK. __ v Ensure that any URL that might turn up in a search result is added to the list of valid hosts and domains in IBM Cognos Configuration. Go to the c10_location/bin or the c10_location/bin64 directory. To manage the additional indexing needs. To configure index search. Procedure 1. do the following: __ v Upgrade from a previous version.

xml file to publish the index to third-party search engines. see the Administration and Security Guide. v Save the configuration.2.For more information. copy the card. and any number of instances of index search services. Procedure 1. expand Environment and click IBM Cognos services. After upgrading to IBM Cognos BI.xml file. start IBM Cognos Configuration and do the following: v In the Explorer window. If you refined your index in a previous version of Go! Search. 2. expand Environment and click IBM Cognos services. an IBM Cognos BI installation can host one instance of the index data service. change the values for Index search service enabled and Index update service enabled to False. For each additional instance of the index search service. In a typical distributed IBM Cognos BI installation. start IBM Cognos Configuration and do the following: v In the Explorer window. v In the Properties window. you must migrate these settings to the new IBM Cognos BI version. To achieve specific operational goals such as more robustness or performance. v In the Properties window. change the value for Index data service enabled to False. Enabling and Disabling Index Services in a Distributed Installation Typically.1: Installation and Configuration Guide . one instance of the index update service. For more information. you will find equivalent functionality in IBM Cognos Administration. enable the index services and index update service enabled in the applications tier.xml file. v In the Properties window. If prompted to overwrite an existing file. change the values for Index data service enabled and Index update service enabled to False. Take note of any custom settings before deleting the csnconfig. click Yes. On the server where you installed Application Tier Components in the data tier. and the index data service enabled in the data tier. start IBM Cognos Configuration and do the following: v In the Explorer window. v Save the configuration. more complex configurations are possible. 3. 2.xml file from the backup location of your older version to the c10_location\bin\card directory. Upgrading from a Previous Version of Index Search If you are upgrading from a product that used IBM Cognos Go! Search and you modified your card. expand Environment and click IBM Cognos services. On the server where you installed Application Tier Components in the applications tier. Procedure 1. Some versions of IBM Cognos Go! Search included a csnconfig. see the Administration and Security Guide. on the server where you installed additional Application Tier Components in the applications tier. 282 IBM Cognos Business Intelligence Version 10.

On a Microsoft Windows operating system. This configuration is known as index sharing. This applies your changes to all index data service instances within the index search environment. Mapped drives are not supported. 9. All index data services can search all index files.v Save the configuration. you may only activate one instance of the index data service at a time. Chapter 9. We recommend this for most parameters. Configuration options 283 . you can achieve load balancing by introducing new servers that share the same index. Create the root directory for your index search index on one of the servers that is part of the data tier of your IBM Cognos BI deployment. 2. you can deploy multiple instances of the index data service to different servers. delete the default setting and type \\indexsearch\sharedIndex as the value for CSN. add the CSN. v Expand Services and Applications and click Services. For example. When your installation of IBM Cognos BI includes multiple data tier servers. 11. In IBM Cognos Connection. 3. then click Advanced.IndexLocation. shared file locations must be specified using the Universal Naming Convention (UNC). Log on to IBM Cognos Connection as an administrator. Share the directory and make sure that all the servers that host an index data service can access it. 5. v Select Start > Control Panel > Administrative Tools > Computer Management. Because searching is CPU-bound. If the index data service is on a UNIX operating system Network File System (NFS). ensure All is selected. The path is \\indexsearch\sharedIndex. Otherwise. Remove the default path and type the new path to the shared index directory as the value for CSN. make sure that the Windows service for IBM Cognos BI runs under a user that has read and write permissions on that shared file system. For example. v Double-click on the IBM Cognos service that hosts the index data service. 4. Procedure 1. Scaling Index Search by Using Index Sharing To scale search operation. Click the Index Search tab.IndexNFSSupport parameter to the advanced configuration settings list and set the value to true. click Launch > IBM Cognos Administration. If you are using Windows. all instances of the index data service must be identically configured and point to a shared file system. Index sharing allows multiple index data services to search and update a single index that is located on the shared file system within the distributed IBM Cognos BI environment. 10. Click Storage. In the Instances box. Click Save. 7. v Select the Log On tab and specify a domain account that has read and write permissions on the shared file system.IndexLocation parameter. This is the root directory of the shared index. 8. 6. create a directory named sharedIndex on the host "indexsearch".

collaboration-related support is added to IBM Cognos BI as follows: v a link is added to the Cognos Connection Welcome page. If the user has access to the IBM Connections homepage. Users have access to IBM Connections activities from within IBM Cognos Workspace and to the IBM Connections homepage from within IBM Cognos BI and IBM Cognos Workspace. 2. Integration with IBM Connections allows business users to collaborate while creating or viewing reports. Procedure 1. The Collaboration discovery URI specifies the IBM Connections server to use as the collaboration provider. performing analysis.Adding IBM OmniFind Enterprise Edition Search Functionality to IBM Cognos Applications If you plan to use IBM OmniFind Enterprise Edition with IBM Cognos BI.2. 284 IBM Cognos Business Intelligence Version 10. Locate the esapi. see the IBM Cognos Administration and Security Guide. go to the OmniFind_installation_location\lib directory. This allows the user to create or view a workspace activity in IBM Connections.jar and siapi. 2. Click Launch. Adding the IBM Search and Index API is not required if you plan to use IBM OmniFind Yahoo Edition. If the user has access to IBM Connection activities. v a link to the IBM Connections homepage is added to the Launch menu in Cognos Connection v a link to the IBM Connections homepage is added to the Actions menu in IBM Cognos Workspace v the Collaborate menu button is added on the workspace application bar in IBM Cognos Workspace.1: Installation and Configuration Guide . or monitoring workspaces. For more information about integrating IBM Cognos Applications with another search engine. When a URI is specified. the link is named Access my social network and links the user to the homepage. you must add the IBM Search and Index API (esapi. IBM Cognos Administration.jar and siapi. Before you begin IBM OmniFindEnterprise Edition product should already be installed and configured with a searchable collection (index). but not the homepage. On the computer where the IBM OmniFindEnterprise Edition product is installed. the link is named My Activities and links the user to the activities page.jar files) to the IBM Cognos installation. Procedure 1.jar files and copy them into the IBM_Cognos_installation_location\webapps\p2pd\WEB-INF\lib directory on each computer where the index search service is enabled. Start IBM Cognos Connection. Configuring the Collaboration Discovery URI You can configure IBM Cognos Business Intelligence and IBM Cognos Workspace to use IBM Connections for collaborative decision-making.

configuration button. You can grant full access to IBM Cognos Workspace or you can grant access only to the publishing function. Change styles in your reports. configure access to the secured functions and features.ibm. specify the URI as follows: http://server_name:port_number/activities/serviceconfigs For example. IBM Cognos BI must be configured and operating before you can configure access for IBM Cognos Workspace. Chapter 9. Configure IBM Cognos Workspace to access IBM Cognos TM1 Applications. __ v Configure access to IBM Cognos Workspace. Collaboration discovery URI. Use the samples. Additional information about configuring permission for users can be found in a technote (www.3. After the configuration tasks are completed. groups. From the toolbar. On the Configuration tab. Configuring IBM Cognos Workspace IBM Cognos Workspace is included with IBM Cognos BI server. __ v Configure Supported MIME Types in Microsoft Internet Information Services. 4.wss?uid=swg21498402) on the IBM Web site. For the Environment category. It delivers dynamic and customizable features that allow you to quickly and easily assemble interactive workspaces using IBM Cognos content. Click OK. as well as external data sources. grant execute and traverse permissions for the Executive Dashboard capability. http://server_name:9080//activities/serviceconfigs where server_name represents the server name where IBM Connections is installed. 6. click Dispatchers and Services to view the list of dispatchers. you can perform the following tasks as required: __ v __ v __ v __ v __ v __ v Set up a database for annotations. Configure IBM Cognos Workspace to use content from a TM1 Data Server. 7.com/support/docview. users. Click the Settings tab. Granting full access to IBM Cognos Workspace To grant access to IBM Cognos Workspace and all its functionality. After you test that IBM Cognos Workspace is running. Complete the following configuration tasks. Configuring access to IBM Cognos Workspace or its functions Configure access to IBM Cognos Workspace by granting required permissions for the Executive Dashboard capability to specified namespaces. 5. or roles. Configure IBM Cognos Workspace to use metric objects. click the set properties . Configuration options 285 .

and click Properties. To set access permissions explicitly for each entry. select the check boxes to grant permissions for the entry. grant traverse permissions for the Executive Dashboard capability and execute permissions for the Publish Dashboards to Collaboration Spaces secured function. 2. 286 IBM Cognos Business Intelligence Version 10. select the check box for the entry. IBM Cognos Administration. and then select the check boxes next to the users. next to 3. On the Security tab. For search options. 4. 3. Select the Permissions tab. Right-click the local computer name. 7. v To search for entries. Click OK. 5. or roles. click Capabilities. Procedure 1. 8. v To type the name of entries that you want to add. click Search and in the Search string box. In IBM Cognos Connection. For each user group. 9. You can then grant the appropriate permissions for each new entry. click Add and choose how to select entries: v To choose from available entries. Click the actions button Spaces. click the actions button the capability name. or users using the following format. Find and select the Executive Dashboard capability. groups. click the appropriate namespace. click Type and type the names of groups.2. Find and click the entry that you want. Configuring Supported MIME Types in Microsoft Internet Information Services If you use Microsoft Internet Information Services (IIS) 6. Find the Executive Dashboard capability. and then select Set properties. Open the Microsoft IIS management console. click Launch.Procedure 1. and click Set properties.namespace/ role_name. roles. Grant Execute permission to all user groups that should have access to IBM Cognos Workspace. 2.0. Procedure 1. click Edit. click Capabilities. In IBM Cognos Connection. and then click OK. To add new entries to the list. Select the Permissions tab. next to Publish Dashboards to Collaboration 4.1: Installation and Configuration Guide . select the Override the access permissions acquired from the parent entry. On the Security tab. where a semicolon (.namespace/user_name.) separates each entry: namespace/group_name. IBM Cognos Administration. click Launch. 5. and in the box next to the list. 2. Granting access to the publishing function for IBM Cognos Workspace To grant access only to the publishing function within IBM Cognos Workspace. then for IBM Cognos Workspace to load successfully. 6. you must define the MIME type that IBM Cognos Workspace uses. type the phrase you want to search for.

Connect to the database as a user with privileges to create and drop tablespaces and to allow execution of SQL statements. 4.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. you must run the scripts to create the tablespaces. b. 6. Make a backup copy of the HTS_tablespaces. type . see the IBM DB2 Information Center. 2. To create the human tasks tablespaces. Chapter 9. Creating tablespaces for the human task and annotation database on DB2 on z/OS If you are using DB2 on z/OS. Click MIME Types. To avoid waiting. Table 67.sql script file and save the file to another location. 7. Table 68. search the Microsoft online library for Handling MIME Types in Internet Explorer. Configuration options 287 . a. You can use your content store database or a separate database for the human task and annotation database. The script must be modified to replace the placeholder parameters with ones that are appropriate for your environment. Save and run the script. Open the HTS2_CREATE_Db2zos.cfg. Apply the new settings. d. The changes will take effect when the worker process recycles. Click New. Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG Description The name of the database. Specifies name of the 32 k buffer pool. In either case. Tablespace parameter names and descriptions for human tasks on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description Specifies the name of the database. Ensure that you use the name convention for DB2 on z/OS. all names of parameters must start with a letter and the length must not exceed six characters. go to the c10_location/configuration/ schemas/hts/zosdb2 directory.3. Specifies the name of the storage group. For example. For more information. type text/plain. See the script for a complete list of the parameters required. Open the original HTS_TABLESPACES. Procedure 1. In the MIME Type box. a database administrator must run scripts to create the tablespaces required for the human task and annotation database. you can restart the World Wide Web Publishing Service. c. 5. For more information. In the Extension box.

d. For the instance where the Application Tier Components are installed. To create the annotations tablespaces. you must first create the database. 3. Setting up a database for Human Tasks and Annotations By default. you must create the required tablespaces by running two scripts. 288 IBM Cognos Business Intelligence Version 10. Open the ANS2_CREATE_Db2zos. start IBM Cognos Configuration. See the script for a complete list of the parameters required. and then configure the Human Tasks and Annotations feature to use the new database. 4.sql script file and save the file to another location. 3. See the script for a complete list of the parameters required. e.See the script for a complete list of the parameters required. In the Explorer. Procedure 1. the data used for the Human Tasks and Annotations feature in IBM Cognos Workspace is stored in the same database as the content store. Save and run the script. You can configure a separate database for Human Tasks and Annotations. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG DSN8G810 BP32K Description The name of the database.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. Tablespace parameter names and descriptions for annotations on DB2 for z/OS Parameter Name NCCOG Description The name of the database. The name of the 32 k buffer pool. If you are using DB2 on z/OS for your database. For more information. go to the c10_location/configuration/ schemas/ans/zosdb2 directory. 2. Open the original ANN_TABLESPACES. right-click Human Task and Annotation Services and select New resource > Database. Make a backup copy of the ANN_TABLESPACES. Save and run the script. b. c. Table 70. see “Creating tablespaces for the human task and annotation database on DB2 on z/OS” on page 287.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment. The name of the storage group. Create a user account that will be used to operate the database. e. Create a database using the same instructions as “Guidelines for creating the content store” on page 45. a.2. Table 69. create a user account under which the database will operate. To set up the database.1: Installation and Configuration Guide . Save and run the script.

select the type. 8. However. you can access the objects from Metric Studio in your workspaces. you can associate the new reports with the object types by editing the cmm_NOT. a Metric Studio contribution file is provided with IBM Cognos BI server. if required. Perform the following tasks as required to configure IBM Cognos Workspace to use metric objects: __ v Change the reports that are rendered by a metric object. and metric objects are available for IBM Cognos Workspace. Metric objects and the reports rendered from them Object type Metric Metric type Scorecard Strategy Report rendered Metric history graph Metric type data Scorecard metric list Strategy metric list Chapter 9. configure the following: v Specify the mandatory values for all properties that are marked with an asterisk. Changing the report rendered by a metric object If an author has created new reports for a metric package. Repeat these steps on each Application Tier Components and Content Manager instance. v Specify the User ID and password for the account that operates the database. metric types and strategies. Configuration options 289 . In the database resource properties window.properties file. type a name for the database. published metric packages always display in IBM Cognos Workspace. any metric package that exists continues to display in the IBM Cognos Workspace content pane. application content does not appear in the content pane. If your product includes the IBM Cognos Metrics Manager and the metric service is enabled. metric application content appears in the IBM Cognos Workspace content pane. To test the connection to the new database. If your product does not include Metrics Manager. If the contribution file is present. The logon credentials are immediately encrypted. In the New Resource . click Test. 9. Whether the Metric Studio contribution file is present or not. the metric package and all metric reports appear in the content pane. remove the Metric Studio contribution file. click Save. Metric objects in IBM Cognos Workspace By default. as shown in the following table: Table 71. This content includes watchlist. from the Actions menu. Each type of metric object that is dragged into a workspace in IBM Cognos Workspace renders a specific report. scorecards.5. From the File menu. All objects that appear in the content pane can be manipulated in the workspace in the same way that they are manipulated in IBM Cognos Connection. and then click OK.Database dialog box. Otherwise. 6. 7. and attempts to access it will produce an error message. metrics. If the contribution file is not present. __ v Remove the metric contribution atom file. if required.

##cmm. 3. ##cmm.object_id. ##cmm. ##cmm.Table 71.object_id.bux_report. In the ##Default reports for BUX section.scorecard=/folder[@name=’Reports’]/ folder[@name=’Reports’]/report[@name=’Scorecard Metric List’] v For strategy. go to the c10_location\webapps\p2pd\WEB-INF\classes directory. 290 IBM Cognos Business Intelligence Version 10.bux_report.bux_report. For the instance where the Application Tier Components are installed.prompt_param_name. Metric objects and the reports rendered from them (continued) Object type Watch list Report rendered Watch list metric list The reports are created automatically with each metric package. 2. ##cmm.metric=/folder[@name=’Reports’]/ folder[@name=’Reports’]/report[@name=’Metric History Graph’] v For metric type. scorecard=object_id For strategy.properties in a text editor. Uncomment the property by removing the ## symbols.2. do the following: a. find the object type that you want to replace in each report: v For metric. ##cmm.prompt_param_name. metric=object_id For metric type.strategy=/folder[@name=’Reports’]/ folder[@name=’Reports’]/report[@name=’Strategy Metric List’] v For watchlist.object_id. metric_type=object_id For scorecard.properties to cmm. Replace the value in the /report string with the object_id parameter of the new report. find the CMM object_id property for the type of object being replaced: For metric. 7. Open cmm.bux_report.prompt_param_name. 6. v ##cmm. If the new report uses a parameter other than object_id. 4.bux_report. ##cmm. Rename the file cmm_NOT.properties.bux_report.metric_type=/folder[@name=’Reports’]/ folder[@name=’Reports’]/report[@name=’Metric Type Data’] v For scorecard. Replace the values in the /folder strings with the folder names where the new report is located.bux_report. Procedure 1.bux_report.1: Installation and Configuration Guide .watchlist=/folder[@name=’Reports’]/ folder[@name=’Workspace Reports’]/report[@name=’Watch List’] 5.

any metric package continues to appear in the IBM Cognos Workspace content pane. 8. Replace the object_id string with the parameter name that the new report uses. ensure that you use the fully qualified domain names for server name values.object_id. Configuration options 291 . 10. strategy=object_id b. Delete the metric_studio_contribution.mydomain. 9. If you are using a distributed installation. you must use the fully qualified domain names for the server name values in the Environment section of IBM Cognos Configuration. Set connection information for your TM1 Server You must modify a configuration file to set the connection information for your TM1 Servers. To configure the TM1 data server for IBM Cognos Workspace. __ v Optionally. Procedure 1. If the IBM Cognos BI gateway is running on a different computer than TM1 Web. and selecting them in the content pane shows their report content.bux_report. selecting it causes an error message to appear. Restart the IBM Cognos service. you must perform the following tasks: __ v Set connection information for your TM1 Server. Also. c. 3. Repeat steps 4 to 7 for each object type that you wish to replace.##cmm.prompt_param_name. Metric packages then continue to appear. Go to the c10_location/configuration/icd/contributions/contrib directory.atom file. Removing the Metric Studio contribution file If your IBM Cognos BI installation does not include IBM Cognos Metrics Manager. A sample contribution file is provided with in your IBM Cognos BI installation.properties file. 2. use http://mycomputer. For example. Save the cmm. Chapter 9. you must modify configuration files in your IBM Cognos BI installation. you can remove the Metric Studio contribution file from your IBM Cognos BI installation. Uncomment the property by removing the ## symbols. Configuring IBM Cognos Workspace to use IBM Cognos TM1 data To be able to use IBM Cognos TM1 data in IBM Cognos Workspace. However. change the name for the Views folder. such as the TM1WebHost. __ v Set the names of your IBM Cognos TM1 server as they would appear in IBM Cognos Workspace. Restart your IBM Cognos services. the configuration file is available on the computers where you installed the Application Tier Components. To prevent this error message.com/ibmcognos rather than http://mycomputer/ibmcognos.

For a TM1 server that does not use IBM Cognos authentication.Procedure 1. v TM1Toolbar This property determines whether the internal toolbar is visible. 5.atom file in a text editor.2 do not allow for an external toolbar.1: Installation and Configuration Guide . 7. If the TM1 Web directory name is not tm1web. TM1WebHost=TM1WebHostName&amp. replace TM1WebHostName and TM1HostName values with the name or IP address of the TM1 Web server and TM1 data server. v TM1WebVirtualDirectory This property is the name of the virtual directory for the TM1 Web. TM1username=admin&amp. change the following properties: v https This property describes the protocol used for the TM1 Web server. go to the c10_location\configuration\icd\contributions\ contrib directory. The first <atom:entry> section is for a TM1 server that does not use Cognos authentication. If you are defining multiple TM1 server connections. TM1WebVirtualDirectory=planningweb&amp. replace the value of the TM1WebVirtualDirectory property with the correct name. Versions of TM1Web older than version 9. TM1Host=TM1HostName&amp. You must also comment out any extra <atom:entry> sections. For a TM1 server that uses IBM Cognos authentication.sample file as tm1_contribution. The second <atom:entry> section is for a TM1 server that uses Cognos authentication. create a <atom:entry> section for each TM1 server. In the appropriate <atom:entry> section for the authentication required. For example. 292 IBM Cognos Business Intelligence Version 10. On the computer where you installed the IBM Cognos BI Application Tier Components. Open the tm1_contribution. and rename the tm1_contribution. The third <atom:entry> section in the sample file is already commented out. All atom:id values in all . For example. To display the internal toolbar. 2.atom. TM1WebVirtualDirectory=tm1web&amp. replace 0 with 1. You must change the values in one <atom:entry> section for each TM1 server you want to access in IBM Cognos Workspace. For example. If you have more TM1 servers you want to add.2. If you are not using the default values. change the highlighted sections shown for the TM1DataServer value: TM1DataServer=CamAuthenticatedTM1ServerHost 6.TM1pass=apple Replace admin and apple with the user ID and password of the administrator account that is used for the TM1 server. you must add <atom:entry> sections as required. set the value to 1. The default value of TM1Toolbar is 0. change the highlighted sections of the sample.5.atom. If the TM1 Web is running with HTTP secure. change the highlighted sections shown for the TM1DataServer value: TM1DataServer=TM1ServerHostWithoutCAM&amp. The file contains three <atom:entry> sections. 3. 4.atom entries must be unique.

Open the file named tm1_en.com. v Rename the file as tm1_language_code. 2. Chapter 9. Configuration options 293 .atom file in the previous task. go to the c10_location\configuration\icd\contributions\ contrib directory. 10.<atom:entry> <atom:id>tag:ibm. 7.properties file. you can create additional language files to display the names in IBM Cognos Workspace. Restart the IBM Cognos services for the changed to take effect. If your environment supports multiple languages: v Make a copy of the tm1_en. Ensure that you use unique names for values such as tm1_rootfeed_1. rootfeed_title_1.2010-01-01:/tm1_rootfeed_2b </atom:id> The samples are unique because of tm1_rootfeed_2 and tm1_rootfeed_2b. If you use languages other than English.cognos.2010-01-01:/tm1_rootfeed_2 </atom:id> <atom:entry> <atom:id>tag:ibm. change the rootfeed_summary_1 value such as: rootfeed_summary_1 = Detail about MyTM1Server 5. 8. Ensure that you comment out or delete any unused <atom:entry> sections.cognos. Add new values for each TM1 server you added in the tm1_contribution.properties.icd. Save and close the file. For example.icd. 9. you can change the name that is displayed in IBM Cognos Workspace for the Views folder. Change the description in the rootfeed_summary_1 property to give a meaningful description for the TM1 server. Change the name for the Views folder Optionally. A sample French properties file is provided: tm1_fr. change the name to appear as: rootfeed_title_1 = MyTM1Server 4. For example. if you defined a name for your TM1 server connection using rootfeed_title_1. Change the text that appears after the equal (=) sign to provide a meaningful name for the TM1 server defined for the title. where language_code is the two-character code for the language that you are using such as ja or es. Ensure that you match the rootfeed_title and rootfeed_summary sections with the values you defined in the tm1_contribution. you can restart the services after the next task. Procedure 1. if you defined a TM1 server connection using the rootfeed_title_1 section in the tm1_contribution. 3. 6. If you want to change the names of the TM1 servers as they would appear in IBM Cognos Workspace.atom file in the previous task. and rootfeed_summary_1.properties. On the computer where you installed the IBM Cognos BI Application Tier Components. Set the names of your IBM Cognos TM1 server You can define the names of your TM1 servers as they would appear in IBM Cognos Workspace.properties in a text editor. Restart the IBM Cognos services.atom file.com.

These objects pick up the 294 IBM Cognos Business Intelligence Version 10. The name of the Views folder is determined by a messages file that is provided with IBM Cognos Workspace.atom file.gif file to the Cognos BI server portal images folder.1: Installation and Configuration Guide . A sample French translation file is provided: tm1buxmsgs_fr. You can configure the report object appear in the original authored style by changing a global property in the IBM Cognos Viewer configuration file. IBM Cognos TM1 Applications generates a URL. Version 8. Report objects that are affected by the global setting include queries. 3. Changing the style of report objects in IBM Cognos Workspace When you drag a report object onto a workspace. Configure IBM Cognos TM1 Applications for interoperability with the IBM Cognos BI server. Configuring IBM Cognos Workspace to access IBM Cognos TM1 Applications IBM Cognos BI server can access the Web client for IBM Cognos TM1 Applications through an external iwidget that displays in the content pane of IBM Cognos Workspace.x style.By default. Replace the word Views in the following section with an appropriate value: <string id="TM1_VIEWS" type="String" usage="TM1 views">Views</string> 5. analyses. and report parts that were authored using IBM Cognos Version 1. 6. Before the iwidget can display. Repeat the steps for each supported language. IBM Cognos Workspace displays an Applications folder and a Views folder for each TM1 server that is identified in the tm1_contribution. Procedure 1. which the IBM Cognos BI server detects. it appears in the silver and blue gradient style of your product. 2. use the TM1 Applications documentation to perform the following tasks. also copy this file to the c10_location/webcontent/icd/ feeds/images folder.xml file and name it using the appropriate language code.x style. 4. Save and close the new file. When copying the icon_active_application. Install IBM Cognos TM1 Applications.2. 2. 3. Results The TM1 Contributor URL displays under Public Folders in the content pane of IBM Cognos Workspace. Open the new translation file in an XML editor. Deploy your applications. Procedure 1.xml. reports. and financial (balance sheet) style. The name of the Applications folder is returned by the TM1 server. Create a copy of the tm1buxmsgs_en. Go to the c10_location\templates\ps\messages directory.

and the router can test the availability of a server using a test URL. see the IBM Cognos Workspace User Guide. you can configure the router to test the availability of an IBM Cognos dispatcher. For more information about using the samples. Chapter 9. 2.global setting even if you saved them before changing the global setting. You can continue to use these products in the same environment. Business users can access the samples for IBM Cognos Workspace by selecting the option to open existing workspaces and then selecting Samples > Models > Cognos Workspace Samples. change the value for useAuthoredReportStyles to true. Configuration options 295 . 3. Some report objects are not affected by the global setting and will always render in the authored style. see “Install the IBM Cognos Business Intelligence Samples” on page 434 and “Setting up the samples” on page 435. such as PowerPlay reports and report object thumbnails. Additional requirements for access depend on how you choose to run the two products. Configure the Router to Test Dispatcher Availability If you use a router to distribute requests to IBM Cognos dispatchers. 4. For more information about installing and setting up the samples. Procedure Configure the router to use a URL with the path /p2pd/servlet/ping. If the dispatcher is not ready. Save the file and then restart the services. the following response is returned: 200 OK Configuring IBM Cognos BI to Work with Other IBM Cognos Products Some IBM Cognos products provide functionality that is not available in IBM Cognos BI. the following response is returned: 503 Service Unavailable If the dispatcher is ready. Additional configuration tasks may be required to ensure that IBM Cognos BI can access objects that were created using other IBM Cognos products. Workspace thumbnails are affected by the global setting only if you rerun the thumbnail. Open the viewerconfig. Procedure 1. For each Content Manager and Application Tier Components instance.properties file in a text editor. Accessing the IBM Cognos Workspace samples IBM Cognos Workspace samples are included with the IBM Cognos BI samples. To make report objects appear in the original authored style. go to thec10_location/webapps/p2pd/WEB-INF/classes directory.

In the Explorer window. On the Application Tier Components computer. if you install Transformer on a Windows Vista computer. is created. you must update default preferences in the Transformer configuration file. two environment variables are preset for users: one for all users and one for the specific user. On Windows. Contributor Data Server. type the password that will be digitally signed. Results A digital signature. Cognos Planning/Cognos BI . secret password.1: Installation and Configuration Guide .Contributor Data Server/General properties. 2. The password is case-sensitive and must match the Signature password property that you configure in IBM Cognos Series 7. Windows Vista has a security enhancement that restricts multiple users from sharing data locations. 5. You can define environment variables and use them in IBM Cognos Configuration when specifying file locations. and you plan to use the cogtr. which are based on IBM Cognos Planning Contributor data sources. property and then click the edit button 4. click Data Access. In the Properties window. The digital signature is encoded by IBM Cognos BI and decoded by Contributor Data Server. In the Value . IBM Cognos Planning. Procedure 1.xml. based on the password. also include the root directory name of the installation location when you specify file locations in IBM Cognos Configuration. Configuration Manager. This helps to ensure secure communication between IBM Cognos BI servers and Contributor Data Server. In addition. you must change file locations properties in IBM Cognos Configuration so that IBM Cognos can use a single data location for all users.Enable Scheduled Reports and Agents for IBM Cognos Planning Contributor Data Sources To run scheduled reports and agents. click the Value box next to the Signature password when it appears. The default root directory for IBM Cognos is c10. start IBM Cognos Configuration.Signature Password dialog box. 3. File Location Properties on Windows Vista If you install IBM Cognos client components in an environment that includes Windows Vista.samples file as a template. 296 IBM Cognos Business Intelligence Version 10. Because the environment variables represent system root locations. The changes must be made on all computers where IBM Cognos client components are installed. you must specify a shared. From the File menu.2. This allows you to direct applicable files to an area that will be accessible by IBM Cognos users. click Save.

Signing key store location . . 5.Update File Location Properties on Windows Vista You must change file locations properties in IBM Cognos Configuration so that IBM Cognos can use a single data location for all users. with the appropriate environment variable and root directory: v For a single file location per user.Certificate location . Chapter 9. . Procedure 1.Encryption key store location 6. Results The environment variables are resolved when the file locations are accessed during system activities. ". click Save.Data files location . %PUBLIC% For example. 4. The changes must be made on all computers where IBM Cognos client components are installed. %LOCALAPPDATA% v For a single file location for all users on the computer. To set a single file location per user. File. 2. specify the path %LOCALAPPDATA%/ c10/deployment. Repeat step 4 for the following properties: v Under Environment. 3. click Environment. Start IBM Cognos Configuration. In the Properties window.. Replace the relative path element.Log file location v Under Cryptography. Configuration options 297 .". click Deployment files location. . In the Explorer window. From the File menu.Temporary files location v Under Environment. Logging.Map files location . .Common symmetric key store location v Under Cryptography. Cognos.

2.1: Installation and Configuration Guide .298 IBM Cognos Business Intelligence Version 10.

do the following: v Specify the location of the applications. 2005. you must install a separate gateway for each namespace that will be used to authenticate portal users. they must be identical. In a distributed environment. If IBM Cognos components are configured with more than one namespace. You must configure each gateway to use the appropriate namespace and then configure the deployed portlets to use that gateway. and view IBM Cognos reports in your working environment. Other users can view IBM Cognos information without needing to know how to use IBM Cognos products. you must modify some Portal Services property settings and prepare the IBM Cognos environment to support the other portal. Specify the Location of the Applications.xml file as part of a custom application portlet. After you configure the required properties. Portal Services is installed automatically with IBM Cognos components. For more information. The installation includes the deployment files for v SAP Enterprise Portal (SAP EP) v IBM WebSphere Portal v Oracle WebCenter Interaction Portal v SharePoint Portal For some deployments of Portal Services.xml File If you use the applications. When used in another portal. For more information.xml file. Note: The steps are required only if you want to use the Extended Applications portlet.Chapter 10. which is included with the IBM Cognos Business Intelligence software development kit. search. it is included with the Application Tier Components. Configuring Portal Services Portal Services provides a set of IBM Cognos portlets that you can use in IBM Cognos Connection and in other portals. © Copyright IBM Corp. v Install and test the portlets on the other portal. To use Portal Services with IBM Cognos components. You can use the portlets to navigate. if required. see the IBM Cognos Business Intelligence Administration and Security Guide. see the IBM Cognos Business Intelligence Administration and Security Guide. If you have multiple instances of the applications. all Application Tier Components computers in a distributed environment must reference the same applications. you must deploy the Cognos portlets to the other portal. 2013 299 . For more information. see the IBM Cognos Business Intelligence Administration and Security Guide. v Configure security for the other portal environment.xml file.xml file. Portal Services can authenticate users in only one namespace.

ensure that Allow anonymous access is set to False.1: Installation and Configuration Guide . click the Value next to Location of 'applications. 2. use one of the following methods: v Enable single signon for the other portal using shared secret. under Security > Authentication. click Cognos. From the File menu. In the Explorer window. 300 IBM Cognos Business Intelligence Version 10. if necessary. You must configure a URI into IBM Cognos components for each portlet in Portal Services. To enable security between IBM Cognos components and the other portal. you must enable single signon to provide seamless integration between the other portal and IBM Cognos components. see the IBM Cognos Business Intelligence Administration and Security Guide. Disable Anonymous Access to IBM Cognos Components Portal Services uses single signon for authentication. For instructions.2. 5.xml'. Results You can now deploy the IBM Cognos portlets to your portal server. Configuring Security for Portal Services When using Portal Services in another portal. click Save. If Portal Services fails to authenticate a user. Portal Services uses single signon to authenticate users. click Save. On the Application Tier Components computer. click Portal Services. If your security infrastructure requires you to use another method for single signon. you can test the Portal Services connections using anonymous logon to ensure that the portlets are working in the other portal. In the Explorer window. From the File menu. 2. 4. If anonymous logon is enabled in IBM Cognos components. 3. Procedure 1.Procedure 1. 3. This means that users do not have to log on to other applications separately through the portal. 4. Replace localhost with a valid host name or IP address and. Start IBM Cognos Configuration. However. v Configure IBM Cognos components for SSL access. You must ensure that anonymous access is disabled in IBM Cognos components for single signon in Portal Services to be successful. In the Properties window. the user receives an error message at the other portal. under Environment. Portal Services logs all portal users as anonymous. start IBM Cognos Configuration. In the Properties window. replace the default port number. do the following: v Disable anonymous access to IBM Cognos components. if required.

create and configure a Custom Java Provider namespace. change the setting to True. configure a namespace to authenticate portal users. set it to (uid=${environment("REMOTE_USER")}) For SharePoint Portal. Using IBM Cognos Configuration. v For the Namespace ID property. if you deploy the portlets to another portal. 2. In IBM Cognos Configuration."")}) 3. The encryption key is determined by the value of a secret character string shared between the portlets and the custom Java security provider on the IBM Cognos server. specify any new ID. However. configure the following properties: v For the Use external identity property. Configure the Required Namespaces IBM Cognos components must have access to a directory server that contains user IDs for all your portal users."SharePoint_Server\\". Using IBM Cognos Configuration.5. Procedure 1. map the portal user IDs to IBM Cognos Series 7 user IDs using OS signons. Chapter 10. Within the portlets or iViews. you must configure an authentication namespace so that the portal and IBM Cognos components share the same authentication source. set External identity mapping to (uid=${replace(${environment("REMOTE_USER")}. For an LDAP namespace. if SharePoint is on a different machine from the LDAP server. You can use shared secret for the other portal only if portal user IDs can be looked up in an authentication namespace that is shared by IBM Cognos components. The Cognos portlets send a message that contains an encrypted version of the portal user ID. v For the External identity mapping property. You must also create a Custom Java Provider namespace to register the shared secret Java provider that is provided with IBM Cognos components. see the IBM Cognos Series 7 documentation. Configuring Portal Services 301 . In IBM Cognos Configuration. Enable Single Signon Using Shared Secret You can use shared secret for single signon between IBM Cognos portlets and IBM Cognos components. you can configure access to an alternate URI for Portal Services images and Web content. IBM Cognos components must have access to a directory server that contains user IDs for all your portal users. 4. Repeat steps 1 to 4 on all servers where you installed IBM Cognos components. you must link the portlets or iViews to the Custom Java Provider namespace within your respective portal: v v v v Cognos iViews (SAP EP) Cognos Portlet Application (WebSphere Portal) remote server (Oracle WebCenter Interaction Portal) Cognos Web Part (SharePoint Portal) You are not required to configure access to the Portal Services Web content. For an IBM Cognos Series 7 namespace. you must configure an authentication namespace so that the portal and IBM Cognos components share the same authentication source. For more information.

2. click the Value box next to Web Content URI. type com.auth. type the ID of the namespace that you configured in step 1. Tip: The trusted signon namespace acts as an intermediary and must be attached to a real directory-based namespace. under Environment > Portal Services. Procedure 1. This parameter represents the authorization secret that must be shared between the Cognos portlets and the IBM Cognos server.CPSTrustedSignon Java class names are case-sensitive. 6. click Save. type the key to be used for single signon. 4. For the cpsauthsecret: CPS Authorization Secret property. You must use a single word as the key. You must use the same character string when you configure the portlet application. From the File menu. you must link the iViews to the Custom Java Provider namespace within your respective portal. In the Property Category box. Configure the Cognos iViews for SAP EP Within the iViews. Under Environment. In the Explorer window. for Gateway Settings. set the Allow Namespace Override property to true. 2.cps. 7.For example. 8.cognos. start IBM Cognos Configuration. Procedure 1. cpstrusted This new ID must be used in the portlet configuration settings. enter the Custom Java Provider namespace ID. v For Shared Secret. In the Properties window. On the computer where you installed the Application Tier Components. configure the following properties: v For Trusted Signon Namespace ID. For the cps: authentication namespace ID property. Open the iView editor for each Cognos iView. v For the Java class name property. click Save. 5. specify a non-null value. 3.2. Configure Access to the Portal Services Web Content After creating the required namespaces. In IBM Cognos Configuration. 3. select Show All. click Portal Services. you must configure access so that users can access the Web content. 4.1: Installation and Configuration Guide . enter the secret character string that you used for the Shared Secret property when you configured the Custom Java Provider namespace. Specify the host name or IP address of the gateway and a port number using the format host_or_IP_address:port 5. 302 IBM Cognos Business Intelligence Version 10. under Environment. For security reasons. From the File menu. Consider this as a secret password. Restart the IBM Cognos service.

wsdl Configure the Cognos Portlets for WebSphere Portal Within the portlets.16.wsdl Example for a servlet gateway: http://172.wsdl v For Cognos Extended Applications Gateway_URI/wsrp/cps4/portlets/sdk?wsdl&b_action=cps.cgi/wsrp/cps4/portlets/ sdk?wsdl&b_action=cps.0.16.wsdl Chapter 10. For each Cognos portlet application.5. For the CPS Endpoint property.wsdl Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos. enter the URL path to access Portal Services components through the gateway. For the cpsserver: CPS Connection Server property. you must link the portlets to the Custom Java Provider namespace within your respective portal.wsdl v For Cognos Extended Applications Gateway_URI/wsrp/cps4/portlets/sdk?wsdl&b_action=cps. The format of the URL is as follows: v For Cognos content portlets Gateway_URI/wsrp/cps4/portlets/nav?wsdl&b_action=cps.1:9500/wsrp/cps4/portlets/nav?wsdl&b_action=cps.wsdl Example for a servlet gateway: http://172.1:9500/wsrp/cps4/portlets/nav?wsdl&b_action=cps.wsdl v For Metrics Manager Watchlist portlets Gateway_URI/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.0.wsdl Example for a servlet gateway: http://172. The format of the URL is as follows: v For Cognos content portlets Gateway_URI/wsrp/cps4/portlets/nav?wsdl&b_action=cps.0. For the cps_auth_secret property. 4.0. 2.cgi/wsrp/cps4/portlets/ nav?wsdl&b_action=cps.cgi/wsrp/cps4/portlets/ cmm?wsdl&b_action=cps. click the edit value icon. enter the URL path to access Portal Services components through the gateway.1:9500/wsrp/cps4/portlets/sdk?wsdl&b_action=cps. enter the secret character string that you used for the Shared Secret property when you configured the Custom Java Provider namespace.16. Configuring Portal Services 303 .cgi/wsrp/cps4/portlets/ nav?wsdl&b_action=cps.wsdl Example for a servlet gateway: http://172.wsdl Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos.wsdl Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos.1:9500/wsrp/cps4/portlets/cmm?wsdl&b_action=cps. Procedure 1. enter the Custom Java Provider namespace ID.wsdl Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos. 3. For the cps_auth_namespace property.16.

edit the cpsalui.cgi/wsrp/cps4/portlets/ cmm?wsdl&b_action=cps. such as Notepad.dll/wsrp/cps4/portlets/ [package]?wsdl&b_action=cps.2.wsdl Example for a servlet gateway: http://172.cgi/wsrp/cps4/portlets/ sdk?wsdl&b_action=cps. Using a plain ASCII editor.16.1:9500/wsrp/cps4/portlets/cmm?wsdl&b_action=cps. Settings for the cpsalui.0.0.1:9500/wsrp/cps4/portlets/sdk?wsdl&b_action=cps. Leave blank.Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos. Table 72. Procedure 1.16. replace the localhost/ibmcognos/cgi-bin/cognos.1: Installation and Configuration Guide .wsdl Example for a servlet gateway: http://172.wsdl forward_cookies= The names of the cookie that should be sent to the Application Tier Components for single signon. 304 IBM Cognos Business Intelligence Version 10. Configure the settings shown in the following table.wsdl Configure the Remote Server for Oracle WebCenter Interaction Portal Within the portlets. For a servlet or ISAPI gateway.cgi portion with the values to target the gateway. you must link the portlets to the Custom Java Provider namespace within your respective portal. http://host_name/ibmcognos/cgi-bin/ cognosisapi.wsdl v For Metrics Manager Watchlist portlets Gateway_URI/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.wsdl Example for a CGI gateway: http://myserver/ibmcognos/cgi-bin/cognos. For example. Specify the URI to the gateway.properties file in the c10_location/cps/oracle/webapps/gadgets/WEB-INF/classes directory. 2.properties file Parameter cps_endpoint Value The URL to connect to the Application Tier Components and extract the WSDL information.

2. Using a plain ASCII editor. build.sh v On Microsoft Windows operating system. see the administration guide for your application server. Results Single signon is configured. Configuring Portal Services 305 . Go to the c10_location/cps/oracle directory and run the following build file: v On UNIX or Linux operating systems.bat This creates a cps-wci. v Stop IBM Cognos BI. you must link the portlets to the Custom Java Provider namespace within your respective portal.config file in the drive\inetpub\wwwroot\wss\VirtualDirectories\virtual_directory_sharepoint _is_running_under. v Copy the cps-wci. Set cps_auth_namespace to the namespace ID for the Custom Java Provider namespace. such as Notepad. 4. Consider this as a secret password.war file in the c10_location/cps/oracle/gadgets directory. specify a non-null value. Procedure 1. If IBM Cognos BI components are using Tomcat.war file to the application server. edit the web. 4.Table 72. cps_auth_namespace The namespace ID for the Custom Java Provider. Chapter 10. v Start IBM Cognos BI. Settings for the cpsalui. 5.war file to the c10_location/webapps directory. For instructions. If IBM Cognos BI components are running under another type of application server.properties file (continued) Parameter cps_auth_secret Value The shared secret code IBM Cognos uses to encrypt an HTTP header variable that carries the user identity. For security reasons. build. Use the same value that you used for Shared Secret in IBM Cognos Configuration. Set cps_auth_secret to the value that you used for Shared Secret in IBM Cognos Configuration. Find the following string: <SSO cps_auth_namespace="" cps_auth_secret="" /> 3. Tomcat automatically expands the WAR file and starts the remote server. copy the cps-wci. This parameter represents the authorization secret that must be shared between the Cognos portlets and the IBM Cognos server. Configure Properties for the Cognos Web Part for SharePoint Portal Within the portlets. 3.

Enable support for Kerberos authentication in your Firefox web browser. v Create service accounts for the IIS application pool for the web applications. v Set up the Service Principal Names (SPN) for the IIS web server. Sharepoint Portal.Enable single signon with Sharepoint using Kerberos authentication To use the Kerberos protocol for your web applications. and IBM Cognos BI. v Register the Service Principal Names (SPN) for the web applications on the service account that is created for the IIS application pool for the web application. Microsoft Internet Explorer Ensure that the URLs for the web applications are in the intranet zone or a zone that is configured to automatically authenticate with Integrated Windows Authentication. v Disable Kernel-mode authentication. you must configure Internet Information Services (IIS). v Configure Kerberos constrained delegation for service accounts. v Associate the website that is used for Cognos BI with an application pool. Configuration summary for enabling single signon with Sharepoint using Kerberos authentication Software Microsoft Windows server Microsoft Internet Information Services (IIS) Configuration tasks Allow users to be trusted for delegation. v Enable Windows authentication v Enable the Kerberos authentication provider for Windows authentication. your web browser.1: Installation and Configuration Guide . v Ensure that Anonymous authentication is disabled. Table 73.2. Configuration summary Use the following table to help you enable single signon with Sharepoint using Kerberos authentication. and ensure that the application pool is run by a domain service account that has delegation enabled. Firefox Active Directory 306 IBM Cognos Business Intelligence Version 10. Microsoft SQL Server.

or the user account under which SharePoint runs. Configuration summary for enabling single signon with Sharepoint using Kerberos authentication (continued) Software SharePoint web application Configuration tasks To enable Kerberos authentication in SharePoint. IBM Cognos BI v Create an authentication namespace and disable Anonymous Access. For more information about enabling Kerberos authentication in Sharepoint. v Disable Anonymous authentication. About this task By default. Use IBM Cognos Configuration to configure the namespace for Kerberos authentication. and ensure that the domain account has delegation enabled. Configuring Portal Services 307 . v Set the SPN on the SQL server. Microsoft SQL Server v Ensure that services are running using the domain account. v Use SharePoint Central Administration to indicate that Kerberos authentication is used to define how users interact with a network service to gain access to network resources. v Associate the SharePoint site with an application pool. to be trusted for delegation. v Disable Kernel-mode authentication. do not select the Account attribute. the Active Directory provider uses Kerberos delegation and integrates with the Microsoft IIS web server for single signon if integrated authentication (formerly named NT Challenge Response) on a Microsoft Windows operating system is enabled on the IIS web server. Chapter 10. which is sensitive and cannot be delegated. see the Microsoft SharePoint documentation (technet. Configuring IBM Cognos BI to use an Active Directory namespace for Kerberos authentication You can use the Active Directory server as your authentication source and for single signon by using Kerberos delegation.aspx). v Grant users appropriate permissions to the data source.com/enus/library/ee806870.Table 73. you must: v Create SharePoint Server managed accounts and ensure that the domain service account is registered as a managed account. v Set the Service Principal Names (SPN) on the SharePoint server. When you are setting up the computers by using the Active Directory user tool.microsoft. Set up the computers. v Create a data source and secure it against the active namespace. ensure that the application is run by a domain service account.

A data source defines the physical connection to a database. type a name for your authentication namespace. specify a unique identifier for the namespace. 2. under the Authentication component. Test the connection to a new namespace. d. including sign-on. In every location where SharePoint is installed. The new authentication provider resource is displayed in the Explorer window. In the Explorer window. Restriction: Do not use colons (:) in the Namespace ID property. To disable Anonymous authentication. type a unique name for the data source. Procedure 1. In the Name and Description page. Under Signon. 5. complete the following steps: a. In the Explorer window. 6. Creating a Kerberos-enabled data source You can create a data source authenticated by the Kerberos protocol by using IBM Cognos Administration. 308 IBM Cognos Business Intelligence Version 10. select Launch > IBM Cognos Administration. from the Type menu. and click OK. for the NamespaceID property. 3. Namespace. In the Type list. . In IBM Cognos Connection. 6. select Use the default object gateway. and click New resource. select the type of data source that you want to create. under Security. select Data Source Connections. b. and choose the namespace that you created to authenticate users against the Kerberos data source. Specify the values for all other required properties to ensure that IBM Cognos can locate and use your existing authentication provider. open IBM Cognos Configuration. 3. Select the New data source button 4. 4. Click File > Save. In the Connection page.2. see the IBM Cognos Business Intelligence Administration and Security Guide. right-click the new authentication resource and click Test. c. right-click Authentication. 8.Procedure 1. 8. click Active Directory and then click OK. In the Name box. 7. 5. For information about connection parameters for the data source. In the Properties window. click the authentication namespace that you created. Specify the connection parameters for the Microsoft SQL Server data source. On the Configuration tab. In the Explorer window.1: Installation and Configuration Guide . In the Properties window. The credentials that are used to authenticate to the data source are taken from the specified namespace to which the user authenticated previously. ensure that Allow anonymous access is set to False. select An external namespace. Authentication. Under Isolation level. 7. under Authentication. The data source specifies the parameters that are needed to connect to the database. 2. 9. Repeat steps a to c on all web application servers that use Kerberos authentication. Click File > Save. such as Microsoft SQL Server or Microsoft Analysis Services. under Security.

You must map the users logon credentials in the data source to a namespace. ensure that you have v configured IBM Cognos components to use an SAP authentication source v enabled single signon between IBM Cognos components and SAP BW v installed the latest service packs on the SAP BW server Service packs can be downloaded from SAPNET. Chapter 10. you must configure IBM Cognos components with an SAP namespace that links to an SAP BW server.dll and place both files in the /run directory of the SAP BW server. To enable SSO for SAP EP. v installed the latest hot patches for the SAP portal v installed the Enterprise Portal plug-in that corresponds to the SAP EP release or SAP BW server For SAP releases earlier than 6. v installed the SAP Security Library on the SAP BW servers From sapservX. For more information. on SAPNET. you define an IBM Cognos data source in SAP EP. you can see whether the connection was successful. Results The new Kerberos-enabled data source is displayed in the Data Source Connections list on the Configuration tab. Enable Single Signon for SAP EP with User Mapping If you enable single signon with user mapping. Portal Services iViews transmit the logon credentials to IBM Cognos components using HTTP Basic Authentication. Enable Single Signon for SAP EP with the SAP Logon Ticket If you enable single signon with the SAP Logon Ticket. under /general/misc/security/SAPSECU/platform. return to the previous steps. Before you start. You can now use the Cognos iViews in the SAP Enterprise Portal. complete the procedures for single signon with SAP logon tickets in the SAP Enterprise Portal Security Guide. download EP50_PLUG-IN for Basis 620 (SAPKINE32A). install SAPKINE32A. Using transaction SAINT. and can be selected when you are using the Metadata wizard in Framework Manager. If it was unsuccessful.2. click Test the connection.9. Users must have the same user ID in all SAP systems that are accessed through single signon. Configuring Portal Services 309 . download sapsecin and sepsecu. and verify your connection parameters. To test whether the parameters are correct. Individual users or an administrator can enter the user IDs and passwords for IBM Cognos components in the data source. In the Status column. see the Administration and Security Guide. click Close. and then click Test. Then you must copy the certificate that was generated during SAP EP installation to the SAP BW personal security environment.

user v system alias (Create a system alias) For more information. 5. For information about configuring a URL to use HTTP Basic Authentication.c8/systems/Cognos directory: v Logon Method = UIDPW v server name = the name of the IBM Cognos server v v v port number = port number of the gateway Protocol of Target system = HTTP User Mapping Type = admin. Configure the gateway URI that will be used by Portal Services to require authentication using HTTP Basic Authentication. in an attribute called CPS: User Mapping Datasource. you must perform certain tasks in the security environment. In the SAP portal.cognos.pct. Adjust the iView configuration to access the secure URL. see the documentation for your Web server. see the SAP Enterprise Portal Administration Guide. If you use an LDAP namespace. For each Cognos iView. 3. 2. change the setting to True. enable user mapping for the data source by entering the name of the system alias at the iView level. Procedure 1. For each Cognos iView. In IBM Cognos Configuration. see the SAP Enterprise Portal Administration Guide.2.1: Installation and Configuration Guide . see the documentation for the gateway or for your Web server. see the Administration and Security Guide. Register the IBM Cognos credentials for the portal users. see the SAP Enterprise Portal Administration Guide. set it to (uid=${environment("REMOTE_USER")}) Create the Data Source and Map the Users You must set up the logon credentials and define the user mappings for the Cognos iViews. Procedure 1.Prepare the Environment Before you map user logon credentials. 4. configure a namespace to authenticate portal users. Results You can now use the Cognos iViews in the SAP Enterprise Portal. Users can enter their own user IDs and passwords. Enable secure communication between SAP EP and IBM Cognos. v For the External identity mapping property. For more information. ensure that the following properties are configured for the data source in the /PortalContent/other_vendors/every_user/ com. 310 IBM Cognos Business Intelligence Version 10. set the CPS: Authentication Namespace ID property to the namespace that you want to use for authentication. For more information. configure the following properties: v For the Use external identity property. 3. For more information. 4. 2. For information.

configure a namespace to authenticate portal users. Configuring Portal Services 311 . 5. After single signon is set up. For more information. see “Configuring the SSL protocol for IBM Cognos components” on page 257. To use application server single signon. see the Administration and Security Guide. In IBM Cognos Configuration. For information about SSL for IBM Cognos components on a WebSphere Application Server. Install an alternate CGI or ISAPI or servlet gateway in IBM Cognos. In the administration console of the Web server. see the Administration and Security Guide. For more information about Active Credential objects. you can use the IBM Cognos portlets in the WebSphere Portal. LtpaToken. SiteMinderToken. Chapter 10.properties file in the c10_location/cps/oracle/webapps/ gadgets/WEB-INF/classes directory. using SSL. see the documentation for IBM WebSphere Portal. configure the virtual directories to access the gateway. 2. 4. Enable Single Signon for Oracle WebCenter Interaction Portal Using Basic Authentication You can configure a portlet in WebCenter Interaction Portal to send the username and password as an HTTP Basic authentication header. see the documentation for your Web server. Credentials for the portal user are passed to the gateway using this object. For more information. You can now use the IBM Cognos portlets in the SAP Enterprise Portal. Enable Single Signon for WebSphere Portal Using the Application Server The Portal Services portlets can use the Active Credentials objects provided by WebSphere Portal to connect to IBM Cognos components. Configure the WebCenter Interaction remote server to access IBM Cognos BI: v Edit the cpsalui. Portal Services supports the following Active Credentials objects: HttpBasicAuth. and WebSealToken. The header can be used with an authentication namespace to provide single signon.Enable Secure Communication Between SAP EP and IBM Cognos Components A secure connection. Procedure 1. see the documentation for IBM WebSphere Application Server. is not required between SAP EP and IBM Cognos components. edit properties for the all iViews so that the cpsserver: CPS Connection Server property uses https instead of http. Configure the gateway. 3. For more information. After SSL is enabled. To enable SSL between SAP EP and IBM Cognos components. It is more important if you enabled single signon with user mapping. see your SAP EP security documentation.

wsdl v Set the cps_auth_namespace property to the namespace that you want to use for authentication. For a CGI gateway. you can use the default setting if the gateway and the remote server are on the same computer. WebCenter Interaction Portal sends the CA SiteMinder active authentication token to the remote server. 312 IBM Cognos Business Intelligence Version 10. For a CGI gateway. For a servlet or ISAPI gateway.dll/wsrp/cps4/ portlets/[package]?wsdl&b_action=cps.dll/wsrp/cps4/ portlets/[package]?wsdl&b_action=cps.1: Installation and Configuration Guide . replace the localhost/ibmcognos/cgi-bin/ cognos. which sends the token to the IBM Cognos gateway.v Change the cps_endpoint property to indicate the URL of the gateway. In IBM Cognos Configuration. Procedure 1. you can use the default setting if the gateway and the remote server are on the same computer. you can also use it for single signon with WebCenter Interaction Portal.wsdl v Change the cps_auth_namespace property to the namespace that you want to use for authentication. configure a CA SiteMinder authentication namespace. 2. For instructions. replace the localhost portion with host_name:port For a servlet or ISAPI gateway. see “Configure IBM Cognos components to use CA SiteMinder” on page 360. Enable Single Signon for Oracle WebCenter Interaction Portal Using CA SiteMinder If you use CA SiteMinder to provide single signon in your security infrastructure. Otherwise.cgi portion with the values to target the gateway. v Change the cps_endpoint property to indicate the URL of the gateway. You must configure a CA SiteMinder authentication namespace in IBM Cognos BI. Otherwise. http://host_name:port/ibmcognos/cgi-bin/cognosisapi. replace the localhost portion with host_name:port.cgi portion with the values to target the gateway.properties file in the c10_location/cps/oracle/webapps/ gadgets/WEB-INF/classes directory. For example. replace the localhost/ibmcognos/cgi-bin/ cognos. Configure the remote server to forward the authentication token: v Edit the cpsalui.2. http://host_name:port/ibmcognos/cgi-bin/cognosisapi. v Change the forward_cookies property to include the name of the active authentication token that CA SiteMinder provides. For example.

the archived outputs are not deleted in your external repository. v In Cognos Connection. v Create and run a content archival maintenance task to select folders and packages to archive in the external repository. IBM Cognos content archival Storing archived content in your external repository provides you with the ability to adhere to regulatory compliance requirements. v Create a data source connection to the external repository. Once you set a repository connection for packages and folders. This efficient mechanism allows your company to meet corporate and government requirements while providing a seamless user experience. which means that there is no need to run the content archival maintenance task again. users can make critical comparisons between current data and historical data. This workflow only needs to be completed once since all of your content is currently located in your content store. see the IBM Cognos Business Intelligence Administration and Security Guide. select repository connections for the packages and folders that need to be archived. The first workflow allows administrators archive packages and folders after installing IBM Cognos Content Archival software. Content archival can also be configured to use your file system. you must upgrade this software with fix pack. 2013 313 . Workflow 1: Archiving content after installing connectivity software Administrators can archive saved report output for specific packages and folders or all packages and folders after installing or upgrading IBM Cognos Business Intelligence. 2005. The content archived in the external repository is not managed in IBM Cognos environment.Chapter 11. If you already have IBM Filenet CMIS version 1 of the software installed. version 2. The software supports an IBM FileNet Content Manager with IBM FileNet CMIS external repository. By providing search results for recent and archived content. if you delete reports in IBM Cognos Connection. and can enhance the scalability and performance of IBM Cognos products by reducing the size of content in the content store. any new report output is automatically archived. There are two workflow scenarios for archiving your content. Administrators create a data source connection to an external repository to allow content to move from the content store to the repository. Users can view the archived content in the external repository from IBM Cognos Connection. © Copyright IBM Corp. For example. The second workflow allows administrators to create repository connections for new packages and folders. For information about administering your archives.

Importing content into a folder or package that is configured for archiving to an external repository does not automatically move and archive the imported content into the repository. for example.xml and deleteTask.xml. there may be situations when you must preserve content IDs. Preserve content IDs before you archive If required.Workflow 2: Creating repository connections for new packages and folders Administrators can create repository connections for new packages and folders by completing these tasks: v Create a data source connection to the external repository. The deleteTask. It is important to note that this task does not move your content from the content store to the external repository. However. You must select repository connections for your packages and folders in IBM Cognos Connection first. Once the content is marked. The archiveTask. the content archival task is complete. A background task in Content Manager finds the marked items and then copies and saves them in the external repository. when moving report output to a external report repository. you can preserve content IDs before report output is archived. Using content archival content maintenance tasks The content archival content maintenance task creates a reference to the report versions in the folders and packages that you select and configure. You can also use this file to set thread execution times and archive outputs of selected formats. For the configuration changes to take effect you must stop and start your IBM Cognos services.2. Report versions in folders and packages that are not marked for archiving are available for deletion from the content store.xml file is a configuration file that retrieves and deletes marked version objects from the queue. select repository connections for the packages and folders that need to be archived.1: Installation and Configuration Guide . An administrator must run a content archival content maintenance task for this folder or package to archive the imported content. Background tasks The background XML tasks used to move content from the content store to the external repository are archiveTask. v In Cognos Connection. Selecting folders and packages marks the content within and allows it to remain in the content store until it is archived in your external repository.xml file moves marked content to an external ECM repository. Objects in the content store have content IDs that are deleted and replaced with new IDs by default when you run an import deployment and move content to a target environment. Configure content archival You must configure your environment for content archival. 314 IBM Cognos Business Intelligence Version 10.

type file:/// followed by the local path. 4./file-system-path. IBM Cognos content archival 315 . type a unique name for your file system repository. see the IBM Cognos Administration and Security Guide. For more information. Click Actions > Edit Global Configuration. Click OK. both the Content Manager and Application Tier Components computers must have access to the file location. for example file://server/share. such as file:///. file:///file-system-path. Type the path to your file system location. Note: There is no limit to the number of aliases you can create. You can install custom classes and properties files at any time. for example. In a distributed installation. Use both URIs only in a distributed installation. in the unixURI column.Creating a file location for a file system repository To archive reports or report specifications to an IBM Cognos content archival file system repository.Alias Roots dialog box appears. file:///c:/file-system-path or type file:// followed by the server name and share path. This might take a few minutes. you must import a set of custom classes and properties files into IBM FileNet Content Manager. 1. Start IBM Cognos Configuration. v On UNIX or Linux. Content Manager and Application Tier Components must be able to access this location by using a file URI. 2. stop the IBM Cognos service. 3. Note: Relative paths. click the edit button. On the General tab. you must create an alias root that points to a file location on a local drive or network share. Before you begin You must be an administrator and have access to the file location.. 7. Restart the IBM Cognos service. 8. click inside the value field. in the windowsURI column. 5. and when the Value . are not supported. Importing custom classes definitions and properties into IBM FileNet Content Manager To use IBM Cognos content archival. Chapter 11. click Add. In the Alias root name column. Custom classes definitions and properties include FileNet specific metadata. type file:/// followed by the local path. where file-system-path is the full path to an existing file location: v On Windows. for example. The UNIX URI and the Windows URI in an alias root must point to the same location on the file system. select Alias Roots. 6. Procedure If running. Results Use this file system repository name to create a data source connection to use with the Cognos content archival software.

Select the CMECMIntegrationObjects_CEExport_Manifest. 5. 4. If FileNet archiving is not already set up. From the main menu. you must import a set of custom classes and properties files. 6.xml files to a local folder on the FileNet server. 8. Select a target Object Store. Open the FileNet Enterprise Manager Administration tool and connect to the domain for the FileNet external repository. click Browse._xxx. 2. As there is no Resource Manager that is defined during the installation process.xml file and click Import. Procedure 1. 316 IBM Cognos Business Intelligence Version 10. Importing custom classes definitions and properties into IBM Content Manager 8 To use IBM Cognos content archival with IBM Content Manager 8. Open the Content Manager 8 System Administration Client. and select the CMECMIntegrationTypes_RMImport_MimeTypes. You must also update the CMIS configuration file with the IBM Cognos folder types. From the Import XML Options window. go to c10_location/configuration/ repository/filenet/upgrade/directory. Note: It might take a long time for changes to be updated across all FileNet nodes. there are conflict error messages during the import process. You can install custom classes and properties files at any time. 3.Procedure 1. Copy the CMECMIntegrationObjects_CEExport. 3. The default location is <c10_location>/configuration/repository/ contentManager8/New directory. and click Import All Items to import the definitions into the object store. click Tools > Import XML. click Import Manifest File and browse to where the CMECMIntegrationObjects_CEExport. Custom classes definitions and properties include IBM Content Manager 8 specific metadata. Restart the FileNet Content Engine and FileNet CMIS application to apply the changes to your environment. click Browse._xxx. 2.xsd file from which you want to import the objects. and select the CMECMIntegrationTypes_RMImport_Manifest. If you have FileNet archiving set up. go to c10_location/configuration/ repository/filenet/new/ directory.xml files are located. v In the Administrative objects file field.xml file to import the Administrative objects file. 7. In the Import Options pane.2.1: Installation and Configuration Guide . Before you begin You must have IBM Content Manager 8 installed with an IBM Content Manager 8 CMIS version 1.1 external repository. File to import section: v In the Data model file field.

Specifying an available time to run the archival process To maintain high system performance during peak hours. restart the CMIS for Content Manager Application. expand Item Types. and click Accept. A blackout period is a temporary period in which the movement of data is denied. For example. Click Import to begin the import process. open the tasksManager. 2.ibm. b. 6. c. under Processing options.htm). click Import. From the Confirm Import Selection window. Note: For more information about manually deploying CMIS. the default file path is: C:\Program Files\IBM\CM_CMIS\ profiles\profile1 a. Run the CMIS for Content Manager 8 configuration program and select the option to redeploy the CMIS configuration file automatically. and double-click an item type that indicates a conflict. To update the CMIS configuration file to detect the IBM Cognos folder types. to 5 p. select Process interactively. Repeat steps a and b for each item type that indicates a conflict. b. Tuesday through Friday. IBM Cognos content archival 317 . 11. By default. After the import is complete. 8. from the Import XML Options window.4.. 10.properties file in the IBM CMIS for Content Manager configuration profiles folder. run the CMIS for Content Manager 8 configuration program to create a profile. you can configure a blackout period to specify when the archive or delete tasks run. in the Resulting Target column.com/ infocenter/cmgmt/v8r4m0/topic/com. add the following <blackoutPeriods> element as a child element of the backgroundTasksManager element. see Manually deploying IBM CMIS for Content Manager (http://pic. For UNIX. click Continue.00 a. For example. To view conflicts. From the WebSphere Application Server administrative console. After you resolve all the conflicts. 9. Using an XML text editor.installingcmcmis. 7.ibm. Save and close the file. 12. 5.doc/ cmsde001. click OK. a. from the Import Preprocessor Results window.REPORTVERSION c. From the Import Preprocessor Results window.xml file. a blackout period is not defined when the software is installed. to specify a weekly blackout period from 8. Go to the c10_location/webapps/p2pd/WEB-INF/cm/tasks/manager directory. Locate the folderTypes line.m.COGNOSSREPORT. 3. Procedure 1. Open the cmpathservice. folderTypes = ClbFolder. select the names for the Resource Manager and Collection created when you installed Content Manager 8. Add the IBM Cognos folders types COGNOSREPORT and REPORTVERSION in uppercase. Separate each folder type by a comma.m.dhe. Chapter 11. the default file path is: /opt/IBM/CM_CMIS/profiles/profile1 For Windows. From the Details of Import Definition and Target Definition window.

v start time = <hour>08</hour> v stop time = <hour>17</hour> v days = <day>Tuesday</day> <day>Wednesday</day> <day>Thursday</day> <day>Friday</day> 4. and all threads that run every day of the week. Procedure 1. add the following <executionPeriods> XML element as a child element of the backgroundTask element. to midnight. The archive and delete background tasks use threads to move content.00 a.00 a. to configure three threads that execute from midnight to 8.m.00 p. If required. 6. Threads are units of processing time that are scheduled by the operating system.m. Specifying thread execution time You can use threads to schedule operating system processing time. Go to the c10_location/webapps/p2pd/WEB-INF/cm/tasks/config directory. open the archiveTask. Using an XML text editor. The maximum number of threads is 7.m. 5. 2. Save and close the file.m.xml file.00 p. Restart background activities on the Content Manager service.. decrease the number of threads available to the archiving and deletion processes.2.. For example. <executionPeriods> <executionPeriod> <threads>3</threads> <startTime> <hour>00</hour> <minute>00</minute> </startTime> <stopTime> <hour>08</hour> <minute>00</minute> </stopTime> <days> <day>Monday</day> <day>Tuesday</day> <day>Wednesday</day> <day>Thursday</day> <day>Friday</day> <day>Saturday</day> <day>Sunday</day> </days> </executionPeriod> <executionPeriod> <startTime> <hour>08</hour> <minute>00</minute> </startTime> <stopTime> <hour>17</hour> <minute>00</minute> </stopTime> <days> <day>Monday</day> <day>Tuesday</day> 318 IBM Cognos Business Intelligence Version 10.1: Installation and Configuration Guide . one thread that executes from 8. no threads that execute from 5. 3. to 5.

queries. Using an XML text editor. Go to the c10_location/webapps/p2pd/WEB-INF/cm/tasks/config directory. see the IBM Cognos Business Intelligence Administration and Security Guide. are archived. Archiving selected formats of report outputs You can limit archiving to limit archiving to specific output formats. analysis. 3.xml file is a configuration file for the background task called deleteTask. For example. XML. which retrieves and deletes marked version objects from the queue. Chapter 11. Report specifications describe how data was generated within a report. for example HTML with graphics. Procedure 1. add the following <outputFormats> XML element as a child element of the runOptions XML element. report specification output is archived. HTML and Excel. 2. <outputFormats> <outputFormat>PDF</outputFormat> </outputFormats> You can use the existing sample outputFormats element and modify the list to specify output formats to be archived. IBM Cognos content archival 319 . By default outputs of any given format. and document objects v Content Removal that marks versions and histories. open the archiveTask. The deleteTask. Specifying that report specifications are not archived By default. Save and close the file.xml file.xml file is located in the c10_location/webapps/p2pd/WEB-INF/cm/ tasks/config directory. You can limit archiving of specific output formats to the repository. Removal of marked version objects from the queue The deleteTask. For more information about retention rules. You cannot selectively archive multiple file report output versions.<day>Wednesday</day> <day>Thursday</day> <day>Friday</day> <day>Saturday</day> <day>Sunday</day> </days> </executionPeriod> </executionPeriods> 4. There are two content maintenance tasks that mark and move version content into a queue: v Retention Rules Updater that updates and applies retention rules on reports. to define the archiving of only PDF report output versions. Save and close the file. including PDF.

Go to the c10_location/webapps/p2pd/WEB-INF/repositories/config directory. 8. Using an XML text editor. For more information. 7.cognos.cm.xml. Go to the c10_location/webapps/p2pd/WEB-INF/repositories/config directory. open the CM. 5.FILENET. 3. you must modify two files: CM. Comment out or remove the following element: <property repositoryName="REPORTEXECUTIONSPECIFICATION" repositoryType="ASSOCIATED" metadataPropertyName="specification"> <associatedObjectTypes> <objectType name="VERSIONSPECIFICATION"> <properties> <property repositoryName="cmis:name" repositoryType="STRING" metadataPropertyName="reportVersionDefaultName" valueHandler="com.xml in a text editor. v If you archive your content to IBM Content Manager 8.xml file. depending on whether you archive your content to an IBM FileNet Content Manager repository or an IBM Content Manager 8 repository. 2. the objectType name value is <objectType name="$t!-2_VERSIONSPECIFICATIONv-1">. and either CM_FILENET.xml.1: Installation and Configuration Guide . Restart background activities on the Content Manager service. Do one of the following steps: v If you archive your content to FileNet. 320 IBM Cognos Business Intelligence Version 10.xml file.2. 6. Comment out or remove the following line: <property name="specifications" metadataPropertyName="specification" useTempFile="true" 4. Save and close the file.xml in a text editor. see the IBM Cognos Business Intelligence Administration and Security Guide.To turn off the archiving of report specifications. PropertyValueAppendStringHandler" valueHandlerArgument="_specification"/> </properties> </objectType> </associatedObjectTypes> </property> Note: In the CM.xml or CM_CM8. open the file named CM. open the file named CM. repositoryPluginFramework. Procedure 1.

ibm. Members of an activity interact in an online location in which they create.com/ldd/ lcwiki.lotus. see the following: v the customer support site (http://www. Activities is a web-based collaboration tool for collecting.com/support/docview. you can quickly pull together the correct people and resources you need to get the job done. Because it is easy to invite new members.5 requires you to have IBM WebSphere Application Server version 6. and create and assign to-do items.0 requirements.5 requirements. you will also have to deploy IBM Cognos BI to IBM WebSphere Application Server.boulder.0.Chapter 12.jsp) v the IBM Connections wiki page (http://www.ibm. An activity is a way for you to organize your work and collaborate with others in a shared web space. collect. IBM Connections is social networking software designed for the workplace.nsf) For more information about IBM Connections version 3. Activities are part of IBM Connections and are integrated with IBM Cognos Workspace. organizing. Using Collaboration with IBM Cognos Workspace Collaboration capabilities in IBM Cognos Workspace provide a bridge between using IBM Cognos Business Intelligence to discover a business problem and acting to resolve it. To use activities with IBM Cognos Workspace.lotus. For more information about IBM Connections version 2. IBM Connections and IBM Cognos BI must be installed on computers in the same domain. rather than using the Apache Tomcat servlet container that is provided with IBM Cognos BI. and reusing work related to a goal. You can post messages.xsp?lookupName=Lotus%20Connections%203 %20documentation&SessionID=CPF70J9VI3) Installation considerations Installing IBM Cognos BI and IBM Connections requires some deployment choices. you must install IBM Connections and configure it to work with IBM Cognos BI. For example.ibm. share files and links to web sites.wss?rs=899 &uid=swg27016547) v the IBM Connections Information Center (http://publib. see the following: v the customer support site (https://www. 2013 321 .1.23 running and to have security enabled on your IBM WebSphere Application Server profile. © Copyright IBM Corp. To allow single signon between IBM Cognos BI and IBM Connections. IBM Connections version 2. sharing.wss?uid=swg27019882) v the IBM Connections Information Center (http://www. and share a set of ideas and resources to support a goal.nsf/xpViewCategories. 2005.com/support/ docview.com/ldd/lcwiki.com/ infocenter/ltscnnct/v2r0/index.

Microsoft SQL Server. you must install IBM WebSphere Application Server. you must create databases for Activities and Home page to use IBM Cognos BI collaboration with IBM Connections. At a minimum.ibm. You do not have to use the same database server for IBM Connections as for your IBM Cognos BI server.When you install IBM Connections.com/software/lotus/products/connections/features. For more information about the database drivers.help/t_install_standalone. or an Oracle database. see the installation instructions in the IBM Connections Information Center (http://publib. To install IBM Connections. The directory integrator will create profiles in IBM Connections for users from your LDAP.connections. If you choose to install the Profiles feature of IBM Connections. You must also secure the IBM WebSphere Application Server profile you will be using for IBM Connections against your authentication provider using an IBM WebSphere Application Server federated repository configuration.ibm. and create the required IBM Connections databases.1: Installation and Configuration Guide . For more information. as well as use any of the other IBM Connections features you have installed. To use single signon between IBM Cognos BI and IBM Connections. install Activities and Home Page to allow collaboration with IBM Cognos BI.html). You must use a separate IBM WebSphere Application Server instance or a separate profile on the same instance. 322 IBM Cognos Business Intelligence Version 10.help/t_install_databases_using_wizard. you require a JDBC driver for your database.ibm. To install IBM Connections. you must deploy IBM Cognos BI to IBM WebSphere Application Server.html). You must have the required JDBC driver before you install the product. For more information about IBM Connections features. install updates for IBM WebSphere Application Server. see the IBM Connections Information Center (http://publib. you must. you must use the IBM Tivoli Directory Integrator to create user profiles in order for your users to be able to log in to IBM Connections.25. IBM Connections has different database support than IBM Cognos BI.connections. at a minimum.boulder.ibm.jsp?topic=/ com.2. IBM Connections requires a database for each of the features you install.html).boulder. Users can then log in and create activities from IBM Cognos Workspace. Install a database server or prepare an existing database server Ensure you use a supported database for IBM Connections and for IBM Cognos BI.jsp?topic=/ com. Installation process Use the following list to guide you through the install process for the software needed to deploy IBM Cognos BI with IBM Connections. see the IBM Connections features and benefits page (http://www.com/infocenter/ltscnnct/v2r0/index. and to populate user profiles. The Database Wizard for IBM Connections allows you to create the IBM Connections databases on IBM DB2.25. Home Page. such as Activities.ibm. etc.com/infocenter/ltscnnct/v2r0/index.

When you install IBM WebSphere Application Server. Installing to IBM WebSphere Application Server does. The system requirements for IBM Connection 3.0-WS-WAS-WinX32. but you can apply it after you have installed the product. Security is required for IBM Connections. If you do not require single signon. you must configure IBM WebSphere Application Server with an LDAP directory used for authentication and user attributes using a federated repository configuration. however.1.com/infocenter/ltscnnct/v2r0/index. enter 23. In Product. for Microsoft Windows. Search for the Fix Pack by entering the appropriate search criteria: for example.0.0.ibm. you can deploy IBM Cognos BI using Apache Tomcat or a supported application server. you must set a shared key between the profile you are using for IBM Connections and the profile you are using for IBM Cognos BI. select WebSphere Application Server.com/support/ docview.wss?uid=swg27019882).ibm.wss?rs=899&uid=swg27016547).ibm. provide the option for single signon between the applications. Single signon allows the applications to share your log in information such that users only have to log in once to use either application. In Installed Version select 6.FP0000023. Using Collaboration with IBM Cognos Workspace 323 .com/support/ docview. Secure your IBM WebSphere Application Server profile(s) You must enable security for the IBM WebSphere Application Server profile into which you will be installing IBM Connections.5 (http://www. you must update your IBM WebSphere Application Server 6. For more information about setting up security using a federated repository configuration.boulder. When you secure your IBM WebSphere Application Server profile.ibm.Install IBM WebSphere Application Server Ensure you use a supported version of IBM WebSphere Application Server for IBM Connections. For example.ibm. Fix packs are available from the IBM Fix Central web site (http://www.1. To set up single signon. Create an additional IBM WebSphere Application Server profile.jsp). The system requirements for IBM Connections 2.1 installation with Fix Pack 23.boulder. see the IBM Connections Information Center (http:// publib. the Fix Pack would be 6.com/infocenter/wasinfo/v6r1/index. Do not use the same profile for both applications. select WebSphere. For more information. you can clear the Enable administrative security check box. in Product Group. you must create an additional profile for one of the applications. Select the appropriate Fix Pack for your installation. You do not have to install IBM Cognos BI to IBM WebSphere Application Server to use collaboration with IBM Connections.0 (https://www. In the Text box. see the IBM WebSphere Information Center (http://publib. For example.com/ support/fixcentral/).jsp?topic=/ Chapter 12. if required If you are installing IBM Cognos BI and IBM Connections to the same IBM WebSphere Application Server.

To be able to successfully create Activities from IBM Cognos Workspace. For IBM Connections 3.2.com. see the IBM Connections wiki page (http://www. you are prompted for a database driver to connect to the IBM Connections databases. For more information about the database drivers. For more information. Install IBM Cognos BI.connections. see “Enable IBM Connections to accept activities created by IBM Cognos Workspace” on page 327.25. During the installation. see the following topic in the IBM Connections Information Center (http://publib. Update IBM Connections for IBM Cognos BI For more information. you must add your domain to your IBM WebSphere Application Server profile security configuration.ibm. Install IBM Connections You must have created and secured an IBM WebSphere Application Server profile before you install IBM Connections.lotus.help/t_install_standalone. If you are installing IBM Cognos BI to IBM WebSphere Application Server.0. After you have installed the Fix Pack and the Interim Fix.ibm. You do this by modifying two IBM Connections configuration files. you should secure the profile you are using for IBM Cognos BI. and then build the application for IBM WebSphere Application Server.1: Installation and Configuration Guide . see “Allow access to IBM Connections from IBM Cognos BI” on page 326. you must modify a configuration file to allow IBM Cognos BI to communicate with IBM Connections. You must also have created the required IBM Connections databases. If you are installing IBM Cognos BI on IBM WebSphere Application Server. you must enable access for a BI User role before you build the application file to install on IBM WebSphere Application Server. For more information. and you want single signon.25. see “Add user role to enable single signon between IBM WebSphere profiles” on page 374. to the same authentication source as your profile for IBM Connections. you must build the application in IBM Cognos Configuration.html).html).com/infocenter/ltscnnct/v2r0/index.help/t_inst_federated_repositories. For more information. 324 IBM Cognos Business Intelligence Version 10. see “Configure application server properties and install IBM Cognos components” on page 380. and then install the application in IBM WebSphere Application Server.connections. as well as IBM Cognos BI.boulder.com/ldd/ lcwiki. see “Mandatory updates required for IBM Connections” on page 325.jsp?topic=/ com.nsf/dx/Setting_up_federated_repositories_lc3). if required If you are installing IBM Cognos BI on IBM WebSphere Application Server and you want to use single signon between IBM Connections and IBM Cognos BI. For more information.ibm.

then IBM Connections will not allow access as it cannot verify the domain from which the access is coming.ibm. Using Collaboration with IBM Cognos Workspace 325 . In Chapter 12. For more information.jsp?topic=/com.boulder. in Product Group.com/ infocenter/ltscnnct/v2r0/index. When you configure your IBM Cognos BI.com/ infocenter/cogic/v1r0m0/index.ibm. see “Configuring the Collaboration Discovery URI” on page 284.Configure IBM Cognos BI When you configure IBM Cognos BI. see “Port and URI Settings” on page 224.help/ c_updating_lotusconnections. For more information. select Lotus.com/ infocenter/ltscnnct/v2r0/index. you must set the Collaboration discovery URI in IBM Cognos Administration. see the IBM Connections Information Center (http://publib.jsp?topic=/com.html The Fix Pack is available from the IBM Fix Central Web site: http://www. see “Configure IBM Cognos components to run within the application server” on page 375. You can set the domain values when you configure IBM Cognos BI. Search for the Fix Pack by entering the appropriate search criteria: for example. For the most up-to-date information about required Fix Packs and Interim Fixes. The directory integrator creates user profiles from your LDAP.boulder. you must add the server and port information to the Cognos Application Firewall in order to allow access from IBM Cognos BI to IBM Connections.com/support/fixcentral/. You must apply the following to your IBM Connections 2.5.ibm. if required If you have installed the IBM Connections Profiles feature. For more information about setting up Tivoli Directory Integrator and adding user profiles. The Collaboration discovery URI provides access to creating activities from IBM Cognos Workspace and adds links to IBM Connections from menus in IBM Cognos Connection.help/ t_prof_install_profiles_db. see “IBM Cognos Application Firewall” on page 230.0.5 installation: v Fix Pack version 2.connections. you must update your IBM Connections installation by applying required Fix Packs or Interim Fixes. After you have installed and configured your IBM Connections and IBM Cognos BI software. you must ensure that you use the full domain name of the computer where your services are running and for your gateway. select IBM Connections. Mandatory updates required for IBM Connections To use IBM Connections with IBM Cognos Business Intelligence. see the Information Center for this product at http://publib.ibm.boulder. For more information.ibm.connections.jsp.ibm. For more information. If you do not include the domain. see the following topic in the IBM Connections Information Center: http://publib. Create IBM Connections profiles using the population wizard.html).25. In Product.2 For more information about updating IBM Connections.25. you must create user profiles in IBM Connections using the Tivoli Directory Integrator before users can log in.

In Product. The Interim Fixes are available from the IBM Fix Central Web site: http://www. The file to be copied is named oa-config.2.25. The downloaded Fix Pack is named LC2502_FixPack.0. 326 IBM Cognos Business Intelligence Version 10. in the APAR or SPR box.0.5. enter 2.com/infocenter/ltscnnct/v2r0/index. The files are located in your IBM WebSphere Application Server directory.xsd and it is included with the required Interim Fix.0 installation: v Interim Fix.com/eserver/support/fixes/fixcentral/.0.com to the list of allowable domains in IBM Connections. or iFix. In the Individual fix IDs box.com/support/fixcentral/.connections. in Product Group. In Installed Version select 2. For example.jar. In Product. if your IBM Cognos BI server is running on mycomputer. Allow access to IBM Connections from IBM Cognos BI To enable collaboration between IBM Cognos BI and IBM Connections.jsp?topic=/ com. see http://publib. select IBM Connections.ibm.5. select IBM Connections.xml. select Lotus. Search for the iFix by entering the appropriate search criteria: for example.jar. you must then install Interim Fix LO52425. enter LO52700.boulder. Adding the domain allows access to IBM Connections from computers in that domain.0. Search for the Interim Fix by entering the appropriate search criteria: for example.5. In Installed Version select 3. LO56863 and LO57924 The iFixes are available from the IBM Fix Central Web site: http:// www. You must apply the following to your IBM Connections 3. If you do not add the domain. The file to be modified is named oa-config. in Product Group.1: Installation and Configuration Guide .ibm. select Lotus.0.com. oa-config.0.html. Ensure that you back up the files before you modify them. The iFix appears in the search results as interim fix: 3. You must have installed the appropriate Fix Pack and Interim Fix before you modify these files.mycompany. For example.ibm. and is downloaded as LO56863. you must update a file in your IBM Connections installation and then modify a file to add the domain for the server where IBM Cognos BI is running.0.0. then you must add mycompany.0.xml allows access from IBM Cognos BI. You can apply multiple Interim Fixes at the same time.help/t_install_interim-fix_silent-mode.0-LC-MultiACTIVITIES-IFLO56863. In the APAR or SPR box. IBM Cognos BI will not be able to create activities. For more information.Installed Version select 2.2-LC-Multi-FP000002. v The following Interim Fixes must be applied: LO52700 LO52560 LO51723 LO53215 LO51605 For IBM Cognos BI integration.ibm. enter LO56863.0.

For example. 2. copy the file named oa-config. then synchronize these changes with the nodes before restarting the profile.xsd to the WebSphere_location\profiles\connections_profile\InstalledApps\ computer_nameNode##Cell\LotusConnections-config directory. Chapter 12.deptB.xml in a text editor. you may see errors when you create the activity in IBM Cognos Workspace. and make a copy of the file named oa-config. At the end of the file. open the file named oa-config. but before the </config> element.com as the domain. applications. 3.mycompany\.com part of the domain name. Results IBM Cognos BI will now be able to communicate with IBM Connections and to create activities. you must modify the files in the LotusConnections-config directory on the Deployment Manager computer.com make up your domain. enter . you must add your domain to a setting in your IBM WebSphere Application Server profile where you have installed IBM Connections. IBM Cognos BI is installed on a computer with . For example. ensure that you use only the common part of the domain name.mycompany.mycompany. In the Domain name box.com</domain> </WidgetRedirectWhitelist> where . If you have different subdomains on your network. Open the IBM WebSphere Application Server administration console. 11. Go to the WebSphere_location\profiles\connections_profile\InstalledApps\ computer_nameNode##Cell\LotusConnections-config directory. Procedure 1. 5.com. From the IBM Cognos BI product CDs or the location where you downloaded the Interim Fix file.mycompany.mycompany and . and infrastructure page. Save and close the file. 4. Enable IBM Connections to accept activities created by IBM Cognos Workspace To allow IBM Cognos Workspace to properly create activities in IBM Connections. and then click Save. Using Collaboration with IBM Cognos Workspace 327 .deptA. add the following element: <WidgetRedirectWhitelist> <domain>. and IBM Connections is installed on a computer with . enter your domain name. 8.com. Click OK. 6. Restart the IBM WebSphere Application Server profile where IBM Connections is installed. 9. you must include only the . 10. In the same directory. In the Authentication section. 7. Ensure that you include the period before the domain name.xsd.mycompany.*\. Click the link for the Secure administration. click Web Security > Single sign-on (SSO).If you are using a network deployment of IBM Connections. If you do not add the domain.

Procedure 1. by clicking Start > All Programs > IBM WebSphere > Application Server v6. including the period before the domain name. and ensure sure you select the appropriate Web server for what you have installed.mycompany. install all of the components.template in a text editor. for example enter . Start the IBM WebSphere Application Server administration console. In the Authentication section.com/infocenter/wasinfo/v6r0/ index.nd. 4.2. and do the following: v Open the file named application. v Edit the application section to include a security-role element. Go to the c10_location\webapps\p2pd\WEB-INF directory on the computer where you installed IBM Cognos BI. Click Security > Secure administration.xml. you must install the Gateway component on your Web server computer. as shown in the following example: 328 IBM Cognos Business Intelligence Version 10.Procedure 1. You must install the Gateway component on the Web server computer so that the required static content is available. applications and infrastructure. Run your IBM WebSphere Application Server installation. and select Web Server Plug-ins Installation. Install the IBM Cognos Business Intelligence components. Enable single signon between IBM Connections and IBM Cognos Business Intelligence To enable single signon between IBM Connections and IBM Cognos Business Intelligence using your Web server as the access point. If you are using a single server installation. The Integrated Solutions Console appears prompting you to log in. 6. you must configure IBM WebSphere Application Server to know about the Web server following the information provided in the IBM WebSphere page. 3.doc/info/ae/ae/ tins_road_plugins. Follow the steps in the wizard. 2. enter the domain for your computer.jsp?topic=/com. and infrastructure page appears. Change all values for fileServingEnabled to false.ibm. click Web Security > Single sign-on (SSO). you must install a Web server plug-in that is provided with your IBM WebSphere Application Server installation. 7. The Secure administration. In the Domain name box. 5. applications.html 5. If you are distributing your installation.com. see the following IBM WebSphere page: http://publib. Create a virtual directory for the Gateway named /p2pd/servlet that points to the c10_location/webcontent directory.boulder. Go to the c10_location\war\p2pd directory.websphere.xmi file in a text editor. For more information about installing the plug-in. 4.ibm.1 > Profiles > profile name > Administrative Console. After you install the plug-in. 3. and open the file named ibm-web-ext. 8.1: Installation and Configuration Guide . and then click Save. 9. Save and close the file. Ensure that you use the appropriate domain for your computer. Click OK. 2.

and save your configuration. v Click IBM Cognos. v After the last servlet-mapping section. Ensure that you do not include the static content when you generate the EAR file. and before the closing web-apps element. open the file named web. After you have installed the IBM Cognos application to IBM WebSphere. and do the following: v If you have installed Content Manager on the computer. click Security role to user/group mapping. 11. Configure IBM Cognos BI as required using IBM Cognos Configuration. Install the IBM Cognos application on IBM WebSphere Application Server. For single signon. open the file named web. you must enable the security role. 10. Chapter 12. v In the Detail properties section. 12.xml. Using Collaboration with IBM Cognos Workspace 329 . add the following: <security-constraint> <web-resource-collection> <web-resource-name>Cognos Dispatcher</web-resource-name> <url-pattern>/servlet/dispatch/ext/*</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>BI User</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>Cognos Dispatcher</realm-name> </login-config> <security-role> <role-name>BI User</role-name> </security-role> v Save and close the file. Use IBM Cognos Configuration to create the deployment file to install to IBM WebSphere.<application> <display-name>IBM Cognos 10</display-name> <module> <web> <web-uri>@p2pdwar@</web-uri> <context-root>@p2pd@</context-root> </web> </module> <security-role id="SecurityRole_Cognos_BI_User"> <description/> <role-name>BI User</role-name> </security-role> </application> v Save and close the file. If you have not installed Content Manager.xml.withCM in a text editor. including securing it using the same authentication source as you have used for IBM Connections. you must enable a user role after you have installed the application. click Applications > Enterprise applications. Go to the c10_location\webapps\p2pd\WEB-INF directory.noCM. v In the IBM WebSphere administration console. 13.

applications.v Select the Select check box for BI User. and import a key from profile A into profile B. and then click Save. your URL will be: http://web_server_name/ p2pd/servlet/dispatch/ext 330 IBM Cognos Business Intelligence Version 10. enter a password. For the more information. Select the Web server. Then select the Web server again. If you are using the Web server plug-in for load balancing. After you install IBM Cognos to IBM WebSphere Application Server. you must swap keys between your IBM WebSphere profiles. you must generate and propagate the Web server plug-in configuration. under Servers. 15. v Click OK. To do this. click Security > Secure administration.2.1: Installation and Configuration Guide . 16. Results To access the IBM Cognos BI portal. and select the All authenticated? check box. If you are not using an IBM WebSphere Network Deployment. v In your IBM WebSphere administration console. click Web servers. in the IBM WebSphere administration console. and click Propagate Plug-in. v In the Cross-cell single sign-on section. v Repeat these steps for the other profile so that you import a key from profile B into profile A. turn off the internal load balancing done by the dispatcher. see the topic on using cluster compatible mode for dispatchers in the IBM Cognos Business Intelligence Administration and Security Guide. and infrastructure. 14. and then import the key to the other profile. v Export the key. click Authentication mechanisms and expiration. v In the Authentication section. and click Generate Plug-in.

Also. IBM Cognos components support the following types of servers as authentication sources: v IBM Cognos Series 7 namespace v Active Directory Server v v v v Custom Authentication Provider LDAP CA SiteMinder RACF v SAP If you use more than one Content Manager. you can disable anonymous access. see the Administration and Security Guide. © Copyright IBM Corp. You can configure the namespace if you still require the user account information. and groups. For information about deleting the namespace. see the Administration and Security Guide. you must configure IBM Cognos components with an appropriate namespace for the type of authentication provider in your environment. which namespace you want to use. you must configure identical authentication providers in each Content Manager location. the unconfigured namespace appears in the list of authentication providers in the Administration portal. 2013 331 . This means that the type of authentication provider you select and the way you configure it must be identical in all locations for all platforms. you must use the same authentication namespace for both versions. roles. You can configure multiple namespaces for authentication and then choose. If these libraries are not available on Linux. If you choose to use authenticated logon only. Configuring IBM Cognos Components to Use an Authentication Provider IBM Cognos components run with two levels of logon: anonymous and authenticated. If you upgraded from ReportNet and IBM Cognos detects a previously configured namespace that is no longer configured. anonymous access is enabled. Some authentication providers require libraries external to the IBM Cognos environment to be available. When IBM Cognos is installed in a single Linux-based computer. IBM Cognos can be configured to use only LDAP V3-compliant directory servers and custom providers as authentication sources. By default.Chapter 13. or when Content Manager is installed on a Linux-based computer. The configuration must contain information that is accessible by all Content Managers. users. the authentication provider cannot be initialized. For more information. For authenticated logon. 2005. you can delete the namespace. the old secured content will not be available because the new version may not contain the same policies. Otherwise. Otherwise. at run time. when upgrading from one version to another. You can use both types of logon with your installation.

In the Explorer window. For more information. and distribution lists. While this does not affect how the permissions work. To use an authentication provider and to require users to authenticate. a user administering the permission settings may see "unknown" entries. you can safely delete them. start IBM Cognos Configuration. Users can select namespaces when they log in to the IBM Cognos portal. under Security > Authentication. The Cognos namespace stores information about IBM Cognos groups. __ v Configure IBM Cognos components to use an authentication provider. Because these entries refer to users. you must install Content Manager on a Microsoft Windows computer: v IBM Cognos Series 7 namespace v Active Directory Server v SAP BW If you enable security.1: Installation and Configuration Guide . if required. see the Administration and Security Guide. IBM Cognos components do not require user authentication. For more information. the user preferences. Google OneBox applications are open and anonymous. click Cognos. Procedure 1. you can use IBM Cognos Configuration to disable anonymous access. My Folders. groups. By default. such as the Anonymous User. Important: Do not disable security after you enable it. This means that a user logs on once and can then switch to another application without being asked to log on again. In each location where Content Manager is installed. 2. Disable Anonymous Access If you want to use authenticated logon only. If your application requires secure authentication. and refers to objects in other 332 IBM Cognos Business Intelligence Version 10. see “Hide the Namespace from Users During Login” on page 347. you can enable single signon between your authentication provider environment and IBM Cognos components. and My Pages entries are permanently lost.If you want to configure one of the following as your authentication source. Users can log on anonymously. Related tasks: “Set up security for a Google OneBox sample module” on page 419 By default.2. you must configure security settings immediately after you complete the installation and configuration process. After you configure an authentication provider for IBM Cognos components. Existing permission settings will refer to users. groups. The IBM Cognos resource represents the Cognos namespace. contacts. If you delete a namespace. or roles that no longer exist. do the following: __ v Disable anonymous access. You can hide Custom Java namespaces and CA SiteMinder namespaces from users. you must configure the Google Search Appliance (GSA) and your IBM Cognos installation appropriately. and roles which no longer exist.

3. Restrict User Access to the Cognos Namespace You can restrict access to users belonging to any group or role defined in the Cognos built-in namespace. Configuring IBM Cognos Components to Use an Authentication Provider 333 . From the File menu. you must use an LDAP namespace to configure Active Directory for all Content Managers. using IBM Cognos Administration. In the Properties window. click the box next to the Allow anonymous access property and then select False. under Security. click Save. using IBM Cognos Administration. change the value of Restrict access to members of the built-in namespace to True. When you use an LDAP namespace to authenticate against Active Directory Server. using IBM Cognos Configuration. You do not have access to Active Directory features such as advanced properties for domains and single signon using Kerberos delegation. For more information. see the IBM Cognos Business Intelligence Administration and Security Guide. Results Now. click Save. If you install Content Manager on a mix of Windows and UNIX computers. start IBM Cognos Configuration. In the Properties window. click Authentication. For information about adding or removing members of a group or role.security namespaces. Chapter 13. see the IBM Cognos Business Intelligence Administration and Security Guide. you can configure Active Directory as your authentication source using an Active Directory namespace. Procedure 1. If you install Content Manager on a UNIX-based computer. Results You must now use the portal to remove the Everyone group from the built-in roles and groups. By default. 4. v Ensure that authorized users belong to at least one role or group. and then ensure that authorized users belong to at least one built-in role or group. you are limited to LDAP features only. Configuring IBM Cognos Components to Use Active Directory Server If you install Content Manager on a Microsoft Windows operating system computer. In each Content Manager location. In the Explorer window. 3. From the File menu. 2. all users belong to several built-in groups or roles. v Remove the Everyone group from the built-in roles and groups. To restrict access. 4. you must configure a namespace so that users are required to provide logon credentials when they access IBM Cognos resources. you must do the following: v Enable the property to restrict access. you must instead use an LDAP namespace to configure Active Directory as your authentication source.

Related tasks: “Include or Exclude Domains Using Advanced Properties” on page 336 When you configure an authentication namespace for IBM Cognos. Configure IBM Cognos components to use an Active Directory Server namespace 2. users from only one domain can log in. users from related (parent-child) domains and unrelated domain trees within the same forest can also log in. Enable single signon between Active Directory and IBM Cognos components Related concepts: “Enable single signon between Active Directory Server and IBM Cognos components” on page 338 By default. ensure the following configuration: v The IBM Cognos gateway is installed on an IIS Web server that is configured for Integrated Authentication on Microsoft Windows operating system . You cannot connect to the Active Directory Global Catalog. “Configure an LDAP namespace for Active Directory Server” on page 349 If you configure a new LDAP namespace for use with an Active Directory Server. 334 IBM Cognos Business Intelligence Version 10. By default. the Active Directory provider uses Kerberos authentication. which is a caching server for Active Directory Server. you must change it. ensure that the Authenticated users group has Read privileges for the Active Directory folder where users are stored. You must use an LDAP namespace to configure Active Directory as your authentication source. Active Directory Server uses port 389. If you are configuring an Active Directory namespace to support single signon with a Microsoft SQL Server or Microsoft Analysis Server data source. you must modify the necessary settings and change the values for all properties of the Active Directory objects. the same restrictions apply as for UNIX. Configure an Active Directory Namespace You can use Active Directory Server as your authentication provider.If you install Content Manager on a Linux-based computer. v Content Manager is installed on a Windows 2000 or Windows 2003 server. You also have the option of making custom user properties from the Active Directory Server available to IBM Cognos components.2. By using the Advanced properties for Active Directory Server. Before you begin For IBM Cognos to work properly with Active Directory Server. If you want to use Microsoft SQL Server or Microsoft Analysis Server as a data source and use single signon for authentication. Procedure 1. you must use Active Directory as your authentication source. If the connection uses port 3268. Enable secure communication to the Active Directory Server. v The gateway is assigned to the local intranet Web site in your Web browser. if required 3.1: Installation and Configuration Guide . It integrates with the IIS web server for single signon if Windows authentication (formerly named NT Challenge Response) is enabled on the IIS web server.

For more information about data sources. 6. under Authentication. specify the user ID and password for the Binding credentials property. right-click Authentication. IIS Web server. 5.com:389. From the File menu. 7. The new authentication provider resource appears in the Explorer window. You can use the command blocks can be used with Chapter 13. To support Active Directory Server failover.com:389 instead of dc1. In the Explorer window. under the Authentication component. 2. Results IBM Cognos loads. see the Framework Manager User Guide You can also use the custom properties inside command blocks to configure Oracle sessions and connections. In the Explorer window. Specify the values for all other required properties to ensure that IBM Cognos components can locate and use your existing authentication provider. click the appropriate namespace and then click OK. The custom properties are available as session parameters through Framework Manager. and the data source server (Microsoft SQL Server or Microsoft Analysis Server) belong to the Active Directory domain. under Security. type a name for your authentication namespace.v Content Manager. open IBM Cognos Configuration. To configure this. Specify the values for the Host and port property. initializes. In the Name box. Procedure 1. Make Custom User Properties for Active Directory Available to IBM Cognos Components You can use arbitrary user attributes from your Active Directory Server in IBM Cognos components. right-click the new authentication resource and click Test. and then click New resource > Namespace. 9. For more information about session parameters. 8. click Save. and configures the provider libraries for the namespace. Test the connection to a new namespace. use mydomain. In the Properties window. In the Type list. you must add these attributes as custom properties for the Active Directory namespace. In every location where you installed Content Manager. specify a unique identifier for the namespace. If you want to search for details when authentication fails.mydomain. For example. v 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 the Namespace ID property. Application Tier Components. 3. Configuring IBM Cognos Components to Use an Authentication Provider 335 . see the IBM Cognos Business Intelligence Administration and Security Guide. you can specify the domain name instead of a specific domain controller. Use the credentials of an Active Directory Server user who has search and read privileges for that server. 4. 10.

3. use your Web browser to connect to the Active Directory Server and copy the CA root certificate to the Content Manager location. see the documentation for your Web browser. For information. In the Value . restart the service: v In the Explorer window. use Microsoft Management Console (MMC) to import the CA root certificate to the certificate store for the local computer. 9. use the same Web browser as in step 1 to import the CA root certificate to the certificate store for your user account. 336 IBM Cognos Business Intelligence Version 10. In IBM Cognos Configuration. users from related (parent-child) domains and unrelated domain trees within the same forest can also log in. In the Properties window. click in the Value column for Custom properties and click the edit icon. In the Explorer window.Oracle light-weight connections and virtual private databases. Click the Name column and type the name you want IBM Cognos components to use for the session parameter. 2.1: Installation and Configuration Guide . Enabling Secure Communication to the Active Directory Server If you are using an SSL connection to the Active Directory Server. v From the Actions menu. under Security > Authentication. open IBM Cognos Configuration. By using the Advanced properties for Active Directory Server. 2. IBM Cognos. For information. Click OK. 4. 8. 7. see the documentation for MMC. 6. In every location where you installed Content Manager. In every Content Manager location. you must copy the certificate from the Active Directory Server to the Content Manager location. click Add. v If you are running the IBM Cognos session under the local account. click Save. users from only one domain can log in. Include or Exclude Domains Using Advanced Properties When you configure an authentication namespace for IBM Cognos. click IBM Cognos services. From the File menu. Procedure 1. click the Active Directory namespace. Add the CA root certificate to the certificate store of the account that you are using for the current IBM Cognos session: v If you are running the IBM Cognos session under a user account. see the IBM Cognos Business Intelligence Administration and Security Guide. click Restart.2. Click the Value column and type the name of the account parameter in your Active Directory Server. 3.Custom properties window. 5. Repeat steps 4 to 6 for each custom parameter. Procedure 1. For more information.

In every location where you installed Content Manager. under Security > Authentication. click Save. In the Explorer window. 3. click the Active Directory namespace. with the values from the following table: Table 74. v For users in one domain tree. specify the host and port of the top-level controller for the domain tree. 8. v For users in all domain trees in the forest. under Security > Authentication. users in all domain trees in the forest can log in to IBM Cognos. Click in the Value column for Advanced properties and click the edit icon. In the Explorer window. In the Value . Configuring IBM Cognos Components to Use an Authentication Provider 337 . Advanced properties settings Authentication for One domain One domain tree chaseReferrals False True MultiDomainTrees False False True All domain trees in the forest True 7. click Add. specify the Host and port property: Chapter 13. specify the host and port of any domain controller in the forest. click the Active Directory namespace. In the Properties window. 2. 3. If you set a parameter named MultiDomainTrees to true. open IBM Cognos Configuration. chaseReferrals and MultiDomainTrees.If you set a parameter named chaseReferrals to true. In the Properties window. Click OK. Procedure 1. specify the host and port of a domain controller for the single domain. 6. open IBM Cognos Configuration. Related tasks: “Configuring IBM Cognos Components to Use Active Directory Server” on page 333 If you install Content Manager on a Microsoft Windows operating system computer. Users from a parent domain of the original authenticated domain or in a different domain tree cannot log in. 2. you can configure Active Directory as your authentication source using an Active Directory namespace. Authenticating Domain Trees Procedure 1.Advanced properties window. Specify two new properties. 5. specify the Host and port property: v For users in one domain. 4. From the File menu. In every location where you installed Content Manager. users in the original authenticated domain and all child domains of the domain tree can log in to IBM Cognos.

chaseReferrals and MultiDomainTrees. they are promoted for their domain account. 5. specify the host and port of a domain controller for the single domain. In the Value . which prevents them from getting authenticated to IBM Cognos BI. you can configure the provider to access the environment variable REMOTE_USER to achieve single signon. you can choose to use Service for User (S4U). you are not prompted to reenter authentication information when you access IBM Cognos content that is secured by the Active Directory namespace.Advanced properties window.1: Installation and Configuration Guide . For example. you must ensure that you complete the following tasks: 1. From the File menu. Click OK. Click in the Value column for Advanced properties and click the edit icon. If Windows authentication is enabled. Properties for setting authenticating domain trees Authentication for One domain One domain tree chaseReferrals False True MultiDomainTrees False False True All domain trees in the forest True 7. To enable S4U. S4U allows users to access IBM Cognos BI from computers not on the Active Directory domain. 6.2. v For users in one domain tree. they get the Kerberos ticket with Identity privilege only. with the values from the following table: Table 75. 4. 8. click Add. specify the host and port of any domain controller in the forest. Using another variable can cause a security vulnerability. specify the host and port of the top-level controller for the domain tree. you can use S4U. If you do not want Kerberos authentication. To resolve this issue. However. you have users whose computers do not belong to the domain.v For users in one domain. you must use enable constrained delegation. Set up Windows authentication on your IIS web server. If you use Kerberos authentication. 338 IBM Cognos Business Intelligence Version 10. but they do have the domain account. It integrates with the IIS web server for single signon if Windows authentication (formerly named NT Challenge Response) is enabled on the IIS web server. the Active Directory provider uses Kerberos authentication. click Save. To enable single signon to use Kerberos authentication. Important: Ensure that you use only the variable REMOTE_USER. Enable single signon between Active Directory Server and IBM Cognos components By default. v For users in all domain trees in the forest. Specify two new properties. When they open their web browsers.

Chapter 13. to be trusted. you must add an sAMAccountName user for Content Manager when you configure your gateway. You must set up IIS so that your MyDomain\IISUser is the application pool identity 2. you must configure the sAMAccountName for the user who runs the Application Tier Components when you add the Active Directory namespace. If you are configuring single signon to your database servers. you do not have to add any additional settings. Enabling single signon to use Kerberos authentication with constrained delegation To be able to use constrained delegation. If you use Kerberos with constrained delegation. For example. Set up the computers.MyDomain. Install Content Manager on a computer that is part of the Active Directory domain. or the user account under which Content Manager runs. 3. Enabling single signon to use Kerberos authentication If your IIS web server is configured for Windows authentication. For example: setspn -A ibmcognosba/CognosCMUser MyDomain\CognosCMUser setspn -A ibmcognosba/CognosATCUser MyDomain\CognosATCUser In these commands. The SPNs are the users that you enter in the sAMAccountName fields in IBM Cognos Configuration. another who runs the Application Tier Components. for the active and standby Content Managers. Each user is in the MyDomain domain. Run the setspn command for your IBM Cognos users. you must define the service principal names (SPN) for the users that are configured to run the IBMCognos components and your Microsoft Internet Information Services (IIS) web server's application pool in your Active Directory domain. Configuring IBM Cognos Components to Use an Authentication Provider 339 . you must use ibmcognosba as shown in the examples. Run the setspn command for the computer where IIS is running. Note: In this example. the sAMAccountName users you must enter are CognosCMUser and CognosATCUser. The Application Tier Components user is CognosATCUser. assume that you have one user who runs the Content Manager component. The application pool user is IISUser. All active and stand by Content Managers must be configured to run under the same account. All Application Tier Components must be configured to run under the same account.com MyDomain\IISUser 3. 1. Related tasks: “Configuring IBM Cognos Components to Use Active Directory Server” on page 333 If you install Content Manager on a Microsoft Windows operating system computer. For example: setspn -A http/IISServerName MyDomain\IISUser setspn -A http/IISServerName. The user names and domains must match your environment. and another who runs your web server's application pool. The Content Manager user is CognosCMUser.2. you can configure Active Directory as your authentication source using an Active Directory namespace. Kerberos authentication is used as the default.

and select the Active Directory namespace. click Add. enter one of the following values: v Enter KerberosS4UAuthentication if you want to use Kerberos authentication first.Advanced properties dialog box. Finally. Important: This value is required only if you are configuring single signon to your Microsoft SQL Server or Microsoft SQL Server Analysis Services database server. In the Name column. Procedure 1. if you want to use the credentials to run scheduled jobs. see you database server documentation. the user is prompted for credentials. Click in the Value column for Application Tier Components sAMAccountName. For more information. The user name is saved in UPN format. For example. click Add. Click File > Save. and enter the sAMAccountName of the user who runs the Application Tier Components. and CognosATCUser). Restart the IBM Cognos service. If S4U fails. In the Value column. under Security > Authentication. Select Trust this user for delegation to specified services only and Use any authentication protocol if you are using the S4U Kerberos extension. 10.2.4. Click in the Value column for Advanced properties and then click the edit icon. Service For User (S4U) authentication is attempted. For example. add ibmcognosba as a service type. enter one of the following values: v Enter CredentialForTC if you want to save the user's credentials as a trusted credential. In the Value . If you are configuring single signon to your Microsoft SQL Server or Microsoft SQL Server Analysis Services database server. you must select Trust this user for delegation to specified services only and Use Kerberos only to use Kerberos with constrained delegation. 5. do not change this value. 5. 2. 6. 3. 9.1: Installation and Configuration Guide . On the Delegation tab for all users (IISUser. In the Explorer window. Click OK. 12. CognosCMUser. open IBM Cognos Configuration. 7. you must configure the constrained delegation in the Active Directory Users and Computers administration tool. In the Value . type singleSignonOption. If you are not configuring single signon to the database server.Advanced properties dialog box. And then you must add the required SPNs. v Enter S4UForTC if you want to save only the authenticated user name as a trusted credential. you must set up the SPN for the database server. 13. the user is prompted for credentials. type trustedCredentialType. 340 IBM Cognos Business Intelligence Version 10. If Kerberos fails. v Enter S4UAuthentication if you want to use S4U authentication first. 11. 4. add the MSOLAPSvc3 or MSQLSVC service. 8. and scheduled jobs can be run with the UPN without requiring the user's password. On the computer where you installed Content Manager. If you are configuring single signon for the datasource. And add DomainController1 and DomainController2 as service type ldap. In the Name column. In the Value column. If S4U fails.

12. single signon to Microsoft OLAP (MSAS) data sources is not possible. Click in the Value column for Content Manager sAMAccountName.Advanced properties dialog box. type trustedCredentialType. In the Value column. Users will be authenticated based on the authentication and signon configuration of the IBM Cognos Series 7 namespace. click Add. In the Explorer window. you can configure the provider to access the environment variable REMOTE_USER to achieve single signon. Microsoft IIS sets REMOTE_USER by default when you enable Windows authentication. you can also choose to save the REMOTE_USER as a trusted credential. 4. and select the Active Directory namespace. 10. 3. Configuring IBM Cognos to Use IBM Cognos Series 7 Namespace You can configure IBM Cognos components to use an IBM Cognos Series 7 namespace as the authentication provider. under Security > Authentication. In the Name column. specify a user ID and password and then click OK. click Add. 17. Important: Ensure that you use only the variable REMOTE_USER.14. open IBM Cognos Configuration. 15. open IBM Cognos Configuration. You must set the advanced property singleSignOnOption to the value IdentityMapping. 9. click Environment. Click OK. and then click the edit icon. in the Value Advanced properties dialog box. type IdentityMapping. If you want to save the REMOTE_USER as a trusted credential. Click File > Save. In the Value . If Kerberos authentication is not used. Click in the Value column for Binding credentials. When you define the REMOTE_USER. 16. Saving as a trusted credential means that scheduled jobs authenticate the REMOTE_USER with the Binding Credential privileges. 2. On the computer where you installed Content Manager. Procedure 1. 8. type singleSignOnOption 6. In the Name column. On the computer where you installed the Gateway components. Chapter 13. In the Value column. Enabling single signon between Active Directory Server and IBM Cognos Components to use REMOTE_USER If you do not want Kerberos authentication. type IdentityMappingForTC. In the Value . and enter the sAMAccountName of the user who runs Content Manager. Click in the Value column for Advanced properties and then click the edit icon. 7. Configuring IBM Cognos Components to Use an Authentication Provider 341 . You must also specify bind credentials for the Active Directory namespace. In the Explorer window. 5. Using another variable can cause a security vulnerability. 11.Binding credentials dialog box.

3. 4. Otherwise. specify a unique identifier for the namespace. type a name for your authentication namespace. 5. for the Namespace ID property. In the Explorer window. and then click New resource > Namespace. if the server name is used in 342 IBM Cognos Business Intelligence Version 10. right-click Authentication.An IBM Cognos Series 7 namespace is required if you want to use IBM Cognos Series 7 PowerCubes and Transformer models in IBM Cognos Business Intelligence. also ensure that the ticket server is running. the locations where Content Manager is installed must use the same locale as the data in the IBM Cognos Series 7 namespace. Configure a Series 7 namespace 2. under Security. Specify the values for all other required properties to ensure that IBM Cognos components can locate and use your existing authentication provider. Enable secure communication to the directory server used by the IBM Cognos Series 7 namespace. Note: You cannot use an IBM Cognos Series 7 Local Authentication Export (LAE) file for authentication with IBM Cognos components. To maintain performance. You must configure the namespace before you load the Transformer models. ensure that the Data encoding property is set to UTF-8. The new authentication provider resource appears in the Explorer window. You can configure IBM Cognos components to use multiple IBM Cognos Series 7 authentication providers. If you change the configuration information stored in the directory server used for IBM Cognos Series 7. If you are publishing from PowerPlay Enterprise Server to IBM Cognos BI. Procedure 1. In the Properties window. if required 3. In addition. Enable single signon between IBM Cognos Series 7 and IBM Cognos Configure an IBM Cognos Series 7 Namespace You can configure IBM Cognos to use one or more IBM Cognos Series 7 namespaces for authentication. The host value can be a server name or an IP address. A user must be in at least one Access Manager user class to log on to IBM Cognos components. In every location where you installed Content Manager. open IBM Cognos Configuration. 6.0.2. Procedure 1. If your IBM Cognos Series 7 namespace version is 16. For example.1: Installation and Configuration Guide . In the Name box. under the Authentication component. you must restart the IBM Cognos service before the changes take effect in the IBM Cognos installation. In the Type list. you must use the same value format used in IBM Cognos Series 7 Configuration Manager for the location of the directory server. All IBM Cognos Series 7 namespaces must use the same primary IBM Cognos Series 7 Ticket Server. 2. click the appropriate namespace and then click OK. you may receive errors or be prompted for authentication more than once.

see the IBM Cognos Access Manager Administrator Guide and the documentation for your Directory Server. Domain. By configuring single signon. click Save. On the Components tab. click Add. Domain. Enabling Single Signon Between IBM Cognos Series 7 and IBM Cognos If your IBM Cognos Series 7 namespace has been configured for integration with your external authentication mechanisms for single signon. type False. the IBM Cognos Series 7 provider will automatically use this configuration. start Configuration Manager. 5. 8. you must now define the SaferAPIGetTrustedSignonWithEnv function.2 of the IBM Cognos Series 7 namespace. Access Manager . If the IBM Cognos Series 7 namespace uses the Trusted Signon plug-in for single signon. expand Services. 2. 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. From the File menu. Click Open the current configuration. you must also use the server name in IBM Cognos Configuration for IBM Cognos BI. 3. Test the connection to a new namespace. and Secure Flag Enabled properties match the settings configured for IBM Cognos BI. In the Properties window. In the Properties window. click the edit icon. ensure that the Path. you are not prompted to reenter authentication information when accessing IBM Cognos content that is secured by the IBM Cognos Series 7 namespace. Save and close Configuration Manager. v In the Name box. in the Explorer window. Chapter 13. you must disable the Series7NamespacesAreUnicode setting. 4. you must copy the certificate from the Directory Server to each Content Manager location. Procedure 1. v In the Value box. and then click OK. 9. If your namespace environment includes version 15. type Series7NamespacesAreUnicode. 7.Advanced properties window. Configuring IBM Cognos Components to Use an Authentication Provider 343 .Web Authentication and click Cookie Settings. 7.IBM Cognos Series 7 Configuration Manager. right-click the new authentication resource and click Test. in the Advanced Properties value. In the Explorer window. For more information. v In the Value . and Secure flag enabled properties match the settings configured for IBM Cognos Series 7. ensure that the Path. v In the Properties window. Ensure that you configured IBM Cognos components to use an IBM Cognos Series 7 namespace as an authentication provider. For IBM Cognos Series 7. under Cookie settings. 6. under Authentication. 10.

see the IBM Cognos Series 7 documentation. Access Manager calls SaferAPIFreeBuffer() to free the memory allocated. **implementerData). OS signons must exist and be enabled in the current namespace. both the SaferAPIGetTrustedSignonWithEnv and SaferAPIGetTrustedSignon functions are required. The memory for the returned trustedSignonName and trustedDomainName is allocated internally in this API. For information about the SaferAPIGetTrustedSignon function. Then you must recompile and redeploy the library for single signon to be achieved between IBM Cognos components and your authentication mechanism. You must implement both the SaferAPIGetTrustedSignon and SaferAPIFreeBuffer functions to successfully register the library when SaferAPIGetTrustedSignonWithEnv is implemented. Therefore. *trustedSignonNameLength. If the function returns SAFER_SUCCESS.2. This update is required because IBM Cognos logon is not performed at the Web server as is the case for IBM Cognos Series 7 applications. /*[IN]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[IN/OUT]*/ 344 IBM Cognos Business Intelligence Version 10. 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. If the function returns SAFER_INFO_REQUIRED.Results You can now add IBM Cognos Upfront Series 7 NewsBoxes to your IBM Cognos Connection portal pages. The SaferAPIGetTrustedSignonWithEnv function is an updated version of the SaferAPIGetTrustedSignon function. The memory for the returned reqEnvVarList is allocated internally in this API. The function SaferAPIGetError is required only if you want specific error messages returned from your plug-in. **reqEnvVarList. Access Manager calls SaferAPIFreeTrustedSignon to free the memory allocated. you must define the SaferAPIGetTrustedSignonWithEnv function in your plug-in. Syntax SaferAPIGetTrustedSignonWithEnv( EnvVar char void unsigned long void unsigned long SAFER_USER_TYPE void envVar[]. **trustedDomainName. SaferAPIGetTrustedSignonWithEnv Function For users to be successfully authenticated by Access Manager. *trustedDomainNameLength. it is not possible for the plug-in to perform a getenv() API call to retrieve Web server environment variables. **trustedSignonName.1: Installation and Configuration Guide . If you are running both IBM Cognos Series 7 and IBM Cognos products using the same plug-in. *userType. The plug-in can request that specific environment variables be removed from the Web server using the SaferAPIGetTrustedSignonWithEnv function.

This value is mandatory and must be set to zero if there is no trustedDomainName. An integer value that indicates the length of the trustedDomainName. the return is null. If there is no trustedDomainName. [in/out] implementerData A pointer used to preserve implementation-specific data between invocations. This value is mandatory. An anonymous user account must exist and be enabled in the current namespace. This value is valid only if the trusted signon plug-in was invoked and you set a value for it. A sequence of bytes that identifies the currently authenticated user. This length should exclude the null terminator. The end of the array is represented by an entry with a null envVarName and a null envVarValue. An invocation occurs every time Access Manager calls the trusted signon plug-in. You do not need to null-terminate this value. [in] reqEnvVarList [out] trustedSignonName [out] trustedSignonNameLength [out] trustedDomainName [out] trustedDomainNameLength [out] userType Chapter 13. A value that indicates the type of user that Access Manager will authenticate. A string that contains a comma-separated list of environment variable names that are requested by the Safer implementation.Parameters for the SaferAPIGetTrustedSignonWithEnv Function Table 76. Parameters and description for the SaferAPIGetTrustedSignonWithEnv Function Parameter [in] envVar Description An array of environment variable names and values that were retrieved from the Web server. A sequence of bytes that identifies the domain of the currently authenticated user. Configuring IBM Cognos Components to Use an Authentication Provider 345 . if there is one. This length should exclude the null terminator. SAFER_GUEST_USER A guest user. the envVar array contains only the end of array marker. This value does not need to be null-terminated. SAFER_ANONYMOUS_USER An anonymous user. This value is mandatory. The end of the list must be null-terminated. This value is optional. Note that the first time this API is called. This value is mandatory. if there is one. An integer value that indicates the length of the trustedSignonName. The following return values are required for Access Manager to successfully authenticate users: SAFER_NORMAL_USER A named user. A guest user account must exist and be enabled in the current namespace. OS signons must exist and be enabled in the current namespace.

Tip: Do not use colons (:) in the Namespace ID property. right-click Authentication. You can hide the namespace from users during logon. under Authentication. From the File menu. and click New resource > Namespace. You can also use it as a single signon mechanism to integrate IBM Cognos components with your security infrastructure. 5. Ensure that the versions of Java runtime environment (JRE) and Java Software Development Kit that you use are compatible with each other. In the Properties window. under the Authentication component. If you use supported versions of the JRE and Java Software Development Kit that are not compatible with each other. You can use a custom authentication provider to access and authenticate users to an alternate authentication source.2. Any additional configuration for authentication source access. or custom attributes are dependent on the custom authentication provider implementation. see the Custom Authentication Provider Developer Guide. click Save. specify a unique identifier for the namespace. select Custom Java Provider and then click OK. Test the connection to a new namespace. then the custom Java authentication provider that you configure will not appear in the list of namespaces in IBM Cognos Configuration. right-click the new authentication resource and click Test. 7. for the NamespaceID property. 8. single signon. type a name for your authentication namespace. under Security. 346 IBM Cognos Business Intelligence Version 10. For more information. open IBM Cognos Configuration. In the Type list. 4. In every location where Content Manager is installed. initializes. The new authentication provider resource appears in the Explorer window. you can configure IBM Cognos components to use it. 2. Results IBM Cognos loads. In the Explorer window. Specify the values for all other required properties to ensure that IBM Cognos can locate and use your existing authentication provider. 6. In the Explorer window.Configuring IBM Cognos to Use a Custom Authentication Provider If you implemented a custom Java authentication provider with your existing security infrastructure. 3. and configures the provider libraries for the namespace. Procedure 1. Configure a Custom Authentication Namespace You can configure IBM Cognos components to use a custom authentication namespace. In the Name box.1: Installation and Configuration Guide .

click the custom Java authentication provider. You also have the option of making custom user properties from the LDAP namespace available to IBM Cognos components. if required Enable secure communication to the LDAP server. 4. In each location where you configured a custom Java authentication provider. the LDAP authentication provider must construct the distinguished name (DN). IBM Directory Server.Hide the Namespace from Users During Login You can hide namespaces from users during login. if required Enable single signon between LDAP and IBM Cognos components. Configuring IBM Cognos Components to Use an Authentication Provider 347 . Procedure 1. it attempts to use the User lookup property to construct the DN. if required LDAP Mapping To bind a user to the LDAP server. “Configure an LDAP Namespace” on page 348 Make custom user properties available to IBM Cognos components. or Oracle Directory Server. under Security > Authentication. it uses the External identity mapping property to try to resolve the user's DN. For more information. In the Properties window. Results The namespace is not shown on the selection list that is presented at login. 3. 2. you may want to integrate single signon across systems but maintain the ability for customers to authenticate directly to IBM Cognos without being prompted to choose a namespace. From the File menu. If it cannot find the environment variable or the DN in the LDAP server. 4. 3. If the Use external identity property is set to True. Configuring IBM Cognos Components to Use LDAP You can configure IBM Cognos components to use an LDAP namespace as the authentication provider. click the box next to Selectable for authentication and select False. For example. If you want to bind users to the LDAP server. see the IBM Cognos Business Intelligence Administration and Security Guide. see “LDAP Mapping. 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. Chapter 13. Novell Directory Server. open IBM Cognos Configuration. click Save. You can have trusted signon namespaces without showing them on the namespace selection list that is presented when users log in. In the Explorer window. 2. Active Directory Server.” Procedure 1. You can use an LDAP namespace for users that are stored in an LDAP user directory.

1: Installation and Configuration Guide . 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. v For Oracle Directory Server.2. and folders as the Bind user.If users are stored hierarchically within the directory server. Procedure 1. you can configure the User lookup and External identity mapping properties to use search filters. you can specify whether to use bind credentials to search the LDAP directory server by configuring the Use bind credentials for search property. the LDAP provider binds to the directory server using the Bind user DN and password or using anonymous if no value is specified. 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. such as uid=${userID}. searches are performed using the bind user credentials or using anonymous if no value is specified. 348 IBM Cognos Business Intelligence Version 10. When the property is enabled. searches are performed using the credentials of the logged-on user. If you do not use external identity mapping. you must escape all special characters that are used in the DN. such as Active Directory Server or CA SiteMinder. for the properties User lookup. If you are configuring an LDAP namespace for a directory server other than LDAP. see the appropriate section: v For Active Directory Server. see Configure an LDAP Namespace for Novell Directory Server. see Configure an LDAP Namespace for IBM Directory Server. External identity mapping. groups. or Bind user DN and password. see Configure an LDAP Namespace for Oracle Directory Server. v For Novell Directory Server. In every location where you installed Content Manager. When the property is disabled. When the LDAP authentication provider performs these searches. Note that if you use a DN syntax. see the IBM Cognos Business Intelligence Administration and Security Guide. ou=mycompany. v For IBM Directory Server. such as (uid=${userID}). If you use a search syntax. for the properties User lookup or External identity mapping. 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.com. see Configure an LDAP Namespace for Active Directory Server. you must not escape special characters that are used in the DN. The LDAP user directory may be accessed from within another server environment. All users who log on to IBM Cognos using external identity mapping see the same users. For more information. it uses the filters you specify for the User lookup and External identity mapping properties. which is the default setting. open IBM Cognos Configuration. Configure an LDAP Namespace You can configure IBM Cognos components to use an LDAP namespace when the users are stored in an LDAP user directory. When an LDAP namespace has been configured to use the External identity mapping property for authentication.

8. click Save. 7. Chapter 13. 11. LDAP attributes that are mapped to the Name property in Folder mappings. Depending on the LDAP configuration. the search is done using anonymous. specify a unique identifier for the namespace. v Set Use bind credentials for search to True. The new authentication provider resource appears in the Explorer window. Specify the values for all other required properties to ensure that IBM Cognos components can locate and use your existing authentication provider. If no values are specified. If external identity mapping is enabled. 5. 10. If external identity mapping is not enabled. right-click Authentication. Check the mapping settings for required objects and attributes. Test the connection to a new namespace. 6. type a name for your authentication namespace. and configures the provider libraries for the namespace. initializes. under the Authentication component. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. Group mappings. the Name property must not be blank. 4. the LDAP authentication provider binds as anonymous. you must modify the necessary settings and change the values for all properties of the Active Directory objects. In the Properties window. In the Type list. right-click the new authentication resource and click Test. If you do not specify a user ID and password. In the Explorer window. and then click New resource > Namespace. 3. In addition. use bind credentials for searching the LDAP directory server by doing the following: v Ensure that Use external identity is set to False. If you do not use external identity mapping. under Security. In that case. v Specify the user ID and password for Bind user DN and password. Bind user DN and password are used only when a search filter is specified for the User lookup property. Bind user DN and password are used for all LDAP access. Configuring IBM Cognos Components to Use an Authentication Provider 349 . and anonymous access is enabled. when the user DN is established. for the Namespace ID property. then specify these values. From the File menu. under Authentication. Configure an LDAP namespace for Active Directory Server If you configure a new LDAP namespace for use with an Active Directory Server. Results IBM Cognos loads. subsequent requests to the LDAP server are executed under the authentication context of the end user.2. 9. In the Explorer window. you may have to change some default values to ensure successful communication between IBM Cognos components and the LDAP server. and Account mappings must be accessible to all authenticated users. click the appropriate namespace and then click OK. In the Name box.

In the Name box. In every location where you installed Content Manager. enter (sAMAccountName=${userID}) v If you use single signon. use the values that are specified in the following table. enter (sAMAccountName=${replace(${environment("REMOTE_USER")}. enter user@domain. Tip: Do not use colons (:) in the Namespace ID property. 6.2. v For Bind user DN and password. 3.Procedure 1. 2.1: Installation and Configuration Guide . If no values are specified. The following settings are examples: v For User lookup. 4. set the value to True.container description ou. LDAP advanced mapping values for use with Active Directory Server objects Mappings Folder LDAP property Object class Description Name Group Object class Description LDAP value organizationalUnit.organization. the LDAP authentication provider binds as anonymous. under the Authentication component. for the NamespaceID property. To configure the LDAP advanced mapping properties for use with the Active Directory Server objects. In the Properties window. Specify the values for all other required properties to ensure that IBM Cognos components can locate and use your existing authentication provider. Table 77. v Set Use bind credentials for search to True. enter objectGUID 7. open IBM Cognos Configuration. 9. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. enter (sAMAccountName=${environment("REMOTE_USER")}) If you want to remove the domain name from the REMOTE_USER variable. If you do not use external identity mapping. v Specify the user ID and password for Bind user DN and password. for Use external identity. 8. In the Explorer window. specify a unique identifier for the namespace. In the Type list.cn group description 350 IBM Cognos Business Intelligence Version 10. The new authentication provider resource appears in the Explorer window. v If you use single signon. right-click Authentication. and then click New resource > Namespace. 5. Using another variable can cause a security vulnerability. use bind credentials for searching the LDAP directory server by doing the following steps: v Ensure that Use external identity is set to False. under Security. "domain\\"."")}). type a name for your authentication namespace. v For Unique identifier.o. then specify these values. for External identity mapping. Important: Ensure that you use only the variable REMOTE_USER. click the appropriate namespace and then click OK.

you can configure Active Directory as your authentication source using an Active Directory namespace. From the File menu. Test the connection to a new namespace. If you have modified the schema.Table 77. LDAP attributes that are mapped to the Name property in Folder mappings. and Account mappings must be accessible to all authenticated users. Results IBM Cognos loads. click Save. you may have to make additional mapping changes. Related tasks: “Configuring IBM Cognos Components to Use Active Directory Server” on page 333 If you install Content Manager on a Microsoft Windows operating system computer. you must modify the necessary settings and change the values for all properties of the IBM Directory objects. right-click the new authentication resource and click Test. under Authentication. initializes. Chapter 13. In addition. Configure an LDAP Namespace for IBM Directory Server If you configure a new LDAP namespace for use with an IBM Directory Server. Configuring IBM Cognos Components to Use an Authentication Provider 351 . 11. the Name property must not be blank. and configures the provider libraries for the namespace. 10. In the Explorer window. Group mappings. LDAP advanced mapping values for use with Active Directory Server objects (continued) Mappings LDAP property Member Name Account Object class Business phone Content locale Description Email Fax/Phone Given name Home phone Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value member cn user telephonenumber (leave blank) description mail facsimiletelephonenumber givenname homephone mobile displayName pager unicodePwd postaladdress (leave blank) sn sAMAccountName These mapping properties represent changes that are based on a default Active Directory Server installation.

If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. and then click OK. use bind credentials for searching the LDAP directory server by doing the following: v Ensure that Use external identity is set to False. for the NamespaceID property. 2. 9. If no values are specified. 4. The new authentication namespace resource appears in the Explorer window. open IBM Cognos Configuration. right-click Authentication. specify cn=root 7. 6.cn groupofnames description member cn inetorgperson telephonenumber 352 IBM Cognos Business Intelligence Version 10. under the Authentication component. Specify the values for all other required properties to ensure that IBM Cognos can locate and use your existing authentication namespace. v Specify the user ID and password for Bind user DN and password.o. 8.container description ou. specify (cn=${userID}) v For Bind user DN and password. Tip: Do not use colons (:) in the Namespace ID property. specify a unique identifier for the namespace.2. In the Name box. Table 78. In the Properties window. If you do not use external identity mapping. 3. type a name for your authentication namespace. In the Type list. and then click New resource > Namespace. then specify these values. 5. use the values specified in the following table. v For User lookup.1: Installation and Configuration Guide .Procedure 1. LDAP advanced mapping values for use with IBM Directory Server objects Mappings Folder LDAP property Object class Description Name Group Object class Description Member Name Account Object class Business phone LDAP value organizationalunit. click LDAP. the LDAP authentication namespace binds as anonymous. v Set Use bind credentials for search to True.organization. To configure the LDAP advanced mapping properties for use with IBM Directory Server objects. under Security. In each location where you installed Content Manager. In the Explorer window.

In the Name box. From the File menu. you must modify the necessary settings and change the values for all properties of the Novell Directory objects. If you have modified the schema.Table 78. Chapter 13. right-click Authentication. the Name property must not be blank. Group mappings. In every location where you installed Content Manager. under Security. 3. and then click New resource > Namespace. 2. Procedure 1. In addition. 10. and Account mappings must be accessible to all authenticated users. open IBM Cognos Configuration. LDAP advanced mapping values for use with IBM Directory Server objects (continued) Mappings LDAP property Content locale Description Email Fax/Phone Given name Home phone Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value (leave blank) description mail facsimiletelephonenumber givenname homephone mobile cn pager userPassword postaladdress (leave blank) sn uid These mapping properties represent changes based on a default IBM Directory Server installation. In the Explorer window. Configure an LDAP Namespace for Novell Directory Server If you configure a new LDAP namespace for use with a Novell Directory Server. click Save. LDAP attributes that are mapped to the Name property in Folder mappings. Configuring IBM Cognos Components to Use an Authentication Provider 353 . type a name for your authentication namespace. you may have to make additional mapping changes.

Tip: Do not use colons (:) in the Namespace ID property. v Specify the user ID and password for Bind user DN and password. under the Authentication component. LDAP advanced mapping values for use with Novell Directory Server objects Mappings Folder LDAP property Object class Description Name Group Object class Description Member Name Account Object class Business phone Content locale Description Email LDAP value organizationalunit. 5. Table 79.o. such as cn=Admin.1: Installation and Configuration Guide .2. The new authentication namespace resource appears in the Explorer window. If no values are specified. 6. Specify the values for all other required properties to ensure that IBM Cognos can locate and use your existing authentication namespace.0=COGNOS 7. To configure the LDAP advanced mapping properties for use with Novell Directory Server objects. specify the base DN for an administration user. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches.cn groupofnames description member cn inetOrgPerson telephonenumber Language description mail 354 IBM Cognos Business Intelligence Version 10. use the values specified in the following table.organization. then specify these values. 8.container description ou. 9. specify a unique identifier for the namespace.4. v Set Use bind credentials for search to True. specify (cn=${userID}) v For Bind user DN and password. the LDAP authentication namespace binds as anonymous. click LDAP and then click OK. use bind credentials for searching the LDAP directory server by doing the following: v Ensure that Use external identity is set to False. for the Namespace ID property. If you do not use external identity mapping. v For User lookup. In the Properties window. In the Type list.

Configuring IBM Cognos Components to Use an Authentication Provider 355 . click LDAP and then click OK. the Name property must not be blank. If you have modified the schema. Procedure 1. 10. In every location where you installed Content Manager. and Account mappings must be accessible to all authenticated users. type a name for your authentication namespace. 3. Group mappings. under Security. For users to successfully log in to IBM Cognos Connection. under the Authentication component. In the Explorer window. you must modify the necessary settings and change the values for all properties of the Oracle Directory Server objects. open IBM Cognos Configuration. Chapter 13. The new authentication namespace resource appears in the Explorer window. LDAP advanced mapping values for use with Novell Directory Server objects (continued) Mappings LDAP property Fax/Phone Given name Home phone Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value facsimiletelephonenumber givenname homephone mobile cn pager (leave blank) postaladdress Language sn uid These mapping properties represent changes based on a default Novell Directory Server installation. 4. From the File menu. 2. In the Type list. they must have permission to read the ou and o attributes. you may have to make additional mapping changes. right-click Authentication. In addition. LDAP attributes that are mapped to the Name property in Folder mappings. In the Name box. and then click New resource > Namespace.Table 79. click Save. Configure an LDAP Namespace for Oracle Directory Server If you configure a new LDAP namespace for use with Oracle Directory Server.

Using another variable can cause a security vulnerability. use the values specified in the following table. the LDAP authentication namespace binds as anonymous. If you do not use external identity mapping. v For Unique identifier. 9. set the value to True. for the Namespace ID property.organization description ou. If no values are specified. type nsuniqueid 7. specify any attribute. v Specify the user ID and password for Bind user DN and password. use bind credentials for searching the LDAP directory server by doing the following: v Ensure that Use external identity is set to False.2. 8. Tip: Do not use colons (:) in the Namespace ID property. Specify the values for all other required properties to ensure that IBM Cognos can locate and use your existing authentication namespace. Table 80. such as the NT user domain ID or the user ID: (ntuserdomainid=$environment("REMOTE_USER")}) (uid=${environment("REMOTE_USER")}) Important: Ensure that you use only the variable REMOTE_USER. To configure the LDAP advanced mapping properties for use with Oracle Directory Server objects.5. enter (uid=${userID}) v If you use single signon. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. v Set Use bind credentials for search to True. v If you use single signon. then specify these values.1: Installation and Configuration Guide . In the Properties window. 6.o groupofuniquenames description uniquemember cn inetorgperson telephonenumber preferredlanguage description mail facsimiletelephonenumber givenname homephone 356 IBM Cognos Business Intelligence Version 10. specify a unique identifier for the namespace. for External identity mapping. LDAP advanced mapping values for use with Oracle Directory Server objects Mappings Folder LDAP property Object class Description Name Group Object class Description Member Name Account Object class Business phone Content locale Description Email Fax/Phone Given name Home phone LDAP value organizationalUnit. for Use external identity. The following settings are examples: v For User lookup.

4. Repeat the preceding two steps for each custom parameter. From the File menu. For more information. 5. If you have modified the schema. For more information about session parameters. under Security > Authentication. Procedure 1. LDAP advanced mapping values for use with Oracle Directory Server objects (continued) Mappings LDAP property Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value mobile cn pager userPassword postaladdress preferredlanguage sn uid These mapping properties represent changes based on a default Oracle Directory Server installation. In addition. and click the edit icon. The custom properties are available as session parameters through Framework Manager. and Account mappings must be accessible to all authenticated users. Click the Value column. click the LDAP namespace. In each location where you installed Content Manager. 7. 3. click Add. click Save. see the Framework Manager User Guide. In the Explorer window. 8. and type the name you want IBM Cognos components to use for the session parameter. open Cognos Configuration. the Name property must not be blank. Click the Name column. 6. see the IBM Cognos Business Intelligence Administration and Security Guide. LDAP attributes that are mapped to the Name property in Folder mappings. You can use the command blocks with Oracle lightweight connections and virtual private databases.Custom properties window. 10. You can also use the custom properties inside command blocks to configure Oracle sessions and connections. In the Value . you must add these attributes as custom properties for the LDAP namespace. click in the Value column for Custom properties. you may have to make additional mapping changes. Click OK. To configure this. In the Properties window. 2. Configuring IBM Cognos Components to Use an Authentication Provider 357 . Make Custom User Properties for LDAP Available to IBM Cognos Components You can use arbitrary user attributes from your LDAP authentication provider in IBM Cognos components.Table 80. Chapter 13. Group mappings. and type the name of the account parameter in your LDAP authentication provider.

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. Next.2.db files.cert -t C. LDAPS prevents sensitive information in the directory server and the LDAP credentials from being sent as clear text. which is available from the FTP Web site at Mozilla. To enable LDAPS.6.db and cert7.9.7 of the NSPR library. The appropriate certutil tool is available from the FTP Web site at Mozilla. 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: v For a CA certificate. Before you begin IBM Cognos works with both the cert8. 2. You must use the certutil tool from Netscape OpenSource toolkit NSS_3_11_4_RTM to create the certificate database. and server_certificate is the prefix of the directory server certificate file. 3. type certutil -A -n certificate_name -d certificate_directory -i CA. v 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. create a certificate database to contain the certificates. including those from the certutil tool that is provided with Microsoft Active Directory.db file in the new directory. The server certificate must be a copy of either v 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. From the File menu. 358 IBM Cognos Business Intelligence Version 10. Finally.db file and a key3.1: Installation and Configuration Guide . This command creates a cert8.C. Procedure 1. IBM Cognos does not accept other versions of cert8.db versions of the client certificate database. type certutil -A -n certificate_name -d certificate_directory -i server_certificate. such as the CA name or host name. configure the directory server and the IBM Cognos LDAP namespace to use LDAPS. install a server certificate that is signed by a certificate authority in the directory server. Create the certificate database by typing certutil -N -d certificate_directory where certificate_directory is the directory that you created in step 1.C v For a directory server certificate. click Save. You must also use version 4. Create a directory for the certificate database.cert -t P where certificate_name is an alias that you assign.

for the Host and port property. Repeat steps 6 to 11 on every other location where Content Manager is installed. revise the properties. If the test fails. groups. right-click the LDAP namespace and click Test.4. For more information. For the SSL certificate database property. 12. If you want IBM Cognos components to work with applications that use Java or application server security. Replace operation The replace operation returns a copy of the string with all occurrences of the old substring replaced by the new substring. Characters such as \ and " need escaping. Enabling Single Signon Between LDAP and IBM Cognos Components You achieve single signon to IBM Cognos components by configuring the External Identity mapping property. Configuring IBM Cognos Components to Use an Authentication Provider 359 . Copy the certificate database directory to the c10_location/configuration directory on every location where Content Manager is installed. 5. From the File menu. In the Explorer window. In the Explorer window. click the LDAP namespace. The following rules apply: v The character \ escapes the characters in the function parameters. 6. specify the path to the cert7. The External Identity mapping can refer to a CGI environment variable or an HTTP header variable. In the Properties window. You can apply limited expression editing to the External Identity mapping property using the replace operation. 11. change the port to the secure LDAPS port. 7. the External Identity mapping can refer to the userPrincipalName session variable.db file. see the online help for IBM Cognos Configuration. the LDAP provider binds to the directory server using the Bind user DN and password or using anonymous if no value is specified. and folders as the Bind user. 9. Configure the directory server to use LDAPS and restart the directory server. Include the token ${environment("USER_PRINCIPAL")} in the value for the property. you can configure the External identity mapping property to obtain the user ID from the Java user principal. The resolved value of the External Identity mapping property at runtime must be a valid user DN. start IBM Cognos Configuration. In each Content Manager location where you configured the LDAP namespace to use the directory server. see the documentation for the directory server. ensuring that the correct certificate is used. For more information. 10. under Security > Authentication. When an LDAP namespace is configured to use the External Identity mapping property for authentication. 8. click Restart. From the Actions menu. All users who log on to IBM Cognos using external identity mapping see the same users. In the case of an application server gateway or dispatcher entry pointing to IBM Cognos components. click Save. Chapter 13.

After you configure the SiteMinder namespace in IBM Cognos Configuration. new)} Parameters for the Replace Operation Table 81.)} ${replace(${environment("REMOTE_USER")}.1: Installation and Configuration Guide . CA SiteMinder configured for more than one user directory If your CA SiteMinder environment is configured for more than one user directory. old .x agents. This does not mean that you must configure CA SiteMinder to set REMOTE_USER. Examples ${replace(${environment("REMOTE_USER")}. Parameters and description for the Replace Operation Parameter str old new Description The string to search. Syntax ${replace(str . The 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 CA SiteMinder environment. The substring that replaces the old substring."NAMERICA\\". 360 IBM Cognos Business Intelligence Version 10.2. The substring to be replaced by the new substring. ensure that the External identity mapping property is enabled and that you include the REMOTE_USER token in property value."")} Configure IBM Cognos components to use CA SiteMinder You can configure IBM Cognos components to use a CA SiteMinder namespace as an authentication source."NAMERICA\\". you must also add a corresponding LDAP or Active Directory Server namespace to IBM Cognos Configuration for each user directory that is defined in CA SiteMinder. When you configure a corresponding Active Directory namespace. Note: The authentication provider uses the CA SiteMinder Software Development Kit to implement a custom agent. ensure that the singleSignOnOption property is set to IdentityMapping. The custom agent deployment requires that you set the Agent Properties in the CA SiteMinder Policy server administration console to support 4. you must use the SiteMinder namespace type in IBM Cognos Configuration.v Nested function calls are not supported. v Special characters are not supported. When you configure a corresponding LDAP namespace.

For more information. Chapter 13. Ensure that SetRemoteUser is activated. You can hide namespaces from users during login. you can configure the appropriate LDAP or Active Directory namespace. Configuring the SiteMinder namespace If you configured CA SiteMinder for more than one user directory. Using another variable can cause a security vulnerability. see “Enabling single signon between Active Directory Server and IBM Cognos Components to use REMOTE_USER” on page 341. see “Enabling single signon between Active Directory Server and IBM Cognos Components to use REMOTE_USER” on page 341. After you add the SiteMinder namespace. Important: Ensure that you use only the variable REMOTE_USER. When you configure a corresponding LDAP namespace. You can have trusted signon namespaces without showing them on the namespace selection list that is presented when users login. For example. When you configure the Active Directory namespace. CA SiteMinder configured with only one user directory If your CA SiteMinder environment is configured with only one user directory. you must use the SiteMinder namespace type in IBM Cognos Configuration. In this case. Important: Ensure that you use only the variable REMOTE_USER. For example. or you can configure the SiteMinder with one user directory. ensure that the External identity mapping property is enabled and that you include the REMOTE_USER token in property value. Using another variable can cause a security vulnerability. you can configure IBM Cognos components with an LDAP namespace or with one SiteMinder namespace. you must also add a corresponding LDAP namespace for each user directory in your CA SiteMinder environment. you want to integrate single sign-on across systems but maintain the ability for customers to authenticate directly to IBM Cognos without being prompted to choose a namespace. Configuring IBM Cognos Components to Use an Authentication Provider 361 . In this case. you do not have to use the SiteMinder namespace type in IBM Cognos Configuration. If the CA SiteMinder user directory is Active Directory.For more information. if the CA SiteMinder user directory is LDAP. If you want to use the user directory as your authentication source directly instead of configuring a SiteMinder namespace. referring to one user directory that is an LDAP namespace. you can use an Active Directory namespace or an LDAP namespace that is configured for use with Active Directory. You can also use the SiteMinder namespace type if users are stored in an LDAP server or an Active Directory server. verify the Agent Configuration Object properties in CA SiteMinder Policy Server. you can use the user directory as your authentication source by configuring the appropriate namespace. ensure that the singleSignOnOption property is set to IdentityMapping.

362 IBM Cognos Business Intelligence Version 10. specify a unique identifier for the namespace. 14. In the Namespace ID property. In the Properties window. Note: If you do not want the namespace name to appear to users when they are logging in. Specify values for the other required properties. select the SiteMinder and then click OK.2. under Security > Authentication. Note: Do not use a colon (:) in the identifier. right-click Authentication. append the directory that contains the CA SiteMinder library file to the appropriate library path environment variable. and click New resource > SiteMinder Policy Server.Before you begin To use the SiteMinder namespace.so smagentapi. In the Explorer window. LIBPATH 2. Table 82. In the Name box. type a name for your authentication namespace. type a value for the Namespace ID reference property. PATH Open IBM Cognos Configuration. CA SiteMinder library files Operating system Solaris and AIX Microsoft Windows 64-bit Microsoft Windows 32-bit CA SiteMinder library file libsmagentapi. set the Selectable for authentication property to False. you must obtain the required CA SiteMinder library files. v For Microsoft Windows operating systems. 3. Select the namespace that you added. In the Properties window. and add the files to the appropriate library path for your operating system. right-click the namespace that you added.dll smerrlog. 7. v For Solaris operating systems.1: Installation and Configuration Guide . 9.dll smagentapi. 10. right-click the new SiteMinder policy server that you added and click New resource > User directory. In the Explorer window. 5. which are shown in the following table. specify the Host property and any other property values you want to change. In the Name box. In the Explorer window. 12. In the Name box. 13. On the computer where you installed Content Manager. 6.dll Procedure 1. 15. LD_LIBRARY_PATH v For AIX operating systems. and click New resource > Namespace. 8. 11. 4. type a name for the policy server and click OK. In the Type list. type a name for the user directory and click OK. under Security. Configure a user directory for each user directory in the SiteMinder policy server. Important: The name of the user directory must match the policy server name.

right-click the new authentication resource and click Test. For more information. In the Explorer window. type the value that corresponds to the Tivoli Directory Server. you must do the following: v You must be running Tivoli Directory Server. Configuring IBM Cognos Components to Use an Authentication Provider 363 . Before you begin Before you configure the RACF namespace. right-click Authentication. Chapter 13. open IBM Cognos Configuration. Enable single signon between the RACF provider and IBM Cognos components Configuring a RACF Namespace You can configure a Resource Access Control Facility (RACF) namespace using IBM Cognos Configuration. to access the SDBM (RACF) database. Configuring IBM Cognos to Use a RACF Provider for Authentication If you use a Resource Access Control Facility (RACF) provider for authentication in your enterprise environment. 18. under Authentication. under the Authentication component. For the Base Distinguished Name property. type the value that matches the suffix that is configured for SDBM in the Tivoli Directory Server. Test the connection to a new namespace. specify a unique identifier for the namespace. 17.16. type a name for your authentication namespace. For the Host and port property. Ensure that you use the same value for the Namespace ID property that you use for the Namespace ID property for the SiteMinder namespace. Configure a corresponding LDAP or Active Directory namespace for each user directory. under Security. Configure secure communication 3. see the topic about configuring Tivoli Access Manager for LDAP in the IBM Information Center. do the following: v In the Explorer window. you can also use it for authentication in IBM Cognos products. To create the namespace. Procedure 1. The new authentication provider resource appears in the Explorer window. v Tivoli Directory Server must be configured for LDAP. 5. Do not use colons (:) in the Namespace ID property. Procedure 1. v In the Name box. 3. and click New resource > Namespace. In the location where you installed Content Manager. click RACF and then click OK. Configure IBM Cognos components to use a RACF namespace 2. v In the Type list. 2. 4. for the Namespace ID property. In the Properties window. Click File > Save.

In every location where you installed Content Manager. Procedure 1. All users who log on to IBM Cognos using identity mapping see the same users. Click the value column for Binding credentials and then click the edit icon. 364 IBM Cognos Business Intelligence Version 10. under Authentication. You achieve single signon by configuring identity mapping in IBM Cognos Configuration. change Enable identity mapping to True. configure WebSphere to set REMOTE_USER. 7. and folders as the binding user. When a RACF namespace is configured to use identity mapping for authentication. If you are using an SSL connection to the RACF provider. under Security. 7. In IBM Cognos Configuration. 5. click Restart. open IBM Cognos Configuration. 2. 6.2. Configure IBM Cognos to use SAP To use an SAP server as your authentication provider. groups. click in the value column and select the value from the drop-down list. restart the service: v In the Explorer window. and simplify user identity management across the network. and select the service. Important: Ensure that you use only the variable REMOTE_USER. configuring IBM WebSphere Application Server to set the REMOTE_USER. and then configuring WebSphere to authenticate against RACF.1: Installation and Configuration Guide . 9. expand IBM Cognos services. specify the User ID and Password. 8. the RACF namespace binds to the RACF provider using the binding credentials or anonymously if no binding credentials are specified. avoid the need for multiple signons. Using another variable can cause a security vulnerability. 3. right-click Authentication.6. Test the connection to a new namespace. 4. In the Explorer window. set the Enable SSL property to true. Using the WebSphere documentation. In the Explorer window. click Save. In the Resource properties window. In the Value . To map to RACF account properties such as email and phone number.Binding credentials dialog box. and then click the RACF namespace. v From the Actions menu. for the Base segment DATA and the TSO segment USERDATA properties under Account mappings. 8. Enabling single signon between RACF and IBM Cognos Enable single signon between the Resource Access Control Facility (RACF) provider and IBM Cognos components to simplify the authentication process for users. right-click the new authentication resource and click Test. Using the WebSphere documentation. you must use a supported version of SAP BW. configure WebSphere to authenticate using the RACF provider. From the File menu.

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 components: users or administrators.

SAP Authorization Settings for IBM Cognos Users
The authorization objects in the following table are required for any IBM Cognos user.
Table 83. SAP authorization settings for IBM Cognos users Authorization object S_RFC Authorization check for RFC access Name of RFC to be protected RFC1 RS_UNIFICATION, SDTX, SH3A, SU_USER, SYST, SUSO Type of RFC to be protected S_USER_GRP User Master Maintenance: User Groups Name of user group * Activity FUGR 03 Field Activity Value

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

SAP Authorization Settings for IBM Cognos Administrators
If users perform administrative tasks and searches for users and roles, the values from the following table must be added to the S_RFC authorization object in addition to the values for IBM Cognos users.
Table 84. SAP authorization settings for IBM Cognos administrators Authorization object S_RFC Authorization check for RFC access RFC_NAME Type of RFC object to be protected PRGN_J2EE, SHSS, SOA3 FUGR Field Activity Value 16

Some of the values shown, such as *, are default values that you might want to modify for your environment.

Chapter 13. Configuring IBM Cognos Components to Use an Authentication Provider

365

Connectivity Between SAP BW and IBM Cognos on UNIX
To configure connectivity between SAP BW and IBM Cognos 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: v Solaris LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<librfccm.so_directory> v HP-UX SHLIB_PATH=$SHLIB_PATH:<librfccm.sl_directory> v AIX LIBPATH=$LIBPATH:<librfc.a_directory>

Configure an SAP Namespace
You can configure IBM Cognos components to use an SAP server as the authentication source.

Before you begin
If you installed your IBM Cognos product on a 64-bit server, you must also manually copy the SAP RFC library files to the IBM Cognos installation directory.

Procedure
1. If running on a 64-bit server, do the following: v Go to the SAP installation directory on the 64-bit server. v Copy all 64-bit SAP RFC library files to c10_64_location\bin64, where c10_64_location is the directory where you installed the IBM Cognos server. v Copy all 32-bit SAP RFC library files to c10_64_location\bin. 2. If running on a 32-bit server, copy all 32-bit SAP library files from the SAP installation directory to the c10_64_location\bin64 directory. 3. In the location where you installed Content Manager, open IBM Cognos Configuration. 4. In the Explorer window, under Security, right-click Authentication, and click New resource > Namespace. 5. In the Name box, type a name for your authentication namespace. 6. In the Type list, click SAP and then click OK. The new authentication provider resource appears in the Explorer window, under the Authentication component. 7. In the Properties window, for the Namespace ID property, specify a unique identifier for the namespace. Important: Do not use colons (:) in the Namespace ID property. 8. Specify the values for all required properties to ensure that IBM Cognos 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. 9. If the SAP system encodes the contents of cookies, enable the decode tickets feature: v In the Properties window, for Advanced properties, click the Value and then click the edit icon.

366

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

v Click Add. v Enter the name URLDecodeTickets and enter the value true v Click OK. All SAP logon tickets will be decoded by the SAP namespace before establishing a connection. 10. From the File menu, click Save. 11. Test the connection to a new namespace. In the Explorer window, under Authentication, right-click the new authentication resource and click Test.

Enable Single Signon Between SAP and IBM Cognos
You can enable single signon between SAP Enterprise Portal and IBM Cognos 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: v login/accept_sso2_ticket = 1 v login/create_sso2_ticket = 1 v login/ticket_expiration_time = 200

Delete an Authentication Provider
If they are no longer required, you can delete namespaces that you added, or unconfigure namespaces that IBM Cognos components detected. 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 IBM Cognos Business Intelligence Administration and Security Guide.

Procedure
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 in that location. 4. From the File menu, click Save. 5. Repeat steps 1 to 4 for each location 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 IBM Cognos Business Intelligence Administration and Security Guide.

Results
After you delete a namespace, it appears as Inactive in the portal.

Chapter 13. Configuring IBM Cognos Components to Use an Authentication Provider

367

368

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

Chapter 14. Using an application server other than Tomcat
IBM Cognos Business Intelligence installs and uses Tomcat as the application server by default. However, you can choose to run IBM Cognos BI in another supported application server instead. The application servers you can use to run IBM Cognos BI in include the following: v IBM WebSphere Application Server v Oracle WebLogic Server v Red Hat JBoss v SAP NetWeaver For IBM Cognos BI for Linux on System z, IBM WebSphere Application Server is supported. To ensure that your product works properly, apply all minimum required operating system patches and use only the versions of other software that are supported for an IBM Cognos product. You can also choose to run the IBM Cognos Servlet Gateway on a supported application server instead of using a Web server. When using the servlet gateway, your environment does not require a Web server. The application server and the servlet gateway replace the functions provided by the Web server and other IBM Cognos gateways. To set up IBM Cognos BI to run on your application server, do the following: v Create a separate JVM instance, if necessary. v v v v v v v v v v v Check that IBM Cognos components are properly set up. Back up any existing IBM Cognos data and encryption keys, if required. Set environment variables. Add user role to enable single signon for collaboration with IBM Connections Configure IBM Cognos components to run within the application server. Identifying the JDK for WebLogic 9 on AIX , if necessary. Change the application server startup script, if necessary. Configure application server properties and deploy IBM Cognos BI. Enable SSL, if required. Configure the web server. Unregister dispatchers that are no longer used.

Create a separate JVM instance
When possible, IBM Cognos Business Intelligence must be installed in a Java Virtual Machine (JVM) instance that is separate from the application server admin processes to isolate both IBM Cognos BI and the administrative functions of the application server.

© Copyright IBM Corp. 2005, 2013

369

Running IBM Cognos BI in a separate JVM instance eliminates potential Java class or system resource conflicts and ensures that IBM Cognos BI does not affect any existing customer applications. An isolated JVM instance can be established by creating one of the following: v a separate server instance in IBM WebSphere v a separate managed server in Oracle WebLogic v a separate server instance for Red Hat JBoss v a separate Java instance for SAP NetWeaver If you are using the IBM Cognos Servlet Gateway, it must be run in an instance that is separate from IBM Cognos BI.

Set JVM parameters for performance
To improve performance of IBM Cognos BI in your application server, you can apply some or all of the following Java virtual machine (JVM) settings. You do not need to change these settings if you are using Tomcat as the application server. For example, you can: v Include the -Xcompressedrefs option if you are using a 64-bit application server. This option causes object references to be stored as a 32-bit representation, which reduces the 64-bit object size to be the same as a 32-bit object. v Include the -Xdump option to control how dump agents and dumps are used. For example, include the following options: – -Xdump:heap+system:none – -Xdump:system:events=gpf+abort,range=1..2,request=
serial+compact+prepwalk

– -Xdump:system:events=systhrow+throw,filter=java/lang/OutOfMemory*,
range=1..2,request=serial+compact+prepwalk

Check the setup of IBM Cognos components
Ensure that the following is done before you set up IBM Cognos components to run on the application server: v IBM Cognos components are installed. v Before you start IBM Cognos Business Intelligence, the database for the content store must be set up. Install and configure the database clients, if required, and then test the database connectivity. v The application server is installed and operational on each computer where IBM Cognos components are installed. For more information about installation, see your application server documentation. v The fully qualified installation location of all fonts is specified on all Application Tier Component computers. You specify this location in IBM Cognos Configuration. By default, the installation location does not use a fully qualified path. v The application server user account has full access permissions for the IBM Cognos installation. Tip: Create a new UNIX or Linux operating system group named cognos. This group must contain the user that starts the application server and the user that

370

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

owns the IBM Cognos files. Change the group ownership of the IBM Cognos files to the cognos 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.

Back up existing IBM Cognos information
You must back up existing IBM Cognos information if IBM Cognos Business Intelligence components are running on an application server (including Tomcat) and you are changing to an application server that ships with its own JVM. You must also back up existing IBM Cognos information if you must change the JVM you are using. Note: You must back up existing IBM Cognos information within the working environment prior to upgrade. Before configuring IBM Cognos BI components to run on the new application server or JVM, you must back up v content store data by creating a deployment export. v configuration information by exporting it. Any encrypted data is decrypted during the export. v cryptographic keys by saving them to an alternate location. New cryptographic keys must be created using the same JVM that the application server uses. Because these keys can be created only if the previous keys are deleted, it is important to back up the previous keys. To ensure the security and integrity of your IBM Cognos data, back up the content store, configuration information, and cryptographic keys to a directory that is protected from unauthorized or inappropriate access. Tip: To check if any cryptographic keys exist, look in the c10_location/ configuration directory. Cryptographic keys exist if this directory includes the following subdirectories: csk, encryptkeypair or signkeypair.

Procedure
1. If data exists in the content store, start the IBM Cognos service and export the entire content store using the Deployment tool. For more information, see the topic about creating an export deployment specification in the IBM Cognos Business Intelligence Administration and Security Guide. 2. In IBM Cognos Configuration, from the File menu, click Export As and save the configuration information in a decrypted format. When naming the file, use a name such as decrypted.xml. Export the data to a directory that is protected from unauthorized or inappropriate access because passwords are stored in plain text. You are prompted to acknowledge that the export is an unsecure operation. 3. Stop the IBM Cognos service: v If you use Tomcat, stop the IBM Cognos service and close IBM Cognos Configuration. v If you use an application server other than Tomcat, shut down IBM Cognos BI in your environment.

Chapter 14. Using an application server other than Tomcat

371

4. Back up any existing cryptographic keys by saving the appropriate files and directories to an alternate location that is secure. The files are v c10_location/configuration/cogstartup.xml v c10_location/configuration/caSerial v c10_location/configuration/cogconfig.prefs v c10_location/configuration/coglocale.xml The directories are v c10_location/configuration/csk v c10_location/configuration/encryptkeypair v c10_location/configuration/signkeypair 5. Delete the caSerial and cogconfig.prefs files and the three directories: csk, encryptkeypair, and signkeypair. 6. Replace the c10_location/configuration/cogstartup.xml file with the file that contains the data exported from IBM Cognos Configuration (for example, decrypted.xml). In the c10_location/configuration directory, the file must use the name cogstartup.xml. The information in this file will be automatically re-encrypted using new cryptographic keys when you save the configuration in IBM Cognos Configuration.

Set environment variables
You must set environment variables to identify the location of the Java Virtual Machine (JVM) environment and the library path. You can set environment variables using any of the following methods: v On Microsoft Windows operating system, set a system or user variable, or edit the application server's startup script. If you set a user variable, ensure that you set it for the user account that will run the application server, or administration console. v On UNIX and Linux operating systems, set an environment variable in the user profile, or edit the application server's startup script. For information about editing an application server's startup script, see “Change the application server startup script” on page 378. Tip: Most application server versions ship with a script specifically intended for setting environment variables. For example, some IBM WebSphere versions ship with setupCmdLine.bat or setupCmdLine.sh. These scripts can be modified to set appropriate values for use with IBM Cognos components. Most of these scripts set the JAVA_HOME environment variable by default.

Procedure
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 the JAVA_HOME environment variable must be set to reference it.

372

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

IBM Cognos Configuration uses this variable to create encryption keys for IBM Cognos components that are compatible with the JVM used by the application server. For example, for WebLogic under Windows, the JVM used by the application server is specified as: drive:/WebLogic_location/jdkversion 2. Append c10_location/bin to the appropriate environment variable from the following table.
Table 85. Application server environment variables Operating system Windows AIX Solaris and Linux HP-UX Environment variable PATH LIBPATH LD_LIBRARY_PATH SHLIB_PATH

The library path environment variable is used to locate the IBM Cognos library files. Note: Ensure that the 32-bit or 64-bit library files are set in your environment variables. For a 64-bit version of IBM Cognos BI, the 64-bit library files must be listed first. For a 32-bit version, the 32 bit library files must be listed first. Tip: To install multiple instances of IBM Cognos Business Intelligence on a single server, set the PATH, LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH variable within the application server instance scope and not as a global variable to ensure that each instance has a unique value.

Adjusting the default connection time-out value for IBM Cognos Business Intelligence
The default setting for the connection time-out value used in IBM Cognos Business Intelligence is 25 seconds. Some application servers, such as IBM WebSphere, use a shorter value. To avoid conflicts between the connection time-out settings, change the connection time-out value in IBM Cognos BI. The value must be smaller than the setting that is configured in the application server.

Procedure
1. Open thec10_location/configuration/BIBusTK_Config.xml file in a text editor. 2. Find the following string:
<BIBUSTK_CONNECTION_TIMEOUT>25000</BIBUSTK_CONNECTION_TIMEOUT>

3. Change the value to 90% of the value specified for the application server. For example, WebSphere uses a default connection time-out value of 30 seconds. Calculate 90% of 30 seconds, which is 27 seconds. Change the string to
<BIBUSTK_CONNECTION_TIMEOUT>27000</BIBUSTK_CONNECTION_TIMEOUT>

4. Save the file. 5. Repeat these steps in each location where you installed IBM Cognos BI.

Chapter 14. Using an application server other than Tomcat

373

Add user role to enable single signon between IBM WebSphere profiles
If you are using collaboration with IBM Connections, and you want to enable single signon between your IBM WebSphere profiles, you must modify two IBM Cognos Business Intelligence configuration files before you build and install your IBM Cognos BI application. To set up single signon, you must set a shared password between the profile you are using for Lotus® Connections and the profile you are using for IBM Cognos BI. For more information, see the IBM WebSphere http://publib.boulder.ibm.com/ infocenter/wasinfo/v6r1/index.jsp. Single signon between IBM Cognos BI and IBM Connections is enabled by IBM WebSphere. This means that you must access IBM Cognos BI directly through the dispatcher, rather than through your Web server. For example, instead of accessing the IBM Cognos BI application from a URL such as http://webserver_name/ ibmcognos, you will have to access it though the dispatcher URL, such as http://WebSphere_servername.domain:port/p2pd/servlet/dispatch/ext, where port is the port number of the IBM WebSphere profile where you have installed IBM Cognos BI. The URL is the same as that for your Dispatcher URIs for gateway in IBM Cognos Configuration.

Procedure
1. Go to the cognos_install_location\war\p2pd directory. 2. Open the file named application.xml.template in a text editor. 3. Edit the application section to include the following elements:
<application> <display-name>IBM Cognos 10</display-name> <module> <web> <web-uri>@p2pdwar@</web-uri> <context-root>@p2pd@</context-root> </web> </module> <security-role id="SecurityRole_Cognos_BI_User"> <description/> <role-name>BI User</role-name> </security-role> </application>

4. 5. 6. 7.

Save and close the file. Go to the cognos_install_location\webapps\p2pd\WEB-INF directory. Open the file named web.xml.withCM in a text editor. After the last servlet-mapping section, and before the </web-apps> element, add the following:
<security-constraint> <web-resource-collection> <web-resource-name>Cognos Dispatcher</web-resource-name> <url-pattern>/servlet/dispatch/ext/*</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>BI User</role-name> </auth-constraint> </security-constraint> <login-config>

374

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

<auth-method>BASIC</auth-method> <realm-name>Cognos Dispatcher</realm-name> </login-config> <security-role> <role-name>BI User</role-name> </security-role>

8. Save and close the file.

Results
You can now configure IBM Cognos components to run within IBM WebSphere.

Configure IBM Cognos components to run within the application server
IBM Cognos Business Intelligence must be configured with the application server configuration information, and the configuration must be saved to create new cryptographic keys. IBM Cognos Configuration uses the Java Virtual Machine (JVM) that is defined by the JAVA_HOME environment variable. You must set the JAVA_HOME environment variable to the JVM supplied or used by the application server before you run IBM Cognos Configuration. If you are using IBM WebSphere, you can use the Build Application Wizard to create the application as well as install it. You do not have to use the IBM WebSphere administration console to set properties or install the application. For more information, see “Use the Build Application Wizard to build and install IBM Cognos on IBM WebSphere Application Server” on page 377.

Procedure
1. Stop the IBM Cognos service if it is running. 2. Start IBM Cognos Configuration: If you have existing incompatible encryption keys, you will be prompted to automatically generate new ones at this time. Tip: Ensure that the existing keys are backed up to a secure location before proceeding. There is no undo action available after you generate new keys. 3. Use the Build Application Wizard to create the application file that will be deployed to the application server. To launch the Build Application Wizard from IBM Cognos Configuration, under Actions, click Build Application Files. The wizard allows you to select the type of application to build and the context root used to access the application. You must build the application file on the same computer on which you will be deploying the file. The context root value entered in the wizard must be the same as is entered in the Environment tab, and used to deploy to the application server. For IBM Cognos BI, the default context root and application directory name is p2pd, which can be used in most cases. For the IBM Cognos Servlet Gateway, the default context root and application directory name is ServletGateway. Other default application deployment values, such as the application name, may be changed to better suit your environment. Note: If you are installing IBM Cognos BI on IBM WebSphere and using collaboration with IBM Connections, ensure that you select Include static files
Chapter 14. Using an application server other than Tomcat

375

from the Webcontent folder. This will allow you to access the application without using a Web server and allow you to configure single signon between IBM Cognos BI and IBM Connections. Tip: It is not necessary to rebuild or redeploy the archive file when you make configuration changes because configuration information is stored externally to the application. For WebLogic and JBoss, you can use the Build Application wizard in IBM Cognos Configuration to build the application to an expanded directory. For example, for WebLogic, you put the application in C:\bea\user_projects\ domains\apps\p2pd, where p2pd is the name of the application. When deploying the application from the WebLogic Administration Console, you would select the p2pd directory. For JBoss, if you use the Expand files into a folder option, you must include the .war extension in the name of the folder where the wizard will create the p2pd application. When the wizard prompts for the folder location, go to JBoss_location/server/instance_name/deploy and create a folder named p2pd.war. For information about which type of application file, WAR, EAR or expanded directory, is supported in your environment, see your application server documentation. 4. In the Explorer window of IBM Cognos Configuration, expand Environment and then change the following properties to use the port number and host name or IP address of the server where the IBM Cognos BI component and application server are installed. v All URIs for the dispatcher, including – Dispatcher URIs for Gateway – External dispatcher URI – Internal dispatcher URI – Dispatcher URI for external applications v Gateway URI v Content Manager URIs The application server must be configured to listen on the host name or IP address entered in the URI. For more information, see your application server documentation. If you change the context root from the default value of p2pd, you must change the context root portion of the URI as well. Important: If you are using collaboration with IBM Connections, ensure that you use the full domain name of the computer where your services are running for the URIs. If you do not include the domain, IBM Connections will not allow access as it cannot verify the domain from which the access is coming. For example, you must change values such as http://localhost:9300 to use the server name, domain, and the transport port number for your IBM WebSphere profile. If you have IBM WebSphere installed on a computer named MyComputer that is running on your domain named MyCompanyName.com, then localhost must be changed to MyComputer.MyCompanyName.com. If you are using the default IBM WebSphere transport port number, 9080, then http://localhost:9300/ would be http:// MyComputer.MyCompanyName.com:9080/. 5. Under Environment > IBM Cognos services, right-click IBM Cognos, and then click Delete.

376

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

The entry for the IBM Cognos service is used to configure environment settings for running under Tomcat. The entry is not required when using a different application server. 6. Complete other required configuration changes such as v specifying properties for the Content Manager database v entering user IDs and passwords If you used the default settings for the IBM Cognos installation, you may only have to make minor changes to the default configuration settings. 7. Save the configuration. New cryptographic keys are created using the JVM that is defined by the JAVA_HOME variable. 8. Close IBM Cognos Configuration.

Use the Build Application Wizard to build and install IBM Cognos on IBM WebSphere Application Server
Use the Build Application Wizard to build, install, and configure your IBM Cognos application on IBM WebSphere Application Server. You can perform all of the actions in sequence, or you can perform them individually. The following task describes the process in sequence.

Before you begin
IBM WebSphere Application Server must be installed on the same computer as you have installed IBM Cognos BI. You must set the JAVA_HOME environment variable to the JVM supplied or used by the application server before you run IBM Cognos Configuration. IBM WebSphere Application Server does not need to be running to use the Build Application Wizard to install IBM Cognos BI.

Procedure
1. Start IBM Cognos Configuration. 2. In the Explorer window, under IBM Cognos services, right-click IBM Cognos, and click Delete. 3. Right-click IBM Cognos Service, click New Resource > Configuration. 4. Enter a Name, and select WebSphere in the Type box. 5. Click OK. 6. In the WebSphere Application Server location box, click the browse icon, and select the location of your IBM Websphere Application Server installation. 7. In the Profile box, select the name of the profile into which you want IBM Cognos BI installed. You can enter a new name in the Profile box. IBM Cognos Configuration will create a new profile using the name you enter. If a previous installation of IBM Cognos exists in the profile you select, the Build Application Wizard will allow you to uninstall the previous installation before installing the new one. 8. In the Server Instance box, select the server instance for your IBM WebSphere profile.

Chapter 14. Using an application server other than Tomcat

377

9. Right-click the name you gave your IBM WebSphere configuration, and click Build. The Build Application Wizard appears. Follow the instructions in the wizard and click the Help icon for more information for each page. The wizard will allow you to build the application, and install it to the IBM WebSphere profile. The application will be configured to run. For example, the path values will be added and the correct JVM settings will be applied. On the Configure IBM Cognos for WebSphere page, ensure that you enter the correct port numbers for the IBM WebSphere profile. The values are provided in the page. These values will be applied to the IBM Cognos Configuration Environment settings. Tip: To test your IBM WebSphere configuration, right-click the name you gave your IBM WebSphere configuration, and click Test. The dialog will show any configuration errors. Click the Details icon to view any messages. 10. Restart your IBM WebSphere profile. You can uninstall your IBM Cognos application from IBM WebSphere from IBM Cognos Configuration. Right-click the name you gave your IBM WebSphere configuration, and click Uninstall.

Identifying the JDK for WebLogic 9 on AIX
WebLogic 9 requires Java Development Kit (JDK) 1.5. If you use WebLogic Server 9 on AIX, you must update the Java options in the commEnv.sh file to specify the appropriate serial version unique identifier (UID). If you do not make this update, a serial version UID mismatch occurs when using WebLogic Server 9 with IBM Java 5.

Procedure
1. Open the WebLogic9_location/common/bin/commEnv.sh file. 2. Modify the file to include the following command:
JAVA_OPTIONS="${JAVA_OPTIONS} -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0" export JAVA_OPTIONS

3. Save and close the commEnv.sh file.

Change the application server startup script
Some application servers have specific requirements that you must meet before you can run IBM Cognos Business Intelligence. Depending on the application server, you may have to define environment variables, copy files, and add or change code in files. If you are using Red Hat JBoss or Oracle WebLogic Server, you must make changes to the application server startup script. If you are using IBM WebSphere Application Server, you do not have to change the startup script unless you want to add the environment variable changes. If you do make changes, use the administration console. If your environment contains a JRE that you are using for other products, the JRE folder may contain .jar files that are not compatible with the .jar files that are provided with IBM Cognos BI. This may result in a failure to start IBM Cognos BI

378

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

on your application server. In this situation, direct IBM Cognos BI to use the endorsed .jar files by including the following parameter in the Java command line:
-Djava.endorsed.dirs=${ibmcognos_home}/tomcat[version]/common/endorsed

Change the application server startup script for WebLogic
If you are using Oracle WebLogic Server, the startup script must be modified to specify Java Virtual Machine (JVM) settings. For WebLogic 9, use the Administration Console to modify the WebLogic environment.

Procedure
1. Create a WebLogic Server (WLS) domain for IBM Cognos BI. If you are configuring the IBM Cognos Servlet Gateway, create a second domain for this application. For information about creating domains, see the WebLogic documentation. 2. Go to the WebLogic9_location/user_projects/domains/domain_name/bin directory and open the application server startup script in an editor. The name of the startup script may vary depending on the type of WebLogic installation performed. For example, in a managed server installation, the name of the startup script is startManagedWebLogic.sh or startManagedWebLogic.cmd. 3. For non-IBM JRE versions, select the JVM run mode, and change the default setting from JAVA_VM= to JAVA_VM=-server. 4. Modify the JAVA_OPTIONS to set the appropriate XML parser for IBM Cognos BI. Add the third line, as shown in this example:
JAVA_OPTIONS= -Dweblogic.security.SSL.trustedCAKeyStore= %WL_HOME%\server\lib\cacerts -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser

5. Set the minimum and maximum memory used by the JVM. Typically, the memory is set using two JVM parameters: -Xms and -Xmx. A minimum of 256 MB and a maximum of 768 MB are suggested starting values. You can change these values to suit your environment. The MaxPermSize parameter must also be set. Here is an example:
-XX:MaxPermSize=128m

For information about JVM parameters, see the JVM or application server documentation. 6. Ensure that the production mode is enabled by changing PRODUCTION_MODE= to PRODUCTION_MODE=true. 7. Save and close the file.

Change the application server startup script for JBoss
If you are using Red Hat JBoss, the startup script must be modified to specify Java Virtual Machine (JVM) settings. You must also specify a log4j argument. For Red Hat JBoss, create a copy of the default server instance so that you can use the original default server instance as a backup. Give the copy a name that does not use spaces, such as cognos.

Procedure
1. Go to the JBoss_location/bin directory and open run.bat or run.sh in an editor.
Chapter 14. Using an application server other than Tomcat

379

2. Go to the JAVA_OPTS variable and add the following parameters:
-Xms512m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.client.gcInterval=3600000 -DLog4j.defaultInitOverride=true

The minimum and maximum memory settings are suggested starting values. You can change these values to suit your environment. For information about these parameters, see the JVM or application server documentation. 3. For HP Itanium 64 bit, also add the following parameters:
-Djava.library.path=/install_location/bin64 -d64 -Xss4m

If SSL is enabled, increase the Java thread stack to 12 MB. For example, -Xss12m. 4. Save and close the file.

Configure application server properties and install IBM Cognos components
You must configure application server properties and install the IBM Cognos components on your application server.

Install IBM Cognos on WebSphere
Follow these steps to install on WebSphere.

Procedure
1. Start the WebSphere Application Server, and then access the WebSphere Administrative Console. 2. Create a new server instance into which the IBM Cognos Business Intelligence application will be deployed, if this option is available in the version you are running. If you are deploying the IBM Cognos Servlet Gateway, create a second separate server instance. 3. Install a new Enterprise Application using the application file that was built by IBM Cognos Configuration. For IBM Cognos BI, the default context root is p2pd, which can be used in most cases. For the IBM Cognos Servlet Gateway, the default context root is ServletGateway. Other default application deployment values, such as the application name, may be changed to better suit your environment. The context root value used to deploy the application must be the same as the context root value entered in IBM Cognos Configuration when running the Build Application wizard. 4. Set the memory used by the JVM. Usually, the memory is set by adding or changing the initial and maximum Java heap size. For information about these parameters, see the JVM or application server documentation. Tip: A minimum of 256 MB and a maximum of 768 MB are suggested starting values. You can change these values to suit your environment. 5. Set other JVM options, if required.

380

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

The JVM process can be tuned by specifying various options as arguments to the Java process. For information about the possible parameters, see the JVM documentation. 6. In the server properties, add an environment variable, as listed in the following table, that references the installation_location/bin directory.
Table 86. Operating system environment variables Operating system Microsoft Windows AIX Solaris HP-UX Environment variable PATH LIBPATH LD_LIBRARY_PATH SHLIB_PATH

Ensure that you use the appropriate library files for the version of the IBM Cognos BI server that you install. IBM Cognos BI requires 32-bit library files when running in a 32-bit application server and it requires 64-bit library files when running in a 64-bit application server. Depending on the version of DB2 that you have installed, you may have to change the library files or change the order in which the library files are listed so that IBM Cognos BI server can find the correct files. Whichever version of library files are needed must be listed first. 7. If you are using collaboration with IBM Connections, you must enable access for the BI User role you added in “Add user role to enable single signon between IBM WebSphere profiles” on page 374. v In the IBM WebSphere administration console, click Applications > Enterprise applications. v Click IBM Cognos. v In the Detail properties section, click Security role to user/group mapping. v Select the Select check box for BI User, and select the All authenticated? check box. v Click OK, and then click Save. 8. Stop and then restart the WebSphere application server instance used for IBM Cognos components. 9. Verify that IBM Cognos components are running by looking for the following message in the application server admin console or in the application server log file: The dispatcher is ready to process requests.

Install IBM Cognos on WebLogic
Follow these steps to install on WebLogic.

Procedure
1. If you used the expanded directory option when building the application in IBM Cognos Configuration, go to step 2. If you created a WAR file, expand the application manually: v Create a directory in a location that is accessible to the application server, giving the directory the same name as the context root.
Chapter 14. Using an application server other than Tomcat

381

For IBM Cognos BI, the default context root and application directory name is p2pd, which can be used in most cases. For the IBM Cognos Servlet Gateway, the default context root is ServletGateway. Other default application deployment values, such as the application name, may be changed to better suit your environment. The context root value used to deploy the application must be the same as the context root value entered in IBM Cognos Configuration. v From the directory you just created, extract the application WAR file to the WebLogic installation using the following command from a command prompt: WebLogic_location/jdk_version/bin/jar xvfm "installation_location/ application.war" . A space and then a period are required at the end of the command. In this command, the period does not refer to the current directory. 2. Start the WebLogic Administration Server and the WebLogic Managed Server associated with the IBM Cognos domain. Node Manager must be started before you can start and stop Managed Server instances using the Administration Console 3. You must modify the environment in the WebLogic Administration Console before deploying IBM Cognos BI. Logon to the Administration Console and navigate to the Managed Server instance that will host the IBM Cognos BI application. Select the Server Start tab for the Managed Server instance and enable edit mode. 4. In the Java Home box, enter the path for the JVM. This value must be the same as is used for IBM Cognos BI. You must use the JVM that is included with the WebLogic installation. 5. Set the Java arguments. The Java arguments include all JVM settings, such as memory settings specified using two JVM parameters: -Xms and -Xmx. The MaxPermSize must also be set. You must also set the appropriate XML parser for IBM Cognos BI. For example, in the Arguments box, type -Xms768m -Xmx768m -XX:MaxPermSize=128m -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser If you use WebLogic on AIX, you must also specify the appropriate serial version UID in the Java arguments. If you do not make this update, a serial version UID mismatch occurs when using WebLogic with Java 5 because WebLogic requires JDK 1.5. For example, in the Arguments box, type -Xms768m -Xmx768m -XX:MaxPermSize=128m -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 For information about JVM parameters, see the JVM or application server documentation. 6. Save and apply the changes. You can now start and stop the Managed Server instance from the Control tab. 7. Start the server instance. The server instance must be started before deploying IBM Cognos BI or IBM Cognos Servlet Gateway. 8. Deploy the IBM Cognos BI or IBM Cognos Servlet Gateway application in the WebLogic console using a new Web application as follows:

382

IBM Cognos Business Intelligence Version 10.2.1: Installation and Configuration Guide

highlight Server_IDxxxxxxx. and then click Set. highlight CompressedOthers. Note: IBM Cognos BI uses a custom loader. Open the configuration tool by typing drive:\usr\sap\sapid\JCxx\j2ee\configtool\configtool. We suggest a minimum value of 768 MB. services. Under cluster-data.driver=org. type false. If your computer has less than 1. set the reload period for the Web application to -1 to improve performance. services.bat 2. Tip: We suggest an initial KeepAliveTimeout number of at least 60. After the deployment has completed successfully.sax.SAXParser 8. This will prevent WebLogic from checking for updated application files that are used only in a development environment. 11. Install IBM Cognos on SAP NetWeaver Follow these steps to install on SAP NetWeaver. 3. Under Global Properties. 6. 4. v Select the target server instance. under cluster-data.parsers.v Set the application name. Procedure 1. where xxxxxxx is the ID number for your installation. you may have issues when you run SAP NetWeaver. Use the Administration Server only for WebLogic administration tasks and deploy the IBM Cognos BI application to its own Managed Server instance. In the Java parameters box. click Yes. you would type D:\usr\sap\J2E\JC00\j2ee\configtool\configtool. 9. highlight KeepAliveTimeout and type a higher number and then click Set. When prompted to use the default DB settings. if the SAP ID is J2E and the installation is on drive D. highlight Server_IDxxxxxxx. Verify that IBM Cognos components are running by looking for the following message in the application server console window or in the application server log file: The dispatcher is ready to process requests. 7. Chapter 14. instance_IDxxxxxxx. Set the memory used by the JVM.xml. and highlight http. instance_IDxxxxxxx. 9. ibmcognos v Set the path to the directory where the expanded application files are located. set the XML parser as follows: -Dorg. Stop and then restart the WebLogic Managed Server associated with the IBM Cognos domain to activate the changes. For IBM Cognos BI environments that use Report Studio.5 GB of memory. Follow the recommendations from SAP. Under Global Properties. You must use the expanded directory option when deploying. For more information.xerces. For example. Using an application server other than Tomcat 383 . 10.bat For example. Dispatcher_IDxxxxxxx. instance_IDxxxxxxx. highlight http. Under cluster-data. see SAP Note 723909 in the SAP Support Portal.apache. 5.

Use the Deploy tool to create a new project.0 as the binding address. In the server. to run jBoss 5. Procedure 1. You are prompted to restart the server.ear for IBM Cognos BI and ServletGateway. 11. 384 IBM Cognos Business Intelligence Version 10. ensure that you secure your application server properly and do not use -b 0.1 Connector on port 8080 --> <Connector port="8080" address="${jboss.0.2. open the JBoss_location/server/instance_name/deploy/jbossweb-tomcat55.# In a test environment. Important: For a production environment. When you are prompted to start the application. the file is named p2pd.tc5.sar/server. For example.web. Verify that IBM Cognos components are running by looking for the following message in the application server console window or in the application server log file: The dispatcher is ready to process requests. see the jBoss documentation.0. you can use -b 0. <Service name="jboss.xml file. Start the application server. 16. However.xml file. use a command like run. this may cause errors when you access your IBM Cognos BI application.0. By default. 14.0.bind. For jBoss 5. To avoid these errors.0. 6. 15.1).#.0. 12. Install IBM Cognos on JBoss Follow these steps to install on JBoss. For example. 4. Using the Deploy tool. Save the project. Load the IBM Cognos application file you created using IBM Cognos Configuration.StandardService"> <!-.web" className="org. 5.xml file.0.A HTTP/1.10. The p2pd application is automatically detected and started by the application server. the default behaviour is to bind its services to the localhost (127. For more information. 2. connect to the Administration tool and deploy the application file.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/> 3. 13.tomcat. Put the p2pd application in the JBoss_location/server/instance_name/deploy folder. If you do not want to use the default port of 8080.ear for IBM Cognos Servlet Gateway. click Yes.jboss. which binds to all available interfaces.0 with legacy behaviour. Restart the server by using the SAP Management Console or by restarting the services in Services. Save the changes.bat -c <server_name> -b #. change the default port number of 8080 used by the server instance to the port specified in IBM Cognos Configuration.1: Installation and Configuration Guide . add the -b attribute when you start the server.#. if it is not already in this location. Save and close the server.0.

sh -T -i -r ca./configuration/ signkeypair/jCAKeystore -p NoPassWordSet Restriction: Ensure that the user who runs the script has read access to the directory where the certificate is stored and read access to the certificate file..cer. For information about using CA certificates with your application server./configuration/ signkeypair/jCAKeystore -p NoPassWordSet v On UNIX or Linux operating systems.cer -k . type: ThirdPartyCertificateTool.com/software/data/cognos/ customercenter/). Chapter 14.bat -T -i -r ca. Otherwise. 2. From the c10_location/bin directory: v On Microsoft Windows operating system..509 format. see the IBM Cognos Customer Center (http://www. you must also enable SSL in the application server environment. Before you begin On UNIX or Linux operating systems. refer to the application server documentation. Configuring web communication For most types of supported application servers.. Copy the CA certificate to the c10_location/bin directory and rename the file to ca. For information about configuring the web server. you use a web server and an IBM Cognos gateway for Web communication. For more information about configuring the application server to use SSL. You must type jCAKeystore as the name of the CA keystore. For information about configuring the WebSphere Web server plugin. run the tool with -java:local to use the JRE that is provided with the installation. For example. ensure that you set a JAVA_HOME environment variable before you use the ThirdPartyCertificateTool. This file must be Base-64 encoded X. On Microsoft Windows operating systems. You then identify the SSL server certificate to Cognos components.Enabling the secure socket layer If you use the Secure Socket Layer (SSL) for IBM Cognos components.cer -k . An SSL server certificate is generated by another certificate authority (CA). The certificate of the CA that generated the SSL server certificate is also provided. type: ThirdPartyCertificateTool. Procedure 1. see the CA documentation.lang. Using an application server other than Tomcat 385 .bat -java:local -T -i -r .. you might see an error similar to the following error message: Exception in thread "main" java. 3. ThirdPartyCertificateTool. see “Configuring the web server” on page 96.NullPointerException error when you import the certificate. Configure the application server to use SSL.ibm.

Click Unregister. 6. 4. In the confirmation dialog box. Procedure Create the virtual directory listed in the following table: Table 87. 386 IBM Cognos Business Intelligence Version 10. This virtual directory is required to allow the static content (html pages.1: Installation and Configuration Guide . Click Launch > IBM Cognos Administration. Upgrade to IBM Cognos BI in an application server environment If you are upgrading from a supported release to IBM Cognos Business Intelligence. click More. Back up your existing IBM Cognos information.If you are using SAP NetWeaver on Microsoft Windows and you are not using a Web Server and an IBM Cognos gateway for web communication. select the option to include the static files from the webcontent folder. Configure virtual directory for SAP NetWeaver If you are using SAP NetWeaver and you are not using a web Server and an IBM Cognos gateway for web communication. follow the steps to configure a virtual directory. When building the IBM Cognos application file. For the dispatcher you want to unregister. 2. also known as a web alias. On the Configuration tab. Procedure 1. 3. p2pd for IBM Cognos Business Intelligence or ServletGateway for the IBM Cognos Servlet Gateway). you will have dispatchers registered in the content store. you must create a virtual directory. Virtual directories for SAP NetWeaver Alias context_root (for example. and so on) to load. click Dispatchers and Services. You remove dispatchers using IBM Cognos Administration. Create a virtual directory that uses the context root value as a name (by default. You must unregister any dispatchers that were previously registered for Tomcat. p2pd) Location c10_location/webcontent Permission Read Unregister dispatchers that were configured for Tomcat If you are installing IBM Cognos BI to an application server after you have already started the product with Tomcat.2. Procedure 1. Ensure the virtual directory points to the c10_location/webcontent folder. from the Actions column. perform the following steps. click OK. images. 5. Open IBM Cognos Connection by connecting to the IBM Cognos Business Intelligence portal and clicking IBM Cognos Content on the Welcome page.

Most installations must perform the following: v “Configure IBM Cognos components to run within the application server” on page 375 v Configure application server properties and deploy IBM Cognos BI. and then restart the services. For information about undeploying applications. Chapter 14. see your application server documentation. 3. Follow the appropriate instructions in this chapter for changing to your application server. delete the directory. To activate new features after upgrading. Install the new version of IBM Cognos BI.2. remove any IBM Cognos . Using an application server other than Tomcat 387 . 4. save the configuration in IBM Cognos Configuration. 6. If the directory to which the existing IBM Cognos application was originally deployed is not removed during the undeploy process. Uninstall the existing version. Use the administrative tools for your application server to undeploy the existing IBM Cognos application. Also.jar files that are cached in your application server environment. 5.

1: Installation and Configuration Guide .2.388 IBM Cognos Business Intelligence Version 10.

a technology that supplies tools to manage and monitor applications and service-oriented networks. System Performance Metrics IBM Cognos BI provides system metrics that you can use to monitor the health of the entire system and of each server. how long a Java Virtual Machine (JVM) has been running. For more information about monitoring system performance metrics. You can also monitor system metrics externally to IBM Cognos Administration by using Java Management Extensions (JMX). 6. Some examples of system performance metrics are the number of sessions in your system. In the Value column. © Copyright IBM Corp. click Environment. You can also set the thresholds for the metric scores. In the Properties window. click the edit icon. type an available port number. type a user ID and password. You can take a snapshot of the current system metrics so that you can track trends over time or review details about the state of the system at a particular time. Then you use a secure user ID and password to connect to the metrics through a JMX connection tool. 4. under Dispatcher Settings. Monitoring System Metrics Externally You can monitor system metrics outside of IBM Cognos Administration by using industry standard Java Management Extensions (JMX). In the Value column. Before you begin You must install Oracle Java SE Development Kit or the Java Software Development Kit from IBM before you can use the external monitoring feature. how long a report is in a queue. In the location where Content Manager is installed. Click External JMX credential. For more information.Chapter 15. 2005. dispatcher. 2013 389 . start IBM Cognos Configuration. Performance Maintenance This section includes topics about using IBM Cognos Business Intelligence and other tools and metrics to maintain the performance of your IBM Cognos Business Intelligence environment. First. click External JMX port. and the number of requests and processes in the system. see the IBM Cognos Business Intelligence Administration and Security Guide. Procedure 1. 5. you configure two JMX properties in IBM Cognos Configuration to enable secure access to the metrics in the Java environment. In the Explorer window. and then click OK. 3. and service. 2. System performance metrics reside in the Java environment. see the topic about the metric dump file in the IBM Cognos Business Intelligence Troubleshooting Guide. but can be monitored in IBM Cognos Administration through IBM Cognos Connection.

1: Installation and Configuration Guide . you should disable the services associated with the missing components. you can disable them to improve the performance of other services. to dedicate a computer to running and distributing reports. Annotation service 390 IBM Cognos Business Intelligence Version 10. IBM Cognos services After you install and configure IBM Cognos BI. the performance of the Application Tier Components will improve. Each dispatcher has a set of associated services. When you disable the presentation service. v If some IBM Cognos BI components are not installed on a computer. service:jmx:rmi://Content_Manager_server/jndi/rmi:// monitoring_server:<JMXport>/proxyserver where JMXport is the value that you typed for External JMX port. 7. IBM Cognos services Service Agent service Purpose Runs agents. you must enable the Presentation service. Enabling Only Services That are Required If some IBM Cognos BI services are not required in your environment. v If you want to use Query Studio. v If you want to use Analysis Studio. Enables the addition of commentary to reports via the IBM Cognos Workspace. you can disable the presentation service on an Application Tier Components computer. v the user ID and password to secure the connection Use the same values that you configured for External JMX credential. For example. the agent service asks the monitor service to run the tasks. even if connecting locally. you must enable the Report service. one dispatcher is available on each computer by default. Note: v The Presentation service must remain enabled on at least one computer in your IBM Cognos BI environment. If the conditions for an agent are met when the agent runs. Table 88.The user ID and password ensure that only an authorized user can connect to the system metrics data in the Java environment. Otherwise the IBM Cognos BI components will randomly fail. Save the changes and restart the service. These comments persist across versions of the report. listed in the following table. and Content_Manager_server and monitoring_server are machine names.2. specify the following information in the JMX connection tool: v the URL to connect to the system metrics data For example. 8. To access the system metrics data. using the port specified in External JMX port. Do not use localhost.

Table 88. agents. including lists of aliases and examples. such as the report service. Provides write. and administration functions. such as import and export Data movement service Manages the execution of data movement tasks in IBM Cognos BI. deployment imports and exports. and manages event objects that represent reports. Steps include reports. Microsoft Excel XML or PDF. Runs jobs by signaling the monitor service to run job steps in the background. delete. agent service. Graphics can be generated in 4 different formats: Raster. exports. Enhances the overall system performance and Content Manager scalability by caching frequent query results in each dispatcher. are created in Data Manager Designer and published to IBM Cognos BI. and metrics Produces graphics on behalf of the Report service. v Performs object manipulation functions in the content store. Vector. Enables the creation and management of human tasks. such as add. and so on. delete. such as Builds and JobStreams. Data movement tasks. move. IBM Cognos services (continued) Service Batch report service Purpose Manages background requests to run reports and provides output on behalf of the monitor service. update. A human task such as report approval can be assigned to individuals or groups on an ad hoc basis or by any of the other services. job service. other jobs. jobs. Provides search and drill-through functions. Provides basic full-text functions for storage and retrieval of terms and indexed summary documents. schedules. Sends emails to an external SMTP server on behalf of other services. Content Manager cache service Content Manager service Delivery service Event management service Graphics service Human task service Index data service Index search service Index update service Job service Chapter 15. and copy v Performs content store management functions. import. or data integration service Creates. content store maintenance. Performance Maintenance 391 . query. update.

Query Studio. and administration capabilities in IBM Cognos Connection Query service Manages Dynamic Query requests and returns the result to the requesting batch or report service. such as HTML or PDF v Provides display. or the agent service to run an agent. Report Studio. IBM Cognos services (continued) Service Log service Purpose Records log messages generated by the dispatcher and other services. a database. v Creates history objects within the content manager and manages failover and recovery for executing entries PowerPlay service Presentation service Manages requests to run PowerPlay reports. v Manages the monitoring and execution of tasks that are scheduled. the job service to run a job. Metric Studio service Migration service Monitor service Report data service 392 IBM Cognos Business Intelligence Version 10. Windows Event Viewer. Provides the Metric Studio user interface for monitoring and entering performance information Manages the migration from IBM Cognos Series 7 to IBM Cognos BI. and Analysis Studio. v Transforms generic XML responses from another service into output format. including: v security events v system and application error information v selected diagnostic information Metadata service Provides support for data lineage information displayed in Cognos Viewer. or run as a background task v Assigns a target service to handle a scheduled task. navigation. submitted for execution at a later time. For example.2.1: Installation and Configuration Guide . or a UNIX system log.Table 88. The log service can be configured to record log information in a file. Lineage information includes information such as data source and calculation expressions. The log information can then be analyzed by customers or by Cognos Software Services. such as IBM Cognos BI for Microsoft Office and IBM Cognos Mobile. Manages the transfer of report data between IBM Cognos BI and applications that consume the data. a remote log server. the monitor service may ask the batch report service to run a report.

do not use IBM Cognos Configuration to configure the resources. Instead. Performance Maintenance 393 . v Create the tables in a system-managed table space. By reassigning the tables that contain LOBS to a system-managed tablespace. Start IBM Cognos Configuration. In the Properties window. memory footprint. you reduce the number of direct I/O requests. allocate sufficient log space to restructure the database. Adjusting the Memory Resources for the IBM Cognos Service To improve performance in a distributed environment. By default. the application server that IBM Cognos BI uses by default. The IBM Cognos service is available only on the computers where you installed Content Manager or the Application Tier Components. The configuration settings for the IBM Cognos service apply only to Tomcat. do the following: v Export the data from the tables that contain at least one large object (LOB). This results in direct I/O requests on the LOBS. which affects performance.Table 88. To reconfigure the DB2 content store. IBM Cognos services (continued) Service Report service Purpose Manages interactive requests to run reports and provides output for a user in IBM Cognos Connection or a studio. v To reduce the startup time. DB2 assigns tables that contain large objects (LOBS) to a database-managed tablespace. Repository service Tuning a DB2 Content Store If you use a DB2 database for the content store . the IBM Cognos service is configured to use minimal memory resources to optimize startup time. 3. v Import the data into the tables. the LOBS are not managed by the DB2 buffer pools. As a result. If you want to configure IBM Cognos BI to run on another application server. use the default setting of 768. By default. change the value for Maximum memory in MB. Before changing a DB2 content store. and then click IBM Cognos. 2. configure the resources within that application server environment. Manages requests to retrieve archived report output from an archive repository or object store. you can take steps to improve the speed with which requests are processed. you can change the amount of resources that the IBM Cognos service uses. Procedure 1. Chapter 15. In the Explorer window. and resources used. expand Environment > IBM Cognos services.

Reducing the number of requests per process Use the following steps to reduce the number of requests per process for an instance of the IBM Cognos service. go to the c10_location\bin directory. 6. 6. type a value about double the default value. 3.sh file (on UNIX or Linux). 2. 4. regenerate the EAR file and deploy it to the WebSphere application server. v To maximize operating speeds and if performance is more important than fast startup time. Restart the IBM Cognos service.1: Installation and Configuration Guide . change the following values: a. On the computer where you have installed the Cognos Content Database component. Change the value for default_process_use_limit from 0 (unlimited) to a fixed number of requests. 4. In that section. such as 1152.2.bat file (on Windows) or derby. Go to the c10_location/webapps/p2pd/WEB-INF/services directory. 5. Save the file.1". where the number of simultaneous requests is greater than ten.v To balance between fast startup time and quick operating speeds. you can edit the maxThreads and acceptCount settings to improve performance. Open the reportservice. 2. From the File menu.5 times the default value. you must adjust the default JVM memory settings and increase the page cache size for Derby. Change maxThreads="500" to maxThreads="1500" b. type a value about 1. Procedure 1. Increase the Request-handling Capacity for Cognos Content Database Cognos Content Database is configured for use with a small system. Procedure 1. 2. click Save. Open the server. If you use Cognos Content Database in a large system. Save the file.xml file in an XML editor. Change acceptCount="500" to acceptCount="100" 5. Procedure 1. For example. and if your computer has a lot of resources. 4. for WebSphere. Restart your IBM Cognos services.xml file. Open the derby. If you deployed IBM Cognos BI to an application server. 3. such as 1536. Find the line <Connector port="9300" protocol="HTTP/1. rebuild the application file and deploy it to the application server. Go to the c10_location/tomcat/conf directory. Find the following line: 394 IBM Cognos Business Intelligence Version 10. Tune Apache Tomcat settings for 64-bit installations If you are using Apache Tomcat on a 64-bit installation. 3.

properties.sample to derby.storage. Procedure 1. If HTML reports are required. Chapter 15. Go to the appropriate database directory. HTML reports take longer than PDF reports to open because more requests are processed for HTML reports. For example.set MEM_SETTINGS=-Xmx256m and change it to the following: set MEM_SETTINGS="-Xmx1152m -XX:MaxPermSize=128M -XX:MaxNewSize=576m -XX:NewSize=288m" 4. you use this script before or after loading data when the volume or distribution of data has changed significantly.properties. see the IBM Cognos Business Intelligence Administration and Security Guide. Typically. You can reduce the amount of time for reports to open in remote locations in two ways. You may also want to set the Queue Time Limit setting to 360. Depending on the database type. open the derby.pageCacheSize=15000 Improve Metric Store Database Performance IBM Cognos BI provides a script called cmm_update_stats that updates your metric store database indexes. 2. In addition. Go to the following directory: c10_location\configuration\schemas\cmm 3. will be delivered faster. You can reduce the number of requests between the browser and the server by running the report in PDF format. Comment out the following line: derby. 6. In the same directory. run one of the following scripts from the command line: v For Microsoft SQL Server or DB2: cmm_update_stats host_name metric_store_name Admin_user_name password v For Oracle: cmm_update_stats metric_store_name Admin_user_name password Reduce Delivery Time for Reports in a Network Reports that are distributed globally take longer to open in remote locations than to open locally. such as graphics and style sheets. rename derby. Static content. In the c10_location\configuration directory. you may want to increase the asynchronous timeout setting to avoid getting error messages. 5. Increase Asynchronous Timeout in High User Load Environments If you have a high user load (over 165 users) and interactive reports are running continuously in a distributed installation. which improves performance. you can speed up the delivery of the report by configuring additional gateways in some of the remote locations. For information. performance may improve if you run this script after increasing the number of scorecards from 100 to 1000. Performance Maintenance 395 .properties file. 4. The default is 30000. Ensure that there is no activity in the metric store database.

Restart the service. 2. Change the async_wait_timeout_ms parameter to 120000.xml file in a text editor.2. Save the file. Go to the following directory: c10_locationwebapps/p2pd/WEB-INF/services/. 396 IBM Cognos Business Intelligence Version 10. Procedure 1.To resolve this problem. 3. 5. increase the wait timeout. 4.1: Installation and Configuration Guide . Open the reportservice.

or locale mapping by editing the coglocale. you must edit the cogstartup. When you save the cogstartup. In this case. If you distribute IBM Cognos BI components across several computers.xml file. the cogstartup. When you edit the cogstartup. remember that XML is case-sensitive. you can add a component to your configuration.xml file and then edit the values to suit your environment. ensure that you © Copyright IBM Corp. By default. 2005.xml file directly and then run IBM Cognos Configuration in silent mode. the server time zone is not set for your IBM Cognos components when you modify the cogstartup.xml file unless you use the graphical user interface. some configuration tasks are required so that IBM Cognos BI works in your environment. Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems The console attached to the UNIX or Linux operating system computer on which you are installing IBM Cognos Business Intelligence may not support a Java-based graphical user interface.xml to configure IBM Cognos Business Intelligence to work in your environment. You can change the default behavior of IBM Cognos BI by editing the cogstartup.Chapter 16. Important: Some configuration settings are not saved in the cogstartup. If you want IBM Cognos BI to use a resource. elements and values. __ v Apply the configuration and the locale settings to your computer by running IBM Cognos Configuration in silent mode. You must perform the following tasks manually: __ v Change default configuration settings by editing the cogstartup.xml file.xml file is encoded using UTF-8. the order in which you configure and start the computers is important. For example. You do this by copying the required XML code from the sample files into the cogstartup. such as an authentication provider that already exists in your environment. The encoding of your user locale is set by your environment variables. You can also use sample files that enable IBM Cognos BI to use resources that already exist in your environment. Before you edit the cogstartup.xml file to change property values.xml file. located in the c10_location/configuration directory.xml file. 2013 397 . including element and attribute labels. Other configuration tasks are optional and depend on your reporting environment. located in the c10_location/configuration directory. ensure that you change the encoding of your user locale to match the encoding used. other user settings that rely on the server time zone may not operate as expected.xml file. Manually change default configuration settings If the console attached to your UNIX or Linux operating system computer does not support a Java-based graphical user interface. For all installations. Case is important in all uses of text. __ v Change language or currency support.

1: Installation and Configuration Guide . Adding a component to your configuration The cogstartup. Procedure 1. 6. 3. Go to the c10_location/configuration directory. Go to the c10_location/configuration/samples directory. IBM Cognos BI can use only one instance at a time of the following elements: v The database for the content store v A cryptographic provider v A configuration template for the IBM Cognos service You should be familiar with the structure of XML files before you start editing them. You can then edit the configuration values to suit your environment. open the ContentManager_language_code. Save and close the file.xml sample file to replace the default database connection information. to use an Oracle database for the content store. open the Cryptography_language_code. you can use the ContentManager_language code. Find the configuration setting you want to change by looking at the help and description comments that appear before the start tag of the <crn:parameter> elements. DB2. Open the cogstartup.xml file. v To use an authentication provider. Tip: Use the type attribute to help you determine the data type for the configuration property. Results You should now use a validating XML editor to validate your changes against the rules in the cogstartup. 398 IBM Cognos Business Intelligence Version 10. You can change the components that IBM Cognos BI uses by copying XML elements from sample files into the cogstartup. Repeat steps 3 to 4 until the configuration values are appropriate your environment.2.v make a backup copy v create the content store on an available computer in your network v review the configuration requirements for your installation type Procedure 1. 5. Choose a sample file to open in an editor: v To use Oracle. 2.xml file in an editor.xml file.xml file.xml file. 2. v To use a cryptographic provider. 4. Change the value of the <crn:value> element to suit your environment.xml file contains configuration settings used by IBM Cognos Business Intelligence and by default components.xsd file. For example. open the Authentication_language_code. or Sybase for the content store. located in the c10_location/configuration.

Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems 399 .. do not change the class attribute.xml file. 6. Open the cogstartup.> . Run IBM Cognos Configuration in silent mode by typing the following command: . open the Logging_language_code.xml file in an editor. 7.v To send log messages somewhere other than a file. Go to the c10_location/configuration directory.xml file in an editor. 9. For the <crn:instance> element.. Change the value of the <crn:value> element to suit your environment.sh -s This ensures that the file is valid and that passwords are encrypted. You can change the name attribute to suit your environment. look for the (Begin of) and (End of) comments: <!-(Begin of) DB2 template --> <crn:instance . <crn:instance class="Oracle" name="MyContentStore"> 8. 4. you change the value and then set the encryption flag to false. </crn:instance> <!-End of) DB2 template --> 4. Open the cogstartup. open the CognosService_language_code. Copy the elements that you need. For example.xml file. Go to the c10_location/configuration directory. Tip: Ensure that you copy the code including the start and end tags for the <crn:instance>element. Save and close the file. in the cogstartup. change only the name attribute to suit your environment. 2. Change the values of these new elements to suit your environment. Find the encrypted setting you want to change by looking at the help and description comments that appear before the start tag of the <crn:parameter> elements.xml file and replace the appropriate <crn:instance> element. For example.. Paste the code from the sample file to the cogstartup. To prompt IBM Cognos Configuration to save an encrypted setting. Chapter 16. 3. 3. v To use a medium or large template for the amount of resources the IBM Cognos BI process uses. Procedure 1. Changing manually encrypted settings You can manually change encrypted settings. if you use an Oracle database for the content store. 5./cogconfig. such as passwords and user credentials..xml file.

sh -s Results The new settings are saved and encrypted.5. Type the following configuration command: . IBM Cognos checks to see if the report is available in Content Manager in the user's locale. you must manually edit the coglocale. not fr. Therefore. Next. the report is available in en-us and fr-fr. Because the user's locale is fr-ca. Tip: Use the type attribute to help you determine the data type for the configuration property. contact your support representative. which may come from different sources and in various formats. you must install the language files on all computers in your distributed installation. such as en-us (English-United States) and fr-fr (French-France). it is mapped to fr. 400 IBM Cognos Business Intelligence Version 10. Before you can add language support to the user interface. Global settings on UNIX and Linux operating systems If the console attached to your UNIX or Linux operating system computer does not support a Java-based graphical user interface. IBM Cognos maps the user's locale to a normalized locale configured on the Content Locale Mapping tab. In this case. First. Save and close the file. Change the encryption value to false. en-us becomes en and fr-fr becomes fr.1: Installation and Configuration Guide . IBM Cognos uses the locale mapping to determine which report the user sees. IBM Cognos BI components ensure that all locales. Example 1 A report is available in Content Manager in two locales. 7. If it is not available in the user's locale. IBM Cognos uses the mapped value to see if the report is available in fr. <crn:value encrypted="false"> Repeat steps 3 to 5 until the configuration values are appropriate for your environment./cogconfig. but the user locale is set to fr-ca (French-Canadian). For example. For more information. use a normalized form. That means that all expanded locales conform to a language and regional code setting.2.xml file. 6. 8. You can change global settings v to specify the language used in the user interface when the language in the user's locale is not available v to specify the locale used in reports when the user's locale is not available v to add currency or locale support to report data and metadata v to add language support to the user interface By default. IBM Cognos maps each of the available reports to a normalized locale.

the user having the user locale fr-ca will see the report saved with the locale fr-fr. Table 89. and start and end tags are listed in the following table. IBM Cognos chooses which locale to use. 4. delete the element. attributes. Example 3 The report and the user locales do not map to a common language. Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems 401 . In this case. 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). Open the coglocale. Procedure 1. Changing manually the global settings on UNIX and Linux operating systems Use the following steps to change global settings on UNIX and Linux operating systems using the coglocale file. Example 2 The user's locale and the report locales all map to the same language. you may want to configure a mapping. 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 chooses the language. The elements. Save and close the file. The user will see the report in the locale setting that IBM Cognos chooses.Because both report and the user locale maps to fr. On every computer where you installed Content Manager. go to the c10_location/configuration directory.xml file in an editor. For example. 2. Tags for global settings Type of element Language Content Locales Currency Product Locale Mapping Content Locale Mapping Fonts Cookie settings. archive location for reports Start tag <supportedProductLocales> <supportedContentLocales> <supportedCurrencies> <productLocaleMap> <contentLocaleMap> <supportedFonts> <parameter name="setting"> End tag </supportedProductLocales> </supportedContentLocales> </supportedCurrencies> </productLocaleMap> </contentLocaleMap> </supportedFonts> </parameter> Tip: To remove support. IBM Cognos maps each locale to en. IBM Cognos chooses the language. Chapter 16. Add or modify the required element and attribute between the appropriate start and end tags. For example. 3.

Starting and stopping Cognos BI in silent mode on UNIX and Linux operating systems You run IBM Cognos Configuration in silent mode to apply the configuration settings and start the services on UNIX or Linux operating system computers that do not support a Java-based graphical user interface. If you add a currency code that is not supported. located in the c10_location/configuration directory. 2. see “Manually change default configuration settings” on page 397. Results IBM Cognos Configuration applies the configuration settings specified in the cogstartup. Copy this file to each IBM Cognos computer in your installation. you should ensure the cogstartup. 402 IBM Cognos Business Intelligence Version 10.csv file in the c10_location/logs directory. Starting Cognos BI in silent mode on UNIX and Linux operating systems Use the following steps to start the IBM Cognos Business Intelligence software in silent mode. Ensure that the cogstartup.1: Installation and Configuration Guide .Results Tip: Use a validating XML editor to validate your changes against the rules in the cogstartup.xsd file is located in the c10_location/configuration directory. and if applicable. located in the c10_location/configuration. generates digital certificates.2. starts the Cognos service or process. The cogstartup. Stopping Cognos BI in silent mode on UNIX and Linux operating systems Use the following steps to stop the IBM Cognos Business Intelligence software in silent mode. Procedure 1./cogconfig.sh -s Tip: To view log messages that were generated during an unattended configuration. For more information. 3. see the cogconfig_response. encrypts credentials.xml file in the c10_location/bin/ directory.xml file.xml file.xsd file. Type the following command . Before you run the configuration tool in silent mode.xsd file. has been modified for your environment. you must manually add it to the i18n_res.xml file is valid according to the rules defined in the cogstartup. Go to the c10_location/bin64 directory.

Procedure 1. or an expanded directory that includes all the files necessary for the application. build. If the application server is not being used as a Web server. You can create a Web archive (. IBM Cognos Business Intelligence provides a Build Application wizard that you can use to create the application file. 3. you do not need to include the IBM Cognos static content (html pages. Procedure 1. and so on) in the application file. If you choose not to use the Build Application wizard. 2. you must complete the following steps to create the application file. see the documentation provided with the application server.sh file_type option where file_type can be one of the values listed in the following table: Table 90. Go to the c10_location/war/p2pd directory.sh -stop Manually create an IBM Cognos application file IBM Cognos Business Intelligence and the servlet gateway must be packaged into an application file for deployment to supported application servers. build. Excluding the static content when creating the application file reduces the size of the file. images. For information about WAR and EAR files or expanded directories and to determine what is supported by your application server. Creating an IBM Cognos application file for the Business Intelligence software If you choose not to use the Build Application wizard. Type the following command . Run the build script by using the following command syntax: v For Microsoft Windows operating system. an Enterprise archive (. Go to the c10_location/bin64 directory. Stop the IBM Cognos service if it is running. 2. Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems 403 .bat file_type option v For UNIX or Linux operating systems./cogconfig. you must complete the following steps to create the application file.war) file. A list of file type options and descriptions for an application file for the Business Intelligence software Value war war_without_webcontent war_without_docsamples Description WAR file with static content WAR file with no static content WAR file with static content and with no documentation and sample files Chapter 16.ear) file.

ear Path and name of the EAR file to be created -Dexpand_location=value (For expand file types) path/directory Path to directory where the application files are to be Default is ./p2pd./.. you must complete the following steps to create the application file.2../..1: Installation and Configuration Guide . 404 IBM Cognos Business Intelligence Version 10. A list of options. and descriptions for an application file for the Business Intelligence software Option -Dappserver_type=value Value jboss other (default) Description Perform actions for a JBoss application server Perform actions for a non-JBoss application server -Dcontext_root=value p2pd (default) Preset a context root value for the application Path and name of the WAR file to be created -Dwar_name=value path/filename Default is . values././p2pd.Table 90./temp/expand expanded Creating an IBM Cognos application file for a servlet gateway If you choose not to use the Build Application wizard. A list of file type options and descriptions for an application file for the Business Intelligence software (continued) Value ear ear_without_webcontent ear_without_docsamples Description EAR file with static content EAR file with no static content EAR file with static content and with no documentation and sample files directory containing the application with static content directory containing the application with no static content directory containing the application with static content and with no documentation and sample files expand expand_without_webcontent expand_without_docsamples and where option can be one or more of the values listed in the following table: Table 91..war -Dear_name=value path/filename Default is ...

./ServletGateway./ServletGateway.war -Dear_name=value path/filename Default is . Manually configuring IBM Cognos Business Intelligence on UNIX and Linux operating systems 405 . 3..bat file_type option v For UNIX or Linux. Option values and descriptions for an application file for a servlet gateway Option -Dappserver_type=value Value jboss other (default) Description Perform actions for a JBoss application server Perform actions for a non-JBoss application server -Dcontext_root=value ServletGateway (default) Preset a context root value for the application Path and name of the WAR file to be created -Dwar_name=value path/filename Default is .. Stop the IBM Cognos service if it is running. 2. build.ear Path and name of the EAR file to be created Chapter 16. Go to the c10_location/war/gateway directory. File type values and descriptions for an application file for a servlet gateway Value gateway_war gateway_war_without_docsamples Description WAR file with static content WAR file with static content and with no documentation and sample files EAR file with static content EAR file with static content and with no documentation and sample files directory containing the application with static content directory containing the application with static content and with no documentation and sample files gateway_ear gateway_ear_without_docsamples expand expand_without_docsamples and where option can be one or more of the values listed in the following table: Table 93. Run the build script by using the following command syntax: v For Windows./.Procedure 1.sh file_type option where file_type can be one of the values listed in the following table: Table 92./. build..

/.Table 93.1: Installation and Configuration Guide ../temp/expand expanded 406 IBM Cognos Business Intelligence Version 10. Option values and descriptions for an application file for a servlet gateway (continued) Option -Dexpand_location=value Value path/directory Description Path to directory where the application files are to be Default is ..2.

ats file for your environment before you can use it for an unattended installation. Use a pre configured configuration file from another computer. 4. 2. you can use the default transfer specification file named response. ensure that all the system requirements and prerequisites are met and that all other software that you need is installed and configured. Results After you complete these tasks. Procedure 1. the options you select are recorded in a transfer specification file. if you already installed IBM Cognos BI components on a sample computer. You must modify the response. Run the installation tool in silent mode. ensure that the IBM Cognos Business Intelligence installation directory on all computers is protected from unauthorized or inappropriate access. Using an unattended installation and configuration Use an unattended installation and configuration to do the following: v install an identical configuration across several computers on your network v automate the installation and configuration process by specifying options and settings for users v install and configure components in a UNIX or Linux environment that does not have XWindows Before you set up an unattended installation and configuration. Configure a transfer specification file (.Chapter 17.ats. Unattended installations You use a transfer specification file to copy IBM Cognos BI components to your computer without being prompted for information. If you do not use the installation wizard to install components. A value of zero (0) indicates success and all other values indicate that an error occurred. Each time you install IBM Cognos BI components using the installation wizard. Therefore. 2013 407 .ats) to specify installation options. You can check if the unattended installation was successful by checking the return status. You can also set up an unattended uninstallation. Run the configuration tool in silent mode. 3. you can use the generated transfer specification file as a template for unattended installations on different computers. 2005. Then you will be ready to use IBM Cognos BI. © Copyright IBM Corp.

go to c10_location/instlog. Use the installation wizard to install IBM Cognos BI components on one computer. Copy the generated transfer specification file to the computer where you plan to install IBM Cognos BI. type the following. In a command or terminal window. and copy the contents of the disk to your computer. On the computer where you plan to install the software.2. go to the operating system directory where you copied the installation files. 2. see the LA_language_code and notices files in either of these locations: v on the product disk in the root installation directory for the operating system v on the computer from which you copied the transfer specification file in the c10_location\license\product directory 8. Transfer specification file product codes Product_code BISRVR CRNSRVR BIMODEL CMMSRVR BIMEMOD BITRSFRMR BISAMPLES LP Product IBM Cognos BI Server IBM Cognos BI Reporting Server IBM Cognos Framework Manager IBM Cognos Metrics Manager IBM Cognos Metric Designer IBM Cognos BI Transformer Samples Supplementary Language Documentation 4. 3. Save the transfer specification file in the directory where you copied the installation files. Type the following command: v On Windows. 9.1: Installation and Configuration Guide . Where product_code is as listed in the following table: Table 94. 7. change the I Agree property to y. do one of the following: v Insert the appropriate product installation disk.Use a response file from an installation on another computer Use the following steps to duplicate an installation from one computer to another without being prompted for information. 6. In the License Agreement dialogs. Open the transfer specification file in a text editor.ats. The filename format is ts-product_code-version-yyyymmdd_hhmm. This action means that you are accepting the license agreement.ats 408 IBM Cognos Business Intelligence Version 10. v Copy the product installation files you downloaded to your computer. Procedure 1. 10.ats file: issetup -s location\filename. Locate the transfer specification file (. After the installation has completed. To read the terms of the license agreement.ats) that was generated during the installation. 5. where location is the directory where you copied the filename.

for the APPFOLDER= property./issetupnx -s location/filename.ats file. go to the directory for your operating system and type . On the computer where you plan to install the software.ats file. 7. Errors are recorded in the c10_location\instlog directory in a summary error log file.txt. 4. In the [Component List] section. Tip: There should be no space on either side of the equal sign. log messages are sent to a log file in the Temp directory./issetup -ats filename v On Windows computers. Type the installation location in APPDIR=location. Enter 0 if you do not want to install the component. check the log files for error messages. Use a response. After all errors are resolved. type a name for the Start menu shortcut. to generate the a response.ats file. Chapter 17. Using an unattended installation and configuration 409 . For a Windows installation.txt. do one of the following: v Insert the appropriate product installation disk. The filename format is tl-product_code-version-yyyymmddhhmm_summary-error. In the License Agreement dialogs. type: .ats file. 2. Modifying a response file Generate and modify a response file to specify and record your installation preferences. v Copy the product installation files you downloaded to your computer. and copy the contents of the disk to your computer.ats v On UNIX or Linux where you do not have XWindows. to generate the a response. Open the response. enter 1 for each component you want to install. Each section in the file corresponds to a dialog box in the installation wizard. v To use the response file that is provided with the installation.ats file in a text editor. see the LA_language_code and notices files in either of these locations: v on the product disk in the root installation directory for the operating system v on the computer from which you copied the transfer specification file in the c10_location\license\product directory 5. type: .ats Results If a return status other than zero (0) is returned. go to the directory for your operating system and type issetup -ats filename 3. To read the terms of the license agreement. v On UNIX computers. If errors occur before sufficient initialization occurs. This action means that you are accepting the license agreement./issetup -s location/filename. (=). change the I Agree property to y. 6. The filename format is tl-product_code-versionyyyymmdd-hhmm. go to the directory for your operating system and find the response. You can also modify the response file template that is provided. Procedure 1.v On UNIX or Linux. you can set up an unattended configuration.

The filename format is tl-product_code-version-yyyymmddhhmm_summary-error.txt./issetup -s -displayLog. Results If a return status other than 0 (zero) is returned. log messages are sent to a log file in the Temp directory. 2. For the install information in the [Install Conditions] section. 9. go to “Starting an unattended installation.ats file and display the status. where location is the directory where you copied the filename. Go to the directory where you saved the response.2.1: Installation and Configuration Guide . 8. Errors are recorded in the c10_location\instlog directory in a summary error log file.txt.ats file to a local directory after you make the necessary changes. to start a silent installation by using the default response.” Starting an unattended installation You can start an unattended installation and either choose to display or not display messages during the installation process. After all errors are resolved. type the following. What to do next When you are ready to run the silent installation.ats v On UNIX or Linux where you do not have XWindows: . type 1 for the ALLUSERS_FLAG= property.ats file with no messages displayed during the installation. v On UNIX or Linux. For example. you can add the -nomsgboxes option to the issetup command. you can set up an unattended configuration. to start a silent installation by using the default response. 410 IBM Cognos Business Intelligence Version 10. type: . The filename format is tl-product_code-versionyyyymmdd-hhmm. you can add the -displayLog option to the issetupnx command. At the command prompt. type: . enter 1 if the condition is true. Save the response./issetup -s location/filename. check the log files for error messages.ats file.Tip: To ensure that the shortcut folder is visible to all users. type one of the following commands: v On Windows. Enter 0 if the condition is false. For example. to view the status of the installation on the screen.ats file: issetup -s location\filename./issetupnx -s location/filename. Procedure 1.ats Note: In a UNIX or Linux environment. type: issetup -s -nomsgboxes.ats To bypass displaying messages on the screen. If errors occur before sufficient initialization occurs.

fonts. locate and open the folder. type . Click Save. 8. see “Changing Global Settings” on page 272. Before you begin Ensure that the configuration settings on the computer where you are exporting the configuration are appropriate to use on another computer with the same installed components. You can then run IBM Cognos Configuration in silent mode. 7. 10. 3.csv file in the c10_location/logs directory.sh -s v On Windows. Procedure 1. 5. Copy the exported configuration file to the c10_location/configuration directory on the computer where you plan to use the unattended configuration. Go to c10_location/bin or c10_location/bin64 directory. see the cogconfig_response. you must export a configuration from an existing installation that has the same IBM Cognos BI components installed. from the File menu. 6. in the Look in box. click Export as. For more information. product locale./cogconfig. type a name for the configuration file. you must also copy the global configuration file to the computer where you plan to use the unattended configuration.xml. For example. copy the coglocale. ensure this setting is appropriate for the new computer's configuration. if you changed the host name portion of the Gateway URI property from localhost to an IP address or computer name.bat -s Tip: To view log messages that were generated during an unattended configuration. If you want to export the current configuration to a different folder. Chapter 17. If you changed the global configuration on the source computer. When prompted about exporting decrypted content. 2. 9. A value of zero (0) indicates success and all other values indicate that an error occurred. If you made changes to the global configuration settings. In the File name box. Rename the file to cogstartup. Global configuration includes such settings as content locale. You can check if the unattended configuration was successful by checking the return status. The exported configuration contains the properties of the IBM Cognos BI components that you installed on one computer.Use an unattended configuration To use an unattended configuration. In IBM Cognos Configuration. 4. Using an unattended installation and configuration 411 .xml file to the c10_location/configuration directory on the computer where you plan to do the unattended configuration. and cookie settings. Type the following command: v On UNIX or Linux. type cogconfig. currencies. click Yes.

Enter 0 if you want to leave the component installed.xml file. type . Go to the c10_location/uninstall directory.ini in a text editor. 5. 2. From the command line.Results IBM Cognos Configuration applies the configuration settings specified in the cogstartup. type uninst -u -s v On UNIX or Linux. Use an unattended uninstallation Use an unattended uninstallation to automate the removal of components on several computers that have the same components or remove components on a UNIX or Linux environment that does not have XWindows./uninstnx -u -s 412 IBM Cognos Business Intelligence Version 10. starts IBM Cognos service or process. type the following command: v On Windows. all installed components are set to be removed.1: Installation and Configuration Guide . and if applicable. In the section named [Package List]. enter 1 for each component you want to uninstall./uninst -u -s v On UNIX or Linux without XWindows. 6. go to the c10_location\uninstall directory. encrypts credentials. Open the file named uninst. At the command prompt. By default. 3. generates digital certificates. Procedure 1. type . Save and close the file. The packages listed in the [Package List] section are described in the following table: Package code BISRVR CRNSRVR BIMODEL CMMSRVR BIMEMOD BITRSFRMR BISAMPLES LP Product IBM Cognos BI Server IBM Cognos BI Reporting Server Framework Manager IBM Cognos Metrics Manager Metric Designer IBM Cognos BI Transformer Samples Supplementary Language Documentation 4.2.

If you are running IBM Cognos BI in an application server environment. you may have to perform this action manually. type: kill -TERM pid 3. To uninstall IBM Cognos Business Intelligence. and you retain these files until you delete them manually. After you have undeployed IBM Cognos BI components. To uninstall IBM Cognos BI. type . go to the c10_location/uninstall directory and type the appropriate command: v If you use XWindows. 4. use the administration tool provided with the application server to stop the application if it is running and undeploy the Java portion of IBM Cognos BI components. © Copyright IBM Corp. Follow the prompts to complete the uninstallation. you uninstall server components and modeling tools. and from the Actions menu. Stop the IBM Cognos BI process: v If you run XWindows. v If you do not run XWindows. If you want to keep your database after uninstalling. Your installation location remains on your computer. Uninstall IBM Cognos Business Intelligence on UNIX or Linux operating systems If you no longer require IBM Cognos Business Intelligence or if you are upgrading on your UNIX or Linux operating system. start IBM Cognos Configuration.Chapter 18. Important: Do not delete the configuration and data files if you are upgrading to a new version of IBM Cognos BI and you want to use the configuration data with the new version. 2013 413 . such as configuration and user data files. Uninstalling IBM Cognos BI It is important to use uninstall programs to completely remove all files and modifications to system files. uninstall IBM Cognos BI. click Stop. Procedure 1. 2005./uninst -u v If you do not use XWindows. therefore. complete the steps in this section to uninstall on UNIX and Microsoft Windows operating systems. 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 BI process by typing the following command: ps -ef | grep cogbootstrapservice 2. the default location for the database files is in the c10_location/contentstore directory. Uninstalling does not remove any files that changed since the installation. do not delete this directory. Many application servers do not completely re