COGNOS(R) 8 BUSINESS INTELLIGENCE

INSTALLATION AND CONFIGURATION GUIDE

Cognos 8 Business Intelligence Installation and Configuration Guide 01-08-2005 CR Transfer 8.1

Cognos(R) 8 Business Intelligence Readme INSTALLATION AND CONFIGURATION GUIDE

THE NEXT LEVEL OF PERFORMANCE

TM

Product Information
This document applies to Cognos 8 Version 8.1 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site (http://support.cognos.com).
(R)

Copyright
Copyright (C) 2005 Cognos Incorporated. Portions of Cognos(R) software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated.

Table of Contents
Introduction 7 Chapter 1: Components Used by Cognos 8 9 Server Components 9 Modeling Components 10 Third-Party Components 11 Cognos 8 With Cognos Series 7 Applications 11 Chapter 2: Distribution Options for Cognos 8 13 Distributing Cognos 8 Reporting Components 13 All Components on One Computer 13 Gateways on Separate Computers 14 Application Tier Components and Content Managers on Separate Computers 15 Cognos 8 Products on the Same Computer 17 Distributing Framework Manager Components 17 Distributing Cognos 8 Scorecarding Components 18 All Components on One Computer 19 Gateways on Separate Computers 19 Application Tier Components and Content Managers on Separate Computers 20 Cognos 8 Products on the Same Computer 22 Distributing Metric Designer Components 22 Chapter 3: Workflows for Cognos 8 25 Installing Cognos 8 with Metric Studio 25 Installing Cognos 8 without Metric Studio 27 Adding Metric Studio to a Cognos 8 Installation 29 Chapter 4: Upgrade Considerations for Cognos 8 31 New File and Directory Names After Upgrade 32 Upgrade ReportNet to Cognos 8 33 Upgrading Using the Silent Configuration Option 37 Upgrade Metrics Manager to Cognos 8 38 Upgrade Metrics Manager and Security Information 38 Run ReportNet and Cognos 8 at the Same Time 41 Chapter 5: Installing Cognos 8 43 Install Server Components 43 Default Settings for Cognos 8 48 Install Framework Manager 49 Default Settings for Framework Manager 50 Install Metric Designer 50 Default Settings for Metric Designer 52 Chapter 6: Setting Up the Environment 53 Create Databases for the Content Store and Metric Store 53 Set Up the Database Client for the Content Store or Metric Store 58 Setting Up Environment Variables on UNIX for the Metric Store 59 Update the Java Environment 60 Configure the Web Server 61 Web Browser Settings 62 Configure the Router to Test Whether a Dispatcher is Available 63 Set Up the Data Source or Import Source Environment 63

Installation and Configuration Guide 3

Chapter 7: Configuring Cognos 8 67 Start Cognos Configuration 67 Configuring Single Computer Installations 68 Set Database Connection Properties for the Content Store 68 Specify a Mail Server Account and Notification Database 70 Create a Metric Package 71 Test the Installation and Configuration 72 Finishing the Configuration 73 Configuring Distributed Installations 74 Configuring Content Manager Computers 75 Configuring Application Tier Components Computers 79 Configure Gateway Computers 81 Create a Metric Package 82 Configuring Framework Manager Computers 84 Configure Metric Designer 86 Test the Installation and Configuration 88 Changing Default Configuration Settings 89 Change a URI 90 Configure Cryptographic Settings 92 Configuring the SSL Protocol 93 Configure Cognos 8 Components to Use Cognos Application Firewall 97 Configure Temporary File Properties 98 Configuring Log Messages 98 Changing the Gateway 101 Configure the Gateway to Use a Namespace 104 Enable and Disable Services 105 Specify Resources for the Cognos 8 Service 105 Global Settings 106 Configuring Fonts 111 Change the Default Font for PDF Reports 112 Change the Location of Map Charts for Report Studio 113 Configuring Portal Services 113 Specify the Location of the Applications.xml File 114 Configuring Security for Portal Services 114 Configuring Cognos 8 Components to Use an Authentication Provider 122 Disable Anonymous Access 123 Restrict User Access to Cognos 8 123 Configuring Cognos 8 Components to Use Active Directory Server 124 Configuring Cognos 8 to Use Cognos Series 7 Namespace 127 Configuring Cognos 8 to Use a Custom Authentication Provider 130 Configuring Cognos 8 Components to Use LDAP 131 Configuring Cognos 8 Components to Use Netegrity SiteMinder 137 Configuring Cognos 8 Components to Use an NTLM Namespace 139 Configuring Cognos 8 to Use SAP 140 Test the Namespaces 142 Delete an Authentication Provider 142 Chapter 8: Changing Application Servers 145 Check the Setup of Cognos Components 146 Back Up Existing Cognos Information 146 Set Environment Variables 147 Copy Cognos Security Provider Files 148 Configure Cognos Components to Run Within the Application Server 148 Change the Application Server Startup Script 150 Configure Application Server Properties and Deploy Cognos Components 151 Enable SSL 154 Configuring the Web Server 154

4

Unregister Dispatchers 154 Import Content Store Data 155 Upgrade from ReportNet to Cognos 8 in an Application Server Environment 155 Upgrade from Metrics Manager to Cognos 8 in an Application Server Environment 155 Chapter 9: Advanced Configuration Options 157 Change the Type of JVM Used by Cognos 8 157 Changing the Version of JVM Used by Cognos 8 Components 158 Configuring Cognos 8 Components to Use a Third-party Certificate Authority 160 Generate Keys and Certificate Signing Requests 160 Configure Cognos 8 Components to Run Within a Third-party Certificate Authority 162 Chapter 10: Setting Up the Samples 163 Restore Backup Files for the Samples Databases 163 Create Data Source Connections to the Samples Relational Databases 164 Set up Microsoft SQL Server Analysis Services Cube Samples 165 Set up DB2 Cube Sample 166 Create Data Source Connection to OLAP Data Sources 166 Set up the Metric Studio Sample 167 Import Metric Data into Metric Store 167 Set up the Metric Designer Sample 169 Set up the Event Studio Sample 170 Import the Samples (Cognos_Samples. GO_Events) 170 Return the GOSL Database to the Original State (Event Studio) 171 Sample Database Models 171 Remove the Samples Databases from Cognos 8 172 Chapter 11: Setting Up an Unattended Installation and Configuration 173 Set Up an Unattended Installation 173 Set Up an Unattended Configuration 175 Chapter 12: Uninstalling Cognos 8 177 Uninstall Cognos 8 on UNIX or Linux 177 Uninstall Cognos 8 on Windows 177 Uninstall Framework Manager 178 Uninstall Metric Designer 179 Appendix A: Manually Configuring Cognos 8 181 Manually Configuring Cognos 8 on UNIX and Linux 181 Manually Change Default Configuration Settings on UNIX and Linux Computers 181 Manually Change the Global Settings on UNIX and Linux Computers 184 Run Cognos Configuration in Silent Mode on UNIX and Linux Computers 185 Manually Create a Cognos Archive File 185 Appendix B: Troubleshooting 187 Log Files 187 Run Database Cleanup Scripts 188 Improve Metric Store Database Performance 190 Problems Starting Cognos 8 190 CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration 191 Cognos BI Server Not Available When Starting Cognos 8 192 Cognos 8 Services Fail to Restart After a Network Outage 195 No Warning That Installing a Later Version of Cognos 8 Will Automatically Update the Earlier Version of the Content Store 195 DPR-ERR-2058 Error Appears in Web Browser When Starting Cognos 8 195 DPR-ERR-2022 Error Appears in Web Browser When Starting Cognos 8 196 Application Server Startup Script Fails 197 Problems Configuring Cognos 8 197 Installation and Configuration Guide 5 . GO_Metrics. Cognos_PowerCube.

Error Trying to Encrypt Information When Saving Your Configuration 197 Unable to Save Your Configuration 198 Java Error When Starting Cognos Configuration 198 Cryptographic Error When Starting Cognos Configuration 198 Current Configuration Settings Are Not Applied to Your Computer 199 Font on UNIX Not Found When Starting Cognos Configuration 199 Images Are Missing in PDF Reports 199 Some Users Are Prompted to Log On When Using Active Directory Server 200 Errors When Logging On Using an SAP Authentication Provider 200 HTTP 500 Server Error for Oracle Application Server 200 CGI Timeout Error While Connected to Cognos 8 Components Through a Web Browser 200 Servlet Failed with IOException Error on WebLogic Server Console 201 Servlet Class Fails to Load in WebLogic 201 Glossary 203 Index 207 6 .

Installation and Configuration Guide 7 . and Portal Services. Note that the availability of the studios described in these documents depends on your licensing permissions. scorecarding. Cognos 8 is a Web product with integrated reporting. and may be referred to in this document. developing installation strategies. and setting up samples. and event management features. To change your licensing permissions. Document Cognos 8 Administration and Security Guide Description Managing servers.Introduction This guide contains instructions for installing. analysis. security. reports. upgrading. setting up Cognos samples. and customizing Cognos 8 Helping administrators to quickly identify and solve problems Using Cognos Configuration to configure Cognos 8 Planning the Cognos 8 architecture. and testing Cognos 8.cognos. visit the Cognos support Web site (http://support. The following documents contain related information. To use this guide. and optimizing performance Creating and publishing models using Framework Manager Helping administrators to quickly identify and solve problems Authoring scorecard applications and monitoring the metrics within them Monitoring metrics within a scorecard application Creating extracts that map and transfer information from relational and dimensional data sources to Metric Studio Cognos 8 Troubleshooting Guide Cognos Configuration User Guide Cognos 8 Architecture and Planning Guide Framework Manager User Guide Cognos 8 Troubleshooting Guide Metric Studio User Guide for Authors Metric Studio User Guide Metric Designer User Guide This document is available as online help and as an online book. configuring. see your administrator. changing application servers. you should be familiar with • reporting concepts • scorecarding concepts • database and data warehouse concepts • security issues • basic Windows and/or UNIX administration skills • the existing server environment and security infrastructure in your organization For more information about using this product.com).

or the whole book. 8 . or the Help menu and help button in Windows products. You can also download the online help from the Cognos support Web site (http://support. you can click the following link to open a printable version of this document (PDF). and maintaining the Cognos software. reference books. However. Books for Printing The information in each online help system is available in online book format (PDF). the information from a given help system may be divided into more than one online book. Online books are available from the introduction to the online help for each component. You can print selected pages. non-transferable license to use. Use online books when you want to print a document or when you want to search the whole document. All online books are available on the Cognos documentation CD. and other materials to meet the needs of our varied audience. operating. Online help is available from the help button in a Web browser. Our documentation includes user guides. a section.cognos. solely for the purpose of providing internal training on. in printed or electronic format. and reproduce the copyright materials. tutorial guides.Introduction From within the online help. copy. Cognos grants you a non-exclusive. You can also read the product readme files and the installation guides directly from Cognos product CDs.com). Online Help All information is available in online help.

as well as the server functionality for routing and processing user requests. and events. Server components include the following tools: Cognos Connection Cognos Connection is a Web portal provided with Cognos 8. It is accessible through Cognos Connection and any existing enterprise portal. and distribute a wide range of professional reports. Analysis Studio provides access to dimensional. providing a single access point to the corporate data available to its products. Some of these existing resources are required. and edit and modify reports created in Query Studio or Analysis Studio.Chapter 1: Components Used by Cognos 8 Cognos 8 is a Web-based business intelligence solution with integrated reporting. such as using a third-party security provider for authentication. can be integrated with Cognos Connection. analysis. users can explore. such as a Java Virtual Machine or a third-party database for the content store. professional reports created in Report Studio. Analyses created in Analysis Studio can be opened in Report Studio and used to build professional reports. and URLs to other applications. and compare dimensional data. scorecards. Other business intelligence applications. Server Components Server components provide the user interfaces for reporting. Cognos 8 integrates easily into your existing infrastructure by using resources that are in your environment. You can configure Cognos 8 products to run on supported application servers that you currently use in your environment. and event management features. OLAP (online analytical processing). By default. analysis. Analysis Studio In Analysis Studio. Report Studio Report Studio lets report authors create. Users can run all their Web-based Cognos 8 applications through Cognos Connection. Installation and Configuration Guide 9 . Query Studio Query Studio is an ad-hoc reporting tool that lets users with little or no training quickly design. They can also define corporate-standard report templates for use in Query Studio. and for creating reports. analyzing. scorecarding. It provides a single point of entry for querying. analyze. and dimensionally modeled relational data sources. and event management. Other resources are optional. Cognos 8 uses Tomcat as an application server. scorecarding. Cognos Viewer Cognos Viewer is a portlet in which you can view and interact with any type of published Cognos content. edit. Cognos 8 includes Cognos 8 Business Intelligence Server and Cognos 8 Business Intelligence Modeling. create and save reports to meet reporting needs not covered by the standard. and organizing data.

sending an email to the appropriate people. Content Manager Content Manager is the Cognos 8 service that manages the storage of customer application data. people are alerted to take action. and monitor the status of events. a support call from a key customer or the cancellation of a large order may trigger an event. which reside on one or more Web servers.iqd) files. metrics. JDBC. integrated business view of any number of heterogeneous data sources. Metric Designer Metric Designer is the Cognos 8 modeling tool used to create extracts for use in Cognos 8 scorecarding applications. Gateways are often CGI programs. and manage the Cognos namespace. and improves performance when querying data from different data sources.Chapter 1: Components Used by Cognos 8 Event Studio In Event Studio. but may follow other standards. Users can monitor. analyze. models. Modeling components include the following tools: Framework Manager Framework Manager is the Cognos 8 modeling tool for creating and managing business-related metadata for use in Cognos 8 analysis and reporting. For example. Cognos Configuration Cognos Configuration is a tool that you use to configure Cognos 8. deliver alerts by email. configuration data. providing a single. Transformer Transformer is a modeling tool for creating PowerCubes for use with Cognos Series 7 and Cognos 8. When an event occurs. Content Manager is needed to publish models. manage scheduling information. Metric Studio In Metric Studio. 10 . retrieve or store report specifications. Metadata is published for use by reporting tools as a package. including security. Content Manager stores information in a content store database. Modeling Components Modeling components model data within data sources to structure and present data in a way that is meaningful to users. Open XML and WSDL. 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. Gateway Web communication in Cognos 8 is typically through gateways. report specifications. Agents can publish details to the portal. and report output. you can create and deliver a customized scorecarding environment for monitoring and analyzing metrics throughout your organization. and report on time-critical information by using scorecards based on cross-functional metrics. run and distribute reports based on events. Composite Information Server Composite Information Server provides access to additional data sources such as LDAP. and to start and stop its services. Extracts are used to map and transfer information from existing metadata sources such as Framework Manager and Impromptu Query Definition (. A gateway is an extension of a Web server program that transfers information from the Web server to another server. such as Internet Server Application Program Interface (ISAPI) and Apache Modules (apache_mod).

You can access Series 7 entries from the following Series 7 applications. Metric Store A metric store is a relational database that contains content for metric packages. and the packages that contain them. Cognos Contributor You can access unpublished Cognos Contributor cubes that are secured against a Series 7 namespace. For information about accessing Series 7 entries. Content Store The content store is a relational database that contains data that Cognos 8 needs to operate. connection information for data sources. dimensional cubes. files. see the Administration and Security Guide. such as user preferences. Design models and log files are not stored in the content store. information about the external namespace. Data Sources Data sources are relational databases. You can then use the Series 7 PowerPlay authoring tools to create and edit Series 7 PowerPlay reports. such as report specifications. Cognos Series 7 Upfront Series 7 reports and cubes can be published to the Cognos 8 portal. For example. see the documentation provided with your edition of Transformer. Application Tier Components use data source connections to access data sources. Third-Party Components In addition to the tools provided with Cognos 8. or other physical data stores that can be accessed through Cognos 8. and information about scheduling and bursting reports. and the Cognos namespace itself. A metric store also contains Metric Studio settings. Map Manager Administrators and modelers use a Windows utility named Map Manager to import maps and update labels for maps in Report Studio. it requires the following components that are created using third-party resources. Cognos 8 With Cognos Series 7 Applications If you configure Cognos 8 to use the Cognos Series 7 namespace. For map features such as country and city names. When you run a Series 7 report. one metric store may contain content for a sales application and another metric store may contain content for a finance application. published models. For information about using Map Manager. the report runs in the Series 7 application used to create it. The Cognos 8 service that uses the content store is named Content Manager. More than one metric store may be created. you can see Series 7 entries in Cognos Connection. see the Map Manager Installation and User Guide. Installation and Configuration Guide 11 . administrators and modelers can define alternative names to provide multilingual versions of text that appears on the map.Chapter 1: Components Used by Cognos 8 For information about installing and configuring Transformer. Cognos Series 7 PowerPlay You can access NewsIndexes and NewsBoxes of the Series 7 version of Cognos Upfront from Cognos Connection.

Chapter 1: Components Used by Cognos 8 Cognos Finance You can access Cognos Finance cubes that are secured against a Series 7 namespace. 12 . Transformer You can access Cognos PowerCubes generated by Transformer 7.2 and later.

decide how you will install it in your environment. query databases. In addition to installing the Content Manager. all server components for Cognos 8 reporting. or distribute them across a network. The best distribution option depends on your reporting or scorecarding requirements. you must install Framework Manager. In this option. and gateway components. All Components on One Computer You can install all the Cognos 8 reporting components on one computer. the metadata modeling application for business intelligence. If your Web server is on UNIX or Linux. In the following diagram. After installing Cognos 8 reporting components. availability. the single computer must also be running a Web server. If you plan to install both Cognos 8 reporting and scorecarding components on the same computer. you must install the Windows-based Framework Manager on a separate computer that runs on Windows. Because the gateway must be located with the Web server. or security based on the processing characteristics of your organization. Configuration requirements differ depending on whether you install all components on a single or multiple computers. you must configure them so they can communicate with each other. and preferences. This option is typically used for a demonstration or in a proof of concept environment. Application Tier Components. and the remaining Cognos components are on other computers. the gateway and Web server are on one computer. are installed on one computer. we recommend that you install them in the same installation location. except Framework Manager. such as the Content Manager. Choose this option to maximize performance. You can install these components using any of these options: • Install all components on one computer. The content store. Installation and Configuration Guide 13 . resources. • Install Cognos 8 reporting components on the same computer as other Cognos 8 products. Choose this scenario for proof of concept or demonstration environments where the user load is small. you can install Framework Manager and the content store on a computer separate from the Application Tier Components. capacity.Chapter 2: Distribution Options for Cognos 8 Before implementing Cognos 8. Application Tier Components. No matter which Cognos installation scenario you follow. Cognos 8 shares components for reporting and for scorecarding. • Install Application Tier Components and Content Manager on separate computers. you specify where to place the gateways. • Install the gateway on a separate computer. and Framework Manager are located on separate computers. You may choose this option if you have existing Web servers available to handle Cognos component requests. and Content Manager. You can install all Cognos 8 components on one computer. Distributing Cognos 8 Reporting Components When you install Cognos 8 reporting components.

Using multiple Web servers to manage incoming requests provides a better level of service.Chapter 2: Distribution Options for Cognos 8 Framework Manager Single-Computer Installation of Cognos Server Components Web server Gateway Application Tier Components Content Manager Content store Query databases Configuration Requirements If you install all server components for Cognos 8 reporting on the same computer. you may want to install a gateway on each Web server. You can install the gateway and a Web server on one computer. you must then • configure your Web server to view Cognos content • specify connection information to the content store • set up an email account for notifications (if you intend to email reports) Gateways on Separate Computers The gateway manages communications among Cognos 8 reporting components. If you install only the gateway component on the same computer as the Web server. 14 . and install the remaining Cognos 8 reporting components on other computers. This separation of processing may be required if you have a firewall between the Web server and your Application Tier Components computers. two Web servers each have a gateway installed. If you have a Web farm. It can reside on one or more Web servers. your Web server manages the core Web services and does not process user requests. Incoming requests are passed to either gateway and forwarded to the Application Tier Components computer. In the following diagram.

You also have better accessibility and throughput than on a single computer. you can install the Application Tier Components on multiple computers dedicated to processing incoming requests. or on different computers. Content Manager stores all report specifications. you must ensure that you can view Cognos content and that the gateways can communicate with other Cognos components. incoming requests are routed to a gateway. Installation and Configuration Guide 15 . which queries the content store and sends the results back to the report server for rendering. you distribute and balance loads among the computers. schedule jobs. By installing the Application Tier Components on multiple computers. as well as failover support. and jobs in the content store. and render reports. Installing on different computers can improve performance. You can install the Application Tier Components and Content Manager on the same computer. packages. availability. To improve scalability in an environment in which there is typically a large volume of report requests to process. On each computer where the gateway is installed you must • configure cryptographic properties • configure your Web server to view Cognos content • configure the Dispatcher URIs Application Tier Components and Content Managers on Separate Computers One or more report servers use the Cognos Connection interface to balance loads. The report server forwards the request to Content Manager. results. The gateway forwards the request to one of the Application Tier Components computers. In the following diagram. folders. perform queries.Chapter 2: Distribution Options for Cognos 8 Web servers Gateways Multiple Gateways Installation Application Tier Components Content Manager Content store Query databases Configuration Requirements If you install one or more gateways on separate computers. access data. and capacity.

unsaved session data is lost. For failover support. When the new active Content Manager takes over. information about the external namespace and the Cognos namespace itself. When an active Content Manager fails. Content Manager stores data that Cognos 8 needs to operate. and information about scheduling and bursting reports. such as report specifications. One becomes active only if the computer on which the active Content Manager is installed fails. although only one is active at any time. to ensure that they can communicate with other Cognos 8 reporting components you must • configure cryptographic properties • specify all Content Manager URIs • specify the Dispatcher URIs • specify the Dispatcher URI for external applications More Than One Content Manager You can install any number of installations of Content Manager. published models.Chapter 2: Distribution Options for Cognos 8 Web servers Gateways Multiple Application Tier Components Installation Application Tier Components Default active Content Manager Standby Content Managers Content store Query databases Configuration Requirements If you install one or more Application Tier Components on a separate computer. you must • configure cryptographic properties • specify connection information to the content store • specify the Dispatcher URIs 16 . users may be prompted to logon. Configuration Requirements On each computer where you install Content Manager. You may choose to install Content Manager separately from the Application Tier Components if your data contains sensitive information. Data is then stored in the data tier along with your security information. and the packages that contain them. it is advisable to install Content Manager on two or more computers. The content store is a relational database management system (RDBMS). There is only one content store for each Cognos installation. The other installations each act as a standby Content Manager. connection information for data sources.

we strongly recommend that you install them in the same installation location. The installation program checks to determine whether other Cognos 8 components exist in the installation location. If you use a Web server other than Microsoft IIS. and you have medium-sized and large models (approaching 1 MB in size). If you install more than one Cognos 8 product on the same computer. including the gateway. Distributing Framework Manager Components Framework Manager can be installed on a computer that contains other Cognos 8 reporting components or on a computer that is separate from other Cognos 8 reporting components. For either route. If a component exists and can be shared. and your Application Tier Components. Content Manager. see "Configuring Framework Manager Computers" (p. the modeling tool uses the BI Bus SOAP API. Web Servers Other Than Microsoft IIS For Web servers other than Microsoft Internet Information Services (IIS). 84). the models are broken into smaller pieces (chunked) for transmission. no functional difference exists between the two communication routes between the modeling tool and the Application Tier Components dispatcher. If you use the Web server route. your Web server. For more information about configuring Framework Manager. and how you configure it. Framework Manager stores run-time models on the Application Tier Components computer. it is not reinstalled. we recommend that you configure the modeling tool to communicate through your Web server gateway (Route 1). content store.Chapter 2: Distribution Options for Cognos 8 • • • specify all Content Manager URIs specify the Dispatcher URI for external applications setup an email account for notifications (if you want to email reports) Cognos 8 Products on the Same Computer Cognos 8 products are designed to share components. This eliminates the need to set up additional communications channels if you use firewalls to separate the modeling tool. Cognos Connection. can depend on how large your metadata models are and on which Web server you use. and Cognos Configuration. It can communicate with the server using one of two routes: • Route 1: through the Web server gateway • Route 2: directly to the Application Tier Components dispatcher Route 1 Route 2 Framework Manager Framework Manager Web server Gateway Web server Gateway Application Tier Components Dispatcher Application Tier Components Dispatcher Where you install Framework Manager. Installation and Configuration Guide 17 .

you must configure Framework Manager to communicate with the dispatcher. You must ensure that Framework Manager can communicate with Cognos 8 reporting components. You can install these components using any of these options: • Install all components on one computer. and Content Manager. You may choose this option if you have existing Web servers available to handle Cognos component requests. you can install the modeling tool in the same architectural tier as the Application Tier Components. either through the gateway or directly. On the computer where Framework Manager is installed. In this option. communications issues can arise. if you use Microsoft IIS. Framework Manager Firewall Firewall Application Tier Components 3 2 Communication with Application Tier Components Web server Gateway 1 3 To avoid this requirement. you must configure the modeling tool to communicate directly with the Application Tier Components dispatcher. • Install the gateway on a separate computer. you specify where to place the gateways.Chapter 2: Distribution Options for Cognos 8 Microsoft IIS Web Servers Microsoft IIS does not support chunking. As a result. which can be installed on one or more Web servers. and you build medium-sized or large models (approaching 1 MB in size). If the modeling tool is installed outside a network firewall that protects the Application Tier Components. and the remaining Cognos components are on other computers. This option is typically used for a demonstration or in a proof of concept environment. Framework Manager Firewall Firewall Application Tier Components 3 2 Communication with Application Tier Components Web server Gateway 1 3 Configuration Requirements Framework Manager communicates with the Application Tier Components. measures must be taken to ensure that communication can occur through the network firewall. 18 . Application Tier Components. This is done by configuring the Dispatcher URI for external applications. Firewall Considerations When the modeling tool communicates directly with the dispatcher. To publish models. configure cryptographic properties and the following environment properties: • Gateway URI • Dispatcher URI for external applications Distributing Cognos 8 Scorecarding Components When you install Cognos 8 scorecarding components. the gateway and Web server are on one computer.

Cognos 8 products share components. Installation and Configuration Guide 19 . Choose this option to maximize performance. It can reside on one or more Web servers.Chapter 2: Distribution Options for Cognos 8 • Install Application Tier Components and Content Manager on separate computers. If you plan to install Cognos 8 scorecarding components on the same computer as other Cognos 8 products. If your Web server is on UNIX. you may want to install a gateway on each Web server. • After installing Cognos 8 scorecarding components. The metric store can also be installed on a different computer. The content store and metric store are located on separate computers. and install the remaining Cognos 8 scorecarding components on other computers. The metric store is usually installed on the same computer as Content Manager. are installed on one computer. or security based on the processing characteristics of your organization. and gateway components. You can install the gateway and a Web server on one computer. you must • configure your Web server to view Cognos content • specify connection information to the content store Gateways on Separate Computers The gateway manages communications among Cognos 8 scorecarding components. Application Tier Components. you must configure them so they can communicate with each other. Install Cognos 8 scorecarding components on the same computer as other Cognos 8 products. 50). In the following diagram. All Components on One Computer You can install all the Cognos 8 scorecarding components on one computer. Because the gateway must be located with the Web server. Choose this scenario for proof of concept or demonstration environments where the user load is small. such as the Content Manager. the single computer must also be running a Web server. except Metric Designer. capacity. No matter which Cognos installation scenario you follow. Single-Computer Installation of Cognos 8 scorecarding Components Web server Gateway Application Tier Components Content Manager Content store Metric stores Configuration Requirements If you install all Cognos 8 scorecarding components on the same computer. all Cognos 8 scorecarding components. we recommend that you install them in the same installation location. availability. the metadata modeling application for scorecarding. you may choose to install Metric Designer (p. you must install the Windows-based Metric Designer on a separate computer that runs on Windows. you can install Metric Designer and the content store on a computer separate from the Application Tier Components. If you have a Web farm. Using multiple Web servers to manage incoming requests provides a better level of service. In addition to installing the Content Manager.

Chapter 2: Distribution Options for Cognos 8 If you install only the gateway component on the same computer as the Web server. By doing this. Incoming requests are passed to either gateway and forwarded to the Application Tier Components computer for processing. you distribute and balance loads among the computers. or on different computers. This separation of processing may be required if you have a firewall between the Web server and your other Cognos 8 scorecarding components. execute tasks. The gateway forwards the request to one of the Application Tier Components for processing. availability. You also have better accessibility and throughput than on a single computer. your Web server manages the core Web services and does not process user requests. you can install the Application Tier Components on multiple computers dedicated to processing incoming requests. and render scorecards. You can install the Application Tier Components and Content Manager on the same computer. Installing on different computers can improve performance. you must • configure cryptographic properties • configure your Web server to view Cognos content • configure the Dispatcher URIs Application Tier Components and Content Managers on Separate Computers Application Tier Components process Cognos requests. such as the data source connections in the content store. as well as failover support. 20 . Content Manager stores and retrieves information. and capacity. In the following diagram. two Web servers each have a gateway installed. incoming requests are routed to a gateway. balance loads. To improve scalability in an environment in which there is typically a large volume of report requests to process. you must ensure that you can view Cognos content and that the gateways can communicate with other Cognos components. Web server Gateway Multiple Gateways Installation Application Tier Components Content Manager Content store Metric stores Configuration Requirements If you install one or more gateways on a separate computer. On each computer where the gateway is installed. In the following diagram.

such as report specifications. One becomes active only if the computer on which the active Content Manager is installed fails. users may be prompted to logon. and the packages that contain them. Configuration Requirements On each computer where you install Content Manager. published models. When an active Content Manager fails. although only one is active at any time. unsaved session data is lost. You must • configure cryptographic properties • specify all Content Manager URIs • specify the Dispatcher URIs More Than One Content Manager You can install any number of installations of Content Manager. you must • configure cryptographic properties • specify connection information to the content store • specify the Dispatcher URIs • specify all Content Manager URIs Installation and Configuration Guide 21 . and information about scheduling and bursting reports. The content store is a relational database management system (RDBMS). ensure that they can communicate with other Cognos 8 components. When the new active Content Manager takes over. The other installations each act as a standby Content Manager. For failover support. it is advisable to install Content Manager on two or more computers. You may choose to install Content Manager separately from the Application Tier Components if your data contains sensitive information. Content Manager stores data that Cognos 8 needs to operate.Chapter 2: Distribution Options for Cognos 8 Web server Gateway Multiple Application Tier Components Installation Application Tier Components Default active Content Manager Standby Content Managers Content store Metric stores Configuration Requirements If you install one or more Application Tier Components on a separate computer. connection information for data sources. information about the external namespace and the Cognos namespace itself. There is only one content store for each Cognos installation. Data is then stored in the data tier along with your security information.

see "Configure Metric Designer" (p.Chapter 2: Distribution Options for Cognos 8 Cognos 8 Products on the Same Computer Cognos 8 products are designed to share components. no functional difference exists between the two communication routes between the modeling tool and the Application Tier Components dispatcher. the models are broken into smaller pieces (chunked) for transmission. your Web server. Content Manager. If you install more than one Cognos 8 product on the same computer. communication can occur using one of two routes: • Route 1: through the Web server gateway • Route 2: directly to the Application Tier Components dispatcher Route 1 Route 2 Metric Designer Metric Designer Web server Gateway Web server Gateway Application Tier Components Dispatcher Application Tier Components Dispatcher Where you install Metric Designer. Cognos Connection. if you want to define and load a large amount of metrics from relational and dimensional data sources. and you have medium-sized and large models (approaching 1 MB in size). For more information about configuring Metric Designer. This eliminates the need to set up additional communications channels if you use firewalls to separate the modeling tool. content store. and how you configure it.iqd files). we strongly recommend that you install them in the same installation location. and Cognos Configuration. install Metric Designer to extract the data. If Metric Designer is installed on a different Windows computer from other Cognos 8 components. Web Servers Other Than Microsoft IIS For Web servers other than Microsoft Internet Information Services (IIS). 86). the modeling tool uses the BI Bus SOAP API. or Impromptu Query Definitions (. For either route. it is not reinstalled. If you use a Web server other than Microsoft IIS. can depend on how large your metadata models are and which Web server you use. including the gateway. 22 . The installation program checks to determine whether other Cognos 8 components exist in the installation location. If other Cognos 8 components are running in a UNIX environment. we recommend that you configure the modeling tool to communicate through your Web server gateway (Route 1). you must install the Windows-based Metric Designer on a Windows computer. If you use the Web server route. Install Metric Designer after installing and configuring other Cognos 8 components. and your Application Tier Components. If a component exists and can be shared. Distributing Metric Designer Components For Metric Studio. Framework Manager packages. including PowerCubes.

Chapter 2: Distribution Options for Cognos 8 Microsoft IIS Web Servers Microsoft IIS does not support chunking. communications issues can arise. 86). Metric Designer Firewall Firewall Application Tier Components 3 2 Communication with Application Tier Components Web server Gateway 1 3 To avoid this requirement. To publish models. you must configure Metric Designer to communicate with the dispatcher. and you build medium-sized or large models (approaching 1 MB in size). either through the gateway or directly. If the modeling tool is installed outside a network firewall that protects the Application Tier Components. Installation and Configuration Guide 23 . On the computer where Metric Designer is installed. As a result. which can be installed on one or more Web servers. This is done by configuring the Dispatcher URI for external applications. if you use Microsoft IIS. Metric Designer Firewall Firewall Application Tier Components 3 2 Communication with Application Tier Components Web server Gateway 1 3 Configuration Requirements Metric Designer communicates with the Application Tier Components. you can install the modeling tool in the same architectural tier as the Application Tier Components. you must configure the modeling tool to communicate directly with the Application Tier Components dispatcher. configure cryptographic properties and the following environment properties: • Gateway URI • Dispatcher URI for external applications Additional configuration is required after you install Metric Designer so that it can access some types of data sources (p. You must ensure that Metric Designer can communicate with other Cognos 8 scorecarding components. Firewall Considerations When the modeling tool communicates directly with the dispatcher. measures must be taken to ensure that communication can occur through the network firewall.

Chapter 2: Distribution Options for Cognos 8 24 .

145). Installation and Configuration Guide 25 . Installing Cognos 8 with Metric Studio You can install Cognos 8 and Metric Studio at the same time. additional tasks are required for distributed installations so that the components can communicate with each other.Chapter 3: Workflows for Cognos 8 After you decide on the appropriate distribution options (p. The following workflows show the required tasks for installing and configuring a single-computer installation and a distributed installation. Depending on the Cognos 8 solution purchased by your organization. For example. 27). Many of the tasks you perform for distributed installations are the same as those you perform for single-computer installations. see "Adding Metric Studio to a Cognos 8 Installation" (p. follow one workflow to install and configure Cognos 8 on a single computer. 29). However. We recommend that you print the workflow you plan to use. you must follow a specific workflow to install and configure Cognos 8. 89) and changing application servers (p. The workflows do not show optional configuration tasks (p. For information about installing Cognos 8 without Metric Studio or installing Framework Manager. For information about adding Metric Studio to an existing Cognos 8 installation or installing Metric Designer. Follow another workflow to install and configure Cognos 8 in a distributed installation. see "Installing Cognos 8 without Metric Studio" (p. Metric Studio may be available to you. Workflows are provided for • installing Cognos 8 with Metric Studio • installing Cognos 8 without Metric Studio • adding Metric Studio to an existing Cognos 8 installation The workflows require that you perform tasks in sequence. 13) for your environment. You can then use the printed copy as a checklist to ensure that you have completed all tasks.

set up metric store environment variables Test installation and configuration Update Java environment Finish configuration Configure Web server Configure Web browsers 26 .Chapter 3: Workflows for Cognos 8 Single-Computer Installation Install Install Cognos 8 Set up environment Create content store database Configure Set database connection properties for content store Install Metric Studio Create metric store database Configure mail server account and notification database Check default settings Set up database clients for content store and metric store Create metric package On UNIX.

These workflows show the required tasks for installing and configuring on a single computer and in a distributed installation. see "Adding Metric Studio to a Cognos 8 Installation" (p. Installation and Configuration Guide 27 . Metric Studio Application Tier Components must also be installed on all computers where Application Tier Components for other Cognos 8 products are installed. Installing Cognos 8 without Metric Studio You can install Cognos 8 without Metric Studio. For information about installing Cognos 8 with Metric Studio. A workflow is also provided for installing and configuring Framework Manager. 25). see "Installing Cognos 8 with Metric Studio" (p.Chapter 3: Workflows for Cognos 8 Distributed Installation Install Install Cognos 8 components on two or more computers Set up environment Create content store database Configure Configure Content Manager computers Install Metric Studio components on two or more computers * Create metric store database Configure Application Tier Components computers Check default settings Set up database clients for content store and metric store Configure gateway component computers On UNIX. For information about adding Metric Studio to an existing Cognos 8 installation or installing Metric Designer. 29). set up metric store environment variables Create metric package Update Java environment Test installation and configuration Configure Web server Finish configuration Configure Web browsers * In addition to the Metric Studio computers where Application Tier Components are installed.

Chapter 3: Workflows for Cognos 8 Single-Computer Installation Install Install Cognos 8 Set up environment Create content store database Configure Set database connection properties for content store Check default settings Set up database clients for content store Configure mail server account and notification database Update Java environment Test installation and configuration Configure Web server Finish configuration Configure Web browsers Distributed Installation Install Install Cognos 8 components on two or more computers Set up environment Create content store database Configure Configure Content Manager computer Check default settings Set up database clients for content store Configure Application Tier Components computers Update Java environment Configure gateway component computers Configure Web server Test installation and configuration Configure Web browsers Finish configuration 28 .

upgrade projects Adding Metric Studio to a Cognos 8 Installation You may choose to add Metric Studio to an existing Cognos 8 installation. A workflow is also provided for installing and configuring Metric Designer. see "Installing Cognos 8 with Metric Studio" (p.Chapter 3: Workflows for Cognos 8 Framework Manager Installation Set up Ensure other Cognos 8 components are installed. set up metric store environment variables Finish configuration Installation and Configuration Guide 29 . For information about installing Cognos 8 without Metric Studio. Single-Computer Installation Install Set up environment Configure Install Metric Studio Create metric store database Create metric package Check default settings Set up database clients for metric store Test installation and configuration On UNIX. configured. 27). and working Install Install Framework Manager on Windows computer Configure For distributed install. The following workflows show the required tasks for installing and configuring on a single computer and in a distributed installation where a Cognos 8 installation exists. see "Installing Cognos 8 without Metric Studio" (p. configure environment properties Check default settings If required. For information about installing Cognos 8 and Metric Studio at the same time. 25).

and working Install Install Metric Designer on Windows computer Configure For distributed install. set up metric store environment variables Test installation and configuration Finish configuration * In addition to the Metric Studio computers where Application Tier Components are installed. configured. upgrade projects 30 .Chapter 3: Workflows for Cognos 8 Distributed Installation Install Set up environment Configure Install Metric Studio components on two or more computers * Create metric store database Configure Application Tier Components computers Check default settings Set up database clients for metric store Create metric package On UNIX. Metric Designer Installation Set up Ensure other Cognos 8 components are installed. Metric Studio Application Tier Components must also be installed on all computers where Application Tier Components for other Cognos 8 products are installed. configure environment properties Ensure applications associated with the metadata sources you will use are installed and running Check default settings If required.

After upgrading to Cognos 8 using existing data. Some methods. we recommend that you set access permissions on those reports to limit user access. copying the configuration data files to the Cognos 8 installation directory. classes. Do not upgrade your report specifications if you have SDK applications that create. modify. you must plan your upgrade strategy. You can upgrade directly to Cognos 8 from the following product versions: • ReportNet 1. If both ReportNet and Metrics Manager are on the same computer and you plan to upgrade to Cognos 8. configuring Cognos 8 to use the existing content store or a copy of it. When you upgrade. Because of the potential for users to upgrade report specifications that SDK applications may depend on. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. see the Release Notes appendixes in the Cognos 8 SDK Developer Guide. If you run a ReportNet report in Cognos 8. and properties are obsolete. When upgrading from ReportNet. and enumeration sets. After a report is upgraded to Cognos 8. You can run different versions of the software on your computer at the same time. you must ensure that the configuration data from ReportNet is copied to the Cognos 8 installation location. For information about changes to methods. your SDK applications may not be able to access the upgraded report specifications. This includes backing up existing data. you must make some changes to your SDK program for it to function with the Cognos 8 version of the WSDL file. classes. For more information about setting access permissions.Chapter 4: Upgrade Considerations for Cognos 8 You must upgrade the software to move from an earlier version of ReportNet or Metrics Manager to Cognos 8. Some other methods. New report specifications have been added in Cognos 8. classes. see the Cognos 8 Administration and Security Guide. and then Metrics Manager.1 MR1 or MR2 and then upgrade to Cognos 8. upgrade ReportNet first. you must first upgrade to ReportNet 1. For information about new features in Cognos 8. For information about upgrading report specifications. Otherwise. Installation and Configuration Guide 31 . Components from different versions are not compatible. and reapplying any manual edits or customizations that you applied in the earlier version. Deprecated features continue to function as before. Before you begin upgrading. and properties have been deprecated in Cognos 8.1 MR1 or MR2 • Metrics Manager 2. properties. The strategy depends on the data that you want to use and any customizing that you have done with your existing configuration.0 or later If you have an earlier version of ReportNet. additional configuration may be required if you want to use new features. or save report specifications. see Cognos 8 New Features. it cannot be returned to the ReportNet format. and have been removed from the Cognos 8 SDK. see the Cognos 8 SDK Developer Guide. You must upgrade all components. if you want to use an existing configuration directory. it is automatically upgraded to the Cognos 8 format. but will be removed in future releases. SDK Applications You must use the Cognos 8 SDK with Cognos 8 Business Intelligence. provided that you install them in different directories and configure each to use a different content store and a different set of ports and URLs for each version.

To upgrade a project.Chapter 4: Upgrade Considerations for Cognos 8 We recommend that you do not upgrade your report specifications if you are unsure about whether you have SDK applications that create. Metrics Manager Data Stores In earlier versions. Before exporting the data store content. you can export the content from the data store. ReportNet name crn crn crnstartup. Content Manager When you upgrade ReportNet. Contact your SDK administrator for more information about your SDK applications. You must change the alias for the virtual directory manually. After you upgrade. the existing directory names do not change. modify. Framework Manager You can use the same models and projects in Framework Manager for Cognos 8 that you used with the earlier version. install Cognos 8. You cannot use upgraded projects with the earlier version because they are not backward compatible. The following names are affected. default directory names change when you install Cognos 8. If you want to use data store content from an earlier version. you must configure Cognos 8 to use a copy of the content store. 88) Metric Designer. In Cognos 8. Cognos 8 can read deployment archives produced by ReportNet. you cannot use Framework Manager to publish your model without losing backward compatibility. and import the content into the metric store. For more information. To protect your original content store data. ensure that you back it up. If you have SDK applications that rely on an earlier version of the report specifications. Metric Designer You can upgrade projects from earlier versions of Metrics Manager if you want to use them with Cognos 8 (p. and retrieve information. If you install Cognos 8 in the same directory as ReportNet. or save report specifications. you open and save it in the new version of Framework Manager. Content Manager automatically upgrades the schema and contents in the content store. Before upgrading projects. Metrics Manager used a data store database to store. organize. if required. in case you need to revert to the earlier version. ensure that you have backed them up. directory. You cannot use the metric store with the earlier version of Metrics Manager because it is not backward compatible. New File and Directory Names After Upgrade After you upgrade from ReportNet to Cognos 8. see the Framework Manager User Guide. this database is referred to as the metric store. If you install Cognos 8 in a different directory from ReportNet. in case you must revert to the earlier version. You create a copy by backing up the original content store and restoring the data into a new content store. and command names will be different. you cannot use the upgraded content store with ReportNet because it is not backward compatible. some file. Some file name changes occur when you install Cognos 8 and other changes occur after you save the Cognos 8 configuration.xml Cognos 8 name c8 cognos8 cogstartup.xml Description Default installation directory Default Web browser alias or virtual directory Configuration data file used when starting Cognos Configuration 32 .

prefs crconfig_response.log crconfigw.bat cogserver. de.exe crconfig. xml crnlocale.log cogconfigw.x ml crnformat.exe issetup.xml Cognos 8 name cogstartup_yyyymmddhhmm. Installation and Configuration Guide 33 .csv cogconfig_response.xml Description Configuration data file that stores choices made each time the configuration is saved Configuration data file that stores codes for global configuration settings Configuration data file that stores choices made each time global configuration settings are saved Configuration data file that stores formats for numeric data.sh crconfig.exe ReportNetService_languageco CognosService_languagecode. xml coglocale.prefs cogconfig.sh cogconfig.csv xstartup issetup xwsetup issetupcc xwsetup.exe cogconfig. dates.xml xml Upgrade ReportNet to Cognos 8 You can install and upgrade to Cognos 8 in the same directory as ReportNet or in a different directory.bat crconfig. and times Default logging file File to start Cognos Configuration on Windows File to start Cognos Configuration in silent mode on Windows File to start Cognos Configuration on UNIX and Linux Configuration data file that stores user preferences for Cognos Configuration Silent mode log file that stores activities performed while Cognos Configuration runs in silent mode Command to start the installation wizard on XWindows Command to start the installation wizard on UNIX and Linux File to start the installation wizard on Windows Sample file for medium or large configuration crnlocale_yyyymmddhhmm.xml crnserver.xml cogformat.x ml coglocale_yyyymmddhhmm.Chapter 4: Upgrade Considerations for Cognos 8 ReportNet name crnstartup_yyyymmddhhmm.

For information on how to do this. If you want to install Cognos 8 in a new directory. back up your existing content store database. Customized ReportNet Files If you manually edited any configuration files. All other steps are the same as documented in this section. Steps to Install in the Same Directory 1.xml in the appropriate directory.xml files is to be used only when you have made a large number of customizations to these files. You may have modified files other than those in the configuration folder. If you made many customization changes to system. If you are installing on a new computer. Automatic upgrade of system. If so. see "Upgrade from ReportNet to Cognos 8 in an Application Server Environment" (p. see the Administration and Security Guide. Back up the following files to a secure location: • crnlocale. Using your database tools. crn_location/templates/ps 3. Cognos 8 installs and uses Tomcat as its application server by default.1. For more information. Before uninstalling. 2. export the configuration data to the same secure location. the changes will be overwritten during the upgrade. The system. you can keep ReportNet active until you are satisfied with the operation of the new version. you store it in a secure directory. A deployment upgrade is required if you want to change the type of database that you use for the content store. Therefore.xml in the crn_location/configuration directory • server. if required Ensure that you note the directory path. The report administrator will not be able to create deployment definitions in Cognos 8. 34 .xml files are overwritten during the installation of Cognos 8. When you upgrade from ReportNet 1. If you upgrade from ReportNet and you do not want to use Tomcat. the report administrator will no longer have access to the Content Administration tool. The Cognos 8 presentation service supports automatic upgrade of some ReportNet system. For more information about deployment. An alternative method of upgrading is to export the entire content store to a deployment archive in ReportNet and then import the deployment archive into Cognos 8. The directory must be protected from unauthorized or inappropriate access. The system. see the documentation for your database. 35).xml files. you should also back up the additional files before upgrading. only the steps for exporting and restoring the configuration data are different. you must back up the ReportNet versions of these files and then copy them to the directory after installing Cognos 8.Chapter 4: Upgrade Considerations for Cognos 8 If you want to install Cognos 8 in the same directory. You must reapply the changes in the Cognos 8 environment. see "Steps to Install in a New Directory" (p. If you use the deployment upgrade method.1 to Cognos 8.27/conf directory • system. In Cognos Configuration. For example. you must first uninstall ReportNet.xml files for which automatic upgrade is supported are in the following directories: • crn_location/templates/ps • crn_location/templates/ps/portal • crn_location/templates/ps/qs Note: The recommended method to upgrade customized files is to manually reapply changes after the new software is installed. you must follow a different set of steps to upgrade.xml in the crn_location/tomcat4. The automatic upgrade will be applied when you start the Cognos 8 service. You should also back up these files so that the original version can be restored if necessary. When you back up the configuration data. You should keep a record of any customizations to ensure that they can be reapplied after upgrading.xml files in ReportNet. you can use this automatic upgrade feature instead of reapplying the changes manually after upgrading. ensure that all Framework Manager projects are not checked into a source control system. 155).

Old SAP iViews will not work with the new Portal Services producer component. Important: Because the exported crnstartup.xml to crn_location/tomcat4.xml. Back up the following files to a secure location: Installation and Configuration Guide 35 . or save report specifications. Start Cognos 8. In addition. 7. For files that you manually edited in ReportNet. • Copy server. For information. Stop all Cognos services. review the configuration. 12. In Cognos Configuration. If you use SAP Enterprise Portal. and then save it. 5. Install (p. modify. Report Studio users must clear their Web browser cache to get the latest images. System.xml files from the secure backup location as follows: • Copy crnstartup. 14. For example. Back up any manually edited files in the crn_location/configuration and other directories to a secure location. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. 49) and configure (p. Steps to Install in a New Directory 1. if required. see the Framework Manager User Guide. IMPORTANT: Do not upgrade your report specifications if you have SDK applications that create. to a Cognos 8 compatible version. Any projects that are checked in when you uninstall will not be upgraded. your SDK applications may not be able to access the upgraded report specifications. Uninstall ReportNet from every ReportNet computer.xml and crnlocale. see the documentation for your database.Chapter 4: Upgrade Considerations for Cognos 8 To make the data usable for upgrading. The default setting is to not upgrade report specifications. you may need to reconfigure the following properties: • Title • Open action links going outside a portal For more information.xml to crn_location/configuration. Copy the . Do not copy the customized files to the crn_location directories. For instructions. If you use a source control system such as CVS. 15. The earlier versions of these files may not be compatible with Cognos 8.1. 11. When you save the configuration. For information on how to do this. 86) as required. Otherwise.xml files are upgraded.xml to the appropriate directory. see the Cognos 8 SDK Developer Guide. Using your database tools. For instructions. 10. if required. ensure that all Framework Manager projects you want upgraded are checked out before uninstalling ReportNet. edit the same files in the crn_location directory and reapply the changes that you made to the original customized files. 13. Upgrade your Framework Manager projects and reports (p.27/conf. Install Cognos 8 in the same directory that you used for ReportNet on every computer (p. see the documentation for the older version of ReportNet. click Yes. see the SAP EP Cognos iView documentation. name the file crnstartup. an upgrade dialog appears and asks if you want to upgrade your report specifications. 9. 8. 84) Framework Manager. 4. do not save your reports until the SDK applications have been updated. ensure that the location is secure. 16. • Copy system. 6. see the Administration and Security Guide. upgrade your master iView. 43). 2. If you use pages created in ReportNet. Cognos 8 automatically upgrades the content store.xml file contains unencrypted passwords. copy your existing content store database into a new content store database. For information about upgrading report specifications. crn_location/templates/ps If you are prompted to overwrite existing files.

System. or save report specifications. Ensure that security authentication settings are not changed. Important: Because the exported crnstartup. click Yes. Cognos 8 automatically upgrades the new content store. For example. The default setting is to not upgrade report specifications. 7. For files that you manually edited in ReportNet. crn_location/templates/ps • In Cognos Configuration. 4. For information about upgrading report specifications. Copy the .xml to c8_location/configuration.xml file contains unencrypted passwords.27/conf. the portal shows the dispatchers that are registered for both versions.1. You must first update your SDK applications to comply with the Cognos 8 report specifications schema. an upgrade dialog appears and asks if you want to upgrade your report specifications. if required. 8. 49) and configure (p. When you open the Administration portal in Cognos 8. For more information. Do not copy the customized files to the c8_location directories. For example.xml and crnlocale. ensure that the location is secure. 10. you may need to reconfigure the following properties: • Title • • • 3. • Back up any manually edited files in the crn_location/configuration and other directories to a secure location. If you use pages created in ReportNet. Otherwise. export the configuration data to the same secure location. For instructions. users. 41). Open the Administration portal in Cognos 8. to a Cognos 8 compatible version. • Copy system. In addition.xml in the appropriate directory. configure Cognos 8 to point to the new content store. Upgrade your Framework Manager projects and reports (p. Install (p. Start Cognos 8. edit the same files in the c8_location directory and reapply the changes that you made to the original customized files. IMPORTANT: Do not upgrade your report specifications if you have SDK applications that create. Ensure that the port numbers and service name for Cognos 8 are different from those used for ReportNet so that there are no conflicts. 11. Configure new Web server aliases (p.xml in the crn_location/configuration directory server. • Copy server. 61). In Cognos Configuration.27/conf directory system. if required. do not save your reports until the SDK applications have been updated. and unregister the dispatchers that are used with ReportNet.xml to the same directory in the new location as it was in the ReportNet location. The earlier versions of these files may not be compatible with Cognos 8. Install Cognos 8 in a new directory (p. To make the data usable for upgrading. c8_location/templates/ps If you are prompted to overwrite existing files. roles. 86) as required. 84) Framework Manager. the namespaces must be the same for policies. and then save the configuration (p. For example. Report Studio users must clear their Web browser cache to get the latest images. see the Administration and Security Guide. 9. 43). your SDK applications may not be able to access the upgraded report specifications. 6. if required Ensure that you note the directory path.xml to c8_location/tomcat4. modify. use a different cookie path.1. When you save the configuration. 5.xml in the crn_location/tomcat4.xml. name the file crnstartup. 36 . see the Framework Manager User Guide. see the Cognos 8 SDK Developer Guide. 12. and groups to work correctly.xml files from the secure backup location to the following directory: • Copy crnstartup.xml files are upgraded.Chapter 4: Upgrade Considerations for Cognos 8 crnlocale. configure new ports and URLs.

Modify other settings as required. If you installed Cognos 8 in a new directory. you must ensure that the option to upgrade the report specifications is set correctly. For more information.sh -s • On Windows. If you use SAP Enterprise Portal. see the documentation for the older version of ReportNet. you must also change the settings for ports and the Web server alias./cogconfig. • Uninstall ReportNet from all ReportNet computers. For more information. type cogconfig.Chapter 4: Upgrade Considerations for Cognos 8 • Open action links going outside a portal For more information. see the Administration and Security Guide. it is important to protect the installation directory from unauthorized or inappropriate access. Japanese. If you want to upgrade the configuration in silent mode. stop at step 11. or Korean characters. change the value to true. 41) for the settings to modify. upgrade your master iView. do the following: • Stop ReportNet. When you are ready to uninstall ReportNet. and scorecarding features. do not start Cognos Configuration. If you use a DB2 database for the content store. type . 13. stop at step 7. 14. see the SAP EP Cognos iView documentation. • Edit the crnstartup. perform the following steps and then return to the steps in the preceding section. If you use Chinese. When you complete the upgrade tasks. For instructions. see the Architecture and Planning Guide. follow the steps in the preceding section and stop at the step to configure Cognos 8: • In the steps to install in the same directory. When you reach that step. Type the configuration command: • On UNIX or Linux. Upgrading Using the Silent Configuration Option You can run a silent configuration to upgrade the configuration from ReportNet to Cognos 8. you can tune the database to take advantage of DB2 features. leave the value as false. If you installed Cognos 8 in a new directory. Instead. To ensure the security and integrity of Cognos 8.bat -s Installation and Configuration Guide 37 . see "Run ReportNet and Cognos 8 at the Same Time" (p.xml file in crn_location/configuration or c8_location/configuration and look for the following lines: <crn:parameter name="doReportSpecUpgrade"> <crn:value xsi:type="xsd:boolean">false</crn:value> </crn:parameter> • • • Set the value for the report specification upgrade: • To skip the upgrade of the report specifications. • To upgrade the report specifications. • In the steps to install in a new directory. you may notice differences in some characters after upgrading to Cognos 8. Old SAP iViews will not work with the new Portal Services producer component. For information. see the Troubleshooting Guide. Cognos 8 is fully configured except for new properties and features. Before you run the silent configuration.

59). see "Upgrade Metrics Manager and Security Information" (p. see the Metric Studio User Guide for Authors. 5. protect the installation directory from unauthorized or inappropriate access. see the documentation provided with your earlier version of Metrics Manager. For each metric store. the user will have read access to the scorecard. an upgrade utility is available. If you want to upgrade the security information for the earlier version of Metrics Manager. For more information. review the information about Cognos 8 security to determine if it meets your requirements. If you exported content from data stores in step 1. 86) Metric Designer on Windows. After the upgrade utility is run. install Cognos 8 in a different directory from the earlier version of Metrics Manager (p. create one metric store database (p. upgrade ReportNet first. see "Upgrade from Metrics Manager to Cognos 8 in an Application Server Environment" (p. see the Administration and Security Guide. Steps 1. 2. Install (p. If the Cognos 8 security model does not meet your requirements and you must upgrade your existing security information. 8. assume a user belongs to two user classes. 7. If both ReportNet and Metrics Manager are on the same computer and you plan to upgrade to Cognos 8. import the contents of each data store into a different metric store. Install Cognos 8: • If you are upgrading only Metrics Manager. Set up the environment (p. To ensure the security and integrity of Cognos 8.Chapter 4: Upgrade Considerations for Cognos 8 Upgrade Metrics Manager to Cognos 8 You must install and upgrade to Cognos 8 in a different directory from the earlier version of Metrics Manager. 88). Export the contents of any data store that you want to use with Cognos 8 from the earlier version of Metrics Manager. The upgrade utility does not map the Deny permission if it was used in the earlier version of Metrics Manager. follow the steps to upgrade ReportNet to Cognos 8 (p. Cognos 8 and earlier versions of Metrics Manager use different security models. If you upgrade from Metrics Manager and you do not want to use Tomcat. You can keep Metrics Manager active until you are satisfied with the operation of Cognos 8. For information about importing data. 82). When you are ready. Cognos 8 installs and uses Tomcat as its application server by default. stop the earlier version of Metrics Manager and uninstall it as described in the documentation provided with it. Upgrade Metrics Manager and Security Information Cognos 8 and earlier versions of Metrics Manager use different security models. Before upgrading to Cognos 8. 4. If you exported the contents of one or more data stores in step 1. Upgrade Metric Designer projects and extracts as required (p. 155). 33). For the same scorecard. 38). 53). you must follow a different procedure to upgrade. you must follow a different set of steps to upgrade. For more information. 58) and environment variables on UNIX (p. 38 . For information. • If ReportNet is on the same computer as Metrics Manager. set up the database client (p. You use this utility during the upgrade process to map the security permissions for scorecards and metrics in the earlier version to corresponding permissions in Cognos 8. For more information. For example. Create a metric package (p. 53) for the contents of each data store. 6. 3. one user class has Read permission and the other user class has Deny permission. 43). 50) and configure (p. and then Metrics Manager.

If you plan to upgrade the content of more than one data store. By default. read_mapping A comma delimited list of Cognos 8 permissions to grant for the read permission level set in the earlier version of Metrics Manager. This property is optional. The list of files must contain all of the policy links that you want to import into the Cognos 8 metric store.2. The default output file name is policies. the default character set of the platform is used. flat_file_version The version of the flat file from the earlier version of Metrics Manager. The list must include all of the scorecards that you want to import into the Cognos 8 metric store. The following table describes the properties that must be defined in the control file. This property is optional.cms. other objects in these files are ignored.metric or . This file is a text file. write_mapping A comma delimited list of Cognos 8 permissions to grant for the write permission level set in the earlier version of Metrics Manager One of the following suffixes may be added to specify the permissions for a specific object type: . By default. policy_file input_file_encoding Installation and Configuration Guide 39 . Only scorecards are imported. Only policy links are imported. Property scorecard_file Description A comma delimited list of object_stage (.cml) files from the earlier version of Metrics Manager that contain the policies to be upgraded. A comma delimited list of source object_link_stage (. One of the following suffixes may be added to specify the permissions for a specific object type: . the default character set of the platform is used.scorecard. you must create a control file for each data store and run the upgrade utility for each control file.0 or 2. output_file The name of the file where the generated Cognos 8 policies will be written. other objects in these files are ignored. This property is optional.2. The value may be 2.scorecard. The default value is 2. output_file_encoding The desired character set of the output file. The character set of the input files.cmo) files that contain the scorecards from the earlier version of Metrics Manager. This property is optional.Chapter 4: Upgrade Considerations for Cognos 8 The upgrade utility maps security information for one data store using the information in a control file that you create.metric or .

Chapter 4: Upgrade Considerations for Cognos 8 Property administrator_mapping Description A comma delimited list of Cognos 8 permissions to grant for the administer permission level set in the earlier version of Metrics Manager. 2.readannotations. see the Metric Studio User Guide for Authors. Create a metric package (p.writeProject administrator_mapping=read. The permissions include: • Read • Write • Setpolicy • Readannotations • Annotate • Writeproject • Writeactual • Writetarget • Writetolerance • Writeudc One of the following suffixes may be added to specify the permissions for a specific object type: .readannotations write_mapping=read. 9. install Cognos 8 in a different directory from the earlier version of Metrics Manager (p.write. 8.cms by default. 4. 53) and set up the metric store database client (p. Upgrade Metric Designer projects and extracts as required (p.annotate. Example The following shows an example control file: scorecard_file=c:\\cmm_exports\\export_scorecards. 58) and environment variables on UNIX (p. Export the contents of the data store from the earlier version of Metrics Manager. 6.1 (Tools. For more information. see the Metric Studio User Guide for Authors. Import sources). 86) Metric Designer on Windows.annotate. Install (p. 3.writetarget. • If ReportNet is on the same computer as Metrics Manager. 40 .writeProject. 43). 59). Import the contents of the output file generated by the upgrade utility. Import the contents of the data store into the metric store. follow the steps to upgrade ReportNet to Cognos 8 (p.2 output_file=new_policies. For more information.writeudc Steps 1. This file is named policies. 33). Type the following command from a command prompt: cmm_migrate_policies control_filename 5.cmo policy_file=c:\\cmm_exports\\export_permissions. writeactual. 50) and configure (p. 53). Ensure that you create a metric store database (p.readannotations. set the import file format to 8. Set up the environment (p. see the documentation provided with your earlier version of Metrics Manager. 82). For more information. 88).writetolerance.cml flat_file_version=2. 10. Install Cognos 8: • If you are upgrading only Metrics Manager.cms read_mapping=read.metric or . In Metric Studio.scorecard. 7.

• In the Application Protection box. click the value for Gateway URI and ensure that the URI contains the correct Web server alias for Cognos 8 For example. click Environment. 9. change the port number for the following URIs to match the new port number that you entered for Internal dispatcher URI. In the Properties window. 10. Other configuration changes may be required depending on your environment. Steps 1. protect the installation directory from unauthorized or inappropriate access. 4. clicking the Virtual Directory tab instead of the Home Directory tab. To ensure the security and integrity of Cognos 8. click Data Access. Content Store. specify the name of the new content store. • In the Properties window. • Under Dispatcher Settings. Save the configuration and start Cognos 8. right-click the default Web site and then click Properties. In the Explorer window.Chapter 4: Upgrade Considerations for Cognos 8 11. replace crn with cognos8. configure Cognos 8 to use the new content store: • For Database name. • Repeat the above three bulleted steps for each of the virtual directories for Cognos 8. Change the cookie path: • From the Actions menu. 6. click Cookie Settings.0 Web server. If you use Portal Services. Under Gateway Settings. 7. Run ReportNet and Cognos 8 at the Same Time You must change the ports and the Web server alias if you want to run Cognos 8 and the earlier version of ReportNet on the same computer and at the same time. Content Manager. under Dispatcher Settings. Installation and Configuration Guide 41 . Start Cognos Configuration. If you use an ISAPI gateway on an IIS 6.xml file: • in the Explorer window. In the Properties window. change the port for External dispatcher URI. If you use an ISAPI gateway on an IIS 6. stop the earlier version of Metrics Manager and uninstall it as described in the documentation provided with it. • Under Other URI Settings. • For User ID and password. you must isolate the Cognos 8 gateway to prevent a conflict with the ReportNet gateway. 5. click Environment. click Edit Global Configuration. If you are using Portal Services.xml matches the port for the other URI properties. click the value for Internal dispatcher URI. • Click the Home Directory tab. 3. change the application protection setting: • In IIS Manager. You isolate the gateway by setting the application protection for the Web site and virtual directories to High. If required. click the edit button and specify the userid and password to access the new content store. When you are ready.xml file. 8. • Click OK. 2. ensure that the port number for Location of Applications. you must specify the location of the applications. update the applications. 12. Portal Services. Select the port number and then type the new port number. click High and then click OK. 11. In the Explorer window. • Change to a different path from the one that is used by ReportNet. change the port for Dispatcher URI for external applications and Content Manager URIs. • In the Global Configuration window. Content Manager URIs does not appear on a gateway computer.0 Web server.

42 . Note: When you change from the default ports on Windows. it will run in a separate memory space. You can now run ReportNet and Cognos 8 at the same time.Chapter 4: Upgrade Considerations for Cognos 8 The next time the Cognos 8 gateway is requested. You can view the service name and port number under Services in your Windows administrative tools. the port number is automatically appended to the service name. The service name in Cognos Configuration does not show the port number.

The hardware requirements depend on your Cognos environment. The installation wizard for your Cognos 8 product is provided on the installation CDs. If you are upgrading from a previous release of Cognos products. It does not affect the file permissions within the directories. run-time generated files. To run graphical-mode installation. you must use the upgrading steps. On UNIX. However. If your Cognos 8 product uses more than one CD. you can install server components using either a character-based interface or a graphical user interface. 49). such as logs.Chapter 5: Installing Cognos 8 If you plan to install two or more Cognos 8 components on the same computer. For instructions about installing Metric Designer. This affects only the installation directories. For information about upgrading from ReportNet or Metrics Manager. ensure that your computer meets the software and hardware requirements for those components. you must set up your environment. For Cognos 8 products that use a single CD. files from the CD are temporarily copied to this directory. 145). see "Changing Application Servers" (p. run the installation wizard from the product CD. respect the mask. 50). the console attached to your UNIX computer must support a Java-based graphical user interface. ensure that the system clocks on the Content Manager computers are synchronized. For instructions about installing Framework Manager. We recommend umask 022 on the installation directory. Application Tier Components. You can install the gateway. Installation and Configuration Guide 43 . copy the contents of the CDs to a secure location on your computer and then run the installation wizard from that location. System Requirements Before you install Cognos 8. During installation. see "Install Metric Designer" (p. you must be aware of the installation requirements. we strongly recommend that you install them in the same installation location to avoid conflicts among ports and other default settings. For more information. On UNIX. ensure that you have administrator privileges for the Windows computer you are installing on. Also ensure that your computer has a TEMP system variable that points to the directory where you want to store temporary files. Only the components that you choose to install are copied from the CD to your computer. and Content Manager components on multiple computers. such as disk space. Cognos 8 respects the file mode creation mask (umask) of the account running the installation program. Important: For successful failover between Content Managers. see "Upgrade Considerations for Cognos 8" (p. see "Install Framework Manager" (p. On Windows. Install Server Components Use the installation wizard to select the components you want to install and the location on your computer where you want to install them. 31). After you install Cognos 8. If you are installing Cognos 8 in an application server environment. You may require additional resources.

If you are using an application server.) RAM Operating system specifications Disk space Minimum: 1 GB File descriptor limit set to 1024 on Solaris (recommended) Minimum: 1 GB of free space on the drive that contains the temporary directory used by Cognos components. Ensure that you have sufficient disk space for future requirements. the size of the metric store will increase over time. Database One of the following databases available to store Cognos data: • Oracle • DB2 • Microsoft SQL Server TCP/IP connectivity to Microsoft SQL Server • Sybase For Metric Studio. use the JRE that is installed with it.Chapter 5: Installing Cognos 8 The following table lists the minimum hardware and software requirements to run Cognos 8. For Metric Studio. the following databases are supported for the metric store: • Oracle • DB2 • Microsoft SQL Server TCP/IP connectivity to Microsoft SQL Server Web browser For all Web browsers. Web server JRE A Web server installed and started Java Runtime Environment (JRE) JRE is installed automatically with Cognos 8 on Windows. the following enabled: • cookies • JavaScript For Microsoft Internet Explorer only. Requirement Operating system Specification Windows UNIX: • Sun Solaris • HP-UX • IBM AIX Red Hat Enterprise Linux on Intel-compatible x86 (Some Cognos 8 components are not supported under Linux. the following enabled: • Run ActiveX controls and plug-ins • Script ActiveX controls marked safe for scripting • Active scripting • Allow META REFRESH 44 .

cognos.Chapter 5: Installing Cognos 8 Requirement Other Specification For a terminal emulator to install Cognos 8 on UNIX. The database client software for the metric store must be installed and configured on each computer where you install Application Tier Components. the report server supports the Data Direct ODBC driver. Database Connectivity for the Metric Store Database For Metric Studio. classes12. patches. browsers. It is important to apply all required operating system patches and to use only the versions of third-party software that are supported for a Cognos product. the JDBC driver is included with Metric Studio and no other software is required. For Oracle databases. On UNIX and Linux. Metric Studio uses the JDBC OCI driver. Database Connectivity for the Reporting Database For Cognos 8.jar. Cognos 8 requires TCP/IP connectivity with the Microsoft SQL Server. for Microsoft SQL Server only. allowing you to run Framework Manager action logs. It is important to note that the Linux operating system is available in a number of distributions and supports a number of hardware platforms. On Windows. Web servers. Microsoft Data Access Component (MDAC) for use with product samples If you want to email reports. the JDBC driver is included with Cognos components and no other software is required.jar.20 • BW Add-on Supported Environments You can view an up-to-date list of environments supported by Cognos products. the report server supports the native database connectivity. database servers. On UNIX. Content Manager uses the JDBC thin driver. Installation and Configuration Guide 45 . For Microsoft SQL Server. and application servers on the Cognos support site (http://support. Content Manager uses the JDBC driver. Framework Manager is not installed. Otherwise. This driver is available from Data Direct. directory servers. For Microsoft SQL Server. For Oracle databases. Metric Studio connects to the metric store using JDBC on both Windows and UNIX. For DB2 databases. Cognos 8 requires TCP/IP connectivity with the Microsoft SQL Server. Database Connectivity for the Content Store Database The database client software for the database that is used as the content store must be installed and configured on each computer where you install Content Manager. the report server supports either native database connectivity or ODBC. Cognos components require TCP/IP connectivity with the database server. the BMTScriptPlayer will not work. the emulation set to VT220 equivalent or better to ensure that the hot keys in the Installation wizard work On Windows.com). Ensure that the operating system and hardware combination you are using is a supported combination. Metric Studio uses the JDBC driver that requires DB2 client installation. the Application Tier Components must be able to access the metric store. When you install Cognos 8 on Linux. your product may not work properly. such as operating systems. For DB2 databases. Ensure that you install the database API software for your reporting sources on each Cognos 8 server computer. Content Manager uses the JDBC driver that requires DB2 client installation. jconn2. The BMTScriptPlayer is a command-line utility that interfaces with the Framework Manager engine. the ability to use a mail server SAP BW The following SAP Front-End components installed on each Cognos 8 server computer: • SAP GUI 6. the only service that accesses the query database (also known as reporting database) is the reporting engine that runs reports. Because Framework Manager is not installed. For Sybase.

Mount the CD for your Cognos server product using Rock Ridge file extensions. An example of the installation location of a Java Runtime Environment is /directory/java/java_version/jre. go to the location on your computer where you copied the contents from the CDs. On UNIX. Follow the directions in the installation wizard and copy the required files to your computer./issetupcc 8. stop the Cognos 8 service. Some UNIX and Linux Web servers do not support non-ASCII characters in directory names. 5. if you do not have a CD-ROM. • When the installation is complete. 6. • If your Cognos 8 product uses more than one CD. type pfs_mount -t rrip <device><mount_dir> -o xlat=unix For example. Important: To mount the Cognos CD on HP-UX. Start the installation wizard: • If you use XWindows. type . Install Cognos 8 components in a directory that contains only ASCII characters in the path name. go to the directory on the CD that is appropriate for your operating system. Set the JAVA_HOME environment variable to point to the installation location of your Java Runtime Environment (JRE). mount the CD on a Windows drive and FTP the single tarball file to an installation location on the UNIX computer. type bg pfs_mountd and then type bg pfsd • To mount the drive. type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons to unmount the CD. do the following: • Add the pfs_mount directory in your path. On HP-UX./issetup • If you do not use XWindows. 3. PATH=/usr/sbin/:$PATH export PATH • To start the required NFS daemons and run the daemons in the background. Go to the installation location: • If your Cognos 8 product uses one CD. you must install Cognos 8 into a different directory. type pfs_umount /cdrom and kill the pfsd and pfs_mountd daemons. 7. 4. type . copy the contents of the directory that is appropriate for your operating system on each CD to a single secure location on your computer. If you are installing to a directory with other Cognos 8 components. pfs_mount /dev/dsk/c0t2d0 /cdrom -o xlat=unix You can now install or copy files as a non-root user using a Cognos CD from this drive. 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. If your Cognos 8 product uses more than one CD.Chapter 5: Installing Cognos 8 Steps for UNIX and Linux 1. 2. Cognos 8 requires Sun Java to run on Linux. For example. If you are installing Cognos 8 on a computer that already has ReportNet and you want to keep the ReportNet. Tip: To unmount a CD on HP-UX. 46 .

NoClassDefFoundError: javax/net/ServerSocketFactory: Steps for Windows 1. If you are installing to a directory with other Cognos 8 components. You must also update your Java security framework (p.lang. select View the Readme and then select Finish. click Yes. 58). LD_LIBRARY_PATH • For AIX. On Linux. double-click the issetup. To ensure the security and integrity of Cognos 8. 2. Choose how to proceed in the Finish page of the installation wizard: • We recommend that you do not configure Cognos 8 immediately because you must do other tasks first to ensure that your environment is properly set up. click Finish. • If the console attached to your computer does not support a Java-based graphical user interface or if you want to configure Cognos 8 later. If you use Oracle. you must install Cognos 8 into a different directory. 5. in the win32 directory on the CD. stop the Cognos 8 service. LIBPATH • For HP-UX. DB2. If your Cognos 8 product uses more than one CD. 9. The Welcome page of the installation wizard should appear. • If the Welcome page for the installation wizard appears. 4. Installation and Configuration Guide 47 . 60) before you can configure Cognos 8. 3. close the readme text file by pressing Crtl + C or q.Chapter 5: Installing Cognos 8 If you are installing it in a directory that already has other Cognos 8 components. Select the language to use for the installation. if the console attached to your computer supports a Java-based graphical user interface. Follow the directions in the installation wizard to copy the required files to your computer. secure location on your computer. Otherwise. • For Solaris and Linux.xml in c8_location/configuration directory. you can click Start Cognos Configuration. • In the secure location. If you receive a message that the folder already contains a folder named zipfiles and do you want to overwrite it.exe file. SHLIB_PATH 11. set the PRINTER environment variable to the name of your printer. do the following: • Insert each CD for your Cognos server products. you are prompted for the location of a directory in which to store backup copies of the files that will be overwritten. it is important to protect the installation directory from unauthorized or inappropriate access. • Copy the contents of each CD to a single. click Cancel and then click Yes when prompted to exit the wizard. Tip: For character-mode installations on UNIX and Linux. 10. [ ERROR ] java. The Welcome page of the installation wizard should appear. you may receive the following error: [Cryptography] 1. If no Welcome page appears. double-click the issetup. or editing cogstartup. • If you want to see late-breaking information about Cognos 8. or Sybase you can now set up the database client for the content store and the metric store (p. You can later configure Cognos 8 using Cognos Configuration by starting cogconfig. insert the CD for your Cognos server product and then open the installation menu. If your Cognos 8 product is on a single CD. Append the c8_location/bin directory to the appropriate library path environment variable.exe file.sh in the c8_location/bin directory. and you want to keep ReportNet running. However. If you are installing Cognos 8 on a computer that already has ReportNet.

click Start Cognos Configuration.Chapter 5: Installing Cognos 8 If you are installing in a directory that already has other Cognos 8 components. • If you want to see late-breaking information about Cognos components. Use the Windows Start menu to start Cognos Configuration from the shortcut folder. Default Settings for Cognos 8 The following table lists the default ports and URI settings for Cognos 8. You can directly update the shutdown port using Cognos Configuration. Click Finish. 90). 93). In the Finish page of the installation wizard: • If you want to configure Cognos components immediately. After installation. You can also change them by editing the cogstartup.1 Connector SSL Coyote HTTP/1.cgi The URI to the gateway http://localhost:9300/p2pd The URI to the dispatcher /servlet/dispatch http://localhost:9300/p2pd The URI to the dispatcher /servlet/dispatch http://localhost:9300/p2pd The URI to the primary /servlet/dispatch/ext dispatcher used by the gateway 9362 The port used by the local log server The following table lists the default settings used by Cognos 8 for Tomcat. 90) or to enable the SSL protocol (p. The non-SSL and SSL connectors are automatically updated in the server. you are prompted for the location of a directory in which to store backup copies of the files that will be overwritten. Setting Non-SSL Coyote HTTP/1. External) Dispatcher URI for external applications Dispatcher URIs for Gateway Log server port Default Description http://localhost:9300/p2pd The URI to Content Manager /servlet http://localhost:80/cognos 8/cgi-bin/cognos.1 connector Shutdown port Port 9300 Description The port Tomcat uses to pass requests from the Web server to Cognos 8 The port Tomcat uses to listen for secure connections The port Tomcat uses to listen for a shutdown command 9334 9399 48 . Setting Content Manager URI Gateway URI Dispatcher URI (Internal.xml file when you use Cognos Configuration to change the dispatcher port (p. 7. you can use the configuration tool to change the settings (p. 6.xml file in the c8_location/configuration directory. click View the Readme.

If you use an Oracle database as a data source for your reports. on the same computer as other Cognos 8 components. You may require additional resources. you are prompted to do so during the installation. If you are installing the modeling tool in the same directory as Cognos 8 and do not stop the Cognos 8 services. numeric. ask your system administrator to add you to the Administrator group on your computer. However. Default settings chosen by Cognos are used for the configuration. ensure that the Windows computer meets Cognos 8 software and hardware requirements. Installation and Configuration Guide 49 . 178). If you are upgrading Framework Manager from an older version. and calendar conventions automatically adapt to the native language and locale. Requirement Operating system RAM Specification Windows Minimum: 512 MB Recommended: 1 GB Disk space Database Minimum: 500 MB of free space on the drive that contains the temporary directory used by Cognos 8 Database client software installed on the same computer as Framework Manager (Oracle. we recommend that you close all programs that are currently running to ensure that the installation program copies all the required files to your computer. depending on the size of your models. or Sybase only) Database connectivity set up Other Microsoft Data Access Component (MDAC) 2. If you are installing in a directory with other Cognos 8 components. All required files are copied to one computer. or if you installed Cognos 8 on a different computer. or on a different computer. System Requirements for Framework Manager Before you install Framework Manager. DB2. Also. such as disk space.character_set For example. NLS_LANG = JAPANESE_JAPAN. monetary. stop the Cognos 8 service. Insert the CD for your Cognos modeling product and then open the installation menu. 3. Before you install the modeling tool. ensure that you have administrator privileges for the Windows computer you are installing on.Chapter 5: Installing Cognos 8 Install Framework Manager You can install Framework Manager.UTF8 The value of the variable determines the locale-dependent behavior of Cognos 8. time. you must first uninstall the older version of Framework Manager (p. you may want to change these default settings if existing conditions make the default choices inappropriate. sort order. date. If you are not an administrator. The size of the models you create affects the hardware requirements.6 or later for use with product samples Steps 1. The following table lists the minimum hardware and software requirements to run Framework Manager. We recommend that you install and configure all Cognos 8 server components before you install the modeling tool. set the NLS_LANG environment variable by typing the following command on each computer where Framework Manager and the Application Tier Components server are installed: NLS_LANG = language_territory. Error messages. the metadata modeling tool for Cognos 8 for reporting. 2.

xml file in the c8_location/configuration directory.cgi Description The URI to the Cognos 8 gateway http://localhost:9300/p2pd The URI to the dispatcher /servlet/dispatch 9362 The port used by the local log server Install Metric Designer You can install Metric Designer. You can also change them by editing the cogstartup. click Start Cognos Configuration. click View the Readme. 6. However. Default settings chosen by Cognos are used for the configuration. Use the Windows Start menu to start Cognos Configuration from the shortcut folder. To ensure the security and integrity of Cognos 8. or if you installed Cognos 8 on a different computer. If no Welcome page appears. If you use Oracle. and you want to keep ReportNet running. or on a different computer. 7. 5. 4. you may want to change these default settings if existing conditions make the default choices inappropriate. If you are installing in a directory that already has other Cognos 8 components. All required files are copied to one computer. double-click the issetup. In the Finish page of the installation wizard: • If you want to configure Cognos components immediately. you must install Cognos 8 into a different directory. we recommend that you close all programs that are currently running to ensure that the installation program copies all the required files to your computer. Follow the directions in the installation wizard to copy the required files to your computer. the metadata modeling tool for Metric Studio. some configuration tasks may be required to ensure that it works in your reporting environment (p. or Sybase as the database server for the content store in a distributed installation. If you are installing Cognos 8 on a computer that already has ReportNet. If you are not an administrator. DB2.exe file. Component Gateway Dispatcher URI for external applications Log Server Port Default http://localhost:80/cognos 8/cgi-bin/cognos. ask your system administrator to add you to the Administrator group on your computer. it is important to protect the installation directory from unauthorized or inappropriate access. After installation. you must now install the database client software (p. After you install Framework Manager on your Windows computer. Also. Default Settings for Framework Manager The following table lists the default settings for the Cognos 8 ports and URIs that are used by Framework Manager. Select the language to use for the installation. 58) on the same computer where you installed Framework Manager. 84). you can use the configuration tool to change the settings. you are prompted for the location of a directory in which to store backup copies of the files that will be overwritten. on the same computer as Cognos 8 components. • If you want to see late-breaking information about Cognos components.Chapter 5: Installing Cognos 8 The Welcome page of the installation wizard should appear. Click Finish. 50 . ensure that you have administrator privileges for the Windows computer you are installing on. in the win32 directory on the CD. Before you install the modeling tool.

it is important to protect the installation directory from unauthorized or inappropriate access. such as disk space. If no Welcome page appears. To ensure the security and integrity of Cognos 8. The Welcome page of the installation wizard should appear. 58) on the same computer where you installed Metric Designer.exe file. depending on the size of your models. ensure that the Windows computer meets Cognos 8’s software and hardware requirements. 7. • If you want to see late-breaking information about Cognos components. you must now install the database client software (p. You should also install and configure the target application where you will load data or metadata. 3. stop the Cognos 8 service. 6. The size of the models you create affects the hardware requirements. Click Finish.Chapter 5: Installing Cognos 8 We recommend that you install and configure all Cognos 8 server components before you install the modeling tool. If you are installing the modeling tool in the same directory as Cognos 8 and do not stop the Cognos 8 services. click Start Cognos Configuration. System Requirements for Metric Designer Before you install Metric Designer. In the Finish page of the installation wizard: • If you want to configure Cognos components immediately. If you are installing in a directory with other Cognos 8 components. Use the Windows Start menu to start Cognos Configuration from the shortcut folder. If you use Oracle or DB2 as the database server for the metric store in a distributed installation. double-click the issetup. 2. you are prompted to do so during the installation. 5. Select the language to use to run the installation wizard.6 or later for use with product samples Steps 1. click View the Readme. in the win32 directory on the CD. You may require additional resources. Follow the directions in the installation wizard to copy the required files to your computer. The following table lists the minimum hardware and software requirements to run Metric Designer. Installation and Configuration Guide 51 . Insert the CD for your Cognos modeling product and then open the installation menu. 4. Requirement Operating system Specification Windows (design interface and engine) UNIX (engine only): • Sun Solaris • HP-UX • IBM AIX Red Hat Enterprise Linux on Intel-compatible x86 (engine only) RAM Minimum: 512 MB Recommended: 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.

After installation.Chapter 5: Installing Cognos 8 After you install Metric Designer on your Windows computer. Component Gateway Dispatcher URI for external applications Default Description http://localhost:80/cognos8/c The URI to the gateway gi-bin/cognos. You can also change them by editing the cogstartup. you can use Cognos Configuration to change the settings. Default Settings for Metric Designer The following table lists the default settings for the ports and URIs that are used by Metric Designer.cgi http://localhost:9300/p2pd/se The URI to the dispatcher rvlet/dispatch 52 .xml file in the c8_location/configuration directory. some configuration tasks may be required to ensure that it works in your scorecarding environment (p. 86).

which is required by Cognos 8 to access data. By default. You must create a metric store database using Oracle. An Oracle or Microsoft SQL Server database can use UTF-8 or UTF-16 encoding. you must create the data sources for Framework Manager. and present character data. 67) to work in your environment. you must create at least one database to be used as a metric store. you must use DB2 or Oracle for the database that is used for the content store. You must ensure that a Web browser and a Web server are set up to provide access to Cognos components. such as user preferences. global settings (such as the language and currency formats shown in the user interface). A metric store also contains scorecarding application settings. For Metric Studio. or greater than the letter 'b'. Configure the Web browser. For example. if required. if using Metric Studio. connections to data sources. Create Databases for the Content Store and Metric Store The content store is a database that Content Manager uses to store global configuration data. and whether the collation is accent-sensitive. A DB2 or Sybase database must use UTF-8 encoding. if required. if required. ❑ Set up the database client for the content store (Oracle. equal to. DB2 and Sybase) and. ❑ ❑ ❑ ❑ ❑ ❑ ❑ ❑ Update the Java environment. For Cognos 8 for reporting. Design models and log files are not stored in the content store. Set up the data source environment for Framework Manager. Installation and Configuration Guide 53 . compare. a metric store. DB2.Chapter 6: Setting Up the Environment After you install Cognos 8. or Sybase Adaptive Server Enterprise (ASE). if required. Set up the database client for Metric Designer. It is important to note that Cognos 8 uses a single sort order that specifies the rules used by the database to interpret. and product-specific content. Cognos 8 products share the content store database. Configure the router to test whether a dispatcher is available. For Cognos 8. Microsoft SQL Server. Set up the database client for Framework Manager. ❑ Set up environment variables on UNIX for the metric store. Configure the Web server. You must ensure that a Java Runtime Environment (JRE) is available. After you complete these tasks. a sort order defines whether the letter 'a' is less than. All database types must use the TCP/IP protocol. you must configure it to support Cognos features. collect. if required. A metric store is a database that contains content for metric packages. if using Metric Studio. or DB2. if using Metric Studio. you must configure the Cognos components (p. Microsoft SQL Server. On Linux. you must create the database to be used as the content store. You must create this database using Oracle. a metric store (Oracle and DB2). you must set up resources in your environment so that the components can operate. If you use a router. Use the following checklist to guide you through the setup process: ❑ Create the database for the content store and. Set up import sources for Metric Designer. if required. whether the collation is case-sensitive.

4. 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. In the c8_location/configuration/schemas/cmm/sqlserver directory. The user created by the script and given database owner permissions. Value hostname database_name username Setting The name of the computer where the database will be created. Determine if the database is Unicode.cmd script by typing the following command: cmm_create_db hostname database_name username password [user_to_create] Use the following values in your command. 3. This value is optional. Create the database. The user account must be the database owner (dbo) or aliased to the database owner. Tip: One method is to type the following select statement: select * from NLS_DATABASE_PARAMETERS The result set returns NLS_CHARACTERSET as UTF-8 or UTF-16. If you performed a Typical installation of Microsoft SQL Server. Steps for the Content Store on Microsoft SQL Server 1. If you are upgrading from ReportNet. Important: If you are upgrading and you want to keep the existing version of ReportNet. Steps for Oracle 1. The user ID must have permission to create the database. Ensure that the database collation sequence is case-insensitive. password user_to_create 2. Determine which user account Cognos 8 will use to access the database. You must follow the appropriate upgrade process (p. run the cmm_create_db. after you install you must change the authentication mode to SQL Server and Windows. The name of the database that will be created. or AL32UTF8 or AL16UTF16. see the knowledge base article 269587 on the Microsoft Web site. you cannot use it with ReportNet. To ensure the security and integrity of databases. use a different user account for each content store to ensure that each Cognos 8 instance is fully isolated from the others. The password for the username. you can use your existing content store with Cognos 8. Determine which user account Metric Studio will use to access the database. use a different user account for the metric stores. Grant create and drop table privileges for the database to the user account. or not Unicode. For more information. The user ID with permissions to create the database. 2. If you are using Metric Studio. After the content store is upgraded to Cognos 8. it is also important to protect them from unauthorized or inappropriate access.Chapter 6: Setting Up the Environment Your database administrator must back up Cognos 8 databases regularly because they contain the Cognos data. Ensure that the user account for the content store is a member of the db_ddladmin role. you must create a new content store database for use with Cognos 8. 54 . such as the sa user. 35) when creating the new content store database. Steps for the Metric Store on Microsoft SQL Server 1.

Steps for the Content Store on DB2 1. For the metric store. The path where the data files will be created. Determine which user account Metric Studio will use to access the database. and sequences For a metric store. create a new database. 2. and drop tables. Tip: If you want to host more than one content store on your Oracle instance and you will use both at the same time. 2. use a different user account for each content store to ensure that each Cognos 8 instance is fully isolated from the others.Chapter 6: Setting Up the Environment For the metric store. Ensure that the user account that accesses the database has permission to do the following: • connect to the database • create. specifying AL32UTF8 or AL16UTF16 for the database character set parameters. triggers. views. The version of Oracle software that is installed. procedures. 3. Environment variable DB2DIR Description The top level directory that contains the database client software or the entire database installation. update. All permissions must be granted directly to the user account rather than to a role. Set the appropriate environment variables for DB2. oracle9 or oracle10. For example. • insert. The user account must be the database owner (dbo) or aliased to the database owner. If the result set returns an NLS_CHARACTERSET that is not Unicode. create the database specifying NLS_NCHAR_CHARACTERSET as UTF-8 or AL16UTF16. Determine which user account Cognos 8 will use to access the database. Installation and Configuration Guide 55 . In the c8_location/configuration/schemas/cmm/oracle directory. the NLS_NCHAR_CHARACTERSET should be UTF-8 or AL16UTF16. This value is optional. and delete data in the database tables Steps for the Metric Store on Oracle If the Database Does Not Exist 1. you must also ensure that this user account has permission to create types and to execute on DBMS_LOCK and DBMS_UTILITY packages. run the cmm_create_db.cmd script by typing the following command: cmm_create_db sid path database_version [user_to_create] Use the following values in your command. The user created by the script and given database owner permissions. alter. 4. Value sid path database_version user_to_create Setting The SID for the new database that will be created.

use a different user account for each content store to ensure that each Cognos 8 instance is fully isolated from the others. Do not set it to an infinite timeout value. Property Application heap size (applheapsz) Lock Timeout Setting 1024k 4 min. 3. If the codepage is not Unicode. Create a regular user tablespace with a page size of 4k.Chapter 6: Setting Up the Environment Environment variable Description The load library path. 10. Examples: On Solaris: LD_LIBRARY_PATH On AIX: LIBPATH Solaris example: LD_LIBRARY_PATH=$DB2DIR/lib: $LD_LIBRARY_PATH AIX example: LIBPATH=$DB2DIR/lib: $LIBPATH On HP-UX: SHLIB_PATH DB2INSTANCE DB2CODEPAGE HP-UX example: SHLIB_PATH=$DB2DIR/lib: $SHLIB_PATH The default database server connection. We recommend that you set the Lock Timeout configuration parameter to a reasonably long timeout value. 7.You must add driver location. If you already created the content store and are now creating a logging database. 6. Create a user temporary tablespace with a page size of 4k. (or 240 sec. 9. Tip: If you want to host more than one content store on your DB2 instance and you will use both at the same time. For information about whether to use this environment variable. CONNECT and IMPLICITSCHEMA privileges for the database. create an additional regular user tablespace with a page size of 8k. such as four minutes or 240 seconds. 56 . If you are using Metric Studio. Setting this optional environment variable to a value of 1208 provides support for multilingual databases. 2. For Windows XP. create a new database that has a codepage value of 1208. 8. Ensure that the user account has USE privileges for the USER TEMPORARY tablespace and other appropriate tablespaces associated with the database.) 5. see the DB2 documentation. Determine which user account Cognos 8 will use to access the database. Determine if the database is Unicode by typing the following at the command prompt: db2 get database configuration for database_name The codepage is Unicode if it has a value of 1208. Global temporary tables will be created in the user temporary tablespace. 11. ensure that the user account has GRANT privileges for the USER TEMPORARY tablespace. Create a buffer pool with a page size of 16k. Ensure that the user account has CREATETAB. Grant create and drop table privileges on the database to the user account. Create a system temporary tablespace with a page size of 16k. 4. use a different user account for the metric stores. Ensure that you set the following configuration parameters.

Add the UTF-8 character set to the server instance. type cmm_create_db. The initializedb. Set the new database device as the default. Keep a backup of the database device for recovery purposes. 5. On UNIX. If required. 6. the drive on which the database objects will be created. make UTF-8 the default character set on the server. Determine which user account Metric Studio will use to access the database. and must have DBADM privileges to create the schema. run the cmm_create_db. The database alias name.5. 2. The name of the database that will be created.db2 script is invoked by the cmm_create_db. On Windows. Tip: Set log_segment to a minimum of 10 MB. For instructions. The password for the username. This value is optional. Create the database. third party C compiler. Create a database device. This tool sets up the communication between the JDBC driver and the Sybase Adaptive Server instance. Steps for Sybase 1. the compiler must be installed on each DB2 server computer used to the metric store. type cmm_create_db dbinstance username password dbname drive dbalias On UNIX. On the Sybase server. and compiles stored procedures using a platform-specific. the path where the database objects will be created.cmd script in the c8_location/configuration/schemas/cmm/db2 directory and the initializedb. 3. see the Sybase documentation. For instructions. 4. The name must have a maximum of 8 characters. password dbname drive/path dbalias 3. The user ID must have SYSADM or SYSCTRL privileges. Information about the new database will be stored in the new database device. The user ID with permissions to create the database. create a server instance with an 8K server page size.Chapter 6: Setting Up the Environment Steps for the Metric Store on DB2 1. Value dbinstance username Setting The DB2 instance name where the database will be created.cmd script by typing the following command: On Windows. Note: If your DB2 server is an earlier version than 8. If required. Installation and Configuration Guide 57 .cmd script and defines the buffer pools and tablespaces. 7.db2 script in the c8_location/configuration/schemas/cmm/db2/util directory.sh dbinstance username password dbname path dbalias Use the following values in your command. In the c8_location/configuration/schemas/cmm/db2 directory. The user account must have DBADM privileges.2. 2. and it cannot start with a number. Your database administrator can review the scripts to ensure they suit your environment. see the Sybase documentation. install jConnect 5. Locate the cmm_create_db.

Install the DB2 client software on the appropriate computers. 7. 4. use a different user account for each content store to ensure that each Cognos 8 instance is fully isolated from the others. stop the DB2 services and the HTML Search Server. Repeat this entire procedure on the Cognos 8 computers where the software must be installed. 6. create rule. additional steps are required after you install Cognos 8 before you can configure it. You can tune the database to take advantage of DB2 features. Note: If the content store database and Content Manager are on the same computer. You must set up the following on every computer where Content Manager or Framework Manager is installed: • If you use an Oracle database for the content store.jar. 78). Ensure that the user account has the following privileges for the database: create default. Copy the classes12. 9. On Windows. For more information. 5.0 driver. • If you use a DB2 database for the content store. the JSQLConnect. This file includes both the drivers required by the content store and metric stores.zip file to db2java. Determine which user account Cognos 8 will use to access the database. • If you use a DB2 database for a metric store. If the content store is on a different computer from Content Manager. Rename the db2java. When you configure the Content Manager computers. • If you use a Sybase database for the content store. Steps for DB2 1. see the Architecture and Planning Guide. 2. configure a database alias to the content store: • On Windows. you must set up the following on every computer where Application Tier Components for Metric Studio or Metric Designer are installed: • If you use an Oracle database for the metric store. If you use Oracle or DB2 for metric stores. you must set up the database client software and the JDBC 2. ensure that they are all configured to use the same content store (p. For the database.zip file to the c8_location/webapps/p2pd/WEB-INF/lib directory. create procedure. 10. On the computer where Oracle is installed. Tip: If you want to host more than one content store on your Sybase instance and you will use them at the same time. you must set up the JDBC OCI driver. you must set up the JDBC driver.0 driver. To copy the JDBC2 driver. 58 . go to the ORACLE_HOME/jdbc/lib directory. restart the DB2 services and the HTML Search Server.Chapter 6: Setting Up the Environment 8. 3. Grant create and drop table privileges on the database to the user account. Set Up the Database Client for the Content Store or Metric Store If you use Oracle. and create view.jar file is installed to the appropriate location by default and no additional steps are required. On Windows. • On UNIX and Linux. Steps for Oracle 1. or Sybase as the database server for the content store.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on the Cognos 8 computers where the software must be installed. DB2. set the Select into property to True and restart the server. the content store name is automatically used to create an alias. 2. copy the DB2_installation/sqllib/java/db2java. you must set up the database client software and the JDBC 2. If you use a Microsoft SQL Server database for the content or the metric store. run the DB2 Client Configuration Assistant. create table. use the DB2 command line interface. you must set up the JDBC driver.

which allows calls to the Oracle database to determine the required server connections.profile or . you must set and export the database environment variables for the user of the metric store before you start the Cognos processes. 84).Chapter 6: Setting Up the Environment Steps for Sybase 1.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager or Framework Manager is installed. On the computer where Sybase is installed. Copy the jconn2. 67). ensure that the 32-bit Oracle libraries are in the library search path. Example: /usr/local/bin/coraenv TNS_ADMIN The directory that contains the Oracle tnsnames. you must specify environment variables before you can use a DB2 or Oracle database as the metric store. The proper syntax for creating environment variables is shell dependent. some configuration tasks are required to ensure that Cognos 8 (p. Framework Manager (p. One way to set these environment variables is to include these commands in the .login script of the user who starts the Cognos services. Environment variable ORACLE_HOME Description The top level directory that contains the database client software or the entire database installation. When you set the load library paths. Example: /usr/oracle You may be able to use an Oracle script to create the environment variables. If the installation is complete. Setting Up Environment Variables on UNIX for the Metric Store For Cognos 8. Example: $ORACLE_HOME/network/admin PATH The variable to locate executable files. which is usually the $ORACLE_HOME/lib directory or the $ORACLE_HOME/lib32 directory if you installed a 64-bit Oracle client. For more information. Contact your database or network administrator for the correct values for your system. Oracle For Oracle databases. see the Oracle documentation. 86) work in your environment. Example: $PATH:$ORACLE_HOME/bin Installation and Configuration Guide 59 . The following table describes environment variables for Oracle databases. Cognos 8 uses these database variables to connect to your database. 2. go to the Sybase_location/jConnect-5_5/classes directory.ora file. and Metric Designer (p.

jar (Java Archive) files are present in your Java Runtime Environment (JRE).3. Do not overwrite existing . On Solaris: LD_LIBRARY_PATH Solaris Examples: LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBR ARY_PATH LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LI BRARY_PATH AIX Examples: LIBPATH=$ORACLE_HOME/lib:$LIBPATH LIBPATH=$ORACLE_HOME/lib32:$LIBPATH HP-UX Examples: SHLIB_PATH=$ORACLE_HOME/lib:$SHLIB_PATH SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH On AIX: LIBPATH On HP-UX: SHLIB_PATH DB2 For IBM DB2 databases. JVM_version/jre/lib/ext • For JRE.1/lib/ext directory to the extension directory. Cognos 8 checks the environment variable JAVA_HOME to locate a JRE.2 on UNIX. you cannot save your configuration. If you use Sun JRE 1. JVM_version/lib/ext 3. you must check that the required . For Bourne or Korn shells. Java 1. Ensure that you installed the correct JRE for the hardware that you are using. Steps 1. Ensure that the JAVA_HOME environment variable points to the location of the JRE that you are using. ensure that you are using the correct startup file for the /dev/random device. such as data encryption and key management. 60 .jar files. Create the following extension directory if it does not exist in your JVM environment: • For JDK.4.jar files are missing. For more information. it may be necessary to restart your computer for it to take effect. Update the Java Environment Before Cognos 8 can use cryptographic operations. you must set the database variables by running the environment setup scripts included with the IBM DB2 installation. If any of the required . On Windows.1 is the minimum supported JRE for Cognos 8. existing applications may not work. You must use /etc/init. Ensure that the JAVA_HOME environment variable is set to the JRE location. set it so that the environment in which Tomcat is running can access it.d/f20random. therefore. Copy the contents of the c8_location/bin/jre/1. If you set it as a user variable. If you set it as a system variable. see your UNIX documentation. 2. check the . you can set JAVA_HOME as a system variable or a user variable. If you do.3.d or /etc/rc3.jar files before you start Cognos Configuration.profile script: DB2_installation_path/db2profile Contact your database or network administrator for the correct values for your system. 4. run the following command or add it to the .Chapter 6: Setting Up the Environment Environment variable Description The load library path. You must.

If you want to use Report Studio’s image browser. also known as Web aliases. set the content expiry on the c8_location/pat/images virtual directory in your Web server. On UNIX and Linux. Note: When you upgrade. You must set up virtual directories. You can postpone this check until a specified date by using the content expiry feature of the Web server. 2. enable Web Distributed Authoring and Versioning (WebDAV) on your Web server. before you use Web pages generated by Cognos 8. 3. their Web browser checks with the Web server to determine if images are current. If you have more than one version of ReportNet on one computer. For Cognos 8 for reporting. If you install Cognos 8 reporting components in a different location from ReportNet. you must use different alias names for Cognos 8. For Java System Web Server. 90). If you use Web aliases other than cognos8. The cognos8/cgi-bin alias must be defined as a ScriptAlias.conf file located in the Apache_installation/conf directory.xml file permissions to ensure that it belongs to the same group as the Web server. Installation and Configuration Guide 61 . change the existing aliases to include the new location.Chapter 6: Setting Up the Environment Configure the Web Server For all installations. or you are using Microsoft Internet Application Interface (ISAPI). apache_mod or a servlet gateway. However. 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. or your Web server is on another computer.xml file has read permission for others. specify a directory in which to enable WebDAV. see the documentation for your Web server. You can then remove the read permission for others. If you use Apache Web Server. this can result in excess network traffic. you can continue to use the existing aliases. Note: Java System Web Server was formerly named Sun ONE Web Server or iPlanet Web Server. For more information about changing the gateway URI. ensure that you define the cognos8/cgi-bin alias before the cognos8 alias. see "Change a URI" (p. If you are upgrading from ReportNet. you must configure your Web server. ensure that you define the cognos8/cgi-bin alias before the cognos8 alias in the httpd. For Apache Web Server. If you run your Web server under a specific group. see your Web server documentation. you must use cgi-bin as the second part of the alias and you must change the virtual directory in the Gateway URI property to match the new Cognos alias. Steps 1. For information about configuring WebDAV. Each time a user opens Report Studio. Because there are over 600 images. Create the following virtual directories: Alias cognos8 cognos8/cgi-bin Location c8_location/webcontent c8_location/cgi-bin Permission Read Execute You can use a name other than cognos8 in the aliases. you can change the cogstartup. For Cognos 8 for reporting. For information on setting content expiry. for the directories that contain the HTML and Web files for Cognos 8. change the Gateway URI (p. Report Studio users must clear their Web browser cache to get the latest images. By default the cogstartup. Note: iPlanet does not support WebDAV.xml file in the c8_location/configuration directory. the account under which the Web server runs must have read access to the cogstartup. 101) when you configure Cognos components.

and Firefox. Cognos 8 does not provide or download ActiveX controls. copy. which is a component of the browser. ActiveX support must be enabled because Microsoft implements XML using ActiveX. Cookie AS_TICKET Cam_passport cc_session cc_state Type Purpose Cognos Connection Cognos Viewer Query Studio Session temporary Created if Cognos 8 is configured to use a Cognos Series 7 namespace Session temporary Stores a reference to a user session stored on the Content Manager server Session temporary Holds session information that is specific to Cognos Connection Session temporary Holds information during edit operations. and paste 62 . Browser Internet Explorer Setting Allow Cookies Active Scripting Allow META REFRESH Cognos component Cognos Connection Cognos Viewer Report Studio Query Studio Analysis Studio Event Studio Metric Studio Internet Explorer Run ActiveX controls and plug-ins Script ActiveX controls marked safe for scripting Netscape Allow Cookies JavaScript Report Studio Query Studio Analysis Studio Cognos Connection Query Studio Event Studio Metric Studio Firefox Allow Cookies Enable Java Enable JavaScript Load Images Note: Report Studio and Query Studio use the native Microsoft Internet Explorer XML support. For all browsers.Chapter 6: Setting Up the Environment Web Browser Settings Cognos 8 uses the default browser configurations provided by Microsoft. Cognos 8 uses the following cookies to store user information. Only the ActiveX controls that are installed as part of Internet Explorer are enabled through this configuration. such as cut. you must ensure that settings are enabled for cookies and Java scripts. The following table shows the settings that must be enabled in the supported Web browsers. Netscape. Additional required settings are specific to the browser.

Set the environment variable for multilingual support: • For Oracle. you can configure the router to test the availability of a Cognos 8 dispatcher. the following response is returned: 200 OK Set Up the Data Source or Import Source Environment The Cognos 8 modeling tools create and manage metadata. 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 Persistent After upgrading or installing new software. Ensure that you install the appropriate language packs to support the character sets and currency symbols you use. If you use a Sybase data source. Commonly. set the NLS_LANG (National Language Support) environment variable on each computer where Framework Manager or Metric Designer and the Cognos 8 server are installed by typing the following command: NLS_LANG = language_territory. and is set for all Cognos users Persistent Persistent Stores the choice that the user makes for "view members folder" in Report Studio Stores the current folder path if local file access is used. If you upgraded from an older version of Framework Manager. Framework Manager creates and manages metadata for the reporting functions 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 the import source environment for Metric Designer.character_set Installation and Configuration Guide 63 . you are not required to set up anything in the data source environment. and the router can test the availability of a server using a test URL. You must set up the data source environment only if you installed Framework Manager in a different location from the older version. these things depend on the third-party technology you use for your data or import source. Configure the Router to Test Whether a Dispatcher is Available If you use a router to distribute requests to Cognos 8 dispatchers. To test the availability of a dispatcher. Because metadata is derived from data sources in multi-platform or multilingual environments. Steps 1. If the dispatcher is not ready. these steps are not necessary.Chapter 6: Setting Up the Environment Cookie CRN CRN_RS PAT_CURRENT_FOL DER qs Type Purpose Session temporary Contains the content and product locale information. the following response is returned: 503 Service Unavailable If the dispatcher is ready. do the following: • Configure the router to use a URL with the path /p2pd/servlet/ping. restart the Web browser and advise users to clear their browser cache.

set the DB2CODEPAGE environment variable to a value of 1252. RSAB. No settings are required for SAP BW. SU_USER Type of RFC object to be protected S_TABU_DIS Activity Authorization Group S_USER_GRP Activity User group in user master main S_RS_COMP Activity Info Area InfoCube Name (ID) of reporting component FUGR 03 &NC& 03. RSOB. and calendar conventions automatically adapt to the native language and locale. For Oracle. 4.UTF8 The value of the variable determines the locale-dependent behavior of Cognos 8. For more information about whether to use this optional environment variable. For SAP BW. time. 2. numeric. RS_UNIFICATION.Chapter 6: Setting Up the Environment An example is NLS_LANG = JAPANESE_JAPAN. Some of the values shown. configure the following authorization objects so that the modeling tool can retrieve metadata. are default values that you may want to modify for your environment. For Oracle. SUGU. RFC1. sort order. 05 * * InfoArea Technical Name InfoCube Technical Name * Type of reporting component * S_RS_COMP1 Activity Name (ID) of reporting component * * Type of reporting component * Owner (Person Responsible) S_RS_HIER Activity Hierarchy Name * 71 Hierarchy Name 64 . add $ORACLE_HOME/lib to your LD_LIBRARY_PATH. see the DB2 documentation. copy the classes12. such as *. Authorization object S_RFC Field Activity Value 16 Name of RFC to be protected SYST. date. 3. SDTX.jar file from /oracle/oraXX/jdbc/lib to the c8_location/webapps/p2pd/WEB-INF/lib directory. SAP supports only a single code page on non-Unicode SAP BW systems. • For DB2. Error messages. monetary.

which is needed by the modeling tool. For more information about SAP BW authorization objects. Create the new authorization group as a customization in the SAP system. The new authorization group restricts the user’s access to the above table only. see Transaction SU03. you must configure the Cognos 8 components (p. 67) to work in your environment. After you complete these tasks.Chapter 6: Setting Up the Environment Authorization object Field InfoObject Version Value InfoObject Technical Name Hierarchy Version 03 DATA DEFINITION S_RS_ICUBE Activity InfoCube sub-object InfoArea InfoCube InfoArea Technical Name InfoCube Technical Name &NC& represents any table that does not have an authorization group. create a new authorization group and assign the table RSHIEDIR to it. For security reasons. Installation and Configuration Guide 65 .

Chapter 6: Setting Up the Environment 66 .

or Linux only if additional setup is not required. Use these optional configuration tasks to customize your configuration so that Cognos 8 easily integrates into your existing environment. or you must assign a logon account to the Cognos 8 service. you must configure your Web server and specify the database connection properties to the content store. You can configure Cognos 8 to use other resources. some configuration tasks are required. You can configure the Cognos 8 service to use a special user account by selecting the Cognos 8 service from the list of services shown in the Services window in Windows. However. To start Cognos Configuration in interactive mode: • On UNIX or Linux. you can change settings to improve performance. you have several configuration options depending on if you want to continue to use your existing installation. on Windows. Start Cognos Configuration Use the configuration tool. to configure Cognos 8.Chapter 7: Configuring Cognos 8 After you install one or more Cognos 8 components on your computer. you can balance requests among dispatchers by changing their processing capacity or by setting the minimum and maximum number of processes and connections. For example. the console attached to the UNIX or Linux computer on which you are installing Cognos 8 components may not support a Java-based graphical user interface. to print reports using a network printer. and then run Cognos Configuration in silent mode. Other configuration tasks are optional and depend on your Cognos environment. you can deliver Cognos content using a third-party portal by configuring Portal Services. For example. default property settings chosen by Cognos are used to configure the components. use Cognos Configuration to configure your settings. such as printers and Web servers. Before starting Cognos Configuration. If you use a load-balancing scheme in your environment. we recommend that you copy the JDBC drivers to the appropriate location before you start the configuration tool. For example. For information about upgrade options. Initially. For example. you can configure features for Cognos Application Firewall or specify the amount of resources Cognos 8 uses. You should start Cognos Configuration in the last page of the installation wizard on Windows. 13). or to start and stop Cognos services. However. you must configure them to work in your Cognos environment. For example. some additional configuration tasks are required to ensure that the components can communicate with each other. such as using an authentication provider and then enabling single signon for the database connection and the users. the account must already have access to the network printer. The account under which Cognos 8 runs must have access to all required resources. For more information about tuning server performance. go to the c8_location/bin directory and then type Installation and Configuration Guide 67 . If you are upgrading from ReportNet. or to better suit your environment.xml file in the c8_location/configuration directory. Cognos Configuration. see "Upgrade Considerations for Cognos 8" (p. For all types of installations (p. 31). ensure that the operating environment is properly set up. UNIX. For all Windows and most UNIX and Linux installations. You must then manually edit the cogstartup. ensure that all variables have been set. see the Administration and Security Guide. The order in which you configure and start the components is also important. If you distribute Cognos 8 across several computers. Also. For example. you may want to change these default settings if existing conditions make the default choices inappropriate. if you use a database server other than Microsoft SQL for the content store.

you can test the connection between Content Manager and the content store. some configuration tasks are required so that those components work in your Cognos environment. and running on the same computer as the Cognos 8 components • you created the database for the content store and. Cognos 8 uses enterprise-oriented Oracle features to select a listener. • Configuring Single Computer Installations If you install all Cognos server components on one computer. If you keep ReportNet running. ensure that • all Cognos server components are installed on one computer • a Web server is installed. start Cognos Configuration.sh On Windows. Content Manager uses the database logon to access the content store. and Sybase Databases 1. for example. if required Test the installation and configuration Finish the configuration After you complete these configuration tasks. After you save the configuration and start the Cognos 8 service. 84). configure Cognos 8 to point to the existing content store. Cognos Configuration. 68 .Chapter 7: Configuring Cognos 8 . the content store is automatically upgraded and cannot be used by ReportNet. automatically reconnect to the database if the connection fails. under Data Access. If you change the value of a property./cogconfig. you must specify the database server information to ensure that Content Manager can connect to the database you use for the content store. Ensure that the database server has the protocol set to TCP/IP. if using Metric Studio. Content Manager. Set Database Connection Properties for the Content Store For all installations. If you are upgrading from ReportNet. configured. Framework Manager or Metric Designer. Additional configuration tasks are required if either of the Windows modeling tools. click Programs. Cognos 8. Framework Manager (p. you must save the configuration and then restart the Cognos 8 service to apply the new settings to your computer. DB2. Steps for Oracle. 86). You can also configure the Windows modeling tools. are installed on a separate computer. Cognos 8 uses features of the database server to manage the connection. and Metric Designer (p. After you set the database connection properties. Note: Some database servers are available with advanced features. In the Explorer window. balance connection requests among listeners. switch to another listener if the first listener fails. Before you configure Cognos 8. and balance connection requests among dispatchers. the databases for metric stores on an available computer in your network • a Web browser is installed and configured on the same computer as Cognos 8 Use the following checklist to guide you through the required configuration tasks: ❑ Set the database connection properties for the content store ❑ ❑ ❑ ❑ Configure a mail server account Create a metric package. When you select an advanced database. On the computer where you installed Content Manager. you can change the default behavior of Cognos 8 (p. If you select the advanced Oracle database. 2. right-click Content Store and click Delete. from the Start menu. Ensure that you used one of the supported database servers to create the content store. 89) to better suit your Cognos environment. you must configure Cognos 8 to point to a new content store. Cognos 8 requires the TCP/IP protocol to access data and the content store.

2. right-click the new database and click Test. 9. Steps for Microsoft SQL Server Databases 1. If the connection properties are not specified correctly. type the appropriate values for the Database server and port number and Database name properties. In the Properties window. start Cognos Configuration. The logon credentials are immediately encrypted. 3. ensure that you select the type of database you use for the older version of ReportNet. When a content store is used by a new version of Cognos 8. Content Manager can now access the required tables in the content store that you used for the older version. checks the database permissions. If you are upgrading and want to use an existing content store. specify a user ID and password: • Click the Value box next to the User ID and password property and then click the edit button when it appears. Right-click Content Manager. 5. Content Manager. Installation and Configuration Guide 69 . For example. By default.Chapter 7: Configuring Cognos 8 This deletes the default resource. type the appropriate values and click OK. click Save. Content Manager can now create the required tables in the content store when you start the Cognos 8 service for the first time. In the Name box. Content Manager must be configured to access only one content store. If you installed more than one version of Cognos 8. in the Properties window. 7. for the Database name property. For the Database name property. the tables are not created and you cannot connect to Cognos Connection. In the Type box. and then click New resource. When a content store is used by a new version of Cognos 8. provide values depending on your database type: • If you use a DB2 database. 4. type the name of the database you previously created in Microsoft SQL Server to use as the content store. change the default value for the Database server and port number. ensure that you select the type of database you use for the older version of ReportNet. (description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl ))) • If you use a Sybase database. click Content Store. • If you use an advanced Oracle database. Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection. under Data Access. Database. it cannot be used by an older version of ReportNet. select Oracle database (Advanced). 3.User ID and password dialog box. Cognos components use properties for a Microsoft SQL Server database. type the database alias. it cannot be used by older versions. • If you use an Oracle database. In the Explorer window. type the Oracle Net8 keyword-value pair for the connection. you must use a different content store for each version. type a name for the resource. type the appropriate values for the Database server and port number and Service name properties. 8. for the Database specifier property. If you want to change the logon credentials. select the type of database and click OK. The table is not deleted and is used each time the test is repeated. In the Explorer window. and creates and populates a table. 6. On the computer where you installed Content Manager. If you are upgrading and want to use an existing content store. If you are upgrading from ReportNet. you must use a different content store for each version. If you installed more than one version of Cognos 8. From the File menu. Test the connection between Content Manager and the content store. If necessary. • In the Value . 4. Content Manager connects to the database.

click Yes. right-click Notification and select New resource. ensure that the notification database exists and that all Content Manager computers are configured to use it. Ensure that the default user name has been removed. Specify a Mail Server Account and Notification Database If you want to send reports by email. • In the Properties window. for load balancing). 6. In the Properties window. for the SMTP mail server property. Otherwise. you can test the connections to the mail server and notification database. 2. click Notification. Click the Value box next to the User ID and password property and then click the edit button when it appears. By default. Steps 1. Click the Value box next to the Account and password property and then click the edit button when it appears. If so. 8. On each computer where Content Manager is installed. type the appropriate values and then click OK. If the connection properties are not specified correctly. the notification server uses the same database that Content Manager uses for the content store. 6. you must configure all Content Manager and Application Tier Components computers to use the same database for notification. • Select the type of database from the pull-down menu. and creates and populates a table. under Data Access. start Cognos Configuration. Identify the database that is used for notification: • In the Explorer window. • Click OK. Type the appropriate values in the Value . Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. You can use a separate database for notification. the tables are not created and you cannot connect to Cognos Connection. Content Manager connects to the database. In the Value . type the appropriate value for the default sender account. • Type a name for the database resource. Test the connection between Content Manager and the content store.User ID and password dialog box. You must also specify the location of the database that is used by the notification server to store job and schedule information. 70 . The logon credentials are immediately encrypted. the default account is used and notifications will not work properly. Tip: If logon credentials are not required for the SMTP server. In the Explorer window. In the Properties window. right-click the new database and click Test. type the host name and port of your SMTP (outgoing) mail server. Content Manager can now create the required tables in the content store when you start the Cognos 8 service for the first time. In the Explorer window. When you are prompted for confirmation to leave this property blank. click Save. 5. Cognos 8 uses the mail server account and settings that were set up for ReportNet. 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. When you finish configuring a mail server account and notification database. enter the values for the notification database resource. remove the default information for the Account and password property. If you are upgrading from ReportNet. 7. checks the database permissions. 4.Chapter 7: Configuring Cognos 8 5. 7. Database. If you use a distributed installation (for example.Account and password dialog box and then click OK. 3. From the File menu. Tip: To be able to open reports that are sent by email. you must configure a mail server account.

Cognos 8 tests the database connection and tests the mail server connection. and click Next. Before you can use the New Metric Package wizard. A metric package is a Cognos Connection representation of a Metric Studio application. click Initialize. For a new metric store. type the name of the database server and the database. The New Metric Package wizard appears automatically the first time you access Metric Studio. Click Metric Studio. Specify the information required for your database type: • For a Microsoft SQL Server database. and type the user ID and password of the user account with access to the database. you must have access to a metric store used with Metrics Manager version 2. click Test. including the start and end dates of the fiscal year. Installation and Configuration Guide 71 . 8. select the Password and Create a signon that the Everyone group can use check boxes. select the Password and Create a signon that the Everyone group can use check boxes. and type the user ID and password of the user account with access to the database. • For an Oracle database. From the File menu. The New Metric Package wizard appears. you do not have to perform this step. Test the notification and mail server connections. Click Finish. 6. Metric Studio opens and the new metric package is displayed in Cognos Connection. For information about managing the metric store. type the connection string. you must create at least one metric package using the New Metric Package wizard. Tip: To test whether the parameters are correct. you can use the wizard to upgrade the metric store. Under Signons. Create a Metric Package Before users can use Metric Studio. Click Next and follow the prompts to provide the information necessary to initialize the database. In the Type box. Click the new data source and click Next.0 or later or you must create a database for a new metric store (p. see the Cognos 8 Administration and Security Guide. 8. 10. and type the user ID and password of the user account with access to the database. type the name of the database and the connection string. and metric management tasks for that application. 53). reports. Click Next and then click Finish. you also provide the information necessary to initialize the database. and click Next. 5.1 or later. Tip: To use the default notification database. Type a name and description for the data source connection for the metric store that contains the content for this metric package. 4. 11. Select User ID.Chapter 7: Configuring Cognos 8 Ensure that the values match on all Content Manager computers. • For a DB2 database. Steps 1. Under User ID. Type a name and description for the Metric Studio application to represent this metric package. click the database type and then click Next. 9. The metric package content is stored in a metric store. 9. In the Explorer window right-click Notification and click Test. 7. click Save. including how to load data. select the Password and Create a signon that the Everyone group can use check boxes. 3. Start Cognos Connection. When you see the page that summarizes the data source details and the metric store settings. Click New data source. 2. A metric package contains connection information. If the database was used with an earlier version of Metric Studio 8. Use the wizard to define the metric package name and the data source connection to the metric store.

you must start the Cognos 8 service. If you installed Metric Studio and you have created a package. 7. a message appears indicating that configuration files were detected and upgraded to the new version. For information about managing the metric store. click the database type and click Next. 6. Under User ID.Chapter 7: Configuring Cognos 8 Steps Using an Existing Metric Store 1. 3. Click New data source. Under Signons. type the name of the database and the connection string. If you are upgrading. see your operating system documentation. Start Cognos Configuration. Ensure that you save your configuration. Tip: To test whether the parameters are correct. type the name of the database server and the database. Click the new data source and click Next. You can create a metric package only if Metric Studio is installed and configured properly. Steps for Cognos 8 1. and click Next. 72 . you must configure the process as a daemon. • For an Oracle database. select the Password and Create a signon that the Everyone group can use check boxes. 2. On UNIX and Linux. see the Administration and Security Guide. type the connection string. 10. From the Actions menu. Start Cognos Connection. Note: Cognos 8 cannot access any reporting data unless the data is first packaged in and published from Framework Manager. Click Metric Studio. Then you can test the installation by starting the Cognos 8 service and then opening Cognos Connection. click Test. 4. select the Password and Create a signon that the Everyone group can use check boxes. the Cognos 8 service is configured to start automatically by default. Specify the information required for your database type: • For a Microsoft SQL Server database. select the Password and Create a signon that the Everyone group can use check boxes. You must install and configure both the server components of Cognos 8 and Framework Manager before you can use Cognos 8 for reporting. 5. otherwise you will not be able to start the Cognos 8 service. • For a DB2 database. and type the user ID and password of the user account with access to the database. In the Type box. Test the Installation and Configuration You can test your configuration settings by running the test feature before you start the Cognos 8 service. 9. If you installed Framework Manager or Metric Designer. The wizard updates the database schemas and other information. you have already tested your installation and configuration. For more information. Metric Studio opens and the new metric package is displayed in Cognos Connection. 8. Select User ID. Click Next and then click Finish. 2. On Windows. Before you can use Framework Manager or Metric Designer. Type the name and description for the data source connection for the metric store that contains the content for this metric package. click Test. and type the user ID and password of the user account with access to the database. Type the name and description for the Metric Studio application to represent this metric package and click Next. and type the user ID and password of the user account with access to the database. 3. you can test it by starting the application and creating a project. The New Metric Package wizard appears. Click Upgrade. to start the Cognos 8 process automatically.

It may take a few minutes for the Cognos 8 service to start. click Programs. click Local Configuration. • For the CGI gateway: http://host_name:port/cognos8 • For an ISAPI gateway: http://host_name:port/cognos8/isapi • For Apache Connector on Windows: http://host_name:port/cognos8/cgi-bin/mod_cognos. and the mail server. tests the namespace configuration. 5. from the Start menu. If any test fails. in the Explorer window. reconfigure the affected properties and then test again. Start the Cognos 8 service. from the Start menu. you can perform some additional configuration tasks to customize the behavior of Cognos 8 components to better suit your Cognos environment (p. Installation and Configuration Guide 73 . and tests the connections to the content store. where cognos8 is the virtual directory you created when you configured the Web server. your Cognos 8 installation is working. such as configuring Cognos 8 components to use an authentication provider (p. 6.sl • For a gateway servlet: http://host_name:port/context_root/servlet/ Gateway It may take a few minutes for the Web page to open. Framework Manager. logging database. To start Metric Designer. 122).so • For Apache Connector on HPUX: http://host_name:port/cognos8/cgi-bin/mod_cognos. If you see the Welcome page of Cognos Connection. From the Actions menu. Steps for Framework Manager 1. 4. If you see the Welcome page of Metric Designer. If you see the Welcome page of Framework Manager. This action starts all installed services that are not running. Open a Web browser.dll • For Apache Connector on Solaris and AIX: http://host_name:port/cognos8/cgi-bin/mod_cognos. You may be prompted to upgrade if the model schema version is older than the currently supported version. If you want to start a particular service. 89). To start Framework Manager. 7. Tip: If Test is not available for selection. your installation is working. We recommend that you specify the amount of resources the Cognos 8 service uses to ensure that performance is optimized. Finishing the Configuration After you complete the required configuration tasks. notification database. You can also add resources. 2. select the service node in the Explorer window and then click Start from the Actions menu. Cognos 8. click Start. Cognos 8.Chapter 7: Configuring Cognos 8 Cognos Configuration checks the CSK availability. 2. Do not start the service until all tests pass. Open Cognos Connection by typing one the following. Steps for Metric Designer 1. Metric Designer. your installation is working. click Programs. Start the Cognos 8 service.

If you install Cognos 8 in new locations. and Content Manager on multiple computers. Use the following checklist to guide you through the required configuration tasks: ❑ Configure the Content Manager computers ❑ ❑ ❑ ❑ ❑ ❑ ❑ Configure the Application Tier Components computers Configure the gateway computers Create a metric package. and the database that is used for notification. you can change the default behavior of Cognos 8 components (p. if required Test the installation and configuration Finish the configuration After you complete these configuration tasks. 122) or enabling and disabling services (p. You must also configure cryptographic properties to ensure that each computer uses the same settings. see the Architecture and Planning Guide. you can install any one of the following components on a separate computer: • gateway • Application Tier Components • Content Manager For information about planning a distributed installation. if required Configure the Metric Designer computers. If you are upgrading from ReportNet. If you install Cognos 8 components on more than one computer. 122). You can also add resources. Other configuration tasks. 89) to better suit your Cognos environment. You must configure the gateway computer last so that cryptographic keys are shared and secure communication can take place among the three components. gateway. The dispatcher should be located on a report server computer. such as using an authentication provider (p. you must update the locations using Cognos Configuration. all the distributed components must be the same version of Cognos 8. You must configure and then start the services on at least one computer where you installed Content Manager before you configure other computers in your Cognos environment. you must configure environment properties so that the distributed components can communicate with each other: • The Content Manager computers must know the location of the content store. We recommend that you specify the amount of resources the Cognos 8 service uses to ensure that performance is optimized. In a distributed environment. the other Content Manager computers. • The Application Tier Components computer must know the location of the Content Manager computers and the database to use for job and schedule information. The server specified for the External Dispatcher URI property on the gateway computer must be the last server that you start. 105) are optional and change the default behavior of Cognos 8 components to better suit your reporting or scorecarding objectives.Chapter 7: Configuring Cognos 8 Configuring Distributed Installations To improve performance or to enhance security. You can install the Application Tier Components. if required Configure the Framework Manager computers. the sequence in which you configure computers is important. such as configuring Cognos 8 components to use an authentication provider (p. 74 . • The gateway computer must know the location of at least one dispatcher.

2. see the Administration and Security Guide. Your installation may include more than one Content Manager. which is installed with Content Manager. configure Cognos 8 to point to the existing content store. using the Administration tool. The standby Content Manager computers are for failover protection. If you select the advanced Oracle database. unsaved session data is lost. Ensure that the database server has the protocol set to TCP/IP. is available to issue certificates to other Cognos computers. DB2. switch to another listener if the first listener fails. the content store is automatically upgraded and cannot be used by ReportNet. One Content Manager computer is active and one or more Content Manager computers are on standby. This ensures that the certificate authority service. ensure that you created the database for the content store on an available computer in your network. When the active Content Manager fails. However. If the active Content Manager computer is not available because of a software or hardware failure. For more information about activating a Content Manager service. Note: Some database servers are available with advanced features. In the Explorer window. When you select an advanced database. start Cognos Configuration. If you are upgrading from ReportNet.Chapter 7: Configuring Cognos 8 Configuring Content Manager Computers In a distributed installation. for example. you must configure Cognos 8 to point to a new content store. you can test the connection between Content Manager and the content store. right-click Content Store and click Delete. To support failover protection. balance connection requests among listeners. you can use the existing configuration data. Cognos 8 components use features of the database server to manage the connection. After you save the configuration and start the Cognos 8 service. Before you configure Content Manager. Cognos 8 components require the TCP/IP protocol to access data and the content store. If you are upgrading from ReportNet. Use the following checklist to guide you through the required configuration tasks for the Content Manager computers: ❑ Set the database connection properties for the content store ❑ Specify a mail server account and notification database ❑ Configure the environment properties ❑ Start the Cognos 8 service Set Database Connection Properties for the Content Store For all installations. under Data Access. at least one of the computers where you installed Content Manager must be configured. each on a different computer. Steps for Oracle. Content Manager. On the computer where you installed Content Manager. The first Content Manager computer to be started becomes the default active Content Manager. you must specify the database server information to ensure that Content Manager can connect to the database you use for the content store. Cognos 8 components use enterprise-oriented Oracle features to select a listener. If you keep ReportNet. running and accessible before you configure other computers in your Cognos environment. users may be prompted to log on. and Sybase Databases 1. When another Content Manager becomes active. Installation and Configuration Guide 75 . some features in Cognos 8 are new. We recommend that you configure the new features. Content Manager uses the database logon to access the content store. Ensure that you used one of the supported database servers to create the content store. you must synchronize the system clocks on the Content Manager computers. automatically reconnect to the database if the connection fails. You can designate another Content Manager computer as default active. a standby Content Manager computer becomes active and requests are directed to it. and balance connection requests among dispatchers. After you set the database connection properties.

it cannot be used by older versions. In the Name box. • If you use an advanced Oracle database. type the appropriate values and click OK. type the name of the database you previously created in Microsoft SQL Server to use as the content store. In the Type box. In the Explorer window. type the database alias. Cognos components use properties for a Microsoft SQL Server database. If you are upgrading from ReportNet. for the Database specifier property. click Content Store. right-click the new database and click Test. • In the Value . start Cognos Configuration. type a name for the resource. 8. If you are upgrading and want to use an existing content store. checks the database permissions. From the File menu. provide values depending on your database type: • If you use a DB2 database. If you want to change the logon credentials. you must use a different content store for each version. The logon credentials are immediately encrypted. ensure that you select the type of database you use for the older version of ReportNet. When a content store is used by a new version of Cognos 8. in the Properties window. If you are upgrading and want to use an existing content store. If necessary. and creates and populates a table. Steps for Microsoft SQL Server Databases 1. 6. ensure that you select the type of database you use for the older version of ReportNet. On the computer where you installed Content Manager. 3. for the Database name property. In the Properties window. type the appropriate values for the Database server and port number and Service name properties. 7. If the connection properties are not specified correctly. 4. 2. 9. Right-click Content Manager. 4. type the Oracle Net8 keyword-value pair for the connection. under Data Access. Database. the tables are not created and you cannot connect to Cognos Connection. Test the connection between Content Manager and the content store. For the Database name property. select the type of database and click OK. (description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl ))) • If you use a Sybase database. When a content store is used by a new version of Cognos 8. Content Manager must be configured to access only one content store. Content Manager can now access the required tables in the content store that you used for ReportNet. Content Manager. Content Manager can now create the required tables in the content store when you start the Cognos 8 service for the first time. 76 . In the Explorer window. 5. If you installed more than one version of Cognos 8. select Oracle database (Advanced). type the appropriate values for the Database server and port number and Database name properties. By default. • If you use an Oracle database. Content Manager connects to the database. and then click New resource. If you installed more than one version of Cognos 8. click Save. 3.User ID and password dialog box.Chapter 7: Configuring Cognos 8 This deletes the default resource. specify a user ID and password: • Click the Value box next to the User ID and password property and then click the edit button when it appears. you must use a different content store for each version. Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection. change the default value for the Database server and port number. For example. it cannot be used by an older version of ReportNet.

You must also specify the location of the database that is used by the notification server to store job and schedule information. If you are upgrading from ReportNet. type the host name and port of your SMTP (outgoing) mail server. click Notification. Click the Value box next to the Account and password property and then click the edit button when it appears. • Select the type of database from the pull-down menu. In the Properties window. for load balancing). you must configure a mail server account. Installation and Configuration Guide 77 . When you are prompted for confirmation to leave this property blank. checks the database permissions. type the appropriate value for the default sender account.Account and password dialog box and then click OK. remove the default information for the Account and password property. Steps 1. • Click OK. You can use a separate database for notification. When you finish configuring a mail server account and notification database. Ensure that the default user name has been removed. In the Explorer window. start Cognos Configuration. under Data Access. By default. If so. Identify the database that is used for notification: • In the Explorer window. From the File menu. In the Properties window. 4. 3. right-click the new database and click Test.User ID and password dialog box. Cognos 8 uses the mail server account and settings that were set up for the older version. If you use a distributed installation (for example. right-click Notification and select New resource. Test the connection between Content Manager and the content store. Tip: To be able to open reports that are sent by email. In the Explorer window. In the Value . 6. If the connection properties are not specified correctly. you must change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. you can test the connections to the mail server and notification database. enter the values for the notification database resource. On each computer where Content Manager is installed. Type the appropriate values in the Value . and creates and populates a table. the notification server uses the same database that Content Manager uses for the content store. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. click Save. • Type a name for the database resource. Specify a Mail Server Account and Notification Database If you want to send reports by email. click Yes. Database. • In the Properties window. Content Manager connects to the database. Click the Value box next to the User ID and password property and then click the edit button when it appears. 2. ensure that the notification database exists and that all Content Manager computers are configured to use it. Content Manager can now create the required tables in the content store when you start the Cognos 8 service for the first time. Tip: If logon credentials are not required for the SMTP server. for the SMTP mail server property. 6. 7. 5. type the appropriate values and then click OK. the default account is used and notifications will not work properly. Otherwise. 8. you must configure all Content Manager and Application Tier Components computers to use the same database for notification. The logon credentials are immediately encrypted. 7.Chapter 7: Configuring Cognos 8 5. the tables are not created and you cannot connect to Cognos Connection.

start Cognos Configuration. 105) on the Content Manager computers. click Add.Chapter 7: Configuring Cognos 8 Ensure that the values match on all Content Manager computers. From the File menu. select the service node in the Explorer window and then click Start from the Actions menu. 122). such as the Application Tier Components computer and gateway computers. Important: You must include all Content Manager URIs in the list. you do not have to perform this step. • Repeat the previous two bulleted steps for each URI to be added. or change global settings (p. click Environment. 78 . click Save. • Click OK. click the value for Content Manager URIs and then click the edit button. If you use Web aliases other than cognos8. From the File menu. Specify the URIs for the other Content Manager computers: • In the Value . you must make the same changes on the other Content Manager computers. Cognos 8 tests the database connection and tests the mail server connection. in the Properties window. On the Content Manager computer that you want to designate as the default active Content Manager. Otherwise you can continue to configure the Content Manager computers by changing the default property settings (p. you can configure Cognos 8 components to use an authentication provider (p. you must list all Content Manager URIs on each Content Manager computer. Tip: To use the default notification database. Configure Environment Properties for Content Manager Computers After installing Content Manager on the computers you are using for failover protection. If you installed more than one Content Manager. This value identifies the local Content Manager computer and is required. If you are upgrading. 5. This action starts all installed services that are not running. 2. For example. click the value for Gateway URI and change the cognos8 element to the name you used in your Web aliases. click and then type the full URI of the Content Manager computer. 9. 4. Steps for the First Content Manager Computer 1. you must configure Content Manager on those computers. Tip: We recommend that you use the computer with the highest processor speed for the default active Content Manager. 8. 8.Content Manager URIs dialog box. 9. ensure that Create symmetric key store is set to True. 89) so that they better suit your environment. The key store must be created on the default active Content Manager computer. under CSK settings. In the Properties window. • In the blank row of the table. In the Explorer window right-click Notification and click Test. 10. under Security. click Cryptography. In the Explorer window. If you want to start a particular service. enable and disable services (p. In the Explorer window. 3. Important: If you change global settings on one Content Manager computer. 7. click Save. After you complete the required configuration tasks. 106). 6. Do not delete the first value in the table. You can then perform the required configuration tasks on other computers. Set Store symmetric key locally to True. From the Actions menu. click Start. Test the notification and mail server connections. you must also add the standby Content Manager URIs to the original Content Manager computer. In the Properties window. the certificate authority service is available to issue certificates to other Cognos computers.

Chapter 7: Configuring Cognos 8 As soon as Cognos 8 components start. 8. In the Properties window. click Environment. In the Explorer window. you must list all Content Manager URIs on each report server computer. 11. Ensure that you already configured the Environment properties on at least one Content Manager computer and that Cognos 8 components are running on that computer. start Cognos Configuration. Configuring Application Tier Components Computers You can install the Application Tier Components component on one or more computers. 2. click Cognos. click Cryptography. In the Properties window. Do not delete the first value in the table. 14. If you are upgrading from ReportNet. click Add. Ensure that the computer where you installed the active Content Manager is configured and available before you configure Application Tier Components computers. On the standby Content Manager computer. In the Explorer window. The key store is created on the default active Content Manager computer. 12. on the Application Tier Components computer. ❑ Configure Environment properties. 13. click Content Store. From the Actions menu. If you installed more than one Content Manager. Installation and Configuration Guide 79 . Steps for Standby Content Manager Computers 1. From the File menu. set the Password property to match what you configured on the default active Content Manager computer. Specify the URIs for the other Content Manager computers: • In the Value . click and then type the full URI of the Content Manager computer. Ensure that all other cryptographic settings match what you configured on the default active Content Manager computer. select the service node in the Explorer window and then click Start from the Actions menu. There can be only one key store in a Cognos installation. click Start. under Security. Cognos 8 uses the existing configuration data for the Application Tier Components computers. Cryptography. 4. 7. This action starts all installed services that are not running. Important: You must include all Content Manager URIs in the list.Content Manager URIs dialog box. Ensure that the values for all of the properties match what you configured on the default active Content Manager computer. 10. click the value for Content Manager URIs and then click the edit button. you must do the following: ❑ Specify a mail server account and notification database. this computer becomes the default active Content Manager computer. you must configure all the environment properties. Content Manager. if you installed the Application Tier Components in a new location. under Data Access. • Click OK. set Create symmetric key store to False. under Security. depending on your environment. 9. • Repeat the previous two bulleted steps for each URI to be added. If you want to start a particular service. under CSK settings. click Save. This value identifies the local Content Manager computer and is required. the default cryptographic provider. • In the blank row of the table. In the Explorer window. 5. 6. However. Under the Certificate Authority settings property group. 3. In the Explorer window. If Content Manager and the Application Tier Components are installed on separate computers.

In the Properties window. click Save. type the host name and port of your SMTP (outgoing) mail server. for the SMTP mail server property. the default account is used and notifications will not work properly. Configure Environment Properties for Application Tier Components Computers If you install the Application Tier Components component on a different computer than Content Manager. the Application Tier Components computer can work in your environment. Tip: If logon credentials are not required for the SMTP server.Chapter 7: Configuring Cognos 8 ❑ Start the Cognos 8 service (if not already running). Other configuration tasks are optional and may be performed later. 80 . right-click Notification and select New resource. Tip: To be able to open reports that are sent by email. 6. Click the Value box next to the Account and password property and then click the edit button when it appears. If you are upgrading from ReportNet. You must also specify the location of the database that is used by the notification server to store job and schedule information. enter the values for the notification database resource. Start Cognos Configuration. click Notification. Cognos 8 uses the mail server account and settings that were set up for the older version. 7. After you complete these required configuration tasks. Steps 1. In the Explorer window. 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. In the Explorer window right-click Notification and click Test. you must configure a mail server account. Identify the database that is used for notification: • In the Explorer window. • Type a name for the database resource. 4. click Yes. under Data Access. remove the default information for the Account and password property. 8. Ensure that the values match on all report server and Content Manager computers. When you finish configuring a mail server account and notification database. Cognos 8 tests the database connection and tests the mail server connection. start Cognos Configuration. you can test the connections to the mail server and notification database. Ensure that the default user name has been removed. The distributed components can then communicate with each other. You must use the same database that is used for notification on Content Manager computers. 5. Otherwise. Type the appropriate values in the Value . • Select the type of database from the pull-down menu. Specify a Mail Server Account and Notification Database If you want to send reports by email. 3. Test the notification and mail server connections. On each computer where a report server is installed. From the File menu. type the appropriate value for the default sender account. Otherwise the URL in the email will contain localhost and remote users will not be able to open the report. You must configure all report server computers to use the same database for notification. Database. In the Properties window. 2. Steps 1.Account and password dialog box and then click OK. • In the Properties window. 9. you must configure the Application Tier Components computer so that it knows the location of Content Manager. When you are prompted for confirmation to leave this property blank. • Click OK.

Otherwise you can continue to configure the Application Tier Components computers by changing the default property settings so that they better suit your environment. specify the appropriate value for the Gateway URI. 10. you can configure more than one dispatcher for a gateway computer. click and then type the full URI of the Content Manager computer. We recommend that the gateway use the dispatcher on a Application Tier Components computer.Content Manager URIs dialog box. select the service node in the Explorer window and then click Start from the Actions menu. the default cryptographic provider. requests are normally routed to the first dispatcher in the list. Under the Certificate Authority settings property group. you must configure the gateway computer so that it knows the location of a dispatcher. such as the gateway computers. 6. Installation and Configuration Guide 81 . • In the blank row of the table. 11. Specify the URIs for the remaining Content Manager computers: • In the Value . the gateway computer can work in your environment. The primary dispatcher status is monitored by the gateway. In the Properties window. click Cognos. 9. From the File menu. Cryptography. After you completed the required configuration tasks for each Application Tier Components computer in your environment. 4. 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. Important: You must include all Content Manager URIs in the list. 8. In the Explorer window. under Security. click Start. set the Password property to match what you configured on the default active Content Manager computer. 105). For example.Chapter 7: Configuring Cognos 8 2. click Add. click the value for Content Manager URIs and then click the edit button. A dispatcher is installed on every Content Manager and Application Tier Components computer. If you are using Tomcat. 105). When multiple dispatchers are configured. from the Actions menu. and requests are routed back to this component when it returns to service. you can enable and disable services (p. This action starts all installed services that are not running. Ensure that all other cryptographic settings match what you set on the default active Content Manager computer. If you want to start a particular service. configure where to send log messages (p. Change the localhost portion of the existing URI to the name of any Content Manager computer. You must configure the Environment properties on the gateway computer. by changing the localhost portion to the name of the gateway computer. If you install the gateway component on a different computer than Content Manager or Application Tier Components. If this dispatcher becomes unavailable. 5. Configure Gateway Computers You can install the gateway on one or more Web server computers. 7. click Environment. 98) or configure the amount of resources the Cognos 8 service uses (p. In the Properties window. Other configuration tasks are optional and may be performed later. 3. • Click OK. In the Explorer window. you can now perform the required configuration tasks on other computers. click Save. For failover protection. • Repeat the previous two bulleted steps for each URI to be added. the gateway determines the next functioning dispatcher on the list and routes requests there. After you do the required configuration tasks.

Chapter 7: Configuring Cognos 8

Steps
1. Start 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: • Click in the value column. • Click the edit button. • Change the localhost portion of the URI to the name or IP address of an Application Tier Components computer. Tip: If you want to send requests to the gateway from an SDK application, we recommend that you connect to a dedicated gateway that is configured to connect to the dispatcher using the Internal Dispatcher URI. Do not change your main gateway to use the Internal Dispatcher URI. Doing so will reduce the security of the Cognos 8 portal and studios. • 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. • 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. Cognos 8 components check the CSK availability. 8. From the File menu, click Save. After you completed the required configuration tasks for each gateway computer in your environment, you can continue to configure the gateway computers by changing the default property settings so that they better suit your environment. For example, you can configure a gateway to use a namespace.

Create a Metric Package
Before users can use Metric Studio, you must create at least one metric package using the New Metric Package wizard. A metric package is a Cognos Connection representation of a Metric Studio application. A metric package contains connection information, reports, and metric management tasks for that application. The metric package content is stored in a metric store. The New Metric Package wizard appears automatically the first time you access Metric Studio. Use the wizard to define the metric package name and the data source connection to the metric store. For a new metric store, you also provide the information necessary to initialize the database, including the start and end dates of the fiscal year. If the database was used with an earlier version of Metric Studio 8.1 or later, you can use the wizard to upgrade the metric store. Before you can use the New Metric Package wizard, you must have access to a metric store used with Metrics Manager version 2.0 or later or you must create a database for a new metric store (p. 53). 1. Start Cognos Connection. 2. Click Metric Studio. The New Metric Package wizard appears. 3. Type a name and description for the Metric Studio application to represent this metric package, and click Next.

82

Chapter 7: Configuring Cognos 8 4. Click New data source. 5. Type a name and description for the data source connection for the metric store that contains the content for this metric package, and click Next. 6. In the Type box, click the database type and then click Next. 7. Specify the information required for your database type: • For a Microsoft SQL Server database, type the name of the database server and the database. Under Signons, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. • For an Oracle database, type the connection string. Under User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. • For a DB2 database, type the name of the database and the connection string. Select User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. Tip: To test whether the parameters are correct, click Test. 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. Click Finish. Metric Studio opens and the new metric package is displayed in Cognos Connection. For information about managing the metric store, including how to load data, see the Cognos 8 Administration and Security Guide.

Steps Using an Existing Metric Store
1. Start Cognos Connection. 2. Click Metric Studio. The New Metric Package wizard appears. 3. Type the name and description for the Metric Studio application to represent this metric package and click Next. 4. Click New data source. 5. Type the name and description for the data source connection for the metric store that contains the content for this metric package, and click Next. 6. In the Type box, click the database type and click Next. 7. Specify the information required for your database type: • For a Microsoft SQL Server database, type the name of the database server and the database. Under Signons, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. • For an Oracle database, type the connection string. Under User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. • For a DB2 database, type the name of the database and the connection string. Select User ID, select the Password and Create a signon that the Everyone group can use check boxes, and type the user ID and password of the user account with access to the database. Tip: To test whether the parameters are correct, click Test. 8. Click Next and then click Finish. 9. Click the new data source and click Next. 10. Click Upgrade. The wizard updates the database schemas and other information. Metric Studio opens and the new metric package is displayed in Cognos Connection. For information about managing the metric store, see the Administration and Security Guide. Installation and Configuration Guide 83

Chapter 7: Configuring Cognos 8

Configuring Framework Manager Computers
After you install Framework Manager on your Windows computer, you configure it so that it works in your reporting environment. Some configuration tasks are optional. You perform them to change the default property values used by Framework Manager. If you install Framework Manager on the same computer as the non-modeling components of Cognos 8, no configuration is required if you • configure your Web server using the default virtual directories • use the default ports • use the default resources • use the default cryptographic settings If you upgraded from an older version of Framework Manager, you can use the same models and projects that you used with the older version. To upgrade existing projects, you must open them in the new version of Framework Manager. If you install Framework Manager on a different computer from the non-modeling components of Cognos 8, you must do the following: ❑ Configure environment properties for Framework Manager computers.

❑ Configure a source control system. ❑ Upgrade Framework Manager projects, if required. Configure Environment Properties for Framework Manager Computers
If you install Framework Manager on a different computer from the non-modeling components of Cognos 8, you must configure it to communicate with the other components. We recommend that you install and configure Cognos 8 components before you configure Framework Manager. You must first install and configure Content Manager and then start the Cognos 8 service on at least one Content Manager computer before you configure Framework Manager. This ensures that the certificate authority service issues a certificate to the Framework Manager computer. You must also set up the data sources (p. 63) before you configure Framework Manager. Ensure that the Web server is configured and running (p. 61). Important: If Cognos 8 was installed in more than one location, ensure that all URIs point to the correct version of Cognos 8. Framework Manager must be configured to use the same version of Cognos 8.

Installations with a Firewall
You can configure Framework Manager to access the non-modeling components of Cognos 8 through the dispatcher or through the gateway. If the computer where you installed Framework Manager does not have access to the Cognos 8 dispatcher because of a firewall, you must configure Framework Manager to access Cognos 8 through the gateway. In this type of installation, Framework Manager and the gateway must be outside the firewall and the dispatcher must be inside the firewall. In addition, Framework Manager must have access to a Web server that supports chunked transfer encoding and is outside the firewall.

Steps
1. On the computer where you installed Framework Manager, start Cognos Configuration. 2. In the Explorer window, click Environment. 3. In the Properties window, in the Gateway URI box, type the appropriate value. • To use ISAPI, replace cognos.cgi with cognosisapi.dll. • To use an Apache Web server, type the following syntax: For Apache 1.3 module, http://host_name:port/cognos8/cgi-bin/mod_cognos.dll For Apache 2.0 module, 84

Chapter 7: Configuring Cognos 8 http://host_name:port/cognos8/cgi-bin/mod2_cognos.dll Note: Ensure that you configured your Apache Web Server (p. 101). • To use a servlet gateway, type the following syntax: http[s]://host_name:port/context_root/servlet/Gateway where context_root is the value you assigned to the ServletGateway Web application when you deployed the ServletGateway application. Note: Ensure that you configured your Web server to support the servlet gateway (p. 102). • If you are not using a Web server, to use the dispatcher as the gateway, type the following syntax: http[s]://host_name:port/p2pd/servlet/dispatch Change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. Specify the value for the Dispatcher URI for external applications: • If your Web server is configured not to allow anonymous access, type the URI of the dispatcher, ensuring that you change the host name in the URI from localhost. • If your Web server supports chunked transfer encoding and Framework Manager is inside the firewall, type the URI of the dispatcher, ensuring that you change the host name in the URI from localhost. • In all other situations, including when the dispatcher is behind a firewall, type the same value you specified for the Gateway URI, ensuring that you change the host name in the URI from localhost. In the Explorer window, under Cryptography, click Cognos, the default cryptographic provider. Under the Certificate Authority settings property group, for the Password property, type the same password you configured on the default active Content Manager computer. From the File menu, click Save.

4. 5.

6. 7. 8.

Framework Manager is now configured to communicate with the other components of Cognos 8. You can configure a source control system.

Configure a Source Control System
To help you manage, share, and secure different versions of your metadata, you can configure Framework Manager to use a source control system. You must already have one of the following source control system clients set up on the same computer as Framework Manager: • Component Software Concurrent Versions System • Visual Source Safe For more information about installing and setting up source control systems, see Repository Control in the Framework Manager User Guide.

Steps
1. Start Cognos Configuration. 2. In the Explorer window, under Environment, right-click Source Control Systems and click New resource, Source Control System. Source Control System is available on Windows computers that have Framework Manager installed and on Windows or UNIX computers that have Application Tier Components installed. 3. In the Name box, type a name for your source control system. 4. In the Type box, select a source control system from the list. 5. Click OK. 6. In the Properties window, for the Source control system executable file (.exe) location property, specify the file location and name of the .exe file. • For VSS, type file_location\ss.exe Installation and Configuration Guide 85

Start the Cognos 8 service. Before upgrading a project. you can change a port. other Cognos 8 components must be installed and configured. • Check out the project you want to upgrade using the third-party repository control. Steps 1. choose a location: • To save the backup model in the default location. 5. you must copy the model to a folder on a local machine. Click OK. click Open Existing Project. if your project links to a segment in a different project. see the Framework Manager User Guide. see the Framework Manager User Guide.exe where version is the CVS version number. Framework Manager will not open the project. and Metric Designer must be installed. you must configure environment properties for Metric Designer computers. If the model schema version is older than the currently supported version. • Upgrade Framework Manager Projects You can upgrade the metadata in an earlier version of a Framework Manager project by opening the project in the latest version of Framework Manager.Chapter 7: Configuring Cognos 8 For CVS. In the Start page. Start Framework Manager. For more information. you may be prompted to specify a location for a backup of the project. For more information. 6. no configuration is required. and then copy the project back to the original LAN location. we recommend that you do the following: • Update any dependent projects or segments that you referenced in your project. From your local machine. type file_location\cvs-version. click Yes and browse to the location. You must now republish your packages to a current version of the Application Tier Components server. you can upgrade existing projects in the new version of Framework Manager. If you are prompted for a location to store the backup. configure SSL protocol. For example. configure cryptographic settings. For more information. Configure Metric Designer If you install Metric Designer on the same computer as other Cognos 8 components. click Save. If you install Metric Designer on a different computer from other Cognos 8 components. you must upgrade the segment first. 2. 7. Before you configure Metric Designer. if required. You can test your installation and configuration. see their documentation. For information about using different Cognos 8 components.cpf file. click No. see the third-party vendor documentation. start Cognos Connection and select Quick Tour. or change the Gateway URI to use an alternate gateway. upgrade the model. You can also change default settings. From the File menu. 86 . If you click Cancel. If you upgraded from an older version of Framework Manager. Click Open. 7. • To upgrade a model that is located on a LAN. For example. Locate the project folder you want to open. 3. 4. • To specify a different location. A message appears indicating that the project was created using an older version of Framework Manager and asking if you want to specify a location for the backup file. and click the . To take a tour of Cognos 8. You can then upgrade the parent project.

0 module mod2_cognos.sl Apache 2.dll mod2_cognos. In addition. ensure that you configure it first (p.0 or later. To upgrade existing projects. set this property to the value of the Dispatcher URI. ensuring that you change the host name in the URI from localhost. • To use ISAPI. in the Gateway URI box. you must configure it to communicate with the computers where the gateway and Content Manager are installed. replace cognos. start Cognos Configuration. type the URI of the dispatcher. Installation and Configuration Guide 87 . Steps 1. Installations with a Firewall You can configure Metric Designer to access the Cognos 8 server components through the dispatcher or through the gateway. If you are using an Apache Web server. Metric Designer must have access to a Web server that supports chunked transfer encoding and is outside the firewall.sl 4.3 module mod_cognos. you must open them in the new version of Metric Designer and redefine the data source connections and other references. If the computer where you installed Metric Designer does not have access to the Cognos 8 dispatcher because of a firewall.so mod_cognos. In the Explorer window.so mod2_cognos.Chapter 7: Configuring Cognos 8 If you upgraded from Metrics Manager version 2. and the Cognos 8 service is running. specify the appropriate value for the Dispatcher URI for external applications property. you can use the same extracts and projects that you used with the older version. type the URI of the dispatcher.dll. this property can be set to the same value as the Gateway URI. Specify the value for the Dispatcher URI for external applications: • If your Web server is configured not to allow anonymous access. If you are using a firewall. • To use apache_mod. type the following syntax: http://host_name:port/cognos8/cgi-bin/module where module is as follows: Operating system Windows Solaris and AIX HPUX Apache 1.dll mod_cognos.cgi with cognosisapi. This ensures that the certificate authority service issues a certificate to the Metric Designer computer. In most cases. In the Properties window. click Environment. you must configure Metric Designer to access Cognos 8 through the gateway. 2. 5. You must first install and configure Content Manager and then start the Cognos 8 service on at least one Content Manager computer before you configure Metric Designer. Configure Environment Properties for Metric Designer Computers If you install Metric Designer on a different computer from other Cognos 8 components. We recommend that you install and configure other Cognos 8 components before you configure Metric Designer. In the Properties window. • If your Web server supports chunked transfer encoding and Metric Designer is inside the firewall. In this type of installation. 101). Metric Designer and the gateway must be outside the firewall and the dispatcher is inside the firewall. Before you configure Metric Designer. On the computer where you installed Metric Designer. ensuring that you change the host name in the URI from localhost. ensure that the Web server is configured and running. 3. type the appropriate value: • Change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name.

you can test it by starting the application and creating a project. If you are prompted for a location to store the backup. Start the Cognos 8 service. 7. to start the Cognos 8 process automatically. 2. 88 . upgrade the model. Then you can test the installation by starting the Cognos 8 service and then opening Cognos Connection. For more information. click No. 5. Steps 1. ensuring that you change the host name in the URI from localhost. Locate the project folder you want to open. choose a location: • To save the backup model in the default location. and then copy the project back to the original LAN location. • To specify a different location. the Cognos 8 service is configured to start automatically by default. You can create a metric package only if Metric Studio is installed and configured properly. click Open a Project. Metric Designer will not open the project. a message appears indicating that configuration files were detected and upgraded to the new version. Before upgrading a project with a model that is located on a LAN. including when the dispatcher is behind a firewall. you have already tested your installation and configuration. If you installed Metric Studio and you have created a package. Metric Designer is now configured to communicate with other Cognos 8 components. you must copy the model to a folder on a local machine. In the Start page. you must configure the process as a daemon. You must install and configure both the server components of Cognos 8 and Framework Manager before you can use Cognos 8 for reporting. 8.Chapter 7: Configuring Cognos 8 In all other situations. Click Open. Ensure that you save your configuration. you are prompted to choose an existing metric package or data source connection to be used. click Yes and browse to the location. 2. Steps for Cognos 8 1. Note: Cognos 8 cannot access any reporting data unless the data is first packaged in and published from Framework Manager. Start Metric Designer. You are prompted to back up the project if the model schema version is older than the currently supported version. 6. you must start the Cognos 8 service. 6. 3. If you are upgrading. Start Cognos Configuration. On Windows. otherwise you will not be able to start the Cognos 8 service. A message appears indicating that the project was created using an earlier version of Metrics Designer and asking if you want to specify a location for the backup file. • Upgrade Metrics Designer Projects You can upgrade the metadata in an earlier version of a Metrics Designer project by opening the project in the current version of Metric Designer. From your local machine. click Save. If you installed Framework Manager or Metric Designer. Before you can use Framework Manager or Metric Designer. see your operating system documentation. 4. Click OK. From the File menu. Test the Installation and Configuration You can test your configuration settings by running the test feature before you start the Cognos 8 service. If you click Cancel. and click the .cpf file. On UNIX and Linux. If the metric package or data source connection associated with the project no longer exists. type the same value you specified for the Gateway URI.

your Cognos 8 installation is working. select the service node in the Explorer window and then click Start from the Actions menu. Tip: If Test is not available for selection. such as a port is being used by another process. Changing Default Configuration Settings When you install Cognos 8 components. 2. To start Metric Designer. click Start. 5. from the Start menu. the installation uses default configuration settings. Cognos Configuration checks the CSK availability. If you want to start a particular service. and the mail server. and tests the connections to the content store. Framework Manager. If you see the Welcome page of Cognos Connection. click Programs. 6. If you see the Welcome page of Framework Manager. Steps for Metric Designer 1. If you have any reason not to use these default values. click Local Configuration. click Programs. If you change the value of a property. use Cognos Configuration to change the value. You may be prompted to upgrade if the model schema version is older than the currently supported version. in the Explorer window. 2. From the Actions menu. Do not start the service until all tests pass. your installation is working. Start the Cognos 8 service. Open Cognos Connection by typing one the following. If any test fails. Start the Cognos 8 service. Installation and Configuration Guide 89 . tests the namespace configuration. If you see the Welcome page of Metric Designer. click Test. This action starts all installed services that are not running. Steps for Framework Manager 1. Open a Web browser. Cognos 8. Metric Designer. 4. you must save the configuration and then restart the Cognos 8 service to apply the new settings to your computer. notification database. where cognos8 is the virtual directory you created when you configured the Web server. logging database. Cognos 8. your installation is working. reconfigure the affected properties and then test again. from the Start menu. • For the CGI gateway: http://host_name:port/cognos8 • For an ISAPI gateway: http://host_name:port/cognos8/isapi • For Apache Connector on Windows: http://host_name:port/cognos8/cgi-bin/mod_cognos.dll • For Apache Connector on Solaris and AIX: http://host_name:port/cognos8/cgi-bin/mod_cognos.so • For Apache Connector on HPUX: http://host_name:port/cognos8/cgi-bin/mod_cognos.Chapter 7: Configuring Cognos 8 3. From the Actions menu. It may take a few minutes for the Cognos 8 service to start.sl • For a gateway servlet: http://host_name:port/context_root/servlet/ Gateway It may take a few minutes for the Web page to open. To start Framework Manager. 7.

1 domain name. For Metric Studio. host name or IP port context root p2pd alias path servlet/ dispatch 90 . or a fully qualified 192. 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. 9300 or 80 Specifies the port on which the host system listens for requests. you can install and configure Metric Designer. either Hyper Text Transfer Protocol or Hyper Text Transfer Protocol (Secure). localhost Specifies the identity of the host on the network. Change a URI You can change certain elements in a URI depending on your environment. You can or use an IP address. The default port for a Web server is 80. you can install and configure Framework Manager. a computer name. The default port for Tomcat is 9300. For Cognos 8. ensure that you configured all computers where you installed Content Manager before you change default configuration settings on other Cognos computers. such as product and content locales. Used by the application server to route a request to the correct component within a Web application. configure an authentication provider. and cookie settings • configure fonts • change the default font for reports • change the location of map charts for Report Studio After you change the default behavior of Cognos 8 to better suit your Cognos environment. For example you can • change a URI • configure cryptographic settings • configure SSL protocol • configure Cognos 8 components to use Cognos Application Firewall • configure temporary file properties • specify where to send log messages • change the gateway • configure the gateway to use a namespace • enable and disable services • specify the amount of resources the Cognos 8 service uses • change global settings.Chapter 7: Configuring Cognos 8 For distributed installations. or dispatcher URI protocol://host_name_or_IP:port/context_root/alias_path • For a Gateway URI or a Web content URI protocol://host_name_or_IP:port/virtual_directory/gateway_application OR protocol://host_name_or_IP:port/context_root/alias_path Element protocol Examples Description http or https Specifies the protocol used to request and transmit information. A Cognos URI contains the following elements: • For a Content Manager URI. or test the installation and configuration.0. email encoding. you can configure Portal Services.168. Dispatcher URI for external applications.

it is not necessary to change this from the default value of p2pd. Steps 1.cgi. or the application server to route requests to the appropriate Java application. Start Cognos Configuration.cgi Description Used by the Web server to map a virtual directory or alias to a physical location. with the exception that the Servlet Gateway application can have a unique value. then the default gateway application would be cognos. Protocol This element specifies whether standard (http) or secure (https) communication is used when transmitting or receiving information. 93). 2. click Environment. Virtual Directory This element must indicate the virtual directory alias exactly as it is defined in your Web server configuration.cgi. In a distributed Cognos 8 environment. Alias Path This portion of the URI must not be modified or Cognos 8 components will not function correctly. in the default Gateway URI of http://localhost:80/cognos8/cgi-bin/cognos. the context root for all application deployments must be the same. if you are accessing Cognos 8 components using a Common Gateway Interface (CGI). Select the element and type the new information. Context Root The context root element is used by the Web server. fully qualified domain name. or IP address in a distributed installation. under Environment. You may use an IP address if name resolution is not possible. ensure that host names can be resolved to IP addresses by all servers in the environment. click the Value box next to the URI property that you want to change. Host Name or IP The host name is the name of the server as it is identified on the network. In the Properties window. For more information about secure communication. For example. In the Explorer window click the appropriate group or component: • To change an element for the dispatcher. 4. The value entered must match the value in your Web server. Tomcat. 3. see "Configuring the SSL Protocol" (p. For example.Chapter 7: Configuring Cognos 8 Element virtual directory gateway application Examples cognos8/ cognos. • To change an element for the local log server. the virtual directory is cognos8/cgi-bin. If you use Tomcat. Specifies the name of the Cognos gateway application that is used. The context root can only be changed if you are using a third-party application server. Installation and Configuration Guide 91 . Gateway Application The Gateway URI must include a reference to the gateway application. In a mixed environment of UNIX and Windows servers. You must change the localhost element of a URI to a server name. or application server configuration. Port This element specifies the port on which the host system has a socket open to listen for requests. The value is defined and used internally by Cognos 8. Tomcat. click Logging.

By default. under SSL Settings. If you change the cryptographic keys in Content Manager. In addition. You must then save the configuration on each computer so that they obtain the new cryptographic keys from Content Manager. you can test it on the gateway computer. set Create symmetric key store to True. • common symmetric key store (CSK) properties The CSK is used by Cognos 8 to encrypt and decrypt data. If you delete the default cryptographic provider. In the Properties window. click Save. 92 . You can configure cryptographic and cryptographic provider settings. or SDK services on this system. Configure Cryptographic Settings Cognos 8 components require a cryptographic provider. For more information. such as the Enhanced Encryption Module for OpenSSL or the Enhanced Encryption Module for Entrust. 2. The Common symmetric key store location property is ignored. Content Manager. Because the change affects all the URIs that are based on the local dispatcher. including the following: • advanced algorithms These include signing and digest algorithms. you must configure another provider to replace it. After configuring a cryptographic provider. ensure that you specify the new port number when you configure remote computers that use the dispatcher. including standby Content Manager. you must set the Create symmetric key store property to True on the default active Content Manager computer. In the Explorer window. click Cryptography. the cryptographic provider uses keys up to 56 bits in length for data encryption and secure sockets layer (SSL) protocol. All other Content Manager computers must have this property set to False. • If you want the computers at both ends of a transmission to prove their identity. • 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. all Cognos 8 components in a distributed installation must be configured with the same cryptographic provider settings. change Store symmetric key locally to False. On all other computers. Cognos 8 requires a cryptographic provider. Start Cognos Configuration. see the Enhanced Encryption Module for OpenSSL Installation and Configuration Guide or the Enhanced Encryption Module for Entrust Installation and Configuration Guide. you must change Create symmetric key store to False. 5. You can configure other cryptographic providers which use key sizes greater than 56 bits. otherwise they will not run. you must change the URIs of all local components. the Cognos computers obtain the cryptographic keys from Content Manager. under CSK settings. under CSK settings. • encryption key store properties The encryption key pair includes the private key used to encrypt data and the public key used to decrypt data. • On computers that do not contain Content Manager. From the File menu. Steps for Cryptographic Settings 1. 3. change the default values by clicking the Value box and then selecting the appropriate value: • Only on the default active Content Manager computer. the key is retrieved from Content Manager when required. available from Cognos. you must delete the cryptographic keys on the other Cognos computers. Important: In a distributed installation. When Store symmetric key locally is False. Tip: If you change the dispatcher port in the dispatcher URI.Chapter 7: Configuring Cognos 8 Tip: To change the port used by the local dispatcher. such as by changing application servers or reinstalling Content Manager. In an installation where you have one or more standby Content Manager computers. if you do not want to store the CSKs locally. change the value of the Internal dispatcher URI property. under Security. change Use mutual authentication to True.

96). • If you want to change the location of the encryption keys. 3. • If you want to use a third-party certificate authority. click Save. under Security. see "Configuring Cognos 8 Components to Use a Third-party Certificate Authority" (p. 5. Cognos components on the local computer communicate using this protocol. ❑ Select and rank Cipher Suites to be used in an SSL connection. In addition. Start Cognos Configuration. Configuring the SSL Protocol The Secure Sockets Layer (SSL) protocol is used to secure communication between Cognos components installed on the same computer or on different computers. select another value. Test the cryptographic provider on a gateway computer only. if required (p. In the Explorer window. In the Explorer window. Configure SSL for Cognos 8 You can configure Cognos components to use the SSL protocol for • internal connections only • external connections only • internal and external connections • connections to local and remote log servers If you configure SSL only for internal connections. After you configure the cryptographic provider. You must ensure that SSL is set up for the other servers and then you must set up a shared trust between Cognos components and the other servers. right-click Cryptography and click Test. Therefore. Steps for Cryptographic Provider Settings 1. 4. passwords in your configuration and any data you create are encrypted. you must now configure Cognos 8 components to use the CA. click Save. Cognos 8 components check the availability of the symmetric key. for the Digest algorithm property. If you use a third-party Certificate Authority (CA) server. http requests. change the Signing key store location property to the new location. 160). 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 Certificate Authority settings. After configuring the SSL protocol. From the File menu. Cryptography. Installation and Configuration Guide 93 . which control the quality of protection used in the SSL connection. This property must be true to ensure all transmissions are encrypted. The dispatcher listens for secure connections on a different port than for remote. 2. For more information. ❑ Set up shared trust between Cognos components and other servers. under Signing key settings. To configure SSL protocol. • If you want to change the location of the signing keys. • If you want to change the digest algorithm. under Encryption key settings. do the following: ❑ Configure SSL for Cognos components (p. click Cognos. From the File menu. you can select and rank cipher suites. change Encryption key store location to the new location.Chapter 7: Configuring Cognos 8 We recommend that you do not change the Use confidentiality setting. you may want to set up SSL connections between Cognos components and other servers. you must configure two dispatcher URIs. change Use third party CA to True. 93).

1 or SSL Coyote HTTP/1. Also. located in the c8_location/tomcat4. the internal dispatcher port is accessible only to the components on the local computer. you can restart the service. both the non-SSL Coyote HTTP/1. only one HTTP/1. Single Computer Installations In single computer installations.1.1 and SSL Coyote HTTP/1.1 connector is required in the Tomcat configuration file. Similarly. the dispatcher can use the same port for internal and external connections. After you save the configuration with SSL settings. You must do this because you cannot set up the SSL protocol before trust has been established.1 connectors are enabled in the server. That means that you must first configure the computer where the default active Content Manager is installed and then start the services on this computer before you configure other computers or start services on other computers. you can configure the SSL protocol on other Cognos computers in your environment. you ensure that the certificate authority service on the default active Content Manager computer can issue certificates to other computers in the Cognos environment.xml file.1 connector. If you configure SSL for all connections. After you configure all computers in the distributed installation to use the default. If the internal dispatcher URI is prefixed with http but the external dispatcher URI is prefixed with https. ensure that you follow the required order of configuring computers in a distributed environment. the dispatcher can use the same port for all communications. if you do not use SSL for local or remote communication. You must configure the dispatcher to listen for secure. You must also update the Content Manager URIs. If the internal and external dispatcher URIs use different protocol or ports. Dispatcher URI for external applications. By first configuring the default active Content Manager computer and starting the services.xml file. 94 . Distributed Installations In distributed installations. the server. After you test your installation. or vice versa.Chapter 7: Configuring Cognos 8 If you configure SSL only for external connections. After you do this. non-secure protocol. When you configure Cognos 8 to use the SSL protocol. if required. remote requests on a different port than local. ensure that you first configure the default active Content Manager computer to use the protocol and start the services on the default active Content Manager computer. we recommend that you test your installation to ensure that Cognos components are working properly. you must first configure all Cognos computers to use the non-secure (http) protocol before you configure Cognos components to use the SSL protocol. and Gateway URI to use SSL. if you are using the Cognos certificate authority service. The internal dispatcher URI must also specify localhost. communications from remote Cognos components to the local computer use the SSL protocol. The port number in the dispatcher URIs is used to update the port number in the appropriate non-SSL Coyote HTTP/1. you can configure the SSL protocol. 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. if you are running Cognos 8 without SSL.27/conf directory. HTTP requests. Tomcat Connectors When the internal and external dispatcher URIs are the same. you must stop the service before adding SSL to your configuration.

type the same URI for both the Internal dispatcher URI and External dispatcher URI properties. the Internal dispatcher URI property must also specify localhost. From the File menu. • For external connections only. 6. you must reconfigure the default active Content Manager computer to use the non-secure protocol. the Internal dispatcher URI property must also specify localhost. You must then save your configuration on the new computer so that the computer can get the certificate from the active Content Manager computer. In the Properties window. • For all connections. The ports in the two dispatcher URIs must be different. Note: You do not have to use port 9343. Type https and a secure port. click Security. type https in all the URIs. including the Content Manager URIs. type https and a port for SSL communication. In the Explorer window. • For internal connections only. If you use Tomcat. Installation and Configuration Guide 95 . you can re-enable SSL on the default active Content Manager computer and then configure the new component to use SSL. 7. To use SSL protocol. After this occurs. You can choose any available port. type https and a secure port. The ports in the two dispatcher URIs must be different. Configure the SSL protocol for the other environment URIs. type the appropriate values for the Internal dispatcher URI and External dispatcher URI values: • To configure SSL for internal connections only. Add a Component to a Computer You can later add a component to the same location as other Cognos components. In the Explorer window. you do not have to disable the SSL protocol on the default active Content Manager computer before configuring the new component to use SSL. The computer has a certificate and the certificate is in a known location. you must configure the new computer to use the non-secure protocol. Cognos. If the existing components use SSL. click Save. for the External dispatcher URI property. 4. Cryptography.Chapter 7: Configuring Cognos 8 Add a Computer to an Installation If you later add a computer to your distributed environment and SSL is enabled for external connections. 3. This ensures that the certificate authority service that is installed on the default active Content Manager computer can issue a certificate to the new computer. and Gateway URI. If the existing components currently use the SSL protocol. Another certificate is issued for this new installation when you save your new configuration. However. 5. for the Internal dispatcher URI property. If you use Tomcat. the Dispatcher URI for external applications. you must specify passwords for the Cognos 8 encryption key stores. you can re-enable SSL on the default active Content Manager computer and then configure the new component to use SSL. type https in the URIs that do not contain localhost. Steps 1. 2. click Environment. After the default active Content Manager computer is configured and running. There are more settings under Security. For the Internal dispatcher URI property. type http and use the default or another available port. Start Cognos Configuration. you must disable the SSL protocol on the default active Content Manager computer before configuring the new component to use SSL. After this occurs. such as 9343. Then. type http and use the default or another available port. you can also add a component to a different location on the same computer as other Cognos components. Cryptography. you start the services on the default active Content Manager computer. • To configure SSL for external connections only. For the External dispatcher URI property. type https in the URIs that contain localhost. the default SSL port. • To configure SSL for all connections.

or preference. type ThirdPartyCertificateTool. 96 . click the check box and then click Remove. To move a cipher suite up or down in the Current values list. see the documentation for your server.sh -E -T -r destination_file -k c8_location/configuration/signkeypair/jCAKeystore -p password On Windows. It contains cryptographic. The selected cipher suites are presented in priority sequence for the client and server sides of the negotiation.509 format. you must also copy the certificate from your certificate authority to the trust store for Cognos servers. 3. You can eliminate cipher suites that do not meet your requirements and then assign a priority. From the File menu. 2. the browsers automatically prompt users to update their trust stores. To remove a cipher suite from the Current values list. Start Cognos Configuration. Extract the Cognos certificate by typing the following command: On UNIX or Linux. hash. Click OK. you do not have to set up shared trust between Cognos server and other servers. The item at the top of the list has the highest priority. click Cryptography. Copy the certificate from your certificate authority to a secure location on the Cognos server. authentication. Steps to Copy the Cognos Certificate to Another Server 1. to the remaining cipher suites. you must add the Cognos certificate to the trust store on the other servers. click the check box and then click the up or down arrows. 4.Chapter 7: Configuring Cognos 8 Select and Rank Cipher Suites for SSL An SSL connection begins with a negotiation in which the client and server present a list of supported cipher suites in a priority sequence. 7. Steps to Copy the CA Certificate to Cognos Servers 1. and key exchange algorithms. Note: If you use browsers to connect to Cognos components. Cognos provides a list of supported cipher suites for SSL. Set Up Shared Trust Between Cognos Servers and Other Servers If you want to use the default Cognos certificate authority and you want to use SSL for connections from other servers to Cognos servers. click the check box in the Available values list and then click Add. Ensure that the CA certificate is in Base-64 encoded X. A cipher suite provides the quality of protection for the connection. For information on updating the server trust store. Cognos. 2. 9. 6. 8. In the Properties window. Click the edit button. If you want the connection between Cognos servers and the other server to be mutually authenticated. type ThirdPartyCertificateTool. 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. The SSL protocol selects the highest priority suite that the client and the server both support.bat -E -T -r destination_file -k c8_location/configuration/signkeypair/jCAKeystore -p password 3. Steps 1. If you have configured Cognos components to use a third-party certificate authority (CA). click Save. To move a cipher suite to the Current values list. In the Explorer window. Import the certificate to the trust store on your server. Go to the c8_location/bin directory. 5.

click the value and then click the edit button. • In the Value . under Security. which contains rejected requests only. Cognos Application Firewall protects the Cognos Web products from malicious data. click and then type the host or domain name. the file is named caf. see the Architecture and Planning Guide. Import the CA certificate by typing the following command: On UNIX or Linux. In the Properties window. add any additional characters that are prohibited by SiteMinder. 2. If you configure a destination for log messages (p. • For the Third party XSS characters property.log file. unexpected behavior and product errors may result. this should not be done under normal circumstances. For more information about Cognos Application Firewall. Steps 1. which gives administrators control over which groups or users can view detailed error messages. Cognos Application Firewall also has a Secure Error feature. log messages are stored in the c8_location/logs/cogserver. The CAF enabled property must have the same setting on all Cognos 8 computers. The most common forms of malicious data are buffer overflows and cross-site scripting attacks (XSS links). start Cognos Configuration. If firewall validation fails. 4. Installation and Configuration Guide 97 .Valid domains or hosts dialog box. On a gateway-only installation. set the appropriate values. If it is disabled on some computers and enabled on other computers. • In the blank row of the table. The default characters are >. type ThirdPartyCertificateTool. • Repeat the previous two bulleted steps for each name to be added. On each computer identified as an external dispatcher. for the CAF enabled property. Cognos Application Firewall may modify these HTTP and XML requests. Disabling the Cognos Application Firewall will remove this protection. Cognos Application Firewall is enabled.log. 98). You can track firewall activity by checking the log file. 5.bat -T -i -r CA_certificate_file -k c8_location/configuration/signkeypair/jCAKeystore -p password Configure Cognos 8 Components to Use Cognos Application Firewall Cognos Application Firewall analyzes and validates HTTP and XML requests before they are processed by Cognos servers. type ThirdPartyCertificateTool. By default. You can also add host and domain names to the Cognos list of validated names. • Click OK. and ’. For more information. add the hostnames of the Cognos Series 7 gateway servers to the list. you can check the log file to find where the failure occurred. Important: The Cognos Application Firewall is an essential component of Cognos security. In the Properties window. click Add. <. Add host and domain names to the Cognos list of validated names: • For the Valid domains and hosts property. By default. helping to provide protection against penetration vulnerabilities. In the Explorer window. Cognos Application Firewall log messages are sent to the specified destination. either through script injection in valid pages or redirection to another Web site. click Cognos Application Firewall. to use third-party cross site scripting (XSS): • For the Is third party XSS checking enabled property. 3. Tip: If you are drilling through from Cognos Series 7 to reports on Cognos 8.Chapter 7: Configuring Cognos 8 2. change the value to True. You can change settings for XSS checking. therefore. see the Administration and Security Guide.sh -T -i -r CA_certificate_file -k c8_location/configuration/signkeypair/jCAKeystore -p password On Windows.

You can add names manually to the list of valid domains and hosts. By default. full control privileges • on UNIX or Linux. the following types: • a remote log server • a file • a database A Remote Log Server In a distributed installation. 6. We recommend that you first set up read-only access for all users to the c8_location directory. 2. You can configure the log server to send log messages to an alternative file. A Database The log server can also send messages to a database on the same or another computer. You can then configure the common log server to send the log messages to a flat file or database on the same or another computer. Adding names is useful when you need to redirect requests to non-Cognos computers using the Back or Cancel functions within the web browser. Cognos Application Firewall considers domain names derived from the environment configuration properties to be safe domain names. For information about log messages. you can configure the log servers to send log messages to a single log server. 3. 4. such as the UNIX or Linux syslog or the Windows NT Event log. When the remote log server becomes available. which include. set the Encrypt temporary files property to True. Steps Start Cognos Configuration. see the Architecture and Planning Guide.Chapter 7: Configuring Cognos 8 Cognos Application Firewall validates domain and host names to protect URLs that are created. By default. In the Explorer window. A local log server is automatically installed when you install Content Manager or the Application Tier Components.log file located in the c8_location/logs directory. 98 . an automatic recovery process moves all log information to the remote log server and deletes the local log files. and are not readable like regular log files. for the Temporary files location property. Configure Temporary File Properties You can change the location where Cognos 8 components store recently viewed reports. log messages are redirected to recovery files on the local computer in the c8_location/logs/recovery/remote directory. The log server can send log messages to one or more destinations. 5. click Environment. Configuring Log Messages You can specify where the local log server sends log messages. If the remote log server becomes unavailable. If you require the content of temporary files to be encrypted. specify the new location. A File The log server is configured by default to send log messages to the crnserver. Ensure that the user account under which Cognos 8 components run have the appropriate privileges to the temporary files location. which acts as a common log server. These recovery files have timestamp information in their file names. but are not limited to. Cognos 8 components store temporary files in the c8_location/temp directory and the files are not encrypted. read-write privileges 1. Save the configuration. In the Properties window. and you can choose to encrypt their content. For example: • on Windows.

On Windows. Important: For DB2. however. Rename the db2java. Rename the classes12. Note: If the logging database and log server are on the same computer. or Sybase as the database server. 4. Configuring Log Messages To configure log messages: ❑ Create the logging database using the same procedure as to create the content store database (p. • For version 8. If you use an Oracle or Sybase database. ❑ Specify the log messages destination. This copies the JDBC2 driver. The only additional step is to ensure that the Microsoft SQL Server uses TCP/IP connectivity. On the computer where Oracle is installed. you must create an additional regular user tablespace with a page size of 8k for Cognos 8 components to create the logging database. If you use a DB2 database. go to the DB2_installation/java12 directory.zip file to the c8_location/webapps/p2pd/WEB-INF/lib directory.2. go to DB2_installation\java12 directory and run the usejdbc2. if required. Steps for Oracle 1. Copy the classes12. If you are using the same type of database for the log messages as you use for the content store. 3. You must. go to the ORACLE_HOME/jdbc/lib directory. Install the DB2 client software on the computer where Content Manager or a Application Tier Components are installed. you must set up the JDBC driver. You can test the connection to the logging database before you restart the Cognos 8 service. db2java. you do not have to set up a JDBC driver on the Content Manager computers. After you configure Cognos 8 components to send messages to a logging database.2. Cognos 8 components create the required tables and table fields.0 driver. Go to the appropriate directory to copy the JDBC2 driver: • For version 7. and restart the Cognos 8 service. If the logging database is on a different computer from the log server. • On UNIX or Linux. additional steps are required. 2. 2. run the DB2 Client Configuration Assistant.jar. ❑ Set up the database client. the logging database name is automatically used to create an alias. use the DB2 command line interface.zip file to classes12. Set Up the Database Client for a Logging Database After you create a database for your log messages. 53). Steps for DB2 1. stop the DB2 services and the HTML Search Server. Copy the db2java. On Windows. 5. • For version 7. on Windows. on UNIX. 3. to the DB2_installation/java directory. If you use a Microsoft SQL Server database. you must set up the database client software and the JDBC 2.zip file to db2java. if you use Oracle.jar file is installed to the appropriate location by default. configure a database alias to the logging database: • On Windows. DB2.zip file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager or Application Tier Components are installed. set up a JDBC driver on the Application Tier Components computers. Installation and Configuration Guide 99 .bat script. the JSQLConnect. go to the DB2_installation/java directory. 6.Chapter 7: Configuring Cognos 8 The logging database has the same configuration and user account requirements as the content store database. restart the DB2 services and the HTML Search Server. 7.zip.jar.

On the computer where you installed Content Manager or the Application Tier Components. 13. start Cognos Configuration.sql 2.5. 11. 9. 10. Specify the Log Messages Destination You can configure a type of destination for the log messages.Chapter 7: Configuring Cognos 8 8. 4. Cognos 8. click Cognos 8 service. click Logging. 53) • set up the database client 2. set the Enable SSL property to True. • Test the connection to the new database. If the destination is a database. Go to the Sybase_location/jConnect-5_5/classes directory. 100 . Repeat this entire procedure on every computer where Content Manager or Application Tier Components are installed. • In the Name box. in the Properties window. If the destination is a database. Cognos 8 components test all of the databases. If the destination is a file or a remote log server. 12. click Save. type the name of the destination. under Environment. Steps 1. From the File menu. enable the JDBC driver using the following script: Sybase_location/jConnect-5_5/sp/sql_server12. ensure that you • created the logging database (p. Copy the jconn2. click the type of destination and then click OK. In the Explorer window. 3. In the Explorer window. click the database type. and then configure properties for the specific destination. • In the Type list. set the Enable TCP property to True. ensure that you include the DB2_installation/java12 directory in the library path environment variable and that it comes before the DB2_installation/lib directory.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager or Framework Manager is installed. 5. Destination. In the Explorer window. 3. under Environment. right-click Logging and click Test. In the Type list. Database. you must later specify the log messages destination when you configure the remote log server. type the appropriate values for the mandatory and optional properties. 9. 6. Cognos 8 components connect to the database. You can also configure more than one destination for log messages. 8. and then click OK. • If you used https in the Internal dispatcher URI. Cognos 8 components create the required tables and fields in the database that you created.2. type the appropriate values for the mandatory and optional properties. right-click Logging. click Restart. add a database resource: • In the Explorer window. in the Properties window. • In the Properties window. right-click the database. • If you want to use TCP between Cognos 8 components and the remote log server. 7. On UNIX. for version 7. From the File menu. For a remote log server. set the log server properties. and click New resource. If you configured more than one database for logging messages. under Environment. If you selected a database as the destination. Steps for Sybase 1. Repeat steps 5 to 9 for each destination to which you want the log server to send messages. In the Explorer window. In the Name box. and click New resource. type the name of the logging database that you created. In the Properties window. On the computer where Sybase is installed.

Steps 1. 4. For Apache 1. or Linux HPUX Apache 1. If the destination was a database. 6. On HPUX. Then specify the ISAPI URI. you can use Cognos 8 components to run log reports from the database.dll mod_cognos.so mod_cognos. Open the httpd.Chapter 7: Configuring Cognos 8 If the destination was a remote log server. Append the c8_location/cgi-bin directory to the appropriate environment variable: • On Solaris or Linux. For Apache 1.0.x.3.dll mod2_cognos. Before you change the gateway. LIBPATH 3.0 module mod2_cognos.0 module is required. change the cognos.so mod2_cognos. see the Administration and Security Guide.dll. in your browser.3. 5. add the following to the end of the add module list: Installation and Configuration Guide 101 . You can use one of the following gateways: • Microsoft Internet Application Programming Interface (ISAPI) for Microsoft Internet Information Services on Windows • apache_mod for Apache Web Server • servlet for an application server or Web server that supports Java There is no additional Web server configuration required to use ISAPI.3. do the following: • Ensure that the LD_PRELOAD environment variable contains /usr/lib/libcl.x and the Cognos Apache 2 module requires Apache Server 2. which controls the amount of detail and type of messages that are sent to a log file or database.3. SHLIB_PATH For Apache 2. http://host_name/cognos8/isapi.3 module mod_cognos. Configure the Gateway for Cognos Apache Web Server Module Cognos 8 provides two Apache modules. AIX. To access Cognos 8 components using ISAPI.sl Apache 2. For instructions. Changing the Gateway To improve Web server performance. in Cognos Configuration. Stop Apache Web Server. Add the following to the end of the load module list: LoadModule cognos_module "c8_location/cgi-bin/module_name" where module_name is as follows: Operating system Windows Solaris. we recommend that you first ensure that the default CGI gateway and your configuration work in your environment.cgi portion of the Gateway URI property to cognosisapi. You can also set the logging level. 7.2. 2. Go to the Apache_installation/conf directory. configure and start the remote log server. you can configure Cognos 8 to use alternate gateways that replace the default CGI program.sl On Linux. set the COG_CGIBIN_DIR environment variable to c8_location/cgi-bin. • For Apache 1. SHLIB_PATH and LD_LIBRARY_PATH • On AIX. LD_LIBRARY_PATH • On HPUX. The Cognos Apache module requires Apache Server 1.0. Then restart the Cognos 8 service on the local computer. Apache 2.conf file in an editor.

you copy Cognos security provider files to the JVM environment. 16. on Windows. For Apache 1. After ensuring that the required components are installed and operating.0. Add the following to the aliases section: ScriptAlias /cognos8/cgi-bin "c8_location/cgi-bin" Alias /cognos8 "c8_location/webcontent" Alias /cognos8/help "c8_location/webcontent/documentation" <Directory "c8_location/webcontent"> Options Indexes MultiViews </Directory> The <Directory> directive is optional. 14. 102 . enable searching for LD_LIBRARY_PATH by running the following command in the Apache_installation/bin directory: chatr +s enable +b enable httpd 15. add the following to the user directory section: <IfModule mod_cognos. For Apache 2.c> CGIBinDir "c8_location/cgi-bin" </IfModule> 13. Configure a Servlet Gateway You can configure the Servlet Gateway to run under a supported application server or Sun Java System Web Server. add the following to the user directory section: <IfModule mod_cognos. 10.cpp 8. add the following to the server status reports section: <Location /cognos8/cgi-bin/diag_filename> SetHandler cognos-handler </Location> where filename is the same as in step 6. and AIX.0. For Apache 2. on HPUX. Solaris. Note: Sun Java System Web Server was formerly named Sun ONE Web Server or iPlanet Web Server. The diag_ string is required.3. change the application server startup script (application servers only). 11. and then deploy the Cognos servlet gateway to the application server or Sun Java System Web Server. Tip: Ensure that you define the cognos8/cgi-bin alias before the cognos8 and cognos8/help aliases. To enable the gateway diagnostic page. In Cognos Configuration. configure Cognos 8.cpp> CGIBinDir "c8_location/cgi-bin" </IfModule> 12. 9. configure the Gateway URI property to use the apache_mod gateway: http://host_name:port/cognos8/cgi-bin/filename where filename matches the name that you used in step 9.Chapter 7: Configuring Cognos 8 AddModule mod_cognos. Add the following to the server status reports section: <Location /cognos8/cgi-bin/filename> SetHandler cognos-handler </Location> where filename is the same as in step 6. Save and close the file. Start Apache Web Server.

2. These files provide additional encryption and decryption routines that are not supplied as part of a default JVM installation. Copy the contents of the c8_location/bin/jre/1. Change the group ownership of the Cognos files to the cognos8 group and change the file permissions for all Cognos files to GROUP READABLE/WRITABLE/EXECUTABLE. Tip: If the application server or Sun Java System Web Server ships with a JVM. you must configure the gateway to decode cookies before you build the application file by doing the following: • Open install_location/war/gateway/web. Set the JAVA_HOME environment variable to point to the JVM used by the application server. Create one of the following directories if it does not exist in your JVM environment: For JDK. For simplicity. you can also use the application server user or Sun Java System user account to install and run Cognos components. Important: Do not overwrite any existing files. To ensure security. start Cognos Configuration: • On Windows. For Sun Java System Web Server. the default location for the JRE is install_location/bin/https/jdk. This group must contain the user that starts the application server or Sun Java System server and the user that owns the Cognos files. 3.Chapter 7: Configuring Cognos 8 The Cognos security provider files must be located in the JVM environment used by your application server or Sun Java System server. Note: For Sun Java System Web Server. 3. then the JAVA_HOME environment variable should be set to reference it. 43) on the same system as the application server or the Sun Java System Web Server • the Cognos 8 dispatcher and Content Manager components are installed and running in the environment • the application server user account or Sun Java System user account has full access permissions for the Cognos installation We recommend that you create a new UNIX or Linux group named cognos8. ensure that • the application server or Sun Java System Web Server is installed and operational on each computer where the servlet gateway is to be installed • Cognos 8 Gateway components are installed (p. JVM_version/lib/ext Some JVM distributions do not ship with either of these directories.bat in a command window or select Cognos Configuration from the Start menu. 2. encryption files must be loaded by the JVM using the java extensions directory. Before you set up the Cognos servlet gateway.3. Backup the JVM_version/jre/lib/ext directory if it exists. Steps to Copy Cognos Security Provider Files 1. type cogconfig.1/lib/ext directory to the JVM_version/jre/lib/ext directory for the JVM environment. From the c8_location/bin directory. Installation and Configuration Guide 103 .--> <param-name>urldecodeCookies</param-name> <!--"true" or "false" --> <param-value>true</param-value> </init-param> • Save the file. <init-param> <!--Should the Gateway URL decode incoming cookies? Use ’true’ if you’re running Java System or iPlanet or Sun ONE Web Server and ’false’ otherwise. Steps to Configure Cognos 8 1.xml in an xml or text editor and enable the urldecode option by changing the parameter value from false to true. JVM_version/jre/lib/ext For JRE. Cognos Configuration uses this variable to locate the JVM used by the applications server or Sun Java System Web Server and the security provider files supplied by Cognos.

type cogconfig. Start the associated administrative console. To create the application file to deploy to the application server or Sun Java System Web Server. 104 . click Build Application Files. 4. you must now change the application server startup script (p. you can configure each Web server to use a different namespace. 6.war file by using the following syntax: wdeploy deploy -u context_root -i webserverinstance -v vs_id path/ServletGateway. For example. from the Actions menu. Start Sun Java System Web Server. Click the Apply link in the administrative console. expand Environment. A maximum heap memory setting of between 256MB and 512MB is a suggested starting value that you can change to suit your environment. start Cognos Configuration. Add the c8_location/bin path to the Native Lib Path Prefix environment variable located under JVM Path Settings. 5. see the documentation for Sun Java System Web Application Server. 7. On the computer where the gateway is located. For Sun Java System Web Server. 9. see "Change a URI" (p. Tip: The default context root is /ServletGateway 6. If you are using an application server. In the Explorer window of Cognos Configuration. Deploy the ServletGateway. In the Properties window. The changes are applied and the server is restarted. enter the gateway URI. Users logged onto the Web server where the gateway is located are not prompted to choose an authentication source. change the Dispatcher URIs for Gateway property to use the port number and host name or IP address of the server where the dispatcher component is installed.sh If you have existing incompatible encryption keys.war For more information. 8. Save the configuration. The Build Application Wizard opens and allows you to select the type of application to build and the context root to use to access the application. you can configure the gateway to connect to one namespace. select a WAR file on the second page of the wizard. New cryptographic keys are created using the JVM that is defined by the JAVA_HOME variable. 4. Create a new server instance into which the Cognos 8 application can be deployed. To access Cognos 8 components using the servlet gateway. Steps 1. Close Cognos Configuration. The default context root value for the servlet gateway is /ServletGateway. For example. 7.Chapter 7: Configuring Cognos 8 • On UNIX or Linux. under Gateway settings. 3. 2. Complete other required configuration changes such as enabling security. Open a command prompt in the following directory: Sun_Java_System_location\bin\https\httpadmin\bin 5. if you have two Web servers. Configure the Gateway to Use a Namespace If Cognos 8 components use multiple namespaces or if anonymous access is enabled and Cognos 8 components use one namespace. 150) and then configure the application server properties and deploy Cognos components (p. you will be prompted to automatically generate new ones at this time. 90). 151). http[s]:host_name:port/ServletGateway The servlet gateway URI is case-sensitive. Steps to Deploy Cognos Components for Sun Java System Web Server 1. For more information.

under Environment. In Windows. Requests are sent only to dispatchers where a given service is enabled. 3.Chapter 7: Configuring Cognos 8 2. and click New resource. type the Namespace ID of the namespace you want to use. Start Cognos Configuration. Disabling a service prevents the service from loading into memory. In the Properties window. click the Value next to the service that you want to disable or enable. In the Explorer window. click Save. 5. In the Properties window. click Environment. click True. click Cognos 8 service. The Cognos 8 service is available only on the computers where you installed Content Manager or the Application Tier Components. When disabled. • To enable the service. In the Explorer window. Configuration. Steps 1. You will see this name in the list of services running on your computer. right-click Cognos 8. 2. 4. In the Type box. The service does not run until you enable it. you can disable the presentation service on a report server computer. you can change the amount of resources that the Cognos 8 service uses by choosing a configuration template. to dedicate a computer to running and distributing reports. If you installed all components on several computers. click the configuration template to use: Installation and Configuration Guide 105 . Note: The default values for dispatcher service and presentation service are false on computers that have the Content Manager only installed. On all other types of installations. all services that run under that dispatcher are also disabled. services do not start and therefore do not consume resources. Enable and Disable Services In a distributed installation. This deletes the default configuration template for the service. all services are enabled. the default values are true. you can send certain types of requests to specific computers by enabling or disabling the installed services. Specify Resources for the Cognos 8 Service To improve performance in a distributed environment. 3. In the Explorer window. To dedicate a computer in a distributed installation to processing Metric Studio application requests. disable the Data Integration Service on the computer. 2. the name you choose is used to register the service. Type a name for the service. 3. Only dispatcher services that are enabled can process requests. By default. in the Value box next to the Gateway namespace property. under Environment. click False. 4. If you disable the dispatcher service. Click the appropriate state for the services: • To disable the service. 5. From the File menu. click Save. the Cognos 8 service is configured to use minimal memory resources to optimize startup time. Cognos 8 service. and click Delete. Start Cognos Configuration. For example. Steps 1. 4. Right-click Cognos 8 service. you can disable appropriate services on each computer to get the distributed configuration you require. From the File menu. By default.

Click Add. Repeat steps 3 to 5 for other language support that you want to add. For example. In the second column. From the Actions menu. click Save. click Small configuration. Ensure that you install the appropriate language packs to support the character sets you use. Click OK. contact your Cognos support representative. click Medium configuration. 6. Cognos 8 components ensure that all locales. 7. 3. you can remove the language from the list. click Edit Global Configuration. • If you want to maximize operating speeds and if performance is more important than fast startup time. 4. From the File menu. Click the Product Locales tab. click Large configuration. data is not affected. That means that all expanded locales conform to a language and regional code setting.Chapter 7: Configuring Cognos 8 If you previously changed the default setting and now want to reduce the startup time. Adding languages to the Cognos environment does not guarantee that your computer has a font that can display Web pages in your preferred languages. select the check box next to the Supported Locale and then click Remove. you must install the language files on all computers in your distributed installation. use a normalized form. Each computer has a default system locale and one user locale per user. 5. Steps 1. • If you want a balance between fast startup time and quick operating speeds. Important: If you change global settings on one Content Manager computer. From the File menu. 106 . Before you can add language support to the user interface. click Save. you must make the same changes on the other Content Manager computers. In the Properties window. 6. 2. edit the properties so that they are appropriate for your environment. and if your computer has more resources. Tip: To remove support. 7. memory footprint. which may come from different sources and in various formats. For more information. If you change the user interface language of the product. 8. type the language portion of a locale. if you do not require a German user interface. and resources used. On each Content Manager computer. • Global Settings You change global settings • to customize language support for the user interface • to customize currency support • to customize content locale support • to map the language used in the product user interface • to map content locales • to add fonts to your Cognos environment • to customize the default time zone • to change the encoding for email messages • to customize cookie settings By default. The user locales may be different from the default system locale. start Cognos Configuration. Customize Language Support to the User Interface Use the Product Locales table to add or remove the user interface language support.

Chapter 7: Configuring Cognos 8

Customize Currency Support
If you require additional currencies or want to remove some from the user interface, you can update the list of supported currencies in the Currencies table. By default Cognos 8 components show only a subset of supported currencies in the user interface. Currencies are identified by their ISO 4217 currency code. The complete list of supported currencies that can be added are listed in the i18n_res.xml file in the c8_location/bin/ directory. If you add a currency code that is not supported by Cognos, you must manually add it to the i18n_res.xml file in the c8_location/bin/ directory. Copy this file to each Cognos computer in your installation. Adding currencies to the Cognos environment does not guarantee that your computer has a font with the required characters to display the currency. Ensure that you install the appropriate language packs to the support currency symbols you use. For example, to display the Indian currency symbol (rupee) correctly, you must run a Japanese operating system or install a Japanese language.

Steps
On each Content Manager computer, start Cognos Configuration. From the Actions menu, click Edit Global Configuration. Click the Currencies tab. Click Add. Tip: To remove support, select the check box next to the supported item and then click Remove. 5. In the second column, type an appropriate value. The value you add must comply with ISO 4217 codes for the representation of currencies and formats. Usually the value you add is a three-letter alphabetic code. The first two characters are letters representing the ISO 3166 country code for the country the currency is from. The additional letter represents the first letter of the currency. 6. Repeat steps 3 to 5 for other types of support that you want to add. 7. From the File menu, click Save. 1. 2. 3. 4.

Customize Content Locale Support
To ensure users see reports, data or metadata in their preferred language, or specific to their region, you can add partial locales (language) or complete locales (language-region) to the Content Locales table. This way, if content is available in different languages, or in different locales, it is rendered to users based on their user locale. If a locale is not required, you can remove it from the list. You must leave at least one content locale in the list for the report server to operate. Adding incomplete locales (languages) to the Cognos environment does not guarantee that your computer has a font that can display Web pages in your preferred languages. Ensure that you install the appropriate language packs to support the character sets you use. If you view reports in Thai language, digits are not supported.

Steps
On each Content Manager computer, start Cognos Configuration. From the Actions menu, click Edit Global Configuration. Click the Content Locales tab. Click Add. Tip: To remove support, select the check box next to the supported item and then click Remove. 5. In the second column, type an appropriate value. • To add language support for report data and metadata, type a partial local (language) setting. • To add support specific to a region, type a complete locale (language-region) setting. 1. 2. 3. 4.

Installation and Configuration Guide 107

Chapter 7: Configuring Cognos 8 6. Repeat steps 3 to 5 for each additional locale that you want to support. 7. From the File menu, click Save.

Map Content Locales
Use the Content Locale Mappings table to map user locales to a complete (language-region) or partial (language) locale. You can also map a user’s preferred language to another language if content is not available in the user’s preferred language. For example, if a report or scorecard is not available in a preferred language, for example Vietnamese, but is available in French and German, you can use the Content Mappings table to map the preferred language (Vietnamese) to another language (French or German). This way, you see the report or scorecard in the mapped language. By default, the Content Locale Mappings table includes locales that do not contain the region. This allows you to use only the language portion of the locale when you specify locale settings and ensures that you always see the correct information. For example, in a multilingual database, data is usually available in different languages, such as French (fr), Spanish (es) and English (en), rather than being available in different locales, such as English Canada (en-ca), English United States (en-us), or French France (fr-fr). The following examples shows the method that Cognos 8 components use to determine which report or scorecard the user sees if the multiple language versions are available.

Example 1
A report is available in Content Manager in two locales, such as en-us (English-United States) and fr-fr (French-France), but the user locale is set to fr-ca (French-Canadian). Cognos 8 uses the locale mapping to determine which report the user sees. First, Cognos 8 checks to see if the report is available in Content Manager in the user’s locale. If it is not available in the user’s locale, Cognos 8 maps the user’s locale to a normalized locale configured on the Content Locale Mapping tab. Because the user’s locale is fr-ca, it is mapped to fr. Cognos 8 uses the mapped value to see if the report is available in fr. In this case, the report is available in en-us and fr-fr, not fr. Next, Cognos 8 maps each of the available reports to a normalized locale. Therefore, en-us becomes en and fr-fr becomes fr. Because both report and the user locale maps to fr, the user having the user locale fr-ca will see the report saved with the locale fr-fr.

Example 2
The user’s locale and the report locales all map to the same language. Cognos 8 chooses which locale to use. For example, if a user’s locale is en-ca (English-Canada) and the reports are available in en-us (English-United States) and en-gb (English-United Kingdom), Cognos 8 maps each locale to en. The user will see the report in the locale setting that Cognos 8 chooses.

Example 3
The report and the user locales do not map to a common language. Cognos 8 chooses the language. In this case, you may want to configure a mapping. For example, if a report is available in en-us (English-United States) and fr-fr (French-France), but the user locale is es-es (Spanish-Spain), Cognos 8 chooses the language.

Steps
1. 2. 3. 4. 5. On each Content Manager computer, start Cognos Configuration. From the Actions menu, click Edit Global Configuration. Click the Content Locale Mapping tab. Click Add. In the Key box, type the user locale: • To ensure all regions for a user locale see content in a specific language, type the language portion of the locale, followed by a dash (-) and an asterisk (*). For example, type fr-*

108

Chapter 7: Configuring Cognos 8 To ensure a user locale (language-region) sees content in a specific language, type the complete locale. For example, type fr-ch • To map a preferred language to another language, type the preferred language portion of the locale. For example, type zh Tip: To specify the locale to use for a range of keys, use the wildcard character (*) with the Key value and then, in the Locale Mapping box, type the locale. For example, if you want all the German keys to use the German locale, type de* in the Key box and type de in the Locale Mapping box. In the Locale Mapping box, type the language portion of the locale. User locales specified in the Key box will see content in this language. Repeat steps 3 to 5 for other mappings you want to do. Click OK. From the File menu, click Save. •

6. 7. 8. 9.

Map Product Locales
Use the Product Locale Mappings table to specify the language used in the user interface when the language specified in the user’s locale is not available. You can ensure that all regions for a locale use the same language, or that a specific, complete locale (language-region) uses a particular language. By default, the user sees the product interface in the language that matches the language setting of the user locale.

Steps
1. 2. 3. 4. 5. On each Content Manager computer, start Cognos Configuration. From the Actions menu, click Edit Global Configuration. Click the Product Locale Mappings tab. Click Add. In the Key box, type the user locale: • To ensure all regions for a locale see the user interface in a specific language, type the language portion of the locale, followed by a dash (-) and an asterisk (*). For example, type es-* • To ensure a complete locale (language-region) see the user interface in a specific language, type the complete locale. For example, type es-es • To map a preferred language to another language, type the preferred language portion of the locale. For example, type zh Tip: To specify which locale to use as the default, use the wildcard character (*) for the Key value and then, in the Locale Mapping box type the locale. In the Locale Mapping box, type the language portion of the locale. User locales specified in the Key box will see content in this language. Repeat steps 3 to 5 for other mappings you want to do. Click OK. From the File menu, click Save.

6. 7. 8. 9.

Customize the Server Time Zone
You can customize the time zone used by Content Manager by selecting a different server time zone in Cognos Configuration.

Installation and Configuration Guide 109

Chapter 7: Configuring Cognos 8 Content Manager is configured to use the time zone of your operating system by default. All scheduled activities in Cognos 8 are set using this time zone. In addition, users in Cognos Connection use this time zone if they set their preferences for the default time zone. For more information about setting user preferences in Cognos Connection, see the Administration and Security Guide.

Steps
1. 2. 3. 4. 5. Start Cognos Configuration. From the Actions menu, click Edit Global Configuration. In the Global Configuration window, click the Server tab. Click the Value column for Server time zone and select another time zone from the list. From the File menu, click Save.

Change Encoding for Email Messages
By default, Cognos 8 components use UTF-8 encoding in emails. This value sets the default encoding used by the delivery service in this instance for all email messages. You may have older email clients or send email from Cognos 8 to cell phones and PDAs that do not recognize UTF-8. If so, you can change the email encoding to a value that works on all your email clients (for example, ISO-8859-1, Shift-JIS). Each instance of Cognos 8 that has an available delivery service must be changed. The specified encoding affects only the subject, attachment names, and plain body text of the message. HTML body text and the content of the attachments remains in UTF-8 encoding. Note: The conversion from Unicode to the Japanese encoding EUC-JP and ISO-2022-JP is not fully supported by the Java runtime environment. If you select either of these two settings, the characters are not supported in the subject or body text of the email.

Steps
1. 2. 3. 4. 5. 6. Start Cognos Configuration. From the Actions menu, click Edit Global Configuration. In the Global Configuration window, click the Server tab. Click the Value column for the Email Encoding property. Scroll to the desired setting and click it. From the File menu, click Save.

Customize Cookie Settings
Based on the requirements of your Cognos environment, you may need to modify the settings that Cognos 8 components use to create cookies. You can use Cognos Configuration to customize the cookie domain, path, and secure flag. Cognos 8 components determine the cookie domain from the HTTP request submitted by the client, which is typically a Web browser. In most network configurations, HTTP requests pass through intermediaries such as proxy servers and firewalls as they travel from the browser to Cognos 8 components. Some intermediaries modify the information that Cognos 8 components use to calculate the cookie domain, and Cognos 8 components then cannot set cookies. The usual symptom of this problem is that users are repeatedly prompted to log on. To avoid this problem, configure the cookie domain. To set the correct value for the cookie domain, use the format and value that represents the widest coverage for the host. Host computer or server suffix is .com, .edu, .gov, .int, .mil, .net, or .org Format for domain computer or server name (no dots) .name.suffix (two dots) Example mycompany .mycompany.com

110

physical font. Cognos 8 components use a set of global fonts. 2. click Edit Global Configuration. 3. In the Supported Font Name box. If you want to use a new font in your reports. start Cognos Configuration.co. the browser substitutes a different font. Cognos 8 components also use fonts to render charts used in PDF and HTML reports. click the box next to the font name and then click Remove. From the Actions menu. Click OK. fonts must be available where the report or chart is rendered. Click the Fonts tab. 4. 5. Cognos 8 components substitute a different font. 1.Chapter 7: Configuring Cognos 8 Host other Format for domain . type the font name and then click OK. Because HTML reports are rendered on a browser. If a requested font is not available. Click in the Value column under Cookie Settings for each property that you want to change and specify the new value. 3. To show output correctly. which are available on all Cognos server computers. All global fonts. the fonts must be installed on the Cognos server. If a global font is not installed on all Cognos computers. From the File menu. 6. the dispatcher derives the domain from the host name of the request. you must ❑ add the font to the list of supported fonts ❑ specify the file location of the new font ❑ map the new font to the physical font name.suffix (three dots) Example . click Save.travelinfo. must be installed on all Cognos computers in your environment.nz Steps 1. Steps On each Content Manager computer. including new fonts that you add. If a requested font is not available.name2. In the case of charts and PDF reports. 2. From the Actions menu. the required fonts must be installed on the computer of each Cognos user who will read the HTML report. 4. Installation and Configuration Guide 111 . Click Add. By default. On each Content Manager computer. If you leave the Domain property blank. if required Add Fonts to the Cognos Environment You can add fonts to the list of supported fonts in your Cognos environment if you want to generate reports that use fonts that are currently not available. Click the Server tab. Tip: To remove a font from the list of supported fonts. Configuring Fonts Cognos 8 components use fonts to render PDF reports on the Cognos server.name1. click Edit Global Configuration. 5. You can also remove fonts. start Cognos Configuration. you must map the global font to an installed.

Chapter 7: Configuring Cognos 8

Specify the Location of Available Fonts
You must specify the installation location of all fonts, including fonts that you add to the list of supported fonts. By default, the list of fonts consists of fonts installed in the c8_location/bin/fonts directory of the Cognos computer. If Cognos 8 components are installed on a Windows computer, they also use the fonts installed in the Windows font directory. You specify the font location on all computers where Application Tier Components are installed.

Steps
1. On each Application Tier Components computer, start Cognos Configuration. 2. In the Explorer window, click Environment. 3. In the Properties window, for the Physical fonts locations property, specify the location of the fonts. Tip: If there are multiple font paths, separate each path by a semicolon (;). 4. From the File menu, click Save.

Map Supported Fonts to Installed Fonts
You can substitute global fonts, which are not installed on the computer, for physical fonts. For example, you add a font to the list of supported fonts that is not installed on the Cognos computer. You can specify which font to use as a substitute. You map fonts on each computer where the report server is installed. No mapping is required if you add a font to the supported font list that is installed on Cognos computers. However, you must specify the location of the font.

Steps
1. On each Application Tier Components computer, start Cognos Configuration. 2. In the Explorer window, click Environment. 3. In the Properties window, click the Value box next to the Physical fonts map property, and then click the edit button. The Value - Physical fonts map dialog box appears. 4. Click Add. Tip: To remove a font, select the check box next to the font and click Remove. 5. In the Global Font Name box, type the name of the font you added to the supported font list. 6. Click the Physical Font Name box. 7. If you know the physical font name, type it. Otherwise, click the edit button. In the Physical Font Name dialog box, click Search Now and then click a font name from the results. 8. Repeat steps 4 to 7 for each global font that requires mapping. 9. Click OK. 10. From the File menu, click Save. Now, if required, you must specify the installation location of the fonts.

Change the Default Font for PDF Reports
You can change the default font that Cognos 8 components use for PDF reports. You see this default font when you open a report. You change the default font on the computer where Content Manager is installed. After you make the change, the font becomes the default for all computers in your installation. You change the font used for PDF reports using Cognos Configuration. Ensure that the default font is installed on all computers in your Cognos installation.

Steps
1. On each Content Manager computer, start Cognos Configuration. 112

Chapter 7: Configuring Cognos 8 2. 3. 4. 5. From the Actions menu, click Edit Global Configuration. Click the Server tab. In the Default font box, type the font you want to use as the default for reports. On all Application Tier Components computers, ensure that the installation location of the default font is specified in the Physical fonts locations property (in the Explorer window, under Environment) or that the font is in the Windows font directory. 6. From the File menu, click Save.

Change the Location of Map Charts for Report Studio
Cognos 8 comes with a set of sample map charts that you can use in Report Studio. By default, the map charts are stored in the c8_location/maps directory on the Application Tier Components computer. You can change the location of the map charts by using Cognos Configuration. For more information about using map charts, see the Report Studio User Guide. For information about using custom maps from third-party sources, see the Map Manager Installation and User Guide.

Steps
1. 2. 3. 4. 5. 6. On the Application Tier Components computer, start Cognos Configuration. In the Explorer window, click Environment. In the Properties window, click the value for Map files location. Click the edit button. In the Select Folder window, navigate to the directory you want and then click Select. From the File menu, click Save.

Configuring Portal Services
Portal Services provides a set of Cognos portlets that you can use in Cognos Connection and in third-party portals. You can use the portlets to navigate, search, and view Cognos reports in your working environment. Other users can view Cognos information without needing to know how to use Cognos products. For more information, see the Administration and Security Guide. Portal Services is installed automatically with Cognos 8 components. In a distributed environment, it is included with the Application Tier Components. The installation includes the deployment files for • SAP Enterprise Portal (SAP EP) • IBM WebSphere Portal • Plumtree Portal For some deployments of Portal Services, you must modify some Portal Services property settings and prepare the Cognos environment to support the third-party portal. When used in a third-party portal, Portal Services can authenticate users in only one namespace. If Cognos 8 components are configured with more than one namespace, you must install a separate gateway for each namespace that will be used to authenticate portal users. You must configure each gateway to use the appropriate namespace (p. 104) and then configure the deployed portlets to use that gateway. After you configure the required properties, you must deploy the Cognos portlets to the third-party portal. For more information, see the Administration and Security Guide. To use Portal Services with Cognos 8 components, do the following: ❑ Specify the location of the applications.xml file, if required.

❑ Install and test the portlets on the third-party portal.
For more information, see the Administration and Security Guide. ❑ Configure security for the third-party portal environment. Installation and Configuration Guide 113

Chapter 7: Configuring Cognos 8

Specify the Location of the Applications.xml File
If you use the applications.xml file as part of a custom application portlet, all Application Tier Components computers in a distributed environment must reference the same applications.xml file. If you have multiple instances of the applications.xml file, they must be identical. Note: The steps are required only if you want to use the Extended Applications portlet, which is included with the Cognos 8 software development kit.

Steps
1. 2. 3. 4. On the computer where you installed the report server, start Cognos Configuration. In the Explorer window, under Environment, click Portal Services. In the Properties window, click the Value next to Location of ’applications.xml’. Replace localhost with a valid host name or IP address and, if necessary, replace the default port number. 5. From the File menu, click Save. You can now deploy the Cognos portlets to your portal server. For instructions, see the Administration and Security Guide.

Configuring Security for Portal Services
When using Portal Services in a third-party portal, you must enable single signon to provide seamless integration between the third-party portal and Cognos 8 components. Portal Services uses single signon to authenticate users. This means that users do not have to log on to other applications separately through the portal. You must configure a URI into Cognos 8 components for each portlet in Portal Services. If Cognos 8 components use a single namespace for authentication, all portlets can access Cognos 8 components using the main gateway URI. If Cognos 8 components use more than one namespace, the portlets must connect to a dedicated gateway. We recommend using a dedicated gateway for Portal Services. To enable security between Cognos 8 components and the third-party portal, do the following: ❑ Disable anonymous access to Cognos 8 components.

❑ Enable single signon for the third-party portal using shared secret.
If your security infrastructure requires you to use another method for single signon, use one of the following methods: • "Enable Single Signon for SAP EP with the SAP Logon Ticket" (p. 118) • "Enable Single Signon for SAP EP with User Mapping" (p. 119) • "Enable Single Signon for WebSphere Portal Using the Application Server" (p. 120) • "Enable Single Signon for Plumtree Portal Using Basic Authentication" (p. 120) • "Enable Single Signon for Plumtree Portal Using SiteMinder" (p. 121) ❑ Configure Cognos 8 components for SSL access, if required. For instructions, see the Installation and Configuration Guide.

Disable Anonymous Access to Cognos 8 Components
Portal Services uses single signon for authentication. If anonymous logon is enabled in Cognos 8 components, Portal Services logs all portal users as anonymous. You must ensure that anonymous access is disabled in Cognos 8 components for single signon in Portal Services to be successful. However, you can test the Portal Services connections using anonymous logon to ensure that the portlets are working in the third-party portal. If Portal Services fails to authenticate a user, the user receives an error message at the third-party portal.

Steps
1. Start Cognos Configuration.

114

Chapter 7: Configuring Cognos 8 2. 3. 4. 5. In the Explorer window, under Security, Authentication, click Cognos. In the Properties window, ensure that Allow anonymous access is set to False. From the File menu, click Save. Repeat steps 1 to 4 on all servers where you installed Cognos 8 components.

Enable Single Signon Using Shared Secret
You can use shared secret for single signon between Cognos portlets and Cognos 8 components. The Cognos portlets send a message that contains an encrypted version of the portal user ID. 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 Cognos server. You can use shared secret for the third-party portal only if portal user IDs can be looked up in an NTLM, LDAP, or Cognos Series 7 authentication namespace that is shared by Cognos 8 components. Cognos 8 components must have access to a directory server that contains user IDs for all your portal users. Using Cognos Configuration, you must configure an authentication namespace so that the portal and Cognos 8 components share the same authentication source. You must also create a Custom Java Provider namespace to register the shared secret Java provider that is provided with Cognos 8 components. You must then create a dedicated gateway that is configured to target the Custom Java Provider namespace. You must configure access to the required Web content on the dedicated gateway. Finally, you must provide access from the portlets to Cognos 8 through a dedicated gateway and the required shared secret by configuring the appropriate portlet application: • Cognos iViews (SAP EP) • Cognos Portlet Application (WebSphere Portal) • remote server (Plumtree Portal)

Steps to Configure the Required Namespaces
1. In Cognos Configuration, configure a namespace to authenticate portal users. For instructions, see the topic about configuring LDAP, NTLM, or Cognos Series 7 authentication providers in the Installation and Configuration Guide. 2. For an LDAP namespace, configure the following properties: • For the Use external identity property, change the setting to True. • For the External identity mapping property, set it to (uid=${environment("REMOTE_USER")}) Other properties may be required. For more information, see the topic about configuring Cognos 8 components to use LDAP in the Installation and Configuration Guide. 3. For a Cognos Series 7 namespace, map the portal user IDs to Cognos Series 7 user IDs using OS signons. For more information, see the Cognos Series 7 documentation. 4. In Cognos Configuration, create and configure a Custom Java Provider namespace. For instructions, see the topic about configuring a custom authentication namespace in the Installation and Configuration Guide. • For the Namespace ID property, specify any new ID. For example, cpstrusted This new ID must be used when you configure the dedicated gateway. • For the Java class name property, type com.cognos.cps.auth.CPSTrustedSignon Java class names are case-sensitive. 5. In Cognos Configuration, under Environment, Portal Services, configure the following properties: • For Trusted Signon Namespace ID, type the namespace ID of the LDAP, NTLM, or Cognos Series 7 namespace that you configured in step 1.

Installation and Configuration Guide 115

enter the URL path to access Portal Services components through the dedicated gateway. 3. click Environment. In the Explorer window. 3. change the Gateway namespace property to match the name you configured for the Namespace ID property for the Custom Java Provider namespace. Change the Internal Dispatcher URI and External Dispatcher URI properties to specify the URI for the main Cognos 8 components dispatcher.wsdl Example for a servlet gateway: http://172. start Cognos Configuration. 2.wsdl 116 . click Save. In the Properties window.wsdl • For Cognos Extended Applications Gateway_URI/wsrp/cps4/portlets/sdk?wsdl&b_action=cps. • Steps to Configure a Dedicated Gateway 1. 4. Start Cognos Configuration for the new gateway. 4. For Shared Secret. under Environment.0. This parameter represents the authorization secret that must be shared between the Cognos portlets and the Cognos server. or Cognos Series 7.16.wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos. In the Properties window. From the File menu. 2. we recommend you specify a non-null value. Consider this as a secret password.16. click the Value box next to Web Content URI.Chapter 7: Configuring Cognos 8 Tip: The trusted signon namespace acts as an intermediary and must be attached to a real directory-based namespace of type LDAP. Steps to Configure Access to the Portal Services Web Content 1.1:9500/wsrp/cps4/portlets/nav?wsdl&b_action=cps. see the topic about Installing Cognos 8 in the Installation and Configuration Guide. Specify the host name or IP address of the dedicated gateway and a port number using the format host_or_IP_address:port 5.wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos. For example. For instructions. 2. The format of the URL is as follows: • For Cognos content portlets Gateway_URI/wsrp/cps4/portlets/nav?wsdl&b_action=cps.0. cpstrusted 5. 3. For security reasons. Steps to Configure the Cognos iViews for SAP EP 1. You must use the same character string when you configure the portlet application. In the Explorer window.wsdl Example for a servlet gateway: http://172. For the cpsserver: CPS Connection Server property.cgi/wsrp/cps4/portlets/sdk?wsdl&b_action=cps . NTLM. Ensure that you have installed an alternate gateway. select Show All.cgi/wsrp/cps4/portlets/nav?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. In the Property Category box. On the computer where you installed the Application Tier Components. 4. For the cpsauthsecret: CPS Authorization Secret property. type the key to be used for single signon. click Portal Services. Open the iView editor for each Cognos iView.1:9500/wsrp/cps4/portlets/sdk?wsdl&b_action=cps.

wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos.16. For the cps_auth_secret property. enter the URL path to access Portal Services components through the dedicated gateway.cgi/wsrp/cps4/portlets/cmm?wsdl&b_action=cp s. enter the secret character string that you used for the Shared Secret property when you configured the Custom Java Provider namespace.Chapter 7: Configuring Cognos 8 • For Metrics Manager Watchlist portlets Gateway_URI/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.cgi/wsrp/cps4/portlets/sdk?wsdl&b_action=cps .wsdl • For Metrics Manager Watchlist portlets Gateway_URI/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.cgi/wsrp/cps4/portlets/nav?wsdl&b_action=cps .wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos.16. For the CPS Endpoint property.0. The format of the URL is as follows: • For Cognos content portlets Gateway_URI/wsrp/cps4/portlets/nav?wsdl&b_action=cps. For each Cognos portlet application. Installation and Configuration Guide 117 .properties file in the c8_location/cps/plumtree/webapps/gadgets/WEB-INF/classes directory.16.wsdl Example for a servlet gateway: http://172.1:9500/wsrp/cps4/portlets/nav?wsdl&b_action=cps. click Modify Parameters.16.wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos.wsdl • For Cognos Extended Applications Gateway_URI/wsrp/cps4/portlets/sdk?wsdl&b_action=cps. 2. Using a plain ASCII editor. edit the cpspt.0.1:9500/wsrp/cps4/portlets/sdk?wsdl&b_action=cps.1:9500/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.1:9500/wsrp/cps4/portlets/cmm?wsdl&b_action=cps.cgi/wsrp/cps4/portlets/cmm?wsdl&b_action=cp s.wsdl Example for a CGI gateway: http://myserver/cognos8/cgi-bin/cognos.wsdl Steps to Configure the Cognos Portlets for WebSphere Portal 1. 3.wsdl Example for a servlet gateway: http://172.wsdl Example for a servlet gateway: http://172.wsdl Steps to Configure the Remote Server for Plumtree Portal 1. such as Notepad.wsdl Example for a servlet gateway: http://172.0.0.

Go to the c8_location/cps/plumtree directory and run the following build file: • On UNIX or Linux. Consider this as a secret password. For security reasons. see the topic about changing the gateway in the Installation and Configuration Guide. build.wsdl For instructions. cps_auth_secret The shared secret code Cognos 8 uses to encrypt an HTTP header variable that carries the user identity.cgi portion with the values to target the dedicated gateway.isapi/wsrp/cps4/portlets/[ package]?wsdl&b_action=cps. Enable Single Signon for SAP EP with the SAP Logon Ticket If you enable single signon with the SAP Logon Ticket. If Cognos 8 components are running under another type of application server.sh • On Windows. see the Installation and Configuration Guide. you must configure Cognos 8 components with an SAP namespace that links to an SAP BW server. Use the same value that you used for Shared Secret in Cognos Configuration. forward_cookies= The names of the cookie that should be sent to the report server for single signon. Configure the following settings. Tomcat automatically expands the WAR file and starts the remote server. • Copy the cps-pt. Before you start. see the administration guide for your application server. Parameter cps_endpoint Value The URL to connect to the report server and extract the WSDL information. Leave blank. 5. If Cognos 8 components are running using Tomcat. we recommend you specify a non-null value. build. Then you must copy the certificate that was generated during SAP EP installation to the SAP BW personal security environment.war file in the c8_location/cps/plumtree/gadgets directory. Users must have the same user ID in all SAP systems that are accessed through single signon. • enabled single signon between Cognos 8 components and SAP BW 118 . 3. • Start Cognos 8. ensure that you • configured Cognos 8 components to use an SAP authentication source For more information. 4. This parameter represents the authorization secret that must be shared between the Cognos portlets and the Cognos 8 server. • Stop Cognos 8.war file to the application server. For a servlet or ISAPI gateway.Chapter 7: Configuring Cognos 8 2. For example. replace the localhost/cognos8/cgi-bin/cognos. Specify the URI to the dedicated gateway. Single signon is configured. copy the cps-pt.war file to the c8_location/webapps directory.bat This creates a cps-pt. http://host_name/cognos8/cgi-bin/cognos. For instructions.

• Configure the gateway to authenticate all incoming logons using the associated namespace. Configure the gateway URI that will be used by Portal Services to require authentication using HTTP Basic Authentication. download sapsecin and sepsecu. Steps to Prepare the Environment 1. download EP50_PLUG-IN for Basis 620 (SAPKINE32A). or Cognos Series 7 authentication providers in the Installation and Configuration Guide. • For the External identity mapping property. You can now use the Cognos iViews in the SAP Enterprise Portal.2. For instructions. see the topic about installing Cognos 8 in the Installation and Configuration Guide. install SAPKINE32A. installed the latest hot patches for the SAP portal installed the Enterprise Portal plug-in that corresponds to the SAP EP release or SAP BW server For SAP releases earlier than 6. installed the latest service packs on the SAP BW server Service packs can be downloaded from SAPNET. Individual users or an administrator can enter the user IDs and passwords for Cognos 8 components in the data source. NTLM. do the following: • Install another instance of the gateway. Adjust the iView configuration to access the secure URL. For more information. installed the SAP Security Library on the SAP BW servers From sapservX. You must map the users logon credentials in the data source to an LDAP or Cognos Series 7 or NTLM namespace. change the setting to True.dll and place both files in the /run directory of the SAP BW server. see the topic about configuring the gateway to use a namespace in the Installation and Configuration Guide. see the topic about configuring LDAP. under /general/misc/security/SAPSECU/platform. complete the procedures for single signon with SAP logon tickets in the SAP Enterprise Portal Security Guide. see the topic about configuring Cognos 8 components to use LDAP in the Installation and Configuration Guide.pct. For information about configuring a URL to use HTTP Basic Authentication. 2. If you use an LDAP namespace. configure the following properties: • For the Use external identity property. see the documentation for the gateway or for your Web server. Portal Services iViews transmit the logon credentials to Cognos 8 components using HTTP Basic Authentication. see the Administration and Security Guide. Steps to Create the Data Source and Map the Users 1.Chapter 7: Configuring Cognos 8 For more information. 4. on SAPNET. For more information. see the documentation for your Web server. configure a namespace to authenticate portal users. For information. 3. If Cognos 8 components are configured with more than one namespace. 5. In Cognos Configuration.c8/systems/Cognos 8 directory: • Logon Method = UIDPW • server name = the name of the Cognos server Installation and Configuration Guide 119 . In the SAP portal. For more information. For more information. see the Installation and Configuration Guide. • • • • To enable SSO for SAP EP. set it to (uid=${environment("REMOTE_USER")}) Other properties may be required.cognos. Using transaction SAINT. ensure that the following properties are configured for the data source in the /PortalContent/other_vendors/every_user/com. you define a Cognos data source in SAP EP. Enable Single Signon for SAP EP with User Mapping If you enable single signon with user mapping.

To use application server single signon. see the SAP Enterprise Portal Administration Guide. edit properties for the all iViews so that the cpsserver: CPS Connection Server property uses https instead of http. For more information about Active Credential objects. see the documentation for IBM WebSphere Portal. After single signon is set up. For more information. The SSL security supported by SAP uses encryption above 56 bits. see the Administration and Security Guide. For more information. Credentials for the portal user are passed to the gateway using this object. You can now use the Cognos iViews in the SAP Enterprise Portal. see the SAP Enterprise Portal Administration Guide. see the Administration and Security Guide. For more information about configuring SSL in Cognos 8 components. Steps 1. LtpaToken. using SSL. 3. or Cognos Series 7 authentication namespace to provide single signon. For more information. LDAP. see the Cognos Enhanced Encryption Module for OpenSSL Installation and Configuration Guide. in an attribute called CPS: User Mapping Datasource. By default. you must purchase and install the Enhanced Encryption Module for OpenSSL on top of Cognos 8 components. see your SAP EP security documentation. Enable Secure Communication Between SAP EP and Cognos 8 Components A secure connection. To enable SSL between SAP EP and Cognos 8 components. The header can be used with an NTLM. 2. After SSL is enabled. Cognos provides an enhanced encryption module as a complementary product. you can use the Cognos portlets in the WebSphere Portal. see the documentation for IBM WebSphere Application Server. SiteMinderToken. configure a namespace to authenticate portal users.user • system alias (Create a system alias) For more information. In Cognos Configuration. It is more important if you enabled single signon with user mapping. see the Administration and Security Guide. see the SAP Enterprise Portal Administration Guide. For more information. For information about SSL for Cognos 8 components on a WebSphere Application Server. see the topic about enabling SSL in the application server chapter of the Installation and Configuration Guide. and WebSealToken. For more information.Chapter 7: Configuring Cognos 8 • port number = port number of the dedicated gateway • Protocol of Target system = HTTP • User Mapping Type = admin. Register the Cognos credentials for the portal users. 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 Cognos 8 components. For each Cognos iView. You can now use the Cognos portlets in the SAP Enterprise Portal. To enable SSL. enable user mapping for the data source by entering the name of the system alias at the iView level. For more information. 120 . Cognos 8 components use an encryption algorithm up to 56 bits. Enable Single Signon for Plumtree Portal Using Basic Authentication You can configure a portlet in Plumtree Portal to send the username and password as an HTTP Basic authentication header. We recommend that you enable secure communication between SAP EP and Cognos 8. Portal Services supports the following Active Credentials objects: HttpBasicAuth. Users can enter their own user IDs and passwords. see the topic about configuring the SSL protocol in the Installation and Configuration Guide. is not required between SAP EP and Cognos 8 components.

In the administration console of the Web server. Otherwise. see the topic about installing Cognos 8 in the Installation and Configuration Guide.isapi/wsrp/cps4/portlets/[package]?wsdl &b_action=cps. In Cognos Configuration. Enable Single Signon for Plumtree Portal Using SiteMinder If you use Netegrity SiteMinder to provide single signon in your security infrastructure. For instructions. For instructions. • Change the forward_cookies property to include the name of the active authentication token that SiteMinder provides. Configure the Plumtree remote server to access Cognos 8 using the dedicated gateway: • Edit the cpspt. For a CGI gateway. replace the localhost/cognos8/cgi-bin/cognos. NTLM. Plumtree Portal sends the SiteMinder active authentication token to the remote server. see the topic about installing Cognos 8 in the Installation and Configuration Guide. For instructions. http://host_name:port/cognos8/cgi-bin/cognos. you can also use it for single signon with Plumtree Portal. For a CGI gateway. which sends the token to the Cognos 8 gateway. replace the localhost portion with host_name:port. configure the virtual directories to access the dedicated gateway. see the documentation for your Web server. 2. Configure the remote server to forward the authentication token: • Edit the cpspt. Otherwise.wsdl . you can use the default setting if the dedicated gateway and the remote server are on the same computer. For instructions. see the Installation and Configuration Guide.wsdl Installation and Configuration Guide 121 . see the topic about configuring LDAP.properties file in the c8_location/cps/plumtree/webapps/gadgets/WEB-INF/classes directory. see the Installation and Configuration Guide. Steps 1. • Change the cps_endpoint property to indicate the URL of the dedicated gateway. 3. see the topic about configuring SiteMinder authentication namespaces in the Installation and Configuration Guide. or Cognos Series 7 authentication providers in the Installation and Configuration Guide. For example. 4. Configure the gateway. 4. For example. replace the localhost portion with host_name:port.cgi portion with the values to target the dedicated gateway. You must configure a SiteMinder authentication namespace in Cognos 8.properties file in the c8_location/cps/Plumtree/webapps/gadgets/WEB-INF/classes directory.Chapter 7: Configuring Cognos 8 For instructions. replace the localhost/cognos8/cgi-bin/cognos. 2. For instructions. For a servlet or ISAPI gateway. http://host_name:port/cognos8/cgi-bin/cognos.isapi/wsrp/cps4/portlets/[package]?wsdl &b_action=cps. Install an alternate CGI or ISAPI or servlet gateway in Cognos 8. Install an alternate CGI or ISAPI or servlet gateway in Cognos 8. 5.cgi portion with the values to target the dedicated gateway. you can use the default setting if the dedicated gateway and the remote server are on the same computer. For more information. configure a SiteMinder authentication namespace. For a servlet or ISAPI gateway. 3. Configure the gateway. • Change the cps_endpoint property to indicate the URL of the dedicated gateway.

The configuration must contain information that is accessible by all Content Manager computers. you can test namespaces. or when Content Manager is installed on a Linux computer. After you delete a namespace using Cognos Configuration. For authenticated logon. you must use the same authentication namespace for both versions. you can disable anonymous access. you can delete the namespace. Important: You must not delete the Cognos namespace. see the Administration and Security Guide. By default. Some authentication providers require libraries external to the Cognos 8 environment to be available. when upgrading from one version to another. see the Administration and Security Guide. When Cognos 8 is installed on a single Linux computer. and groups. you must configure Cognos 8 components with an appropriate namespace for the type of authentication provider in your environment. After you configure new namespaces. Cognos 8 components support the following types of servers as authentication sources: • Active Directory Server • Cognos Series 7 • Custom Authentication Provider • LDAP • Netegrity SiteMinder • NTLM • SAP If you use more than one Content Manager computer. roles. you must install Content Manager on a non-Linux computer: • Cognos Series 7 namespace • Active Directory Server • SAP BW • NTLM • Netegrity SiteMinder 122 . If these libraries are not available on Linux. You can also delete namespaces that you added if they are no longer required (p. If you choose to use only authenticated logon.Chapter 7: Configuring Cognos 8 Configuring Cognos 8 Components to Use an Authentication Provider Cognos 8 components run with two levels of logon: anonymous and authenticated. users. It contains authentication data that pertains to all users and is required to save the configuration. For more information. Also. You can configure the namespace if you still require the user account information. For information about deleting the namespace. Cognos 8 can be configured to use only LDAP V3-compliant directory servers and custom providers as authentication sources. you must complete the process by deleting it in the portal. If you upgraded from ReportNet and Cognos 8 detects a previously configured namespace that is no longer configured. you must configure identical authentication providers on each Content Manager computer. You can use both types of logon with your installation. anonymous access is enabled. the authentication provider cannot be initialized. the unconfigured namespace appears in the list of authentication providers in the Administration portal. 142). If you want to configure a one of the following as your authentication source. Otherwise. You can configure multiple namespaces for authentication and then choose at run time which namespace you want to use. This means that the type of authentication provider you select and the way you configure it must be identical on all computers for all platforms. Otherwise. the new version may not contain the same policies.

3. and roles which no longer exist. contacts. under Security. Installation and Configuration Guide 123 . groups. Users can log on anonymously. under Security. For more information. For more information. The Cognos namespace stores information about Cognos groups. start Cognos Configuration. if required. you can use Cognos Configuration to disable anonymous access. and refers to objects in other security namespaces. such as the Anonymous User. Now. see the Architecture and Planning Guide. On each Content Manager computer. and distribution lists. For more information. you must configure security settings immediately after you complete the installation and configuration process. and My Pages entries are permanently lost. see the Administration and Security Guide. change the value of Restrict access to members of the built-in namespace to True. click the box next to the Allow anonymous access property and then click False. This means that a user logs on once and can then switch to another application without being asked to log on again. see the Administration and Security Guide. ❑ Configure Cognos 8 components to use an authentication provider. Because these entries refer to users. groups or roles that no longer exist. You must now use the portal to remove the Everyone group from the Cognos built-in roles and groups and then ensure that authorized users belong to at least one Cognos built-in role or group. 2. Authentication. click Save. all users belong to several built-in groups or roles. My Folders. the user preferences. In the Explorer window. click Cognos. In the Explorer window. To restrict access. users are required to provide logon credentials when they access Cognos resources. 3. 4. click Save. To use an authentication provider and to require users to authenticate: ❑ Disable anonymous access. After you configure an authentication provider for Cognos 8 components. click Authentication. 4. start Cognos Configuration. Disable Anonymous Access By default. you can safely delete them. 2. From the File menu. In the Properties window. From the File menu. The Cognos resource represents the Cognos namespace. Important: We recommend that you do not disable security after you enable it. By default. you must: • enable the property to restrict access • remove the Everyone group from the Cognos built-in roles and groups • ensure that authorized users belong to at least one Cognos role or group Steps 1.Chapter 7: Configuring Cognos 8 If you enable security. On each Content Manager computer. Cognos 8 components do not require user authentication. While this does not affect how the permissions work. Restrict User Access to Cognos 8 Access can be restricted to users belonging to any group or role defined in the Cognos built-in namespace. a user administering the permission settings may see "unknown" entries. Steps 1. If you delete a namespace. you can enable single signon between your authentication provider environment and Cognos 8 components. If you want to use authenticated logon only. In the Properties window. Existing permission settings will refer to users.

see the Administration and Security Guide. click the appropriate namespace and then click OK. right-click Authentication. do the following: ❑ Configure Cognos 8 components to use an Active Directory Server namespace ❑ Enable secure communication to the Active Directory Server. for the Namespace ID property. In the Explorer window. Configuring Cognos 8 Components to Use Active Directory Server If you install Content Manager on a Windows computer. If you are configuring an Active Directory namespace to support single signon with a Microsoft SQL Server or Microsoft Analysis Server data source. the report server (Application Tier Components). In the Name box. 6. 2.Chapter 7: Configuring Cognos 8 For information about adding or removing members of a Cognos group or role. For more information. 3. If you install Content Manager on a UNIX computer. and the data source server (Microsoft SQL Server or Microsoft Analysis Server) must belong to the Active Directory domain. if required ❑ Enable single signon between Active Directory Server and Cognos 8 components Configure an Active Directory Namespace You can use Active Directory Server as your authentication provider. 132). If you install Content Manager on both UNIX and Windows computers. you must instead use an LDAP namespace to configure Active Directory as your authentication source. you must ensure that the Authenticated users group has Read privileges for the Active Directory folder where users are stored. Steps 1. Note: For Cognos 8 to work properly with Active Directory Server. specify a unique identifier for the namespace. If you install Content Manager on a Linux computer. type a name for your authentication namespace. 124 . In the Type list. IIS Web server. see the Administration and Security Guide. you must use an LDAP namespace to configure Active Directory on all Content Manager computers. In the Properties window. you must use Active Directory as your authentication source. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. under Security. If you want to use Microsoft SQL Server or Microsoft Analysis Server as a data source and use single signon for authentication. You also have the option of making custom user properties from the Active Directory Server available to Cognos 8 components. The new authentication provider resource appears in the Explorer window. and then click New resource. the following configuration is required: • The Cognos 8 gateway must be installed on an IIS Web server that is configured for Windows Integrated Authentication. • Content Manager. you can configure Active Directory as your authentication source using an Active Directory namespace. 5. you cannot use an Active Directory Server as your authentication source. • The data source connection for Microsoft SQL Server or Microsoft Analysis Server must be configured for External Namespace and that namespace must be the Active Directory namespace. see "Configure an LDAP Namespace for Active Directory Server" (p. Namespace. 4. under the Authentication component. On every computer where you installed Content Manager. • Content Manager must be installed on a Windows 2000 or Windows 2003 server. For more information about data sources. To use an Active Directory Server namespace and to set up single signon. open Cognos Configuration.

Add the CA root certificate to the certificate store of the account that you are using for the current Cognos session: • If you are running the Cognos session under a user account. In the Explorer window. In the Properties window. 7. 2. 8. see the documentation for MMC. see the Framework Manager User Guide. Make Custom User Properties for Active Directory Available to Cognos 8 Components You can use arbitrary user attributes from your Active Directory Server in Cognos 8 components. For information. 3. initializes. see the Administration and Security Guide. Use the credentials of an Active Directory Server user who has search and read privileges for that server. click Add. you must copy the certificate from the Active Directory Server to the Content Manager computer. 6. In the Value . click in the Value column for Custom properties and click the edit button. The custom properties can also be used inside command blocks that are used to configure Oracle sessions and connections.Custom properties window. From the File menu. and configures the provider libraries for the namespace. From the File menu. In Cognos Configuration. Enabling Secure Communication to the Active Directory Server If you are using an SSL connection to the Active Directory Server. Click the Value column and enter the name of the account parameter in your Active Directory Server. The command blocks can be used with Oracle light-weight connections and virtual private databases. For more information about session parameters. right-click the new authentication resource and click Test. Specify the values for the Host and port property. For information. see the documentation for your Web browser. Click OK. In the Explorer window. Cognos 8. The custom properties are available as session parameters through Framework Manager. To configure this. On every Content Manager computer. click Save. Cognos 8 loads.Chapter 7: Configuring Cognos 8 7. 8. open Cognos Configuration. 3. 5. you must add these attributes as custom properties for the Active Directory namespace. On every computer where you installed Content Manager. 9. Test the connection to a new namespace. under Security. under Authentication. 2. click Cognos 8 service. If you want to be able to search for details when authentication fails. 9. Click the Name column and enter the name you want Cognos 8 components to use for the session parameter. 10. Steps 1. Authentication. restart the service: • In the Explorer window. use the same Web browser as in step 1 to import the CA root certificate to the certificate store for your user account. Steps 1. use Microsoft Management Console (MMC) to import the CA root certificate to the certificate store for the local computer. use your Web browser to connect to the Active Directory Server and copy the CA root certificate to a location on the Content Manager computer. click the Active Directory namespace. • If you are running the Cognos session under the local computer account. specify the user ID and password for the Binding credentials property. Repeat the preceding two bulleted steps for each custom parameter. 4. click Save. For more information. Installation and Configuration Guide 125 .

8. Steps 1. Set up Windows Integrated Authenticated on the IIS Web server. In the Value . Microsoft sets REMOTE_USER by default when you enable Windows Integrated Authentication. specify the host and port of any domain controller in the forest. chase_referrals and multi_domain_tree. You must set the advanced property singleSignonOption to the value IdentityMapping. specify the host and port of the top-level controller for the domain tree. open Cognos Configuration. If you do not want Kerberos delegation. 3. users in all domain trees in the forest can log in to Cognos 8. click Save. chase_referrals False True True multi_domain_tree False False True Enabling Single Signon Between Active Directory Server and Cognos 8 Components By default. In the Explorer window. you are not prompted to reenter authentication information when accessing Cognos content that is secured by the Active Directory namespace. From the File menu. click Add. users in the original authenticated domain and all child domains of the domain tree can log in to Cognos 8. users from only one domain can log in. 6. • For users in all domain trees in the forest. Authentication. If Integrated Authenticated is enabled. with the following values: Authentication for One domain One domain tree All domain trees in the forest 7. 126 . the provider can be configured to access the environment variable REMOTE_USER to achieve single signon. Include or Exclude Domains Using Advanced Properties When you configure an authentication namespace for Cognos 8. specify the host and port of a domain controller for the single domain. • For users in one domain tree. 4. specify the Host and port property: • For users in one domain. By using the Advanced properties for Active Directory Server. Authentication in One Domain Tree If you set a parameter named chase_referrals to true. the Active Directory provider uses Kerberos delegation and integrates with the IIS Web server for single signon if Integrated Authenticated (formerly named NT Challenge Response) is enabled on the IIS Web server. Authentication in All Domain Trees in the Forest If you set a parameter named multi_domain_tree to true.Chapter 7: Configuring Cognos 8 • From the Actions menu. 5. Click OK. under Security. click the Active Directory namespace. Specify two new properties. Click in the Value column for Advanced properties and click the edit button. Users above the original authenticated domain or in a different domain tree cannot log in. 2. Steps for Single Signon Using Kerberos Delegation 1. On every computer where you installed Content Manager. click Restart. users from related (parent-child) domains and unrelated domain trees within the same forest can also log in.Advanced properties window. In the Properties window.

Users will be authenticated based on the authentication and signon configuration of the Cognos Series 7 namespace. The Active Directory provider now uses REMOTE_USER for single signon.Advanced properties window. 3. You can configure Cognos 8 components to use multiple Cognos Series 7 authentication providers. type IdentityMapping 7. under Security. right-click Authentication. type singleSignonOption 6. for the active and standby Content Manager computers. Otherwise. In the Value . Click OK. In the Explorer window.Chapter 7: Configuring Cognos 8 2. In the Explorer window. you may receive errors or be prompted for authentication more than once. When setting up the computers using the Active Directory user tool. and then click New resource. open Cognos Configuration. If you change the configuration information stored in the directory server used for Cognos Series 7. open Cognos Configuration. In the Value column. 4. type a name for your authentication namespace. you must install Content Manager on a non-Linux computer. 5. A user must be in at least one Access Manager user class to be able to log on to Cognos 8 components. If you want to configure a Cognos Series 7 namespace as your authentication source. if required ❑ Enable single signon between Cognos Series 7 and Cognos 8 Configure a Cognos Series 7 Namespace You can configure Cognos 8 to use one or more Cognos Series 7 namespaces for authentication. or the user account under which Content Manager runs. Set up the computers. 2. in the Value column. To use a Cognos Series 7 namespace and to set up single signon. click Add. Steps for Single Signon Using REMOTE_USER 1. click the Active Directory namespace. to be trusted for delegation. Steps 1. which is sensitive and cannot be delegated. edit Advanced properties and. Namespace. Click in the Value column for Advanced properties and then click the edit button. In the Name box. type KerberosAuthentication Configuring Cognos 8 to Use Cognos Series 7 Namespace You can configure Cognos 8 components to use a Cognos Series 7 namespace as the authentication provider. Note: You cannot use a Cognos Series 7 Local Authentication Export (LAE) file for authentication with Cognos 8 components. On every computer where you installed Content Manager. 3. Installation and Configuration Guide 127 . Install Content Manager on a computer that is part of the domain. On every computer where you installed Content Manager. We recommend that all Cognos Series 7 namespaces use the same primary Cognos Series 7 Ticket Server. If you want to switch back to Kerberos delegation. under Security. Authentication. do not select the Account attribute. do the following: ❑ Configure Cognos 8 to use a Cognos Series 7 namespace ❑ Enable secure communication to the directory server used by the Cognos Series 7 namespace. 3. you must restart the Cognos 8 service before the changes take effect in the Cognos installation. In the Name column. 2.

The new authentication provider resource appears in the Explorer window. For more information. click Save. You can now add Cognos Upfront Series 7 NewsBoxes to your Cognos Connection portal pages. 127). in the Explorer window. right-click the new authentication resource and click Test. If the Cognos Series 7 namespace uses the Trusted Signon plug-in for single signon. 128 . 7. you are not prompted to reenter authentication information when accessing Cognos content that is secured by the Cognos Series 7 namespace. Cognos Series 7 Namespaces and the Cognos Series 7 Trusted Signon Plug-in If the Cognos Series 7 namespace uses the Trusted Signon plug-in for single signon. expand Services. Save and close Configuration Manager. If your Series 7 namespace version is 16. you must define the SaferAPIGetTrustedSignonWithEnv function in your plug-in. Cognos 8 loads. Steps 1. Access Manager Runtime and click Cookie Settings. Domain and Secure Flag Enabled properties match the settings configured for Cognos 8. Domain and Secure flag enabled properties match the settings configured for Cognos Series 7. Enabling Single Signon Between Cognos Series 7 and Cognos 8 If your Cognos Series 7 namespace has been configured for integration with your external authentication mechanisms for single signon. From the File menu. Enabling Secure Communication to the Directory Server Used by the Series 7 Namespace If you are using an SSL connection to the Directory Server used by the Cognos Series 7 namespace. you must use the same format to identify the Cognos Series 7 directory server in both Cognos Series 7 and Cognos 8. 2.0. under the Authentication component. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. In the Properties window. under Cookie settings. Click Open the current configuration. 4. In the Explorer window. 5. initializes.Chapter 7: Configuring Cognos 8 4. By configuring single signon. see the Cognos Access Manager Administrator Guide and the documentation for your Directory Server. In the Type list. ensure that the Path. Test the connection to a new namespace. 7. ensure that the Path. under Authentication. 6. On the Components tab. for the Namespace ID property. the computers where Content Manager is installed must use the same locale as the data in the Series 7 namespace. you must copy the certificate from the Directory Server to each Content Manager computer. Ensure that you configured Cognos 8 components to use a Cognos Series 7 namespace as an authentication provider (p. In the Properties window. Then you must recompile and redeploy the library for single signon to be achieved between Cognos 8 components and your authentication mechanism. 8. 5. start Configuration Manager. the Cognos Series 7 provider will automatically use this configuration. If you want to publish from PowerPlay Enterprise Server. ensure that the Data encoding property is set to UTF-8. In addition. you must use a host name in the Host and port property in Cognos 8. 9. If you specify a host name in Cognos Series 7. In the Properties window. you must now define the SaferAPIGetTrustedSignonWithEnv function. specify a unique identifier for the namespace. 6. click the appropriate namespace and then click OK. For Cognos Series 7. 3. and configures the provider libraries for the namespace.

This value does not need to be null-terminated. If you are running both Cognos Series 7 and Cognos 8 products using the same plug-in. it is not possible for the plug-in to perform a getenv( ) API call to retrieve Web server environment variables. Access Manager calls SaferAPIFreeTrustedSignon to free the memory allocated. Note that the first time this API is called.Chapter 7: Configuring Cognos 8 The SaferAPIGetTrustedSignonWithEnv function is an updated version of the SaferAPIGetTrustedSignon function. *userType. A sequence of bytes that identifies the currently authenticated user. A string that contains a comma separated list of environment variable names that are requested by the Safer implementation. Access Manager calls SaferAPIFreeBuffer() to free the memory allocated. OS signons must exist and be enabled in the current namespace. This update is required because Cognos 8 logon is not performed at the Web server as is the case for Cognos Series 7 applications. Syntax SaferAPIGetTrustedSignonWithEnv( EnvVar char void unsigned long void unsigned long SAFER_USER_TYPE void envVar[]. **trustedDomainName. For information about the SaferAPIGetTrustedSignon function. Therefore. If the function returns SAFER_INFO_REQUIRED. both the SaferAPIGetTrustedSignonWithEnv and SaferAPIGetTrustedSignon functions are required. the envVar array contains only the end of array marker. Both functions. The function SaferAPIGetError is required only if you want specific error messages returned from your plug-in. *trustedSignonNameLength. The plug-in can request that specific environment variables be removed from the Web server using the SaferAPIGetTrustedSignonWithEnv function. The memory for the returned reqEnvVarList is allocated internally in this API. **reqEnvVarList. *trustedDomainNameLength. The end of the array is represented by an entry with a null envVarName and a null envVarValue. /*[IN]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[OUT]*/ /*[IN/OUT]*/ Parameter [in] envVar Description An array of environment variable names and values that were retrieved from the Web server. SaferAPIGetTrustedSignonWithEnv Function For users to be successfully authenticated by Access Manager. The memory for the returned trustedSignonName and trustedDomainName is allocated internally in this API. [in] reqEnvVarList [out] trustedSignonName Installation and Configuration Guide 129 . The end of the list must be null-terminated. **implementerData). SaferAPIGetTrustedSignon and SaferAPIFreeBuffer must be implemented to successfully register the library when SaferAPIGetTrustedSignonWithEnv is implemented. This value is mandatory. **trustedSignonName. If the function returns SAFER_SUCCESS. see the Cognos Series 7 documentation.

This length should exclude the null terminator. if there is one. This value does not need to be null-terminated. If there is no trustedDomainName. • SAFER_ANONYMOUS_USER An anonymous user. An invocation occurs every time Access Manager calls the trusted signon plug-in. A guest user account must exist and be enabled in the current namespace. The following return values are required for users to be successfully authenticated by Access Manager: • SAFER_NORMAL_USER A named user. or custom attributes are dependent on the custom authentication provider implementation. 130 . the return is null. Steps 1. You can also use it as a single signon mechanism to integrate Cognos 8 components with your security infrastructure. single signon. Any additional configuration for authentication source access. This value is optional. An integer value that indicates the length of the trustedDomainName. OS signons must exist and be enabled in the current namespace. open Cognos Configuration. You can use a custom authentication provider to access and authenticate users to an alternate authentication source. This length should exclude the null terminator. On every computer where you installed Content Manager. An anonymous user account must exist and be enabled in the current namespace. This value is mandatory and must be set to zero if there is no trustedDomainName. This value is mandatory. Configuring Cognos 8 to Use a Custom Authentication Provider If you implemented a custom Java authentication provider with your existing security infrastructure. A sequence of bytes that identifies the domain of the currently authenticated user. you can configure Cognos 8 components to use it. This value is mandatory. Configure a Custom Authentication Namespace You can configure Cognos 8 components to use a custom authentication namespace. [out] trustedDomainName [out] trustedDomainNameLength [out] userType [in/out] implementerData A pointer used to preserve implementation-specific data between invocations. • SAFER_GUEST_USER A guest user. A value that indicates the type of user that Access Manager will authenticate.Chapter 7: Configuring Cognos 8 Parameter [out] trustedSignonNameLength Description An integer value that indicates the length of the trustedSignonName. This value is valid only if the trusted signon plug-in was invoked and you set a value for it. if there is one. see the Custom Authentication Provider Developer Guide. For more information.

5. and folders as the Bind user. Configuring Cognos 8 Components to Use LDAP You can configure Cognos 8 components to use an LDAP namespace as the authentication provider. under the Authentication component. You also have the option of making custom user properties from the LDAP namespace available to Cognos 8 components.Chapter 7: Configuring Cognos 8 2. If the Use external identity property is set to True. 8. The new authentication provider resource appears in the Explorer window. if required Make custom user properties available to Cognos 8 components. type a name for your authentication namespace. All users who log on to Cognos 8 using external identity mapping see the same users. From the File menu. the LDAP authentication provider must construct the distinguished name (DN). click Save. In the Explorer window. In the Name box. When an LDAP namespace has been configured to use the External identity mapping property for authentication. Specify the values for all other required properties to ensure that Cognos 8 can locate and use your existing authentication provider. right-click Authentication. 4. under Security. under Authentication. When the LDAP authentication provider performs these searches. In the Type list. The LDAP user directory may be accessed from within another server environment. and click New resource. 6. such as Active Directory Server or Netegrity SiteMinder. if required Enable secure communication to the LDAP server. If it cannot find the environment variable or the DN in the LDAP server. you can configure the User lookup and External identity mapping properties to use search filters. specify a unique identifier for the namespace. Test the connection to a new namespace. If you are configuring an LDAP namespace for a Novell Directory Server. Tip: Do not use colons (:) in the Namespace ID property. To bind a user to the LDAP server. if required Enable single signon between LDAP and Cognos 8 components Configure an LDAP Namespace You can configure Cognos 8 components to use an LDAP namespace when the users are stored in an LDAP user directory. see Configure an LDAP Namespace for IBM Directory Server. initializes. the LDAP provider binds to the directory server using the Bind user DN and password or using anonymous if no value is specified. To use an LDAP namespace and set up single signon. for the Namespace ID property. If users are stored hierarchically within the directory server. 3. it attempts to use the User lookup property to construct the DN. In the Explorer window. see Configure an LDAP Namespace for Active Directory Server. If you are configuring an LDAP namespace for an IBM Directory Server. Cognos 8 loads. Installation and Configuration Guide 131 . see Configure an LDAP Namespace for Novell Directory Server. If you are configuring an LDAP namespace for an Active Directory Server. 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. right-click the new authentication resource and click Test. Namespace. it uses the External identity mapping property to try to resolve the user's DN. click Custom Java Provider and then click OK. and configures the provider libraries for the namespace. 7. groups. it uses the filters you specify for the User lookup and External identity mapping properties. do the following: ❑ Configure Cognos 8 components to use an LDAP namespace ❑ ❑ ❑ ❑ Configure an LDAP namespace for use with Active Directory Server. In the Properties window.

Cognos 8 loads. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. open Cognos Configuration. Steps 1. On every computer where you installed Content Manager. 4. we recommend that you type objectGuid 8. 2. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. for the Namespace ID property. under Authentication. under Security. In the Properties window.Chapter 7: Configuring Cognos 8 Steps 1. the LDAP authentication provider binds as anonymous. For the Unique identifier property. right-click the new authentication resource and click Test. 7. subsequent requests to the LDAP server are executed under the authentication context of the end user. right-click Authentication. you may have to change some default values to ensure successful communication between Cognos 8 components and the LDAP server. 3. then specify these values. Check the mapping settings for required objects and attributes. If external identity mapping is enabled. 5. specify a unique identifier for the namespace. specify a unique identifier for the namespace. Namespace. In the Properties window. when the user DN is established. right-click Authentication. then specify these values. under the Authentication component. In the Explorer window. type a name for your authentication namespace. open Cognos Configuration. In the Name box. In the Name box. Configure an LDAP Namespace for Active Directory Server If you configure a new LDAP namespace for use with an Active Directory Server. type a name for your authentication namespace. 2. 7. under Security. click the appropriate namespace and then click OK. under the Authentication component. initializes. If no values are specified. Bind user DN and password are used only when a search filter is specified for the User lookup property. 9. for the Namespace ID property. 5. 132 . If external identity mapping is not enabled. Namespace. 3. you must modify the necessary settings and change the values for all properties of the Active Directory objects. Tip: Do not use colons (:) in the Namespace ID property. Depending on the LDAP configuration. On every computer where you installed Content Manager. Test the connection to a new namespace. From the File menu. In that case. and then click New resource. 8. The new authentication provider resource appears in the Explorer window. In the Type list. Bind user DN and password are used for all LDAP access. 6. and then click New resource. 4. In the Type list. the LDAP authentication provider binds as anonymous. If no values are specified. In the Explorer window. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. 6. and configures the provider libraries for the namespace. click the appropriate namespace and then click OK. click Save. In the Explorer window. 10. The new authentication provider resource appears in the Explorer window.

organization" Description "ou. 10.o" Group Description 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 based on a default Active Directory Server installation. Configure an LDAP Namespace for IBM Directory Server If you configure a new LDAP namespace for use with an IBM Directory Server. From the File menu. right-click the new authentication resource and click Test. use the values specified in the following table. Test the connection to a new namespace. under Authentication. Installation and Configuration Guide 133 . In the Explorer window. 11. To configure the LDAP advanced mapping properties for use with the Active Directory Server objects. you may have to make additional mapping changes. Cognos 8 loads. you must modify the necessary settings and change the values for all properties of the IBM Directory objects. and configures the provider libraries for the namespace.Chapter 7: Configuring Cognos 8 9. 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 Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value "organizationalunit. initializes. click Save. If you have modified the schema.

In the Name box. To configure the LDAP advanced mapping properties for use with IBM Directory Server objects. 6. specify a unique identifier for the namespace. Specify the values for all other required properties to ensure that Cognos 8 can locate and use your existing authentication namespace.organization description ou. the LDAP authentication namespace binds as anonymous. 3. then specify these values. The new authentication namespace resource appears in the Explorer window. In the Properties window. open Cognos Configuration. for the Namespace ID property.o groupofnames description member cn organizationalperson telephonenumber (leave blank) description (leave blank) facsimiletelephonenumber givenname (leave blank) (leave blank) cn (leave blank) userPassword postaladdress 134 . use the values specified in the following table. If no values are specified. 2. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches.Chapter 7: Configuring Cognos 8 Steps 1. 4. under Security. Namespace. and then click New resource. Tip: Do not use colons (:) in the Namespace ID property. 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 Mobile phone Name Pager phone Password Postal address LDAP value organizationalunit. On every computer where you installed Content Manager. In the Explorer window. 8. right-click Authentication. click LDAP and then click OK. under the Authentication component. type a name for your authentication namespace. 7. In the Type list. 5.

Steps 1. If you have modified the schema. use the values specified in the following table. and then click New resource. for the Namespace ID property.o groupofnames description member cn inetorgperson telephonenumber preferredlanguage Installation and Configuration Guide 135 . On every computer where you installed Content Manager. under Security. click LDAP and then click OK. 6. If no values are specified.Chapter 7: Configuring Cognos 8 Mappings LDAP property Product locale Surname Username LDAP value (leave blank) sn cn These mapping properties represent changes based on a default IBM Directory Server installation. In the Type list. 3.organization description ou. the LDAP authentication namespace binds as anonymous. 4. specify a unique identifier for the namespace. Specify the values for all other required properties to ensure that Cognos 8 can locate and use your existing authentication namespace. Tip: Do not use colons (:) in the Namespace ID property. Namespace. In the Name box. open Cognos Configuration. 5. under the Authentication component. From the File menu. click Save. Configure an LDAP Namespace for Novell Directory Server If you configure a new LDAP namespace for use with a Novell Directory Server. The new authentication namespace resource appears in the Explorer window. Mappings Folder LDAP property Object class Description Name Group Object class Description Member Name Account Object class Business phone Content locale LDAP value organizationalunit. type a name for your authentication namespace. you may have to make additional mapping changes. specify (cn=${userID}) 7. To configure the LDAP advanced mapping properties for use with Novell Directory Server objects. 9. right-click Authentication. • For the User lookup property. 8. If you want the LDAP authentication provider to bind to the directory server using a specific Bind user DN and password when performing searches. then specify these values. 2. In the Properties window. you must modify the necessary settings and change the values for all properties of the Novell Directory objects. In the Explorer window.

In the Explorer window. Authentication. you must add these attributes as custom properties for the LDAP namespace. The custom properties can also be used inside command blocks that are used to configure Oracle sessions and connections. 9. On every computer where you installed Content Manager. click Save. To configure this. 7. 2. click Save. under Security. Click OK. If you have modified the schema. click the LDAP namespace. Make Custom User Properties for LDAP Available to Cognos 8 Components You can use arbitrary user attributes from your LDAP authentication provider in Cognos 8 components. Click the Name column. 9. Click the Value column. From the File menu. you may have to make additional mapping changes. From the File menu. 3. open Cognos Configuration. 6. The custom properties are available as session parameters through Framework Manager. 8. For more information. 5. click in the Value column for Custom properties and click the edit button. and enter the name of the account parameter in your LDAP authentication provider. In the Value . see the Administration and Security Guide. In the Properties window. see the Framework Manager User Guide. and enter the name you want Cognos 8 components to use for the session parameter. The command blocks can be used with Oracle lightweight connections and virtual private databases. 4.Custom properties window. click Add. For more information about session parameters. Repeat the preceding two bulleted steps for each custom parameter.Chapter 7: Configuring Cognos 8 Mappings LDAP property Description Email Fax/Phone Given name Home phone Mobile phone Name Pager phone Password Postal address Product locale Surname Username LDAP value description mail facsimiletelephonenumber givenname homephone mobile cn pager userPassword postaladdress preferredlanguage sn uid These mapping properties represent changes based on a default Novell Directory Server installation. 136 . Steps 1.

Examples ${replace(${environment("REMOTE_USER")}. you can configure the External identity mapping property to obtain the user ID from the Java user principal.Chapter 7: Configuring Cognos 8 Enabling Secure Communication to the LDAP Server To enable SSL.new)} Parameter str old new Description The string to search. The substring to be replaced by the new substring."")} Configuring Cognos 8 Components to Use Netegrity SiteMinder You can configure Cognos 8 components to use a Netegrity SiteMinder namespace as the authentication source. the External Identity mapping can refer to the userPrincipalName session variable. The External Identity mapping can refer to a CGI environment variable or an HTTP header variable. • Special characters are not supported. The following rules apply: • The character \ is used to escape the characters in the function parameters.)} ${replace(${environment("REMOTE_USER")}. and folders as the Bind user. Installation and Configuration Guide 137 . For information. The resolved value of the External Identity mapping property at runtime must be a valid user DN. see the online help for Cognos Configuration. You can apply limited expression editing to the External Identity mapping property using the replace operation. All users who log on to Cognos 8 using external identity mapping see the same users. Include the token ${environment("USER_PRINCIPAL")} in the value for the property. The substring that replaces the old substring.old. Active Directory Server. When an LDAP namespace is configured to use the External Identity mapping property for authentication. Syntax ${replace(str. Characters such as \ and " need escaping. NTLM. you must specify the path and name of the certificate database in the SSL certificate database for the LDAP server. • Nested function calls are not supported. provided that you installed Content Manager on a non-Linux computer. or SiteMinder namespace depending on your SiteMinder configuration. and NTLM user directories. If you want Cognos 8 components to work with applications that use Java or application server security. For more information. Enabling Single Signon Between LDAP and Cognos 8 Components You achieve single signon to Cognos 8 components by configuring the External Identity mapping property. see the documentation for the LDAP server."NAMERICA\\". the LDAP provider binds to the directory server using the Bind user DN and password or using anonymous if no value is specified. Replace Operation The replace operation returns a copy of the string with all occurrences of the old substring replaced by the new substring. In the case of an application server gateway or dispatcher entry pointing to Cognos 8 components. To configure an authentication provider in a SiteMinder environment."NAMERICA\\". Supported SiteMinder configurations are LDAP. groups. you configure an LDAP.

2. under the Authentication component. 3. In the Explorer window. On the computer where you installed Content Manager. Note: When configuring a corresponding LDAP namespace. you must use the SiteMinder namespace. In this case. Namespace. In the Properties window. 139) namespace. 4. you must verify the Agent Configuration Object properties in SiteMinder Policy Server. you must also add a corresponding LDAP or NTLM namespace to the Cognos configuration for each user directory defined in SiteMinder. referring to one user directory that is an NTLM namespace. for the Namespace ID property. specify a unique identifier for the namespace. do the following: ❑ Configure Cognos 8 components to use a SiteMinder namespace ❑ Enable secure communication to the SiteMinder user directory. If you want to use the user directory as your authentication source directly instead of configuring a SiteMinder namespace. the SiteMinder namespace is not required. if required ❑ Enable single signon between SiteMinder and Cognos 8 ❑ Protect the Cognos Web alias. you must use the SiteMinder namespace. 5. and click New resource.Chapter 7: Configuring Cognos 8 If you configured SiteMinder for more than one user directory. you must use an LDAP namespace that is configured for use with Active Directory. or you can configure the SiteMinder provider with one user directory. The Cognos SiteMinder namespace passes user information internally to the corresponding LDAP namespace when it receives successful user identification from the SiteMinder environment. configure the appropriate LDAP (p. Note: When configuring the LDAP namespace in this case. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. If SiteMinder is configured with only one user directory. In the Name box. Tip: Do not use colons (:) in the Namespace ID property. Configure a SiteMinder Namespace If you configured SiteMinder for more than one user directory. you can configure Cognos 8 components with an NTLM namespace or configure Cognos 8 components with one SiteMinder namespace. open Cognos Configuration. Ensure that SetRemoteUser is activated. If the SiteMinder user directory is Active Directory. In the Type list. you must ensure that the External identity mapping property is enabled and that you include the token REMOTE_USER in the value for the property. This does not mean that Netegrity SiteMinder must be configured to set REMOTE_USER. click the Netegrity SiteMinder namespace and then click OK. To use a SiteMinder namespace and to set up single signon. right-click Authentication. You can also configure a SiteMinder namespace if users are stored in • an LDAP server • an NTLM server • an Active Directory server Steps 1. 138 . type a name for your authentication namespace. 131) or NTLM (p. For example. you must ensure that the External identity mapping property is enabled and that you include the token REMOTE_USER in the value for the property. After configuring the SiteMinder namespace in Cognos 8 components. You can use the user directory as your authentication source by configuring the appropriate namespace. After adding the SiteMinder namespace. The new authentication provider resource appears in the Explorer window. you must also add a corresponding LDAP or NTLM namespace for each user directory. if the SiteMinder user directory is NTML. 6. under Security.

For more information. In the Name box. 61). Protecting the Cognos Web Alias SiteMinder must be configured correctly to protect the Cognos Web alias. Integrated Windows Authentication is used for single signon and no additional configuration is required. type a name for the policy server and click OK. do the following: ❑ Configure Cognos 8 components to use an NTLM namespace ❑ Enable single signon between NTLM and Cognos 8 components Installation and Configuration Guide 139 . In the Properties window. In the Explorer window. From the File menu. and configures the provider libraries for the namespace. and authorized. Authentication. User directory. you must verify the Agent Configuration Object properties in the SiteMinder Policy Server. In the Explorer window. Configure a corresponding LDAP or NTLM namespace for each LDAP or NTLM user directory. as the authentication source. type a name for the user directory and click OK. For more information about configuring Web aliases. 11. For more information. 131). initializes. right-click the new SiteMinder Policy Server and click New resource. To use NTLM and to set up single signon. 9. specify the Host property and any other property values you want to change. 13. you must appropriately configure the Cognos namespace for the user directory. Configuring Cognos 8 Components to Use an NTLM Namespace You can configure Cognos 8 components to use the Windows native security. Enable Single Signon Between SiteMinder and Cognos 8 By configuring single signon. see "Configure an LDAP Namespace" (p. If the SiteMinder user directory is NTLM. Ensure that SetRemoteUser is activated. under Security. you are not prompted to reenter authentication information. you must configure the SiteMinder user directory to use external identity mapping to the REMOTE_USER environment variable. Test the connection to a new namespace. 8. 14. right-click the Netegrity namespace and click New resource. under Authentication. click Save. If you are not using NTLM in your IS environment. In the Explorer window. you cannot use an NTLM namespace. 12. right-click the new authentication resource and click Test. In the Name box. SiteMinder Policy Server. NT LAN Manager (NTLM). Enabling Secure Communication to the SiteMinder User Directory If you use an SSL connection to the directory server. 10. Cognos 8 components automatically refer to the SiteMinder session cookie for user session data. authenticated. Important: Ensure that you use the same value for the Namespace ID property that you use for the Namespace ID property for the SiteMinder namespace. 15. Important: The name of the user directory must match the name that appears on the policy server. see "Configure the Web Server" (p. Use the SiteMinder test tool provided with SiteMinder to verify that the resource is protected. Cognos 8 loads. see your SiteMinder documentation. type a value for the Namespace ID reference property. In the Properties window. If you want to use an NTLM user directory as your authentication source with Netegrity SiteMinder.Chapter 7: Configuring Cognos 8 7. If the SiteMinder user directory is LDAP. Tip: Configure a user directory for each user directory in the SiteMinder policy server.

users or administrators. 3. Steps 1. The NTLM user directory may also be accessed using a Netegrity SiteMinder authentication provider. you can assign users to user groups or roles or both. 7. Test the connection to a new namespace. Cognos 8 loads. The new authentication provider resource appears in the Explorer window. Configuring Cognos 8 to Use SAP To use an SAP server as your authentication provider. The SAP authentication provider uses only the roles. The authorization rights required by the SAP user depend on who uses Cognos 8 components. 4. 8. click NTLM and click OK. Install Content Manager on a computer that is part of the domain. under Security. to be trusted for delegation. Set up the computers. or the user account under which Content Manager runs. 2. 3. right-click the new authentication resource and click Test. for the Namespace ID property. 140 . Tip: Do not use colons (:) in the Namespace ID property. In the Name box. specify a unique identifier for the namespace. In the Explorer window. you are not prompted to reenter authentication information when accessing Cognos content that is secured by the NTLM namespace. In SAP BW. Specify the values for all other required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. On the computer where you installed Content Manager. In the Properties window. and click New resource. Set up Windows Integrated Authenticated on the IIS Web server. From the File menu. the Cognos NTLM provider integrates with the IIS Web server for single signon if Windows Integrated Authentication (formerly named NT Challenge Response) is enabled on the IIS Web server. In the Explorer window. under Authentication. Enable Single Signon Between NTLM and Cognos 8 Components By default. Namespace. under the Authentication component. and configures the provider libraries for the namespace. In the Type list. open Cognos Configuration. Content Manager must be installed on a non-Linux computer. you must use SAP BW version 3. Steps 1. In addition. click Save. If Windows Integrated Authentication is enabled. 2.Chapter 7: Configuring Cognos 8 Configure an NTLM Namespace You can configure Cognos 8 components to use an NTLM namespace when users are stored in an NTLM user directory. initializes. right-click Authentication.0 B or later. type a name for your authentication namespace. 6. 5. for the active and standby Content Manager computers.

are default values that you may want to modify for your environment. Some of the values shown.so_directory> • HPUX SHLIB_PATH=$SHLIB_PATH:<librfccm. SUSO FUGR 03 Field Activity Value 16 SAP Authorization Settings for Cognos Administrators If users will perform administrative tasks and searches for users and roles. do the following: ❑ Configure Cognos 8 components to use an SAP namespace ❑ Enable single signon between SAP and Cognos 8 components Installation and Configuration Guide 141 . SOA3 FUGR Field Activity Value 16 Connectivity Between SAP BW and Cognos 8 on UNIX To configure connectivity between SAP BW and Cognos 8 components on a UNIX operating system. SDTX. such as *.Chapter 7: Configuring Cognos 8 SAP Authorization Settings for Cognos 8 Users The following authorization objects are required for any Cognos user. SH3A.a_directory> To use SAP and to set up single signon. SYST. such as *. Authorization object S_RFC Authorization check for RFC access RFC_NAME Type of RFC object to be protected PRGN_J2EE. are default values that you may want to modify for your environment. Some of the values shown. SU_USER. ensure that you install the SAP shared library file (provided by SAP) and add it to the library path environment variable as follows: • Solaris LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<librfccm. Authorization object S_RFC Authorization check for RFC access Name of RCF to be protected Type of RFC object to be protected S_USER_GRP User Master Maintenance: User Groups Name of user group * Activity RFC1 RS_UNIFICATION. the following values must be added to the S_RFC authorization object in addition to the values listed above for Cognos 8 users. SHSS.sl_directory> • AIX LIBPATH=$LIBPATH:<librfc.

The new authentication provider resource appears in the Explorer window. under Security. In the Explorer window. type a name for your authentication namespace. and configure the provider libraries for the namespace. Cognos 8 components load. 6. specify a unique identifier for the namespace. To test the configuration for all namespaces. initialize. initialize. Test the connection to a new namespace. Namespace. 3. In the Type list. To do so. right-click Authentication and click Test. It contains authentication data that pertains to all users and is required to save the configuration. Tip: To cancel a namespace test. Cognos 8 loads. Depending on your environment. and configure the provider libraries for one namespace before testing the next namespace. 5. 7. initializes. Delete an Authentication Provider If they are no longer required. In the Explorer window. You can test all namespaces at the same time or test them individually. for the Host property. From the File menu. To test the configuration for a single namespace. right-click Authentication. right-click the new authentication resource and click Test. 8. for the Namespace ID property. The test stops when the current namespace test is complete. under Authentication. Specify the values for all required properties to ensure that Cognos 8 components can locate and use your existing authentication provider. under Authentication. set the following system parameters on the SAP BW server: • login/accept_sso2_ticket = 1 • login/create_sso2_ticket = 1 • login/ticket_expiration_time = 200 Test the Namespaces After you configure one or more new namespaces for Cognos 8 components. In the Name box. Tip: Do not use colons (:) in the Namespace ID property. open Cognos Configuration. Steps 1. do the following: • In the Explorer window. and click New resource. Important: You must not delete the Cognos namespace. Enable Single Signon Between SAP and Cognos 8 You can enable single signon between SAP Enterprise Portal and Cognos 8 components as well as when using the external namespace function of the SAP BW data source connections. you may have to add the SAP router string to the SAP host name. you can test the namespaces. 2. 142 . Cognos 8 components load. do the following: • In the Explorer window. In the Properties window. The test can occur before or after you start the Cognos 8 service. right-click the new authentication resource and click Test. 4. click SAP and then click OK. click Save. On the computer where you installed Content Manager.Chapter 7: Configuring Cognos 8 Configure an SAP Namespace You can configure Cognos 8 components to use an SAP server as the authentication source. under the Authentication component. you can delete namespaces that you added or unconfigured namespaces that Cognos 8 components detected after an upgrade. and configures the provider libraries for the namespace. click Cancel.

5. From the File menu. For more information. you can no longer log on to the namespace. under Security. The namespace disappears from the Explorer window and you can no longer log on to the namespace on that computer. Authentication. it appears as Inactive in the portal. open Cognos Configuration. For more information. In the Explorer window. Installation and Configuration Guide 143 . Click Yes to confirm. 2. 3. Steps 1. On a computer where you installed Content Manager. 4. After you delete a namespace. right-click the namespace and click Delete. see the Administration and Security Guide.Chapter 7: Configuring Cognos 8 When you delete a namespace. Security data for the namespace remains in Content Manager until you permanently delete it in the portal. Repeat steps 1 to 4 for each computer where you installed Content Manager. You must now log on to the portal and permanently delete the data for the namespace. click Save. see the Administration and Security Guide.

Chapter 7: Configuring Cognos 8 144 .

Cognos 8 allows you to modify the context root value from the default of /p2pd or /ServletGateway. Web servers. see "Upgrade from ReportNet to Cognos 8 in an Application Server Environment" (p. This ensures that Cognos 8 does not affect any existing customer applications. do the following: ❑ Check that Cognos components are properly set up ❑ ❑ ❑ ❑ ❑ ❑ ❑ Back up any existing Cognos data and encryption keys. It is important to apply all required operating system patches and to use only the versions of third-party software that are supported for a Cognos product. For information about configuring a multi-server distributed installation of Cognos 8 in an application server environment. Cognos 8 can run within any of the following application servers: • IBM WebSphere Application Server • BEA WebLogic Server • SAP Web Application Server • Oracle Application Server Note: On Linux. 102). which can have a unique value. contact Cognos support (http://support. 155). and application servers on the Cognos support site (http://support.cognos. Cognos 8 can run using Tomcat and IBM WebSphere Application Server only. If you are upgrading from Metrics Manager to Cognos 8 Metrics Manager.com). browsers. In a distributed Cognos 8 environment. database servers. with the exception of the servlet gateway application. your product may not work properly. patches.Chapter 8: Changing Application Servers Cognos 8 installs and uses Tomcat as the application server by default. Cognos 8 must be installed in a JVM instance that is separate from the application server admin processes to isolate both Cognos 8 and the administrative functions of the application server.com). Cognos 8 must be run in a Java Virtual Machine (JVM) instance isolated from other existing applications. such as operating systems. To eliminate potential java class or system resource conflicts. An isolated JVM instance can be established by creating one of the following: • a separate server instance in IBM WebSphere • a separate managed server in BEA WebLogic • a separate OC4J instance in Oracle 10g Application Server • a separate Java instance for SAP Web Application Server If you are upgrading from ReportNet to Cognos 8 ReportNet. if required Installation and Configuration Guide 145 .cognos. if necessary Configure application server properties and deploy Cognos 8 Enable SSL. directory servers. see "Configure a Servlet Gateway" (p. Otherwise. If you do not want to use Tomcat. if required Set environment variables Copy Cognos security provider files to the Java Virtual Machine (JVM) environment Configure Cognos components to run within the application server Change the application server startup script. see "Upgrade from Metrics Manager to Cognos 8 in an Application Server Environment" (p. 155). the context root for all application deployments must be the same. To set up Cognos 8 to run on your application server. For more information about setting up the servlet gateway. You can view an up-to-date list of environments supported by Cognos products.

it is important to back up the previous keys. • cryptographic keys by saving them to an alternate location. This group must contain the user that starts the application server and the user that owns the Cognos files. ❑ Before you start Cognos 8. Spaces interfere with the internal scripts and command parameters. If you must use an install path that includes spaces. Before configuring Cognos 8 components to run on the new application server or JVM. 146 . 89). 43). see your application server documentation. • with a JVM from one vendor and you are changing to another JVM vendor. you can perform some additional configuration tasks to customize the behavior of Cognos components to better suit your reporting environment (p. look in the c8_location/configuration directory. use the 8. configuration information. if required (p. • configuration information by exporting it. and cryptographic keys to a directory that is protected from unauthorized or inappropriate access. Note: You must back up existing Cognos information within the working environment prior to upgrade. you can also use the application server user account to install and run Cognos components. Tip: We recommend that you create a new UNIX or Linux group named cognos8. Because these keys can be created only if the previous keys are deleted. Change the group ownership of the Cognos files to the cognos8 group and change the file permissions for all Cognos files to GROUP READABLE/WRITABLE/EXECUTABLE. and then test the database connectivity. Install and configure the database clients.3 DOS naming convention when referring to these locations. 88). You can also test your configuration (p. ❑ The application server is installed and operational on each computer where Cognos components are installed. Tip: To check if any cryptographic keys exist. For simplicity. encryptkeypair or signkeypair.Chapter 8: Changing Application Servers ❑ Configure the web server ❑ Unregister dispatchers that are no longer used ❑ Import any backed up content store data After setting up Cognos 8 to run on your application server. ❑ The application server user account has full access permissions for the Cognos installation. you must back up • content store data by creating a deployment export. the database for the content store must be set up. To ensure the security and integrity of your Cognos data. Tip: Do not use install paths that contain spaces for the application server or Cognos 8. Any encrypted data is decrypted during the export. Check the Setup of Cognos Components Ensure that the following is done before you set up Cognos components to run on the application server: ❑ Cognos components are installed (p. For more information about installation. back up the content store. New cryptographic keys must be created using the same JVM that the application server uses. Cryptographic keys exist if this directory includes the following subdirectories: csk. 58). Back Up Existing Cognos Information You must back up existing Cognos information if Cognos 8 components are running • on an application server (including Tomcat) and you are changing to an application server that ships with its own JVM.

Chapter 8: Changing Application Servers

Steps
1. If data exists in the content store, start the Cognos 8 service and export the entire content store using the Deployment tool. For enhanced security, you must password-protect the deployment export. This action backs up the existing data using a neutral encryption key. For more information, see the Administration and Security Guide. 2. In 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. You are prompted to acknowledge that the export is an unsecure operation. 3. Stop the Cognos 8 service: • If you use Tomcat, stop the Cognos 8 service and close Cognos Configuration. • If you use an application server other than Tomcat, shut down Cognos 8 in your environment. 4. Back up any existing cryptographic keys by saving the appropriate files and directories to an alternate location that is secure. The files are • c8_location/configuration/cogstartup.xml • c8_location/configuration/caSerial • c8_location/configuration/cogconfig.prefs • c8_location/configuration/coglocale.xml The directories are • c8_location/configuration/csk • c8_location/configuration/encryptkeypair • c8_location/configuration/signkeypair 5. Delete the caSerial and cogconfig.prefs files and the three directories: csk, encryptkeypair, and signkeypair. 6. Replace the c8_location/configuration/cogstartup.xml file with the file that contains the data exported from Cognos Configuration (for example, "decrypted.xml"). Important: In the c8_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 Cognos Configuration.

Set Environment Variables
You must set environment variables to identify the location of the JVM environment and the library path. You can set environment variables using any of the following methods: • On Windows, set a system or user variable, or edit the application server’s startup, environment 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. • On UNIX and Linux, set an environment variable in the user profile, or edit the application server’s startup or environment script. For information about editing an application server’s startup script, see "Change the Application Server Startup Script" (p. 150). Tip: Most application server versions ship with a script specifically intended for setting environment variables. For example, some WebSphere versions ship with setupCmdLine.bat or setupCmdLine.sh, WebLogic ships with setEnv.cmd or setEnv.sh, and Oracle ships with iasenv.bat or iasenv.sh. These scripts can be modified to set appropriate values for use with Cognos components. Most of these scripts set the JAVA_HOME environment variable by default.

Installation and Configuration Guide 147

Chapter 8: Changing Application Servers

Steps
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 should be set to reference it. Cognos Configuration uses this variable to create encryption keys for 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/jdk142_04 2. Append c8_location/bin to the appropriate environment variable. This variable is used to locate the Cognos library files. Operating system Windows AIX Solaris and Linux HPUX Environment variable PATH LIBPATH LD_LIBRARY_PATH SHLIB_PATH

Tip: To install multiple instances of Cognos 8 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. Note: The CRN_ROOT variable is no longer required in a non-clustered environment and should be removed if it was used in a previous installation.

Copy Cognos Security Provider Files
The Cognos security provider files must be located in the JVM environment used by your application server. These files provide additional encryption and decryption routines that are not supplied as part of a default JVM installation. To ensure security, encryption files must be loaded by the JVM using the java extensions directory.

Steps
1. Backup the JVM_version/jre/lib/ext directory if it exists. 2. Create one of the following directories if it does not exist in your JVM environment: For JDK, JVM_version/jre/lib/ext For JRE, JVM_version/lib/ext Some JVM distributions do not ship with either of these directories. 3. Copy the contents of the c8_location/bin/jre/1.3.1/lib/ext directory to the JVM_version/jre/lib/ext directory for the JVM environment. Important: Do not overwrite any existing files.

Configure Cognos Components to Run Within the Application Server
Cognos 8 must be configured with the application server configuration information, and the configuration must be saved to create new cryptographic keys. Cognos Configuration uses the JVM that is defined by the JAVA_HOME environment variable.

148

Chapter 8: Changing Application Servers Important: You must set the JAVA_HOME environment variable to the JVM supplied or used by the application server and then copy the security provider files before you run Cognos Configuration.

Steps
1. From the c8_location/bin directory, start Cognos Configuration: • On Windows, type cogconfig.bat in a command window or select Cognos Configuration from the Start menu. • On UNIX or Linux, type cogconfig.sh 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. 2. In the Explorer window of 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 component is installed. • All URIs for the dispatcher, including Dispatcher URIs for Gateway External dispatcher URI Internal dispatcher URI Dispatcher URI for external applications • Gateway URI • 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 URI as well. 3. Under Environment, Cognos 8 service, right-click Cognos 8, and then click Delete. The entry for the Cognos 8 service is used to configure environment settings for running under Tomcat. The entry is not required when using a different application server. 4. Complete other required configuration changes such as • specifying properties for the Content Manager database • entering user IDs and passwords If you used the default settings for the Cognos installation, you may only have to make minor changes to the default configuration settings (p. 89). You can review the configuration for single computer installations (p. 68) or for distributed installations (p. 74) to determine if there are any additional changes required. 5. Save the configuration. New cryptographic keys are created using the JVM that is defined by the JAVA_HOME variable. 6. 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 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. 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. It is not necessary to rebuild or redeploy the archive file when you make configuration changes because configuration information is stored externally. For WebLogic, you can use the Build Application wizard in Cognos Configuration to build the application to an expanded directory. For example, you put the application in C:\bea\user_projects\domins\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.

Installation and Configuration Guide 149

Chapter 8: Changing Application Servers For information about which type of application file, WAR or EAR, is supported in your environment, see your application server documentation. 7. Close Cognos Configuration.

Change the Application Server Startup Script
Some application servers have specific requirements that you must meet before you can run Cognos 8. 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 BEA WebLogic Server, you must make changes to the application server startup script. The startup script must be modified to specify JVM settings. If you are using SAP Web Application Server 6.20, you must make changes to the application server startup script. The startup script must be modified to define Java command line arguments and memory settings. There are no changes required to the application server startup script for SAP Web Application Server 6.40. If you are using IBM WebSphere Application Server or Oracle Application Server, no changes to its startup script are required unless you want to add the environment variable changes to these scripts.

Steps for WebLogic
1. Create a WebLogic Server (WLS) domain for Cognos 8. For WebLogic 7.0, you can use the Domain Configuration Wizard to create the WLS domain. For WebLogic 8.1, you can use the Configuration Wizard to create the WLS domain. For information about creating domains, see the WebLogic documentation. 2. Go to the appropriate directory and open the application server startup script in an editor: Directory WebLogic7.0_ location/user_projects /domain_name WebLogic8.1_ location/user_projects /domains/ domain_name UNIX file startWebLogic.sh Windows file startWebLogic.cmd

startWebLogic.sh

startWebLogic.cmd

3. 4.

5.

6. 7. 150

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 (UNIX) or startManagedWebLogic.cmd (Windows). Select the JVM run mode, and change the default setting from JAVA_VM= to JAVA_VM=-server Modify the JAVA_OPTIONS for WebLogic 7.0.x and 8.1.x as follows: JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\ca certs -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser -Dweblogic.management.discover=false Set the minimum and maximum memory used by the JVM. Typically, the memory is set by adding or changing two JVM parameters: -Xms and -Xmx. For information about these parameters, see the JVM or application server documentation. Tip: A minimum of one-quarter of your physical memory (at least 512 MB) and a maximum of one-half of your physical memory are suggested starting values that you can change to suit your environment. Ensure that the production mode is enabled by changing STARTMODE= to STARTMODE=true Save and close the file.

bat • On UNIX. go to step 2.0: WebLogic_location/user_projects/domain_name For WebLogic 8. may be changed to better suit your environment. 3. Configure Application Server Properties and Deploy Cognos Components You must configure application server properties and deploy the Cognos components. Tip: A minimum of one-quarter of your physical memory. open SAP_location/cluster/server/go. For information about these parameters.Chapter 8: Changing Application Servers Steps for SAP Web Application Server 6. Steps for WebSphere 1. Open the application server startup script in an editor: • On Windows. Usually. see the JVM or application server documentation. 4. open SAP_location/cluster/server/go. Typically. Save and close the file. For information about these parameters. see the JVM or application server documentation. Set the memory used by the JVM. the memory is set by adding or changing two JVM parameters: -Xms and -Xmx. If you created a *. Install a new Enterprise Application using the archive file that contains the Cognos application. which can be used in most cases.sh 2. The default context root is p2pd.1: WebLogic_location/user_projects/domain/domain_name Installation and Configuration Guide 151 . Verify that 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. 5. For example: -XX:MaxPermSize=64m For information about this parameter. Stop and then restart the WebSphere application server instance used for Cognos components. Create a new server instance into which the Cognos 8 application will be deployed. If you are using a JVM version prior to 1. you may need to set the MaxPermSize parameter in the Java command line arguments. The context root value used to deploy the application must be the same as the context root value entered in Cognos Configuration.1_08. 4.20 1. and then start the WebSphere Administrative Console. Steps for WebLogic 1. and a maximum of one-half of your physical memory (at least 512 MB) are suggested starting values that you can change to suit your environment. the memory is set by adding or changing the initial and maximum Java heap size.war file. 2.3. The following show example directory locations: For WebLogic 7. If you used the expanded directory option when building the application in Cognos Configuration. deploy the application manually: • Create a directory in a location that is accessible to the application server. giving the directory the same name as the context root. 3. such as the application name. Tip: A minimum of one-quarter of your physical memory to a maximum of one-half of your physical memory (at least 512 MB) are suggested starting values that you can change to suit your environment. Start the WebSphere Application Server. Set the memory used by the JVM. Other default application deployment values. see the JVM or application server documentation. 6.

For example. the HTTP service uses port 80. if appropriate) associated with the Cognos domain. extract the application . In the SAP J2EE Engine configuration tool. the period does not refer to the current directory. Start the dispatcher for the SAP Web Application Server. 2. Steps for SAP Web Application Server 6.20. Load the Cognos archive file you created named p2pd. make the following environment changes: • For the appropriate server. Using the Deploy tool. For information. 7. Ensure that the HTTP service for the appropriate dispatcher in the cluster is set to a port that is not being used by another program.ear file. see your application server documentation. by default. Verify that 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. 8. may be changed to better suit your environment. Stop and then restart the WebLogic Managed Server associated with the Cognos domain to activate the changes.war" . The context root value used to deploy the application must be the same as the context root value entered in Cognos Configuration. Start the WebLogic Administration Server (and the WebLogic Managed Server. WebLogic_location/user_projects/domain_name/app_directory For WebLogic 8. Important: A space and then a period are required at the end of the command.0. • Check default parameters to ensure that the values are appropriate. If you created a WAR file instead of an EAR file. you can generate the EAR file from the WAR file. 3. 4. Start the state controller for Sap Web Application Server 6. 2. For WebLogic 7. such as the application name.20. 3. configure a new Web application as follows: • Set the application name. 4. Steps for SAP Web Application Server 6. SP23 1. Other default application deployment values. 6. Verify that 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. which may be too short. cognos8 • Set the path to the directory where the expanded application files are located. Start the server for the SAP Web Application Server. WebLogic_location/user_projects/domains/domain_name/app_directory Note: To use the custom loader. You may also need to increase the Keep Alive time-out from the default value of 15 seconds. Save the project. do not select the application WAR file from installation_location when deploying. Open the configuration tool by typing 152 . Set the reload period for the Web application to -1 to improve performance. set the Enable Chunked Response parameter to True.Chapter 8: Changing Application Servers The default context root and application directory name is p2pd.war file to the WebLogic installation using the following command from a command prompt: WebLogic_location/jdk_version/bin/jar xvfm "installation_location/application. This will prevent WebLogic from checking for updated application files.ear. Use the Deploy tool to create a new project. 6. 9. In the WebLogic console. connect to the Administration tool and deploy the p2pd. For example. In this command. • From the directory you just created. 5. 5.40 on Windows 1.1. which can be used in most cases.

5 GB of memory. add an environment variable.xerces. Dispatcher_IDxxxxxxx.apache. Under Global Properties. For information. You can generate the EAR file from the WAR file.ear. Operating system Windows AIX Solaris HPUX Environment variable PATH LIBPATH LD_LIBRARY_PATH SHLIB_PATH 5.ear) file. Set the memory used by the JVM.xml. 8. you may have issues when you run SAP Web Application Server. connect to the Administration tool and deploy the p2pd. 13. 10. In the Java parameters box. Installation and Configuration Guide 153 . When you are prompted to start the application. you would type D:\usr\sap\J2E\JC00\j2ee\configtool\configtool.sax.ear file. Load the Cognos archive file you created named p2pd.Chapter 8: Changing Application Servers drive:\usr\sap\sapid\JCxx\j2ee\configtool\configtool. 2. Restart the server by using the SAP Management Console or by restarting the services in Services. 7. In the server properties. type -Dorg. For information about these parameters.parsers. highlight KeepAliveTimeout and type a higher number and then click Set. 4. services. to a maximum of one-half of your physical memory (at least 512 MB) are suggested starting values that you can change to suit your environment. 3. 5.bat When prompted to use the default DB settings. Using the Deploy tool.war) or enterprise archive (. Tip: We suggest a KeepAliveTimeout number of at least 60. 12. where xxxxxxx is the ID number for your installation. click Yes. Steps for Oracle Application Server 1. If your computer has less than 1. that references the installation_location/bin directory. Tip: A minimum of one-quarter of your physical memory. For more information. 14. the memory is set by adding or changing two JVM parameters: -Xms and -Xmx. The value of the Map to URL parameter must be the same as the context root value entered in Cognos Configuration. 3.SAXParser Save the changes. 2. Under cluster-data. 11. see the JVM or application server documentation. You are prompted to restart the server. see SAP Note 723909 in the SAP Support Portal. Typically. instance_IDxxxxxxx. highlight http. Deploy the Cognos web archive (. 9. as listed in the following table. 6. click Yes. if the SAP ID is J2E and the installation is on drive D.bat For example.driver=org. Set the memory used by the JVM. Under cluster-data. Create an OC4J instance for Cognos components to run within. 4. instance_IDxxxxxxx. In the server properties. Follow the recommendations from SAP. highlight Server_IDxxxxxxx. add "-userThreads" to the OC4J Options. see your application server documentation. Use the Deploy tool to create a new project. Save the project.

contact Cognos Customer Support (http://support. click Server Administration.cognos. The dispatcher information is removed from Content Manager. see "Configure the Web Server" (p. Configure the application server to use SSL. For information about configuring the WebSphere Web server plugin. on the toolbar.com). Configuring the Web Server If you are using a Web server in your environment. 61)./configuration/signkeypair/jCAKeystore -p password • On UNIX or Linux. To access this tool. 3.cer -D . 2. Copy the CA certificate to the installation_location/bin directory and rename the file to ca. click OK. refer to the application server documentation. you must also enable SSL in the application server environment. You then identify the SSL server certificate to Cognos components. An SSL server certificate is generated by a third-party Certificate Authority (CA).cer. unregister any Tomcat dispatchers that are now running under the application server. For information about configuring the web server. On the portal toolbar. unregister any Cognos dispatchers that were previously registered and that are no longer used. Steps 1. 154 . The certificate of the CA that generated the SSL server certificate is also provided.509 format. From the installation_location/bin directory: • On Windows. Open Cognos Connection. For example. configure it now. 4. Start the OC4J instance that you created for Cognos components. 3.sh -T -i -r ca. type: ThirdPartyCertificateTool. 2. For more information./configuration/signkeypair/jCAKeystore -p password Important: You must type jCAKeystore as the name of the CA key store. click the unregister button. you must have execute permissions for the Administration secured function. Unregister Dispatchers After you start the application server and the Cognos application. 7. This file must be Base-64 encoded X. You remove dispatchers using the server administration tool.bat -T -i -r ca.Chapter 8: Changing Application Servers 6.cer -D .. Select the check box for the dispatcher you want to unregister and. In the confirmation dialog. type: ThirdPartyCertificateTool. Tip: You can also unregister dispatchers by clicking More in the Actions column. Steps 1. Enable SSL If you use the Secure Socket Layer (SSL) for Cognos components. Verify that 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..

Also. For more information.0. 38). Step To import the content store data. In WebLogic 8. Back up your existing ReportNet information (p. 43). Installation and Configuration Guide 155 . Most installations must perform the following: • Configure Cognos 8 to run within the application server. remove any ReportNet . 146). import the deployment to restore and encrypt the data using the new encryption keys.Chapter 8: Changing Application Servers Import Content Store Data If you exported the content store before setting up Cognos components to run in your application server (p. Follow the appropriate instructions in this chapter for changing to your application server. 4. the cache location is %WL_HOME%\user_projects\domains\domain-name\ managed-server-name\. Follow the procedure to upgrade Metrics Manager to Cognos 8 (p. perform the following steps. Upgrade from ReportNet to Cognos 8 in an Application Server Environment If you are upgrading from ReportNet to Cognos 8. To activate new features after upgrading. in WebLogic 7. see your application server documentation. 146). Uninstall ReportNet (p. delete the directory. 177).1. Most installations must perform the following: • Configure Cognos 8 to Run within the application server. For information about undeploying applications. start Cognos 8 and import the entire content store using the Deployment tool. and then restart the services. . Use the administrative tools for your application server to undeploy the ReportNet application. Install Cognos 8 (p. • Configure application server properties and deploy Cognos 8. 6. Steps 1. perform the following steps.jar files are sometimes left in %WL_HOME%\user_projects\domain-name\ managed-server-name\. 2. save the configuration in Cognos Configuration.wlnotdelete\crn_p2pd_p2pd\jarfiles You can remove them by deleting the WEB-INF directory. 2. Follow the appropriate instructions in this chapter for changing to your application server.wlnotdelete\extract\crn_p2pd_p2pd\ jarfiles 3.jar files that are cached in your application server environment. Upgrade from Metrics Manager to Cognos 8 in an Application Server Environment If you are upgrading from Metrics Manager to Cognos 8. For example. If the directory to which ReportNet was originally deployed is not removed during the undeploy process. see the Administration and Security Guide. Steps 1. 5. • Configure application server properties and deploy Cognos 8.

To activate new features after upgrading.Chapter 8: Changing Application Servers 3. and then restart the services. 156 . you must save the configuration in Cognos Configuration.

Text hotspot server classic Installation and Configuration Guide 157 . For more information. you can change the type of Java Virtual Machine (JVM) that Cognos 8 components use. if you are using JavaSoft Solaris JDK 1. go to c8_location/bin/jre/jre_version/lib. based on the following criteria: • Java HotSpot Client VM Use this JVM for proof of concept. Change the Type of JVM Used by Cognos 8 To better suit your reporting environment. This JVM is specially tuned to reduce both the startup time for applications and the memory footprint.4 JDKs. Not all Java Development Kits (JDKs) have a Classic VM. You cannot use Cognos Configuration to make these changes. or development environments. you may have to use the Classic VM. Save and close the file. Go to the location where your Java Runtime Environment (JRE) libraries are installed: • In Windows. you have only the HotSpot VM. demonstration. This is the default setting for Cognos installations on Windows. Ensure that the JVM that you want to use is the first uncommented line.cfg in an editor.Chapter 9: Advanced Configuration Options Advanced configuration options are changes that you make after installation to the configuration properties of the resources that Cognos 8 components use. • In UNIX or Linux. Enter the appropriate text for the JVM you want to use: JVM Hotspot Client Hotspot Client Classic 4. Therefore. improve performance. Web site. 3. Cognos does not provide a Java Runtime Environment (JRE). Open jvm. or change the default behavior of Cognos 8 components. • Java HotSpot Server VM Use this JVM for long-running server applications to maximize operating speeds when performance is more important than fast startup time.3 or any of the JavaSoft 1. In UNIX or Linux. Steps 1. 2. go to JAVA_HOME/jre/lib. On UNIX and Linux platforms. Advanced configuration options enhance security. the default JVM that Cognos 8 components use depends on the current setting in your existing JRE. • Classic VM For compatibility reasons. see the Sun Microsystems Inc.

4. some configuration changes are required. Tip: To check if any cryptographic keys exist. If you are using Cognos 8 components in an application server environment. encryptkeypair or signkeypair. To ensure the security and integrity of your Cognos data.4.1.4 may be appropriate in the following situations: • You want to use Cognos 8 components with an application server that requires Java 1. Because these keys can be created only if the previous keys are deleted. if required.Chapter 9: Advanced Configuration Options Changing the Version of JVM Used by Cognos 8 Components Cognos 8 components require Java to operate and supports versions starting at Java 1. If data exists in the content store. The process includes steps for changing to Java 1. use a name such as "decrypted. New cryptographic keys must be created using the same JVM that the application server uses. look in the c8_location/configuration directory. do the following: ❑ Back up existing Cognos data and encryption keys.xml". you must back up • content store data by creating a deployment export.4. if required. • You already use Java 1.4 is installed. and cryptographic keys to a directory that is protected from unauthorized or inappropriate access. see the Administration and Security Guide. In Cognos Configuration. follow the process in "Changing Application Servers" (p. • You want to use Thai characters with Cognos 8 components.3. On Windows. Cognos Configuration and other Cognos 8 components use the JRE referenced by the JAVA_HOME environment variable. back up the content store. Any encrypted data is decrypted during the export. click Export As and save the configuration information in a decrypted format. Export the data to a directory that is protected from unauthorized or inappropriate access. Back Up Cognos Data You must back up existing Cognos information if Cognos 8 components are running • on an application server (including Tomcat) and you are changing to an application server that ships with its own JVM. Before configuring Cognos 8 components to run on the new application server or JVM. For more information. When naming the file. Before you begin. Changing to Java 1. ensure that Cognos 8 components are installed and that Java 1. 2. you must password-protect the deployment export. if JAVA_HOME is not set. Cryptographic keys exist if this directory includes the following subdirectories: csk. If you want to use Java 1. Note: You must back up existing Cognos information within the working environment prior to upgrade. start the Cognos 8 service and export the entire content store using the Deployment tool. To change to Java 1. 145). the JRE that is packaged with Cognos 8 components is used by default. it is important to back up the previous keys. configuration information. • cryptographic keys by saving them to an alternate location. • configuration information by exporting it. ❑ Import data to the content store.4. ❑ Copy Cognos security provider files to the Java Virtual Machine (JVM) environment. from the File menu. You are prompted to acknowledge that the export is an unsecure operation. 158 . Steps 1. This action backs up the existing data using a neutral encryption key. For enhanced security.4 with other applications. The tasks in this section are for a Cognos installation that uses Tomcat. • with a JVM from one vendor and you are changing to another JVM vendor.

JVM_version/jre/lib/ext • For JRE. Steps 1. Copy the contents of the c8_location/bin/jre/1. import the deployment to restore and encrypt the data using the new encryption keys. If you do.jar) files. Create the following directory if it does not exist in your JVM environment: • For JDK. 3. Important: Do not overwrite any existing Java Archive (.xml The directories are • c8_location/configuration/csk • c8_location/configuration/encryptkeypair • c8_location/configuration/signkeypair 5. encryptkeypair. start the Cognos 8 service and import the entire content store using the Deployment tool. Replace the c8_location/configuration/cogstartup. existing applications may not work. 6.prefs • c8_location/configuration/coglocale. • If you use an application server other than Tomcat. 4. Save the configuration. Start Cognos Configuration. 2. The information in this file will be automatically re-encrypted using new cryptographic keys when you save the configuration in Cognos Configuration. Stop the Cognos 8 service: • If you use Tomcat. The files are • c8_location/configuration/cogstartup. Important: In the c8_location/configuration directory.3. "decrypted. For more information.xml").prefs files and the three directories: csk. and signkeypair.Chapter 9: Advanced Configuration Options 3. Installation and Configuration Guide 159 . see the Administration and Security Guide. stop the Cognos 8 service and close Cognos Configuration. shut down Cognos 8 in your environment. JVM_version/lib/ext Some JVM distributions do not ship with this directory. Delete the caSerial and cogconfig.xml file with the file that contains the data exported from Cognos Configuration (for example.xml". the file must use the name "cogstartup.1/lib/ext directory to the JVM_version extension directory for the JVM environment. Import Content Store Data If you exported the content store before changing the JVM.xml • c8_location/configuration/caSerial • c8_location/configuration/cogconfig. Cognos Configuration generates new keys and encrypts the data. Step To import the content store data. Copy Cognos Security Provider Files The Cognos security provider files must be located in the JVM environment for the new version of Java. Back up any existing cryptographic keys by saving the appropriate files and directories to an alternate location that is secure. 4.

To configure Cognos 8 components to use your third-party certificate authority. if you already have an existing third-party certificate authority. Default: RSA -D Directory location Work with the signing identity Work with the encryption identity Work with the trust store (only with -i) Create a new CSR Import a certificate Description 160 . ensure that you specify the same information in both the command line utility tool and in Cognos Configuration. such as iPlanet or Microsoft. You can configure Cognos 8 components to use another certificate authority.Chapter 9: Advanced Configuration Options Configuring Cognos 8 Components to Use a Third-party Certificate Authority By default. The following table lists the options for the command-line tool used to generate keys and signing requests. Cognos 8 components use their own certificate authority (CA) service to establish the root of trust in the Cognos security infrastructure. you must ❑ generate Cognos security keys and certificate signing requests to use with your third-party CA ❑ submit the Cognos security keys and certificates to your third-party certificate authority ❑ configure Cognos 8 components to use a third-party certificate authority Generate Keys and Certificate Signing Requests Use the command line utility to generate all the keys for the Cognos key stores and to generate the certificate signing requests (CSR). RSA or DSA. Command Main operation mode -c -i Operation modifiers -s -e -T Information Flags -d -r -t -p -a DN to use for certificate CSR or certificate file location (depends on mode) certificate authority certificate file (only with -i) Key Store password (must be provided) Key pair algorithm. in your reporting environment. When you configure Cognos 8 components to use a third-party certificate authority.

csr -D .bat c -s -d "CN=SignCert./configuration/signkeypair/jSignKeystore -p password -t ca.csr -D . Create the certificate signing request for the encryption keys by typing the following command: On UNIX or Linux. Go to the c8_location/bin directory. Cryptography./configuration/encryptkeypair/jEncKeystore -p password Important: You must type jEncKeystore as the name of the encryption key store.O=MyCompany. type ThirdPartyCertificateTool.sh -c -e -d "CN=EncryptCert.cer On Windows.O=MyCompany. Create the certificate signing request for the signing keys by typing the following command: On UNIX or Linux.cer Important: You must type jSignKeystore as the name of the signing key store. Copy ca.O=MyCompany.. ensure that the directory specified for -D is the same as the one specified in the Signing key store location property under Security. The certificate authority produces a signing certificate and an encryption certificate. Copy the contents of the encryption certificate into a file called encryptCertificate. Installation and Configuration Guide 161 . signCertificate. Cognos in Cognos Configuration.. Cognos in Cognos Configuration.C=CA" -r signRequest./configuration/signkeypair/jSignKeystore -p password On Windows. 3. 4.C=CA password Steps 1. type ThirdPartyCertificateTool. Import the signing certificate from step 5 into the Cognos signing key store by typing the following command: On UNIX or Linux. type ThirdPartyCertificateTool./configuration/signkeypair/jSignKeystore -p password Important: You must type jSignKeystore as the name of the signing key store.O=MyCompany. Also.. 6./configuration/encryptkeypair/jEncKeystore -p password On Windows.509 format.C=CA" -r encryptRequest..Chapter 9: Advanced Configuration Options The following sample values are used: Property Signing certificate DN Encryption certificate DN Key store password Value CN=SignCert. and encryptCertificate.sh -i -s -r signCertificate.cer to c8_location/bin. 9. ensure that the directory specified for -D is the same as the one specified in the Signing key store location property under Security.cer -D . Also.cer.O=MyCompany./configuration/signkeypair/jSignKeystore -p password -t ca.. type ThirdPartyCertificateTool.cer.bat-i -s -r signCertificate. ensure that the directory specified for -D is the same as the one specified in the Encryption key store location property under Security. Copy the contents of the signing certificate into a file called signCertificate.cer 7. 2..C=CA CN=EncryptCert.cer 8.sh -c -s -d "CN=SignCert. These files must be Base-64 encoded X. type ThirdPartyCertificateTool. Also.O=MyCompany. Input the certificate signing request (CSR) files that were generated in steps 2 and 3 into the third party certificate authority. For more information.csr -D .C=CA" -r encryptRequest.csr -D .C=CA" -r signRequest. see your third-party CA documentation. 5.cer. Cryptography. Cognos in Cognos Configuration.cer -D .bat -c -e -d "CN=EncryptCert. Copy the contents of the CA certificate into a file called ca. type ThirdPartyCertificateTool. Tip: UNIX or Linux filenames are case-sensitive and must be entered exactly as shown. Cryptography.

click Cognos. Import the encryption certificate from step 6 into the Cognos encryption key store by typing the following command: On UNIX or Linux. Cognos in Cognos Configuration. From the File menu. click Save./configuration/signkeypair/jCAKeystore -p password On Windows.cer -D .Chapter 9: Advanced Configuration Options 10. type ThirdPartyCertificateTool. This action starts all installed services that are not running. Configure Cognos 8 Components to Run Within a Third-party Certificate Authority You must configure each Cognos computer to use an external certificate authority by setting the appropriate property in Cognos Configuration. from the Actions menu. Cryptography.bat -i -e -r encryptCertificate. Cognos 8 components assume that all required keys have been generated and vetted by the external certificate authority. Cognos in Cognos Configuration. Steps 1. type ThirdPartyCertificateTool.cer Important: You must type jEncKeystore as the name of the encryption key store. In the Properties window. If you want to start the Cognos 8 service. Import the CA certificate from step 7 into the Cognos trust store by typing the following command: On UNIX or Linux. Cryptography. By setting this property. Also. all properties for the certificate authority and identity name are ignored 4.bat -T -i -r ca. In the Explorer window. select the service node in the Explorer window and then click Start from the Actions menu. 6./configuration/encryptkeypair/jEncKeystore -p password -t ca. Cryptography.. click Start. Ensure that the key store locations and password in Cognos Configuration match the ones you typed in the command-line tool. If you want to start a particular service. Also..cer On Windows..sh -i -e -r encryptCertificate. 162 .cer -D . Note: When you set this property to true. Start Cognos Configuration 2. ensure that the directory specified for -D is the same as the one specified in the Encryption key store location property under Security. type ThirdPartyCertificateTool. ensure that the directory specified for -D is the same as the one specified in the Signing key store location property under Security. type ThirdPartyCertificateTool.sh -T -i -r ca. 3. click the Value box next to the Use third party CA property and then click True./configuration/encryptkeypair/jEncKeystore -p password -t ca.cer -D . Configure the following properties to match the ones you typed in the command line utility: • Signing key store location • Signing key store password • Encryption key store location • Encryption key store password • Certificate Authority key store password 5. 11.cer -D ./configuration/signkeypair/jCAKeystore -p password Important: You must type jCAKeystore as the name of the certificate authority key store.. under Security. under Certificate Authority settings property group.

configured. 165). configured. see "Set up DB2 Cube Sample" (p.tar. To use the DB2 cube sample. including Framework Manager or Metric Designer. configured.tar. Cognos 8 provides sample databases that contain sales and marketing information for a fictional company named the Great Outdoors Company that sells sporting equipment.tar. This action re-creates multilingual versions of the Great Outdoors databases.gz gosldw. For Cognos 8 reports and analysis. Database description Great Outdoors sales Great Outdoors retailers Great Outdoors sales data warehouse SQL Server file gosl gort gosldw Oracle file gosl.gz gohr. Installation and Configuration Guide 163 .gz gomr. you can use two sample cubes that are also provided.dmp gort. The following sample databases and associated files are provided with Cognos 8. Metric Designer must also be installed.tar.dmp gohr.dmp). Restore Backup Files for the Samples Databases To use the samples. Cognos 8 must be installed.dmp gomr. and you must extract them before you can restore the DB2 databases. Oracle export file (. The DB2 move files are compressed. 166).gz Great Outdoors market gomr research Great Outdoors human gohr resources Important: You must give the restored databases the same names as the backup or export file names for the samples to work. use Cognos 8 to run the sample reports or scorecards. You can later remove the Cognos 8 samples.gz gort. The names are case-sensitive. To use the sample content for Metric Designer. To set up a data source connection Cognos Series 7 PowerCube sample. Framework Manager must also be installed. Each database is delivered as a Microsoft SQL Server backup file. the optional modeling tool for Metric Studio.tar.Chapter 10: Setting Up the Samples You can use the Cognos samples to help you learn how to use Cognos 8. See "Set up Microsoft SQL Server Analysis Services Cube Samples" (p. Before you can use the sample databases. and DB2 move files. If you use Microsoft SQL Server Analysis Services. see "Create Data Source Connection to OLAP Data Sources" (p. you ❑ restore the samples databases ❑ create the data source connections ❑ import the sample package and other sample content into the content store After you complete these tasks.dmp DB2 file gosl. and running.dmp gosldw. and running. you must restore backup files for the samples databases. To set up the samples. and running. 166).

Tip: For SQL backup files. Cognos 8 uses this information to connect to the samples databases and run the sample reports or use the sample package. For each database. to restore the database.cognos. Steps 1. see the Microsoft SQL Server documentation or the Cognos Knowledge Base (http://support. click Tools. create at least one user who has Select permissions for all the tables in the restored databases. For more information. Before you restore the samples databases. 2. Click the new data source button. Before you create the data source connections.Chapter 10: Setting Up the Samples Ensure that you restore the samples databases using the UTF-8 character set. restore the database from a device and ensure that the restore locations are correct for the . You can now create the data source connections in the portal. 164 Open Cognos Connection. go to the sqlserver. the schema names that you type for the DB2 data sources must use uppercase letters. extract the DB2 move files by using the gnutar -xcvf DB2_move_filename or tar -xcvf DB2_move_filename command. or db2 directory located in c8_location/webcontent/samples/datasources/db. To create data sources. 4. you must edit the GOSLDWConnect. in Framework Manager. you must use Microsoft SQL Server 2000 or Microsoft SQL Server 7. DB2 Considerations Before you restore the DB2 move files on UNIX or Windows.bat file to create the views in the database. ensure that the Cognos 8 service is running.ldf and . you must have execute permissions for the Directory secured feature and traverse permissions for the Administration secured function. Also. . On the toolbar. Steps 1.mdf database files. Create Data Source Connections to the Samples Relational Databases You must create data source connections to the samples databases that you restored. Also. ensure that the TAR file smart CR/LF conversion option is not selected. If required. If you use WinZip to extract the DB2 move files on Windows. After you extract the DB2 move files. 4.com/kb-app/knowledgebase). To ensure the security and integrity of Cognos 8. Restore the samples databases using your database management tool. ensure that you have 50 MB of disk space available in the target location. On the computer where Cognos 8 is installed. 3. 3. 2. Directory. copy the files to a directory that is protected from unauthorized or inappropriate access. Ensure that TCP/IP connectivity is used for the SQL server. create a large buffer pool of 16 KB and an associated tablespace. SQL Server Considerations If you restore the SQL Server backup files. oracle. You must also run the CreateGOSLDWViews. copy the backup files for the samples databases to your database backup directory. you must restore the backup files for the samples databases. Also. when you set up the Great Outdoors Sales Data Warehouse database in DB2. Click the Data Sources tab.sql file and enter a username and password in the file. The DB2 database names that you type must use uppercase letters.

7. Use the Analysis Manager to restore the database from the GOSLDW.cab file to a directory that you can access from the Microsoft SQL Server Analysis Services Analysis Manager console. Query Studio. type the DB2 connection string. You can now import the samples unless there is a syntax error in the connection string or an incorrect parameter. in the Server Name box. In the Database name box. type GOSL • If you restored the samples databases in Oracle. Tip: To test whether the parameters are correct. Copy the GOSLDW. click Test. type the name of the server where the restored databases are located. You can now create the data source connections using either the Great Outdoors Company or Great Outdoors Finance cubes. select the Password and Create a signon that the Everyone group can use check boxes. 3.cab file. On the computer where Cognos 8 is installed. Installation and Configuration Guide 165 .Chapter 10: Setting Up the Samples 5. type GOSL using uppercase letters. 6. in the DB2 database name box. type goretailers for the data source name and gort for the database name. Do one of the following: • If you restored the samples databases in SQL Server. or 2006. This data is available only in English. The connection string page for the selected database appears.cab in the c8_location/webcontent/samples/datasources/cubes directory. go to the c8_location/webcontent/samples/datasources/cubes/MSAS/en directory. 9. select an isolation level. The Great Outdoors Company cube contains the same monthly sales data as the GOSLDW database. type the Oracle connection string. • For the gosldw database in SQL Server and Oracle. Click Finish. • If you restored the samples databases in DB2. type gosales and then click Next. Under Signons. 8. type go_data_warehouse for the data source name and gosldw for the database name. Set up Microsoft SQL Server Analysis Services Cube Samples Two sample Microsoft SQL Server Analysis Services cubes are provided which you can use from Cognos Connection or Framework Manager. The Great Outdoors Finance cube contains year-to-date financial data for income statements and balance sheet accounts that you can use to create model financial statements in Analysis Studio. click the type of database that you restored and want to connect to. 2. The Great Outdoors data source connections appear as entries in the Data Sources tab of the Directory tool. The sample cubes are contained in an archive file called GOSLDW. 10. type the user ID and password for the user that you created when you restored the databases. type go_data_warehouse for the data source name and GOSLDW for the database name. and then click Finish. In the DB2 connect string box. In the connection page. and Report Studio. For DB2. Note: The Great Outdoors Finance cube contains Actuals using US dollars submissions for 2004. and then click Next. In the Name box. Steps 1. Repeat steps 4 to 9 for the goretailers and gosldw samples databases. 2005. For DB2. The archive file must be restored to a Microsoft SQL Server database running Microsoft Analysis Services. in the SQL*Net connect string box. • For the goretailers database in SQL Server and Oracle. type goretailers for the data source name and GORT for the database name.

3. you must have Hyperion Essbase installed. On the toolbar. The connection string page for the selected database appears. and a DB2 OLAP Server with Essbase Integration Services Console. under type click Cognos PowerCube.xml using the GOSLDW database • Perform an outline member load and a data load Using Hyperion Solutions Essbase Administration. Click OK. Using Essbase Integration Services Console: • Import the Great_Outdoors_Company_Model. type the name of the server. 7. To test whether the parameters are correct. click the design language for the project. and publish it to Cognos Connection (p. In the connection page. Steps for PowerCube Open Cognos Connection. Directory. click Test.xml and the Great_Outdoors_Company_Model. The Import wizard appears.mdc file. click Tools. Tip: You must include the name of the file in the windows location. 166 . type the location of the Great_Outdoors_Company. In the Server name box. 5. Create Data Source Connection to OLAP Data Sources Cognos 8 provides the following OLAP samples: • Great Outdoors Company and Great Outdoors Finance Microsoft SQL Server Analysis Services cubes • Great Outdoors Company PowerCube • Great Outdoors DB2 cube You must create data source connections to the cubes to use the samples.Administration Console: • Set up the generations for the model and populate the cube You can now create a data source connection to the cube.Chapter 10: Setting Up the Samples Set up DB2 Cube Sample To set up the DB2 cube sample. For example. To create data sources. 6. specify a name and location for the project. 1. In the Select Language page. under type click IBM DB2 OLAP Server. Click the Data Sources tab.mdc. 6. In the New Project page. In the connection page. 2. 7. type great_outdoors_company and then click Next. 5. In the Windows location box. 3. 2. In the Name box. 8. The connection string page for the selected database appears. 4. 4. 166). and then click Next. you must have execute permissions for the Directory secured feature and traverse permissions for the Administration secured function. Click Finish. Steps for DB2 Cube 1. Click the new data source button. select an isolation level. 9. Open Framework Manager Click Create a new project. select an isolation level. type c8_location/webcontent/samples/content/datasources/cubes/PowerCubes/Great_Outdoors_ Company. and then click Next.

click the type of Microsoft SQL Server database that you restored and want to connect to. When prompted by the wizard. For more information.Chapter 10: Setting Up the Samples 8. ❑ Specify sources and collation codes for different languages in Metric Studio (p. Set up the Metric Studio Sample To set up the Metric Studio sample. Import Metric Data into Metric Store To import metric data into the metric store. 6. The connection string page for the selected database appears. In the Name box. you must • create a metric store called GOMETRICS. Directory. type the name of the server where the restored databases are located. type the name of the database you restored. Open Cognos Connection. Select January 1. Steps for Microsoft SQL Server Analysis Service Cubes 1. In the Server Name box. and then click Finish. 5. Quarters. 167). In the connection page. 9. To test whether the parameters are correct. • import the metric data into the metric store (p. 9. 3. 168). • create a data source connection in Cognos Connection to the GOMETRICS metric store. 2. click Test. • create a new metric package called GO Metrics that uses the GOMETRICS metric store. see the Framework Manager User Guide. do the following: ❑ Copy all text files from c8_location/webcontent/samples/datasources/metricdata/language_location to c8_location/deployment/cmm. 7. Click the Data Sources tab. 8. Click Finish. see the Metric Studio User Guide for Authors. 4. You must now publish the cube to Cognos Connection. click Test. If needed. in the Database name box. For more information. see "Metrics" in the Cognos 8 Administration and Security Guide. select the standard Gregorian calendar and accept the defaults for Years. click Tools. Click the new data source button. Import the files into the metric store (p. select an isolation level. type the user ID and password for the user that you created when you restored the databases. Under Signons. 2004 as the start date for a period of 3 years. and then click Next. Click Finish. 169). Installation and Configuration Guide 167 . and Months. Tip: To test whether the parameters are correct. For more information about creating metric packages. type great_outdoors_company or great_outdoors_finance and then click Next. select the Password and Create a signon that the Everyone group can use check boxes. On the toolbar.

Chapter 10: Setting Up the Samples Specify Sources for Different Languages The location of language folders and associated collation codes for different data sources follows. Language Chinese (Simplified) Description • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Folder name: zh-hans DB2 code page: 1381 or 1383 Oracle character set name: ZHS16CGB231280 SQL server 2K collation designator: Chinese_PRC_CI_AS Folder name: zh-hant DB2 code page: 950 Oracle character set name: ZHT16MSWIN950 SQL server 2K collation designator: Chinese_Taiwan_Stroke_CI_AS Folder name: nl DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Latin1_General_CI_AS Folder name: en DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Latin_General_CI_AS Folder name: fi DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Finnish_Swedish_CI_AS Folder name: fr DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: French_CI_AS Folder name: de DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Latin1_General_CI_AS Folder name: it DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Latin1_General_CI_AS Folder name: ja DB2 code page: 943 or 932 Oracle character set name: JA16SJIS SQL server 2K collation designator: Japanese_CI_AS Folder name: ko DB2 code page: 1363 or 970 Oracle character set name: KO16KSC5601 SQL server 2K collation designator: Korean_Wansung_CI_AS Chinese (Traditional) Dutch English Finnish French German Italian Japanese Korean 168 .

open the GO Metrics package by clicking the view metric package contents icon in the Actions column. click Metrics Maintenance.1. 9. such as Framework Manager packages. 7. Click Metric Maintenance. 8. 2. Click the Import and transfer data from files into metric store metric task. 4. Steps in Cognos Connection 1. and then type the directory name or file name. in the Tools list. If the folder includes sub-folders. type a descriptive name for the data source. Click New. Set up the Metric Designer Sample Metric Designer creates extracts that load data from different sources. or use wild cards. In the File format box.Chapter 10: Setting Up the Samples Language Portuguese Description • • • • • • • • • • • • Folder name: pt DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Latin1_General_CI_AS Folder name: es DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Modern_Spanish_CI_AS Folder name: sw DB2 code page: 1252 or 819 Oracle character set name: WE8ISO8859P1 SQL server 2K collation designator: Finnish_Swedish_CI_AS Spanish Swedish Steps 1. click Import Sources. into Metric Studio. click Include sub-folders. 2. In the Collation sequence box. 6. Extracts can be run from Metric Designer or Cognos Connection. To set up the Metric Designer sample. Specify the location of tab-delimited files. Steps in Metric Studio 1. in the Tools list. In Metric Studio. Import Files into the Metric Store You can now import the files into the metric store using either Cognos Connection or Metric Studio. You can now use the GO Metrics application in Metric Studio. type the collation code for the appropriate language and type of data source. you must Installation and Configuration Guide 169 . 3. Click Metrics import directory. In Cognos Connection. In the Name box. You can use the full path and name. Click OK. and click the Import and transfer data from files into metric store metric task. in Public Folders or My Folders. Tip: Click the button next to the name of an existing folder or click the button next to New directory. 2. In Metric Studio. 5. click 8.

click the new import button. For more information on locales.bat or event_studio_modify. Copy the zip file from the c8_location/webcontent/samples/content directory to the directory where your deployment archives are saved. You must also create data source connections to the samples databases. You can now import the GO_Events sample. In the upper-right corner. GO_Events) To use the sample package and other content. 3. The language that you select must be supported by your locale. see the configuration tool online help. 2. Steps 1. 171). Modify the GOSL Database Before you import the Event Studio sample. Cognos_PowerCube. you must have traverse permissions for the Administration secured function and execute permissions for the Content Administration feature. Steps 1. To use the Content Administration tool. The default location is c8_location/deployment. Enter the connection information for the customer database.zip deployment archive.Chapter 10: Setting Up the Samples • • • create the metric studio sample (p. The location is set in the configuration tool. you must modify the GOSL database for Event Studio. 4.zip deployment archives. 2. where database is db1. 170) ❑ "Import the Samples (Cognos_Samples. Open the file c8_location/webcontent/samples/db/database/ event_studio_modify. you must restore the databases. 170) When you are finished with the Event Studio samples. 170 . 164). 163) and set up a data source connection to it (p. For information about changing the location. you must import them from the sample deployment archive using the deployment tool. import the Cognos_Samples and GO_Metrics deployment archives (p. you must return the GOSL database to its original state (p.sh file. click Tools. you must create a database connection to the Great Outdoors Company PowerCube and select the language that you want to use. Cognos_PowerCube. GO_Metrics. 170). On the toolbar. 167). GO_Events)" (p. Before you import the Cognos_Samples. sqlserver. Import the Samples (Cognos_Samples. Content Administration.sh. GO_Metrics. Before you import the Cognos_PowerCube. see the Cognos 8 Installation and Configuration Guide. you must create one or more named users with Select permissions for the database tables. or Oracle. Run the event_studio_modify. restore the GOSLDW database (p.bat or event_studio_modify. Set up the Event Studio Sample To set up the Event Studio sample. For each database.zip and GO_Metrics. Open Cognos Connection. 3. if you want other samples to behave as described in the Cognos 8 Administration and Security Guide. you must: ❑ "Modify the GOSL Database" (p.

10. or GO_Events. In the Deployment Archive box. which refers to the samples databases gosl and gort Installation and Configuration Guide 171 . and then select frequency and start and end dates. The Cognos_Samples deployment archive has the following packages or folders: • GO Data Warehouse. and then click Next. Select the action that you want: • To run once now or later. • To save without scheduling or running. select the Disable the schedule check box. and Analysis Studio. select Cognos_Samples. where database is db1. then click Run. or create agents in Event Studio.sh. 7. click Finish. select the packages and folders that you want to import. The summary information appears. The Cognos_PowerCube deployment archive for the Great Oudoors Company has packages or folders for the following languages: • English • French • German • Japanese The GO_Metrics deployment archive has the following packages or folders: • GO Metrics The GO_Events deployment archive has the following packages or folders: • GO Events 9. GO Sales and Retailers. Click OK.bat or event_studio_unmodify. In the Specify the general options page. Cognos_Powercubes. Review the run time and click OK. along with your conflict resolution choice for options that you select. GO Sales. GO_Metrics. Click Next. Query Studio. you must return the GOSL database to its original state if you want other samples to behave as described in the Cognos 8 Administration and Security Guide. and who should own the entries after they are imported. click Save and schedule. When the import is submitted. Click Next. You can now use the sample packages to create reports and analysis in Report Studio. 11. Click Finish. select the folder where you want to save it. Select the options you want. 14. • To schedule at a recurring time. or Oracle. Tip: To temporarily disable the schedule. select whether to include access permissions and references to external namespaces. Type a unique name and an optional description and screen tip for the deployment archive. and then click Next. 12. sqlserver. Click Finish. click Save and run once. 13. click Save only and click Finish. 5. You can also run the sample reports that are available on the Public Folders tab in the portal. and Query Studio Templates. specify the time and date for the run. Complete this step: • Run the file c8_location/webcontent/samples/db/database/ event_studio_unmodify. 6. In the Public Folders Content box. Return the GOSL Database to the Original State (Event Studio) When you are finished with the Event Studio samples. Review the summary information and click Next. view extracts in Metric Designer.Chapter 10: Setting Up the Samples The New Import wizard appears. Sample Database Models The following sample models are provided with Cognos 8: • gosales_goretailers. 8.

This action generates a model named gosales_scriptplayer. To use the samples again. and publishes a package to the content store. The model accesses a dimensional relational data source. including Framework Manager. The Great Outdoors.Chapter 10: Setting Up the Samples • • • • go_data_warehouse. which refers to the samples databases gosl and gort go_events. Select the check box for the sample package you want to delete Click the delete button on the toolbar. GO Sales Scriptplayer These files can be used to run the action logs in sequence. 2. The model accesses a dimensional relational data source. 163). Open Cognos Connection. you must set up the samples (p. GO Data Warehouse Model This model contains financial information and human resources information for the fictional company. 3. and click OK. GO Sales Model This model contains sales analysis information for the fictional company. The Great Outdoors. Steps 1. The Great Outdoors. which refers to the database gosldw go_sales. which refers to the samples databases gosl and gort gosales_scriptplayer. Go Events Model This model contains sales analysis information for the fictional company. 172 . which refers to the samples databases gosl and gort GO Sales and Retailers Model This model contains sales analysis information and retailer information for the fictional company. This action permanently removes the samples from the content store. The model accesses two data sources. Click the Public Folders tab. Remove the Samples Databases from Cognos 8 You can delete the packages on which the samples are based after you finish using the sample reports to learn about Cognos 8. 4. The model accesses a dimensional relational data source. The Great Outdoors.

to your computer without being prompted for information. Copy the transfer specification file to the computer where you plan to install Cognos 8. • If you installed Cognos 8 for reporting. Therefore. To set up an unattended installation and configuration: ❑ configure a transfer specification file (. Installation and Configuration Guide 173 . 2. the file name is ts-CMM-version-yyyymmdd_hhmm. If you do not use the installation wizard to install components.ats that is available on the CD. the file name is ts-CRN-version-yyyymmdd_hhmm.ats file for your environment before you can use it for an unattended installation.ats.Chapter 11: Setting Up an Unattended Installation and Configuration Set up an unattended installation and configuration to • install an identical configuration across several computers on your network • automate the installation and configuration process by specifying options and settings for users Before you set up an unattended installation and configuration. ensure that the Cognos 8 installation directory on all computers is protected from unauthorized or inappropriate access. each time you install Cognos 8 components using the installation wizard. Locate the transfer specification file (. the file name is ts-CMD-version-yyyymmdd_hhmm. By default. ensure that all the system requirements and prerequisites are met and that all third-party products are installed and configured.ats) to specify installation options ❑ run the installation tool in silent mode ❑ use a preconfigured configuration file from another computer ❑ run the configuration tool in silent mode After you complete these tasks. You can check if the unattended installation was successful by checking the return status. 3.ats. Use the installation wizard to install Cognos 8 components on your computer. Steps Using a File Generated by a Previous Installation 1. if you already installed Cognos 8 components on a sample computer. Set Up an Unattended Installation Use a transfer specification file (. Then you will be ready to use Cognos 8. the options you select are recorded in a transfer specification file.ats) that was generated: • If you installed Framework Manager. you can use the generated transfer specification file as a template for unattended installations on different computers.ats. A value of zero (0) indicates success and all other values indicate that an error occurred. you can use the default transfer specification file named response.ats) to copy Cognos 8 components. You must modify the response. 4. • If you installed Metric Studio. including Framework Manager or Metric Designer. the file name is ts-FRAMEWORK MANAGER-version-yyyymmdd_hhmm. Go to c8_location/instlog.ats. • If you installed Metric Designer.

• For Metric Studio components. type issetup -s location/filename.txt. On the computer where you plan to install the software.txt. and then type the following command. the file name is tl-CRN-version-yyyymmdd-hhmm.Chapter 11: Setting Up an Unattended Installation and Configuration 5. the file name is tl-CMD-version-yyyymmdd-hhmm_summary-error.txt.ats File 1. Command Prompt to open a Command Prompt window. 2. If errors occur before sufficient initialization occurrs.ats file in a text editor. where location is where you copied filename.txt. Type the installation location of the program files for Cognos 8: • On Windows. insert the CD and copy the contents to your computer. • For Metric Designer. insert the appropriate CD and copy the contents of the Cognos directory to your computer. type appPath=location • On UNIX or Linux. (=). the transfer specification file: With XWindows.txt. 4. Each section in the response. log messages are sent to one of the following log files in the Temp directory: • For Framework Manager. 6. • For Metric Studio components.ats If a return status other than zero (0) is returned. in the section named [Component List]. For a Windows installation. After all errors are resolved. For the server components of Cognos 8. next to each component: • To install the component.txt. • For Cognos 8 reporting server components. Go to the win32 directory and open the response. the file name is tl-CMM-version-yyyymmdd-hhmm_summary-error. type the following command on a single line. Errors are recorded in the installation directory in the following log file: • For Framework Manager. All required files are installed. type 1 • To not install the component. the file name is tl-CMD-version-yyyymmdd-hhmm_summary-error. the file name is tl-CMM-version-yyyymmdd-hhmm_summary-error. 5. type issetupcc -s location/filename. type the name of the Start menu folder that contains your program shortcuts.txt. • For Metric Designer. 3.ats • On UNIX or Linux. type APPDIR=location Tip: There should be no space on either side of the equal. the file name is tl-FM-version-yyyymmdd-hhmm_summary-error.ats file corresponds to a dialog box in the installation wizard. Also ensure that the installation directory is protected from unauthorized or inappropriate access. click Programs. you can set up an unattended configuration.ats Without XWindows. 174 . the transfer specification file: issetup -s location/filename. type 0 Note: You do not select components for Framework Manager or Metric Designer. check the log files for error messages. Install Cognos 8: • On Windows.txt. On the target computer. for the APPFOLDER= property. Steps Using the Response. • For Cognos 8 reporting components. the file name is tl-FM-version-yyyymmdd-hhmm. where location is the directory where you copied filename. the file name is tl-CRN-version-yyyymmdd-hhmm_summary-error. from the Start menu.

For example. you must also copy the global configuration file from the source computer to the computer where you plan to run an unattended configuration. the file name is tl-CRN-version-yyyymmdd-hhmm_summary-error. and Linux. the file name is tl-CRN-version-yyyymmdd-hhmm. Installation and Configuration Guide 175 . You can check if the unattended configuration was successful by checking the return status. type 1 • To specify the condition is false. 106). • For Cognos 8 reporting components. the file name is tl-CMD-version-yyyymmdd-hhmm_summary-error.txt. Go to the win32 directory. Set Up an Unattended Configuration Before you set up an unattended configuration. type 1 for the VISIBLETOALL= property. • For Metric Studio components.txt. 7.txt. • For Cognos 8 reporting server components. the file name is tl-CMD-version-yyyymmdd-hhmm_summary-error.txt. If you made changes to the global configuration. Also ensure that the installation directory is protected from unauthorized or inappropriate access. you can set up an unattended configuration. you must export a configuration from another computer that has the same Cognos 8 components installed. After all errors are resolved. A value of zero (0) indicates success and all other values indicate that an error occurred.txt. fonts. the file name is tl-FM-version-yyyymmdd-hhmm.Chapter 11: Setting Up an Unattended Installation and Configuration Tip: To ensure that the shortcut folder is visible to all users. where location is the directory where you copied response. Global configuration includes such settings as content locale. the file name is tl-FM-version-yyyymmdd-hhmm_summary-error. If errors occur before sufficient initialization occurrs. the file name is tl-CMM-version-yyyymmdd-hhmm_summary-error. Ensure that the configuration settings on the local computer are appropriate to use to configure another Cognos 8 computer with the same installed components. UNIX with XWindows.txt.ats • On UNIX without XWindows. type 0 Save the response. 8. At the command prompt type the following command.ats file to a local directory after you make the necessary changes. the file name is tl-CMM-version-yyyymmdd-hhmm_summary-error. • For Metric Designer. log messages are sent to one of the following log files in the Temp directory: • For Framework Manager. check the log files for error messages. if you changed the host name portion of the Gateway URI property from local host to an IP address or computer name.ats: • On Windows. Errors are recorded in the installation directory in the following log file: • For Framework Manager. If a return status other than zero (0) is returned. For the install information in the [Install Conditions] section: • To specify the condition is true. and cookie settings. type issetup -s location/response. • For Metric Designer. 9. see "Global Settings" (p.txt. product locale. For more information. type issetupcc -s location/response. ensure this setting is appropriate for the new computer’s configuration. You can then run Cognos Configuration in silent mode.txt. The exported configuration contains the properties of the Cognos 8 components that you installed on the source computer. • For Metric Studio components. currencies.ats 6.

see the cogconfig_response. If you changed the global configuration on the source computer. from the File menu. 2. Type the configuration command: • On UNIX or Linux. encrypts credentials.xml. locate and open the folder./cogconfig. If you want to export the current configuration to a different folder.sh -s • On Windows. type a name for the configuration file. Rename the file to cogstartup. copy the coglocale. Ensure that the folder is protected from unauthorized or inappropriate access. Copy the exported configuration file from the source computer or network location to the c8_location/configuration directory on the the computer where you plan to do an unattended configuration. Click Save. In Cognos Configuration. click Export as.xml. 7. 176 .bat -s Tip: To view log messages that were generated during an unattended configuration. 9. 4.xml file from the source computer to the c8_location/configuration directory on the computer where you plan to do an unattended configuration. starts Cognos 8 service or process. and if applicable. 8. Go to c8_location/bin. 6. generates digital certificates. 5. In the File name box.Chapter 11: Setting Up an Unattended Installation and Configuration Steps 1. Cognos Configuration applies the configuration settings specified in the local copy of cogstartup. in the Look in box.csv file in the c8_location/logs directory. type . type cogconfig. 3.

To uninstall Cognos 8. Your installation location remains on your computer. If you are running Cognos 8 in an application server environment. Delete all temporary Internet files. type: kill -TERM pid 3. After you have undeployed Cognos 8 components. Uninstalling does not remove any files that changed since the installation. and you retain these files until you delete them manually. start Cognos Configuration.Chapter 12: Uninstalling Cognos 8 It is important to use uninstall programs to completely remove all files and modifications to system files. uninstall all Cognos 8 components and the Cognos 8 service. go to the c8_location/uninstall directory and type the appropriate command: • If you use XWindows. you uninstall server components and Framework Manager or Metric Designer. 5. such as configuration and user data files./uninstcc -u 4. Steps to Uninstall Cognos 8 1. Follow the prompts to complete the uninstallation. 177) and on Windows (p. Uninstall Cognos 8 on UNIX or Linux If you no longer require Cognos 8 or if you are upgrading. and from the Actions menu. follow the uninstallation instructions in the documentation for the older version of ReportNet. Stop the Cognos 8 process: • If you run XWindows. Installation and Configuration Guide 177 . complete the steps in this chapter to uninstall on UNIX (p. click Stop. To uninstall Cognos 8. type . Uninstall Cognos 8 on Windows If you no longer require Cognos 8 or if you are upgrading. If the console attached to your computer does not support a Java-based graphical user interface./uninst -u • If you do not use XWindows. Many application servers do not completely remove all deployed application files or directories during an undeploy therefore you may have to perform this action manually. use the administration tool provided by your application server vendor to stop the application if it is running and undeploy the Java portion of Cognos 8 components. type . uninstall Cognos 8. determine the process identification (pid) of the Cognos 8 process by typing the following command: ps -ef | grep cogbootstrapservice 2. If you are upgrading from an older version of ReportNet to Cognos 8. 177). Important: Do not delete the configuration and data files if you are upgrading to a new version of Cognos 8 and you want to use the configuration data with the new version. • If you do not run XWindows.

uninstall it. and you retain these files until you delete them using Windows Explorer. Follow the instructions to uninstall the components. It is not necessary to back up the configuration and data files on Windows. Tip: To find the log file. We recommend that you close all programs before you uninstall Framework Manager. Delete all temporary Internet files. and you retain these files until you delete them using Windows Explorer. click Programs. The cognos_uninst_log. click Programs. some files may not be removed. You must repeat the uninstallation process on each computer that contains Cognos 8 components. If you chose another name. you can uninstall Framework Manager without uninstalling other Cognos 8 components. 178 . Important: Do not delete the configuration and data files if you are upgrading to a new version of Cognos 8. Steps 1. the uninstall wizard lets you choose the packages to uninstall. Otherwise. look in the Temp directory. The Uninstall wizard appears. Tip: Cognos 8 is the default name of the Program Folder that is created during the installation. look in the Temp directory. such as configuration and user data files. see your Web browser documentation. go to that folder to find the program. Uninstalling does not remove any files that changed since the installation. 2. From the Start menu. Follow the instructions to uninstall. some files may not be removed. Otherwise.Chapter 12: Uninstalling Cognos 8 If you installed more than one component in the same location. Cognos 8.htm file records the activities that the Uninstall wizard performs while uninstalling files. Uninstalling does not remove any files that changed since the installation. Important: Do not delete the configuration and data files if you are upgrading to a new version of Cognos 8 and you want to use the configuration data with the new version. The Cognos_uninst_log. see your Web browser documentation. Tip: To find the log file. Your installation location remains on your computer. such as configuration and user data files. Uninstall Cognos 8. Your installation location remains on your computer. If you installed Framework Manager in the same location as Cognos 8. 3. go to that folder to find the program. We recommend that you close all programs before you uninstall Cognos 8. Uninstall Cognos 8.htm file records the activities that the Uninstall wizard performs while uninstalling files. 3. Uninstall Framework Manager If you no longer require Framework Manager or if you are upgrading. For more information. If you chose another name. These files are preserved during the uninstallation. Cognos 8. Steps 1. From the Start menu. 2. The Uninstall wizard appears. Tip: Cognos 8 is the default name of the Program Folder that is created during the installation. For more information. Delete all temporary Internet files.

From the Start menu.Chapter 12: Uninstalling Cognos 8 Uninstall Metric Designer If you no longer require Metric Designer. The Uninstall wizard appears. The Cognos_uninst_log. Delete all temporary Internet files. Uninstalling does not remove any files that changed since the installation. Tip: Cognos 8 is the default name of the Program Folder that is created during the installation. Uninstall Cognos 8. Cognos 8. and you retain these files until you delete them using Windows Explorer. 3. Follow the instructions to uninstall. see your Web browser documentation. For more information. We recommend that you close all programs before you uninstall Metric Designer. uninstall it. go to that folder to find the program. Otherwise. click Programs. such as configuration and user data files. 2.htm file records the activities that the Uninstall wizard performs while uninstalling files. Steps 1. some files may not be removed. If you chose another name. look in the Temp directory. Your installation location remains on your computer. Tip: To find the log file. Installation and Configuration Guide 179 .

Chapter 12: Uninstalling Cognos 8 180 .

xml file. located in the c8_location/configuration directory ❑ apply the configuration and the locale settings to your computer by running Cognos Configuration in silent mode For all installations. some configuration tasks are required so that Cognos 8 works in your environment. or locale mapping by editing the coglocale. ❑ Manually change language or currency support. You must ❑ manually change default configuration settings by editing the cogstartup. or locale mapping by editing the coglocale. Manually Change Default Configuration Settings on UNIX and Linux Computers If the console attached to your UNIX or Linux computer does not support a Java-based graphical user interface. ❑ Apply the configuration and the locale settings to your computer by running Cognos Configuration in silent mode. You can also use sample files that enable Cognos 8 to use resources that already exist in your environment. ❑ Deploy Cognos 8 into an application server environment by manually creating a Cognos archive file. Other configuration tasks are optional and depend on your reporting environment.xml to configure Cognos 8 to work in your environment.xml file. Manually Configuring Cognos 8 on UNIX and Linux The console attached to the UNIX or Linux computer on which you are installing Cognos 8 may not support a Java-based graphical user interface. located in the c8_location/configuration directory. ❑ Manually change default configuration settings by editing the cogstartup.xml file. some configuration tasks are required so that Cognos 8 works in your environment. You can change the default behavior of Cognos 8 by editing the cogstartup.Appendix A: Manually Configuring Cognos 8 The console attached to the UNIX or Linux computer on which you are installing Cognos 8 may not support a Java-based graphical user interface.xml file to change property values. You can also use sample files that enable Cognos 8 to use resources that already exist in your environment. For all installations. located in the c8_location/configuration directory.xml file to change property values. Other configuration tasks are optional and depend on your reporting environment. the order in which you configure and start the computers is important. If you distribute Cognos 8 components across several computers. You must perform the following tasks manually.xml file. You can change the default behavior of Cognos 8 by editing the cogstartup. located in the c8_location/configuration directory ❑ manually change language or currency support. Installation and Configuration Guide 181 . If you distribute Cognos 8 components across several computers. you must edit the cogstartup. the order in which you configure and start the computers is important.

you can use the ContentManager_language code. Open the cogstartup. Tip: Use the type attribute to help you determine the data type for the configuration property. other user settings that rely on the server time zone may not operate as expected. • To use an authentication provider. such as an authentication provider that already exists in your environment.xml file contains configuration settings used by Cognos 8 and by default third-party components. The encoding of your user locale is set by your environment variables. Before you edit the cogstartup. 13) Steps 1. For example. elements and values. including element and attribute labels.xml file is encoded using UTF-8. You can then edit the configuration values to suit your environment. ensure that you • make a backup copy • create the content store on an available computer in your network (p. or Sybase for the content store. You should now use a validating XML editor to validate your changes against the rules in the cogstartup.xml file. Steps 1. When you edit the cogstartup. In this case.xml file directly and then run Cognos Configuration in silent mode. to use an Oracle database instead of a Microsoft SQL Server database for the content store. 5. located in the c8_location/configuration. you can add a component to your configuration. 2.xml file. Go to the c8_location/configuration/samples directory.xsd file.xml file.Appendix A: Manually Configuring Cognos 8 Note: Some configuration settings are not saved in the cogstartup. Change the value of the <crn:value> element to suit your environment. 53) • review the configuration requirements for your installation type (p.xml file. 182 . Save and close the file. Repeat steps 3 to 4 until the configuration values are appropriate your environment. For example. If you want Cognos 8 to use a resource. open the ContentManager_language_code. 3. ensure that you change the encoding of your user locale to match the encoding used. open the Authentication_language_code. 6.xml file unless you use the graphical user interface. You do this by copying the required XML code from the sample files into the cogstartup. Case is important in all uses of text. the server time zone is not set for your Cognos components when you modify the cogstartup.xml file. remember that XML is case-sensitive. Go to the c8_location/configuration directory. Choose a sample file to open in an editor: • To use Oracle.xml file in an editor. DB2.xml file.You can change the components that Cognos 8 uses by copying XML elements from sample files into the cogstartup. When you save the cogstartup. 2.xml sample file to replace the default database connection information. Add a Component to Your Configuration The cogstartup. Cognos 8 can use only one instance at a time of the following elements: • the database for the content store • a cryptographic provider • a configuration template for the Cognos 8 service You should be familiar with the structure of XML files before you start editing them. Important: By default.xml file and then edit the values to suit your environment. 4. the cogstartup. 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.

For example. you change the value and then set the encryption flag to false.> . Go to the c8_location/configuration directory.xml file. Run Cognos Configuration in silent mode by typing the following command: . 5. Manually Change Encrypted Settings You can manually change encrypted settings. Open the cogstartup. don’t change the class attribute. Save and close the file. Open the cogstartup. in the cogstartup. Repeat steps 3 to 5 until the configuration values are appropriate for your environment.. • To use a medium or large template for the amount of resources the Cognos 8 process uses. 7. Go to the c8_location/configuration directory. 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. Paste the code from the sample file to the cogstartup. Change the values of these new elements to suit your environment... if you use an Oracle database for the content store. For example. Change the encryption value to false. 3.Appendix A: Manually Configuring Cognos 8 To use a third-party cryptographic provider. open the Cryptography_language_code. To prompt Cognos Configuration to save an encrypted setting. Steps 1. 2. such as passwords and user credentials. change only the name attribute to suit your environment. Tip: Ensure that you copy the code including the start and end tags for the <crn:instance> element. Save and close the file. </crn:instance> <!-(End of) DB2 template =============================================== --> • 4.xml file. 3. You can change the name attribute to suit your environment. Change the value of the <crn:value> element to suit your environment. For example.xml file in an editor. open the Logging_language_code.xml file in an editor. • To send log messages somewhere other than a file. For the <crn:instance> element./cogconfig. 9. 6. Tip: Use the type attribute to help you determine the data type for the configuration property.xml file.xml file. <crn:instance class="Oracle" name="MyContentStore"> 8. <crn:value encrypted="false"> 6. Installation and Configuration Guide 183 . 7. 4. 5.xml file and replace the appropriate <crn:instance> element.sh -s This ensures that the file is valid and that passwords are encrypted. Copy the elements that you need. look for the (Begin of) and (End of) comments: <!-=============================================== (Begin of) DB2 template --> <crn:instance . open the CognosService_language_code..

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). On every computer where you installed Content Manager. Open the coglocale. You change global settings • to specify the language used in the user interface when the language in the user’s locale is not available • to specify the locale used in reports when the user’s locale is not available • to add currency or locale support to report data and metadata • to add language support to the user interface By default. If it is not available in the user’s locale. en-us becomes en and fr-fr becomes fr. For more information.Appendix A: Manually Configuring Cognos 8 8. but the user locale is es-es (Spanish-Spain). 2. Because the user’s locale is fr-ca. First. For example. 184 . Example 3 The report and the user locales do not map to a common language. Example 2 The user’s locale and the report locales all map to the same language. contact your Cognos support representative. Type the following configuration command: . if a report is available in en-us (English-United States) and fr-fr (French-France). Therefore. The user will see the report in the locale setting that Cognos 8 components choose. Cognos 8 uses the locale mapping to determine which report the user sees. you may want to configure a mapping. such as en-us (English-United States) and fr-fr (French-France). Cognos 8 components choose the language. Cognos 8 components map each locale to en. Before you can add language support to the user interface./cogconfig. In this case. Because both report and the user locale maps to fr. Manually Change the Global Settings on UNIX and Linux Computers If the console attached to your UNIX or Linux computer does not support a Java-based graphical user interface. Cognos 8 uses the mapped value to see if the report is available in fr. which may come from different sources and in various formats. use a normalized form. For example. Cognos 8 components choose which locale to use. it is mapped to fr. the user having the user locale fr-ca will see the report saved with the locale fr-fr. the report is available in en-us and fr-fr. Cognos 8 maps each of the available reports to a normalized locale. Cognos 8 components ensure that all locales.sh -s The new settings are saved and encrypted. Cognos 8 checks to see if the report is available in Content Manager in the user’s locale. not fr. Example 1 A report is available in Content Manager in two locales. Cognos 8 maps the user’s locale to a normalized locale configured on the Content Locale Mapping tab. Cognos 8 chooses the language. go to the c8_location/configuration directory. That means that all expanded locales conform to a language and regional code setting. Next. you must install the language files on all computers in your distributed installation. you must manually edit the coglocale.xml file in an editor. but the user locale is set to fr-ca (French-Canadian). Steps 1.xml file located in the c8_location/configuration directory. In this case.

and if applicable. you must manually add it to the i18n_res. see the cogconfig_response. located in the c8_location/configuration.xml file in the c8_location/bin/ directory. you must complete the following steps to create the archive file. If you choose not to use the Build Application wizard. encrypts credentials. 150) or in a servlet gateway (p. Add or modify the required element and attribute between the appropriate start and end tags. Steps 1. Cognos Configuration applies the configuration settings specified in the local copy of cogstartup. 102). 3. Excluding the static content when creating the archive file reduces the size of the file. Run Cognos Configuration in Silent Mode on UNIX and Linux Computers Run Cognos Configuration in silent mode to apply the configuration settings on your computer if the console attached to your UNIX or Linux computer does not support a Java-based graphical user interface. you should use a validating XML editor to validate your changes against the rules in the cogstartup. located in the c8_location/configuration. 4. Installation and Configuration Guide 185 .sh -s Tip: To view log messages that were generated during an unattended configuration. Cognos 8 provides a Build Application wizard that you can use to create the archive file. 2.xsd file.xml file in the c8_location/configuration directory on the local computer contains the property settings you want to use for your configuration.xml. Copy this file to each Cognos computer in your installation. Type the following configuration command . you do not need to include the Cognos static content in the archive file. Go to c8_location/bin. delete the element.xsd file. If you add a currency code that is not supported by Cognos.Appendix A: Manually Configuring Cognos 8 3. Manually Create a Cognos Archive File Cognos 8 must be packaged into an archive file that will be used to deploy it in the application server environment (p. generates digital certificates. Type of element Language Content Locales Currency Product Locale Mapping Content Locale Mapping Fonts Start tag <supportedProductLocales> <supportedContentLocales> <supportedCurrencies> <productLocaleMap> <contentLocaleMap> <supportedFonts> End tag </supportedProductLocales> </supportedContentLocales> </supportedCurrencies> </productLocaleMap> </contentLocaleMap> </supportedFonts> Tip: To remove support. Before you run the configuration tool in silent mode. Tip: We recommend that you use a validating XML editor to validate your changes against the rules in the cogstartup.csv file in the c8_location/logs directory. Ensure that the cogstartup. starts the Cognos 8 service or process./cogconfig. Save and close the file. If the application server is not being used as a web server.

to build without web content. Run a script by doing one of the following: • On Windows.bat • On Windows. type build.war) file or an Enterprise archive (. to build with web content.sh ear • On UNIX or Linux. to build with web content. Go to the c8_location/war/p2pd directory. to build without web conten build. type build. Run a script by doing one of the following: • On Windows.bat war_without_webcontent • On UNIX or Linux. you must create a WAR file. to build with web content. 2.sh • On UNIX or Linux. to build with web content. If you are using a Sun Java System Web Server. type build. 2. For a servlet gateway. to build without web content. to build without web content.Appendix A: Manually Configuring Cognos 8 You can create a Web archive (.sh ear_without_webcontent 186 . Steps to Create a WAR File 1. see the documentation provided with the application server. Go to the c8_location/war/p2pd directory. type build.bat ear_without_webcontent • On UNIX or Linux. For information about WAR and EAR files and to determine which is supported by your application server.ear) file.sh war_without_webcontent Steps to Create an EAR File 1. you can create a WAR file or an EAR file.bat ear • On Windows. type build. type build. type build.

and includes a time stamp. or are having problems you can revert to a previously saved configuration file. To help isolate the problem.xml. which is available on the Cognos support site (http://support. Another valuable troubleshooting tool is the Knowledge Base. Problems are characterized by their symptoms. The transfer summary-error log file is located in the c8_location/instlog directory.com). each problem can be fixed by implementing a series of actions. The file name identifies the product name. disk space information.Appendix B: Troubleshooting Use this troubleshooting reference information and solutions as a resource to help you solve specific problems you may encounter during or after the installation of Cognos 8 components. The transfer log file is located in the c8_location\instlog directory. the selections you made in the transfer dialogs. When you cannot resolve a problem.txt The Transfer Summary-Error Log File This file records the components you installed. The following is an example of the file name format for backup configuration files: cogstartup_200211231540.cognos. The backup configuration files are located in the c8_location/configuration directory. To analyze a problem. The following is an example of the file name format: tl-COG-8-1-0-0-20050901_1122. When you are troubleshooting. Log Files When you are troubleshooting. and build number. log files can help you.txt The Startup Configuration File This file records your configuration choices each time you save your property settings. The file name is cogstartup. The Knowledge Base is a database of problems and solutions for all Cognos products. version. The file name identifies the product name. and includes a time stamp. the final resource is your Cognos technical support representative. see the Troubleshooting Guide. Each symptom can be traced to one or more causes by using specific troubleshooting tools and techniques. For more information about troubleshooting resources. and build number.xml Installation and Configuration Guide 187 . version. collect the necessary data before you contact your representative. and any errors the installation wizard encountered while transferring components. After being identified. If you are unable to save your configuration. several files can help you: The Transfer Log File This file records the activities that the installation wizard performed while transferring files. The following is an example of the file name format: tl-COG-8-1-0-0-20050901_1122_summary-error. your technical support representative requires information about the situation and the symptoms that you are experiencing.

You can double-click the file to have it appear in your browser. where gateway_interface is cgi.csv and is located in the c8_location/logs directory. Run Database Cleanup Scripts In some troubleshooting situations. use these files to track your changes. gwgateway_interface. gwcgi. mod2 (Apache 2.log (e.htm and is located in the Temp directory. Symptoms of these problems are user IDs and passwords do not work.3 module).log file. it means that Cognos Configuration did not shut down properly the last time you used it.lock file. check the appropriate file or database. locale mapping. The gateway log file uses the following naming format. you may be advised to start with new configuration data. You can use the gateway log file to troubleshoot problems that prevent the gateway from processing requests or from using encryption. If the file exists and Cognos Configuration is not open. If you configured another destination for log messages. The Gateway Log File The gateways record errors in the gateway log file. They are located in the c8_location/logs directory. or isapi. You can delete the lock file and then open Cognos Configuration.0 module). The Silent Mode Log File This file records the activities that Cognos Configuration performed while running in silent mode.. and currency support. The backup configuration files are located in the c8_location/configuration directory. The following is an example of the file name format: coglocale_200211231540. You can use the log file to troubleshoot problems related to uninstalling Cognos 8 components. and the dispatcher is running but users receive the following error message: The Cognos BI server is not available. The log file is named cognos_uninst_log. You can run an SQL script to delete all the tables in any of the following databases that Cognos 8 components use: • content store for data that Cognos 8 needs to operate 188 . The log file is named upgradeLog. or other log files that you configure to receive log messages from the log server. mod (Apache 1. which is located in the c8_location/logs directory.xml and is located in the c8_location/log directory. single signon does not work. Most messages provide information only.xml The Run-Time Log File The default Cognos log file named cogserver. The file is in xml format and references an xslt stylesheet. If you experience problems with language support in the user interface or in reports.g. This log file is named cogconfig_response. you can check the c8_location/configuration directory for the cogstartup. If you experience problems opening Cognos Configuration. The Locale Configuration File This file records the configuration choices you make in Cognos Configuration for product and content locales. but others can help you to diagnose problems in your run-time environment. The ReportNet to Cognos 8 Upgrade File This file contains a summary of the results of an upgrade from ReportNet to Cognos 8. record information after you start the Cognos 8 service. Some log messages indicate problems.Appendix B: Troubleshooting The Startup Configuration Lock File This file is created each time you open Cognos Configuration. It prevents you from opening more than one Cognos Configuration window.log) The Uninstallation Log File This file records the activities that the Uninstall wizard performed while uninstalling files.

Steps 1. its structural definition and data are deleted permanently from the database.sql NC_DROP_DB2.sql cmm_purge_deleted_data dbalias username password Specify the dbalias only if a database with the same name is already cataloged.Appendix B: Troubleshooting • • • delivery database for report notifications log database for log messages metric store for metric package content and Metric Studio user preferences When you delete a table. Database Content store Database Type DB2 Script Name dbClean_db2. database objects may also be deleted.sql Oracle Sybase Notification DB2 dbClean_oracle. go to c8_location\configuration\schemas\content. 4.sql Oracle Sybase Log DB2 NC_DROP_ORA.sql LS_dbClean_sybase. 2. go to c8_location\configuration\schemas\delivery.sql LS_dbClean_db2. run one of the following scripts in the appropriate database tool to delete the tables.sql dbClean_sybase.sql Microsoft SQL Server dbClean_mssqlserver.sql Oracle Sybase Metric store DB2 LS_dbClean_oracle. Go to the appropriate directory: • To delete tables from the log database. • To delete tables from the content store.sql Microsoft SQL Server NC_DROP_MS. 3. For the metric store. Go to the appropriate database directory. Microsoft SQL cmm_purge_deleted_data metric_store_name database_name Admin_user_name password Installation and Configuration Guide 189 .sql NC_DROP_SYBASE. go to c8_location\configuration\schemas\cmm.sql Microsoft SQL Server LS_dbClean_mssql. a new set of required database tables are created automatically in the location specified by your configuration settings. • To delete tables from the notification database. • To delete tables from the metric store. go to c8_location\configuration\schemas\logging. stop the Cognos 8 service. On each computer where Content Manager is located. Depending on the database and database type. When you restart the Cognos 8 service.

browsers. 190 . The third-party application server does not start. Steps 1. Depending on the database type. Solution Check your Web server configuration. Go to the following directory: c8_location\configuration\schemas\cmm 3. Start the Cognos 8 service. The service does not start. such as WebLogic or WebSphere Symptom You do not see the splash screen for Cognos Connection when you start Cognos 8. patches.Appendix B: Troubleshooting Database Database Type Oracle Script Name cmm_purge_deleted_data database_name database_user_name password Replace database_name with the name in the tnsnames.ora file that refers to the database SID for Metric Studio 5. the content store database. You can view an up-to-date list of environments. Ensure that you use third-party software that is supported by Cognos components. and database servers on the Cognos support site (http://support. Ensure that you wait a few moments before submitting a request. Go to the appropriate database directory. 2. directory servers. Improve Metric Store Database Performance Cognos 8 provides a script called cmm_update_stats that updates your metric store database indexes.com). The service starts but no tables are created in Check your content store configuration. Typically. which improves performance. For example. Web servers. 4.cognos. performance may improve if you run this script after increasing the number of scorecards from 100 to 1000. Ensure that there is no activity in the metric store database. Check the file permissions and directory names of the application server installation location. such as operating systems. you use this script before or after loading data when the volume or distribution of data has changed significantly. run one of the following scripts from the command line: • For Microsoft SQL Server or DB2: cmm_update_stats host_name metric_store_name Admin_user_name password • For Oracle: cmm_update_stats metric_store_name Admin_user_name password Problems Starting Cognos 8 You may encounter problems when you try • to start the Cognos 8 service • to open the Welcome page for Cognos Connection for the first time • to start an application server.

3. under CSK settings. start Cognos Configuration. which is equivalent to half a second.prefs file. If you want to start a particular service. Check that Cognos 8 service is available and properly configured. 4. configure the standby Content Manager computer to store the symmetric keys locally. • A standby Content Manager computer may be configured incorrectly. You do this by configuring the ServiceWaitInterval and ServiceMaxTries properties in the c8_location/configuration/cogconfig. click Start. Open the c8_location/configuration/cogconfig. By default. start the Cognos 8 service. From the File menu. 3. set Store symmetric key locally to True. Steps to Change the Wait Time 1. 5. By default. To avoid this error. its value is 500. On the standby Content Manager computer. the setting for storing the symmetric keys may be incorrect. the error message appears.Appendix B: Troubleshooting CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration When you start the Cognos 8 service. Add the following code to the file: ServiceWaitInterval=number of milliseconds ServiceMaxTries=number of times Tip: Add the numeric values that correspond to your configuration needs. Steps to Store Symmetric Keys Locally 1. The Cognos 8 Service Needs More Time By default. There are two possible causes for this problem: • The Cognos 8 service needs more time to start. click Cryptography. To avoid this problem. click Save. 5. Using Cognos Configuration. This action starts all installed services that are not running. stop the Cognos 8 service. under Security. From the Actions menu. you can change the amount of time that Cognos Configuration waits to receive a response from the Cognos 8 service. Content Manager Is Configured Incorrectly If the error message appears on a standby Content Manager computer. at which Cognos Configuration checks the progress of the start request. 2. Cognos Configuration checks the progress of the start request every half second for three minutes. in milliseconds.prefs file in an editor. The ServiceMaxTries property represents the number of times that Cognos Configuration checks the progress of the start request. its value is 360. Installation and Configuration Guide 191 . Save the file. In the Properties window. This file is created automatically the first time you open Cognos Configuration. select the service node in the Explorer window and then click Start from the Actions menu. 4. you may receive the following error message: CFG-ERR-0106 Cognos Configuration received no response from the Cognos 8 service in the allotted time. Using Cognos Configuration. 2. In the Explorer window. If Cognos Configuration does not receive a response within this time. The ServiceWaitInterval property represents the time interval.

Database Oracle 8. The server may be unavailable. the database you created for the content store does not use a supported character encoding: For Oracle: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. Check the Cognos server log file for more information.1. CM-SYS-5126 The content store database server uses the character set US7ASCII. CM-SYS-5121 Content Manager cannot start because the database character set for the content store is not supported. when you open Cognos Connection. For Content Manager to connect to the content store.log file is located in the c8_location/logs directory. the content store must use the appropriate character encoding. By default.7 Character encoding UTF8 UTF16 Oracle 9i AL32UTF8 AL32UTF16 DB2 UDB Sybase ASE Microsoft SQL Server Codeset UTF-8 UTF-8 UTF8 UTF16 192 .Appendix B: Troubleshooting Cognos BI Server Not Available When Starting Cognos 8 After you configure Cognos components and start the Cognos 8 services. Content Manager may not be able to connect to the content store if the content store is not configured properly. If you configured another destination for log messages. For DB2 UDB: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. CM-SYS-5121 Content Manager cannot start because the database character set for the content store is not supported. CM-SYS-5121 Content Manager cannot start because the database character set for the content store is not supported. CM-SYS-5124 The content store database server uses the code page 1252. the cogserver. This may occur if • the content store uses an unsupported character encoding • the content store uses a database collation sequence that is case sensitive • the configuration settings you specified in Cognos Configuration are not valid Unsupported Character Encoding If the following messages appear in the log file. or the gateway may not be correctly configured. For Sybase: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. CM-SYS-5125 The content store database client uses the character set US7ASCII. the following error message may appear: The Cognos Gateway is unable to connect to the Cognos BI server. check the appropriate file or database.

For more information. [IBM][CLI Driver] SQL1013N The database alias name or database name "CM123" could not be found.jsql. CM-CFG-5036 Content Manager failed to connect to the content store. see the database vendor documentation. and Sybase Databases 1. see the database vendor documentation.Appendix B: Troubleshooting To resolve this problem. the database you created for the content store uses a database collation sequence that is case sensitive: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. The connection string is "jdbc:JSQLConnect://localhost:1433/cm". you must recreate the content store database using the correct character encoding. CM-CFG-5036 Content Manager failed to connect to the content store. To resolve this problem. Login fails. url:jdbc:JSQLConnect://localhost:1433/cm For DB2: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. Content Manager requires a content store that has a case-insensitive collation.x: Cannot open database requested in login 'cm'. tables are not created in the content store database when the Cognos 8 service is started. do not use illegal characters such as an underscore in Cognos Configuration for the Service Name property. If the Service Name includes illegal characters. Case Sensitive Collation Sequence If the following messages appear in the log file. Verify your database connection parameters and then contact your database administrator. Invalid Configuration Settings If the following or similar messages appear in the log file. The connection string is "jdbc:oracle:thin:@localhost:1521:pb1" ORA-01017: invalid username/password. you must recreate the content store database using a database collation sequence that is not case sensitive. CM-SYS-5003 Content Manager is unable to access the content store. you did not configure the content store correctly in Cognos Configuration. On the computer where you installed Content Manager.ConnectException: Connection refused: connect If you are using an Oracle database. CM-CFG-5036 Content Manager failed to connect to the content store. For more information. CM-SYS-5007 Content Manager build @cm_build_version@ failed to start! Review the Content Manager log files and then contact your system administrator or customer support. start Cognos Configuration.jnetdirect. logon denied For Sybase: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. Failed Logon:com. DB2. CM-SYS-5122 The content store database has a default collation that is case-sensitive. JZ006: Caught IOException: java. For Oracle: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. Steps to Reconfigure Oracle. The connection string is "jdbc:sybase:Tds:localhost:5000/cm". or convert the character encoding. CM-SYS-5123 The content store database server uses the collation <parameter>. For Microsoft SQL Server: CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.net. Installation and Configuration Guide 193 .

For example. When a content store is used by a new version of Cognos 8. select Oracle database (Advanced). The logon credentials are immediately encrypted. 7. under Data Access. In the Explorer window. • If you use an Oracle database. it cannot be used by an older version of ReportNet. right-click Content Store and click Delete. On the computer where you installed Content Manager. type the Oracle Net8 keyword-value pair for the connection. for the Database specifier property. you must use a different content store for each version. 4. Database. click Save. Content Manager. In the Properties window. type the appropriate values and click OK. 3. provide values depending on your database type: • If you use a DB2 database. In the Explorer window. • In the Value .Appendix B: Troubleshooting 2. Content Manager. From the File menu. Content Manager must be configured to access only one content store. If you are upgrading and want to use an existing content store. type the name of the database you previously created in Microsoft SQL Server to use as the content store. This deletes the default resource. ensure that you select the type of database you use for the older version of ReportNet. specify a user ID and password: • Click the Value box next to the User ID and password property and then click the edit button when it appears. 7. change the default value for the Database server and port number. In the Name box. 5. under Data Access. type the appropriate values for the Database server and port number and Service name properties. From the File menu. type a name for the resource.User ID and password dialog box. In the Value . The logon credentials are immediately encrypted. start Cognos Configuration. and then click New resource. If you installed more than one version of Cognos 8. If you want to change the logon credentials. select the type of database and click OK. 8. Click the Value box next to the User ID and password property and then click the edit button when it appears. If you are upgrading and want to use an existing content store. click Content Store. In the Type box. for the Database name property. If necessary. • If you use an advanced Oracle database. it cannot be used by older versions. 2. If you installed more than one version of Cognos 8. 3. By default. 6. Right-click Content Manager. type the appropriate values for the Database server and port number and Database name properties.User ID and password dialog box. click Save. type the appropriate values and then click OK. you must use a different content store for each version. (description=(address=(host=myhost)(protocol=tcp)(port=1521)(connect_data=(sid=(orcl ))) • If you use a Sybase database. Steps to Reconfigure Microsoft SQL Server Databases 1. in the Properties window. type the database alias. For the Database name property. Cognos components use properties for a Microsoft SQL Server database. 6. 5. When a content store is used by a new version of Cognos 8. 194 . 4. Tip: If you want to use Oracle Net8 keyword-value pair to manage the database connection. ensure that you select the type of database you use for the older version of ReportNet.

Please try again or contact your administrator. The dispatcher is still initializing. the earlier version of ReportNet no longer works because all content is automatically upgraded. No Warning That Installing a Later Version of Cognos 8 Will Automatically Update the Earlier Version of the Content Store You have a version of ReportNet installed on your computer. with solutions. Installation and Configuration Guide 195 . Cognos Services are Not Done Initializing After you start the services in Cognos Configuration and the configuration tool shows that the services are running. You install a later version into a new location. DPR-ERR-2058 Error Appears in Web Browser When Starting Cognos 8 After you start the services in Cognos Configuration and then try to open the portal. XTS handler must be initialized before being invoked. Content Manager is Not Available In a distributed installation. The Cognos 8 services may not initialize successfully. a message similar to one of the following may appear: • DPR-ERR-2058 The dispatcher encountered an error while servicing a request. During the restart.log file in the c8_location/logs directory. requiring a manual restart after the network is restored. • DPR-ERR-2058 The dispatcher cannot service the request at this time. you can choose to use the deployment tool to import the entire content store from an earlier version to the later version. To resolve the problem. or Sybase that is supported by Cognos components. Oracle. If you want to use different versions of ReportNet and Cognos 8 after you upgrade. You receive a warning message about this. Microsoft SQL Server. ensure that Content Manager is installed. To help you determine the specific cause. You use the same database for the content store for both versions. These error messages usually occur when the dispatcher cannot communicate with Content Manager. All existing content in the content store database is replaced by the imported content. configure the Internal Dispatcher URI property in Cognos Configuration to use localhost or the network host name. The Content Store is Not Available or Is Not Configured Properly Ensure that the content store database was created and that you configured it correctly in Cognos Configuration. Ensure also that the other Cognos computers are configured with the correct Content Manager URI. look in the cogserver. Tables are Not Created in the Content Store Ensure that you are using a version of DB2. and running. After you configure the later version and start the Cognos 8 service.Appendix B: Troubleshooting Cognos 8 Services Fail to Restart After a Network Outage The Cognos Bootstrap Service restarts Cognos 8 services after a network outage for Tomcat installations where a network IP address is specified in the internal dispatcher URI. The most common causes are listed below. wait a few minutes for all services to start before you open the portal. ensure that before you install the later version. you • back up the database you use for the content store • restore the backup to a new location Alternatively. configured.

You may be exceeding the expected maximum number of simultaneously active threads per process./tomcat4.sh commands. Ensure that the ulimit settings are unlimited. For example. <.8 and by analyzing the Java. In the /bin/startup. such as %. logon denied Steps to Set the Oracle Database Server Name 1. 3. you must also change the logon credentials for the content store in Cognos Configuration.27/bin/catalina. Content Manager. Check for special characters in the logon password. !. You may also receive the following error messages: • CM-CFG-5036 Content Manager failed to connect to the content store. Stop and restart Cognos 8 using the . The User Does not Have Appropriate Permissions Ensure that the user has the appropriate permissions./tomcat4. DB2 reads information from the NT user management. Occasionally./shutdown. • ORA-01017: invalid username/password. find .1.. Open Cognos Configuration. the JDBC driver does not accept characters that are reserved for xml. 3.1. Change the Oracle database server name to a fully qualified name such as host_name./startup.1. Out of Memory on HP-UX If you are using Tomcat.sh and .0 and 11i are set too low for most Java applications. Tip: You can check the number of threads in your process by using the -eprof option available in JDK 1. DPR-ERR-2022 Error Appears in Web Browser When Starting Cognos 8 After you start the services in Cognos Configuration and then try to open the portal.27/bin/catalina. If the password for the NT account changed. In the Explorer window.. All tables are created on the database. a message similar to the following may appear: 196 . Steps to Increase the maximum Number of Threads Per Process 1.eprof file using HPjmeter by selecting the threads metric.sh start "$@" 2.ora file. Change it to the following: . Have your system administrator change the Kernel parameters as follows: • max_thread_proc = 512 • nkthread = 1024 2.sh run "$@" The run command causes the Tomcat output to appear in the console window for Cognos 8.sh file. 2.companyname:1534 to match the name in the tnsnames. and >. Content Manager Cannot Connect to the Content Store on Oracle If you are using an Oracle database as a content store. you can determine the issue is related to HP-UX server configuration.Appendix B: Troubleshooting The Logon Credentials for the Content Store Are Incorrect Check whether the information changed. the DPR-ERR-2058 error may be generated when logging onto the portal http://host_name/cognos8. click Data Access. Steps to Check for an HP-UX Configuration Problem 1. the issue is an HP-UX configuration problem: OutofMemoryException error: Unable to create new native thread on HP-UX The problem is that the default values for HP-UX 11. Content Store. If the following error message appears in the console window for any of the application servers.

3. Application Server Startup Script Fails You may have problems running the startup scripts for an application server to deploy the Cognos application if Cognos 8 components are installed in a directory with a name that includes spaces. This may be due to an incorrect configuration. The cryptographic error usually means the Java environment is not configured correctly. Ensure that the JAVA_HOME environment variable is set correctly and the appropriate security providers are installed. you may see an error message that the cryptographic information cannot be encrypted. ensure that your Java environment is configured correctly. try adding quotation marks around the directory name that includes spaces or use the 8. The cryptographic information cannot be encrypted.xml file in the c8_location\templates\ps\portal directory with a copy from backup or use an XML editor to edit it.31. start Cognos Configuration. An error occurred when requesting a certificate from the Certificate Authority. If this solution is not easily handled by the startup scripts. In the Explorer window.lang. In the Properties window.3 naming convention. In addition.Appendix B: Troubleshooting DPR-ERR-2022 No response generated. rename the directory and do not include spaces in the new name. On the Content Manager computer. Opening the Portal Too Soon This problem can occur if you try to open the portal before Cognos services are initialized. To avoid this problem. you may encounter problems when you save changes in Cognos Configuration.xml file may have been edited. ensure that you copied the appropriate . Ensure that you • configure and start the services on the computer where Content Manager is located before you configure other components • restart the Cognos 8 service after you make any configuration changes Error Trying to Encrypt Information When Saving Your Configuration When you save your configuration using the configuration tool.NoClassDefFoundError: javax/net/ServerSocketFactory.xml File Contains Errors The system. and the same certificate authority password is configured for all Content Manager computers. Also. the URIs are correct. On UNIX and Linux. click Environment. Problems Configuring Cognos 8 After you install Cognos 8 components. 2. Replace the system. Steps to Check the Configuration 1. after you start the services in Cognos Configuration and the configuration tool shows that the services are running. such as JSSE for JRE 1. verify these properties: Installation and Configuration Guide 197 . the computer where Content Manager is installed must be configured and running. an error message similar to the following may appear: java. The system. To resolve this problem. Do you want to save the configuration in plain text? Before you can encrypt your configuration settings. wait a few minutes for all services to start before you open the portal. or the dispatcher not having finished initializing.jar files to the installation location of your Java Runtime Environment. a damaged installation.

198 . 4. and then click OK. Dispatcher URI for external applications and Content Manager URIs 4. On Windows. Save the configuration and restart Cognos 8. click Save. You can replace the default database type for the content store with Oracle.Appendix B: Troubleshooting Under Gateway Settings. If you click Regenerate in the error dialog. the following error message may appear: The cryptographic information may have been corrupted or the cogstartup. External dispatcher URI and Internal dispatcher URI Under Other URI Settings. under Certificate Authority settings. For example. You may have to fix this file or remove it from disk. right-click Authentication and then click New resource. In the Name box. You may then be prompted to regenerate the cryptographic information for the new JRE or exit to switch back to the previous JRE.xml file is invalid. Java Error When Starting Cognos Configuration When you start Cognos Configuration. You can recreate it. or Sybase. Cognos. you may receive an error message that the Java Runtime Environment (JRE) has changed and that the current cryptographic information is not compatible with the new JRE. Cryptographic Error When Starting Cognos Configuration When you start Cognos Configuration. see the topic on changing the version of JVM that Cognos 8 components use. For more information. see the Installation and Configuration Guide. This error may occur for one of these reasons: • Your configuration data was encrypted using a different JRE than the one Cognos 8 components are currently using. Gateway URI Under Dispatcher Settings. 5. the Cognos 8 service is stopped and the cryptographic information is regenerated. In the Explorer window. click the value for Password. 3. If you click Exit in the error dialog. see the Administration and Security Guide. For more information about creating groups and roles in Cognos 8. • • • Unable to Save Your Configuration You may be unable to save your configuration because you are missing a resource. click Cognos. 2. if you want Cognos 8 components to use the JRE that is installed by default. or the content store. The Cognos namespace appears in the Explorer window. 5. From the File menu. In the Type box. For more information. In the Explorer window. Ensure that the same password is used on all Content Manager computers. 6. DB2. Namespace. Note: If you want to change from one JRE to another. Start Cognos Configuration. click Security. you delete a resource such as the Cognos namespace. but you must then recreate your Cognos groups and roles. a cryptographic provider. In the Properties window. type a name for the resource. You cannot replace the Cognos namespace. Steps to Recreate the Cognos Namespace 1. under Security. Cryptography. unset JAVA_HOME or set JAVA_HOME to c8_location/bin/jre. you must set the JAVA_HOME environment variable to point to the JRE that you used to save your configuration. see the Installation and Configuration Guide. • The cryptographic information may have been corrupted.

Start Cognos Configuration. For more information. The image may be blocked by browser restrictions. select the service node in the Explorer window and then click Start from the Actions menu. To resolve the problem.xml file with a copy from your backup location. click the appropriate command: • If the Cognos 8 service is currently running.properties not found. or JPG. the following error message may appear: Font specified in font. This is a common problem on UNIX. However. After saving the current configuration. It means that the Java Virtual Machine (JVM) is trying to use one or more fonts that are not installed on your computer. you must restart the Cognos 8 service. the JVM should use the system default. The problem occurs regardless of the type of image: BMP. the presence of a firewall. and Cognos Configuration should start and run normally. click Start. see the Java documentation. • If the Cognos 8 service is stopped. you must enable access to the existing image location by the Cognos 8 server or copy the images folder to a location that is accessible to the Cognos 8 server and point all image URLs to the image folder in the new location.. replace the cogstartup. Current Configuration Settings Are Not Applied to Your Computer You change default property values or add a resource to your installation in Cognos Configuration.xml file is manually edited and there is an error in the changed text..properties files. add the missing fonts to your Java Runtime Environment by editing the font. authentication requirements. click Restart. GIF. Here is an example of a URL that points to a new location: http://hostname:port/new_location/images/image. If you want to restart a particular service. are installed with your Java SDK. Images Are Missing in PDF Reports When you run a report. If you want to start a particular service. To avoid this problem. To avoid these errors. the PDF output shows a black box where the image should appear. 2.Appendix B: Troubleshooting This error occurs when Cognos 8 components detect an error in the cogstartup.properties files. Several font.jpg Installation and Configuration Guide 199 . From the Actions menu. select the service node in the Explorer window and then click Restart from the Actions menu. The same report in HTML shows the correct image. which contain standard font environment information. The problem occurs because the image is not accessible to the Cognos 8 server.xml file. To apply the new settings to your computer. or a secured URL. This action starts all installed services that are not running. You can find these files in the JRE_location/lib directory. Font on UNIX Not Found When Starting Cognos Configuration When you start Cognos Configuration. This action starts all installed services that are not running and restarts services that are running. This can occur when the cogstartup. Steps to Restart the Cognos 8 Service 1. you may not see the changes or be able to use the resource in the run-time environment.

Other users get the Cognos logon prompt. click Enable Integrated Windows Authentication. Steps to Enable Integrated Windows Authentication 1.dll. 4. 2. In Internet Explorer. you received the following error message: HTTP 500 .ear -a testApplication -co testOC4Jinstance CGI Timeout Error While Connected to Cognos 8 Components Through a Web Browser When performing operations through your Web browser. IIS does not have a default timeout for ISAPI applications. In your Web browser.cgi portion of the URI to cognosisapi. Single signon for some users may not work if they use Internet Explorer and the option to enable Integrated Windows Authentication is not enabled. Errors When Logging On Using an SAP Authentication Provider HTTP 500 Server Error for Oracle Application Server You configured your Oracle application server and when you tried to deploy Cognos 8 components. To resolve this problem. Create the WAR or EAR file and deploy the file by usingthe following command: dcmctl deployapplication -f path_and_name_of_war_or_ear_file -a application_name -co OC4J_instance_name For example dcmctl deployapplication -f /applications/testApp. 2. The error occurs when you use Windows Internet Information Services (IIS) as your Web server and the gateway is configured to use CGI. Under Environment. 3. if you want to keep using a CGI gateway. On the Advanced tab. In the Windows administrative tools. start Cognos Configuration. click Configuration. There is only one domain and all users are members of that domain. Some users can log on to the system without being prompted again in Cognos 8 components. 2. you receive the following error message: CGI Timeout.Appendix B: Troubleshooting Some Users Are Prompted to Log On When Using Active Directory Server You configured Cognos 8 components to use Microsoft Active Directory Server as an authentication provider. Or. for the Gateway URI property. increase the CGI script timeout. IIS has a default timeout for CGI applications. you must create the WAR or EAR file without Web content. In the Process Options tab. 3. 200 . Steps 1. you can configure the gateway to use ISAPI. from the Tools menu. Under the local computer node. change the cognos. click Internet Options. specify the ISAPI URI: http://computer_name/cognos8/isapi Steps to Increase the CGI Timeout 1. right-click Websites and select Properties. On the gateway computer. process will be deleted from server. Go to the oracle_home\dcm\bin directory. open Internet Information Services.Internal server error To resolve this problem. In the Home Directory tab. 2. Steps to Change the Gateway to ISAPI 1. you can increase the CGI timeout in IIS.

pogo.> <Jul 9.1.war file to the WebLogic installation using the following command: %JAVA_HOME%/bin/jar xvfm "c8_location/p2pd. create a directory named p2pd in the following location: WebLogic_location/user_projects/domain_name 4.cognos. 3.context-path=/p2pd)]: Servlet class com.internal.name=p2pd. Steps 1. 6. 2004 3:47:37 PM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "cfgss" failed to preload on startup in Web application: "p2pd".lang.4.servlet.servlet.java:799) at weblogic.isolation.servlet.log is also not created.ServletException: [HTTP:101249][ServletContext(id=19023494. Installation and Configuration Guide 201 . The cogserver. Open Cognos Configuration and configure the Application Tier Components computer.cognos. When deploying the p2pd.prepareServlet (ServletStubImpl. Although the server claims to receive only a portion of the file.1. java. the entire file is transmitted and the PDF document displays correctly.ServletStubImpl. you may receive servlet exceptions and the dispatcher does not start. extract the p2pd.ServletWrapper for servlet cfgss could not be loaded because the requested class was not found in the classpath /host2/bea812/user_projects/domains/c8/applications/ p2pd/WEB-INF/classes.ClassNotFoundException: com.Appendix B: Troubleshooting Servlet Failed with IOException Error on WebLogic Server Console When you view PDF reports.pogo. For example.isolation. The error message contains the following information: Servlet failed with IOException java.ServletWrapper for servlet cfgss could not be loaded because the requested class was not found in the classpath /host2/bea812/user_projects/domains/c8/applications/ p2pd/WEB-INF/classes. 2004 3:47:37 PM EDT> <Error> <HTTP> <BEA-101249> <[ServletContext(id=19023494. The following error messages appear in the WebLogic Server console: <Jul 9.cognos. Create the p2pd directory in another location and deploy p2pd from there. Restart the Content Manager computer. Servlet Class Fails to Load in WebLogic You may have problems when configuring a distributed server installation and using WebLogic as the application server for Cognos 8.ProtocolException: Didn’t meet stated Content-Length The error occurs only in systems that use WebLogic 8. Create a p2pd directory in a location that is accessible by the WebLogic server but is not in the WebLogic applications directory.internal.preload Servlet(WebAppServletContext. In the WebLogic Server Console.java:3252) To avoid this problem.isolation. do not deploy the p2pd application from the WebLogic applications directory. Start WebLogic. deploy the p2pd application.cognos.net.war for the Application Tier Components computer. you may see an error on the WebLogic server console.name=p2pd. 5. 2.pogo. Create the p2pd. at weblogic. java.war" .1 and JDK 1.ClassNotFoundException: com.WebAppServletContext.lang. 7.ServletWrapper.ServletWrapper. javax. context-path=/p2pd)]: Servlet class com.pogo. There is no need to resolve this problem. In the p2pd directory.isolation.war file.

Appendix B: Troubleshooting 202 .

Certificates are used to positively identify an entity. the two nodes negotiate to see which cipher suite to use when transmitting messages back and forth. encryption. Users must be authenticated before they can be authorized to use any secured resources. cipher suite In SSL. Each Cognos computer in a distributed installation uses a different certificate. application tier components For installation. a secondary name for a database table. anonymous access A method of accessing resources in which users are not authenticated. certificate A document that identifies someone or something by name. a set of authentication. Examples of resources are reports and folders. Installation and Configuration Guide 203 . You can also use a third-party certificate authority. or users. and namespace searches are made available through authentication providers.Glossary access permissions Rules defining the access rights to resources. and all users gain the same access permissions. authentication provider The communication mechanism to an external authentication source. Access permissions can be granted to any combination of namespaces. Certificates are issued by certification authorities. certification authority The Cognos component that issues certificates (identification) to each computer on which components are installed. so that self-joins can be created or ambiguous query paths can be resolved. authentication The process of verifying the identity of users when they log on. alias In modeling and database terminology. Functionality such as user authentication. group membership. and can be used for encryption or decryption. and data integrity algorithms used for exchanging messages between network nodes. the processors that access the query databases to gather information and then render the results as PDF and HTML reports and metrics. groups. They are used for digital signatures and secure communications. Aliases are used to create a distinct reference to the table in the model. Application tier components also pass requests to Content Manager and render the results that Content Manager retrieves from the content store. During an SSL handshake.

models. connection The named information that defines the type of the data source. Web servers often use CGI programs to process forms. date. and the Cognos namespace itself. For example. then credentials must be stored in the content store. dimensional cube. 204 . reports. including application-specific security. but may follow other standards such as ISAPI and Apache Modules. Credentials are created for Cognos components. and information about scheduling and bursting reports. money expressions. its physical location. and manage the Cognos namespace. Letters are glyphs. but in most cases. configuration data. published models. such as formats for time. retrieve or store report specifications. glyph An image of a character in a font. content store The database that contains data that Cognos 8 needs to operate. A deployment archive contains the data from the content store that is being moved. information about the external namespace. data source A relational database. and the regional preferences. money. the term is used in discussions of non-alphabetic writing systems. Design models and log files are not stored in the content store. You can assign your credentials to someone else so that they can use resources that you are authorized to use. metrics. such as report specifications. usually a user name and password. content locale A code that is used to set the language or dialect used for browsers. Gateways are often CGI programs. If a user schedules or programs an action. report text.Glossary common gateway interface A standard that describes how Web servers should access other programs in order to create a document that will appear in a Web browser. manage scheduling information. or other physical data store that can be accessed though Cognos 8. gateway An extension of a Web server program that transfers information from the Web server to another server. Content Manager The Cognos 8 service that manages the storage of customer applications. connection information for data sources. The Cognos 8 service that uses the content store is named Content Manager. and so on. and report output. Content Manager is needed to publish models. A data source can have more than one connection. deployment archive A file used for deployment. and the packages that contain them. file. For Cognos products. and any signon requirements. credentials Information stored about the identity of a Cognos user. and time of day. you can specify a locale for the product interface (product locale) and for the data in the report (content locale).

locale A code that is used to set the language or dialect used for browsers. A job step can also be another job. A passport is created the first time a user accesses Cognos 8. For Cognos products. Usually. a job step is a report. Allows access to user and group information. Credentials are stored encrypted. such as user preferences. identified by a URI reference. you can specify a locale for the product interface (product locale) and for the data in the report (content locale). Passport information is stored in Content Manager memory. passport Session-based information regarding authenticated users. In XML. money. a configured instance of an authentication provider. In Framework Manager. A passport reference number is stored in a memory-only browser cookie for the duration of the session. job step The smallest part of a job that can be run separately. such as reports. job A group of runnable objects. reports. which are used in XML documents as element types and attribute names. a list of users or other groups that can be used to assign access permissions and capabilities. query subjects. namespace For authentication and access control. and the regional preferences. grouping is the action of organizing common values of query item together and only displaying the value once.Glossary group In security. It is retained until a session ends. and so on. and metric management tasks for that application. Headers and footers often appear after each instance of a common value in a grouped column HTTPS A secure version of HTTP Hypertext Transfer Protocol) that incorporates secure sockets layer (SSL). Installation and Configuration Guide 205 . Groups can be referenced from third-party authentication sources or can be local to Cognos 8. Cognos products use HTTPS and SSL to encrypt and transmit passwords securely over the Internet. money expressions. or after a specified period of inactivity. and so on. A metrics store also contains Metric Studio settings. and other jobs that you run and schedule as a batch. report text. A metrics package contains connection information. date. Local groups are managed from the administration portal. agents. and time of day. In reporting. metrics package A Cognos Connection representation of a Metric Studio application. either when the user logs off. a collection of names. metrics store A database that contains content for metrics packages. such as formats for time. namespaces uniquely identify query items. The list of groups that an authentication user is a member of is part of the users passport for a Cognos 8 session. You import different databases into separate namespaces to avoid duplicate names.

and email addresses. XML is extensible because the tags aren't predefined or limited. A SOAP message contains the content of a message and an envelope. report specification The definition of queries. SOAP messages are independent of any operating system or protocol. For Cognos installations. and HTTP. including SMTP. security provider See Authentication Provider. The envelope contains information about the contents and how to process them (XML). such as menu commands. simple object access protocol A lightweight XML-based messaging protocol used to encode the information in Web service request and response messages before sending them over a network. or both to use for parts of the product interface. such as first and last names. You create report specifications by using Report Studio. the response file automates only the process of copying files with the default configuration. layouts. Unlike HTML. Other user information. MIME. Analysis Studio. Query Studio.Glossary portlet A mechanism for displaying Web content as part of a portal page. such as the location of personal folders or preferred formats for viewing reports. XML A language that uses markup symbols or tags to create descriptions of the structure of data. Authenticated user definitions and information. response file An ASCII file that contains the setup data that is needed to automate an installation. and the instructions for sending the message user A person accessing a Cognos 8 application. is stored in Cognos 8. and is related to HTML and SGML. prompts. and may be transported using a variety of Internet protocols. are maintained in third-party authentication sources. regional settings. IDs. or through the Software Development Kit. 206 . A report specificaiton is combined with data by a run operation to create report outputs. and styles that make up a report. product locale The code or setting that specifies what language. passwords. The XML standard is defined by the World Wide Web Consortium (W3C). locales. prompt A report element that asks for parameter values before the report is run.

101 Apache Web Server configuring aliases. 137 for NTLM. 20 application tier components definition. 153 startup scripts for SAP Web Application Server. 84 application server startup script fails. 140 for SAP. 126 enabling SSL. 125 single signon problems. 126 aliases configuring on Apache Web Server. 61 configuring as the gateway. 145 BI bus upgrade considerations. 16. 32 BMTScriptPlayer availability on Linux. 128 using. 111 namespaces. 150 upgrading Cognos 8. 203 Active Directory Server authenticating in multiple domains. 203 authentication with single signon for Active Directory Server. 151 startup scripts for WebLogic. 21 configuring. 101 configuring on Web servers.xml specifying for Portal Services. 142 for SiteMinder. 139 A access permissions definition. 114 authentication Active Directory Server. 200 using for authentication. 181 advanced properties for Active Directory Server. 126 enabling single signon. 201 servlet gateway. 120 authentication namespaces deleting. See certificate authority certificate authority (CA) service. 160 certificate signing requests (CSR). 150 startup scripts for Oracle application server. 15 installing on separate computer for Cognos 8 scorecarding. 158 cryptographic keys. 122 authentication namespaces See also namespaces authentication providers definition.jar file error when starting configuration. 114 Apache gateway configuring. 155 B backing up Cognos 8 information. 45 C CA. 160 configuring.Index Symbols . 102 single signon for WebSphere Portal. 198 Application Tier Components configuration requirements. 151 servlet class fails to load in WebLogic. 128 for LDAP. 160 certificates definition. 62 adding fonts. 203 Analysis Studio components. 101 apache_mod configuring for the gateway. 203 in domain trees for Active Directory Server. 203 disabling. 124 active scripting enabling in Web browsers. 145-155 configuring. 9 anonymous access definition. 203 Installation and Configuration Guide 207 . 142 trusted signon plug-in for Cognos Series 7. 126 for Cognos Series 7. 114 anonymous logon disabling for authenticated logon. 158 the content store. 200 definition. 122 resources. 203 applications. 120 startup scripts. 61 definition. 79 installing on separate computer. 126 single signon for Plumtree Portal using HTTP Basic authentication. 123 disabling for Portal Services. 146 Cognos information. 53 the metric store. 53 BEA WebLogic changing to. 197 application servers changing.

145-155 default configuration settings. 192 system requirements. 11 distributing for Metric Designer. 10. 10 Framework Manager. 163 Cognos 8 components. 192 specifying sort order.Index certification authority definition. 101 the configuration template.lock file. 20 Cognos 8 service configuring. 13 208 . 67 configuring to use alternative servers. 9 Composite Information Server. 192 chase_referrals. 198 Cognos Series 7 enabling single signon. 15. 199 invalid settings. 181. 9 Cognos Contributor access to cubes from Cognos 8. 192 Cognos Configuration (cont'd) problems opening. 105 the location of map charts for Report Studio. 16. 151 restarting services. 203 setting a priority for SSL connections. 19 Content Manager. 9 Cognos 8 installation options. 109 email encoding. 177 Cognos 8 products on same computer as other Cognos 8 products. 43 troubleshooting installations. 200 cgi timeout error. 92 communications distributed components. 112 default time zone. 12 Cognos namespace recreating. 157 to a new version of Java. 198 collation sequences case-sensitive. 110 the Cognos 8 gateway. 97 Cognos Configuration cannot save changes. 22 Event Studio. 22 Cognos 8:on same computer as other Cognos products. 177 uninstalling service. 10. 43 installing Application Tier Components on separate computer. 200 changing a URI. 126 chunking patches application servers. 157 client virtual machine. 20 installing. 10 configuration requirements for Application Tier Components. 128 using for authentication. 43 content store. 199 running on same computer as ReportNet. 203 CFG-ERR-0106 error. 13 uninstalling on UNIX or Linux. 90 application servers. 185 changing properties manually. 184 Cognos samples. 173 default settings. 101 common symmetric key in cryptographic provider. 89 default font for PDF reports. 10 gateway. 128 enabling SSL. 191 CGI timeout error. 15 installing gateway on separate computer. 197 components. 27 Cognos 8 scorecarding distributing components. 127 Cognos Viewer in Cognos 8 server components.xml file invalid file. 177 uninstalling on Windows.xml. 146 cipher suites definition. 14 installing on one computer. 192 workflows. 21. 195. 11 data sources. 80 components Analysis Studio. 21 configuration requirements on one computer. 64 coglocale. 10 Cognos Connection. 41 server not available. 188 running in unattended mode. 19 Cognos 8 scorecarding components installing gateway on separate computer. 43 deploying. 9 Cognos Configuration. 18 installing components on one computer. 187 unsupported characters. 9 configuring. 10 font not found error.xml. 96 classic virtual machine. 204 replacing. 188 cogstartup. 175 Cognos Connection components. 17 cogstartup. 158 character encoding unsupported. 105 Cognos Application Firewall configuring. 11 Cognos Finance access to cubes from Cognos 8. 16. 19 Cognos 8 scorecardingcomponents installing Application Tier Components on separate computer. 157 code pages for data sources. 195 common gateway interface definition. 183 cogstartup. 128 trusted signon plug-in. 113 the type of JVM. 14. 145-155 copying components. 43 gateway configuration requirements.

10 configuration. 70. 37 manual. 173 configuration workflows. 10 Query Studio. 199 configuration tools. 98 transfer specification files (. 204 connectivity setting up for SAP BW authentication provider. 10. 86 Portal Services. 25 configuring a Cognos Series 7 namespace. 62 Web server. 84 connection management for the content store. 16. 32 Content Manager computers configuring. 124 running. 61 content locale customizing. 108 content locales definition. 74 routers. 181 requirements for Metric Designer. 184 cogstartup. 89 applying. 138 an Active Directory namespace. 157 backing up. 41 settings for Cognos 8. 84 shared trust with other servers. 204 failover protection. 9 report server. 181 advanced options. 21 installing. 107 mapping to user locale. 80 Installation and Configuration Guide 209 . 173 Web browsers. 21 configuration. 158 changing the template. 17. 34 configuration files coglocale. 197 error when encrypting information. 148 Cognos 8 service. 21 default active.Index components (cont'd) Metric Designer. 133 an NTLM namespace. 131 an LDAP namespace for Active Directory Server. 160 configuring (cont'd) Cognos 8. 68. 67 Cognos 8 for application servers. 96 single computer installations. 10 used by Cognos 8. 78 on report server computers. 124 an LDAP namespace. 98 distributed installations. 53 standby. 132 an LDAP namespace for IBM Directory Server. 200 in silent mode for upgrade. 127 a SiteMinder namespace. 16. 9 components for Cognos 8 scorecarding installing Application Tier Components on separate computer. 68. 79 certificate authority (CA) service. 19 installing on one computer. 75 definition. 21 upgrade considerations.xml. 75 custom authentication provider. 10 metric store. 80 Metric Designer. 78 requirements for changing application server. 9 Transformer. 16. 21 installation options. 43 on multiple computers. 84-86 gateway computers.ats). 105 Content Manager. 146. 20 installing gateway on separate computer. 130 destination for log messages. 75 Content Manager URIs property on Content Manager computers. 21 cryptographic information cannot be encrypted. 183 required tasks. 197 adding resources. 188 configuration settings. 93 standby Content Manager. 109 components. 141 content expiry images directory. 140 an SAP namespace. 74 fonts. 185 running multiple versions of Cognos 8. 16. 105 Content Manager computers. 142 apache_mod for the gateway. 113 properties in silent configuration. 78 temporary file location. 61 configuring Framework Manager distributed installations. 198 workflows. 204 Content Manager changing the time zone. 77. 68 SSL protocols. 197 error when logging on. 175 configuration lock file. 25 configuration data upgrade considerations. 146 setting up a database. 181 exporting.xml. 75 connections definition. 151 Application Tier Components. 72. 111 Framework Manager. 48 testing. 16. 81 ISAPI for the gateway. 63 servlet for the gateway. 11 Metric Studio. 88 troubleshooting. 16. 43 Report Studio. 19 Composite Information Server components. 84 application server properties. 84 mail server. 197 unable to save. 9 third-party. 23 requirements for single signon with Microsoft Analysis Server or Microsoft SQL Server.

75 database connections. 113 deleting authentication namespaces. 99 default active Content Manager. 55 environment variables for metric store on UNIX. 53 creating DB2. 60 DB2 databases setting up JDBC drivers. 69. 11 creating. See metric store database client setting up for a logging database. 57 deleting tables from the database. 58. See data source connections database connectivity metric store. 89 changing. 55 database connectivity. 123 dispatcher does not start on Application Tier Components computer. 71. 172 demonstration environments. 155. 22 document version. 71. 68. 204 destination for log messages. 204 cookies customizing. 68. 204 data store. 55 metric package. 55 creating metric store. 82 setting data sources components. 125 in LDAP. 43. 45 databases Cognos samples. 154 distributed installation installation and configuration workflows. 195 domain setting for cookies. 204 cross-script checking configuring in Cognos Application Firewall.Index content store backing up. 2 creating content store. 68. 30 distributed installations configuring. 194 Oracle. 82 metric store. 130 custom user properties from Active Directory Server. 45 requirements for content store. 110 enabling in Web browsers. 107 custom authentication providers configuring Cognos 8 to use. 75 default configuration settings. 45 requirements for metric store. 45 environment variables. 163 deleting tables. 98 DB2 code pages. 28. 195 content stores definition. 159 invalid settings. 54 creating Sybase. 112 default location map charts. 11 definition. 197 crytographic keys backing up and deleting. 89 Tomcat. 142 Cognos samples. 57 credentials definition. 48 default font changing for PDF reports. 55 creating Microsoft SQL Server. 53 data source connections to metric store. 188 destination for log messages. 62 copying Cognos 8 components. 97 cryptographic error. 84 deploying Cognos 8. 114 anonymous logon. 2 documentation services failing to start after network outage. 136 customizing cookie settings. 146. 82 DB2 content store. 71. 27. 173 copyright. 158 components. 43. 55 DB2 metric store. 198 cryptographic information cannot be encrypted. 158 currency customizing support. 98 disable content maintenance job. 54 creating Oracle. 64 creating content store. 53. 53 Sybase content store. 75 Microsoft SQL Server. 110 D data Cognos samples. 84 scenarios. 110 database connection strings IBM DB2. 13. 188 import data. 146. 74 configuring Framework Manager. 164 data source connections metric stores. 99 210 . 18 distributing components Metric Designer. 171 disabling anonymous access. 76. 192 requirements for changing application server. 151 deployment archives definition. 201 dispatchers removal. 163 data source connections. 146 upgrading.

199 Framework Manager. 19 recommended settings for Microsoft IIS. 32 functions SaferAPIGetTrustedSignon. 200 gateway computers configuring. 200 corrupt cryptographic information. 196 DPR-ERR-2058 err. 15.ats. 105 encrypted properties changing in silent configuration. 84 configuring for Cognos 8. 110 HTTP 500 Server Error. 10 samples. 17. 129 E EAR file. 198 error messages CGI timeout. 89 uninstalling. 84 configuring to use a namespace. 197 Enterprise archive file deploying Cognos 8. See Enterprise archive file email messages changing the encoding. 84 configuring. 175 External identity mapping property editing for an LDAP namespace. 173 Firefox browser settings. 59 environments supported. 205 H host names resolving in a mixed UNIX and Windows environment. 91 HTML cookies customizing settings. 197 DPR-ERR-2002. 43 installing on separate computer. 45 supported operating systems. 198 servlet class fails to load on WebLogic. 16. 49 testing installation and configuration. 87 environment variables DB2. 111 not found error when starting Cognos Configuration. 201 errors on WebLogic server console. 170 exporting configuration files. 20 configuring a servlet. 23 firewalls access between Framework Manager and Cognos 8. 201 event log destination for log messages. 81 gateways definition. 54 set for application server. 45 Error corrupt cryptographic information.Index domains authentication in domain trees for Active Directory Server. 17 sample models. 80 configuring for Metric Designer. 98 Event Studio components. 160 global configuration setting. 10 accessing Cognos 8 outside a firewall. 73. 62 firewall considerations. 200 cgi timeout. 104 installing. 84 fonts configuring. 147 setting up on UNIX for metric store. 106 glyphs definition. 101 configuring ISAPI. 178 upgrade considerations. 137 G gateway components. 110 enabling Cognos Application Firewall. See Cognos samples groups definition. 10 configuration requirements. 200 generating keys. 55 Oracle. 196 Java Runtime Environment. 174 using a previous installation version. 21 files destination for log messages. 201 SAP authentication provider. 171 system requirements. 200 servlet class fails to load on WebLogic. 183 encryption configuration errors. 198 cryptographic information cannot be encrypted. 14 installing on separate computer for Cognos 8 scorecarding. 195. 98 Installation and Configuration Guide 211 . 185 environment properties configuring for Application Tier Components. 201 servlet failed with IOException. 154 enabling and disabling. 84 configuring apache_mod. 204 Great Outdoors. 97 SSL for an application server. 84-86 configuring source control systems. 195 files (cont'd) response. 204 when to use ISAPI. 199 installation options. 200 F failover protection. 126 DPR-ERR-2022 error. 198 Java Runtime Environment. 85 connects to the wrong URI.

45 database connectivity for metric store. 98 load balancing. 62 invalid cogstartup. 17 testing. 80 enabling and disabling services. 20 loading images in Report Studio.ats). 101 configuring for gateway. 25 installation files transfer specification file (. 60 Java scripts enabling in Web browsers.security updating in UNIX and Linux. 61 installation checklist. 157 Java Archive files (. 88 workflows. 99 setting up Oracle databases. 145 IIS Web server single signon with Active Directory.Index HTTP Basic authentication for single signon with Plumtree Portal. 126 images loading in Report Studio. 61 212 . 21 options for Framework Manager. 200 K keys generating.jar) updating in UNIX and Linux. 107 language support Thai. 135 limited expression editing with LDAP. 61 locales definition. 61 missing from PDF reports. 90 log database deleting tables. 188 J Java changing to a new version. 205 localhost changing. 45 JDBC drivers setting up DB2 databases. 9 Internet Explorer browser settings. 43 unsupported features and components. 158 configuring servlet gateway for Java-compatible Web servers. 145 inunstalling Cognos 8.xml file. 198 invalid settings Cognos Configuration. 173 installation tools running. 62 Java System Web Server configuring aliases. 133 IBM WebSphere changing to. 25 installing Metric Designe. 77. 45 Linux syslog destination for log messages. 148 I IBM DB2 creating connection strings. 67 configuring mail server settings. 177 system requirements. 205 java. 131 LDAP namespace configuring for IBM Directory Server. 198 JDBC database connectivity for content store. 58. 160 L language customizing for user interface. 43 options for Content Manager. 106 language and region customizing. 158 copying security provider files. 107 LDAP editing the External identity mapping property. 99 job steps definition. 192 iPlanet Web Server See Sun Java System Web Server ISAPI accessing Cognos 8. 68. 16. 50 integrating third-party components. 72. 137 using for authentication. 173 installation workflows. 133 configuring for Novell Directory Server. 15. 43 Cognos 8. 102 types of virtual machine. 120 HTTPS definition. 60 JAVA_HOME setting. 137 enabling SSL. 70. 198 Java Runtime Environment (JRE). 84 when to use for a gateway. 192 content store. 137 enabling single signon. 205 JRE requirements for Thai language. 199 images directory content expiry. 107 JVM changing. 105 load-balancing setting. 205 jobs definition. 58. 146. 137 Linux changing application servers. 60 Java error when starting configuration. 158 changing to a new version. 75 IBM Directory Server authentication.

29 Metrics Manager on same computer as ReportNet. 11 NewsIndexes access from Cognos 8. 98 configuring. 139 protecting the Cognos 8 Web alias. 68. 71 upgrading metric store. 98 logging database creating. 10 creating metric package. 51 testing installation and configuration. 188 startup configuration. 83 NewsBoxes access from Cognos 8. 113 Map Manager labels. 71 installation and configuration workflows. 130 recreating. 32 Metric Studio components. 100 locale configuration. 38 metrics packages definition. 10 Transformer. 98 enabling for Cognos Application Firewall. 199 log server messages. 10 models modifying for samples. 198 namespaces See also authentication namespaces Netegrity SiteMinder cross-script checking in Cognos Application Firewall. 187 transfer summary. 70. 104 definition. 11 Installation and Configuration Guide 213 . 75 map charts. 23 configuring. 11 creating. 170 samples. 98 metadata modeling.ats file. 54 creating Oracle. 187 configuring a destination. 139 using for authentication. 50 system requirements. 18. 53 logging databases. 200 Microsoft SQL Server creating connection strings. 62 New Metric Package wizard. 82 metric packages creating. 124 Microsoft IIS Web servers. 142 recreating. 10 Metric Designer.Index log files. 23 recommended gateway settings. 198 namespaces adding. 59 upgrading. 32 metric package creating. 173 sample models. 54 database connectivity. 179 upgrading project. 97 enabling single signon. 199 modeling tools Framework Manager. 170 multi_domain_tree. 11 messages log server. 108 maps Map Manager. 54 database connectivity. 31 uninstalling. 22 installing. 97 log on failure in Framework Manager. 53 components. 188 run-time. 71. 80 managing connections for the content store. 124 missing images in PDF reports. 69. 55 creating Microsoft SQL Server. 205 metrics stores definition. 100 metric stores upgrading. 194 creating content store. 89 uninstalling. 45 setting up environment variables on UNIX. 54 creating metric store. 126 M mail server configuring. 83 N namespace configuring a custom authentication provider. 137 Netscape browser settings. 71. 205 Microsoft Analysis Server namespace requirement. 38 upgrading. 122 configuring for a gateway. 45 namespace requirement. 205 deleting. 82 creating DB2. 76. 187 transfer. 10 configuration requirements. 188 silent mode. 11 mapping content locale to user locale. 188 log messages destination. upgrading. 72. 73. 72. 171 modifying response. 10 Metric Designer components. 77. 82 metric store backing up. 53 creating data source connections. 187 uninstallation. 86 distributing components.

183 configuring for application server. 91 resources adding. 63 Oracle application server HTTP 500 Server Error. 75 creating content store. 31 running on same computer as Cognos 8. 54 database connectivity. upgrading. 199 required tasks configuring. 101 P passports definition. 188 product locale mapping for user interface. 206 ports default configuration settings. 99 environment variables. 90 portal errors in starting. 74 requirements database connectivity for content store. 45 resolving host names in a UNIX and Windows environment. 68. 140 using for authentication. 112 customizing language support. 41 PowerCubes access within Cognos 8.Index no response generated. 188 Novell Directory Server. 201 images missing. 206 projects Metric Designer. 114 portlets definition. 45 database JDBC drivers. 12 PowerPlay access to NewsIndexes and NewsBoxes from Cognos 8. 139 proof of concept. 68. 107 error when viewing in PDF. 63 running Apache Jakarta Project Connector. 206 Report Studio change the location of map charts. 88 prompts definition. 54 creating metric store.xml file. 54 environment variables for metric store on UNIX. 98 Q quality of protection in SSL connections. 198 remote log servers configuring. 32. 41 supported versions for upgrading. 173 routers configuring. 173 using. 151 temporary file location. 100 destination for log messages. 58. 174 response. 196 Portal Services. 9 loading images. 45 disabling anonymous logon in Cognos 8. 201 images missing in PDF format. 113 components. 183 path setting for cookies. 45 database connectivity for metric store. 200 R recreating the Cognos namespace. 199 Plumtree Portal single signon using HTTP Basic authentication. 98 replacing common gateway interface. 110 PDF reports error on WebLogic server console. 109 product locales definition. 45 SAP BW on UNIX. 206 response. 96 Query Studio components. 68.ats. 195. 101 report servers installing. 113 availability on Linux. 11 problems opening Cognos Configuration. 31 upgrading. 59 multilingual support. 173 installation tools. 135 NTLM enabling single signon. 9 O Oracle application server. 101 configuration tools. upgrading. 173 Microsoft Internet Application Programming Interface. 43 report specifications definition. 121 port changing. 206 214 . 153 creating connections strings.ats file modifying. 61 ReportNet on same computer as Metrics Manager. 196 notification database deleting tables. 181 response files definition. 48 running multiple versions of Cognos 8. 84 properties changing in silent configuration. 205 passwords changing in silent configuration. 31 reports changing default font. 120 single signon using SiteMinder. 114 specifying the applications.

96 silent configuration changing properties. 137 SSL connections quality of protection. 119 SAP Logon Ticket used for single signon. 120 using shared secret for Portal Services. 141 authorization settings for Cognos 8 users. 171 setting up. 54 SQL Server. 200 enabling single signon. Cognos 8 checking before changing application servers. 152 authentication provider login errors. 183 for upgrade. 43 security provider copying required files to a JVM location. 141 setup. 105 failing to start after network outage. 141 requirements for UNIX. 121 for SAP EP with SAP Logon Ticket. 139 with Active Directory Server. 29 single computer installations configuring. 206 server time zone changing. 159 security provider files. 165 samples (Cognos) deleting. 84 servlet gateway configuring. 119 for WebSphere Portal using application server. 148 security providers definition. 45 setting up connectivity. 140 SAP BW authorization settings for Cognos 8 administrators. 142 using for authentication. 121 using for authentication. 110 Secure Sockets Layer. 128 with a SiteMinder user directory. with user mapping. 115 SiteMinder cross-script checking in Cognos Application Firewall. 120 setting up shared trust with other servers. 120 for Plumtree Portal using SiteMinder. 26. 195 uninstalling. 129 samples DB2 Cube. 97 enabling single signon. copy to JVM environment. 177 servlet configuring for gateway. 37 silent configurations. 157 services. 139 sorting incorrect sort order in Cognos Connections. 163 SAP BW connectivity. 126 for an LDAP namespace. 195 source control systems configuring for Framework Manager. 28. 170 metric designer. 120 single signon with SAP Logon Ticket. 118 for SAP EP. 137 for an NTLM namespace. 85 SQL Server databases creating content store. See Microsoft SQL Server SSL for SAP EP. 141 SAP Enterprise Portal See SAP EP SAP EP enabling SSL. 142 for Plumtree Portal using HTTP Basic authentication. 109 server virtual machine. 118 single signon with user mapping. 188 SDK applications upgrade considerations. 80 data source connections global configuration. 128 for a SiteMinder user directory. 54 creating metric store. See SSL protocol security settings for Web browsers. 166 Event Studio. 96 with a Cognos Series 7 namespace. 106 setting up samples. 102 setting communication.Index S SaferAPIGetTrustedSignon Function. 172 models. 146 shared secret single signon for Portal Services. See unattended mode simple object access protocol definition. See unattended installations silent mode. 139 single signon for Plumtree Portal. 93 enabling for an application server. 31 secure flag setting for cookies. 140 for an SAP namespace. 105 enabling and disabling. 151 scripts to delete tables from databases. 125 with an LDAP namespace. 118 SAP Web Application Server changing to. 96 SSL protocols configuring. 200 for a Cognos Series 7 namespace. 68 single signon Active Directory Server. 115 shared trust setting up between Cognos 8 and other servers. 206 single computer installation installation and configuration workflows. 145 startup script. 139 for an Active Directory namespace. 163 SAP application server. 154 Installation and Configuration Guide 215 . 137 SiteMinder user directories enabling SSL. 169 metric studio. 167 MSAS cube. See unattended configurations silent installations.

154 updating . 185 setting up. 91 setting up environment variables for metric store. 199 problems. 173 running Cognos Configuration. 190 startup configuration lock file. 43 Framework Manager. 173 response files. 12 components. 119 users definition. 45 Sybase creating content store. 155 content store. 37 URI changing. 59 system requirements. 160 Time zone changing in configuration. 195. 197 startup scripts for WebSphere application server. 72. 49 Metric Designer. See DB2 unable to open Cognos Configuration. 173 V version document. 177 UNIX syslog destination for log messages. 60 JRE in UNIX and Linux. 31 using silent configuration. 195 Metric Designer projects. 51 unattended installations. 106 mapping for product locale. 90 default configuration settings. 98 system requirements. 173 transfer specification files. 98 testing configuration. 60 Upfront access to reports and cubes from Cognos 8. 32. 199 resolving host names in a UNIX and Windows environment. 2 216 . 173 unattended mode.Index standby Content Manager. 183 user interface customize language support. 201 U UDB. 173. 188 template changing the size of template. 11 upgrading Cognos 8 on an application server. 109 Tomcat default configuration settings. 72. 78 starting Cognos 8 service. 10 troubleshooting. 43 uninstalling Cognos 8. 175 uninstalling Cognos 8 on UNIX or Linux. 83 Metrics Manager. 175 unattended configurations. 173 unattended installation setting up. application server access rights. 72. 48 user account. 201 servlet class fails to load on WebLogic. 88 installation. See application servers Sun Java System Web Server servlet gateway. 177 Framework Manager. 174 setting up. 88 Thai language support JRE requirements.ats) configuration. 32. 179 Metrics Manager. 109 user locale mapping to content locale. 108 user mapping single signon for SAP EP. 178 Metric Designer. 188 startup script fails. 206 using preconfigured configuration files. 38 UNIX font not found error. 21 configuring. 102 Sun ONE Web Server See Sun Java System Web Server supported environments. 190 startup problems. 72. 57 syslog destination for log messages. 38 ReportNet. 60 java. 107 third-party certificate authority configuring. 188 unattended configuration.security in UNIX and Linux. 43 Cognos 8. 187 error on WebLogic server console. 146 user credentials changing in silent configuration.jar files. 16. 98 unregister dispatchers. 98 properties. 151 startup scripts. 173 UTF-8 encoding for email messages. 105 temporary file location configuring. 88 metric store. 173 Transformer access to Cognos PowerCubes. 110 T tables deleting from a database. 48 transfer specification files (. 177 Cognos 8 on Windows.

126 WebLogic application server. 140 using for authentication. 43 uninstalling Cognos 8. 139 workflows installation and configuration. 201 servlet class fails to load. 150 startup script fails. 61 W WAR file. 61 setting Report Studio load time. 200 Windows native security (NTLM) enabling single signon. 25 X XML definition. 61 Web archive file deploying Cognos 8. 62 errors in starting the Web portal. 17. 206 Installation and Configuration Guide 217 .Index versions supported ReportNet upgrades. 18. 185 Web browsers configuring. 195 security settings. 197 WebSphere application server. 120 Windows resolving host names in a Windows and UNIX environment. 196 errors in starting the web portal. 31 virtual directories setting up. 151 error on server console. 177 Windows event log destination for log messages. 91 system requirements. 43 Web server configuring. 102 single signon with Active Directory and IIS Web server. 98 Windows IIS recommended gateway settings. See Web archive file Web aliases setting up. 23 servlet gateway. 22 Microsoft IIS. 197 WebSphere Portal single signon using application server. 151 startup script fails. 61 Web servers. 201 startup script.

Index 218 .