Cognos Installation Files

<HEAD>
<meta name="last-review" content="24-01-2003">
<meta name="title" content="Installation Guide">
<meta name="product" content="Cognos BI">
Cognos Series 7 Solution
<meta name="version" content="2">
<meta name="prodversion" content="Cognos BI-2">
<meta name="area" content="support">
for Windows
<meta name="classification" content="documentation">
</HEAD>
Type the Title Bar text for online help
Installation Guide
Installation Guide
24-01-2003
Cognos BI
2
Type the text for the HTML TOC entry
Type the Title Bar text for online help
Cognos Series 7 Version 2
Version 2
Installation Guide
Product Information
This document applies to Cognos Series 7 Version 2 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).
Copyright
Copyright (C) 2003 Cognos Incorporated
While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or
technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in
this document.
This document shows the publication date. The information contained in this document is subject to change without notice. Any
improvements or changes to either the product or the document will be documented in subsequent editions.
U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or
disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at
48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.
This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this
software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system,
transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated.
Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are
trademarks or registered trademarks of their respective companies.
Information about Cognos Products and Accessibility can be found at www.Cognos.com
Table of Contents
Welcome 9
Chapter 1: MR1 Installation and Configuration Documentation Updates 11
Windows Server 2003 Installation and Configuration 11
Java Virtual Machine Support for Windows Server 2003 11
Confirm Administrator Privileges for Windows Server 2003 12
Configure Your Web Server for Windows Server 2003 12
Configure a DNS for Your Sun ONE Directory Server 13
Configure Internet Information Server and Internet Explorer Security 13
Alternate Extensions for Gateway Files 14
CGI Gateways 15
New Configuration Manager Properties 15
Webcontent Root Directory Property 15
Upfront File Manager Disabled Properties 16
ODBC Driver Manager Property 17
Configuring Cognos NoticeCast 17
Enhanced support for NSAPI Gateways 18
Configure NSAPI Gateways 18
Part 1: Making Installation Decisions 21
Chapter 2: Types of Installations 23
Default Installation 23
Custom Installation 24
Upgrade Installation 25
Other Installation Types 26
Chapter 3: Cognos Series 7 Components 27
Cognos Series 7 Reporting 27
Cognos Series 7 Query 30
Cognos Series 7 OLAP 32
Cognos Series 7 PowerPlay Transformer Edition 35
Cognos Series 7 Alerts/Notifications 37
Cognos Series 7 PowerPlay User 39
Cognos Series 7 Impromptu User 40
Cognos Series 7 Impromptu Administrator 41
Cognos Series 7 Visualization 43
Cognos Visualizer User Series 7 45
Cognos Supplementary Software 46
Support Files 47
Default Settings 47
Ports 49
Chapter 4: Mixed Version Environments 55
Configuring Mixed Version Environments 56
Installation Guide 3
Part 2: Installing and Testing Cognos Series 7 59

Chapter 5: Installing by Using Default Settings 61
Verifying Your System Requirements 61
Verify Administrator Privileges 62
Create a TEMP System Variable 62
Set Database Environment Variables 64
Create a Database and Database User for Cognos NoticeCast 64
Installing a Directory Server 65
Install ObjectStore 65
Installing Cognos Series 7 66
Stop Services 66
Install Cognos Components 66
Finishing the Installation 68
Configure Your Web Server 68
Complete the Configuration for Cognos Series 7 Alerts/Notifications 71
Whats Next? 76
Chapter 6: Installing by Distributing Components 77
Preparing for the Installation 77
Create the Database User for Cognos NoticeCast 79
Installing a Directory Server 80
Install ObjectStore 80
Installing Cognos Series 7 Components 81
Stop Services 81
Copy the Components 81
Configuring Cognos Series 7 83
Using the Configuration Manager 84
Configure the Web Server 84
Configure the Directory Server 88
Configuring Component Settings 90
Configuring Cognos NoticeCast Components 91
Apply the Configuration 95
Start Services 95
Specify the Authentication Source 97
Whats Next? 97
Chapter 7: Installing to Upgrade 99
Preparing for the Installation 100
Create the Database User for Cognos NoticeCast 101
Upgrading to Sun ONE Directory Server 102
Upgrade ObjectStore Software 102
Upgrading Cognos Series 7 Components 103
Stop Services 103
Copy the Components 104
4 Cognos Series 7 Solution for Windows
Configuring Cognos Series 7 105

Using the Configuration Manager 106
Configure the Web Server 106
Configure the Directory Server 110
Specify the Authentication Source 113
Configuring Component Settings 114
Configuring Cognos NoticeCast Components 114
Apply the Configuration 119
Start Services 119
Whats Next? 120
Chapter 8: Testing the Installation 121
Test Your Web Server 121
Test ObjectStore 121
Test the Directory Server 122
Test the Ticket Server 123
Test Upfront 124
Test Cognos Series 7 Reporting 124
Test Cognos Series 7 Query 125
Test Cognos Series 7 OLAP 126
Test Cognos Series 7 PowerPlay Transformation Server 126
Test Cognos Series 7 Alerts/Notifications 127
Test Cognos Series 7 Visualization 127
Testing Distributed Sorting 128
Part 3: Upgrading Data 129
Chapter 9: The Upgrade Process 131
Planning the Upgrade 131
In-Place Upgrade 131
Staged Upgrade 131
The Upgrade Process 132
Do I Need to Back Up Before I Start? 132
Upgrade Checklist 132
Checklist for Files You Need 133
Conventions Used in the Upgrade Instructions 134
Service and Process Names 134
Chapter 10: Upgrading Application Data 137
Upgrading Upfront 137
Pack the Upfront Data Store (Required) 138
Unpack the Upfront Data Store 139
Copy Upfront Themes (optional) 141
Verify That Themes Are Assigned to Users (optional) 141
Verify That the Web Alias Information Is Updated 141
Upgrading Cognos Query 142
Pack Cognos Query Data (Required) 142
Unpack Cognos Query Data (Required) 145
Upgrading Impromptu Web Reports 148
Pack the Impromptu Web Reports Data Store (Required) 148
Unpack the Impromptu Web Reports Data Store (Required) 149
Copy the 7.0 PPSRoot Directory 152
Secure PowerPlay Enterprise Server 153
Upgrade PowerPlay Metadata 153
Upgrading Cognos Visualizer 156
Pack Cognos Visualizer Data (Required) 157
Unpack Cognos Visualizer Data (Required) 160
Upgrading Cognos NoticeCast 162

Update the Gateway URLs for All Associated Servers (Required) 162
Update the JDBC Driver Path in NoticeCast Server Administration 163
Update the Gateway URLs in Upfront for All Associated Servers 163
Whats Next? 164
Chapter 11: Upgrading Client Data 165
PowerPlay for Windows 165
PowerPlay for Excel 165
Impromptu 165
Web Browsers 165
Custom Macros and Other Applications 166
Cognos Macros 166
Architect 166
PowerPlay Transformer 166
Upgrading Cognos Visualizer Visualizations 166
Chapter 12: Moving Permanently to Your New Version 169
Uninstall Version 7.0 Components 169
Upgrade the Namespaces (optional) 169
Appendix A: Uninstalling
Cognos Series 7 171
Uninstall the Cognos Components 171
Uninstall Sun ONE Directory Server 173
Uninstall ObjectStore 173
Appendix B: Other Types of Installations 175
Setting Up an Unattended Installation 175
Set Up an Unattended Copy of Cognos Components 175
Set Up an Unattended Configuration of Cognos Components 177
Setting Up Installation Files on the Network 178
Setting Up an Administrative Installation 178
Set Up a Workstation Installation 179
Perform the Workstation Installation 179
Install Multiple Instances of a Cognos Product Gateway on the Same Computer 180
Appendix C: Alternative Upgrades 183
Upgrading PowerPlay Enterprise Server 183
Deployment Manager Commands You Need for the Upgrade 183
Pack Cognos PowerPlay Enterprise Server Data (Required) 184
Unpack Cognos PowerPlay Enterprise Server Data (Required) 186
Upgrading Cognos Visualizer 188
Preparing the environment for upgrade 189
Upgrading Cognos Visualizer Web Server 189
Upgrading Cognos Visualizer Visualizations 189
Update the Gateway URLs in Upfront for All Associated Servers 190
Appendix D: Troubleshooting 193
Troubleshooting Resources 193
General Problems 194
Common Problems 196

Cannot Find Samples Folder or Files 196
Cannot Open a Sample File 196
Ticket Server Not Responding 197
Cannot Start and Stop Ticket Server Using Configuration Manager 198
Access Manager Service Failure or Problems with Authentication or Access
Privileges 198
Cannot Establish Connection to NoticeCast Data Store After Applying Default
Configuration 199
JDBC Driver Not Included in Class Path After Default Configuration 201
Appendix E: Additional Products and Services 203
Install Distributed Component Object Model 203
Install Microsoft Data Access Components 203
Install Microsoft JVM 204
Configure Windows 2000 Active Directory 205
Install Adobe Acrobat Reader 208
Appendix F: Installation Checklist for Windows 211
Index 219
Welcome
This document contains installation instructions for the suite of Cognos Series 7 products.
What Is in This Document

This document contains instructions for doing the following types of installations. We
recommend you start with the first chapter in this book to determine which installation type you
want to use:
New, default installations. All components are selected for you and the default configuration
settings are applied automatically. It is assumed you are installing all Cognos components
and all third-party components on a single computer.
Predominantly default installation, but with some minor changes. You may need to change
some things such as the port number used by one component. This may be the case if a
third-party component such as a directory server is on a separate computer or if you are
upgrading from a previous version.
Custom installations including distributing components across multiple computers and
multiple platforms. You want to select the components to install and configure the
components with your own custom settings.
Upgrade installations from a previous release of Cognos Series 7.
What You Need to Know to Use This Document Effectively

You should be a Windows user and have some experience installing software on Windows
computers.
Other Information
Our documentation includes user guides, tutorial guides, reference books, and other pieces to
meet the needs of our varied audience.
All information is available in online help. Online help is available from the Help button in a Web
browser, or the Help menu and Help button in Windows products.
The information in each online help system is available in online book format (PDF). However,
the information from a given help system may be divided into more than one online book. Use
online books when you want a printed version of a document or when you want to search the
whole document. You can print selected pages, a section, or the whole book. Cognos grants you
a non-exclusive, non-transferable license to use, copy, and reproduce the copyright materials, in
printed or electronic format, solely for the purpose of providing internal training on, operating,
and maintaining the Cognos software.
In Windows products, online books are available from the Windows Start menu (Cognos) and
from the product Help menu (Books for Printing). In a Web browser, online books may be
available from the Welcome section of the help system, or from within the Cognos Web portal
(Upfront). All online books are available on the Cognos documentation CD. You can also read
the product readme files and the installation guides directly from the Cognos product CDs.
Only the installation guides are supplied as printed documents.
Welcome
The following documents contain related information, and may be referred to in this document.
Topic
Location
How to use the product

samples for testing and
how to troubleshoot the
installation
Installation Testing and Samples Setup

Guide
How to plan for an

advanced or distributed
installation
Planning Advanced Installations Guide
How to configure
components
Configuration Manager User Guide
online book (PDF)
online book (PDF)
online book (PDF) and Windows help
How to package business Deployment Manager User Guide

intelligence data and move online book (PDF)
it between Cognos
environments.
Note: For updates to readme files and product documentation, see the Cognos support site
(http://support.cognos.com). You must log on as a supported customer.
Questions or Comments?
For additional technical information about using Cognos Series 7 products, visit the Cognos
support Web site (http://support.cognos.com).
Chapter 1: MR1 Installation and Configuration

Documentation Updates
Windows Server 2003 Installation and Configuration

The installation guide includes installation and configuration instructions for the following
Microsoft Windows operating systems:
Windows 98
Windows NT
Windows XP
Windows 2000
To install and configure Windows Server 2003, follow the instructions for Windows 2000 with the
following exceptions:
Java Virtual Machine Support for Windows Server 2003
Confirm Administrator Privileges for Windows Server 2003
Configure Your Web Server for Windows Server 2003
Configure a DNS for Your Sun ONE Directory Server
Configure Internet Information Server and Internet Explorer Security
Java Virtual Machine Support for Windows Server 2003

The Microsoft Java Virtual Machine (JVM) is not included with Windows Server 2003. If you are
installing Cognos NoticeCast Authoring or PowerPlay Web Launch on a Windows Server 2003
computer that does not already have a JVM, you are prompted to install a JVM.
Steps to Check Whether a JVM Is Installed

1. Click Start, Programs, Command Prompt to open a DOS window.
2. Go to the installation_location\bin directory.
3. Type wjview, and then press Enter.
If the WJView Help window appears, you have a JVM installed on your computer.
Otherwise, you must install it.
Steps to Install a JVM

1. Start the installation menu from your Cognos Supplementary CD as follows:
If you insert the CD, the installation menu should appear. Click Install Support Files,
and then double-click the Microsoft folder, JVM folder, and msjavx86.exe.
If no installation menu appears, go to the Support Files\Microsoft\JVM folder on the CD

and double-click msjavx86.exe.
If you are installing from your network, double-click msjavx86.exe in the JVM folder
where your system administrator copied the third-party support files.
Note: JVM must be version 5.00.3188 or higher. For the latest JVM version see
www.microsoft.com.
2. In the File Download dialog box, click Open.
3. Click Yes, to confirm that you want to install Microsoft Java Virtual Machine and then click
Yes again to accept the license agreement.
4. Restart your computer after the installation is finished.
Chapter 1: MR1 Installation and Configuration Documentation Updates
Confirm Administrator Privileges for Windows Server 2003

Before you install Windows Server 2003, you must confirm that you have administrator
privileges on your computer. If you do not have administrator privileges, ask your system
administrator to add you to the Administrator group.
Steps
1. Right-click the My Computer icon and click Manage.
2. Expand Local Users and Groups.
3. In the left pane of the Computer Management window, click Groups.
4. In the right pane of the Computer Management window, double-click Administrators.
5. Ensure that your user ID or your group ID appears in the Members list.
Configure Your Web Server for Windows Server 2003

To configure your Web server, you must create the following virtual directories using Internet
Information Services Manager (IIS):
webcontent
cgi-bin
help
The virtual directories in the Alias column of the following table are required for all Web servers.
You can use the following alias names or use different alias names. Replace the
installation_location in the Location column with the location where you installed your Cognos
product. The default location is C:\Program Files\Cognos\cer3.
Alias
Location
Permission
cognos
installation_location\webcontent
Read
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
Steps for the Webcontent Directory

1. Click Start, Settings, Control Panel.
2. Double-click Administrative Tools, and then double-click Internet Information Services
Manager.
3. In the left pane of the Internet Information Services Manager window, expand the folder
that has your computer name.
4. Expand the Web Site folder.
5. Right-click the folder that contains the Web site where you will run your Cognos product.
Tip: If you have only one Web site, its default name is Default Web Site.
6. Select New Virtual Directory.
7. In the Virtual Directory Creation Wizard dialog box, click Next.
8. In the Alias text box, type cognos, and then click Next.
9. Click Browse, select the installation_location\webcontent folder, and then click Next.
10. Ensure that the Read and Run-scripts check boxes are selected.
11. Click Next, and then click Finish.
Steps for the cgi-bin Directory

1. In the left pane of Microsoft Management Console, right-click the folder called Cognos
and click New Virtual Directory.

3. In the Alias text box, type cgi-bin, and then click Next.
4. Click Browse, select the installation_location\cgi-bin folder, and then click Next.
5. Ensure that the Read, Run-scripts, and Execute check boxes are selected.
Steps for the Help Directory

1. In the left pane of Microsoft Management Console, right-click the folder called Cognos
and click New Virtual Directory.
3. In the Alias text box, type help, and then click Next.
4. Click Browse, select the installation_location\Documentation folder, and then click Next.
5. Ensure that the Read and Run-scripts check boxes are selected.
Configure a DNS for Your Sun ONE Directory Server

You must configure a Domain Name System (DNS) for the computer where you are installing
Sun ONE Directory Server. The DNS configuration specifies the domain that the server belongs
to.
Steps
1. From the Start menu, click Settings, Control Panel.
2. Double-click System, and click the Computer Name tab.
3. Click Change.
4. In the Computer name box, type the name of your computer.
5. Click More.
6. In the Primary DNS suffix on this computer box, type the name of the domain that you
want the server to belong to such as, yourcompany.com, and click OK.
7. Click OK twice.
8. If prompted, restart your computer to apply the changes.
Configure Internet Information Server and Internet Explorer Security

There are enhanced security settings in Windows Server 2003 for Internet Information Services
and Internet Explorer. These settings are enabled by default when you start Internet Explorer.
Follow the instructions in this section to ensure that Cognos products function as required with
the enhanced security settings.
Internet Information Services Settings

You must set up Internet Information Services to allow access to the .exe and .cgi files in the
cgi-bin directory of Cognos products that use Upfront.
You can either allow all unknown CGI extensions to run or allow Cognos extensions specifically.
If you choose to allow all unknown extensions this effectively turns off the enhanced security.
Steps to Allow All Unknown CGI Extensions

Manager.
3. In the left pane of the Internet Services Manager window, expand your local computer
directory, and then click Web Service Extensions.

4. In the right pane of the window, click All Unknown CGI Extensions, and then click the
Allow button.
The Information Services Manager prompts you to either accept or refuse to allow All
Unknown CGI Extensions.
5. Click Yes.
Steps to Allow Cognos Web Service Extensions

Manager.
3. In the left pane of the Internet Services Manager window, expand your local computer
directory.
4. In the left pane of the Internet Information Services Manager window, right-click Web
Service Extensions, and then select Add a new Web service extension.
5. In the Extension name box, enter a name for the Cognos extension.
6. In the Required Files box, enter the file names that correspond to your Cognos product
gateway programs.
All of these files are located in installation_location\cgi-bin.
The file names are detailed in Alternate Extensions for Gateway Files. There are two
additional files not listed in the table for Access Manager, accessadmin.exe with the
alternate file extension accessadmin.cgi and login.exe with the alternate file extension
login.cgi that should also be added.
7. Click the Set extension status to Allowed check box, and then click OK.
Internet Explorer Settings

If you want to use enhanced security, all the sites that your Web browser opens must be trusted
sites. If Internet Explorer stops loading the page, the problem can be that you tried to access a
server location that is not in the list of trusted sites. To solve the problem, in the error message
that appears, click Add. The server location is added to the list of trusted sites.
Alternatively, the problem can be that the enhanced security setting is prohibiting the script type
that the page is running. To solve the problem, from the incomplete page, click File, select Add
this site to, and click Trusted Sites Zone. This page is added to the trusted sites list.
Alternate Extensions for Gateway Files

Cognos products use gateways with .exe and .cgi file extensions by default. You may have
security policies to prevent .exe files from running on your Web servers. You can choose to use
.cgi versions of all gateways. For more information, see the Configuration Manager User Guide.
Server group
Default file extension
Alternate file extension
Cognos Query
cqcgi.exe
cqcgi.cgi
Impromptu Web Reports
imrap.cgi
imrap.exe
PowerPlay Enterprise Server
ppdscgi.exe
ppdscgi.cgi
Upfront
upfcgi.exe
upfcgi.cgi
Upfront File Manager
fmcgi.exe
fmcgi.cgi
Cognos NoticeCast
upfcgi.exe
upfcgi.cgi
Cognos Visualizer
vizcgi.exe
vizcgi.cgi
CGI Gateways
Modify the gateway properties in Configuration Manager to use the file extension of your choice.
Steps to Change Gateway Properties in Configuration Manager

1. In Configuration Manager, click the Server Configuration tab.
2. Expand All Server Groups.
3. For each server group you want to change, change the Gateway URL property to identify
the correct Web alias and gateway file.
For example, by default, the Upfront gateway is upfcgi.exe. To use the .cgi gateway, you
would change the Gateway URL property to upfcgi.cgi.
4. In the Actions menu, click Apply Topology.
For distributed installations, import the server configuration file (cern.csx) to other
computers to complete the configuration. For more information, see the Configuration
Manager User Guide.
5. If you changed any of the gateway settings for your Upfront server group, complete the
steps 6, 7, and 8. If you did not change the gateway, skip to step 9.
6. Click the Components tab, and then expand Upfront.Gateway.General
7. Modify the Web Program Alias to use the same setting you used for the Upfront Gateway
URL on the Server Configuration tab.
8. From the Actions menu, click Apply Selection.
9. Use the Upfront NewsItem Gateway Manager to ensure all existing Cognos applications
use the new gateways.
For more information, see the Cognos Web Portal User Guide.
Note: Any application or saved report with embeded references, such as Visualizer or
Impromptu Web Reports reports with drill-through targets or Visualizer panel actions must
be configured to use the newly configured gateways.
10. Start Upfront Services
Note: Access Manager gateways do not appear in the server configuration tab of Configuration
Manager. This gateway is automatically determined based on the Upfront gateway type. For
more information, see the Configuration Manager User Guide.
New Configuration Manager Properties

You can change configuration settings using Configuration Manager.
Webcontent Root Directory Property

In previous Cognos Series 7 versions, Upfront Server Administration was used to update the
location of the Web Content Root Directory. In this release (Cognos Series 7, Version 2,
Maintenance Release 1), the Web Content Root Directory field in Upfront Server Administration
is read-only. The Web Content Root Directory is derived from the Upfront Server Group
Gateway URL property managed by Configuration Manager.
Before you proceed with the following steps, you must stop the Upfront services.
Steps
1. Start Configuration Manager.
2. In the Welcome page, click the Start tab.
3. Click Open the current configuration.
4. Click the Server Configuration tab.
5. Expand All Server Groups and click Upfront Server Group.
6. Change the Gateway URL location to match your environment.
7. From the Actions menu, click Apply Topology.

8. For distributed installations, you must import the server configuration file (cern.csx) on other
computers to complete the configuration.
9. Start the Upfront Services.
Object hierarchy: Cognos Shared.Runtime Parameters.Server Configuration.All Server
Group's.Upfront Server Group.Gateway URL
Property
Default value
Description
Gateway URL
/cognos/cgi-bin/upfcgi.e The URL of the top-level

xe
directory in the hierarchy
of the Upfront Web
content. If this property is
set incorrectly, the
browser cannot find the
files that are used to
construct the Upfront
interface and the Upfront
help.
Upfront File Manager Disabled Properties

To enable or disable the Upfront File Manager, you must set properties for each Upfront server
and Upfront gateway. For example, you can disable the Upfront File Manager so that third-party
content cant be published to Upfront.
Before you proceed with the following steps, you must stop the Upfront services.
Steps
3. Expand Upfront.Gateway.General.
4. Change the value for the File Manager Server Enabled property to false.
5. Expand Upfront.Gateway.General.
6. Change the value for the File Manager Gateway Enabled property to false.
7. Click the Upfront File Manager, and then apply the changes.
8. Expand Upfront and click the Upfront Server.
9. Start the Upfront Services.
10. Repeat steps 1 to 9 for each Upfront Server and Upfront Gateway installation.
Object hierarchy: Upfront File Manager.Gateway.General and Upfront File
Manager.Server.General
Property
Default value
Description
File Manager
Server Enabled
True
This property determines

whether the Upfront File
Manager is enabled or
disabled on the Upfront
server.
File Manager
Gateway
Enabled
True

whether the Upfront File
Manager is enabled or
disabled on the Upfront
gateway.
ODBC Driver Manager Property

To configure an ODBC gateway on UNIX, you must set the ODBC Driver Manager property. The
value of this property determines which database types your computer can access.
For a list of the supported databases for these driver managers, visit
http://support.cognos.com/support/products/software_environments.html
Steps
1. In UNIX, go to the installation_location/bin directory.
2. Type configure to start the Configuration Manager command line interface.
3. Type cd computer_name
4. Type cd Services.UDA.General
5. Type ls
All the properties of the General category are shown with their default values.
6. Specify the value of the ODBC Driver Manager property.
Type set "ODBC Driver Manager"=NCR to access a Teradata database.

Tip: NCR is the default value.
Type set "ODBC Driver Manager"=DataDirect to access an SQL Server database.
7. Type apply
Your change is applied to the configuration.
Object hierarchy: Services.UDA.General.ODBC Driver Manager
Property
Default value
Description
ODBC Driver
Manager
NCR

which driver manager is
used to configure the
ODBC gateway on UNIX.
Change this value to
DataDirect to access an
SQL Server database
Configuring Cognos NoticeCast

The change below is an amendment to existing Cognos Series 7 Version 2 installation and
configuration documentation.
In Configuration Manager, the Data Store Connection File property has moved. It is no longer
located in Cognos NoticeCast.NoticeCast Data Store.General. The Data Store Connection
File property is now located in Cognos NoticeCast.NoticeCast Data Store.Connection File.
This change should be noted when reading the following documentation:
Cognos Series 7 Solution for UNIX Installation Guide
Cognos Series 7 Solution for Windows Installation Guide
Cognos Series 7 Configuration Manager User Guide
Tip: Existing Configuration Manager scripts need to be updated if they contain the relocated
Data Store Connection File property.
Enhanced support for NSAPI Gateways

You can now use a single Sun ONE (formerly iPlanet) Web server with multiple server groups
and NSAPI gateways. This configuration method allows the Web server to work with more than
one copy of each product gateway, and replaces the method described in the Configuration
Manager User Guide in these cases. This applies to the following Cognos components:
Cognos Query
Upfront
Cognos Visualizer Server
The following instructions replace the "Configure NSAPI Gateways" topic in the Configuration
Manager User Guide.
Configure NSAPI Gateways

To use NSAPI gateways you modify the gateway properties in Configuration Manager and in the
iPlanet configuration files. If your environment includes reports published to Upfront using a
different gateway, you must update the gateway settings in Upfront to use the new gateway.
Steps to Change Gateway Properties in Configuration Manager

1. In Configuration Manager, click the Server Configuration tab.
2. Expand All Server Groups.
3. For each server group, change the Gateway URL property to identify the NSAPI gateway.
Refer to the list of alternate gateways in the Configuration Manager User Guide for the exact
file name to use for each product.
For example, by default, the Upfront gateway is upfcgi.exe.
To use the NSAPI gateway, change to Gateway URL property to show the Upfront NSAPI
file.
4. From the Actions menu, click Apply Topology.
5. For distributed installations, you must import the server configuration file (cern.csx) on other
computers to complete the configuration.
6. If you changed the gateway for an Upfront server group, complete the following steps.
7. Click the Components tab, and then expand Upfront.Gateway.General.
8. Modify the Web Program Alias to use the same setting you used for the Upfront Gateway
URL on the Server Configuration tab.
Steps to Change Gateway Properties in Upfront
To change the gateway settings for reports already published to Upfront, use the NewsItem
Gateway Manager, which is available from the Administration NewsBox in Upfront.
For more information, see the Cognos Web Portal User Guide.
Change iPlanet Settings for NSAPI Gateways

For iPlanet, you must change several settings in configuration files installed with iPlanet, and, for
UNIX installations, you must modify the start script.
The iPlanet configuration files, obj.conf and magnus.conf, are installed in the /config folder of the
iPlanet installation.

In the following steps, replace <XX> with the prefix of the Cognos product you are configuring.
Cognos Product
Prefix
Cognos Query
cq
imrap
ppds
viz
Upfront
upf
fm
Steps to Modify the iPlanet Configuration Files

1. In obj.conf, for each Cognos product, add the following assign-name directive in the
'<Object name="default">' section before the 'NameTrans fn="pfx2dir"
from="/cognos/cgi-bin"' directive.
NameTrans fn="assign-name" name="<XX>nsapi" from="/cognos/cgi-bin/<XX>nsapi*"
For example, the following assign-name directive is used to implement nsapi for PowerPlay
Enterprise Server.
NameTrans fn="assign-name" name="ppdsnsapi" from="/cognos/cgi-bin/ppdsnsapi*"
2. In obj.conf, for each Cognos product, add the following object section after the '<Object
name="default">' section.
<Object name="<XX>nsapi">
Service fn="<XX>nsapi" method="(POST|HEAD|GET)"
</Object>
For example, the following object section is used to implement nsapi for Upfront.
<Object name="upfnsapi">
Service fn="upfnsapi" method="(POST|HEAD|GET)"
</Object>
3. One NSAPI module services the entire set of server groups for multiple server group
installations. In such a configuration, each server group is distinguished using a unique
URL. For n server groups, you require n NameTrans mappings and n Object elements:
NameTrans fn="assign-name" name="<XX>nsapi<n>" from="< url prefix for nth
group>/cgi-bin/<XX>nsapi*"
Each NameTrans has an associated Object element:

<Object name="<XX>nsapi<n>">
Service fn="<XX>nsapi" method="(POST|HEAD|GET)" GatewayDirectory="<path to cgi-bin
for nth server group>"
</Object>
For example, the following section is used for Cognos Query.

NameTrans fn="assign-name" name="cqnsapi1" from="< url prefix for 1st
group>/cgi-bin/cqnsapi*"
<Object name="cqnsapi1">
Service fn="cqnsapi" method="(POST|HEAD|GET)" GatewayDirectory="<path to cgi-bin for
1st server group>"
</Object>

4. Add the following lines in the Init section of the obj.conf file (for iplanet4) or the magnus.conf
file (for iplanet6):
Init fn="load-modules" shlib="<CGI-BIN> /<XX>nsapi.<EXT> "
funcs="<XX>nsapi,<XX>nsapi-init"
Init fn="<XX>nsapi-init" GatewayDirectory="<CGI-BIN>"
where
<CGI-BIN> is the full path to the installed Cognos cgi-bin directory
<EXT> This extension is based on the platform you are running on. For Windows 'dll', for
HP-UX 'sl', and for AIX and Solaris 'so'.
This ensures that the NSAPI shared library gateways are loaded when you start your
iPlanet server.
For example, the following section is used to implement nsapi for PowerPlay Enterprise
Server on Windows.
Init fn="load-modules" shlib="D:/Program Files/cognos/cer3/cgi-bin/ppdsnsapi.dll
"funcs="ppdsnsapi,ppdsnsapi-init"
Init fn="ppdsnsapi-init" GatewayDirectory="D:/Program Files/cognos/cer3/cgi-bin"
5. If you are running Solaris, append the following to the 'load-modules' directive.
shlib_flags="(default|parent|group)"
6. In the magnus.conf, verify that the StackSize option is set to at least 300000.
Note: You may experience performance issues with request transfers with StackSize values
less than 400000.
7. On all UNIX platforms, create the following symbolic link from the directory that contains the
obj.conf file by typing in the following command:
ln -s /<installation_location>/cer3/cgi-bin/*.enc ./
8. To apply the changes, restart the Web server.
9. If iPlanet is installed on UNIX, complete the following steps to modify the start scripts.
Steps to Modify the Start Script on UNIX

1. Modify the code at the top of your Web server's start script (below #!/bin/sh) to match the
following. Replace <BIN> with the full path to the installed Cognos bin directory and
<CGI-BIN> with the full path to the installed Cognos cgi-bin directory.
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:<CGI-BIN>:<BIN>; export LD_LIBRARY_PATH
LIBPATH=${ LIBPATH }:<CGI-BIN>:<BIN>; export LIBPATH
SHLIB_PATH=${ SHLIB_PATH }:<CGI-BIN>:<BIN>; export SHLIB_PATH
2. If you are running iPlanet on AIX, change the following line in the start script
LIBPATH=${LIBPATH}:${LD_LIBRARY_PATH}:/usr/lib/threads:/usr/ibmcxx/lib:/usr/lib:/lib
; export LIBPATH
to
LIBPATH=${LD_LIBRARY_PATH}:${LIBPATH}:/usr/lib/threads:/usr/ibmcxx/lib:/usr/lib:/lib
; export LIBPATH
3. To apply the changes, restart the Web server.
Steps to Modify the Path Environment Variable on Windows

1. Click Start, Control Panel, System.
2. Select the Environment tab in System Properties.
3. Under System Variables, select the Path variable.
4. Append the path to Cognos bin and cgi-bin.
5. Set the new value.
Part 1: Making Installation Decisions
Chapter 2: Types of Installations

Whenever you install a Cognos product, components are selected, the necessary files are
copied to the computer you choose, properties are configured for each component, and the
configuration is applied. The difference among the types of installations is the extent of choices
you make versus the choices made automatically for you.
What Type of Installation Do I Want?

When you accept the choices made by Cognos, you must still choose a computer and check
that all the prerequisites are met, including installing third-party products. Then after the
installation, we recommend that you test the installation using your own data or the samples
supplied by Cognos.
When you change the choices made by Cognos, some degree of additional preparation is
needed. For minor changes, you may need only to check configuration settings. For a fully
distributed installation with existing data and software, more planning time will be needed.
When you are upgrading from a previous release, more choices must be made; perhaps
retaining two separate environments, running mixed version environments, or changing to a
different topology altogether.
Note: For instructions about configuring mixed version environments, multiple server groups,
and relative URLs, see "Common Configuration Tasks" in the Configuration Manager User
Guide.
Upgrading from any Cognos Series 7 release to Cognos Series 7 Version 2 is covered in this
guide. If you are upgrading from a pre-Series 7 release, you must first upgrade to Cognos
Series 7 using the instructions in the installation guide for your 7.0 product.
Note: This guide does not provide instructions for a minimal installation. Minimal installations
are available for Impromptu Administrator for Windows and PowerPlay Transformer Edition for
Windows and UNIX. A minimal installation is used to install only the components that are
required to run Cognos Series 7, without common security, modeling, or portal functionality.
We highly recommend you also read the overview sections in this chapter, which will help you
choose the type of installation that is best suited to your situation.
Default Installation
When you choose a default installation, you must check the system requirements, choose a
single computer to install the products on, and install the supporting third-party software. The
following choices are automatically made:
All required files are copied to one computer.
Default settings chosen by Cognos are used for configuration.
The default configuration can be automatically applied.
Services and processes are automatically started (if applicable).
Do I Want this Method?

This installation is best used when you are setting up a test or evaluation environment, and
there are no existing conditions that make the default choices inappropriate. This method is also
useful for small production environments. This is the quickest and easiest way to get started.
Your computer must have adequate disk space to hold all the Cognos software, third-party
software, and potentially growing data stores and directories.
If you are a new customer who has no previous versions of Cognos products and no previous
versions of the third-party products and you want to install the software for evaluation or testing,
this is the method you would choose.
If you review the default settings and components, you may find you want all the default
components, but a few configuration settings need to be changed. You can still choose a default
installation. However, you can make configuration changes for some properties in the
Configuration Wizard, which appears after the installation program has copied the files, or by
choosing to launch Configuration Manager. After you change the necessary settings, you apply
the configuration settings to your computer.
For example, if you already have a directory server that is not using the default port, or a base
distinguished name (DN) that is different from the Cognos default, you would simply use the
Configuration Wizard to change these settings for the directory server properties.
Note: For Cognos Series 7 Alerts/Notifications, even the default installation option requires you
to complete some configuration. Specific settings cannot be determined automatically because
they depend on the third-party database you are using. The following third-party databases are
supported: Oracle, IBM DB2, Microsoft SQL Server, and Informix. You must configure the
Cognos product for the type of database you are using.
Where are the Instructions I Must Follow?

For instructions about how to install all components using default configurations settings, or with
minor configuration changes, see "Installing by Using Default Settings" (p. 61).
Custom Installation
If you want to make all the choices, you will want to do a full custom installation. For example,
if you want to use a distributed environment and choose the components and where you
want to copy them to, you will want to do a custom installation.
if you are implementing multiple server groups, you can use the custom installation option to
install only the required components on one or more computers.
For more information about multiple server groups, see the Configuration Manager User
Guide.
This installation method lets you install server components, such as dispatchers, server
components and multiple instances, across more than one computer and even across platforms.
It provides the most flexibility and requires the most knowledge. You will need to know what has
to be configured for each component so that components can communicate together.
To use this installation method, you copy only the components you want on one computer by
selecting the Custom installation type and then selecting specific components. Then during the
installation process, you indicate one of two options:
Open Configuration Manager and configure the components now.
Exit the installation and configure the components later.
You then repeat this process on each computer until you have all components installed and
configured to complete the installation.
Do I Want this Method?

If you are setting up a production environment and want maximum performance, you will likely
want this method. For example, you may want to install the application server components on
one computer and the gateways and Web server components on another computer.
You may also want to separate the security components and install the ticket server on the same
computer that you have the third-party directory server installed on.

If you have users that will be using only certain components such as administration tools, you
will likely want this method to install only the required pieces at the appropriate locations even if
you choose the default configuration for the components you selected. For example, it is often
convenient to have a local Windows workstation as the administration computer. For example,
from this workstation, an administrator can publish report sets to Upfront.

If choosing this method, we highly recommend you first read the Planning Advanced
Installations Guide. We also recommend that you create an installation schematic and use the
Installation Checklist, (p. 211) to record all the configuration settings you plan to use. For
instructions about how to complete the installation, see "Installing by Distributing
Components" (p. 77).
If you are doing a mixed installation and are distributing server components across UNIX and
Windows computers, you will need this installation guide as well as the corresponding
installation guide for the other platform. You can download the other installation guide from the
Cognos support site (http://support.cognos.com).
Upgrade Installation
If you are a customer who has a previous release of Cognos Series 7, you will have some
choices to make before you upgrade. You can choose to upgrade some or all of the Cognos
products you use from 7.0 to 7.1.
You may have Cognos applications that you built and want to migrate to the next version. In
this case, you will want to do a full upgrade both of the software and of your application data.
You have no Cognos application data, or none that you want to migrate to the new version.
In this case, you will just upgrade the software.
Additionally you will decide what computer(s) you are going to use for the upgrade:
If you are using the same computer(s) that currently run your previous version, you will do
an in-place upgrade.
Service will be interrupted while you are installing the new software and upgrading the
application data. However, you can upgrade one product at a time and keep other products
running in the old version.
If you are using separate computer(s) for the upgrade, you will do a staged upgrade.
Service can continue because your previous version is running on different computer(s).
The new environment may simply be your test environment and after you are satisfied that
the new version is upgraded and tested, you may intend to deploy everything back to your
production environment.
Software Upgrade - Do I Want This Method?

The software upgrade is the first step for all upgrade scenarios. You will need to decide if you
want to continue to run your previous version of Cognos Series 7 and whether you will run it at
the same time as the new version or switch back and forth between versions. You can continue
to run your 7.0 data with your 7.1 software, but your applications will not be able to take
advantage of new features.
You can, for example, install the new version using all the same port values and web aliases,
which means that end users dont have to learn new aliases, but then only one version can be
active at a time. You will have some overhead in the management of services and processes,
making sure that the desired version is running and other services are stopped.
If you want to run both versions at the same time, you must choose different ports, create a
second set of Web aliases, use different names for data stores and as a result, maintain a
separate server configuration file (.csx). If you plan to upgrade your applications in a piecemeal
manner, one product at a time, you will find it convenient to maintain both the old and new
environments for some time.

If you are upgrading to computer(s) with the same topology as was used in your previous
environment, you may be able to re-use your existing configuration information, with minor
changes, for example, to your configuration scripts (.ccp) and server configuration file (.csx). For
example, you intend to keep the same platforms, keep the components distributed in the same
way, and set up the same server groups as you had in your previous environment.
You can, however, coincide an upgrade with a move to a new topology, for example, moving from
Windows to UNIX or from one flavour of UNIX to another, or setting up server groups differently.
In this case, you will need to make more extensive configuration changes and will not likely try to
reuse any existing configuration files.

Just as for a custom installation, we recommend you use the Installation Checklist in this
document to record all the configuration settings you plan to use. If you plan to run both versions
of software at the same time, see Mixed Version Environments in this document before you
install the software. If you are changing topology with your upgrade, see Planning Advanced
Installations Guide and Configuration Manager User Guide.
For instructions about how to complete an upgrade installation of the software, see Installing to
Upgrade in this document.
Full Upgrade - Do I Want This Method?

If you want to migrate your Cognos applications to the next version, you will do a software
upgrade followed by a data upgrade. If you are doing a staged upgrade, you will need to deploy
your application data from the computer(s) running the previous version to the equivalent
computer(s) running the new version. You will need to follow a specific order for upgrading
server application data and then client application data if you want to upgrade in a piecemeal
manner and keep applications working in a mixed environment while you are upgrading.

For instructions about upgrading your application data, see Upgrading Application Data and
Upgrading Client Data in this document. Lastly, when you are ready to switch permanently to the
new version, see Moving Permanently to Your New Version in this document.
Other Installation Types

You can also choose other installation methods such as unattended installations. All installation
tasks run automatically, without any user intervention. You can use the same installation script
for a group of computers that have the same configurations, instead of having to set up each
computer individually.
For more information, see "Other Types of Installations" (p. 175).
Chapter 3: Cognos Series 7 Components

If you choose a default installation, all the components described in this section are selected for
you and are configured with default settings. If you choose a custom installation, you can select
just the components you want to install and then complete the configuration. In either case, you
must be aware of system requirements and other third-party requirements before doing any
installation.
Cognos Series 7 Reporting

Cognos Series 7 Reporting provides the tools you need to publish your Impromptu reports on
the Web. Report consumers do not require Impromptu to view or run Impromptu reports from
their Web browsers, and can view reports in .pdf, .xls, .csv, or HTML format. Report consumers
use Upfront, the Cognos Web portal, to view and run reports.
Impromptu Web Reports Server

The Impromptu Web Reports server performs the tasks of queueing, scheduling, and running
Impromptu Web Reports.
Impromptu Web Reports Gateway

The gateway component is, by default, a common gateway interface (CGI) program that handles
only Web requests. Impromptu Web Reports also includes optional ISAPI and NSAPI gateways.
The Impromptu Web Reports gateway uses the server configuration file (.csx) to identify the
dispatcher to pass each request to. It then communicates directly with the Impromptu Web
Reports server to return a document to the user's Web browser after the request is processed.
Impromptu Web Reports Data Store

The Impromptu Web Reports data store is an ObjectStore database that stores the metadata
information for Impromptu Web Reports. ObjectStore is installed separately before installing
Impromptu Web Reports.
Upfront Server
An Upfront server processes requests that maintain and present the Upfront NewsIndex. The
Upfront server includes a dispatcher that manages the queue and forwards the requests to the
Upfront server.
Upfront Gateway
only Web requests. Upfront also includes optional ISAPI and NSAPI gateways. The Upfront
gateway uses the server configuration file (.csx) to identify the Upfront server to pass each
request to. Impromptu Web Reports server and Upfront communicate with each other through
their gateways.
Upfront Data Store

The Upfront data store is a database that stores the Upfront resources, such as NewsBoxes and
NewsItems, that Upfront manages.
Upfront Event Server

If Cognos NoticeCast is installed for use with Impromptu Web Reports, the Upfront Event
Server monitors the Upfront data store for changes to NewsBoxes and NewsItems and forwards
information about the changes to the Cognos NoticeCast server. If a user has specified that the
change should initiate a notification, Cognos NoticeCast generates the notification and sends it
to members of the associated email list. The Upfront event server is located on the same
computer as the Upfront server.

You can manage non-Cognos documents within Upfront. For example, you can upload your
timesheet or expense report as an Upfront NewsItem. You can distribute and secure these
non-Cognos documents after uploading them to Upfront. For example, you can secure your
expense report to ensure that only your manager can access it. You can maintain several
versions of uploaded documents. For example, you can maintain one timesheet for every month
and choose which one you want to make available.
Ticket Server
The ticket server is a security application that issues tickets used to maintain single signons for
users of Web-based products. A ticket allows users to access multiple applications without
having to re-enter authentication data.
Windows Common Logon Server

Windows Common Logon Server retains signon information so that users can move easily
between Cognos products and components in Windows. This component integrates with
Access Manager.
Access Manager Administration

Access Manager Administration is the tool you use to set up and maintain security in Access
Manager, the authentication and authorization service for all Cognos products. Access Manager
works with the security structure contained in the directory server. Access Manager
Administration includes the Access Manager Trusted Signon Software Development Kit (SDK),
which is used to create a trusted signon plug-in. With the plug-in, you can use your existing
security infrastructure with Access Manager.
Cognos Server Administration

Cognos Server Administration is a single user interface that provides access to the
administration tools:
Impromptu Web Reports Report Administration
Use to publish and manage report sets.
Impromptu Web Reports Server Administration
Use to manage Impromptu Web Reports servers.
Upfront Server Administration
Use to manage Upfront servers.
Use to set up and maintain security in Access Manager, the authentication and
authorization service for all Cognos products.
Deployment Manager
Use to pack your Cognos application data (such as Cognos Query queries, PowerPlay
reports and Impromptu Web Reports reports) into a transportable medium that can be
unpacked into another Cognos server environment. Deployment Manager should not be
used to back up your data.
Impromptu Web Reports Tools

The Impromptu Web Reports tools include
Configuration Manager
Use to configure any Cognos Series 7 component or to configure multiple components at
once. For example, you can stop all your Cognos Series 7 services simultaneously.
Access Manager Configuration Wizard
Use to specify your authentication source to Access Manager. The default installation
automatically specifies the Default namespace in Sun ONE Directory Server as the
authentication source.
Access Manager Batch Maintenance
Use to automate maintenance tasks required to manage security in Access Manager.
Access Manager Registration Wizard
Use to register a trusted signon plug-in with Access Manager.
User Defined Functions Software Development Kit (SDK)
Use to create custom business functions for your reporting environment.
Impromptu Administrator
Impromptu Administrator is part of Cognos Series 7 Reporting. You can use Impromptu
Administrator to create Impromptu reports, and create and administer catalogs. The reports you
create can then be published as Impromptu Web Reports.
Architect
Architect is the Cognos data modeling tool provided with Impromptu Administrator. Use
Architect to export an Architect package of objects that represent your business model to an
Impromptu catalog. Architect requires the installation of ObjectStore, a third-party database.
Note: Architect is available with a default installation of Impromptu Administrator with the
following exceptions:
It is not available for multi-byte locales.
It is not available with a minimal installation.
Impromptu Administrator Tools

The Impromptu Administrator tools include
Scheduler
Use to run reports and macros at specified times.
Cognos Script Editor
Use to write, compile, and run macros in the CognosScript language. You can create a user
interface for your macro applications using the CognosScript Dialog Editor.
Audit Configuration and Audit File Processor
Use to enable audits of Impromptu reports and to specify the location and size of the audit
file. You can also set options for processing audit data.
PowerPrompts Developer Studio

Use to create a PowerPrompts application, which is a series of HTML pages that allow
report consumers to select the information they want to see in an Impromptu Web Report.
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with Impromptu Web Reports, Impromptu Administrator, Upfront, and the related administration
tools.
Quick Tours
Quick Tours serve as online introductions to Cognos products. The Impromptu Quick Tour is
installed by default with Cognos Series 7 Reporting.
Samples
Samples provide some representative data that you can use with tutorials and for testing your
installation, especially if you do not have your own data created with previous releases.
For more information about samples, see the Installation Testing and Samples Setup Guide.
Cognos Series 7 Query

Cognos Query is a reporting tool that you use to explore, modify, and create queries on the
Web. You can use the queries to explore information and answer specific questions. Cognos
Query is part of an enterprise reporting solution, which includes Upfront, the Web-based point
of entry for information consumers.
Cognos Query Server

The Cognos Query server executes queries created by the user, and delivers the results.
Cognos Query Gateway

The gateway is, by default, a common gateway interface (CGI) program that receives requests
from Web browsers. Cognos Query also includes optional ISAPI and NSAPI gateways. The
Cognos Query gateway uses the server configuration file (.csx) to identify the dispatcher. The
Cognos Query gateway communicates with the Cognos Query dispatcher to identify the Cognos
Query server to pass each request to. It then communicates directly with the Cognos Query
server to return a document to the user's Web browser after the request was processed.
Cognos Query Dispatcher

The Cognos Query dispatcher balances the processing load on a Cognos Query server. The
dispatcher determines which Cognos Query server is the least busy and the gateway forwards
the request to that server. There is one dispatcher per server group. A server group is one or
more servers that contain the same information and can service the same requests.
Cognos Query Data Store

The Cognos Query data store is the database that stores query definitions and the runtime
version of the Architect model.
Upfront Server
Upfront server.
Upfront Gateway
request to. Cognos Query and Upfront communicate with each other through their gateways.
Upfront Data Store

NewsItems that Upfront manages.

If Cognos NoticeCast is installed for use with Cognos Query, the Upfront event server monitors
the Upfront data store for changes to NewsBoxes and NewsItems and forwards information
about the changes to the Cognos NoticeCast server. If a user has specified that the change
should initiate a notification, Cognos NoticeCast generates the notification and sends it to
members of the associated email list. The Upfront event server is located on the same computer
as the Upfront server.

Architect
Architect is the data modeling tool integrated with Cognos Query. Use Architect to import your
metadata and create an Architect package of objects that present your business model.
Architect also includes the Cognos Query Publish for Architect component, which you can use
to publish Architect packages to Upfront for Cognos Query users. Architect requires the
installation of ObjectStore, a third-party database.
Ticket Server

Access Manager.


Cognos Query Server Administration
Use to manage Cognos Query servers.

Deployment Manager
Use to pack your Cognos application data (such as PowerPlay reports, Impromptu Web
Reports reports, and Cognos Query queries) into a transportable medium that can be
unpacked into another Cognos server environment. Deployment Manager should not be
used to back up your data.
Cognos Query Tools

The Cognos Query tools include
Books
with Cognos Series 7 Query.
Samples
Cognos Series 7 OLAP

Cognos Series 7 OLAP provides users data access to cubes and reports in a local, wide-area or
Web-based network. PowerPlay Enterprise Server can handle simultaneous requests from any
client type. Users can use their Web browser to open reports or cubes stored in Upfront or
PowerPlay Enterprise Server. They can also use PowerPlay for Windows or PowerPlay for Excel
to access any reports or cubes on the server.
PowerPlay Enterprise Server Gateway

only Web requests. PowerPlay Enterprise Server also includes optional ISAPI and NSAPI
gateways. The PowerPlay Enterprise Server gateway uses the server configuration file (.csx) to
identify the PowerPlay dispatcher to pass each request to.
PowerPlay Enterprise Server Dispatcher

The dispatcher component receives PowerPlay requests directly from a Windows or Web client.
A dispatcher manages the request queue and forwards requests to a query or report processor.
PowerPlay Enterprise Server Query and Report Processors

The query and report processors return results for all PowerPlay requests. The query processor
returns results for cube requests and the report processor returns results for report requests.
PowerPlay Enterprise Server Windows Launch Agent

The Windows Launch Agent lets users open a report published to Upfront in PowerPlay for
Windows.
PowerPlay Enterprise Server Cleanup Service

The PowerPlay Enterprise Server Cleanup utility is required only when a PowerPlay Enterprise
Server gateway is installed on a computer without a dispatcher. The Cleanup utility deletes older
temporary files from the Temporary Resource (/ppwb) location.
Upfront Server
Upfront server.
The Upfront server is not available with a minimal installation.
Upfront Gateway
request to. PowerPlay Enterprise Server and Upfront communicate with each other through their
gateways.
The Upfront gateway is not available with a minimal installation.
Upfront Data Store

The Upfront data store is not available with a minimal installation.

If Cognos NoticeCast is installed for use with PowerPlay Enterprise Server, the Upfront event
server monitors the Upfront data store for changes to NewsBoxes and NewsItems and forwards
information about the changes to the Cognos NoticeCast server. If a user has specified that the
change should initiate a notification, Cognos NoticeCast generates the notification and sends it
to members of the associated email list. The Upfront event server is located on the same
computer as the Upfront server.

Ticket Server

The ticket server is not available with a minimal installation.

Access Manager.

Access Manager Administration and related tools are not available with a minimal installation.

PowerPlay Enterprise Server Administration
Use to manage PowerPlay Enterprise servers.
Use to manage Upfront servers. (Not available with a minimal installation.)
authorization service for all Cognos products. (Not available with a minimal installation.)
Deployment Manager
Use to pack your Cognos application data (such as PowerPlay reports, Impromptu reports,
Cognos Query queries) into a transportable medium that can be unpacked into another
Cognos server environment. Deployment Manager should not be used to back up your data.
(Not available with a minimal installation.)
PowerPlay Enterprise Server Tools

The PowerPlay Enterprise Server tools include
PowerPlay Connect
Use to connect to OLAP cubes built with third-party products.
PowerPlay
PowerPlay is the Windows version of the Cognos analysis and reporting tool for OLAP data. Use
PowerPlay to view cubes created with PowerPlay Transformer or other third-party OLAP
servers.
PowerPlay for Excel

Use PowerPlay for Excel for OLAP analysis and reporting if you prefer to work in a Microsoft
Excel environment.
PowerPlay Transformer (Personal Edition)

PowerPlay Transformer is an OLAP modeling tool that you use to build multidimensional models
from your source data. The models are used to create cubes that can be viewed with PowerPlay.
This personal edition of PowerPlay Transformer, provided with PowerPlay, is not installed by
default, but available for selection when you do a custom installation. The personal edition does
not include Architect.
PowerPlay User Tools

The PowerPlay User tools include
Scheduler
Script Editor
User Defined Functions SDK
Books
with Cognos Series 7 OLAP.
Quick Tours
Quick Tours serve as online introductions to Cognos products. Quick Tours for PowerPlay for
Windows and PowerPlay for Excel are installed by default with Cognos Series 7 PowerPlay
User.
Samples
Cognos Series 7 PowerPlay Transformer Edition

The Cognos Series 7 PowerPlay Transformer Edition provides PowerPlay Administrators with
the multidimensional modeling, transformation, extraction, analyzing, and reporting tools for the
PowerPlay family of products.
PowerPlay Transformer
PowerPlay
servers.
PowerPlay for Excel

Excel environment.
Architect
Architect is the data modeling tool provided with PowerPlay Transformer. Use Architect to import
your metadata and create an Architect package of objects that present your business model,
which PowerPlay Transformer can then use as its data source. Architect requires the installation
of ObjectStore, a third-party database.
Note: Architect is available with a default installation of Cognos Series 7 PowerPlay Transformer
Edition (Windows) with the following exceptions:

Access Manager.

PowerPlay Transformer Edition Tools

The PowerPlay Transformer Edition tools include
Scheduler
User Defined Functions SDK
Books
with the products in Cognos Series 7 PowerPlay Transformer Edition.
Quick Tours
Windows and PowerPlay for Excel are available with Cognos Series 7 PowerPlay Transformer
Edition. If you want to install Quick Tours, you must do a custom installation and select them.
Samples
Cognos Series 7 Alerts/Notifications

Cognos Series 7 Alerts/Notifications lets users detect and manage time-critical events in their
business applications. Users create NoticeCast agents, the rule-driven, objects that present
your business model, that listen for, or respond to, events and then send out email notifications
to interested parties.
NoticeCast Server
The NoticeCast server executes queries created by the authoring tool and delivers the resulting
notifications by email. If you have other Cognos Series 7 products installed (such as Cognos
Query, PowerPlay Enterprise Server, Impromptu Web Reports) which have NoticeCast
integration, queries created with these products can also be processed by the NoticeCast
server.
Upfront Server
Upfront server.
Upfront Gateway
request to. Cognos server products communicate with Upfront through their gateways.
Upfront Data Store

The Upfront data store is a database which stores the Upfront resources, such as NewsBoxes
and NewsItems that Upfront manages. In addition, Cognos NoticeCast requires a separate data
store, called the NoticeCast data store, for which you need a third-party database.

The Upfront event server monitors the Upfront data store for changes to NewsBoxes and
NewsItems and forwards information about the changes to the Cognos NoticeCast server. If a
user has specified that the change should initiate a notification, Cognos NoticeCast generates
the notification and sends it to members of the associated email list. The Upfront event server is
located on the same computer as the Upfront server.

NoticeCast Data Store

Cognos NoticeCast stores information in a data store located in a third-party RDBMS (relational
database management system). Cognos NoticeCast supports data stores located in Oracle,
Microsoft SQL Server, Informix, or IBM DB2.
Ticket Server

Access Manager.
NoticeCast Authoring
The NoticeCast authoring tool lets users create agents that access third-party data sources.
Users can make the agents available to other users by publishing the agent to Upfront.
The NoticeCast authoring component is a Java application that runs in a Microsoft Java Virtual
Machine (JVM) under Windows. If installing the authoring component on a Windows NT or
Windows 98 computer that does not already have a JVM, you are prompted to install a JVM.
Windows 2000 SP2 computers have a JVM by default. For instructions, see the Additional
Products and Services Appendix.

Alerts and Notifications
Use to manage the NoticeCast environment.
Portal
Security
Deployment Manager
Use to pack your Cognos application data (such as PowerPlay reports, Impromptu Web
Reports reports, Cognos Query queries) into a transportable medium that can be unpacked
into another Cognos server environment. Deployment Manager should not be used to back
up your data.

NoticeCast Tools
The NoticeCast tools include
Books
with NoticeCast, Upfront, and the related administration tools.
Samples
installation. Access Manager and Upfront samples are provided with Cognos Series 7
Alerts/Notifications.
Cognos Series 7 PowerPlay User

Cognos Series 7 PowerPlay User provides users data access to cubes and reports in a local
environment using the Windows client applications PowerPlay or PowerPlay for Excel. Cognos
Series 7 PowerPlay User also includes PowerPlay Transformer, which you can use to build the
cubes you will see in PowerPlay.
PowerPlay
servers.
PowerPlay for Excel

Excel environment.
PowerPlay Transformer (Personal Edition)

This personal edition of PowerPlay Transformer, provided with PowerPlay, is not installed by
default, but available for selection when you do a custom installation. The personal edition does
not include Architect.

Access Manager.
PowerPlay User Tools

The PowerPlay User tools include
Lets administrators automate maintenance tasks required to manage security in Access
Manager.
Scheduler
Books
with Cognos Series 7 PowerPlay User.
Quick Tours
Windows and PowerPlay for Excel are available with Cognos Series 7 PowerPlay User. If you
want to install Quick Tours, you must do a custom installation and select them.
Samples
Cognos Series 7 Impromptu User

Impromptu is a database reporting tool. You use Impromptu to easily create queries, run them
against your relational database, and format the results.
Impromptu User
Use Impromptu to create, view, and distribute reports. You can easily add filters to rows or
columns in reports; group and sort information; and use picklists, prompts, and exception
highlighting to increase the value of standard reports. Output can be to a variety of formats,
including PDF and HTML, or saved as Microsoft Excel files.
Impromptu Tools
The Impromptu tools include

Manager.
Scheduler
report consumers to select the information they want to see in a report.
Books
A complete PDF documentation set is provided for Impromptu and the related tools.
Quick Tours
available with Impromptu User. If you want to install the Quick Tour, you must do a custom
installation and select it.
Samples
Cognos Series 7 Impromptu Administrator

Impromptu is a database reporting tool. With Impromptu Administrator, you create catalogs,
control security, and maintain your Impromptu environment.
Use Impromptu Administrator to create catalogs that contain metadata from your relational
database. The catalog gives Impromptu users a business-oriented view of the database.
Architect
Architect is the Cognos data modeling tool provided with Impromptu Administrator by default.
Use Architect in Cognos Series 7 Impromptu Administrator to export an Architect package of
objects that present your business model to an Impromptu catalog. Architect requires the
installation of ObjectStore, a third-party database.
Note: Architect is available with a default installation of Cognos Series 7 Impromptu
Administrator, with the following exceptions:

Access Manager.

Impromptu Administrator Tools

The Impromptu Administrator tools include
Manager.
Scheduler
report consumers to select the information they want to see in an Impromptu Web Report.
Books
A complete PDF documentation set is provided for Impromptu Administrator and the related
tools.
Quick Tours
available with Impromptu Administrator. If you want to install the Quick Tour, you must do a
custom installation and select it.
Samples
Cognos Series 7 Visualization

Cognos Series 7 Visualization is a Web application that distributes visualizations created by
authors using the authoring version of Cognos Visualizer through an intranet. Report consumers
view these visualizations using a Web browser.
The following products and components are part of Cognos Series 7 Visualizer for Windows.
Cognos Visualizer Gateway

The Cognos Visualizer gateway component is a common gateway interface (CGI) program that
receives requests from Web browsers (consumers) through a Web server, forwards them to the
Cognos Visualizer Web Edition server, and sends responses back to the Web browsers. The
gateway must be installed on the same computer as the Web server.
Cognos Visualizer Dispatcher

The dispatcher manages the request queue and forwards requests either to a dispatcher on
another computer or to a query processor on the same computer. A dispatcher can reside as a
standalone component.
Cognos Visualizer Query Processor

The query processor is the component of the server that generates results from the data
sources for specific visualizations. More than one instance of the query processor
(vizwebqp.exe) can run on one computer. While a dispatcher can reside as a standalone
component, the query processor must always be installed on a computer with a dispatcher. The
server can create multiple instances of the query processor to balance the request load.
Upfront Server
Upfront server.
Upfront Gateway
The gateway component handles only Web requests. The Upfront gateway uses the server
configuration file (.csx) to identify the Upfront server to pass each request to. Cognos Visualizer
server and Upfront communicate with each other through their gateways.
Upfront Data Store


If Cognos NoticeCast is installed, the Upfront event server monitors the Upfront data store for
changes to NewsBoxes and NewsItems and forwards information about the changes to the
Cognos NoticeCast server. If a user has specified that the change should initiate a notification,
Cognos NoticeCast generates the notification and sends it to members of the associated email
list. The Upfront event server is located on the same computer as the Upfront server.
Ticket Server

Access Manager.


Cognos Visualizer Server Administration
Use to configure and tune the server components (gateway, dispatchers, query processors)
and publish visualizations.
Deployment Manager
Use to pack your Cognos application data (such as PowerPlay reports, Impromptu reports,
Cognos Query queries, and Cognos Visualizer visualizations) into a transportable medium
that can be unpacked into another Cognos server environment. Deployment Manager
should not be used to back up your data.
Cognos Visualizer Tools

The Cognos Visualizer tools include
automatically specifies the default namespace in Netscape Directory Server as the
PowerPlay Connect
Cognos Visualizer Authoring Tool

Use the Cognos Visualizer authoring tool to create visualizations based on your corporate data.
You create visualizations to share information with other members of your organization. Report
consumers view and explore visualizations using the authoring tool, the Cognos Visualizer Web
Edition Client or the Cognos Visualizer Web Edition Viewer. The visualizations help to identify
and understand the underlying trends and relationships that affect your business.
Cognos Visualizer Web Edition Client

Report consumers use the Cognos Visualizer Web Edition Client to open visualizations in a
Web browser. The Web Client software includes a Java plug-in and the required Java Runtime
Environment.
Cognos Visualizer Web Edition Viewer

Report Consumers can use the Cognos Visualizer Web Edition Viewer to open visualizations in
a Web browser. The viewer does not require a Java plug-in or the Java Runtime Environment.
Books
with Cognos Series 7 Visualizations.
Quick Tours
Quick Tours serve as online introductions to Cognos products. Cognos Visualizer Web Edition
Quick Tour and Cognos Visualizer Web Edition Viewer Quick Tour are installed with the gateway
for Web products.
Samples
Cognos Visualizer User Series 7

Cognos Visualizer User Series 7 provides report authors with a variety of options for creating,
presenting, and distributing visual representations of complex data for analysis. Report authors
can consolidate company information from many data sources in a single visualization to
provide a comprehensive vision of the enterprise.
The following products and components are part of Cognos Visualizer User Series 7.
Cognos Visualizer
Use Cognos Visualizer to create visualizations based on your corporate data. Cognos Visualizer
is primarily a presentation and report authoring tool. You create visualizations to share
information with other members of your organization. The visualizations help the members of
your organization to identify and understand the underlying data trends and relationships that
affect your business.
Geoset Manager
Use Geoset Manager to work with map layers and to ensure that custom maps made using
MapInfo Professional are compatible with Cognos Visualizer. Cognos Visualizer supports
MapInfo *.tab files. You can install Geoset Manager using the custom installation option.


Access Manager.

The Cognos Visualizer tools include
PowerPlay Connect
Books
with Cognos Visualizer User Series 7.
Samples
Cognos Supplementary Software

The Cognos Supplementary Software CD contains the Sun ONE Directory Server installation
kits. Sun ONE Directory Server is a lightweight directory access protocol (LDAP) database used
to store the security information that Access Manager manages.
If you want to implement security for multiple users, Sun ONE Directory Server or an equivalent
product (such as Windows 2000 Active Directory) must be installed and configured using the
instructions provided in the Cognos Series 7 Supplementary Software Installation Guide.

Alternatively, you may want to use a local authentication export (.lae) file instead of a directory
server when you implement a single user installation or for a demonstration environment. If you
plan to use an .lae file, you do not need to install a directory server.
Support Files
The install menu provides access to additional third-party products which must be installed and
configured using the instructions provided later in this guide. You may already have some of
these products on your computer or you may not be installing the Cognos products that require
this software. These third-party products include:
eXcelon ObjectStore is the database that must be installed as the data repository for
Impromptu Web Reports, and for any product that is integrated with Architect.
Architect is used with Cognos Query, Impromptu Administrator, and PowerPlay Transformer.
Adobe Acrobat Reader must be used to view the online books.
Microsoft Distributed Component Object Model (DCOM) must be installed if you are using
Windows 98.
Microsoft Data Access Components (MDAC) 2.7 is required for using some product
samples on Windows (for example, Architect samples).
Microsoft Java Virtual Machine (JVM) must be installed on Windows NT and Windows 98
computers for Cognos NoticeCast. Windows 2000 SP2 computers have the JVM by default.
Default Settings
You can apply default configuration settings or use Configuration Manager to customize your
configuration.
The default settings include user IDs and passwords, a default namespace, and port numbers. If
you have any reason not to use the default settings, you must use Configuration Manager to
configure these properties. The following sections list the default Cognos settings.
User IDs and Passwords

The following table provides the default user IDs and passwords that are set during the default
installation. The default Cognos user is created in your namespace by Access Manager.
Logon to
Description
User ID
Password
Sun ONE Directory Server Use to log on to the

Administration by way of
iPlanet Console as
the iPlanet Console
administrator to manage
Sun ONE Directory
Servers.
admin
admin1234
Sun ONE Directory Server Use to log on to the

Administration by way of
iPlanet Console as
the iPlanet Console
Unrestricted User to
access Sun ONE
Directory Server with
unlimited privileges.
cn=Directory
Manager
admin1234
Logon to
Description
User ID
Password
Access Manager
Administration
Use to log on to Access

Manager Administration
as Runtime Administrator
Distinguished Name to
connect to Sun ONE
Directory Server.
cn=Directory
Manager
admin1234
Your Cognos product
Use initially to log on to

your Cognos product.
Administrator
no password
This is the default Cognos

user in your namespace.
Namespace
The default installation creates a namespace in the Sun ONE Directory Server called Default
and uses the following settings to connect to the Sun ONE Directory Server:
Directory server port: 389
Unrestricted User/Runtime Administrator Distinguished Name:
cn=Directory Manager
Directory Suffix: o=Cognos, c=CA
Ports
After the default installation, the following components are automatically configured to
communicate using the default ports indicated.
Cognos Series 7 Reporting uses the following ports by default.
Component
Default port
Sun ONE Directory Server
389
Ticket server
9010
Web server
80
Impromptu Web Reports server
8020
Upfront search engine
4455
Upfront event server
5000
Upfront dispatcher
8030
Upfront server administration
8031
Upfront remote tracing
8032
Upfront data store
8150
8030
ObjectStore
Server
Cache Manager (server)
Cache Manager (client)
Notifications
PowerPrompts
Test server
Data access server
51025
51031
51041
51050
2424
2425

Cognos Series 7 Query uses the following ports by default.
Component
Default port
389
Ticket server
9010
Web server
80
Cognos Query server

Server
Administration
Data Store
Dispatcher
25000
24000
24997
24999
4455
5000
Upfront dispatcher
8030
8031
8032
Upfront data store
8150
8030
ObjectStore
Server
Notifications
51025
51031
51041
51050

Cognos Series 7 OLAP uses the following ports by default.
Component
Default port
389
Ticket server
9010
Web server
80
8010
4455
5000
Upfront dispatcher
8030
8031
8032
Upfront data store
8150
8030
Cognos Series 7 Alerts/ Notifications uses the following ports by default.

Component
Default port
389
Ticket server
9010
Web server
80
NoticeCast dispatcher
10998
NoticeCast data store
10999
4455
5000
Upfront dispatcher
8030
8031
8032
Upfront data store
8150
8030

Cognos Series 7 PowerPlay Transformer Edition uses the following ports by default.
Component
Default port
389
ObjectStore
Server
Notifications
51025
51031
51041
51050
Cognos Series 7 Visualization uses the following ports by default.

Component
Default port
389
Ticket server
9010
Web server
80
Cognos Communication service
9041
Cognos Visualizer dispatcher
8060
4455
5000
Upfront dispatcher
8030
8031
8032
Upfront data store
8150
8030
Services
After the default installation, the following services for Cognos Series 7 are automatically
started. Some services are shared among Cognos products:
Cognos Impromptu Web Reports Service Manager

Cognos Upfront Administration Service (shared)
Cognos Upfront Data Store (shared)
Cognos Upfront Dispatcher (shared)
Cognos Ticket Server (shared)
Sun ONE Directory Server (shared)
ObjectStore Cache Manager R6.0 (shared)
ObjectStore Server R 6.0 (shared)

Cognos Query Server Manager
Cognos PowerPlay Enterprise Server

Cognos NoticeCast Dispatcher

Cognos NoticeCast Data Store
Cognos Upfront Administration (shared)

Note: These services are not required for a minimal installation.
Cognos Series 7 PowerPlay User
none
Cognos Series 7 Impromptu Administrator

Note: These services are not required for a minimal installation.
Cognos Series 7 Impromptu User
none
Cognos Visualizer Web Edition

Cognos Visualizer User Series 7
none
Naming Conventions Used in this Document

This document includes references to path names and renditions related to Cognos products.
Because path names and renditions may be different based on the Cognos products you install,
or whether you change the default values during installation, the following generic references
appear in this document:
installation_location represents the location of a Cognos component or folder.
For example, on Windows, the default location for temporary files used by PowerPlay
Enterprise Server 7.1 is \ProgramFiles\Cognos\cer3\ppserver. The generic reference format
for this path is installation_location\ppserver.
cern represents the rendition of the Cognos component.
For example, for Cognos Series 7 Version 2, the server configuration file is cer3.csx. The
generic reference format for server configuration files is cern.csx.
Chapter 4: Mixed Version Environments

Mixed version environments give you greater control over many installation considerations, such
as managing upgrades.
In a mixed version environment, different versions of Cognos Series 7 products run at the same
time. The different versions may run as separate environments, or the different versions may
work together as a single application sharing common components, such as Upfront and
Cognos security components. The different versions of components can be located on one
computer or distributed across computers that interact with each other.
For example, PowerPlay Enterprise Server 7.0 and PowerPlay Enterprise Server 7.1 can share
the same Upfront 7.1 NewsIndex and the same namespace. Users can drill through and use a
single sign on in PowerPlay Enterprise Server 7.0 and PowerPlay Enterprise Server 7.1. Note
that the namespace must be kept at the schema version format that is compatible with Series
7.0 and earlier versions.
Mixed version environments are typically used to support an upgrade strategy in which you
upgrade different products at different times. You can upgrade your server components one at a
time. This produces intermediate states where you are running a combination of 7.0 and 7.1
components.
You can continue to run your Cognos Series 7 applications for some time even after you
complete the upgrade, such as while you test the new environment. When you are ready to
switch permanently to the 7.1 environment, you uninstall the 7.0 components and make some
permanent changes, such as upgrading the namespace to the current (7.1) schema version
format. If multiple servers balance the request load in a server group, you must upgrade all
servers at the same time. You cannot run different versions of servers to handle load balancing
of the same requests.
Mixed Versions Installed on the Same Computer Using Shared Components

You can install mixed versions on the same computer. Shared components can be on the same
computer, or located on one or more additional computers. You must use Upfront 7.1 when the
7.0 and 7.1 components are configured as a single application. This example can use Windows,
UNIX, or a mixed platform environment.
Upfront 7.1
Directory Server (7.0 schema)
PowerPlay Enterprise Server 7.0
Cognos NoticeCast 7.0
Mixed Versions Managed as Separate Applications

You can install mixed versions on the same computer. The different versions can exist as
separate applications. This example can use Windows, UNIX, or a mixed platform environment.
Upfront 7.0
Upfront 7.1
Mixed Versions Using Separate Computers for Each Version

You can install different versions on separate computers. Shared components can be on the
same computer, or located on one or more additional computers. You can configure drill-through
access between the different versions, but all drill-through targets must be in the same
NewsIndex. This example can use Windows, UNIX, or a mixed platform environment.
PowerPlay client 7.0 on
Windows
Upfront 7.1


drill through
Configuring Mixed Version Environments

When you install mixed versions on the same computer, or when you configure the mixed
version environment as a single application, there are special configuration requirements
although they may be relatively minor, such as changing default port numbers, some
configuration requirements are more complex. For example, to support drill through access from
one version to the other, you must manage server configuration using both Configuration
Manager 7.0 and Configuration Manager 7.1.
If the different versions are installed on separate computers and do not interact, the installation
and configuration process is similar to a single version installation.
For mixed version environments, you may have to perform some or all of the following
configuration tasks:
Specify unique port numbers.
To prevent conflicts when two versions of the same Cognos product are installed on the
same computer, you must specify unique port numbers for each installation.
Configure additional Web aliases.
Most mixed version environments require additional Web server configuration.
Manage configuration files.

In a mixed version environment, you may have to manage separate configuration files for
each version. For example, in a single version environment, you can manage server
configuration using a single .csx file. In a mixed version environment you may have to
manage two server configuration files, one for each version, to ensure that the different
versions interact as expected.
Manage shared components.
You must ensure that shared components are compatible with both versions. For example, if
Cognos security for both versions uses the same namespace, you must use the schema
that is compatible with 7.0 and earlier versions. The 7.1 version schema is not compatible
with 7.0 version Cognos products.
For more information, see the Configuration Manager User Guide.
Part 2: Installing and Testing Cognos Series 7
Chapter 5: Installing by Using Default Settings

A default installation of the Cognos Series 7 solution installs all the Cognos products and
components required to run Cognos Series 7 on a single server. Install by using default settings
both for the selection of components and for the configuration if you want to accept the
installation choices made by Cognos. You can also use the default settings when you want to
accept the choices for components and then make some minor adjustments to the default
configuration. You must still choose a computer and check that all the prerequisites are met,
including installing third-party products.
The installation automatically configures the required settings by using standard defaults. You
do not have to select components when you install or change configuration settings after the
installation. Only Cognos Series 7 Alerts/Notifications requires some configuration with a default
installation because specific settings depend on your choice of third-party database and cannot
be set automatically.
You can also follow the default installation instructions for installing, and then make some minor
changes to configuration settings to better suit your installation environment. The most common
changes are made to the directory server settings as you install the Cognos components. For
instructions, see "Install Cognos Components" (p. 66).
You may prefer to install only the components you want and then complete the required
configurations. For instructions, see "Installing by Distributing Components" (p. 77).
You may have 7.0 components and want to upgrade to 7.1 components. For instructions, see
"Installing to Upgrade" (p. 99).
Use this checklist to guide you through the tasks to complete the default installation process.
Step-by-step instructions follow for each of these tasks:
Verify your system requirements.
Prepare for the installation.
Install a directory server (if required; see the Supplementary Software Installation Guide).
Install ObjectStore (if required).
Install required CDs.
Finish the installation.
After you complete the tasks in this checklist, the default installation will be complete. You can
then start testing the installation. For instructions about how to test an installation, see "Testing
the Installation" (p. 121).
Verifying Your System Requirements

Before you install Cognos Series 7, ensure that the computer meets all of the software and
hardware requirements.
For an up-to-date list of the software environments supported by Cognos products, see the
Cognos support site (http://support.cognos.com). The support site includes information about
operating systems, system requirements, patches, browsers, Web servers, directory servers,
database servers, OLAP servers, and more.
Note: Ensure that you have verified your system requirements. For example, for Cognos
NoticeCast, you must have a database instance and the appropriate JDBC driver. JSQLConnect
is provided by default with Cognos Series 7 Alerts/Notifications for use with Microsoft SQL
Server. You must also have a Web server installed and started, and access to a mail server.
We recommend that you install and run all Cognos services as a distinct user, such as
"Cognos".
Verify Administrator Privileges

Before you install, you must verify that you have administrator privileges for the Windows
computer you are installing on. If, after completing the following steps, you verified that you are
not an administrator, ask your system administrator to add you to the Administrator group on
your computer.
Steps in Windows NT
1. From the Start menu, click Programs, Administrative Tools, User Manager.
The User Manager window appears.
2. In the bottom pane, under Groups, double-click the Administrators group.
If you have administrator privileges, the Local Group Properties window appears and you
will see your user ID listed in the Members box.
If you do not have administrator privileges, you cannot open the group and will receive an
access denied message.
Steps in Windows 2000

1. In the Control Panel, double-click the Users & Passwords icon.
If you have administrator privileges, the Users & Passwords window appears.
2. Click the Users tab if you wish to view your user ID in the user list.
If you do not have administrator privileges, you cannot open Users & Passwords and will
receive a message telling you that you are not a member of the Administrator group.
Steps in Windows XP
1. In the Control Panel, click User Accounts.
If you have administrator privileges, the User Accounts window appears.
2. Click the Users tab to view your user ID in the users list.
If you do not have administrator privileges, you cannot open User Accounts and will
Create a TEMP System Variable

Before you install, ensure that your computer has a TEMP system variable that points to the
folder where you want to store temporary files. During the installation, files from the CD are
temporarily copied into this folder.
Steps in Windows NT
1. Right-click My Computer, and then click Properties.
The System Properties dialog box appears.
2. Click the Environment tab.
3. Scroll through the System Variables box and look for a TEMP variable.
Ensure that you are looking in System Variables and not User Variables. If there is no
TEMP variable (in upper or lowercase), you must create one.
4. Click any variable inside the System Variables box.
This ensures that you will add a system variable, not a user variable.
5. Near the bottom of the window, in the Variable box, type TEMP
This does not alter the variable that you previously selected.
6. In the Value box, type the location of the folder where you want to store temporary files.
You should specify a folder on a drive that has a large amount of free space and is not
heavily used. For example, F:\Temp.
7. Click Set and OK.

1. In the Control Panel, double-click the System icon.
2. Click the Advanced tab, and then click Environment Variables.
4. Under System variables, click New.
The New System Variable dialog box appears.
5. In the Variable Name box, type TEMP
6. In the Variable Value box, type the location of the folder where you want to store temporary
files.
7. Click OK.
8. In the Environment Variables dialog box, click OK.
9. In the System Properties dialog box, click OK.
Steps in Windows XP
1. In the Control Panel, click Performance and Maintenance.
2. Click System.
5. Under System Variables, click New.
files. For example F:\Temp.
8. Click OK.
Set Database Environment Variables

If your application uses a relational database or OLAP data source, you must set the database
environment variables for the user before you start the Cognos processes. The following table
provides example values. Contact your database or network administrator for the correct values
for your system.
Database
Environment variable Description
Oracle 9.2
client
NLS_LANG
The NLS_LANG
environment variable
uses the following
format:
NLS_LANG format =
<language>_<territory
>.<character set>
You must ensure that Oracle's

NLS_LANG environment
variable and the locale
properties specified in
Configuration Manager are
compatible. Failure to do so can
cause unexpected results.
After you complete the
installation, ensure that you use
compatible Configuration
Manager Locale property
settings. For example, if the
environment variable is set to
NLS_LANG
French_France.WE8ISO8859P
1
On Windows, compatible
Configuration Manager Locale
property settings would be
Locale fr-fr
Native Locale fra_fra.28591
Encoding iso-8859-1
For information about
compatible UNIX settings, see
the Cognos Series 7 Solutions
for UNIX Installation Guide.
For additional information, see
your Oracle documentation,
and Locale properties in the
Configuration Manager User
Guide.
Create a Database and Database User for Cognos NoticeCast

This task applies only if you are installing Cognos Series 7 Alerts/Notifications. If you are not
installing this product, you do not need to complete this task. Proceed to the next section.
This task must be completed by your database administrator.
For MS SQL Server, IBM DB2, and Informix, you must first create a database to store the
NoticeCast data store. For Oracle, ensure that NoticeCast will be able to create tables in your
database instance.
For all types of databases, create one database user who has unrestricted access to the data
store. This level of access is required while the tables are being created by the installation
program. After the installation and configuration is complete, the access privileges of this
database user can be modified to standard read and write privileges. All communication
between the Cognos NoticeCast server and the data store is conducted with one database user
ID and password.

If using Microsoft SQL Server, you must ensure that the security properties are set to SQL
Server and Windows NT authentication (SQL/WIN NT) for the database that holds the Cognos
NoticeCast data store. Use these settings on all Windows operating systems. Because Cognos
NoticeCast uses JDBC to connect to the data store, the default Microsoft Windows NT
authentication is not sufficient and may result in an Unable to connect message when logging
on to the data store. For more information, see the Microsoft Web site.
Installing a Directory Server

Installing Sun ONE Directory Server (formerly called Netscape or iPlanet Directory Server)
applies to all Cognos Series 7 products. You can install Sun ONE Directory Server on Windows
or UNIX. For information about installing on either platform, see the Cognos Series 7
Supplementary Software Installation Guide.
If you are using Windows 2000 Active Directory instead of Sun ONE Directory Server, see
"Additional Products and Services" (p. 203)
If you already have a directory server installed, you do not have to install Sun ONE Directory
Server. Instead, you can configure the Cognos Series 7 products to use the existing directory
server. For more information, see "Install Cognos Components" (p. 66).
Install ObjectStore
ObjectStore is the database used by the Impromptu Web Reports data store and by Architect,
the metadata management tool for business models. Architect is used by Cognos Query,
Impromptu Administrator, and PowerPlay Transformer.
Because you can have only one Impromptu Web Reports data store to serve all your Impromptu
Web Reports servers, you should install ObjectStore on a computer that has a backup system in
place.
Install ObjectStore
on every computer where you will install Architect (in Cognos Query, Impromptu
Administrator, and PowerPlay Transformer)
on the computer that holds the Impromptu Web Reports data store
on any computer on which you install the Impromptu Web Reports Server
Steps
1. Open the installation menu from your Cognos CD:
If you insert the CD, the installation menu should appear. Click Install ObjectStore.
If no installation menu appears, navigate to the Support Files\eXcelon\ObjectStore

folder on the CD, and double-click Setup.exe.
If you are installing from your network, double-click Setup.exe in the folder where your
administrator copied the third-party support files.
2. In the Welcome dialog box of the Installation Wizard, click Next and wait for the file transfer
to complete and the ObjectStore Setup window to appear.
3. Verify your Destination Folder location.
Note: In the ObjectStore Setup window, the default destination is always shown as c:\ODI
even though c: may not be the partition you want to install on.
4. Click Browse to specify a destination drive and folder, or accept the default destination
folder c:\ODI.
5. Click Next to accept the Destination Folder location, and continue the installation.
6. If prompted, reboot your computer to complete this installation.
Installing Cognos Series 7

You install Cognos products from the CDs provided with Cognos Series 7.
Notes
You can install Cognos Series 7 products in any order.

The installation is complete only after you have also applied the configuration settings and
started the services. You must be aware of dependencies such as shared data stores when
starting services.
The product-specific administration CDs are for the convenience of customers who want to
install all the administration tools on a separate computer. For the purpose of the default
installation described in this document, this CD is not required because the administration
tools are automatically installed on the same computer as the server products in Cognos
Series 7.
Stop Services
If you have other Cognos products installed, you must stop all Cognos services before you
install or uninstall another Cognos component.
Steps
2. On the Welcome page, click the Start tab.
4. At the top of the Explorer window, click your computer name.
5. From the Actions menu, click Stop Service.
All Cognos services running on your computer are stopped.
Install Cognos Components

You can complete a default installation of multiple Cognos products in two ways:
We recommend that you complete a default installation of multiple Cognos products by
repeating the following steps, selecting the option to Exit the Installation Wizard Without
Configuring Components, and then installing from the next CD. After you have completed
installing from the last CD, you can apply all the default settings for all products at once and
start the services (p. 95). With this option, you first copy all files for all products, and then
apply the default configuration and start services for all products at once.
Alternatively, you can repeat the following steps, once for each CD, and select the option to
Configure Components with Defaults, then stop services before installing the next CD.
With this option, you copy all files, components are configured with default settings, and
services are started, for one product at a time.
Steps
1. Review all prerequisites such as verifying the system requirements and completing the
preparation tasks, including installing a directory server and ObjectStore.
2. Decide which CDs you need.
3. Open the installation menu from the Cognos CD:
If you insert the CD, the installation menu should appear. Click the link to install the
specific product.
If no installation menu appears, double-click Setup.exe in the cognos\product_name

folder on the CD.
administrator copied the installation files.
4. In the Welcome dialog box of the Installation Wizard, read the message and click Next.

5. In the License Agreement dialog box, read the agreement, click I accept, and then click
Next.
6. Type your User Information and click Next.
7. In the Installation Type dialog box, click Default, and then click Next.
8. In the Character Set Selection dialog box, select the set of locales that you require and
click Next.
9. If the Language Selection dialog box appears, select the language you want to use and
click Next.
10. In the Installation Location dialog box, click Next to accept or change the default locations
for components, and then click Next.
11. If prompted to create new folders, click Yes.
12. In the Shortcut Folder dialog box, click Next to accept, or change the default Program
Folder under which all your Cognos Series 7 products are installed, and then click Next.
The Installation Summary appears and lists all the components that will be installed with
the default installation.
13. Click Next.
This starts the file transfer whereby files are copied from the CD to the install location.
14. In the Component Configuration dialog box, select one of following options, and click
Next:
Configure components with defaults - this option starts the Configuration Wizard so
that you can change certain properties if you are using an existing directory server or if
you want to make minor configuration changes to a new directory server. The
Configuration Wizard will apply your changes along with the other default settings and
start the services.
Exit the Installation Wizard Without Configuring Components - this option lets you
exit the installation without configuring any components at this time. When you have
finished installing components, you can start Configuration Manager later and then
configure the components, apply the configuration, and start the services. We
recommend you use this option when installing multiple products.
For more information about configuring your components, see the Configuration Manager
User Guide.
15. If you chose to configure components with defaults, do the following:
In the Welcome dialog box of the Configuration Wizard, click Next.
In the Authentication Source dialog box, select Directory Server and click Next.
In the Directory Server Authentication dialog box, type the information for following
properties:
Computer name where the directory server is installed
Port that is connected to the directory server
Base Distinguished Name (DN) which will be the first entry in the directory tree
creating a branch for your data
Default Namespace Name for the directory server
Click Next.
In the Directory Server Configuration dialog box, click No if you are using an existing
directory server, or click Yes if you want to change settings for a new directory server. If
you click Yes, type the values for the properties you want to change.
Click Next.
In the Server Topology dialog box, select to use the default configuration, or specify a
server configuration file that you want to import, and then click Next.
16. In the Finish dialog box, click Finish.

This starts the configuration, and activation of installed components.
17. Click OK to confirm the successful completion of the configuration.
18. Click Yes if prompted to restart your computer.

19. Click Finish to close the Installation Wizard.
20. Close the CD installation menu.
Note: For Cognos NoticeCast Server, you will be prompted with the option to Open
Configuration Manager to Customize Component Configurations. Cognos NoticeCast
Server cannot be automatically configured because the software cannot detect the type of
database you are using for your NoticeCast data store. After clicking Finish, you must continue
with the NoticeCast Configuration. For instructions, see "Complete the Configuration for Cognos
Series 7 Alerts/Notifications" (p. 71)
Finishing the Installation

To finish the installation, continue with the following tasks. Some of these tasks are optional if
indicated, but most of them must be completed before you test your installation:
Configure your Web Server is mandatory for Cognos Series 7 Query, Reporting, Impromptu
Administrator or Impromptu User (if you installed PowerPrompts), Visualization, OLAP and
Complete the configuration of Cognos NoticeCast is mandatory for Cognos Series 7
Configure Your Web Server

You installed a Web server as a system requirement. You must now configure your Web server
to work in your Cognos environment. To do this, you must set up virtual directories, also known
as Web aliases, for the directories that contain the HTML and Web files for your Cognos
product. You must also set default.htm as the default document for the Web server.
Alias
Location
Permission
cognos
Read
Execute
cognos/help
Read
Note: If your Cognos Series 7 installation includes Cognos Visualizer, and you are using an
iPlanet Web server, you must create two additional aliases and complete additional Web server
configuration. For more information, see "Steps to Configure iPlanet 6 for Cognos
Visualizer" (p. 71).
The following procedures are for creating new Web aliases. See the Configuration Manager
User Guide if you are changing Web aliases for an existing installation. Also, see Configuration
Manager User Guide if you are using alternate gateways, such as NSAPI or ISAPI, instead of
the default CGI programs with your Web products.
Steps for Personal Web Server 4 (Windows NT 4.0) or Personal Web Server 5
(Windows 2000)
1. Start the Personal Web Manager.
For Windows NT, click Start, Programs, Windows NT 4.0 Option Pack, Microsoft
Personal Web Server, Personal Web Manager.
For Windows 2000, click Start, Settings, Control Panel. Double-click Administrative
Tools, and double-click Personal Web Manager.
2. In the Main window, note the URL of your home page; for example, http://computer name.

3. In the left pane, click the Advanced icon.
The Advanced Options dialog box appears.
4. Click Add to create the first of three virtual directories.
5. In the Add Directory dialog box, click Browse and select the
installation_location\webcontent folder, and click OK.
6. In the Alias box, type cognos
7. Under Access, select the Read check box, clear the other check boxes, and then click OK.
You have completed configuration of one virtual directory.
8. In the Virtual Directories box, select the cognos virtual directory you just created, and
click Add.
installation_location\cgi-bin folder, and then click OK.
10. In the Alias box, type cgi-bin
11. To define the access level for the cgi-bin virtual directory:
For Windows NT, under Access, select the Execute check box, clear the other check
boxes, and then click OK.
For Windows 2000, under Application Permissions, click Execute (including

scripts), and then click OK.
12. In the Virtual Directories box, select the cognos virtual directory and click Add.
installation_location\Documentation folder, and then click OK.
14. In the Alias box, type help
16. To set up your default document:
In the Advanced Options dialog box, select the Enable Default Document check box.
In the Default Document box, type default.htm
17. Close Personal Web Manager.
Steps for IIS 4 (Windows NT 4.0) or IIS 5 (Windows 2000)

1. Start the IIS 4.x Internet Service Manager.
Internet Information Server, Internet Service Manager.
Tools, and double-click Internet Services Manager.
2. In the left pane of Microsoft Management Console, expand Internet Information Server,
and then expand the folder that has the name of your computer.
3. Right-click the folder that has the name of the Web site on which you will run your Cognos
product.
If you have only one Web site, its default name is Default Web Site.
4. Click New, Virtual Directory to create the first of three virtual directories.
5. In the Alias to be Used to Access Virtual Directory box, type cognos and click Next.
6. Click Browse and select the installation_location\webcontent folder.
7. Click OK, and click Next.
8. Select Allow Read Access, clear the other check boxes, and then click Finish.
9. In the left pane of Microsoft Management Console, right-click the folder called cognos
and click New, Virtual Directory.
10. In the Alias to be Used to Access Virtual Directory box, type cgi-bin, and click Next.
11. Click Browse and select the installation_location\cgi-bin folder.

For Windows NT, select the Allow Execute Access check box and clear the other
check boxes.
For Windows 2000, under Application Settings, in the Execute Permissions box,
select Scripts & Execute.
14. Click Finish.

16. In the Alias to be Used to Access Virtual Directory box, type help and click Next.
17. Click Browse and select the installation_location\Documentation folder.
Right-click the folder that has the name of the Web site on which you will run your
cognos product (for example, Default Web Site).
Click Properties.
Click the Documents tab.
Select the Enable Default Document check box, and click Add.
In the Default Document Name box, type default.htm and click OK twice.
21. Close Microsoft Management Console.

22. Click Yes to save your settings if prompted.
Steps for iPlanet 6

1. Open a Web browser and type the URL of the iPlanet Enterprise Administration Server.
The default URL format is http://web server name.domain:default administration server port.
For example, http://yourcomputer.yourcompany.com:8888.
2. On the Servers tab, in the Select a Server box, click your Web server and then click
Manage.
3. Click the Class Manager link located at the top right corner.
4. Click the Content Mgmt tab, and then click Additional Document Directories.
5. In the URL prefix box, type cognos
6. In the Map To Directory box, type the full path for the webcontent folder.
For example, installation_location\Cognos\cer3\webcontent.
7. Click OK and then click OK again.
8. In the URL prefix box, type cognos/help
9. In the Map To Directory box, type the full path for the documentation folder.
For example, installation_location\Cognos\cer3\Documentation.
10. Click OK then click OK again.
11. Click the Apply link located in the top right corner to apply your changes.
12. Choose whether to restart the Web server.
13. Click the Programs tab.
14. In the URL prefix box, type cognos/cgi-bin
15. In the CGI directory box, type the full path for the cgi-bin folder.
For example, installation_location\cognos\cer3\cgi-bin.

Click the Content Mgmt tab, and click Document Preferences.
In the Index Filenames box, add default.htm to the list.

Note: Filenames are separated by a comma.
Click OK and then click OK again.
Click the Apply link located in the top right corner to apply your changes.
20. Close the Web browser.

21. If your Cognos Series 7 installation includes Cognos Visualizer, complete the following
iPlanet configuration.
Steps to Configure iPlanet 6 for Cognos Visualizer

1. Complete "Steps for iPlanet 6" (p. 70).
2. Add the following information to the end of the iPlanet obj.conf file located in
iPlanet_installation_location\https-web server name.domain.
<Object name="Download">
ObjectType fn="type-by-exp" exp="*/" type="magnus-internal/directory"
ObjectType fn="force-type" type="application/octet-stream"
</Object>
Note: Do not edit the obj.conf file located in iPlanet_installation_location\https-admserv
3. Open a Web browser and type the URL of the iPlanet Administration Server.
Manage.
5. Stop and then restart the Web server to apply the changes to the obj.conf file.
8. In the URL prefix box, type cognos\plugin
9. In the Map To Directory box, type the full path for the plugin folder.
For example, installation_location\Cognos\cer3\webcontent\plugin.
10. In the Apply Style box, select Download.
12. In the URL prefix box, type cognos/download
13. In the Map To Directory box, type the full path for the download folder.
For example, installation_location\Cognos\cer3\webcontent\viz\download.
Complete the Configuration for Cognos Series 7 Alerts/Notifications

You must complete the configuration of Cognos NoticeCast for your specific environment.
The installation does not complete the configuration of Cognos NoticeCast because it cannot
automatically determine some information, such as which type of database (Oracle, DB2,
Informix, or Microsoft SQL Server) you are using for the NoticeCast data store, or which mail
server you are using.

Use Configuration Manager on the appropriate computer to complete the following
configuration. For more information about using Configuration Manager, see the Configuration
Manager User Guide.
Note: If you installed Cognos NoticeCast for Windows and Cognos NoticeCast Authoring on the
same computer, complete the following procedure to configure NoticeCast. You do not need to
complete the steps in the two subsequent sections, Configure NoticeCast Authoring and
Configure NoticeCast Administration.
Configure NoticeCast Server

Before you can start the NoticeCast server, you must
provide information about the mail server used to deliver notifications
provide information about the third-party database used for the NoticeCast data store
create the NoticeCast data store
Steps to Configure NoticeCast Server

You may need to ask your mail server administrator for the information required in the following
steps.
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. On the Start tab, Click Open the Current Configuration.
Configuration Manager opens.
3. In the Explorer window, expand Cognos NoticeCast.
4. Expand the NoticeCast Server component.
5. Click the Mail Server category.
6. Change the SMTP Server Name property to identify the mail server you can connect to.
7. If your mail server requires logon information, change the SMTP Login Name and SMTP
Login Password properties.
8. In the Email Address of Sender property, replace noticecast@mycompany.com with an
email address that Cognos NoticeCast messages will appear to have been sent by.
Note: We recommend that your mail server administrator create an email account that is
used only for Cognos NoticeCast messages.
9. To allow recipients to reply to a notification, or to unsubscribe from a notification list, specify
the POP3 server properties.
Steps to Configure NoticeCast Data Store

1. If you are using Oracle, DB2, or Informix for your NoticeCast data store, copy the JDBC
driver files for your database into the installation_location\bin folder.
Note: If you are using a Microsoft SQL Server database, the JSQLConnect.jar file is
installed to the appropriate location by default.
2. Expand the NoticeCast Data Store component.
The General category and four data store categories exist, one for each type of supported
database.
3. Click the General category.
The General - Properties window shows the properties that are currently configured for this
category.
4. For the Data Store Connection File property, click in the Value box, and select the
appropriate connection file for the NoticeCast data store. For example, for an Oracle
database, select ora_connection.conf
5. In the Explorer window, click the category appropriate for your type of database. For
example, if using Oracle for the NoticeCast data store, click Oracle Data Store
Configuration.

6. For the Database URL property, change the server name specification in the URL to specify
the name of the server where your NoticeCast data store resides. The default port and
database sid are also part of the URL, but only need to be changed if you are not using
default values. Depending on the database you are using, do one of the following:
In the Oracle Data Store Configuration, Database URL property, replace

OracleServer with the name of the database server. For example,
jdbc:oracle:thin:@OracleServer:1521:ORCL
In the Microsoft SQL Server Data Store Configuration, Database URL property,
replace dbServerName with the name of the database server, and replace
NCDataStoreName with the name of the database. For example,
jdbc:JSQLConnect://ServerName/NCDataStoreName
In DB2 Data Store Configuration, Database URL property, replace DB2ServerName

with the name of the database server, and replace dbName with the name of the
database. For example,
jdbc:DB2://DB2ServerName:port/NCDataStoreName
In Informix Data Store Configuration, Database URL property, replace ServerName

with the name of the database server, replace dbName with the name of the database,
and replace InformixServerName with the name of the Informix Server instance. For
example,
jdbc:informix-sqli://ServerName:1906/dbName:informixserver=InformixServerName
7. For the Data Store Logon ID property, type the user ID for the NoticeCast user.
8. For the Data Store Logon Password property, type the password for the NoticeCast user.
Confirm the password when prompted.
9. Change the value of the JDBC Driver File property to point to the location and file name of
the driver files you are using:
If you are using JSQLConnect.jar with your Microsoft SQL Server database, the MS
SQL JDBC Driver File property already specifies the default location of the JDBC
driver file.
If you are using Oracles default JDBC driver, ensure that the Oracle JDBC Driver File
property points to
installation_location/bin/classes12.zip
If you are using DB2s default JDBC driver, ensure that the DB2 JDBC Driver File
property points to
installation_location/bin/db2java.zip
If you are using Informixs default JDBC driver, ensure that the Informix JDBC Driver
File property points to
installation_location/bin/ifxjdbc.jar
Steps to Create NoticeCast Data Store

1. In the Explorer window, expand the NoticeCast Data Store component, and click the
category named General.
2. In the Properties window, click the Value box next to the Data Store Administration
property, and select Install.
3. In the Explorer window, select the NoticeCast Server component.
4. On the Actions menu, click Apply Selection, and then confirm the action.
Note: Ensure that Access Manager is configured and related services, including services
for the directory server are running before applying the changes.
This action creates the NoticeCast data store and configures your computer with the NoticeCast
server settings. If error messages result, verify that you first created a database user and
assigned unlimited privileges.
Steps to Start Cognos NoticeCast Services

1. In the Explorer window, click the Cognos NoticeCast component.
2. On the Actions menu, click Start Service.
A message appears to confirm that services are started on your computer.

3. Close Configuration Manager.
You are prompted to save your configuration changes in a file. This is optional. For more
information about the benefits of saving to a configuration specification file (.ccs), see the
Configuration Manager User Guide.
Configure NoticeCast Authoring

To configure the NoticeCast authoring component, you specify the location of the NoticeCast
server.
Note: If you installed the NoticeCast authoring component and the NoticeCast server on the
same computer, and you completed the steps required to configure the NoticeCast server, you
do not have to complete the following steps.
Steps
Manager.
2. On the Start tab, click Open the Current Configuration.
3. In the Explorer window, expand Cognos NoticeCast, and then expand the NoticeCast
Client component.
4. Select the NoticeCast Client category.
The Properties window shows the properties that are currently configured for this category.
5. In the NoticeCast Server Name property, verify that the Value box shows the name of the
computer running the NoticeCast server.
6. In the Explorer window, select the NoticeCast Client component.
7. From the Actions menu, click Apply Selection, and then confirm the action.
This action configures your computer with the new settings.
Configure NoticeCast Administration

Note: The following steps are required only if you installed the NoticeCast administration tools
and the NoticeCast server on separate computers. When these components are on separate
computers, the data store configuration information on both computers must match. Record the
data store configuration information from the NoticeCast server computer and use this
information to configure the NoticeCast administration computer.
Steps
driver files for your database into the installation_location/bin folder.
Manager.
4. In the Explorer window, expand Cognos NoticeCast
database.
category.

8. In the Explorer window, click the category appropriate for your type of database, for
example if using Oracle for the NoticeCast data store, click Oracle Data Store
Configuration.


with the name of the database server, and replace NCDataStoreName with the name
of the database. For example,

example,
driver file.
property points to
property points to
13. In the Explorer window, expand Administration, and then expand the NoticeCast
Administration component.
14. Select the NoticeCast Administration category.
15. For the NoticeCast Server Name property, verify that the Value box shows the name of the
16. In the Explorer window, select the NoticeCast Administration component.
Whats Next?
The default installation is now complete. Before you start using Cognos Series 7, you should
test all the components to ensure that they work and that they can communicate with each
other. For testing instructions, see "Testing the Installation" (p. 121).
Chapter 6: Installing by Distributing

Components
This chapter contains information you should use only for doing customized or distributed
installations.
You may prefer to do a default installation of all components, with components configured to use
standard default settings. For instructions, see "Installing by Using Default Settings" (p. 61).
You may have an older version of Cognos Series 7 and want to upgrade your software and data
to Cognos Series 7 Version 2. For instructions, see "Installing to Upgrade" (p. 99).
It is very important that you plan your custom or distributed installation. We recommend that you
create an installation schematic and write down all the custom configuration settings you plan to
use before you actually start installing any software. For assistance, use the checklist that is
provided in this guide (p. 211). We also recommend that you read the Planning Advanced
Installations Guide.
The first phase of a custom installation involves preparing your work environment and copying
the required software components onto one or more computers. The process of doing a custom
installation is almost the same as doing a default installation. You must do the same preparatory
and installation tasks, such as
Install a directory server (if required; see the Supplementary Software Installation Guide).
Install ObjectStore (if required).
Copy the Cognos components.
During a custom installation, you can specify which components you want to install and choose
where you want to install them. The second phase of the installation, therefore, involves
configuring the required settings for each component. If you distribute server components
across multiple computers, you must specify the location of the server and gateway components
and manage the server configuration file (.csx) on each computer. This file contains all the
server configuration information so that gateway components can communicate with their
associated servers. For more information about configuring distributed server environments,
see the Configuration Manager User Guide.

hardware requirements.
Preparing for the Installation

Before you start any installation, we recommend that you close all programs that are currently
running. This will help to ensure that the installation program can copy all the required files onto
your computer.
Chapter 6: Installing by Distributing Components

Note: Ensure that you have verified your system requirements; for example, a Web server is
installed and started.
"Cognos".

Before you install, you must verify that you have administrator privileges for the Windows
computer you are installing on. If, after completing the following steps, you verified that you are
your computer.
Steps in Windows NT

Steps in Windows XP

Before you install, ensure that your computer has a TEMP system variable that points to the
folder where you want to store temporary files. During the installation, files from the CD are
temporarily copied into this folder.
Steps in Windows NT


files.
7. Click OK.
Steps in Windows XP
2. Click System.
8. Click OK.
Create the Database User for Cognos NoticeCast

If you are not installing Cognos Series 7 Alerts/Notifications, you do not need to complete this
task. Proceed to the next section.
database instance.

ID and password.
Installing a Directory Server

Installing Sun ONE Directory Server (formerly called Netscape or iPlanet Directory Server)
applies to all Cognos Series 7 products. You can install Sun ONE Directory Server on Windows
or UNIX. For information about installing on either platform, see the Cognos Series 7
When you have finished installing the directory server and creating the data directory, return to
this guide and configure the directory server. This task is part of Configuring Cognos Series 7
(p. 83).
If you are using Windows 2000 Active Directory instead of Sun ONE Directory Server, see
"Additional Products and Services" (p. 203).
If you already have a directory server installed, you do not have to install or configure a directory
server. Instead, you must specify the existing directory server as your authentication source for
every computer that connects to the directory server. For more information, see "Specify the
Authentication Source" (p. 97).
Install ObjectStore
Because you can have only one Impromptu Web Reports data store to serve all your Impromptu
Web Reports servers, you should install ObjectStore on a computer that has a backup system in
place.
Install ObjectStore
on every computer where you install Architect (in Cognos Query, Impromptu Administrator,
and PowerPlay Transformer)
on the computer that holds the Impromptu Web Reports data store
on any computer on which you install the Impromptu Web Reports Server
You must install Architect and ObjectStore on computers that belong to the same domain.
Otherwise, you will not be able to create and authenticate Architect models. In addition, if you
want to use an Architect model (.cem) that is stored on a shared network drive, you must install
ObjectStore both on the computer that owns the network drive and on the client computer that
accesses the drive. This client computer is the one that is used to run Architect.
Steps


folder c:\ODI.
Installing Cognos Series 7 Components

You copy the software components from the Cognos CDs onto one or more computers. If you
plan to copy components onto more than one computer, you should first familiarize yourself with
your distributed installation options. Some components must be installed on the same computer.
For more information, see the Planning Advanced Installations Guide.
Notes
You can install Cognos Series 7 components in any order.

After you complete the following steps to copy components, you must continue with the
instructions for configuring Cognos Series 7 (p. 83).
The installation is complete only after you have also applied the configuration settings
(p. 95) and started the services (p. 95). You must be aware of dependencies such as shared
data stores when starting services.
You must select the same locale and character set for server and client components when
installing components on separate computers. You may notice inconsistencies if the settings
for locale and character set are not the same for server and client components.
Stop Services
Steps
Copy the Components

Repeat the following steps for each component that you copy. We recommend that you select
the option to Exit the Installation Wizard Without Configuring Components and then copy
components from the next CD before configuring components. After you have copied all the
components, you must then complete the configuration (p. 83). You may be required to stop a
Cognos service before you can copy another Cognos component.
If you are installing Cognos NoticeCast server, select Exit the Installation Wizard Without
Configuring Components and then follow additional instructions (p. 91) to configure the
NoticeCast server.
Steps
specific product.
If no installation menu appears, double-click Setup.exe from the root of the CD.
Next.
7. In the Installation Type dialog box, click Custom, and then click Next.
8. In the Component Selection dialog box, select the components that you want to install,
and click Next.
9. In the Character Set Selection dialog box, select the set of locales that you want to use
and click Next.
10. If the Language Selection dialog box appears, select the languages you want to use and
click Next.
13. In the Shortcut Folder dialog box, click Next to accept or change the default Program
The Installation Summary appears and lists all the components that will be installed with
the custom installation.
14. If you are satisfied with your selection, click Next, or click Back to make corrections, and
then click Next.
This starts the file transfer of the selected components.

15. In the Component Configuration dialog box, select the appropriate option, and click Next.
Your choices are
Configure Components with Defaults - this option starts the Configuration Wizard.
You may want to use the Configuration Wizard for the following reasons:
to apply default values to the installed components and start services by simply clicking
Next on all subsequent dialog boxes.
to make some minor changes related only to the directory server component. The
Configuration Wizard will apply your changes along with the other default settings and
start the services.
to specify that you want to use a local authentication export (.lae) file instead of a
directory server when you implement a single server installation.
for a distributed environment, to create a server configuration file (.csx) or to easily

import a .csx file, which was created on another computer in your distributed
environment.
Open the Configuration Manager to Customize Component Configurations - this

option automatically opens the Configuration Manager after the transfer process. You
can then immediately configure any of the components, apply the configuration, and
start the services.
Exit the Installation Wizard Without Configuring Components - this option allows
you to exit the installation without configuring any components at this time. You can start
Configuration Manager later and then configure the components, apply the
configuration, and start the services. This is useful when installing multiple products.
For more information about configuring your components, see the Configuration Manager
User Guide.
Configuring Cognos Series 7

The next phase of the custom installation process involves configuring all the components,
including third-party software. You must complete this phase before Cognos Series 7 will work.
Notes
Configuring a Web server is applicable only if you are installing Cognos Series 7 Query,
Cognos Series 7 Reporting, Cognos Series 7 Impromptu Administrator (if using
PowerPrompts), Cognos Series 7 Visualization, Cognos Series 7 OLAP and Cognos Series
7 Alerts/Notifications.
In addition to the following list, if you are installing Cognos Series 7 Alerts/Notifications, you
must also configure the Cognos NoticeCast components (p. 91).
You must configure

the Web server. You only do this task once for all your Cognos Series 7 products.
the directory server. You only do this task once for all your Cognos Series 7 products.
the authentication source. You must do this task on every computer on which you installed
Cognos components.
any component settings that you want to change to better suit your specific environment.
This task includes applying the settings to the components on the computer.
the locations of each server component. This task includes updating the server
configuration file so that all the components can communicate with one another. You only
need to do this task if you distributed your server components across more than one
computer.
Note: Even if you accepted the default configuration when you were copying the components
and do not want to change any settings, you must still apply the settings to the components on
the computer.
After you have everything configured, and have applied the settings, you must start all the
services and processes.
You may need to perform some of these tasks in an iterative fashion, depending on how you set
up your custom or distributed installation.
Using the Configuration Manager

To configure Cognos components, you use Configuration Manager. Configuration Manager has
two interfaces, a graphical user interface and a command line interface. You can use either
interface to configure Cognos components on Windows. You can use only the command line
interface on UNIX. In the graphical user interface, the object hierarchy is shown as a folder
structure in the Explorer window. In the command line interface, you navigate through the
object hierarchy by using the select and list commands, and by specifying a sequence of
objects that are delimited by the dot (.) operator.
There are several ways to configure Cognos components. You can directly modify and apply
configurations to one or more components, or you can create and run scripts.
For more information about using Configuration Manager, see the Configuration Manager User
Guide.
Configure the Web Server

You installed a Web server as a system requirement. You must now configure your Web server
to work in your Cognos environment. To do this, you must set up virtual directories, also known
as Web aliases, for the directories that contain the HTML and Web files for your Cognos
product. You must also set default.htm as the default document for the Web server.
Alias
Location
Permission
cognos
Read
Execute
cognos/help
Read
Note: If your Cognos Series 7 installation includes Cognos Visualizer, and you are using an
iPlanet Web server, you must create two additional aliases and complete additional Web server
configuration. For more information, see "Steps to Configure iPlanet 6 for Cognos
Visualizer" (p. 87).
User Guide if you are changing Web aliases for an existing installation. Also, see Configuration
Manager User Guide if you are using alternate gateways, such as NSAPI or ISAPI, instead of
the default CGI programs with your Web products.
(Windows 2000)
6. In the Alias box, type cognos
click Add.
10. In the Alias box, type cgi-bin

14. In the Alias box, type help

Tools, and double-click Internet Services Manager.
2. In the left pane of Microsoft Management Console, expand Internet Information Server,
and then expand the folder that has the name of your computer.
product.
4. Click New, Virtual Directory to create the first of three virtual directories.
5. In the Alias to be Used to Access Virtual Directory box, type cognos and click Next.
6. Click Browse and select the installation_location\webcontent folder.

10. In the Alias to be Used to Access Virtual Directory box, type cgi-bin, and click Next.
11. Click Browse and select the installation_location\cgi-bin folder.
check boxes.
14. Click Finish.

16. In the Alias to be Used to Access Virtual Directory box, type help and click Next.
17. Click Browse and select the installation_location\Documentation folder.
Click Properties.
21. Close Microsoft Management Console.

Steps for iPlanet 6

Manage.
5. In the URL prefix box, type cognos
For example, installation_location\Cognos\cer3\webcontent.
8. In the URL prefix box, type cognos/help
For example, installation_location\Cognos\cer3\Documentation.

14. In the URL prefix box, type cognos/cgi-bin
15. In the CGI directory box, type the full path for the cgi-bin folder.
For example, installation_location\cognos\cer3\cgi-bin.


21. If your Cognos Series 7 installation includes Cognos Visualizer, complete the following
iPlanet configuration.
Steps to Configure iPlanet 6 for Cognos Visualizer

1. Complete "Steps for iPlanet 6" (p. 86).
2. Add the following information to the end of the iPlanet obj.conf file located in
iPlanet_installation_location\https-web server name.domain.
<Object name="Download">
ObjectType fn="type-by-exp" exp="*/" type="magnus-internal/directory"
ObjectType fn="force-type" type="application/octet-stream"
</Object>
Note: Do not edit the obj.conf file located in iPlanet_installation_location\https-admserv
3. Open a Web browser and type the URL of the iPlanet Administration Server.
Manage.
5. Stop and then restart the Web server to apply the changes to the obj.conf file.
8. In the URL prefix box, type cognos\plugin
9. In the Map To Directory box, type the full path for the plugin folder.
For example, installation_location\Cognos\cer3\webcontent\plugin.
12. In the URL prefix box, type cognos/download
13. In the Map To Directory box, type the full path for the download folder.
For example, installation_location\Cognos\cer3\webcontent\viz\download.
Configure the Directory Server

When you installed the directory server, you did some initial configuration, such as specifying
the port and base distinguished name. With a custom installation, after all the Cognos products
are copied to the computer, you must complete additional configuration so that the Cognos
products can communicate with the directory server.
Note: If you installed the directory server using the Cognos installer program described in the
Supplementary Software Installation Guide, the directory server is already configured and you
do not have to complete this section. For more information about directory server considerations
for mixed environments of Series 7.0 and Series 7.1 components, see "Mixed Version
Environments" (p. 55).
You only do this task once. It can be done on any computer where you installed Cognos 7.1
components.
You only need to configure one directory server to use with all your Cognos products.
The configuration process is the same regardless of whether you installed Sun ONE Directory
Server or Windows 2000 Active Directory. By completing this additional configuration task, you
are
extending the directory server schema so that the directory server is compliant with Cognos
products
creating a namespace on the directory server in which you can store Cognos security data.
If you already have a namespace that you want to use, you do not need to create one.
enabling communication between the directory server and the ticket server
Note: You can configure a directory server from either a UNIX or WIndows computer, regardless
of whether your directory is installed on a UNIX or Windows computer. If you wish to configure
your directory server from a UNIX computer, see the UNIX installation guide.
The following table shows all the properties that you must verify or configure.
Property
Value
Are you sure you want

to configure this
directory server?
Enables you to change the default

properties of the directory server.
Schema Version
The schema version format used by the

directory server to store Access Manager
information.
The default setting is No
The displayed default is Current

Server Type
The type of directory server that you

installed.
The default setting is Auto Detect, which
will automatically determine the type of
directory server you are using.
Computer
The name of the computer or IP address

where the directory server is installed
Port
The port that is used by the directory server.

The default is port 389
Property
Value
Base Distinguished
Name (DN)
A distinguished name (DN) which will be the

first entry in the directory tree creating a
branch for your data.
The Cognos default DN for Sun ONE
Directory server is o=cognos, c=ca
The Sun ONE default DN for Sun ONE
Directory Server is dc=your organization,
dc=com
The default DN used by Windows 2000
Active Directory is o=company,
dc=computer name
If you used a different base DN when you
installed the directory server, specify the
new base DN.
Unrestricted User
Distinguished Name
(DN)
The distinguished name (DN) that the

administrator uses to manage the contents
of the directory server with unlimited
privileges.
The default used by Sun ONE Directory
Server is cn=Directory Manager
The default used by Active Directory is
cn=Administrator, cn=users,
dc=computer name
Unrestricted User
Password
A password for the unrestricted user.
Primary Ticket Server

where the ticket server is installed and the
port that is connected to the ticket server.
The Cognos default is admin1234
The default is your_computer_name:9010

Secondary Ticket
Server (1, 2, 3, 4)
The computer names and port numbers of

additional ticket servers.
The default is none
To support failover between ticket servers,
specify one or more secondary ticket
servers.
Enable Ticket Server

Load Balance
Enables you to balance the load between

multiple ticket servers.
The default is No
To enable load balancing between ticket
servers, specify at least one secondary
ticket server and select Yes
Default Namespace
Name
The name of the default namespace in the

directory server.
The default name is default
Default Namespace
Administrator Name
Administrator
Property
Value
Default Namespace
Administrator Signon
Administrator
Default Namespace
Administrator
Password
The default is no password.
Complete these steps to configure your directory server. These steps apply to both local and
remote configuration.
Note
To remotely configure Windows 2000 Active Directory, you should use a version of Configuration
Manager that is installed on a Windows 2000 computer. To use a version of Configuration
Manager that is installed on a Windows NT or Windows 98 computer, you must first install the
ADSI patch, found under Support Files on the Supplementary Software CD. For more
information, see the Additional Products and Services appendix.
Steps
These steps apply to both local and remote configuration.
Manager.
2. In the Welcome dialog box, click the Start tab.
3. Click Open the Current Configuration.
The Configuration Manager opens.
4. In the Explorer window, expand the Services component and then expand Access
Manager - Directory Server.
The Properties window shows the property values that the Cognos product expects in Sun
ONE Directory Server. If you used different settings when installing the directory server, you
must change these settings so that they match. If you do not need to change anything, skip
to step 10.
6. Select the Are you sure you want to configure this directory server? property, and
change the value to Yes.
7. Select the Default Namespace Name property, and type the name of the namespace that
you want to create.
8. Change other properties as required.
Ensure that the Computer property contains the correct location of the directory server,
especially if you are configuring a remote directory server.
9. In the Explorer window, select the General category, and from the Actions menu, click
Apply Selection.
Tip: You can create a script to specify the authentication source, which is convenient if you are
installing components on many computers. For more information, see the Configuration
Manager User Guide.
Configuring Component Settings

After you copy the Cognos components to the computer in a custom installation, the Cognos
Installation Wizard asks you whether you want to configure components now or later. If you
select to configure components now, Configuration Manager starts, and you can modify the
required properties. If you select to configure components later, you must complete the
configuration at a later time by starting Configuration Manager. For distributed environments,
you may want to complete the configuration after all components are installed on the different
computers.

Some common configuration tasks that may be required for your environment include:
specifying non-default port numbers
The default port numbers may not be appropriate for mixed version installations or for
installations where there are multiple instances of a Cognos Series 7 Version 2 product on
the same computer.
configuring properties related to Web aliases
If the Web server is on a different computer, or if you configured the Web server using
non-default Web aliases, you must complete additional configuration.
configuring distributed environments
If the current installation is part of a distributed environment, you must complete additional
configuration to ensure all components can interact correctly.
Also see the Configuration Manager User Guide for instructions on how to
manage the server configuration files (cer3.csx) on each computer in a distributed
environment
modify configuration settings for specific components
Configuring Cognos NoticeCast Components

If you are not installing Cognos Series 7 Alerts/Notifications, you do not need to complete the
steps in this section. Proceed to the section called "Apply the Configuration" (p. 95).
Manager User Guide.

create the NoticeCast data store

steps.
Manager.


database.
category.
Configuration.



example,

driver file.
property points to
property points to
Steps to Create NoticeCast Data Store

property, and select Install.
Note: Ensure that Access Manager is configured and related services, including services
for the directory server are running before applying the changes.
This action creates the NoticeCast data store and configures your computer with the NoticeCast
server settings. If error messages result, verify that you first created a database user and
assigned unlimited privileges.


server.
Steps
Manager.
Client component.


and the NoticeCast server on separate computers. When these components are on separate
Steps
Manager.
database.
category.
Configuration.



example,

driver file.
property points to
property points to
Apply the Configuration

Regardless of whether you decide to accept the default settings or modify them, you must apply
all the configuration settings that you plan to use. The following steps assume that you have
made all the required changes to your configuration settings, and you are ready to apply them to
your server environment.
Steps
Complete these steps on every Windows computer that contains a Cognos component.
Manager.
4. In the Explorer window, click the computer.
All the configuration settings are applied to all the components that are installed on the
computer.
Start Services
After everything is installed and configured, you must start all the services that are associated
with Cognos Series 7 products. Cognos services and processes are not registered during a
custom installation until you start them.

For a distributed installation, we recommend that you start the components in the following
order:
Cognos ticket server
directory server
Upfront services
any shared data stores
ObjectStore services (if applicable)
application servers
Note: For Impromptu Web Reports, when you publish a report set using UNC format for the
report set location, an error will appear if the Impromptu Web Reports services are started as a
system account. For all Impromptu Web Reports servers in the server group, set the Cognos
IWR Service Manager service to start as a user account. Then retry your attempt to publish
using UNC. For more information, see the Impromptu Web Reports Administrator Guide.
The following table contains a list of the Cognos services and processes and where you can
locate them in the object hierarchy in Configuration Manager.
Service or Process
Object Hierarchy Location
Cognos IWR Service

Manager
Cognos Impromptu Web

Reports.Server
Cognos PowerPlay
Enterprise Server
Cognos PowerPlay Enterprise

Server.Dispatcher
Cognos Query.Data Store
Cognos Query.Dispatcher
Cognos Query Server

Manager
Cognos Query.Server
Cognos NoticeCast
Dispatcher
Cognos Noticecast.Noticecast Server
Cognos NoticeCast Data

Store
Cognos Noticecast.Noticecast.Data
Store
Cognos Upfront
Administration Service
Upfront.Shared.Server Administration
Cognos Upfront Data Store
Upfront.Data Store
Cognos Upfront Dispatcher
Upfront.Server
Cognos Visualizer Web

Edition

Server.Dispatcher
Cognos Ticket Server
Services.Access Manager - Ticket

Server
PowerGrid
Services.Powergrid
Steps
Manager.

4. In the Explorer window, click the computer name, product family, component, or category
whose services you want to start.
The item you click must contain one or more services. To check for services, expand the
categories and look for the service icon.
5. From the Actions menu, click Start Service.
Specify the Authentication Source

You need to specify the authentication source that you want your Cognos products to use for
security information such as user IDs and passwords at runtime.
You must complete this task on every computer on which you installed Cognos components.
You can complete this task at any time by using Configuration Manager. For more information,
Your system administrator can provide the information you require to identify the directory server
you want to use.
Note: To support the upgrade process from Cognos Series 7 to Cognos Series 7 Version 2, or if
you intent to maintain both versions, the directory server schema version must be Compatible
with Series 7.0 and earlier versions.
Whats Next?
The distributed installation is now complete. Before you start using Cognos Series 7 products,
you should test all the components to ensure that they work and that they can communicate with
each other. For more information, see "Testing the Installation" (p. 121).
Chapter 7: Installing to Upgrade

This chapter contains information you should use only for upgrading your software from previous
versions of Cognos Series 7.
If you are not upgrading, you can do a default installation of all components (p. 61), with
components configured to use standard default settings.
Alternatively you can install only the components you want (p. 77) and then complete the
required configurations.
If you are upgrading from a pre-Series 7 version, you must first upgrade to Cognos Series 7
using the instructions in the installation guide for your 7.0 product.
It is very important that you plan your upgrade. We recommend that you first create an upgrade
schematic. Write down all the locations where Cognos Series 7 products are currently installed
and any new locations to be added.
For information about planning the sequence of your upgrade tasks see "The Upgrade
Process" (p. 131) and "Mixed Version Environments" (p. 55).
During an upgrade, you specify which components you want to install and where you want to
install them. The second phase of the installation, therefore, involves configuring the required
settings for each component.
If you distribute server components across multiple computers, you must specify the location of
the server and gateway components and manage the server configuration file (.csx) on each
computer. This file contains all the server configuration information so that gateway components
can communicate with their associated servers. For more information about configuring
distributed server environments, see the Configuration Manager User Guide.
If you intend to run both versions of Cognos Series 7, additional configuration is required. For
more information, see the "Mixed Version Environments" chapter in this guide and the
The first phase of an upgrade involves preparing your work environment and copying the
required software components to one or more computers. You must do preparatory and
installation tasks, such as the following:
Install a directory server (optional; see the Supplementary Software Installation Guide).
Install ObjectStore, if required.
Copy the Cognos components.
After you complete the tasks in this checklist, you are ready to configure the components
(p. 105) and upgrade the data (p. 129). The final phase is to test the installation (p. 121).

hardware requirements. For an in-place upgrade, your computers must meet the system
requirements for both the new and old versions of the products you are upgrading.
Preparing for the Installation

Before you start any installation, we recommend that you close all programs that are currently
running. This will help to ensure that the installation program can copy all the required files onto
your computer.
Note: Ensure that you have verified your system requirements; for example, a Web server is
installed and started.
"Cognos".

Before you install, you must verify that you have administrator privileges for any new Windows
computer you are installing on. If after completing the following steps, you verified that you are
your computer.
Steps in Windows NT

Steps in Windows XP

Before you install, ensure that any computer receiving new software has a TEMP system
variable that points to the folder where you want to store temporary files. During the installation,
files from the CD are temporarily copied into this folder.
Steps in Windows NT


files.
7. Click OK.
Steps in Windows XP
2. Click System.
8. Click OK.
Create the Database User for Cognos NoticeCast

For an in-place upgrade, the database and database user were already created for the older
version of Cognos Series 7 Alerts/Notifications. You can skip this section.
For a staged upgrade, you are installing components on new computers and must complete this
section.

database instance.
ID and password.
Upgrading to Sun ONE Directory Server

You may be able to continue using your existing directory server with the new version of Cognos
Series 7. However some older versions of directory server, such as Netscape Directory Server
4.12, are not supported by Cognos Series 7 Version 2. You can take advantage of new
capabilities and better performance by installing Sun ONE Directory Server.
For instructions about upgrading to Sun ONE Directory Server, see the Cognos Series 7
When you finish upgrading the directory server, return to this document and continue installing
Cognos Series 7 components.
If you kept the older directory server for use with the older version of Cognos Series 7 products,
you must now configure the new directory server for use with the new version of Cognos Series
7 products. For instructions, see "Configure the Directory Server" (p. 110).
For example, you can continue to use Windows 2000 Active Directory.
Upgrade ObjectStore Software

If the Cognos server product you intend to upgrade uses ObjectStore, you must install the
version of ObjectStore 6.0 provided on your Cognos Series 7 Version 2 CD.
Install ObjectStore on every Windows computer
that has Architect installed on it
is to be used by Impromptu Web Reports
Because you can have only one Impromptu Web Reports data store to serve all your
Impromptu Web Reports servers, you should install ObjectStore on a computer that has a
backup system in place.
You must install Architect and ObjectStore on computers that belong to the same domain.
Otherwise, you will not be able to create and authenticate Architect models. In addition, if you
want to use an Architect model (.cem) that is stored on a shared network drive, you must install
ObjectStore both on the computer that owns the network drive and on the client computer that
accesses the drive. This client computer is the one that is used to run Architect.
You must first stop the Impromptu Web Reports Service Manager service (if applicable) and
ObjectStore 6.0 services currently running on your Windows computer. You must then uninstall
the old version of ObjectStore 6.0 before installing the new version provided on your Cognos
Series 7 Version 2 CD. For more information, see the "Uninstalling" chapter. The new version of
ObjectStore uses the same ports as the old version. The new version of ObjectStore 6.0 will
work with both Cognos Series 7 and Cognos Series 7 Version 2 products.
Steps

folder c:\ODI.
Upgrading Cognos Series 7 Components

The process for an upgrade is the same as installing for a new installation. The 7.1 components
are installed by default to a new location under a cer3 folder.
To upgrade more than one Cognos product, follow the instructions in this chapter and observe
these general guidelines:
Stop the 7.0 services and processes if they are running on the same computer you are
installing on.
Install the shared Cognos components first (Ticket Server, Access Manager, Upfront). You
can then deselect them from subsequent installation menus.
If you plan to copy components to more than one computer, you should first familiarize
yourself with your distributed installation options. Some components must be installed
together on the same computer. For more information, see the Planning Advanced
Installations Guide.
When prompted to configure at the end of the installation, select the Exit the Installation
Wizard Without Configuring Components option and then copy components from the next
CD before configuring components.
After you copy all the 7.1 components, you must complete the configuration steps (p. 105),
and start the services (p. 119). You must be aware of dependencies, such as shared data
stores, when starting services.
You must select the same locale and character set for server and client components when
installing components on separate computers. You may notice inconsistencies if the settings
for locale and character set are not the same for server and client components.
Stop Services
Steps

Copy the Components

Repeat the following steps for each component that you copy. You may be required to stop a
Cognos service before you can copy another Cognos component.
If you are installing Cognos NoticeCast server, select Exit the Installation Wizard Without
Configuring Components and then follow additional instructions (p. 114) to configure the
NoticeCast server.
Steps
specific product.
If no installation menu appears, double-click Setup.exe from the root of the CD.
Next.
7. In the Installation Type dialog box, click Custom, and then click Next.
8. In the Component Selection dialog box, select the components that you want to install,
and click Next.
9. In the Character Set Selection dialog box, select the set of locales that you want to use
and click Next.
10. If the Language Selection dialog box appears, select the languages you want to use and
click Next.
13. In the Shortcut Folder dialog box, click Next to accept or change the default Program
The Installation Summary appears and lists all the components that will be installed for the
upgrade.
14. If you are satisfied with your selection, click Next, or click Back to make corrections, and
then click Next.
This starts the file transfer of the selected components.
15. In the Component Configuration dialog box, select Exit the Installation Wizard Without
Configuring Components, and click Next.
Configuring Cognos Series 7

The next phase of the upgrade installation process involves configuring all the components,
including third-party software. You must complete this phase before the new version of Cognos
Series 7 will work.
Notes
Configuring a Web server is applicable only if you are installing Cognos Series 7 Query,
Cognos Series 7 Reporting, Cognos Series 7 Impromptu Administrator (if using
PowerPrompts), Cognos Series 7 Visualization, Cognos Series 7 OLAP and Cognos Series
7 Alerts/Notifications.
In addition to the following list, if you are installing Cognos Series 7 Alerts/Notifications, you
must also configure the Cognos NoticeCast components (p. 114).
You must configure
the Web server. You only do this task once for all your Cognos Series 7 products.
the new directory server, if it cannot use the default settings. For example, you kept the old
version, which uses the default settings, for use with the older version of Cognos Series 7.
You do this task only once for all your Cognos Series 7 products.
Note: If you are using Cognos Deployment Manager to upgrade your Series 7 application,
then your Access Manager schema version must be set to Compatible with Series 7.0 and
earlier versions until after the upgrade is complete.
the authentication source. You must do this task on every computer on which you installed
Cognos components. To support the upgrade process, or if you intent maintain both Cognos
Series 7 and Cognos Series 7 Version 2 components, you must use a namespace schema
that is compatible for both versions. For more information, see Configure the Directory
Server.
any component settings that you want to change to better suit your specific environment.
This task includes applying the settings to the components on the computer.
the locations of each server component. This task includes updating the server
configuration file so that all the components can communicate with one another. You only
need to do this task if you distributed your server components across more than one
computer.
Note: Even if you accepted the default configuration when you were copying the
components and do not want to change any settings, you must still apply the settings to the
components on the computer.
After you have everything configured, and have applied the settings, you must start all the
services and processes.
You may need to perform some of these tasks in an iterative fashion, depending on how you set
up your upgrade.
Using the Configuration Manager

To configure Cognos components, you use Configuration Manager. Configuration Manager has
two interfaces, a graphical user interface and a command line interface. You can use either
interface to configure Cognos components on Windows. You can use only the command line
interface on UNIX. In the graphical user interface, the object hierarchy is shown as a folder
structure in the Explorer window. In the command line interface, you navigate through the
object hierarchy by using the select and list commands, and by specifying a sequence of
objects that are delimited by the dot (.) operator.
There are several ways to configure Cognos components. You can directly modify and apply
configurations to one or more components, or you can create scripts.
For more information about using Configuration Manager, see the Configuration Manager User
Guide.

Your Web server currently has the three virtual directories (also known as Web aliases) defined
for use with 7.0 Web products. The following table shows the recommended default aliases and
locations for the Cognos Series 7 installation. The default installation_location is C:\Program
Files\Cognos\cer2.
Alias
Location
Permission
cognos
Read
Execute
cognos/help
Read
You can leave these Web aliases in place for continued use with 7.0 Web products. You must
now create an additional set of unique Web aliases for use with the 7.1 products. You can use a
different name instead of cognos in the aliases. However, you must use cgi-bin and help as the
second part of the alias, for example, your_name/cgi-bin and your_name/help. The following
table shows the new aliases. The default installation location for 7.1 products is C:\Program
Files\Cognos\cer3.
Alias
Location
Permission
cognosv2
Read
cognosv2\cgi-bin installation_location\cgi-bin
cognosv2\help
Execute
installation_location\Documentation Read
After creating the three new Web aliases, you must then update the Web alias information in
Upfront Server Administration. See the instructions at the end of this section.

Notes
If you are using Cognos Visualizer Web Edition Series 7 with iPlanet4 Web server, you must
set up two additional aliases. The following aliases are not required by other Cognos
products, or if you are using Cognos Visualizer Web Edition with a different Web server.
Alias
Location
Permission
cognos/plugin
installation_location\webcontent\
plugin
Read
cognos/viz/downl installation_location\webcontent\v Execute

oad
iz\download
User Guide if you are changing Web aliases for an existing installation.
Also, see Configuration Manager User Guide if you are using alternate gateways, such as
NSAPI or ISAPI, instead of the default CGI programs with your Web products.
(Windows 2000)
6. In the Alias box, type a name that is different from the one being used with the older
Cognos Series 7 products (for example, Cognosv2).
click Add.
Cognos Series 7 products (for example, Cognosv2/cgi-bin).
11. To define the access level for the new cgi-bin virtual directory:

Cognos Series 7 products (for example, Cognosv2/help).


Tools, and double-click Internet Service Manager.
2. In the left pane of the console, expand the folder that has the name of your computer.
product.
4. Click New, Virtual Directory to create the first of three virtual directories using the Virtual
Directory Creation Wizard.
5. Click Next.
6. On the Virtual Directory Alias page, in the Alias box, type a name that is different from the
one being used with the older Cognos Series 7 products (for example, cognosv2) and click
Next.
7. On the Website Content Directory page, next to the Directory box, click Browse and then
click the installation_location\webcontent folder.
10. In the left pane of the console, right-click the folder called cognos and click New, Virtual
Directory.
one being used with the older Cognos Series 7 products (for example, Cognosv2/cgi-bin),
and click Next.
click the installation_location\cgi-bin folder.
check boxes.
15. Click Finish.

one being used with the older Cognos Series 7 products (for example, Cognosv2/help) and
click Next.
click the installation_location\cgi-bin folder.

Click Properties.
22. Close the console.

Steps for iPlanet 6

Manage.
4. Click the Content Mgmt tab, and click Additional Document Directories.
5. In the URL Prefix box, type a name that is different from the one being used with the older
Cognos Series 7 products (for example, Cognosv2)
For example, d:\Program Files\Cognos\cer3\webcontent.
Cognos Series 7 products (for example, Cognosv2/help).
For example, d:\Program Files\Cognos\cer3\Documentation.
Cognos Series 7 products (for example, Cognosv2/cgi-bin).
14. In the CGI Directory box, type the full path for the cgi-bin folder.
For example, d:\Program Files\cognos\cer3\cgi-bin.
15. Click OK, Save and Apply, and then click OK.

Steps to Update the Web Alias Information in Upfront Server Administration

1. From the Start menu, click Programs, Cognos Series 7 Version 2, Cognos Server
Administration.
2. When the Cognos Server Administration window opens, click Portal.
3. Log on to connect to the Web server.

4. In Upfront Server Administration, double-click the server group.
The Server Group Properties dialog box opens.
5. In the General tab, in the Web content root directory box, replace the default Web alias
name \cognos with the name you used for your 7.1 virtual directory (for example,
\Cognosv2).
6. Click OK.
7. From the Actions menu, click Stop and wait until the action has completed.
8. From the Actions menu, click Enable to restart the Web server.

When you upgraded the directory server, you did one of the following:
You uninstalled the older version, installed the new version, and then restored the directory
server data to the new directory server. In this case, it is not necessary to configure the
directory server.
You kept the older version of the directory server for use with an older version of Cognos
Series 7 and installed a second directory server. In this case, you must complete additional
configuration so that the new Cognos products can communicate with the new directory
server.
You do this task only once. Configuration can be done on the computer where the directory
server is located if the same computer also has Cognos components required for the
configuration. Configuration can also be done on any other computer where you installed
Cognos components.
You only need to configure one directory server to use with all your Cognos Series 7 Version 2
products. To support the upgrade process from Cognos Series 7 to Cognos Series 7 Version 2,
or if you intent to maintain both versions, you can not use the default configuration settings. You
must select the Compatible with Series 7.0 and earlier versions option for the schema
version. After you complete the upgrade, and if you are not supporting Cognos Series 7.0
components, you can select update the schema version to Current.
The configuration process is the same regardless of whether you installed Sun ONE Directory
Server or Windows 2000 Active Directory. By completing this additional configuration task, you
are
extending the directory server schema so that the directory server is compliant with Cognos
products
creating a namespace on the directory server in which you can store Cognos security data,
if a namespace does not already exist.
enabling communication between the directory server and the ticket server
Note: You can configure a Sun ONE directory server from either a UNIX or Windows computer,
regardless of whether your directory server is installed on a UNIX or Windows computer. You
must use Configuration Manager on a Windows computer to configure Windows 2000 Active
Directory for use with Cognos products. If you wish to configure your directory server from a
UNIX computer, see the UNIX installation guide.

The following table shows all the properties that you must verify or configure.
Property
Value
Are you sure you want

to configure this
directory server?
Enables you to change the default

properties of the directory server.
Schema Version

information.
The default setting is No
The displayed default is Current

If you are still using your directory server
with Cognos Series 7.0 and earlier products,
you must change the value to Compatible
If you are have two active directory servers
you must use the Compatible with Series
7.0 and earlier versions setting for the
directory server used by Cognos Series 7.1
until the upgrade is complete. You do not
have to change the configuration for the
existing directory server to support the
upgrade process. For the directory server
used by Cognos Series 7.1, you can change
the value to Current when the upgrade to
Cognos Series 7.1 is complete.
If you are only using your directory server
with Cognos Series 7 Version 2, we
recommend that you use the default value
Current.
Notes
You must be ready to switch
permanently to Cognos Series 7 Version
2 before you upgrade to the Current
schema version.
If upgrading from an older version of a
directory server, you must change the
value to Compatible with Series 7.0
and earlier versions in order to restore
the directory server data from the .ldif.
Server Type
The type of directory server that you

installed.
The default setting is Auto Detect, which
will automatically determine the type of
directory server you are using.
Computer

where the new directory server is installed
Port
The port that is used by the new directory

server.
The default is port 389
If you kept the older version of the directory
server, type a different port number for the
new directory server.
Property
Value
Base Distinguished
Name (DN)
A distinguished name (DN) which will be the

first entry in the directory tree creating a
branch for your data.
The Cognos default DN for Sun ONE
Directory server is o=cognos, c=ca
The Sun ONE default DN for Sun ONE
Directory Server is dc=your organization,
dc=com
The default DN used by Windows 2000
Active Directory is o=company,
dc=computer name
If you used a different base DN when you
installed the directory server, specify the
new base DN.
Unrestricted User
distinguished name
(DN)

administrator uses to manage the contents
of the directory server with unlimited
privileges.
The default used by Sun ONE Directory
Server is cn=Directory Manager
dc=computer name
Unrestricted User
password
Primary Ticket Server

where the ticket server is installed and the
port that is connected to the ticket server.
The Cognos default is admin1234
The default is your_computer_name:9010

Secondary Ticket
Server (1, 2, 3, 4)
The computer names and port numbers of

additional ticket servers.
The default is none
To support failover between ticket servers,
specify one or more secondary ticket
servers.
Enable Ticket Server

Load Balance
Enables you to balance the load between

multiple ticket servers.
The default is No
To enable load balancing between ticket
servers, specify at least one secondary
ticket server and select Yes
Default Namespace
Name
The name of the default namespace in the

directory server.
The default name is Default
Default Namespace
Administrator Name
Administrator
Property
Value
Default Namespace
Administrator
Default Namespace
Administrator
Password
The default is no password.
Complete these steps to configure your directory server. These steps apply to both local and
remote configuration.
Note
Manager that is installed on a Windows 2000 computer. To use a version of Configuration
Manager that is installed on a Windows NT or Windows 98 computer, you must first install the
ADSI patch, found under Support Files on the Supplementary Software CD. For more
information, see the Additional Products and Services appendix.
Steps
These steps apply to both local and remote configuration.
Manager.
4. In the Explorer window, expand the Services component and then expand Access
Manager - Directory Server.
The Properties window shows the property values that the Cognos product expects in Sun
ONE Directory Server. If you used different settings when installing the directory server, you
must change these settings so that they match. If you do not need to change anything, skip
to step 10.
6. Select the Are you sure you want to configure this directory server? property, and
change the value to Yes.
7. Select the Default Namespace Name property, and type the name of the namespace that
you want to create.
8. Change other properties as required.
Ensure that the Computer property contains the correct location of the directory server,
especially if you are configuring a remote directory server.
9. In the Explorer window, select the General category, and from the Actions menu, click
Apply Selection.
Tip: You can create a script to specify the authentication source, which is convenient if you are
installing components on many computers. For more information, see the Configuration
Manager User Guide.
Specify the Authentication Source

You need to specify the authentication source that you want your Cognos products to use for
security information such as user IDs and passwords at runtime.
You must complete this task on every computer on which you installed Cognos components.
You can complete this task at any time by using Configuration Manager. For more information,
Your system administrator can provide the information you require to identify the directory server
you want to use.

Note: To support the upgrade process from Cognos Series 7 to Cognos Series 7 Version 2, or if
you intent to maintain both versions, the directory server schema version must be Compatible
Configuring Component Settings

After you copy the Cognos components to the computer in an upgrade installation, you must
configure component settings before you use the new version of Cognos Series 7.
If you want to continue to run your 7.0 components after the upgrade, and the new components
are on the same computer as the old components, you must do the following:
Change the port numbers for the 7.1 components. The default port numbers are already
being used by the 7.0 components.
Configure a unique data store name for the 7.1 Cognos Query data store.
If you are using both your 7.0 and 7.1 versions of Upfront instead of sharing Upfront 7.1
between the two versions of Cognos Series 7, use unique names for the Upfront data
stores.
Use the same name for the Impromptu Web Reports server group and the Upfront server
group in the 7.1 environment as in your 7.0 environment because these names are stored in
the Impromptu Web Reports data store.
Create server groups in your 7.1 environment that are equivalent to the server groups in
your 7.0 environment and configure them with equivalent settings.
For information about other configuration changes you may need to make, see "Mixed Version
Environments" (p. 55) and the section on configuring mixed environments in the Configuration
Manager User Guide.
For instructions about managing the server configuration files (cer3.csx) on each computer in a
distributed environment, see the Configuration Manager User Guide.
For information about modifying configuration settings for specific components, see the
Configuring Cognos NoticeCast Components

For an in-place upgrade, the database and database user are already created for the older
version of Cognos Series 7 Alerts/Notifications and you can skip this section. You can now apply
the configuration (p. 119).
For a staged upgrade, you are installing components on new computers and must complete this
section.
Manager User Guide.

upgrade the NoticeCast data store

steps.
Manager.

database.
category.
Configuration.




example,
driver file.
property points to
property points to
Steps to Upgrade the NoticeCast Data Store

Ensure that your database administrator backed up your NoticeCast data store before
continuing with these steps.
property, and select Update.
This action updates the Cognos NoticeCast data store and configures your computer with
the Cognos NoticeCast server settings. If error messages appear, verify that the database
user is assigned unlimited privileges.



server.
Steps
Manager.
Client component.

and the NoticeCast server on different computers. When these components are on different
Steps
Manager.
database.
category.

Configuration.



example,
driver file.
property points to
property points to
Apply the Configuration

Regardless of whether you decide to accept the default settings or modify them, you must apply
all the configuration settings that you plan to use. The following steps assume that you have
made all the required changes to your configuration settings, and you are ready to apply them to
your server environment.
Steps
Complete these steps on every Windows computer that contains a Cognos component.
Manager.
4. In the Explorer window, click the computer.
All the configuration settings are applied to all the components that are installed on the
computer.
Start Services
After everything is installed and configured, you must start all the services that are associated
with Cognos Series 7 products. Cognos services and processes are not registered during the
upgrade until you start them.
For a distributed installation, we recommend that you start the components in the following
order:
Cognos ticket server
directory server
Upfront services
any shared data stores
ObjectStore services (if applicable)
application servers
Note: For Impromptu Web Reports, when you publish a report set using UNC format for the
report set location, an error will appear if the Impromptu Web Reports services are started as a
system account. For all Impromptu Web Reports servers in the server group, set the Cognos
IWR Service Manager service to start as a user account. Then retry your attempt to publish
using UNC. For more information, see the Impromptu Web Reports Administrator Guide.

The following table contains a list of the Cognos services and processes and where you can
locate them in the object hierarchy in Configuration Manager.
Service or Process
Object Hierarchy Location
Cognos IWR Service

Manager
Cognos Impromptu Web

Reports.Server
Cognos PowerPlay
Enterprise Server
Cognos PowerPlay Enterprise

Server.Dispatcher
Cognos Query.Data Store
Cognos Query.Dispatcher
Cognos Query Server

Manager
Cognos Query.Server
Cognos NoticeCast
Dispatcher
Cognos Noticecast.Noticecast Server
Cognos NoticeCast Data

Store
Cognos Noticecast.Noticecast.Data
Store
Cognos Upfront
Upfront.Shared.Server Administration
Upfront.Data Store
Upfront.Server

Edition

Server.Dispatcher
Services.Access Manager - Ticket

Server
PowerGrid
Services.Powergrid
Steps
Manager.
4. In the Explorer window, click the computer name, product family, component, or category
whose services you want to start.
The item you click must contain one or more services. To check for services, expand the
categories and look for the service icon.
5. From the Actions menu, click Start Service.
Whats Next?
You completed the upgrade of the Cognos Series 7 components. You must now upgrade your
application data (p. 137).
You can also test components to ensure that they work and that they can communicate with
each other (p. 121).
Chapter 8: Testing the Installation

You can choose to test Cognos Series 7 when you have completed the entire installation
process. This can be
immediately after completing the procedures for a default installation (p. 61)
immediately after completing the procedures for a custom installation (p. 77)
after upgrading the software (p. 99) and optionally upgrading the data (p. 129)
If data is required for the test, you can test with your own data created with an earlier version, or
you can use the product samples. For information about using the samples, see the Installation
Testing and Samples Setup Guide.
Test Your Web Server

You can test the Web server by opening the default Web page. This test assumes that you have
configured your Web server as previously described.
Steps
1. Verify that you have configured a Web server.
2. Start a Web browser.
3. Type the URL for the default page of the Web server you configured and press Enter.
The URL is http://server_name/
where server_name is the name of your Web server. By default, this is the name of your
computer.
The default.htm appears in your Web browser.
Test ObjectStore
ObjectStore is installed for the Impromptu Web Reporting data store, and for Architect. You can
test the ObjectStore installation.
To verify that ObjectStore was installed successfully and is ready to be used, ensure that the
services are running.
Steps
1. Open the Services dialog box.
For Windows NT, click Start, Settings, Control Panel, and then double-click Services.
For Windows 2000, click Start, Settings, and Control Panel. Double-click
Administrative Tools, and then double-click Services.
2. Verify that ObjectStore Cache Manager R6.0 and ObjectStore Server R6.0 have the
Status set to Started, and Startup set to Automatic.
Test the Directory Server

Use these steps to test your directory server. Before you can test using Access Manager
Administration, you must add a connection to your directory server. It may be convenient to also
set up the run-time credentials for Access Manager and then save all the connection information
in a Cognos security administration (.csa) file for subsequent use each time you or the
administrator opens Access Manager Administration. These steps apply whether you are using
Sun ONE Directory Server or Windows 2000 Active Directory.
If a saved .csa file is already available because you or your administrator previously set up the
directory server in Access Manager Administration, then you can simply test it by opening the
.csa file, accessing the directory server property sheet, and clicking Test. Otherwise, when you
complete the following tasks, you will also create a .csa file.
Steps to Add a Connection to Your Directory Server

Administration, and then click Security to start Access Manager Administration.
Access Manager Administration opens.
2. In the left pane, click the Directory Servers folder.
3. From the Action menu, click Add Connection.
4. In the Host box, type the name of your computer or the server identifier you defined when
installing your directory server.
5. In the Port/SSL Port box, type the port used by the data directory server.
6. In the Base Distinguished Name box, type the Base Suffix value you defined when
creating the data directory server.
The Cognos default used for Sun ONE Directory Server is
o=Cognos, c=CA
If using Windows 2000 Active Directory, the default is o=company, dc=domain name
7. Click Test to verify your connection.
A message appears stating that the directory server is responding.
Steps to Test the Runtime Credentials

Access Manager Administration opens.
2. In the Explorer window, expand the Directory Servers folder.
3. Right-click the directory server to connect to, and select Properties.
4. Click the Runtime Credentials tab.
The Administrator Access dialog box appears.
5. In the Runtime Administrator Distinguished Name (DN) box, type the distinguished
name that the administrator uses to log on to the directory server. This is the Root DN you
defined when creating the data directory server.
The Sun ONE Directory Server default is cn=Directory Manager
If using Windows 2000 Active Directory, the default is cn=Administrator, cn=users,
dc=domain name
6. In the Runtime Administrator Password box, type the password you defined for the Root
DN.
For example, the Cognos default used for Sun ONE Directory Server is admin1234
If using Windows 2000 Active Directory, the default is password.
7. Click Log On and then click Test.
A message appears stating that the credentials are valid.
Steps to Save the Connection Information

1. From the File menu, click Save.
2. Type a file name for the .csa file and save it in a folder; for example
installation_location\bin\cognos.csa
where installation_location is the location where you installed your Cognos product.
3. Close Access Manager Administration.
Tip: The next time you start Access Manager Administration, you can simply load the saved
connection information by opening the .csa file, or set this file as your default from the File
menu.
Test the Ticket Server

Use these steps to test your connection to the ticket server. In these steps you open the .csa file
you created in the previous section. The .csa file saves the connection information and can be
used to reload the information into Access Manager Administration.
Steps
1. Verify that you completed the test of the directory server and saved a .csa file.
3. From the File menu, click Open and browse for the .csa file you previously created and click
Open.
4. In the Explorer window, expand the Directory Servers folder.
5. Right-click the name of the computer where your directory server is installed and click
Properties.
The Directory Server Properties dialog box opens.
6. Click the Ticket Server tab.
The Administrator Access dialog box appears.
7. In the Runtime Administrator Distinguished Name (DN) box, type the distinguished
name that the administrator uses to log on to the directory server.
This is the Root DN you defined when creating the data directory server. The recommended
default value is cn=Directory Manager
8. In the Runtime Administrator Password box, type the password you defined for the Root
DN.
For example, admin1234
9. Click Log On.
10. Click the Ticket Server tab.
If you used Configuration Manager to configure one or more ticket servers, the information
appears in the Ticket Server Connections list.
11. To connect to additional ticket servers, click Add, and in the Prompt box, type the name or
IP address, and the port of the ticket server computer using the host:port format.
The port you specify must be the same port specified in Configuration Manager. The default
port number is 9010.
12. For each ticket server in the Ticket Server Connections list, select a ticket server and click
Test.
A message appears stating that the ticket server is responding. If an error message
appears, check the connection information.
13. Click OK to close the message box.
14. Click OK to save the changes and close Access Manager Administration.
Note: The entries in the Ticket Server Connections list should not be rearranged at runtime. If
you decide to change the order of your ticket server connections, you must restart your Upfront
services or you may experience authentication problems.
Test Upfront
Use these steps to make sure that you can access Upfront through your Web browser and to
test Upfront Server Administration. You can use Upfront Server Administration to manage
Upfront servers. For more information, see the Upfront online help.
Steps to Test Upfront Web Access

1. Start a Web browser.
2. Type the URL for the Upfront page of the Web server you configured and press Enter. The
URL is http://server_name/cognos/
where server_name is the name of your Web server. By default, this is the name of your
computer.
Steps to Test Upfront Server Administration

Administration, and then click Portal to open Upfront Server Administration.
The Connect dialog box appears.
2. In the Server name box, type the name of your Upfront server (your computer name is the
default), and click Connect.
3. If prompted, log on to the Cognos Common Logon.
To use the default, type Administrator for the User ID, and leave the password box blank.
Upfront Server Administration opens.
4. On the Server menu, click Add Server, type the fully qualified name of your Upfront server,
and click OK.
Your Upfront server is added under the Upfront server group and Upfront Server
Administration is ready to use it.
Test Cognos Series 7 Reporting

You can test the Impromptu Web Reports administration tools and then test using Impromptu
Web Reports
Test Impromptu Web Reports - Server Administration

Use these steps to test Impromptu Web Reports - Server Administration, the tool you can use to
manage Impromptu Web Reports servers.
Steps
1. From the Windows Start menu, click Programs, Cognos Series 7 Version 2, Cognos
Server Administration.
2. In the Cognos Server Administration window, double-click Reports to open Impromptu
Web Reports - Server Administration.
3. Type your User ID, password, and the computer where an Impromptu Web Reports server is
installed, and click Connect
Impromptu Web Reports - Server Administration opens and you are connected to the server
group that this Impromptu Web Reports server is a part of.
You can set properties for the servers, start and stop server processes, and monitor queues.
Note: You can also use Configuration Manager for some of these tasks.
Test Impromptu Web Reports - Report Administration

Use these steps to test Impromptu Web Reports - Report Administration, the tool you can use to
publish report sets.
Steps
1. From the Windows Start menu, click Programs, Cognos Series 7 Version 2, Cognos
Server Administration
2. In the Cognos Administration Server window, double-click Report Publishing to open
Impromptu Web Reports - Report Administration.
3. Type your User ID, password, and the computer where an Impromptu Web Reports server is
installed, and click Connect
Impromptu Web Reports - Report Administration opens.
Test Using Impromptu Web Reports

For information about completing the following tests using sample data, see the Installation
To test Impromptu Web Reports, use Impromptu Web Reports Administration to publish a report
set to Upfront, which serves as the Impromptu Web Reports interface. You then use your Web
browser to access Upfront and view the Impromptu Web Reports you published.
To test Impromptu Administrator, you can create an Impromptu report based on an Impromptu
catalog.
To test Architect working together with Impromptu Administrator, you can open an Architect
model and export the Architect package to an Impromptu catalog. You can then create a report
in Impromptu Administrator based on this catalog.
Test Cognos Series 7 Query

You can test the Cognos Query Administration tool and then test using Cognos Query and its
associated products.
Test Cognos Query Administration

Use these steps to test Cognos Query Server Administration, the tool you can use to manage
Cognos Query servers.
1. To start Cognos Query Server Administration, choose one of the following:
In a Web browser, type the URL for Cognos Query Server Administration
http://server_name/cognos/cq/cqadmin.html
From the Start menu, click Programs, Cognos Series 7 Version 2, Cognos Server
Administration, and then click Ad-hoc Queries to start Cognos Query Server
Administration.
A Logon page appears.
2. Type the default User ID Administrator and leave the Password box blank, and then click
Log On.
3. On the User Class page, click OK.
Cognos Query Server Administration opens as a Java applet. Your Cognos Query servers
are listed in the Query Server tab. You can set properties for the servers, start and stop
server processes, and monitor requests. You can also use Configuration Manager for some
of these tasks.
Note: If you do not have version 1.3 or higher of a Java Runtime Environment (JRE) plug-in
on your computer, a Java Plug In page appears and prompts you to download. Links to the
appropriate Web site for your operating system are provided on the page. Follow the
download instructions and refresh your Web browser.
Test Using Cognos Query

For information about completing the following steps using sample data, see the Installation
To test Architect working together with Cognos Query, you can open an Architect model, create
a package for Cognos Query, and publish the package to an Upfront NewsBox. You can then
access Upfront and view or run the queries that are in the package.
Test Cognos Series 7 OLAP

You can test the PowerPlay Enterprise Server Administration tool and then test using the OLAP
products.
Test PowerPlay Enterprise Server Administration

Use these steps to test PowerPlay Enterprise Server Administration. You can use this tool to
manage PowerPlay Enterprise Servers.
Administration, and then click OLAP Cubes and Reports to start PowerPlay Enterprise
The Connect to Server dialog box appears.
2. In the Server name box, verify or type the name of your PowerPlay Enterprise server (your
computer name is the default), and click OK.
Because this is your first access, you will be prompted with a message to secure your server
now.
3. Click Yes to secure your server.
4. If prompted, log on to the Cognos Common Logon. To use the default, type
Administrator for the User ID, and leave the password box blank.
PowerPlay Enterprise Server Administration opens.
5. In the Set Security dialog box, click OK.
Your PowerPlay Enterprise Server is added under the PowerPlay server group and several
sample cubes and reports are already listed under Items.
Note: If you intend to use Upfront, this last step is mandatory. You must also use the same
namespace for your PowerPlay Enterprise Server as you use for Upfront.
Test Using the OLAP Products

To test PowerPlay Enterprise Server, use PowerPlay Enterprise Server Administration to publish
a report or cube to Upfront. You then use your Web browser to access Upfront and view the
report or cube that you published.
To test your connection from PowerPlay for Windows to PowerPlay Enterprise Server, start
PowerPlay and open a remote cube on the server.
To test Transformer, you can open a cube (.pyi) or a Model Definition Language file (.mdl), which
is used to build a cube.
Test Cognos Series 7 PowerPlay Transformation Server

To test a PowerPlay Transformer Edition installation, use PowerPlay Transformer to create a
cube (.mdc file), and then open it with PowerPlay.
To test Architect working together with Transformer, you can open an Architect model and create
an Architect package for Transformer. You then start Transformer and create a new model based
on the Architect package.

To test PowerPlay for Windows or PowerPlay for Excel, you can open a local report or cube.
Test Cognos Series 7 Alerts/Notifications

You can test whether Cognos NoticeCast is connecting to your NoticeCast data store, by simply
starting the NoticeCast Server Administration tool.
Steps
Administration.
2. In the Cognos Server Administration window, click Alerts and Notifications to start
NoticeCast Server Administration.
To use the default, type Administrator for the User ID, and leave the password box blank.
NoticeCast Server Administration opens.
Before you can do any further testing using Cognos NoticeCast authoring, you must use
Cognos Server Administration to create a data source pool for the NoticeCast authoring
environment. See Cognos Series 7 NoticeCast Administration Guide to complete the required
procedures.
Test Cognos Series 7 Visualization

You can test the Cognos Visualizer Server Administration tool and then test using the Cognos
Visualizer products.
Steps to Test Cognos Visualizer Server Administration

Use these steps to test Cognos Visualizer Server Administration. You can use this tool to
manage Cognos Visualizer servers.
Administration, and then click Visualizations to start Cognos Visualizer Server
Administration.
The Connect to Server dialog box appears.
2. In the Server name box, verify or type the name of your Cognos Visualizer server (your
computer name is the default), and click OK.
Because this is your first access, you will be prompted with a message to secure your server
now.
3. Click Yes to secure your server.
Note: To use the default, type Administrator for the User ID, and leave the password box
blank.
5. In the Set Security dialog box, select user classes to set access privileges, and then click
OK.
Note: If you intend to use Upfront, this last step is mandatory.
The server appears in the Visualization Servers list.
Test Cognos Visualizer Server and Cognos Visualizer Authoring

To test Cognos Visualizer server, use Cognos Visualizer Server Administration to add a
visualization to the server and create a Table of Contents. To view the visualization, use a
browser to access the table of contents, install Cognos Visualizer Web Client, and then view the
visualization. Also, you can publish a visualization to Upfront and then access the visualization
using the Upfront entry.

For more information, see the Cognos Visualizer Administrators Guide.
To test Cognos Visualizer, open a sample visualization.
For more information, see the Cognos Visualizer User Guide.
Testing Distributed Sorting

There are situations that can cause data integrity problems when using Cognos products to
read and merge data after using distributed sorting.
The situations can occur only when all the following conditions are met:
A single logical SQL query is sufficiently complex to be decomposed into two or more
physical database queries, which are subsequently merged together after distributed
sorting. An example of a complex logical query is a query that has groupings with subtotals
containing extended aggregates, such as moving averages or rolling subtotals.
One or more physical queries is sorted by the database, and one or more physical queries
is sorted by another database, or by the operating system on the computer running the
Cognos product. Alternatively, two or more physical queries are sorted by the same
database, then the data results are merged based on the sorting order of the operating
system on the computer running the Cognos product. This process is called distributed
sorting and merging; it is not unique to Cognos products.
The sorting orders are different.
You will not have the problem if the data is sorted in the same order by all your databases and by
your operating system. Even if the data is not sorted in the same order, you may not be currently
experiencing the problem.
The problem is not unique to Cognos products. Products from other vendors may also be
affected by the same problem. To help you determine if you currently, or may in the future,
experience these problems, Cognos provides you with the following:
a Distributed Sorting Validation Kit
new product features to eliminate the potential problems in Cognos products
Please refer to the Troubleshooting Distributed Sorting topic in your products Readme file for
further information.
Part 3: Upgrading Data
Chapter 9: The Upgrade Process

This chapter defines in-place and staged upgrade methods and provides an overview of the
entire process. It also provides some checklists you may find useful during the upgrade process.
Planning the Upgrade

In any production environment, continued service to your users is of critical importance.
Planning the upgrade process is essential to maintaining your level of service, .
Upgrading all computers used by a Cognos application at the same time is not always possible
or necessary. However, for both in-place and staged upgrades, you must upgrade all
components for an application server before you can run the 7.1 application. For example, all
components that PowerPlay Enterprise Server requires must be upgraded before you can run
the 7.1 application.
Plan to use one of these upgrade strategies:
in-place upgrades
The 7.0 components reside on one or more computers, and the 7.1 components are being
installed on the same computers.
staged upgrades
The 7.0 components reside on one or more computers and the 7.1 components are being
installed on different computers that have no Cognos products already installed on them.
In-Place Upgrade
The in-place upgrade instructions assume that you are upgrading specific Cognos components
on the same computer that contains the previous version of the same components.
The first scenario for an in-place upgrade is that your Cognos Series 7 products and the
required third-party products are distributed across several computers. You intend to keep the
same distributed environment and to upgrade each component on the same computer where it
is currently located.
The second scenario for an in-place upgrade is that you have a single computer installation of
Cognos Series 7 products and the required third-party products. You intend to upgrade the
same computer using 7.1 components and new versions of third-party products if required.
All the application data that you need to upgrade is available on the same computer. After the
upgrade is complete, two versions of the same components can be active on the same
computer. The two versions can run independently of each other, or they can share some
components and run cooperatively in a mixed version environment.
Staged Upgrade
The staged upgrade instructions assume that you are using computers that have Cognos
products already installed on them. The 7.0 services and processes can continue to run while
you are installing the new software on different computers.
The first scenario for a staged upgrade is that your Cognos Series 7 products and the required
third-party products are distributed across several computers. You intend to duplicate the same
distributed environment on a different set of computers and will upgrade each new computer
with the corresponding 7.1 components.
The second scenario for a staged upgrade is that you have a single computer installation of your
Cognos Series 7 products and the required third-party products. You intend to use another
single computer for the upgrade of all components.

You may want to use the staged upgrade method when you want to use a test environment
separate from your production environment. You would deploy the application data from your
production environment to your test environment. Later, when the new environment is fully
tested, deploy everything back to your production environment.
Components can be shared and run cooperatively in a mixed version environment just like in an
in-place upgrade.
The Upgrade Process

Follow the same general process for both in-place upgrades and staged upgrades.
Upgrading the Software (required)

Upgrading the software is assumed to be complete when you use the information in this section.
For instructions, see the "Installing to Upgrade" chapter in this guide.
Upgrading Your Application Data (required)

You can upgrade your application data for one server at a time, starting with Upfront, in an
iterative manner.
The server components required by the application you are upgrading have already been
upgraded to the version 7.1 software. For instructions see the "Upgrading Application Data"
chapter in this guide.
Upgrading Your Client Data (required)

Your reports, catalogs, and models can be easily upgraded to the new version. For more
information, see the "Upgrading Client Data" chapter.
Upgrading Security Information (optional)

You complete this step only after all your Cognos Series 7 components have been upgraded
from 7.0 to 7.1 and you are ready to switch permanently to the new environment. For more
information, see the "Moving Permanently to Your New Version" chapter.
Do I Need to Back Up Before I Start?

You do not need to back up your data before you begin the upgrade process with some
exceptions. We recommend backing up in case a rollback is required.
You need to back up the Cognos NoticeCast data store. Your database administrator should
have a copy of the Cognos NoticeCast data store before installing Alerts/Notifications 7.1. After
upgrade, the Cognos NoticeCast data store is no longer usable with your 7.0 product.
We also recommend that you back up your directory server security information if you plan to
upgrade your directory server software to the Sun ONE directory server.
A new set of directories and data stores is created during the upgrade. The previous version of
your data remains in its original location.
If your normal production procedures include backing up data, you may want to schedule your
upgrade after you perform a regular backup.
For information about backing up your data, see the Cognos Series 7 Backup and Recovery
Guide.
Upgrade Checklist
Use the following checklist to verify that you are prepared for the upgrade of your application
data.
A rollback strategy is available.

At minimum, you backed up your
directory server, including namespaces
Cognos NoticeCast data store
other data stores depending on your rollback strategy

Cognos 7.1 components are installed, configured, and running.
Users were notified of possible service interruption.
This is applicable only for in-place upgrades.
Adequate time is scheduled for the upgrade.
You can choose to upgrade one application at a time.
Key stakeholders are available such as, UNIX administrators and database administrators.
Logon and password information is available.
Key stakeholders are aware that no rollback is possible after you
upgrade your directory server namespace
upgrade the Cognos NoticeCast data store
Checklist for Files You Need

The following table lists the files you need to complete the upgrade of the application data for
each product. Most of these files are created only when you complete the steps to pack the
application data for the specific product. For a staged upgrade, you must deploy these files to
the new computer. For an in-place upgrade, you must know where to find your files.
File or folder
Typical location
Your file name

and location
Upfront:
Themes folder
\cer2\webcontent\upfront
\cer2\templates\upfront
Package file
\cer2\bin\UpfPackage.pkg
Cognos Query:
Package definition file
\cer2\packages\<cq>\cq.dmd
Package file
\cer2\packages\<cq>\<cq>\cq.dmp
packlet folder
\cer2\packlets\cq
Impromptu Web Reports:

Report Store folder
\cer2\Report Store
dsdump output XML file
\cer2\bin\output.xml
PowerPlay
Metadata (7.0) folder
\cer2\ppserver\PPSRoot
cubes (.mdc files)
Conventions Used in the Upgrade Instructions

Assume that steps must be completed for both in-place upgrades and staged upgrades unless
they are identified specifically for one or the other.
Case Sensitivity
The upgrade chapters include many references to utilities that run from the Windows or the
UNIX command line interface.
The name of a utility, such as UpfUpgrade, is case sensitive on UNIX but not case sensitive on
Windows.
The name of any parameter, such as -database, or keyword, such as moveallreportset, is case
sensitive and must be typed in lowercase.
When the value of a parameter is a file or directory specification, it is case sensitive on UNIX
and case insensitive on Windows.
Default Locations and File Names

The steps assume that all Cognos products reside in the default installation locations, as
follows:
product version
Windows location
UNIX location
7.0
C:\Program
Files\Cognos\cer2
/usr/cognos/cer2
7.1
C:\Program
Files\Cognos\cer3
/usr/cognos/cer3
If you chose a different location, remember to substitute your path name in these instructions. If
the path name includes a space, you must enclose your path in double quotation marks, such as
"D:\Program Files\Cognos\cer2"
Default file names are used in examples. Remember to substitute your file names if you prefer
not to use the defaults.
Service and Process Names

In the steps that describe the upgrade process, the generic service names are used. The
following table lists the generic names and the actual Windows service and UNIX process
names as they appear in the software.
Cognos Series 7 services Windows service
UNIX process
ns-slapd.exe
ns-slapd
slapd.exe
slapd
Sun ONE Administration

Server
ns-httpd.exe
ns-httpd
httpd.exe
uxwdog
Cognos PowerPlay
Enterprise Server
ppserver.exe
ppserver
cqdbsrv.exe
cqdbsrv
Cognos Query Server
cqqrysvr.exe
cqqrysvr
cqdisp.exe
cqdisp
Cognos Query Server

Manager
cqsvrmgr.exe
cqsvrmgr
Cognos Series 7 services Windows service
UNIX process
TicketServer.exe
TicketServerd
Cognos Upfront
UpfrontAdministrati
on.exe
UpfAdmin
upfdbsrv.exe
upfdbsrv
(also starts rds.exe) (also starts rds)
UpfDispatcherServi UpfDispatcherSer
ce.exe
vice

Service Manager
IWSvcMan.exe
(also starts
IWIWRDisp.exe,
IWIRSDisp.exe,
IWSchMan.exe,
IWReqMan.exe)
iwsvcmgr (also
starts iwiwrdisp,
iwirsdisp,
iwschman,
iwreqman,
iwvtxsrv)
ObjectStore Cache
Manager R6.0
oscmgr6.exe
oscmgr6
ObjectStore Server R6.0
osserver.exe
osserver
Powergrid
Not applicable
udanetd
Chapter 10: Upgrading Application Data

A complete upgrade of a product involves installing new software and upgrading the server
application data and the client data.
If you plan to upgrade your server components one at a time and still continue to run using a
mixed version environment, you must upgrade in the following sequence:
1. Upfront
2. Other applications in any order
However, you must use the following sequence if you need drill-through navigation continue
to work at all stages:
Cognos Query
Cognos Visualizer
Cognos NoticeCast
Security
pack or copy your application data, if applicable
upgrade your server application data
upgrade your client data, such as reports, catalogs, and models
test your application
upgrade Directory Server (optional)
If you are also using Cognos PowerPlay Enterprise Server, you must upgrade PowerPlay
Enterprise Server first and then upgrade Cognos Visualizer. If these products are not upgraded
in the correct order, Cognos Visualizer may not open remote cubes.
Upgrading Upfront
You must upgrade Upfront first for all Cognos Series 7 Web products. Because all Cognos Web
products share the Upfront data store, you need upgrade Upfront only once. You can continue to
use your 7.0 Web products using Upfront 7.0, or you can use them using Upfront 7.1.
For your older version of Cognos NoticeCast to be compatible with Upfront 7.1, you should
upgrade Cognos NoticeCast to 7.0 Maintenance Release 2.
You may want to use your Upfront 7.1 version cooperatively with 7.0 servers, such as PowerPlay
Enterprise Server 7.0.
Before you upgrade the NewsIndex, you must create the equivalent server groups in your 7.1
environment that you have in your 7.0 environment. You would have done this as part of the
required configuration when you upgraded the software.
If you also intend to upgrade Impromptu Web Reports, the Upfront server group names and the
Impromptu Web Reports server group names must be the same in your 7.1 environment as in
your 7.0 environment. This is required because these server group names are stored in the
Impromptu Web Reports data store. If you used the default server group names for Upfront and
Impromptu Web Reports 7.0, you can use the default server group names again with your 7.1
products because the server group names have not changed. If you customized the server
group names, continue using the same customized names.
To upgrade Upfront, you will
pack the Upfront data store by using UpfPack (required)
unpack the Upfront data store by using UpfUpgrade (required)

copy your custom themes (optional)
verify that themes are assigned to users as required (optional)
Pack the Upfront Data Store (Required)

You must run Upfpack for each Upfront instance on the computer that runs the 7.0 Upfront
dispatcher. If the Cognos Web products share Upfront in a distributed environment, run UpfPack
only once for the single instance of Upfront shared by all products.
The following table describes the UpfPack parameters.
Parameter
Description
-un
Username. The user must be an Upfront security

administrator.
-pw
Password associated with the -un username.
-d
Location in the source environment where you want

to store the files generated by the UpfPack utility.
Ensure the folder exists. The default location on
Windows is
C:\Program Files\Cognos\cer2\bin
The default location on UNIX is
/usr/cognos/cer2/bin
-pn
Upfront package file name and location. The default

location is bin\UpfPackage.pkg
-i
Gateway mapping instructions file name and location.

The default location is bin\UpfPGInstructions.htm
-h
Help information.
The packing process creates the package file you will later use to upgrade the Upfront data
store:
On Windows, the default location is \cer2\bin\UpfPackage.pkg
On UNIX, the default location is /cer2/bin/UpfPackage.pkg
A UpfPGInstructions.htm file is also created but is not currently used in the upgrade.
Steps
1. Ensure that the following 7.0 services or corresponding processes are running by using
Configuration Manager:
Cognos Upfront Data Store (cer2)
Cognos Upfront Administration Service (cer2)

On UNIX, you can also start the 7.0 processes from the /usr/cognos/cer2/bin directory by
running the following scripts:
./start-dbserv
./start-upfadmin
2. Ensure that the following 7.0 service or corresponding process is stopped:

Cognos Upfront Dispatcher (cer2)
On UNIX, you can also stop the following 7.0 process by running this script:
./stop-dispatcher
3. Use the 7.0 Access Manager Administration to ensure that your authentication source is
available and ticket server is running.

4. Open a command window (or a terminal emulator session) and go to the bin directory:
On Windows, the default location is

C:\Program Files\Cognos\cer2\bin.
On UNIX, the default location is

/usr/cognos/cer2/bin.
5. Run the UpfPack utility.

On Windows, use the following syntax:
UpfPack [-un username] [-pw password] [-d location]
[-pn Upfront_package_filename] [-i instructions_filename]
You do not need to include a password. You will be prompted if it is required.

For example,
UpfPack -un Administrator
-d "C:\Program Files\Cognos\packupfront"
On UNIX, use the following syntax:

./run-upfpack [-un username] [-pw password] [-d location]
[-pn Upfront_package_filename] [-i instructions_filename]
For example,
./run-upfpack -un Administrator -d /usr/cognos/packupfront
The UpfPack utility creates the UpfPackage.pkg file and the UpfPGInstructions.htm files in
the bin directory unless you specify a different location by using the optional d parameter.
6. Close the command window or UNIX session.
Unpack the Upfront Data Store

Upgrade the Upfront data store by upgrading your NewsIndex to version 7.1. You must first have
packed the Upfront data store.
Ensure that your Access Manager Runtime uses either the same or a replication of the
namespace as Upfront 7.0.
The following table describes UpfUpgrade parameters.
Parameter
Description
-database
Name of the database to be imported from Upfront

version 7.0 to Upfront version 7.1.
-rollback
The option to restore the 7.0 data store to its

original state if a problem such as a power failure
should occur during the upgrade. The -rollback
option uses the information stored during the
upgrade process in the -d location. When
requesting a rollback, you must specify -database
but not -p or -d.
-p
The file name and location of the Upfront package.

The default location is \cer3\bin\UpfUpgrade.pkg
-un
User name. The user must be an Upfront security

administrator.
-pw
Parameter
Description
-d
A directory location where existing 7.1 data store

information is copied as a backup before the
upgrade is executed. This backup information can
then be used in a -rollback command. A backup is
always made either in the specified location or the
default location. The default location is
Upfront\Backup71Dir.
-h
Help information.
Steps
1. For a staged upgrade, the package file you created in the packing step must be available on
the 7.1 computer and then renamed to UpfUpgrade70.pkg, the new default file name:
On Windows, copy the UpfPackage.pkg file from

\Cognos\cer2\bin to \Cognos\cer3\bin and rename it.
On UNIX, use any ftp utility (binary mode) to transfer the UpfPackage.pkg file from
/usr/cognos/cer2/bin to /usr/cognos/cer3/bin and rename it.
2. Ensure that the following 7.0 services or corresponding processes are stopped by using

On UNIX, you can also stop 7.0 processes from the /usr/cognos/cer2/bin directory by
./stop-dbserv
./stop-dispatcher
./stop-upfadmin
3. Ensure that the following 7.1 service or corresponding process is running:

On UNIX, you can also start the following 7.1 process by running this script:
./start-dbserv
4. Use the 7.1 Access Manager Administration tool to ensure that your authentication source
is available and the ticket server is running.
5. Open a command window or a terminal emulator session and go to the bin directory:


6. Run the Upfront upgrade utility.

UpfUpgrade database [-rollback] [-p package_filename]
[-un username] [-pw password][-d backupdir]
For example,
UpfUpgrade database p UpfUpgrade70.pkg un Administrator
pw mypassword

./run-upfupgrade database [-rollback] [-p package_filename] [-un username] [-pw
password] [-d backupdir]
For example,
./run-upfupgrade database p UpfUpgrade70.pkg un Administrator pw mypassword
Verify That Upfront Security Is Set (optional)

You may want to apply the same security to NewsBoxes that you had in your version 7.0
environment. To do so, turn the security setting on for the NewsIndex by using Upfront
Administration. The upgrade process retains your 7.0 security as assigned, but it does not take
effect unless the NewsIndex security setting is on in the 7.1 product. For information about
setting security, see the Upfront Administration Guide.
Copy Upfront Themes (optional)

You may want to copy your Upfront 7.0 themes if you customized them. For information about
themes in Upfront, see the Upfront Developers Guide.
You must copy your templates, style sheets, and image folder to both the Upfront dispatcher and
the Upfront gateway computers before you can use your custom theme in Upfront 7.1. If the
same computer runs both the Upfront gateway and dispatcher, copy both folders to this single
computer.
Copying the standard themes is not necessary because a new set is provided with Upfront 7.1.
The 7.1 templates include additional properties. We recommend that you schedule some
development time to compare your custom templates with the 7.1 templates and add the new
properties to your custom templates as required.
Steps
1. On your Upfront dispatcher computer, copy your template files.
On Windows, copy the files from

C:\Program Files\Cognos\cer2\templates\upfront
to
C:\Program Files\Cognos\cer3\templates\upfront
On UNIX, use any ftp utility to transfer the templates from

/usr/cognos/cer2/templates/upfront
to
/usr/cognos/cer3/templates/upfront
2. On your Upfront gateway computer, copy your HTML style sheet and image files:
On Windows, copy the files from

C:\Program Files\Cognos\cer2\webcontent\upfront
to
C:\Program Files\Cognos\cer3\webcontent\upfront
On UNIX, use any ftp utility to transfer the files from

/usr/cognos/cer2/webcontent/upfront
to
/usr/cognos/cer3/webcontent/upfront
Verify That Themes Are Assigned to Users (optional)

The upgrade process maintains the assignment of themes to users. Users who were assigned a
custom theme in Upfront 7.0 are assigned the same theme after upgrading. Users who were
assigned the default Upfront 7.0 theme (standard70) are assigned to the default Upfront 7.1
theme (standard71) after the upgrade.
The Web user interface in Upfront 7.1 contains a special NewsItem named User manager
personalize settings in the Administration NewsBox. As an administrator, you can use this
NewsItem to verify or update the assignment of themes to your users.
Verify That the Web Alias Information Is Updated

For instructions see the "Installing to Upgrade" chapter. Ensure that you update the Web Alias
information in Upfront Server Administration.
Upgrading Cognos Query

You must upgrade Upfront before upgrading all Cognos Series 7 Web products (Impromptu Web
Reports, PowerPlay Enterprise Server, Cognos Visualizer, Cognos Query, and Cognos
NoticeCast). For more information, see "Upgrading Upfront".
To upgrade Cognos Query, do the following:
Pack the Cognos Query data store (required) (p. 142).
Unpack the Cognos Query data store (required) (p. 145).
For more information about packing and unpacking, see the Deployment Manager User Guide.
Pack Cognos Query Data (Required)

On the 7.1 administration computer, pack the 7.0 Cognos Query data by running 7.1
Deployment Manager.
The packing process creates a package definition file (.dmd), a pack setting file (.dmi), a
package file (.dmp), and a folder of packlets. You need these files to complete the unpacking
steps.
On Windows, the default locations are
\Cognos\cer3\packages\pkg_def_folder\pkg_folder
\Cognos\cer2\packlets\pkg_def_folder\pkg_folder\CQ1
\Cognos\cer3\packlets\pkg_def_folder\pkg_folder\CQ2
\Cognos\cer3\packlets\pkg_def_folder\pkg_folder\Upfront
Note: CQ1 packlets contain information about the 7.0 data store content and CQ2 packlets
contain information about the 7.1 data store content.
On UNIX, the default locations depend on the interface you use. If you use the graphical user
interface of your Windows administration tool to pack UNIX data, the package files are created
on the Windows computer in the default Windows location. The folder of packlets is created on
the UNIX computer in the following default location:
usr/cognos/cer2/packlets/pkg_def_folder/pkg_folder/CQ1
usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/Upfront
If you use the command line, all files and packlets are created on the UNIX computer in the
following default locations:
usr/cognos/cer2/packages/pkg_def_folder/pkg_folder
usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/Upfront
Steps Common to All Environments

1. Ensure that the following 7.0 and 7.1 services or corresponding processes are running by
using Configuration Manager:
Cognos Query Data Store (cer2)
Cognos Query Dispatcher (cer2)
Cognos Query Server Manager (cer2)

On UNIX, you can also start 7.0 and 7.1 processes from the /usr/cognos/cer2/bin and
/usr/cognos/cer3/bin directories by running the following scripts:
./start-dbserv
./start-dispatcher
./start-upfadmin
./start_cqdbsrv
./start_cqdisp
./start_cqsrvmgr
2. Use the 7.0 and 7.1 Access Manager Administration tool to ensure that your authentication
source is available and the ticket server is running.
Steps to Add Cognos Query to Your 7.1 Configuration

1. Click Start, Programs, Cognos Series 7 Version 2, Tools, and then click Configuration
Manager.
4. If you are doing a staged upgrade, you must add a computer name for the 7.0 dispatcher in
the indicated order.
Right-click All Computers, and then click Add Dispatcher.
In the Dispatcher Name box, type the name of the 7.0 server computer.
In the Explorer window, right-click the 7.0 dispatcher name, and then click Add
Component.
Click Cognos Query, and then click OK.
5. Right-click All Server Groups, and then click Add Server Group.
6. In the Select Server Group Component box, click Cognos Query, and then click OK.
The default server group name is CQ Server Group 1.
7. In the Explorer window, right-click CQ Server Group 1, and then click Add Dispatcher.
8. Replace the 7.1 with the 7.0 Cognos Query dispatcher and port.
9. Select the 7.0 Cognos Query dispatcher computer and type the dispatcher port number.
10. In the Gateway URL box, type the appropriate URL for the server group gateway.
11. In the Web server box, type the appropriate Web server name.
12. Click Actions, and then click Apply Topology.
A message appears informing you that the Server Configuration file (cer3.csx) was
successfully created.
13. In the Components tab, apply properties from the root directory.
Steps to Pack Using the Graphical User Interface on Windows

1. To run the graphical user interface, from the Start menu, click Programs, Cognos EP
Series 7 Version 2, Cognos Server Administration.
2. Click Deployment.
3. In the Roadmap window, click Pack.
4. From the File menu, click New.
5. In the New Package Definition dialog box, type a name for the package definition file, such
as cqpkg.
Note: Do not add a file extension. The extension .dmd is enforced.
6. Accept the default Folder Location, or browse to a location.
Note: Do not include the file name in the path.
The default location is \cer3\installation_location\packages\cqpkg.
7. Type the computer name and port number for the computer where the Upfront dispatcher is
running in the 7.1 environment. Use the format host:port or the IP address in the format IP
address:port.
The default port is 8030.
8. If you want to test the connection, click Test.
9. In the New Package Definition dialog box, click OK.
10. Log on if required, and then click OK.
You must be a member of the root user class in Access Manager.
11. Wait until the message Action completed successfully appears, and then close the dialog
box.
The Package Definition Editor appears. The package definition and its parent folder are
listed in the Explorer window.
12. Under the Package Definition tree, do the following:
Expand Dependent Components, and clear all components except Cognos Query and
Access Manager Security Content.
Leave the NewsIndex components as preselected or clear any NewsBoxes that you do
not want to upgrade.
13. From the File menu, click Save As and then click Pack.
The New Package dialog box appears.
14. Type a name for the package file.
You can use the same name that you gave to the package definition file, such as cqpack.
Note: Do not add a file extension. The extension .dmp is enforced.
15. Click OK.
box.
17. Ensure that the following is true:
The cqpkg folder is located in the Packages folder under cer3 on the 7.1 computer.
The Upfront packlet is located in the Packlets folder under cer3 on the 7.1 computer.
The CQ1 packlet is located in the Packlets folder under cer2 on the 7.0 computer.
The CQ2 packlet is located in the Packlets folder under cer3 on the 7.1 computer.
Steps to Pack Using the Command Line on Windows or UNIX

You can use this packing method if you have only Cognos Query installed; otherwise, your
package file will contain data from all installed components. We recommend you use the
graphical user interface to easily deselect the components you don't want to pack. If using the
command line, see the Deployment Manager User Guide for parameter descriptions and
instructions about excluding data in the package definition file and modifying the packing
policies.
1. Go to the cer3/bin directory, and create a package definition file (.dmd) and a pack setting
file (.dmi) by using the following syntax on the command line:
cdmdefine -cd -d package_def_name [-dl package_def_location] -u
Upfront_server[:port]
For example, on Windows or UNIX, the following command uses default locations:
cdmdefine -cd -d cqpkg -u UpfServ:8030
If a port number is not specified, the default port for the 7.1 Upfront server 8030 is assumed.
Note: You must be a member of the root user class in Access Manager.
A message indicates that the files were created. In this example, the cqpkg.dmd and
cqpkg.dmi files are in the C:\Program Files\Cognos\cer3\packages\cqpkg folder on
Windows or the /usr/cognos/cer3/packages/cqpkg folder on UNIX.
3. If you want to clear any Newsboxes or components, or change the packlets location, edit the
.dmi file in a text editor.
4. If you edited the .dmi file in the previous step to modify the package definition file with the
pack setting file, you must type the following command:
cdmdefine -md -d package_def_name [-dl ackage_def_location]
cdmdefine -md -d cqpkg
5. To pack the data and to create the package file (.dmp), type the following:
cdmpack -d package_def_name [-dl package_def_location] -p packagename [-pl
package_location]
cdmpack -d cqpkg -p cqpkg
In this example, the cqpkg.dmp file is created in the C:\Program

Files\Cognos\cer3\packages\cqpkg\cqpkg folder on Windows or the
/usr/cognos/cer3/packages/cqpkg/cqpkg folder on UNIX.
6. Log on again if prompted.
The components to be packed are listed.
7. Respond to the prompt to continue.
You will find the package and packlet files in the default locations or the locations you
specified.
Unpack Cognos Query Data (Required)

On your 7.1 administration computer, unpack the Cognos Query data by running the Cognos
Series 7 Version 2 Deployment Manager to load the package file (.dmp) you created when you
packed the 7.0 Cognos Query data.
Note for UNIX Only

If your 7.1 environment was set up under a different user than your 7.0 environment, you must
ensure that you have full access privileges for the package and packlets in the 7.0 and 7.1
environments. Otherwise, you will not be able to copy the files to the cer3 location.

1. For a staged upgrade, ensure that the files and packlets you created when packing the
Cognos Query data are available on the 7.1 computer.
2. Copy the contents of the packlets folder from
\Cognos\cer2\packlets\pkg_def_folder\pkg_folder\CQ1 to
\Cognos\cer3\packlets\pkg_def_folder\pkg_folder
3. On UNIX, use any FTP utility in binary mode to transfer files.
If you used the Deployment Manager graphical user interface for Deployment Manager on a
Windows computer when you packed the Cognos Query data, transfer the .dmd, .dmi, and
.dmp files from the default cer2 location on the Windows computer to the cer3 location on
the UNIX computer.
If you used the command line when you packed the Cognos Query data, transfer the files:
from the default location /usr/cognos/cer2/packages/pkg_def_folder

to /usr/cognos/cer3/packages/pkg_def_folder
from /usr/cognos/cer2/packages/pkg_def_folder/pkg_folder
to /usr/cognos/cer3/packages/pkg_def_folder/pkg_folder.
In either case, transfer the contents of the packlets folder from
/usr/cognos/cer2/packlets/pkg_def_folder/pkg_folder/CQ1 to
/usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/

On UNIX, you can also start 7.1 processes from the /usr/cognos/cer3/bin directory by
./start-dbserv
./start-dispatcher
./start-upfadmin
./start_cqdbsrv
./start_cqdisp
./start_cqsrvmgr
5. To ensure that your authentication source is available and the ticket server is running, use
the 7.1 Access Manager Administration tool.
Steps to Unpack Using the Graphical User Interface on Windows

1. Reset the 7.1 dispatchers at the at the end of the upgrade process and distribute the
updated cer3.csx to all 7.1 computers in the topology.
2. To run the graphical user interface, from the Start menu, click Programs, Cognos Series 7
Version 2, Cognos Server Administration.
4. In the left frame of the Deployment Manager dialog box, click Unpack and then click Open.
An unpacking report is generated and opened in the work area. Another report named
Unpack.dmr is generated and stored in the folder where the package is located.
5. In the Open dialog box, locate the package file (.dmp), such as C:\Program
Files\Cognos\cer3\packages\cq\cqpkg.dmp, and click Open.
6. In the Package Editor, click Select Target.

7. In the Select Target Environment dialog box, type the name of the Upfront dispatcher
computer and port number in the format host:port, for the computer where the Upfront
server is running in the 7.1 environment.
Tip: You can specify the IP address instead of host:port
8. Click Test and then click Close.
9. In the Package Editor, expand the Access Manager component and verify that the correct
namespace is listed.
10. Expand the NewsIndex component and verify the NewsBoxes.
11. In the Package Editor, click Edit Mappings.
If this button is not visible, click the >> symbol.
12. In the Mapping Editor, select <All> in the list and then click Auto Fill.
If you did not previously enter the connection information for the Upfront server, you are
prompted for this information now.
13. Log on to your authentication source in response to the prompt.
14. When the Auto Fill process prompts you to Replace current target values, click Yes and
then click Close.
Some of the settings may not be mapped automatically. You must map these settings.
15. If required, change the path information for the packlets, such as change cer2 to cer3, and
the gateway and Deployment Server information in the Target column.
16. Ensure that the 7.1 Deployment Server contains valid information on the 7.1 Deployment
Server for both CQ1 and CQ2.
17. Click Save and then, in the Mapping Editor, click Close.
18. In the Package Editor, click Validate.
Any errors and warnings produced by the validation operation appear in the Results
window. For information about any errors, see the Deployment Manager User Guide.
19. If no errors appear, click Unpack.
20. To close the Deployment Manager dialog box, click Close and then click Close in the
Package Editor.
Steps to Unpack Using the Command Line on Windows or UNIX

1. Go to the cer3/bin directory and create an unpack setting file (.dmu) by typing the following
command on the command line:
cdmdefine -cp -d definition -p packagename [-pl package_location] -u
cdmdefine -cp -d cqpack -p cqpkg -u UpfServ:8030
If a port number is not specified, the default port for the Upfront server 8030 is assumed.
In this example, the cqpkg.dmu file will be created in the C:\Program
Files\Cognos\cer3\packages\cqpkg\cqpkg folder on Windows or the
/usr/cognos/cer3/packages/cqpkg/cqpkg folder on UNIX.
2. Open the unpack setting file (.dmu) in a text editor to change the mappings.
For each location identified in the unpack settings file, type an appropriate value for the
TargetValue attribute and save the file.
3. To modify the package file with the unpack setting file, use the following syntax :
cdmdefine -mp -d definition -p packagename [-pl package_location]
cdmdefine -mp -d cqpack -p cqpkg
4. To verify the package, use the following syntax:

cdmunpack -v -d definition -p packagename [-pl package_location] -u
cdmunpack -v -d cqpack -p cqpkg -u UpfServ:8030
One unpacking report is created in the directory where the package is located.

5. To unpack the package, use the following syntax:
cdmunpack -d definition -p packagename [-pl package_location] -u
cdmunpack -d cqpack -p cqpkg -u UpfServ:8030
A second unpacking report is created.

You can now update the gateway URLs in Upfront for Cognos Query (p. 163). You can also test
Cognos Query by publishing a report to Upfront. For more information, see the Installation
Upgrading Impromptu Web Reports

You must upgrade Upfront before upgrading all Cognos Series 7 Web products.
The Impromptu Web Reports server group and the Upfront server group must have the same
name in the 7.1 environment as in your 7.0 environment because these names are stored in the
Impromptu Web Reports data store. This configuration was required when you upgraded the
software. For information about multiple server groups, see the Configuration Manager User
Guide.
To upgrade Impromptu Web Reports do the following:
Pack the Impromptu Web Reports data store by using dsdump (required) (p. 148).
Unpack the Impromptu Web Reports data store by using dsload (required) (p. 149).
Pack the Impromptu Web Reports Data Store (Required)

On the 7.0 computer where Impromptu Web Reports server is running, pack the Impromptu
Web Reports data by running the dsdump utility.
The packing process creates a single .xml file you later use to upgrade the Impromptu Web
Reports data store.
The following table describes the dsdump parameters.
Parameter
Description
-db
The location and file name for the database to be

dumped.
If the Impromptu Web Reports database is on a
separate computer from the Impromptu Web
Reports dispatcher, run the dsdump command
on the dispatcher computer using the following
syntax for this parameter:
-db dbcomputer:dblocation
-fn
The file name for the output .xml file.
-v
The option to generate trace messages. The

levels are
0 - display error information
1 - display major information
2 - display minor information
all - display all information (recommended)
-l
The option to generate a log file with the supplied

name.
Note: The letter l, not the number 1 is used for
this parameter.
Steps
1. Stop and restart ObjectStore Server R6.0 (osserver) to ensure that any transactions still
cached in memory are saved in the data store.
2. Start ObjectStore Cache Manager R6.0 (oscmgr6).
On UNIX, your database administrator must stop and start the service if you do not have
root privileges.
For information about starting ObjectStore services, see the "Testing the Installation"
chapter.
3. Ensure that the following 7.0 services or corresponding processes are stopped using
Configuration Manager.
Cognos Impromptu Web Reports Service Manager (cer2)
Cognos Communication Service (cer2)

On UNIX, you can also stop the 7.0 services from the /usr/cognos/cer2/bin directory by
running the following script:
./stop-iwr


6. On UNIX, ensure that you are in a Bourne shell before you set up your environment by
typing
sh
Type the following command to source the setup file:

. ./iwrsetup.sh
7. Run the dsdump utility:
dsdump db [dbcomputer:]dblocation -fn xml_filename [-v trace level (0-3,all)] [l

log_filename]
The utility dumps the contents of the Impromptu Web Reports database files into a single
transportable .xml file in the bin directory.
For example, when the Impromptu Web Reports database is on the local computer:
dsdump -db "C:\Program Files\Cognos\cer2\iwr\database\iwr70.db" -fn myoutput.xml
v all l logfile.txt
For example, when the Impromptu Web Reports database is on a remote computer (mars):
dsdump -db "mars:C:\Program Files\Cognos\cer2\iwr\database\iwr70.db" -fn
myoutput.xml
v all l logfile.txt
./dsdump db [dbcomputer:]dblocation -fn xml_filename [-v trace level (0-3,all)] [l

log_filename]
For example, if the Impromptu Web Reports database is on the local computer:
./dsdump -db /usr/cognos/cer2/iwr/database/iwr70.db -fn myoutput.xml v all l
logfile.txt
For example, if the Impromptu Web Reports database is on a remote computer (mars):
./dsdump -db mars:/usr/cognos/cer2/iwr/database/iwr70.db -fn myoutput.xml v all l
logfile.txt
Unpack the Impromptu Web Reports Data Store (Required)

On your 7.1 dispatcher computer, run the dsload utility to unpack the Impromptu Web Reports
data store.

The following table describes the dsload parameters.
Parameter
Description
-fn
The file name of the portable XML file

generated by the dsdump utility.
-un
Username.
-pw

Mandatory only if a password has been
defined for the username.
-v
Causes the dsload utility to generate trace

messages. The levels are
0 - display error information
1 - display major information
2 - display minor information
all - display all information (recommended)
-db
Specifies the source database location and

file name.
If the IWR database is on a separate
computer from the IWR dispatcher, run the
dsload command on the dispatcher
computer using the following syntax for this
parameter:
-db dbcomputer:dblocation
Your 7.1 computer must be configured to use the same authentication namespace as the 7.0
computer you used when you ran dsdump. The namespace must also include the same set of
users and classes.
Steps
1. For a staged upgrade, the files you created in the packing step and the files in the report
store directory must be available on the 7.1 computer:
On Windows, copy the xml file from

\cognos\cer2\bin to \cognos\cer3\bin. Also, copy the contents of the report store from
the 7.0 source to the 7.1 target.
On UNIX, use any ftp utility to transfer the .xml file from
/usr/cognos/cer2/bin to /usr/cognos/cer3/bin and the contents of the report store from its
source on 7.0 to its target in 7.1.
Note: If you are upgrading from Windows to UNIX, and the report set directories under the
Report Store directory use mixed case or uppercase, you must change the names to
lowercase. Do not rename the report files (.imr). Rename only the report set directories that
contain the files.
2. Use Configuration Manger to ensure that the following 7.1 service or corresponding process
is stopped:
Cognos Impromptu Web Reports Service Manager (cer3)
On UNIX, you can also stop the 7.1 process from the /usr/cognos/cer3/bin directory by
running the following script:
./stop-iwr
3. Ensure that ObjectStore Server R6.0 (osserver) and ObjectStore Cache Manager
(oscmgr6) are running.
For information about starting ObjectStore services, see the "Testing the Installation"
chapter.

4. Use Configuration Manager to ensure that the following 7.1 services or corresponding
processes are running:

On UNIX you can also start the 7.1 processes by running these scripts:
./start-dbserv
./start-dispatcher
./start-upfadmin
available and the ticket server is running.

C:\ Program Files\Cognos\cer3\bin.
On UNIX, the default location is /usr/cognos/cer3/bin.
typing
sh
Type the following command to source the setup file:

. ./iwrsetup.sh
8. Run the dsload utility.
dsload -fn xml_filename -un username -pw password

[-v trace level (0-3,all)] -db [dbcomputer:]dblocation
dsload -fn myoutput.xml -un Administrator -pw mypassword
-db "C:\Program Files\Cognos\cer3\iwr\database\iwr71.db"
dsload -fn myoutput.xml -un Administrator -pw mypassword
-db "mars:C:\Program Files\Cognos\cer3\iwr\database\iwr71.db"
./dsload -fn xml_filename -un username -pw password

[-v trace level (0-3,all)] -db [dbcomputer:]dblocation
./dsload -fn myoutput.xml -un Administrator -pw mypassword
-db /usr/cognos/cer3/iwr/database/iwr71.db
./dsload -fn myoutput.xml -un Administrator -pw mypassword
-db mars:/usr/cognos/cer3/iwr/database/iwr71.db
The utility reads the .xml file and loads the Impromptu Web Reports and Upfront data
stores.On Windows, start the 7.1 Cognos Impromptu Web Reports Service Manager
Service (cer3) and verify that the service is set to run as a user.
9. On UNIX, go to the /usr/cognos/cer3/bin directory to start the following 7.1 process:
./start-iwr

10. If the location of the report store for your 7.1 environment is different from your 7.0
environment, update the report store location in the Impromptu Web Reports 7.1 database.
You can do this for each report set individually or for all report sets at once.
On Windows, to update the location of one report set at a time, use the following syntax:
iwrconfig -cmd movereportset reportsetname newlocation
On UNIX, to update the location of one report set at a time, use the following syntax:
./iwrconfig -cmd movereportset reportsetname newlocation
On Windows, to update the location of all report sets at once use the following syntax:
iwrconfig -cmd moveAllReportSet newlocation
On UNIX, to update the location of all report sets at once use the following syntax:
./iwrconfig -cmd moveAllReportSet newlocation
Tip: For reference purposes, you can create a file of all report set names and their locations
by typing the following on the command line. You can then use the contents of the output file
as a starting point to build a script.
For example, if you are upgrading from Windows to UNIX, you must reset locations for all
your report sets using lowercase UNIX path names:
iwrconfig -cmd dumpAllreportset >outputfile
Here is an example:
iwrconfig -cmd dumpAllresportset >reportset_loc.txt
11. If you are upgrading across platforms (from Windows to UNIX or from UNIX to Windows),
recreate any hotfiles for your new platform by running your reports in your new Impromptu
Web Reports 7.1 environment.
You can now update the gateway URLs in Upfront for the Impromptu Web Reports server
(p. 163). You can also test Impromptu Web Reports by publishing a report to Upfront. For more
information, see the Installation Testing and Samples Setup Guide.Upgrading PowerPlay
Enterprise Server
You must first upgrade Upfront for all Cognos Series 7 Web products.
If you are using Cognos PowerPlay Enterprise Server, you must upgrade PowerPlay Enterprise
Server first and then upgrade Cognos Visualizer. If these products are not upgraded in the
correct order, Cognos Visualizer may not open remote cubes.
To upgrade PowerPlay Enterprise Server, you must
copy the PPSRoot directory
secure the server
upgrade the PPES metadata
Copy the 7.0 PPSRoot Directory

Objects in PowerPlay Enterprise Server are stored as a hierarchy of files under the PPSRoot
directory. To move your metadata to PowerPlay Enterprise Server 7.1, you must copy this
hierarchy of files.
If additional reports and cubes are not in the PPSRoot folder, you must copy them from the 7.0
computer to the 7.1 computer. You can create the same folder on your 7.1 computer or add
these reports to the PPSRoot folder. All reports and cubes that are drill-through targets must be
in the PPSRoot folder.
Steps
1. For a staged upgrade, you must first copy the contents of the PPSRoot directory and any
additional reports and cubes from the 7.0 computer to the 7.1 computer.
2. Open a command window or a terminal emulator session and go to the version 7.1 ppserver
directory:

C:\Program Files\Cognos\cer3\ppserver.

/usr/cognos/cer3/ppserver.
3. Rename the PPSRoot directory to PPSRoot_backup.


4. Copy the contents that you need from the version 7.0 PPSRoot directory to the 7.1
PPSRoot directory:
On Windows, the default version 7.0 location is

C:\Program Files\Cognos\cer2\ppserver\PPSRoot.
On UNIX, the default version 7.0 location is /usr/cognos/cer2/ppserver/PPSRoot.
Secure PowerPlay Enterprise Server

You must use security if you plan to use PowerPlay with Upfront. If you used security in
PowerPlay Enterprise Server Administration in 7.0, you should set security again in version 7.1
using the same or replication of the same namespace used in 7.0.
Steps
1. Ensure that the following 7.1 service or corresponding process is running by using
Cognos PowerPlay Enterprise Server (cer3)
On UNIX, you can also start the 7.1 process from the /usr/cognos/cer3/bin directory by
running this script:
./start_ppsrv.sh
3. Start the PowerPlay Enterprise Server Administration tool.
4. Secure the server by using the appropriate directory server and namespace.
Upgrade PowerPlay Metadata

You must secure PowerPlay Enterprise Server before running the PowerPlay upgrade utility
ppserver to upgrade the metadata.
Upgrading the PowerPlay metadata involves
updating the cube and report location information by updating .cfx files
updating the server information by updating .ppx files.
The process is similar regardless of platform. However, for an upgrade on Windows, you run
ppserver directly using the -m parameter. For an upgrade on UNIX, you run a script
upgrade_ppsrv.sh that invokes ppserver.
You must update the XML-based .cfx and .ppx files. The configuration files (.cfx) in the PPSRoot
directory contain entries that define the location of the published objects (folders, cubes, and
reports). The associated files (.ppx) contain server information, such as server name and port
number. The ppserver - m [-un username] [-pw password] [searchFor replaceWith] parameter
substitutes the 7.0_report_cube_location for the 7.1_report_cube_location in these entries.
You must run the ppserver command to replace all strings in the .cfx files in each different
location you use for your reports and cubes. If the cubes and reports are kept outside the default
folder structure, substitute the folder name as appropriate.
If cer3 and cer2 are installed at the same level under the same directory structure, ppserver
cer2 cer3 is sufficient. If cer2 and cer3 are located on different drives, you must specify the full
path locations. You must enclose the path in double quotation marks if it includes spaces.
Instead of having to escape the Windows backslash character on UNIX, we recommend that
you use forward slashes for all paths when upgrading the PowerPlay metadata. For example, in
a Windows-to-UNIX upgrade, when defining a cer2 Windows path on a UNIX computer, you can
use forward slashes: "D:/Program Files/Cognos/cer2"

The following table describes the ppserver parameters for Windows and UNIX.
Parameter
Description
-d
Runs PPES services.
-k
Stops PPES services.
-v
Shows PPES version information.
-im
Sets PPES services to start manually.
-i
Sets PPES services to start automatically.
-r
Checks whether PPES service is installed.
-u
Uninstalls PPES service.
[-un username]
[-pw password]
[searchFor
replaceWith]
Migrates PPSRoot hierarchy to the current

version of Upfront; replaces 'searchFor' string with
'replaceWith' in every cfx file.
-m
Use only with ppserver on Windows with the

[searchFor replaceWith] parameter.
-un
Specifies the Username.
-pw
Specifies the Password.
-vm
Verifies the results from the migration to the

current version of Upfront.
-ppx
Updates server name and port number in all ppx

files located in the PPSRoot directory, including
MountAt folders and collections.
Shows parameter usage information.
7.0_report_cube_l Specifies the path to the PPSRoot folder structure

ocation
under cer2 or any folder that contains the version
7.0 reports and cubes.
The string cer2 can be used if the folder structure
will remain identical for version 7.0 and version
7.1.
7.1_report_cube_l Specifies the path to the PPSRoot folder structure
ocation
under cer3 or any folder that will contain the
version 7.1 reports and cubes.
The string cer3 can be used if the folder structure
remains identical for version 7.0 and version 7.1.
Steps for Windows

1. For a staged upgrade, you must first copy your 7.0 PowerPlay cubes (.mdc files) to the 7.1
computer.
2. Ensure that the following 7.1 services are running by using Configuration Manager:

3. Ensure that the following 7.1 service is stopped:
5. Open a command window or a terminal emulator session and go to the 7.1 bin directory:

6. Run the upgrade utility to update the cube and report location information in the cfx files by
typing the following command:
ppserver -m -un userid -pw password 7.0_report_cube_location
7.1_report_cube_location
For example, for a Windows-to-Windows upgrade:

ppserver -m -un Administrator -pw mypassword cer2 cer3

ppserver -m -un Administrator -pw mypassword "D:\Program Files\Cognos\cer2"
"e:\Series7v2\cer3"
You must run this utility in each location that contains your reports and cubes.
You can confirm the locations of your reports and cubes in the .cfx file.
Tip: The ppserver utility accepts forward slashes (/) even on a Windows.
7. Run the upgrade utility to update the server information in the .ppx files by typing the
following command:
ppserver -m -un userid -pw password -ppx

ppserver -m -un Administrator -pw mypassword -ppx
The PowerPlay Enterprise Server 7.0 server name and port in the .ppx files are replaced by
the server name and port used for PowerPlay Enterprise Server 7.1.
You only need to run this utility once.
8. Use Configuration Manager to start the Cognos PowerPlay Enterprise Server (cer3) service
on the 7.1 Windows computer.
Steps for UNIX

1. For a staged upgrade, use an FTP utility (binary mode) to transfer your 7.0 PowerPlay
cubes (.mdc files) and reports (.ppx files) to the 7.1 computer.
2. Ensure that the corresponding 7.1 processes for the following services are running by using
the Configuration Manager command line:

You can also start the 7.1 processes from the /usr/cognos/cer3/bin directory by running the
following scripts:
./start-dbserv
./start-dispatcher
./start-upfadmin
3. Ensure that the corresponding process for this 7.1 service is stopped:
You can also stop this 7.1 process by running the following script:
./stop_ppsrv.sh
5. In the 7.1 bin directory, ensure that you are in a Bourne shell by typing
sh

6. Update the .cfx files by running the upgrade utility to update the cube and report location
information.
You must run this command several times if your reports and cubes are in multiple
locations.
You can confirm the locations of your reports and cubes in the .cfx file.
Type the following command:
./upgrade_ppsrv.sh -un userid -pw password 7.0_report_cube_location
7.1_report_cube_location
For example, for a UNIX-to-UNIX upgrade:

./upgrade_ppsrv.sh -un Administrator -pw mypassword /usr/cognos/cer2 usr/cognos/cer3
For example, for a Windows-to-UNIX upgrade:

./upgrade_ppsrv.sh -un Administrator -pw mypassword "D:/Program Files/Cognos/cer2"
/usr/cognos/cer3
7. Update the .ppx files by running the upgrade utility to update the server information by
typing the following command. You will only need to run this command once:
./upgrade_ppsrv.sh -ppx -un userid -pw password
For example, for a UNIX-to-UNIX upgrade:

./upgrade_ppsrv.sh -un Administrator -pw mypassword -ppx
For example, for a Windows-to-UNIX upgrade:

./upgrade_ppsrv.sh -un Administrator -pw mypassword -ppx
The PowerPlay Enterprise Server 7.0 server name and port in the .ppx files are replaced by
the server name and port used for PowerPlay Enterprise Server 7.1.
8. Start the Cognos PowerPlay Enterprise Server (cer3) service.
9. Run the following script from the /usr/cognos/cer3/bin directory:./start_ppsrv.sh
Complete the Upgrade

1. Ensure that you update the gateway URLs in Upfront for the PowerPlay Enterprise Server
(p. 163).
2. If required, update the Impromptu Web Reports drill mappings. You can upgrade the
Impromptu Web Reports drill mappings using the PowerPlay Enterprise Server
Administration tool.
3. Test PowerPlay Enterprise Server by publishing a cube to Upfront. For more information
about testing, see the Installation Testing and Samples Setup Guide.
You can continue to use cubes built with Series 7 PowerPlay Transformer Edition. To benefit
from the new features in Series 7 Version 2 PowerPlay Transformer Edition, you may want to
upgrade your cubes. For more information, see the "Upgrading Client Data" chapter.
Upgrading Cognos Visualizer

You can upgrade Cognos Visualizer from version 7.0 to 7.1 by using Cognos Deployment
Manager or the command line interface.
If you want to upgrade items published to Upfront, use Cognos Deployment Manager.
If you want to upgrade all items on the Visualizer Web Server, use the command line interface.
For more information about upgrading Cognos Visualizer using the command line interface, see
"Alternative Upgrades".
You must upgrade Upfront before upgrading all Cognos Series 7 Web products.
Before you upgrade Cognos Visualizer, do the following:
Ensure that your Cognos services are running (required) (p. 157)
Add Cognos Visualizer 7.0 to your 7.1 configuration (required) (p. 157)
To upgrade Cognos Visualizer, use 7.1 Deployment Manager to do the following:
Pack the Cognos Visualizer 7.0 data (required) on Windows (p. 157).
Unpack the Cognos Visualizer 7.0 data (required) on UNIX (p. 160).
For more information, see the chapters about packing and unpacking in the Deployment
Manager User Guide.
Pack Cognos Visualizer Data (Required)

On the 7.1 administration computer, pack the Cognos Visualizer data by running 7.1 Cognos
Deployment Manager.
The packing process creates a package definition file (.dmd), a pack setting file (.dmi), a
package file (.dmp), and two packlets. You need these files to complete the unpacking steps.
\Cognos\cer2\packlets\pkg_def_folder\pkg_folder\viz
\Cognos\cer3\packlets\pkd_def_folder\pkg_folder\upfront
On UNIX, the default locations depend on the interface you use. If you use the graphical user
interface of your Windows administration tool to pack UNIX data, the package files are created
on the Windows computer in the default Windows location. The packlets are created on the
UNIX computer in the following default locations:
usr/cognos/cer2/packlets/pkg_def_folder/pkg_folder/viz
usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/upfront
usr/cognos/cer2/packlets/pkg_def_folder/pkg_folder/viz
You can use the command line interface if you have only Cognos Visualizer installed. Otherwise,
your package file will contain data from all installed components. For information about
parameter description and instructions about excluding data in the package definition file, see
the Deployment Manager User Guide. We recommend that you use the graphical user interface
to easily clear the components you do not want to pack.
Steps to Ensure That Your Cognos Services Are Running

1. To ensure that the following 7.0 and 7.1 services or corresponding processes are running,
use Configuration Manager:
Cognos Visualizer Web Edition (cer2)

On UNIX, you can also start 7.0 and 7.1 processes from the /usr/cognos/cer2/bin and
/usr/cognos/cer3/bin directory by running the following scripts:
./start-dbserv
./start-dispatcher
./start-upfadmin
./start_viz.sh
2. Ensure that your authentication source is available and the ticket server is running using the
7.0 and 7.1 Access Manager Administration tool.
Steps to Add Cognos Visualizer 7.0 to Your 7.1 Configuration

1. Click Start, Programs, Cognos Series 7 Version 2, Tools, and then click Configuration
Manager.

4. If you are doing a staged upgrade, add a computer name for the 7.0 dispatcher in the
indicated order.
Right-click All Computers, and then click Add Dispatcher.
In the Dispatcher Name box, type the name of the 7.0 server computer.
In the Explorer window, right-click the 7.0 dispatcher name, and then click Add
Component.
Click Cognos Visualizer, and then click OK.
5. Right-click All Server Groups, and then click Add Server Group.
6. In the Select Server Group Component box, click Cognos Visualizer, and then click OK.
The default server group name is Visualizer Server Group 1.
7. In the Explorer window, right-click Visualizer Server Group 1, and then click Add
Dispatcher.
8. Select the 7.0 Visualizer dispatcher computer and type the dispatchers port number.
9. In the Gateway URL box, type the appropriate URL for the server group gateway.
10. In the Web server box, type the appropriate Web server name.
11. Click Actions, and then click Apply Topology.
A message appears informing you that the Server Configuration file (cer3.csx) was
successfully created.
12. In the Components tab, apply properties from the root directory.
14. Do one of the following:
If you are doing a staged upgrade, create a directory for visualizations on the 7.1
computer that is identical to the directory structure on the 7.0 computer where the
visualizations are located.
If you are doing an in-place upgrade, we recommend that you back up your
visualizations before upgrading them to 7.1.

1. Click the Start menu, Programs, Cognos Series 7 Version 2, Cognos Server
Administration.
5. In the New Package Definition dialog box, type a name for the package definition file, such
as vizpkg.
Tip: Do not add a file extension. The extension .dmd is enforced.
Do not include the file name in the path.
Tip: The default location is installation_location\packages\vizpkg
running in the 7.1 environment. Use the format host:port or the IP address in the format
IP address:port.
8. If you want to test the connection, click Test, and then click OK.
Tip: You must be a member of the root user class in Access Manager.
box.
The Package Definition Editor appears. The package definition and its parent folder are
listed in the Explorer window.

Expand Dependent Components, and exclude all components except CogViz and
Leave the NewsIndex components as preselected or exclude any NewsBoxes that you
do not want to upgrade.
12. From the File menu, click Save, and then click Pack.
13. Type a name for the package file. You can use the same name that you gave to the package
definition file, such as vizpkg.
Note: Do not add a file extension. The extension .dmp is enforced.
14. Click OK.
box.
16. Ensure that the following is true:
The vizpkg folder is located in the Packages folder under cer3 on the 7.1 computer.
The Upfront packlet is located in the Packlets folder under cer3 on the 7.1 computer.
The viz packlet is located in the Packlets folder under cer2 on the 7.0 computer.

typing
sh
2. To source the setup file, type the following command:
. ./setcdmvars.sh
file (.dmi) by using the following syntax on the command line:
cdmdefine -cd -d vizpkg -u UpfServ:8030
If a port number is not specified, the default port for the 7.1 Upfront server, 8030, is
assumed.
A message indicates that the files were created. In this example, the vizpkg.dmd and
vizpkg.dmi files are located in C:\Program Files\Cognos\cer3\packages\vizpkg on Windows
or in /usr/cognos/cer3/packages/vizpkg on UNIX.
5. If you want to deselect any Newsboxes or components, or change the packlets location, edit
the .dmi file in a text editor and then use the following syntax to modify the package
definition file with the pack setting file:
cdmdefine -md -d package_def_name [-dl package_def_location]
cdmdefine -md -d vizpkg
6. Use the following syntax to pack the data and to create the package file (.dmp):
package_location]
cdmpack -d vizpkg -p vizpkg
In this example, the vizpkg.dmp file is created in C:\Program

Files\Cognos\cer3\packages\vizpkg\vizpkg on Windows or in
/usr/cognos/cer3/packages/vizpkg/vizpkg on UNIX.
7. If prompted, log on again.

8. To continue, respond to the prompt.
Unpack Cognos Visualizer Data (Required)

On your 7.1 administration computer, unpack the Cognos Visualizer data by running Cognos
Series 7 Version 2 Deployment Manager to load the package file (.dmp) you created when you
packed the Cognos Visualizer data.
Note for UNIX Only

If your 7.1 environment was set up under a different user than your 7.0 environment, you must
ensure that you have full access privileges for the package and packlets in the 7.1 environment.
Otherwise, you will not be able to copy the files to the cer3 location.

1. If you are doing a staged upgrade, ensure that the files and packlets you created when
packing the Cognos Visualizer data are available on the 7.1 computer.
On Windows, copy the .dmd and .dmi files from

\Cognos\cer2\packlets\pkg_def_folder\pkg_folder\viz to
\Cognos\cer3\packlets\pkg_def_folder\pkg_folder\viz
On UNIX, use any FTP utility, in binary mode, to transfer files.

If you used the graphical user interface for Deployment Manager on a Windows computer
when you packed the Cognos Visualizer data, transfer the .dmd, .dmi, and .dmp files from
the default cer2 location on the Windows computer to the cer3 location on the UNIX
computer.
If you used the command line when you packed the Cognos Visualizer data, copy the files
on the UNIX computer as follows:
/usr/cognos/cer2/packlets/pkg_def_folder/pkg_folder/viz to
/usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/viz

./start-dbserv
./start-dispatcher
./start-upfadmin
./start_viz.sh
3. To ensure that your authentication source is available and the ticket server is running, use
the 7.1 Access Manager Administration tool.

1. Click Start, Programs, Cognos Series 7 Version 2, Cognos Server Administration.
3. In the Roadmap window, click Unpack, and then click Open.
4. Locate the package file (.dmp), such as C:\Program
Files\Cognos\cer3\packages\viz\vizpkg.dmp, and then click Open.
running in the 7.1 environment. Use the format host:port or the IP address in the format
IP address:port.
7. Click Test, and then click Close.

8. In the Package Editor, expand the Access Manager component and ensure that the
correct namespace is listed. Also, expand the NewsIndex component and check the
NewsBoxes.
Tip: If this button is not visible, click the >> symbol.
10. In the Mapping Editor, click <All> in the list, and then click Auto Fill.
11. When prompted, log on to your authentication source.
12. When the Auto Fill process prompts you to Replace current target values, click Yes, and
then click Close.
13. If required, change the path information for the packlets, such as change cer2 to cer3,
visualization location, gateways, and servers in the Target column.
14. Ensure that the 7.1 Deployment Server box contains valid information about the 7.1
Cognos Visualizer server.
window. For information about any errors, see the Deployment Manager User Guide.
18. Click Close to close the Deployment Manager dialog box, and then click Close in the
Package Editor.
You can now update the gateway URLs in Upfront for Cognos Visualizer (p. 163).
You can also test Cognos Visualizer by publishing a report to Upfront. For more information, see
the Installation Testing and Samples Setup Guide.

1. Go to the cer3/bin directory and create an unpack setting file (.dmu) by using the following
syntax on the command line:
cdmdefine -cp -d definition -p packagename [-pl package_location] -u
cdmdefine -cp -d vizpkg -p vizpkg -u UpfServ:8030
If a port number is not specified, the default port for the Upfront server, 8030, is assumed.
In this example, the vizpkg.dmu file will be created in C:\Program
Files\Cognos\cer3\packages\vizpkg\vizpkg on Windows or
/usr/cognos/cer3/packages/vizpkg/vizpkg on UNIX.
4. For each location identified in the unpack settings file, type an appropriate value for the
typing
sh
6. To source the setup file, type the following command:
. ./setcdmvars.sh
7. To modify the package file using the unpack setting file, use the following syntax:
For example, on Windows or UNIX, the following command uses this location:
cdmdefine -mp -d vizkg -p vizpkg

8. To check the package, use the following syntax:
cdmunpack -v -d vizpkg -p vizpkg -u UpfServ:8030
9. To unpack the package, use the following syntax:
cdmunpack -d vizpkg -p vizpkg -u UpfServ:8030

You can now update the gateway URLs in Upfront for Cognos Visualizer (p. 163).
You can also test Cognos Visualizer by publishing a report to Upfront. For more information, see
the Installation Testing and Samples Setup Guide.
Upgrading Cognos NoticeCast

This section assumes that you completed the procedures for configuring Cognos NoticeCast
after you installed the components. During the configuration, your NoticeCast 7.0 data store was
upgraded to 7.1.
You also completed the installation, configuration, and upgrade of all the other Cognos Web
products. This ensures that the current server configuration file (.csx) contains the most
up-to-date information about the location of all Cognos product gateways and dispatchers.
To complete the upgrade of Cognos NoticeCast do the following:
Update the gateway URLs for all the associated servers in NoticeCast Server Administration
(required).
Update the JDBC driver path (required only for upgrades from Cognos Series 7 RTM and
MR1 versions).
Update the gateway URLs in Upfront for NoticeCast agents (required).
Update the Gateway URLs for All Associated Servers (Required)

You must update the gateway URL information in the Cognos NoticeCast data store so that
Cognos NoticeCast contacts the apporpriate server when an agent runs. The URLs are still
pointing to the gateways used with your previous version.
Steps
Administration, and then click Alerts and Notifications.
2. From the Tools menu, click Maintain URLs.
3. Click the URLs tab.
The left pane shows the gateway URLs as they are currently defined in the NoticeCast data
store. The right pane shows the gateway URLs defined for each server group in the Cognos
server configuration file (cer3.csx).
Tip: If you are running Cognos NoticeCast Server Administration from a client computer, the
cer3.csx file may be missing. In this case the list of gateway URLs on the right is empty.
Copy the cer3.csx file from the Cognos NoticeCast Server computer to the Cognos
NoticeCast Administration computer.
4. In the URLs in database list, click the URL to be replaced in the database.
The selected URL appears in the URL to be replaced box.
5. If any characters appended to the path information do not typically belong in a gateway
URL, edit the URL to remove them.
For example, if the URL shows /cognos/cgi-bin/cqcgi.exe/script/reportframe.iws, change it
to /cognos/cgi-bin/cqcgi.exe

6. In the URLs from .csx file list, click the server group URL replace the entry in the URL to
be replaced box.
The selected URL appears in the Replace with box.
7. Click Replace.
8. Click Yes to confirm the URL replacement.
9. Click Exit to close the Maintain URLs dialog box.
Update the JDBC Driver Path in NoticeCast Server Administration

You must complete this procedure only if your NoticeCast version is earlier than 7.0.811 and if
the agent was created in Cognos NoticeCast client. This procedure is not required if the agent
was created in Upfront or if you are upgrading from a 7.0.811 or later version of NoticeCast.
Steps
1. In Cognos NoticeCast Server Administration, from the Tools menu, click Maintain Data
Source.
The Data Source Pool Manager dialog box appears.
2. For each data source in the Name list:
Select the data source and from the File menu, click Edit Data Source.
In the Path box, type or copy the location and file name of the JDBC driver for your
database.
Tip: Use Configuration Manager to copy the appropriate path from the JDBC Driver File
property. This property is found in the category for your database under the NoticeCast
Data Store component.
Click OK.
3. Click Exit to close the Data Source Pool Manager dialog box.
4. Close Cognos NoticeCast Server Administration.
Update the Gateway URLs in Upfront for All Associated

Servers
When you installed Cognos Series 7 Version 2 Web products, you configured your Web server
using three unique Web aliases so that you could leave your 7.0 Web aliases in place. You must
now update these URLs in Upfront for the associated servers, such as Cognos Query,
PowerPlay Enterprise Server, Cognos Visualizer, Impromptu Web Reports.
Note that all Cognos NoticeCast NewsItems use the Upfront gateway, not the gateway of the
product the agent is associated with. For example, for a PowerPlay Agent, the gateway URL in
Upfront points to Cognos NoticeCast 7.1 by using
http://servername/cognosv2/cgi-bin/upfcgi.exe
Steps

./start-dbserv
./start-upfadmin
./start-dispatcher

3. Using a Web browser, connect to Upfront 7.1 using the URL http://servername/cognosv2.
4. Log on to Upfront as a user with administration privileges.
5. Go to the Administration NewsBox.
Note: This Administration NewsBox is not the same as the Administrators Personal
NewsBox.
6. Use the NewsItem Gateway Manager entry to replace references to each 7.0 gateway with
the version 7.1 equivalent.
Each gateway reference is a URL such as the following:
http://servername/cognosv2/cgi-bin/ppdscgi.exe
The gateway entry is case sensitive.
Tip: For most NewsItems, you can verify the correct gateway information in the NewsItem
property of the NewsItem Gateway Manager. For Cognos NoticeCast agents, use the
Upfront gateway defined for the Cognos NoticeCast server group in Configuration Manager.
You can now test Cognos NoticeCast by running a Cognos NoticeCast agent in Upfront. For
more information, see the Installation Testing and Samples Setup Guide.
Whats Next?
The upgrade of the server application data is now complete. Continue with the steps in the next
chapter to upgrade your client data.
Chapter 11: Upgrading Client Data

A complete upgrade of a server product involves installing new software, upgrading the server
application data, and upgrading the client data. The first two parts are assumed to be complete
when you use the information in this chapter.
In general, upgrading the Cognos client data you created through your client applications
authoring and modeling tools requires opening your 7.0 reports, catalogs, and models in version
7.1 of the product and then saving them in the new version. Where additional steps are required,
they are outlined in this section.
While backing up your reports is not a requirement for upgrading, it gives you additional flexibility
in the event that you want to revert to version 7.0 for any reason. In most cases, after your
reports are upgraded to version 7.1, you can no longer open them in version 7.0.
A utility called the Cognos Report Upgrade Utility is available from Cognos Customer Support. It
will be useful if you must upgrade a large number of reports, because it can upgrade a folder of
reports in a single action. It can also compare report output before and after upgrade for any
discrepancies.
PowerPlay for Windows

PowerPlay for Windows 7.0 reports can be opened in PowerPlay 7.1. When you save a report in
PowerPlay Windows 7.1, it will be saved in the 7.1 format.
PowerPlay for Excel

PowerPlay for Excel 7.1 can open reports saved in PowerPlay for Windows 7.0 or PowerPlay
Excel 7.0. When you save a report in PowerPlay Excel 7.1, it will be saved in the 7.1 format.
Impromptu
The upgrade of Impromptu data involves opening and saving the catalog (.cat) and Impromptu
report (.imr) files in Impromptu 7.1. When you open an Impromptu 7.0 report in Impromptu 7.1,
you are prompted to upgrade, use, or exit. If you choose upgrade, your .cat and .imr files are
immediately saved as Impromptu version 7.1 files. If you choose use, your files are opened in
read-only mode and you can upgrade them later.
Notes
After you save your files in Impromptu 7.1, they are no longer accessible in earlier releases of
Impromptu.
Web Browsers
Cognos components, such as Cognos Query Server Administration and PowerPlay Web, use
JavaScript files that are downloaded on first access and stored in the cache for each browser
user.
It is important that version 7.1 users are using version 7.1 JavaScript files. Browsers do
automatically check for newer versions of files, but how often they check is a browser tuning
option. We recommend that you empty the browser cache.
Clear the Browser Cache

Although browsers vary, the following are general steps for clearing your browser cache.
Steps
1. Open your browser.
2. Choose Internet Options from the Tools menu.
3. In the General tab, click the Delete Files button.
4. Click OK to clear the cache.
All temporary files in the cache are deleted.
Custom Macros and Other Applications

The Cognos Series 7 Version 2 products are installed by default in the cer3 directory, but 7.0
versions of the products were installed in the cer2 directory. If you have in-house developed
macros or applications that invoke Cognos products or point to them and you are upgrading
some or all of your Cognos products, you must edit your source to reflect the new directory
structure.
Cognos Macros
No action is required to upgrade Cognos Macros.
Architect
You can open an Architect 7.0 model from Architect 7.1. No action is required to upgrade. As
documented in the installation instructions, ensure that you have the correct version of
ObjectStore installed for Architect 7.1.
PowerPlay Transformer 7.1 can open your 7.0 models, which will have either a .pyi extension or
.mdl extension. No action is required to upgrade your 7.0 models to PowerPlay Transformer 7.1.
If your models are from an earlier version of PowerPlay Transformer and have a file extension of
.pyh or prior, you must first save your models with the .mdl extension and then open them in
PowerPlay Transformer 7.1 to upgrade them to the new version.
Upgrading Cognos Visualizer Visualizations

You can use the VizUpgrade command and either specify the visualizations to upgrade or
upgrade all visualizations in a specified folder. You can upgrade visualizations in place, or save
the upgraded visualizations to a new location that you specify.
The syntax is as follows:
VizUpgrade [-input] filename1.viz [filename2.viz...filenamen.viz] [-dest folder name] [-help]
The following table describes the VizUpgrade parameters.
Parameter
Description
-i or -input
Upgrades one or more visualizations.
-d or -dest
Saves the upgraded visualization files in a location

that you specify.
-h or -help
Provides a description of the command line syntax

for the VizUpgrade command.
Steps
On Windows, go to C:\Program Files\Cognos\cer3\bin directory
On UNIX, go to /usr/cognos/cer3/bin
2. If you use UNIX, ensure that you are in a Bourne shell by typing:
sh
Type the following command to set up the environment:

. ./setvizupgrade.sh
3. Run the VizUpgrade command with the required parameters.

For example, use the following command to upgrade the visualization Metrics.viz in the
same location.
Windows
VizUpgrade -i "d:\Program Files\cer3\Visualizations\Metrics.viz"
UNIX
./vizupgrade -i /usr/cer3/Visualizations/Metrics.viz
For example, use the following command to upgrade all visualizations in the Visualizations
folder.
Windows
VizUpgrade -i "d:\Program Files\cer3\Visualizations\*.viz"
UNIX
./vizupgrade -i /usr/cer3/Visualizations/*.viz
For example, use the following command to upgrade the visualization Metric.viz and save it
in a destination folder named Visualizations.
Note: If the destination folder does not exist, the VizUpgrade command creates a new
folder.
Windows
VizUpgrade -i "d:\Program Files\cer2\Visualizations\Metrics.viz" -dest "d:\Program
Files\cer3\Visualizations\
UNIX
./vizupgrade -i /usr/cer2/Visualizations/Metrics.viz -dest /usr/cer3/Visualizations/
Chapter 12: Moving Permanently to Your New

Version
When you have completed upgrading all your server and client components, including your
application data, and have tested your new 7.1 environment, you may be ready to switch
permanently to version 7.1.
You are then ready to
uninstall the 7.0 components
upgrade your directory server namespace to use the Current schema version format
(optional)
You can then use the Deployment Manager to deploy the version 7.1 application to a production
server or to a new set of servers. For more information, see the Deployment Manager User
Guide.
Uninstall Version 7.0 Components

For instructions about uninstalling, see the Uninstalling section of this guide.
Upgrade the Namespaces (optional)

The final stage in upgrading to Cognos Series 7 Version 2 is to upgrade the namespaces. This
converts the directory server schema used by Access Manager to the Current format. The
Current format is not compatible with 7.0 or earlier versions of products. The Current schema
can store extended and non-ASCII characters in UTF-8 format in your namespace. This format
supports all international characters when storing Access Manager information. For large
deployments, the Current schema version may also provide improved performance.
Note: All Cognos products must be upgraded to Cognos Series 7 Version 2 before you upgrade
the namespaces.
Steps
1. Use Configuration Manager to set the Schema Version parameter in Access Manager to
Current, and then Apply the setting.
For more information about changing settings, see the Configuration Manager User Guide.
2. Click Start, Programs, Cognos Series 7 Version 2, Tools, Access Manager Administration.
3. In the Authentication Information pane, expand the Directory Servers folder.
4. Right-click the directory server for which you want to upgrade the namespaces and click
Upgrade all namespaces to Current.
A message appears warning that upgrading namespaces to the Current schema version
will make the namespaces incompatible with Cognos Series 7 and earlier product versions.
5. Click OK.
6. In the Runtime Administrator distinguished name (DN) box, type the name that you use
to log on to the directory server.
7. In the Runtime Administration password box, type your password.
8. Click Log On.
Chapter 12: Moving Permanently to Your New Version
Appendix A: Uninstalling
Cognos Series 7
To uninstall Cognos Series 7, you can uninstall one or more installed components.You can also
uninstall the third-party products that you installed separately if these arent being used by other
Cognos products.
Uninstall the Cognos Components

Do not remove shared components unless you have no other Cognos product using these
components. Do not remove Access Manager Administration (if applicable) if you later want to
export your security information.
Before you uninstall Cognos Series 7, consider backing up the data stores.
If the Cognos component you are uninstalling is the last component remaining, or you are
uninstalling all Cognos components, you are prompted to specify whether to uninstall all folders
and files in the installation location or only folders and files created during the installation
process. If you choose to uninstall all folders and files, files created in or moved to the folders
after installation are also uninstalled. If you have reports or other information in the installation
location that you want to save, copy this information to a different location before uninstalling, or
choose to uninstall only the folders and files created during the installation.
To uninstall Cognos Series 7 products, select the components you want to uninstall from those
listed in the Add/Remove Programs dialog box:
Cognos Series 7 Version 2
Upfront (shared)
Impromptu Web Reports Administration Tools
Impromptu Web Reports Tools
Impromptu Web Reports Documentation
Impromptu Web Reports Quick Tours
Impromptu Web Reports Samples
Cognos Query
Cognos Query Administration Tools
Cognos Query Documentation
Cognos Query Quick Tours
Cognos Query Samples
Cognos Query Tools
Architect Administration Tools (shared)
Architect Samples (shared)
PowerPlay Windows (shared)
PowerPlay Excel (shared)
PowerPlay Transformer Edition Administration Tools
PowerPlay Transformer Edition Tools
Architect (shared)
PowerPlay Transformer Edition Documentation
PowerPlay Transformer Edition Samples
PowerPlay User Administration Tools
Appendix A: Uninstalling Cognos Series 7
PowerPlay User Tools (shared)

PowerPlay User Documentation (shared)
PowerPlay User Samples (shared)
PowerPlay Enterprise Server Administration Tools
PowerPlay Enterprise Server Tools
PowerPlay Enterprise Server Books
PowerPlay Enterprise Server Samples
Impromptu Administrator (shared)
Impromptu Administrator Administration Tools (shared)
Impromptu Administrator Tools (shared)
Impromptu Administrator Documentation (shared)
Impromptu Quick Tours (shared)
Impromptu Administrator Samples (shared)
Impromptu User
Impromptu User Tools (shared)
Impromptu User Documentation (shared)
Impromptu User Samples (shared)
Cognos NoticeCast Authoring
Cognos NoticeCast Administration
Cognos NoticeCast Documentation
Cognos NoticeCast Server
Cognos NoticeCast Tools
Cognos NoticeCast Tour Files
Cognos NoticeCast Samples
Cognos Visualizer
Cognos Visualizer Administration Tools
Cognos Visualizer Books
Cognos Visualizer Samples
Cognos Visualizer Server Samples
Cognos Visualizer Web Server Books
Cognos Visualizer Web Client
Cognos Common Logon Server (shared)
All the Cognos services used by Cognos Series 7 products are automatically stopped when you
uninstall Cognos components.
Steps
2. Double-click Add/Remove Programs.
3. Select one of the applicable Cognos component groups to uninstall (for example, Cognos
Series 7 Version 2) and do one of the following:
For Windows NT, click Add/Remove.
For Windows 2000, click Change/Remove.

The Uninstall Wizard opens.
4. Click Next.
5. Select the check box beside each component in the list, or click Select All to uninstall all
components at once, and then click Next.
6. If you selected all components, specify whether to uninstall only the files and folders created
during installation, or all the files and folders, including those created after installation.

7. Click Yes to confirm the uninstallation.
8. Click Yes to restart your computer if prompted.
Uninstall Sun ONE Directory Server

For procedures to uninstall Sun ONE Directory Server (formerly called Netscape Directory
Server), see the Cognos Series 7 Supplementary Software Installation Guide.
Uninstall ObjectStore
Before you uninstall ObjectStore, ensure that no other component needs it.
Note: When upgrading, you must uninstall the old version of ObjectStore before you install the
new version.
Steps to Stop Services

ObjectStore server and ObjectStore cache manager run as services. Ensure that there are no
active connections to the server or cache manager services.
Note: You must stop the Cognos Impromptu Web Reports Service Manager service before
stopping the ObjectStore Services and uninstalling ObjectStore.
Steps
2. Double-click Services.
3. From the list of services, select ObjectStore Cache Manager R6.0 and click Stop.
4. When prompted to confirm that you want to stop the service, click Yes.
The cache manager server stops.
5. Repeat steps 3 and 4 for the ObjectStore Server R6.0 service.
Steps to Uninstall ObjectStore

Before you uninstall ObjectStore, you may want to back up the ObjectStore databases that hold
information about the Impromptu Web Reports reports that were created. For more information
about backing up ObjectStore databases, see the ObjectStore documentation.
Steps
1. Ensure that the ObjectStore Server and ObjectStore Cache Manager services are
stopped.
2. From the Start menu, click Programs, ObjectStore Win32, ObjectStore Uninstall.
A message box appears to list the actions that the uninstall program will complete or to warn
you if you have not yet shut down the ObjectStore services.
3. Click Yes to complete the uninstall.
4. In the ObjectStore Uninstallation dialog box, click Next.
5. Click Yes to confirm deletion and removals by the uninstall process.
6. Click OK to confirm the uninstall has completed.
7. Delete any log files created by ObjectStore.
The default log file name and location is c:\odi\ostore.log.
Appendix B: Other Types of Installations

You can perform unattended installations of Cognos products. All installation tasks run
automatically, without any intervention by you. You can use the same installation script for a
group of computers that have the same configurations, instead of having to set up each
computer individually.
You may want to consider other types of installations. You can set up installation files on a
network so that users can install the product on their own computer using these files instead of
the CDs. You can decide what the default set of files will be in the installation package you make
available on the network.
You can install multiple instances of the same Cognos product gateway on the same computer.
To ensure that each instance is installed in a separate location, you must modify the altname.ini
file before installing the second and each subsequent instance.
Setting Up an Unattended Installation

If you want to automate the installation process and specify installation options for your users,
you can set up an unattended installation. Instead of prompting the user for information, such as
where to install and what type of installation to do, an unattended installation reads the
information from prepared files. Unattended installations are convenient if you need to perform
several installations that have the same configuration.
If you plan to do an unattended installation of Cognos components on several computers, it is
recommended that you first use the Installation Wizard and Configuration Manager to install the
same components on one computer. That way, you can use the files that are generated as input
for your unattended installation.
Before you can do an unattended installation, you must select a computer and check that all the
prerequisites are met, including installing third-party products.
To perform an unattended configuration of Cognos products, you must
use a transfer specification file (.ats) to copy the required components to your computer.
use an environment script (.ccp) to configure the components for your environment.
After you successfully complete an unattended installation, the Cognos components will be
installed on your computer.
Notes
To perform an unattended installation, you use the command line interface of Configuration
Manager. We recommend you read the Configuration Manager User Guide before
proceeding.
If you want to complete the unattended installation in one step, you can write a script or
batch file to run both the transfer specification and environment specification files.
Set Up an Unattended Copy of Cognos Components

To copy components to your computer without being prompted for information, the installation
program requires a transfer specification file (.ats).
If you plan to copy the same components to several computers, it is recommended that you use
the Installation Wizard the first time you copy. By default, each time you copy Cognos
components to your computer using the wizards setup screens, the options you select are
recorded in a transfer specification file. Therefore, if you have already copied components to
your computer, you can use the generated transfer specification file as a template for
unattended installations that copy the same components to different computers.

If you do not use the Installation Wizard to copy components to your computer, you can use the
default transfer specification file named response.ats that is available on the product CD. You
need to modify the response.ats file for your environment before you can use it for an
unattended installation.
Steps to Use a Transfer Specification File (.ats) From a Previous Installation

1. Use the Installation Wizard to copy the required components to your computer.
2. Go to the installation_location/instlog directory.
3. Locate the transfer specification file (.ats) that was generated.
The file name follows the same naming convention as the component log file and has the
following format:
ts-PRODUCT-version-yyyymmdd-hhmm.ats
4. Copy the transfer specification file from step 3 to the computer where you will be doing an
unattended copy.
5. On the computer where you will be doing an unattended copy, insert the Cognos Windows
CD.
6. Go to the Cognos/product directory on the CD.
7. Open a command prompt window, and then type the following command, where location is
the directory where you copied the transfer specification file:
xwsetup /s location\ts-product_name-version-yyyymmdd-hhmm.ats
This copies the specified components in the transfer specification file to your computer.
Steps to Use the Default Response.ats File

1. On the computer where you will be doing an unattended copy, insert the Cognos Windows
CD.
2. Go to the Cognos\product directory on the CD.
3. Open the response.ats file in a text editor.
Each section in the response.ats file corresponds to a dialog box in the Installation Wizard.
4. Under the Installation Type title, for the Type property, specify the type of installation.
If you specify Default, the installation program installs all components specified for a default
install. If you specify Custom, the installation program installs the components you specify
in the [Component List] section. If applicable, when you specify Minimal, the installation
program installs only the components required to run the product without common security,
modelling, or portal functionality.
5. For the property named Mode, to specify the method the installation program uses to copy
components, type one of the following:
Client
Workstation
6. In the section named [Component List], specify the components to install for a custom
installation.
"1" specifies the component will be installed.
"0" specifies the component will not be installed.
7. Under the Character Set Selection title, specify the character sets you require.
"1" for RB_LATIN1_LOC specifies that character sets for English, French, German,
Dutch, Spanish, Swedish, Italian, Finnish, Portuguese, and other Western European
languages will be installed.
"0" for RB_OTHER_LOC specifies that only the English character set will be installed.
8. In the section named [Language Selection], specify the language to install for the
multi-lingual components.
"1" specifies the language will be installed.
"0" specifies the language will not be installed.

9. Under the Installation Location title, specify the locations where you want users to install
Cognos components. For example,
appPath specifies the location of the program files.
docPath specifies the location of the documentation files.
samplesPath specifies the location of the samples files.
tourPath specifies the location of the Quick Tour.
10. Under the Shortcut Folder title, for the APPFOLDER property, specify the name of the
Start menu folder that will contain your program shortcuts.
11. For the install information in the section named [Install Conditions],
"1" specifies the condition is true.
"0" specifies the condition is false.
12. Save the response.ats file to a local directory after you make the necessary changes.
13. Go to the Cognos\product directory on the CD.
14. Open a command prompt window, and then type the following command, where location is
the directory where you copied the transfer specification file:
xwsetup /s location\response.ats
This copies the specified components in the transfer specification file to your computer.
If errors are encountered during the unattended copy, they are recorded in a log file named
tl-PRODUCT-version-yyyymmdd-hhmm_summary-error.txt located in the
installation_location\instl directory.
If errors are encountered before sufficient initialization has occurred, the error will be output
to a log file in the Windows Temp directory. The log file name follows the same naming
convention as the transfer specification file and has the following format:
tl-PRODUCT-version-yyyymmdd-hhmm.txt.
Set Up an Unattended Configuration of Cognos Components

To configure components on your computer without any user interaction, you need to use
Configuration Manager to create an environment script file (.ccp). This enables you to specify
configuration settings before installation begins, and you can apply identical configuration
settings to multiple computers. We recommend you read the Configuration Manager User Guide
before proceeding.
If you use the default configuration settings for the Cognos components you install, you do not
need to create an environment script file.
Before you can use an environment script for an unattended configuration, the components that
you need to configure must already be installed.
Steps to Configure Components Using Default Settings
From the installation_location\bin directory, type configcp -u

This applies the current property values for any existing components plus the default
property values for newly transferred components, and then starts the services.
Steps to Configure Components Using Custom Settings

1. On the computer where you want to export the configuration as a script, from the Start
menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration Manager.
3. To create an environment script file,
click Open the Current Configuration to open the current configuration.
click Open a Configuration From a File to open a saved configuration specification

file.
4. If required, modify any property values that need to be changed on the Components tab.
Note: Any changes you make to server settings on the Server Configuration tab are not
saved to the generated environment script file.

5. To export the configuration to an environment script file, from the Actions menu, click
Export Script.
6. In the File name field, enter the name of the file.
7. In the Save in field, select the location where you want to save the environment script file
(.ccp).
The current configuration is saved to the environment script file.
8. To run the script, from the installation_location\bin directory, type the following command,
where file_name is the name of the script file:
configcp -t file_name
Note: You will need to use Configuration Manager in interactive mode to import the server
configuration file (cer3.csx). The file is used by servers, and is not necessary for client
installations.
Configuration Manager uses the information in the environment script file to apply the
property values for the local configuration.
Setting Up Installation Files on the Network

You can copy the contents of the Cognos Series 7 CDs to your network so that users can install
from the network instead of from the CDs. When copying files to the network, you should not
change the directory structure.
Steps
1. Insert one of the installation CDs.
2. Copy the components entire directory structure and files from the CD to a deployment
location on the network.
3. Repeat for each CD provided with the product.
Note: You can also give your users access to a shared CD-ROM drive.
Setting Up an Administrative Installation

As an administrator, you may want to perform an administrative installation to copy the
installation files to the network and at the same time control
what files are included in a default installation
what files are preselected in a custom installation when users install from the network
Note: This type of installation is available for only Windows products.
Steps
1. Open a command prompt window.
2. Type the command to go to the Cognos\product folder on the CD.
3. Type xwsetup /a to start an administrative installation.
The Installation Wizard opens in administrative mode.
Next.
6. In the Installation Location dialog box, under Network Installation Point, click the ellipsis
to browse or create a new network folder where the installation files will be copied.
7. Click Next.
8. In the Workstation Installation dialog box, select the components that will be included in a
default installation when performed by your users, and then click Next.

9. In the Installation Summary dialog box, click Next.
All files are copied to the network installation point.
After the files are successfully copied, users can install the product from the specified
network installation point. The default installation will only install the components you
selected.
10. Click Finish.
11. Type exit to close the Command Prompt window.
Set Up a Workstation Installation

With a workstation installation, a subset of files for the product is installed on the Windows client
computer, while most of the product software resides on a centrally shared computer. This type
of installation allows users to run the software from the network installation point and has the
advantage of using less space on the client computer. However, it inevitably generates more
network traffic.
Notes
If you choose to do a workstation installation for your Windows client product, you cannot
install another Cognos product on the same computer using the usual installation methods.
The two installation methods are mutually exclusive because a workstation installation
resets the installation location.
Only Impromptu and PowerPlay client products support workstation installations.
You cannot develop PowerPrompts from workstation installations of Impromptu.
As an administrator, you must complete an administrative installation to set up the workstation

installation before users can install from the network.
Steps
1. Open a command prompt window.
2. Type the command to go to the Cognos\product folder on the CD.
3. Type xwsetup /a to start an administrative installation.
The Installation Wizard opens in administrative mode.
Next.
6. In the Installation Location dialog box, under Network Installation Point, click the ellipsis
to browse or create a new network folder where the installation files will be copied.
7. Select the Workstation Installation check box.
This option uncompresses the files before copying them to the network.
8. Click Next.
9. In the Workstation Installation dialog box select the components that will be included in a
default installation when performed by your users, and then click Next.
10. Follow the remaining instructions to finish the setup of a workstation installation.
Perform the Workstation Installation

After an administrator sets up the workstation installation, users can do the installation on their
computer by following these steps.
Steps
1. Double-click the setup.exe file that matches the name of the product you are installing in the
Cognos folder where your administrator copied the installation files.
The Installation Wizard opens.

Next.
4. Type your user information and click Next.
5. In the Installation Type dialog box, click Workstation.
6. Follow the remaining instructions to complete the workstation installation.
A subset of files are installed on your computer, the remainder of the files are executed from the
network installation point. You must be connected to the network to use your Cognos product.
Install Multiple Instances of a Cognos Product Gateway

on the Same Computer
You can install more than one instance of Cognos Series 7 Version 2 product gateways on the
same Web server. This enables you to support more than one server group of a Cognos product
on a single Web server. Only the gateway components can be installed more than once. Multiple
installations of non-gateway components are not supported on Windows.
To install multiple instances of a gateway component, install the first instance as you would any
custom installation, selecting the components to install and the installation location. Before
installing each additional instance of the Cognos gateway components, modify parameters in
the altname.ini file to specify the location and rendition for each instance.
Modify altname.ini
The altname.ini file is located in the Cognos/product folder on the Cognos CD. For example, the
location for PowerPlay Enterprise Server is Cognos/ppes.
Note. You do not need to modify altname.ini parameters if you are installing different versions of
the same product on one computer; for example, PowerPlay 7.1 and PowerPlay 7.0.
By default, altname.ini contains the following parameters and values:
[Rendition]
Name=cer3
Description=Cognos Series 7 Version 2
Folder=Cognos Series 7 Version 2
The following table describes each parameter and the modifications to make for second and
subsequent installations of Cognos gateway components. Use the table to determine the
changes to make in the steps that follow.
Parameter
Determines
Name
The installation For each instance after the first,

change this parameter to specify the
location.
directory into which the instance is to
Default:
be installed. We recommend you do
cognos/cer3
not use special characters in the
parameter; for example, change cer3
to cer3a for the second installation,
cer3a to cer3b for the third, and so
on.
Modification Required
Parameter
Determines
Modification Required
Description
The name
displayed in the
Windows Start
menu.
For each instance after the first,

change this parameter. For example,
use Cognos Series 7 Version 2 for the
first instance, Cognos Series 7
Version 2a for the second, and so on.
We recommend you do not use
special characters in the parameter.
Folder
The name
displayed in
Windows for
Add/Remove
programs.
For each instance after the first,

change this parameter. For example,
use Cognos Series 7 Version 2 for the
first instance, Cognos Series 7
Version 2a for the second, and so on.
We recommend you do not use
special characters in the parameter
Example
The following table shows examples of altname.ini parameters for three installations of the
Cognos gateway components.
Parameter
Instance 1
Instance 2
Instance 3
Name
cer3
cer3a
cer3b
Description
Cognos Series
7 Version 2
Cognos Series
7 Version 2a
Cognos Series
7 Version 2a
Folder
Cognos Series
7 Version 2
Cognos Series
7 Version 2a
Cognos Series
7 Version 2a
Steps
1. Install the first instance of the product as you would any distributed installation
2. Copy the altname.ini file from the Cognos CD to the TEMP directory.
3. Modify the name, description, and folder parameters in the altname.ini file as required
(p. 180), and then save the file.
4. Install the next instance of the product as you would any custom installation, selecting only
the gateway components.
If the values from the modified altname.ini file do not appear in the Installation Wizard, the
modified altname.ini file is in the wrong location. Verify that you have placed the modified file
in the directory point to by the TEMP variable.
5. Configure the installed components using Configuration Manager.
Each instance includes a separate installation of Configuration Manager. When configuring
multiple installations, ensure that you use the correct instance of Configuration Manager.
When configuring multiple installations, ensure that port numbers do not conflict with other
instances of Cognos products on the computer, and that each instance of PowerPlay writes
temporary files to its own location. The temporary file location for each instance is set in
Configuration Manager in Cognos PowerPlay Enterprise
Server.Gateway.General.Temporary Resource (/ppwb) Location.
6. Repeat steps 3 through 5 for each subsequent instance you install.
For each installed instance, the name of the configuration specification file (.csx) matches
the value specified in the altname.ini Name parameter. For example, if the Name for the
second and third installations is cer3a and cer3b respectively, the second and third
instances of the .csx files would be cer3a.csx and cer3b.csx. It is important to consider this
when managing these files. When distributing the configuration specification file to the
cgi-bin directories of these instances, rename the file accordingly.
Appendix C: Alternative Upgrades

There are alternative ways to upgrade some Cognos Series 7 products. For information about
the primary procedures, see Upgrading Application Data. As an alternative to the primary
procedures, you can upgrade
PowerPlay Enterprise Server using Cognos Deployment Manager
Cognos Visualizer using the command line interface
You must upgrade Upfront before upgrading PowerPlay Enterprise Server and Cognos
Visualizer. For more information, see Upgrading Upfront.
If you are using both Cognos PowerPlay Enterprise Server and Cognos Visualizer, you must
upgrade PowerPlay Enterprise Server first and then upgrade Cognos Visualizer. If these
products are not upgraded in the correct order, Cognos Visualizer may not open remote cubes.
Upgrading PowerPlay Enterprise Server

You can upgrade Cognos PowerPlay Enterprise Server from version 7.0 to 7.1 using Cognos
Deployment Manager. This is an alternative upgrade method to using the ppserver upgrade
utility.
Before you upgrade PowerPlay Enterprise Server, do the following:
Ensure that your Cognos services are running (required) (p. 184).
Update PowerPlayEnterprise Server URLs in Upfront using Gateway Manager (p. 190).
To upgrade PowerPlay Enterprise Server, use Cognos Deployment Manager 7.1 to do the
following:
Pack the Cognos PowerPlay Enterprise Server 7.0 data (required) (p. 184).
Unpack the Cognos PowerPlay Enterprise Server 7.0 data (required) (p. 186).
For more information, see the chapters about packing and unpacking in the Cognos Deployment
Manager User Guide.
Deployment Manager Commands You Need for the Upgrade

You need the following Deployment Manager commands for the upgrade.
Define command (cdmdefine)

This command is used to create the following files:
package definition (.dmd); A package definition file identifies the data to be packed and the
packing policies for that data.
a pack settings file (.dmi); This file is used to select a subset of the data for packing, to
define a default folder for storing the packlets, or to modify the packing policies. This
command is then used again to update the package definition using the changes made to
the pack settings file.
an unpack settings file (.dmu)
Pack command (cdmpack)

The package definition, which is created using the Define command, must be available before
you can use this command.
Unpack command (cdmunpack)

The package, which is created using the Pack command, must be available before you can use
this command.

For more information, see the Deployment Manager help file D:\ProgramFiles\Cognos\cer3\
Documentation\html\cdm\en\cdm\welcome.html and the Deployment Manager User Guide.
Pack Cognos PowerPlay Enterprise Server Data (Required)

On the 7.1 administration computer, pack the Cognos PowerPlay Enterprise Server data by
running Cognos Deployment Manager 7.1.
The packing process creates a package definition file (.dmd), a pack settings file (.dmi), a
package file (.dmp), and packlets.
\Cognos\cer3\packlets\pkg_def_folder\pkg_folder\ppes
\Cognos\cer3\packlets\pkd_def_folder\pkg_folder\upfront
On UNIX, the default locations depend on the interface you use. If you use Cognos Deployment
Manager graphical user interface to pack UNIX data, the package files are created on the
Windows computer in the default Windows location. The packlets, however, are created on the
UNIX computer in the following default location(s):
usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/ppes
usr/cognos/cer3/packlets/pkg_def_folder/pkg_folder/ppes
Steps to Ensure That Your Cognos Services Are Running

Ensure that the following 7.1 services or corresponding processes are running by using
Configuration Manager.
On UNIX, you can also start 7.1 processes from the /usr/cognos/cer3/bin directory by running
the following scripts:
./start-dbserv
./start-dispatcher
./start-upfadmin
./start-ppsvr.sh

7. Ensure that the 7.1 environment is configured for the appropriate Access Manager Runtime.
8. Click the Start menu, Programs, Cognos Series 7 Version 2, Cognos Server
Administration.
12. In the New Package Definition box, type a name for the package definition file, such as
PPpkg.
Do not add a file extension. The extension .dmd is enforced.
Do not include the file name in the path.
For example, the default location is installation_location\packages\PPpack.

running in the 7.1 environment. Use the format host:port or the IP address in the format IP
address:port.
15. If you want to test the connection, click Test, and then click OK.
17. Wait until the message Action completed successfully appears, and then close the New
Package Definition box.
The Package Definition Editor appears. The package definition file and its parent folder
are listed in the Explorer window.
Expand Dependent Components, and exclude all components except PPES and
Leave the NewsIndex components as preselected or exclude any NewsBoxes that you
do not want to upgrade.
19. In the Package Definition Editor window, click PPES component.

20. In the PPES Properties window, change the properties of the PPES component.
21. Under Pack Operation in the PowerPlay Directory box, provide the location of your
PowerPlay Enterprise Server.
22. Under Pack Operation, click the Type box, and then click the drop-down list and select
Pack All.
23. In the Package Definition Editor window, click NewsIndex, and then deselect the
newsboxes you do not want to upgrade to 7.1.
24. From the File menu, click Save, and then click Pack.
25. Type a name for the package file. You can use the same name that you gave to the package
definition file, such as PPpkg.
Do not add a file extension. The extension .dmp is enforced.
26. Click OK.
box.
Ensure that the following is true:
The PPpack folder is located in the Packages folder under cer3 on the 7.1 computer.
The Upfront and PowerPlay Enterprise Server packlets are located in the Packlets
folder under cer3 on the 7.1 computer(s).

sh

. ./setcdmvars.sh
file (.dmi) by typing the following command on the command line:
cdmdefine -cd -d PPpack -u UpfServ:8030
If a port number is not specified, the default port for the 7.1 Upfront server, 8030, is
assumed.

3. Log on if required.
A message indicates that the files were created. In this example, the PPpack.dmd and
PPpack.dmi files are located in C:\Program Files\Cognos\cer3\packages\PPpack on
Windows or in /usr/cognos/cer3/packages/PPpack on UNIX.
4. If you want to deselect any Newsboxes or components, or change the packlets location, edit
the .dmi file in a text editor and then type the following command to modify the package
definition file with the pack setting file:
cdmdefine -md -d package_def_name [-dl package_def_location]
cdmdefine -md -d PPpack
5. To pack all PowerPlay Enterprise Server Content which was not deployed in a prior release,
such as unpublished content, server properties,and report versions, open the pack settings
file (.dmi) in a text editor.
6. For each packing policy identified in the pack settings file, add or remove the comment
indicator (;) to select the desired response. In the following example, the response for the
PowerPlay Enterprise Server packing policy, Pack Type, is set to Pack All.
[PPES]
. . .
;Type
;PPES.packOperationType choices
PPES.packOperationType=Pack All
;PPES.packOperationType=Pack NewsItems
7. Save, and then close the pack settings file.

8. Go to the installation location/bin directory and from the command line type the following:
cdmdefine -md -d name
The package definition is updated with the information in the pack settings file.
Note: Use -dl pathname to specify the path location of the package definition when a
location other than the default is desired.
For example, -dl c:\deployment files\sales
9. Type the following command to pack the data and to create the package file (.dmp):
package_location]
cdmpack -d PPpack -p PPpack
In this example, the PPpack.dmp file is created in C:\Program

Files\Cognos\cer3\packages\PPpack\PPpack on Windows or in
/usr/cognos/cer3/packages/PPpack/PPpack on UNIX.
10. Log on again if prompted.
11. Respond to the prompt to continue.
Unpack Cognos PowerPlay Enterprise Server Data (Required)

On your 7.1 administration computer, unpack the Cognos PowerPlay Enterprise Server data by
running Cognos Deployment Manager to load the package file (.dmp) you created when you
packed the Cognos PowerPlay Enterprise Server data.

Ensure that the following 7.1 services or corresponding processes are running by using

./start-dbserv
./start-dispatcher
./start-upfadmin
./start_ppsrv.sh

1. Click Start menu, Programs, Cognos Series 7 Version 2, Cognos Server
Administration.
3. Locate the package file (.dmp), such as C:\Program
Files\Cognos\cer3\packages\ppserver\PPpack.dmp, and then click Open.
5. Select the Upfront Dispatcher in the 7.1 environment. Use the format host:port or the IP
address in the format IP address:port.
6. Click Test, and then click Close.
7. In the Package Editor, expand the Access Manager component and verify that the correct
namespace is listed. Also, expand the NewsIndex component and verify the NewsBoxes.
If this button is not visible, click the >> symbol.
9. In the Mapping Editor, select <All> in the list, and then click Auto Fill.
10. Log on to your authentication source in response to the prompt.
11. When the Auto Fill process prompts you to Replace current target values, click Yes, and
then click Close.
12. If required, change the target information for the gateways, cubes, and servers in the Target
column to 7.1.
window. For information about any errors, see the Cognos Deployment Manager User
Guide.
16. Click Close to close the Deployment Manager dialog box, and then click Close in the
Package Editor.

1. On UNIX, ensure that you are in a Bourne shell by typing:
sh

. ./setcdmvars.sh

2. Go to the cer3/bin directory and create an unpack setting file (.dmu) by typing the following
command on the command line:
cdmdefine -cp -p packagename [-pl package_location] -u Upfront_server[:port]
cdmdefine -cp -d PPpack -p PPPack -u UpfServ:8030
If a port number is not specified, the default port for the Upfront server, 8030, is assumed.
In this example, the PPpack.dmu file will be created in the C:\Program
Files\Cognos\cer3\packages\PPpack\PPpack on Windows or the
/usr/cognos/cer3/packages/PPpack/PPpack on UNIX.
3. Log on if required.
For each location identified in the unpack settings file, type an appropriate value for the
5. Type the following command to modify the package file with the unpack setting file:
For example, on Windows or UNIX, the following command uses default location:
cdmdefine -mp -d PPpack -p PPpack
6. Type the following command to verify the package:

cdmunpack -v -d PPpack -p PPpack -u UpfServ:8030
7. Type the following command to unpack the package:
cdmunpack -d PPpack -p PPpack -u UpfServ:8030

The Impromptu Web Reports drill mappings may need to be updated. You can upgrade the drill
mappings using the PowerPlay Enterprise Server Administration tool.
You can now test your 7.1 environment. For more information, see the Installation Testing and
Samples Setup Guide.
Upgrading Cognos Visualizer

You can upgrade Cognos Visualizer from version 7.0 to 7.1 using the command line interface.
This is an alternative upgrade method to using Cognos Deployment Manager.
Use the command line interface if you want to upgrade all items on the Viz Web Server.
Use Cognos Deployment Manager if you want to upgrade items published to Upfront. For more
information about upgrading Cognos Visualizer using Cognos Deployment Manager, see
"Upgrading Application Data".
The following generic service names are used in the steps that describe the upgrade process.
Service
Windows
UNIX
Cognos Visualizer
vizwebsrv.exe
vizwebsrv
Preparing the environment for upgrade

The 7.0 PowerPlay Enterprise Server must be upgraded to 7.1 before you perform the Cognos
Visualizer Web Server upgrade procedures.
If your visualizations are in a single location, you can upgrade all visualizations in that location
from 7.0 to 7.1. However, to provide some backup protection, or to allow you to continue to use
the visualizations with Cognos Visualizer 7.0, you should copy the visualizations to a different
location. For an in-place upgrade, you can copy the visualizations to a different location on the
same computer. For a staged upgrade, you can copy the visualizations to the 7.1 computer.
For visualizations that use remote cubes for data sources, if the location of the 7.1 cubes is
different from the location of the 7.0 cubes, you must remap the visualizations to use the 7.1
cubes.
If you are using Upfront, use Cognos Deployment Manager to map to the 7.1 cubes
If you are not using Upfront, open Visualizations in Cognos Visualizer 7.0 Authoring
tool, update the data source location, and save the visualizations.
Upgrading Cognos Visualizer Web Server

Do the following to upgrade your Cognos Visualizer Web Server.
Steps
1. Rename the vizwebconfig.dat file located in the cer3\bin directory to vizwebconfigold.dat.
2. Copy the vizwebconfig.dat file from the cer2\bin to cer3\bin directory.
3. Open 7.1 Configuration Manager and stop services for Cognos Visualizer Web Server.
4. Apply properties and start services for Cognos Visualizer Web Server.
5. Open 7.1 Cognos Server Administration, and then click Visualizations.
6. Select the 7.1 Visualization server, and then click OK.
7. If you moved the visualizations to a different location for the upgrade to 7.1, complete the
following for all visualizations that appear in the Visualizer Web Server Administration:
Click a visualization, click File, Properties, and then click Visualization.
In the Visualization Source box, change the location to the 7.1 directory, and then click
OK.
8. When you completed the previous step for all visualizations, click the server root and stop
and start services.
Upgrading Cognos Visualizer Visualizations

You can use the VizUpgrade command and either specify the visualizations to upgrade or
upgrade all visualizations in a specified folder. You can upgrade visualizations in place, or save
the upgraded visualizations to a new location that you specify.
The syntax is as follows:
VizUpgrade [-input] filename1.viz [filename2.viz...filenamen.viz] [-dest folder name] [-help]
The following table describes the VizUpgrade parameters.
Parameter
Description
-i or -input
Upgrades one or more visualizations.
-d or -dest
Saves the upgraded visualization files in a location

that you specify.
-h or -help
Provides a description of the command line syntax

for the VizUpgrade command.
Steps
On Windows, go to C:\Program Files\Cognos\cer3\bin directory
On UNIX, go to /usr/cognos/cer3/bin
sh

. ./setvizupgrade.sh
3. Run the VizUpgrade command with the required parameters.

For example, use the following command to upgrade the visualization Metrics.viz in the
same location.
Windows
VizUpgrade -i "d:\Program Files\cer3\Visualizations\Metrics.viz"
UNIX
./vizupgrade -i /usr/cer3/Visualizations/Metrics.viz
For example, use the following command to upgrade all visualizations in the Visualizations
folder.
Windows
VizUpgrade -i "d:\Program Files\cer3\Visualizations\*.viz"
UNIX
./vizupgrade -i /usr/cer3/Visualizations/*.viz
For example, use the following command to upgrade the visualization Metric.viz and save it
in a destination folder named Visualizations.
Note: If the destination folder does not exist, the VizUpgrade command creates a new
folder.
Windows
VizUpgrade -i "d:\Program Files\cer2\Visualizations\Metrics.viz" -dest "d:\Program
Files\cer3\Visualizations\
UNIX
./vizupgrade -i /usr/cer2/Visualizations/Metrics.viz -dest /usr/cer3/Visualizations/
Update the Gateway URLs in Upfront for All Associated

Servers
When you installed Cognos Series 7 Version 2 Web products, you configured your Web server
using three unique Web aliases so that you could leave your 7.0 Web aliases in place. You must
now update these URLs in Upfront for the associated servers, such as Cognos Query,
PowerPlay Enterprise Server, Cognos Visualizer, Impromptu Web Reports.
Note that all Cognos NoticeCast NewsItems use the Upfront gateway, not the gateway of the
product the agent is associated with. For example, for a PowerPlay Agent, the gateway URL in
Upfront points to Cognos NoticeCast 7.1 by using
http://servername/cognosv2/cgi-bin/upfcgi.exe
Steps

./start-dbserv
./start-upfadmin
./start-dispatcher
available and the ticket server is running.
3. Using a Web browser, connect to Upfront 7.1 using the URL http://servername/cognosv2.
4. Log on to Upfront as a user with administration privileges.
5. Go to the Administration NewsBox.
Tip: This Administration NewsBox is not the same as the Administrators Personal
NewsBox.
6. Use the NewsItem Gateway Manager entry to replace references to each 7.0 gateway with
the version 7.1 equivalent.
Each gateway reference is a URL such as the following:
http://servername/cognosv2/cgi-bin/ppdscgi.exe
Tip: The gateway entry is case sensitive. For most NewsItems, you can verify the correct
gateway information in the NewsItem property of the NewsItem Gateway Manager. For
Cognos NoticeCast agents, use the Upfront gateway defined for the Cognos NoticeCast
server group in Configuration Manager.
You can now test Cognos NoticeCast by running a Cognos NoticeCast agent in Upfront. For
more information, see the Installation Testing and Samples Setup Guide.
Appendix D: Troubleshooting
This appendix describes and provides solutions to the most common problems that you may
encounter during or after the installation of Cognos Series 7. Descriptions of all log files are also
included.
Troubleshooting Resources
You can use Configuration Manager to diagnose and fix problems related to the configuration of
your components. For more information about using Configuration Manager, see the
Configuration Manager User Guide or the Configuration Manager online help.
Access Manager - Administration

You can use Access Manager - Administration to verify correct configuration of and connection
to your Directory Server and Ticket Server. From the Properties window of the Directory Server,
you can test whether the Directory Server and Ticket Server respond for the server name and
port numbers you specify.
Windows Event Viewer

The Windows Event Viewer provides information that might help you diagnose problems. To
open the Windows Event Viewer
On Windows NT: From the Start menu, click Programs, Administrative Tools
(Common), Event Viewer.
On Windows 2000: From Control Panel, click Administrative Tools, Event Viewer.
Log Files
The following log files contain information that can help you fix installation and configuration
problems for Cognos Series 7 products:
The transfer log file is a record of the activities that the Installation Wizard performed while
transferring files. The transfer log file is located in the installation_location\instlog folder on
Windows and UNIX. The file name identifies the product name, version, and build number,
and includes a time stamp. The following is an example of the file name format:
tl-PP-7-0-517-0-20011104_0942.txt
The transfer summary-error log is a record of what components were installed, disk space
information, the selections you made in the transfer dialogs, and any errors the Installation
Wizard encountered while transferring components. The transfer summary-error log is
located in the installation_location\instlog folder on Windows and UNIX. The file name
identifies the product name, version, and build number, and includes a time stamp. The
following is an example of the file name format:
tl-PP-7-0-208-0-20011106_1122_summary-error.txt
The configuration activity report is a record of all activities that Configuration Manager
performs. A configuration activity report file is created for each configuration session. The
report is located in the installation_location\instlog folder on Windows and UNIX. The file
name includes a time stamp. The following is an example of the file name format:
cfa-20011105_1652.txt
The configuration error report is a record of any warnings and errors the Installation Wizard
encountered during configuration. The report is in the installation_location\instlog folder on
Windows and UNIX. The file name includes a time stamp. The following is an example of the
file name format:
cfe-20011106_1122.txt
The component list file is a record of all Cognos components installed on your computer.
Each entry in the file consists of the component name and its build number. The component
list file is called cmplst.txt and is located in the installation_location folder.
The configuration specification file (.ccs) is a complete record of the Cognos Series 7
configuration on your computer. You can use Configuration Manager to save your
configuration as a .ccs file and then revert back to that configuration later. You can also
forward your .ccs file to your support personnel or to Cognos Support to help diagnose
configuration problems.
General Problems
Configuration Values Not Applied
If you use Configuration Manager to change configuration values but fail to apply them, the new
values will not take effect and some components may not work properly.
To ensure that all configuration values have been applied, perform an Apply on the computer
after you have configured your components.
Services Not Running

If you use Configuration Manager to change configuration values but fail to start all services,
some components may not work properly.
In a distributed environment, it is possible that another person stopped a service after you
started it. For example, a server administrator may have stopped all services to perform an
upgrade, and then failed to restart all the services.
To ensure that all services are running, perform an Apply and a Start on the computer.
Port Numbers Do Not Match

Port numbers for components must be defined consistently. If the port number for a component
is defined as one value on the computer that provides the service, and as a different value on a
computer that attempts to access the service, the attempt will fail.
Use Configuration Manager to ensure that port numbers for components are defined
consistently across all computers running Cognos Series 7 components.
Failure to Change Default Values

When you install Cognos Series 7 products, certain configuration values exist by default. You
may need to change some configuration values, such as port numbers, to suit your environment.
If you need to change configuration values but fail to do so, some components may not work
properly.
Lack of Connectivity Between Components

There are many possible causes for connectivity problems. These causes include port number
mismatches, services not running, failure to install Cognos components or third-party products,
and basic network connectivity failure, such as an unavailable host.
Multiple Versions of the Server Configuration File

The server configuration file (cern.csx) contains server configuration information that enables
the gateway components to find their associated dispatchers.
We recommend you ensure that the same version of the server configuration file exists on each
computer within your distributed installation.
If you use more than one version of the file some components may not be able to access
services on other servers.
Web Protocol for Relative URL Support

If your Web server uses the HTTP Web protocol and you have a proxy server such as a router or
firewall configured to use the HTTPS protocol, you may experience problems. This is because
your router or firewall may use accelerated SSL encryption technology.
To avoid this situation, do one of the following:
If your proxy server uses the HTTPS protocol and your Web server uses the HTTP protocol,
ensure that you configure all Cognos products to use relative URLs.
Ensure that your Web server and proxy server use the same protocol.
Ensure that your proxy server uses the HTTP protocol and your Web server uses the
HTTPS protocol.
ISO-8859-15 Encoding
This release supports ISO 8859-15 encoding. If your server runs on ISO 8859-15, the server
has to ensure that all reports on the server are writable.
A PowerPlay report is typically generated by PowerPlay for Windows. All characters saved in the
report are encoded with Windows-1252. Because the euro code point is different for
Windows-1252 and ISO 8859-15, PowerPlay needs to convert the report from Windows-1252 to
ISO 8859-15 the first time it is executed.
Mounting Cognos CDs Using the Rock Ridge Method

On HP-UX, if a Cognos CD is not mounted using the Rock Ridge method, or if the Rock Ridge
procedure is not completed correctly, you may see results such as file names not displayed
correctly (all uppercase or all lowercase characters), or a semi-colon (;), or period (.) may
appear at the end of each file name.
To ensure that the Rock Ridge method works as expected, verify that
you followed the Cognos installation guide procedures when mounting the CDs
networking is properly configured including network loopback
nfs.core and nfs.client subsystems are running
PATH includes the directory that contains the PFS utilities
Locales Mapped Incorrectly on Solaris 2.6

When you install Series 7 components on Solaris 2.6, the following locales are mapped
incorrectly and are therefore unavailable:
English - Great Britain
Finnish
Hebrew
If you try to perform an Apply after setting the locale to any of these values, you will get an error
and a default locale will be used. This occurs because the Native Locale name for these locales
changed between Solaris versions 2.6 and 2.7. Configuration Manager is shipped with locale
information for Solaris 2.7.
You can replace the localemap.xml files with a version for Solaris 2.6.
Steps to Replace the localemap.xml File

1. Download the Solaris 2.6 version of localemap.xml from the Cognos Support Web site
(http://support.cognos.com).
2. Replace the localemap.xml file in the installation_location/bin directory with the version you
downloaded.
3. Stop and then Start all Cognos services.
You can select and apply any locale without errors.
Common Problems
This section provides troubleshooting information for common installation and configuration
problems, including those that may occur while using Cognos samples. If your problem is not
listed here, see the Installation Testing and Samples Setup Guide. It contains troubleshooting
information for a wide variety of installation and configuration problems.
Cannot Find Samples Folder or Files

If the Cognos samples folder or files cannot be found on the server, then the Cognos sample
files have not been installed. Perform a custom installation of the Cognos sample files for your
product, then perform the following steps.
Solution Steps
Manager.
2. Perform an Apply on Samples Database Information.
Cannot Open a Sample File

If you cannot open a Cognos sample file or one of your own files, the problem could be caused
by one of the following:
File Access Permissions Do Not Permit You to Open a Cognos Sample File
Sample Files are Not Installed Properly or Cannot Be Read
Your File Was Created With a Previous Version
Incorrect Database Driver
No Connectivity With a Data Server
File Access Permissions Do Not Permit You to Open a Cognos Sample File
If you installed the Cognos sample files but cannot open them, you might not be a member of a
user class (on Windows) or user group (on UNIX) that has access to the Cognos sample files.
Solution
Ask your server administrator to verify that the access permissions for the Cognos sample files
include you.
Samples Files are Not Installed Properly or Cannot Be Read

If you installed the Cognos sample files but cannot open them, the installation wizard may have
encountered problems while installing the Cognos sample files.
You can look at the transfer log error file for entries that identify problems transferring the
Cognos sample files to your computer. The transfer log file is located in the installation location.
The file name includes the product name, the build number, and a date stamp. Below is an
example of the filename format:
tl-PP-7-0-517-0-20011104_0942.txt
Solution
Perform a custom installation of the Cognos samples files for the product.
Your File Was Created With a Previous Version

If your file was created with a previous version of Cognos software, it may not be compatible.
Solution
Follow the upgrade procedures in the installation guide to make your data files compatible with
Cognos Series 7 products.
Incorrect Database Driver

You need the correct database driver to use the sample databases on Windows. The correct
database driver is Microsoft Access Driver (.mdb), and the filename is odbcjt32.dll. This driver is
installed with Microsoft Data Access Component (MDAC) 2.7.
Solution
1. Verify that you have the correct database driver installed.
If you followed the instructions in the installation guide to perform a default installation, then
you already verified the system requirement to have MDAC 2.7 installed.
2. If necessary, install MDAC 2.7 from your Cognos installation CD. See the Additional
Products and Services chapter in the installation guide for more information about installing
this third-party product.
3. Use Configuration Manager to perform an Apply and a Start on the computer.
No Connectivity With a Data Server

There may be problems with the connection between your computer and a data server. Possible
problems include incorrect port numbers and network connectivity problems.
Solution
1. From your computer, ping the server by computer name.
If the ping is successful, proceed to step 3.
2. From your computer, ping the server by IP address.
If this ping is unsuccessful, there is a network problem or the server is not running.
If this ping is successful and the ping by server name was unsuccessful, there is a problem
connecting with the server name. If the server name that you pinged in step 1 exists and is
running, the Domain Name System (DNS) may be unable to translate the server name to
the correct IP address. To resolve this, you may need to edit the host file.
3. Use Configuration Manager to verify that the configuration values, such as port numbers
and server names, are correct.
4. If changes are necessary, stop the service, make any necessary changes, and then perform
an Apply and a Start on the computer.
Ticket Server Not Responding

If you are using Access Manager - Administration, you may receive a message that tells you that
the ticket server is not responding.
This problem can occur if the configuration values for the ticket server are incorrect, or if the
Ticket Server is not running, or if the ticket server cannot be pinged.
Solution
Manager.
2. Expand Services, Access Manager - Ticket Server, and click General.
3. Verify that the configuration values for the ticket server are correct and update them if
necessary.
Note: The default port for the Cognos Series 7 Ticket Server is 9010. Previous versions
used port 999.
4. Perform an Apply and a Start on Access Manager - Ticket Server.
5. Expand Services, Access Manager - Directory Server, and click General.
6. Verify that the ticket server port number listed in Access Manager - Ticket Server and the
ticket server port number listed in Access Manager - Directory Server are the same.
7. Verify that the Ticket Server Computer listed in Access Manager - Directory Server is
the name of the computer where the ticket server is installed.
8. Perform an Apply and a Start on Access Manager - Directory Server.
Cannot Start and Stop Ticket Server Using Configuration Manager

You may be unable to use Configuration Manager to start and stop Cognos Ticket Server
services.
This problem can occur if you did not upgrade to the Cognos Series 7 Ticket Server. Earlier
versions of the Ticket Server will work with Cognos Series 7 products, but you cannot start and
stop the Ticket Server from Configuration Manager unless you upgrade to the Cognos Series 7
Ticket Server.
Solution
Upgrade your Ticket Server to Cognos Series 7 by performing a custom installation of the Ticket
Server from the installation CD. See the installation guide for more information.
When you upgrade to the Cognos Series 7 Ticket Server, it will be installed in the
Cognos\TicketServer folder. Earlier versions of the Ticket Server were installed in the
Cognos\cer1 folder.
You can continue to use the cern version of the Ticket Server with earlier Cognos products, or
you can use the Cognos Series 7 version of the Ticket Server. If you use the Cognos Series 7
version, check the configuration values for your products to ensure that they can connect to the
Cognos Series 7 Ticket Server. The default port value for the Cognos Series 7 Ticket Server is
9010. Earlier versions used port 999 as the default value.
Access Manager Service Failure or Problems with Authentication or

Access Privileges
You may receive one of two messages if Access Manager fails.
If you are using PowerPlay Enterprise Server Administration, you may receive an error message
about an Access Manager service failure.
If you are using a remote installation of Upfront or PowerPlay Enterprise Server Administration,
you may receive an error message telling you that the administration server has not been
previously authenticated or does not have the proper access privileges.
Both of these problems could be caused by one of the following:
Ticket Server Configuration Values Incorrect
Ticket Server Not Installed
Ticket Server Not Running
Ticket Server Configuration Values Incorrect

If the configuration values for the ticket server are not set properly, the ticket server will be
unable to communicate with the dispatcher.
Solution
Use Configuration Manager to verify that the configuration values for the ticket server are
correct.
Steps
1. On the computer where the ticket server is installed, start Configuration Manager.
2. Expand Services, Access Manager - Ticket Server, and click General.
necessary.
Note: The default port for the ticket server is 9010. Previous versions used port 999 as a
default. Verify that the port listed for Access Manager - Ticket Server and the ticket server
port listed for Access Manager - Directory Server are the same.
4. Perform an Apply and a Start on Access Manager - Ticket Server.
Ticket Server Not Installed

The ticket server must be installed to work with Access Manager and PowerPlay Enterprise
Solution
1. Perform a custom installation of the ticket server.
necessary.
Note: The default port for the ticket server is 9010. Previous versions used port 999 as a
default. Verify that the port listed for Access Manager - Ticket Server and the ticket server
port listed for Access Manager - Directory Server are the same.
3. Perform an Apply on Access Manager - Ticket Server.
4. Perform a Start on Access Manager - Ticket Server.
Ticket Server Not Running

The ticket server must be running to work with Access Manager.
Solution
Start the ticket server to ensure that it is running.
Steps for Windows

1. On the computer where the Ticket Server is installed, use the Services tool in Control
Panel to check whether Cognos Ticket Server is running.
Note: It is possible that the ticket server is not running properly, even if it appears to be
running.
2. If the ticket server is running, stop it.
Manager.
4. Perform a Start on Access Manager - Ticket Server in Services.
Steps for UNIX

1. Use the following command to check whether the ticket server is running:
ps -ef | grep TicketServerd
Note: It is possible that the ticket server is not running properly, even if it appears to be
running.
3. If Access Manager - Ticket Server is running, stop it.
You can find Access Manager - Ticket Server within Services.
4. Perform a Start on the ticket server.
Cannot Establish Connection to NoticeCast Data Store After Applying

Default Configuration
If you encounter an error in NoticeCast when performing a default apply, a problem with
connecting to the data store has occurred. The problem could be caused by one of the following:
Data Store User ID or Password is Incorrect
Database URL is Incorrect for Your Database
Database Computer Not Running or Network Not Available
Database Not Set Up to Contain the NoticeCast Data Store
Data Store User ID or Password is Incorrect

The user ID and password used to access the database data store is not recognized.
Solution
1. Verify the user logon ID and password for accessing the data store with your database
administrator.
Manager.
3. Navigate to Cognos NoticeCast.NoticeCast Data Store.database Data Store Configuration
4. Change the user ID in the Data Store Logon ID parameter.
5. Change the user logon password in the Data Store Logon Password parameter.
Database URL is Incorrect for Your Database

If the database computer is running and network connections are fine, the URL specified in the
Database URL property in Cognos NoticeCast.NoticeCast Data Store.database Data Store
Configuration is not correct.
Solution
1. Verify the URL with your database administrator.
Manager.
3. Navigate to Cognos NoticeCast.NoticeCast Data Store.database Data Store Configuration
4. Change the URL for the database in the Database URL parameter.
Database Computer Not Running or Network Not Available

If the computer on which the database is located is not running or if you have a network
problem, NoticeCast server will not be able to establish a connection.
Solution
1. Ping the server using the database computer name.
2. If the database computer is responding, ensure the required services are running on it.
3. If the database computer is not responding, ping it using the IP address for the computer.
4. If the database computer is not responding, resolve the network connectivity issue then
retest the connection.
5. If the database computer is responding using the IP address but not the database computer
name, there is a problem with your network recognizing the relationship between the
database computer and the IP address. Resolve this problem with your network
administrator and test the connection.
Database Not Set Up to Contain the NoticeCast Data Store

The NoticeCast data store must be defined within the database in order for NoticeCast server to
be able to connect to the data store.
Solution
Ensure the database has been set up to contain the NoticeCast data store.
JDBC Driver Not Included in Class Path After Default Configuration

Performing an Apply of the NoticeCast configuration properties results in an error that the
defined JDBC driver is not included in the class path. NoticeCast uses Java Database
Connectivity (JDBC) to connect to the data store. If your NoticeCast data store is within an SQL
server database, you have a suitable driver installed already. If your data store is within Oracle,
Informix, or DB2, you must locate the driver in your installation directories and ensure that this
location is specified in Configuration Manager configuration properties. Note that Java is case
sensitive.
Solution
1. Ensure in Configuration Manager the Data Store Connection File parameter at Cognos
NoticeCast.NoticeCast Data Store.General is set to the correct database type.
2. Ensure that in Configuration Manager the database JDBC Driver File parameter at Cognos
NoticeCast.NoticeCast Data Store.database Data Store Configuration is set to the correct
location and filename of your JDBC driver. The path and filename are case-sensitive in
UNIX. In the Configuration Manager property path used above, database indicates the type
of database in use.
Appendix E: Additional Products and Services

You may need to install and configure third-party products that work with Cognos Series 7. You
may already have these products installed and configured, or you may be using an alternative
product such as Windows 2000 Active Directory instead of Sun ONE Directory Server.
Install Distributed Component Object Model

Distributed Component Object Model (DCOM) is applicable only for Windows 98 computers.
DCOM is provided by default with Windows 2000 and Windows NT.
You must have a compatible version of DCOM on every Windows 98 computer that runs a
Cognos product. DCOM is a protocol that enables software on different computers to
communicate over a network.
Steps to Verify if DCOM is on Your Computer

You can verify if DCOM is installed on your computer by starting Distributed COM Configuration
utility.
1. From the Start menu, click Run, and then type dcomcnfg
2. Click OK.
The Distributed COM Configuration Properties window appears.
Steps to Install DCOM on Windows 98

and then double-click the Microsoft folder, DCOM folder, and dcom98.htm.
If no installation menu appears, navigate to the Support Files\Microsoft\DCOM folder on

the CD and click dcom98.htm.
If you are installing from your network, double-click dcom98.htm in the DCOM folder
where your administrator copied the third-party support files.
The Install Microsofts Distributed COM 1.3 for Windows 98 page appears.
2. Follow the instructions to access the download page.
3. On the download page, select the DCOM for Windows 98 configuration utility option.
4. Restart your computer after the installation is finished and before you install any other
software.
Install Microsoft Data Access Components

Microsoft Data Access Components (MDAC) is applicable only if you are using the Cognos
product samples.
MDAC includes the ActiveX, OLE DB, and ODBC drivers that your operating system needs to
access diverse data sources. Some of the samples provided with Cognos products require your
computer to be equipped with database drivers.
Many applications require MDAC and it is likely already installed on your computer. You can first
determine the version you have installed so you will know whether an upgrade is necessary for
Note: For Windows 98 computers, you must install Microsoft Distributed Component Object
Model (DCOM) before you install MDAC.
Steps to Verify Your Current Version of MDAC

1. In Windows Explorer, search the drive where you installed the operating system for two
specific .dll files associated with MDAC (Msdadc.dll and Oledb32.dll).
2. Right-click the file name and click Properties.
3. Click the Version tab and note the file version number.
4. Access the Microsoft Web site to compare this file version number to the corresponding
MDAC version using the reference table provided on the Web site.
Steps to Install MDAC

and then double-click the Microsoft folder, MDAC folder, and mdac_typ.exe.
If no installation menu appears, navigate to the Support Files\Microsoft\MDAC folder on

the CD and click mdac_typ.exe.
If you are installing from your network, double-click mdac_typ.exe in the MDAC folder
2. Follow the instructions in the Installation Wizard.

software.
Install Microsoft JVM

Microsoft Java Virtual Machine (JVM) must be installed on Windows NT and Windows 98
computers for Cognos NoticeCast client. Windows 2000 SP2 computers have the JVM by
default.
Steps to Verify if JVM is on Your Computer

1. Click Start, Programs, Command Prompt to open a DOS window.
2. Type wjview and press Enter.
If the WJView Help window appears, you have JVM on your computer. If the command is
not recognized, you do not have JVM on your computer and you must complete the steps to
install it.
Steps to Install JVM

and then double-click the Microsoft folder, JVM folder, and msjavx86.exe.
If no installation menu appears, navigate to the Support Files\Microsoft\JVM folder on

the CD and click msjavx86.exe.
If you are installing from your network, double-click msjavx86.exe in the JVM folder
2. Change the directory to the installation_location\bin.

The default location is Program Files\Cognos\cer3\bin
software.
Configure Windows 2000 Active Directory

If you want to use Windows 2000 Active Directory instead of Sun ONE Directory Server, you
must first install Windows 2000 Active Directory, then install your Cognos product, and then
configure the Cognos product for use with Windows 2000 Active Directory. The configuration
adds a namespace in the directory server that Cognos products can use. Use Configuration
Manager to do this configuration. The configuration needs to be completed only once for the
directory server, not for every computer that accesses the directory server.
Manager that is installed on a Windows 2000 computer. Otherwise, you must first install an
ADSI patch on your Windows NT or Windows 98 computer as described in a following section.
Steps
Manager.
2. From the Welcome page, click the Start tab.
Configuration Manager opens with your computers current configuration shown.
4. In the Explorer window, expand the Services, then expand Access Manager - Directory
Server.
6. Type the following values for the corresponding General property.
Property
Value
Are you sure you want The default is No.

to configure this
Change this property to Yes or other
directory server?
property changes will not take effect.
Schema Version

defaults.
The displayed default is Current.
If you are still using your directory server
with Cognos Series 7.0 and earlier
products, you must change the value to
Compatible with Series 7.0 and earlier
versions.
If you are only using your directory server
with Cognos Series 7 Version 2, we
recommend that you use the default
value Current.
Notes
You must be ready to switch
permanently to Cognos Series 7
Version 2 before you upgrade to the
Current schema version.
If upgrading from an older version of
a directory server, you must change
the value to Compatible with Series
7.0 and earlier versions in order to
restore the directory server data from
the .ldif.
Property
Value
Server Type
A list of supported directory servers.

The default is Auto-Detect.
Change the property to Active Directory.
Computer

where the directory server is installed.
Port
The port that is connected to the directory

server.
The default is port 389.
If you used a different port for the Active
Directory server, specify the new port
number.
Base distinguished
name (DN)
A distinguished name (DN) which will be

the first entry in the directory tree creating
a branch for your data.
The default base DN used by Active
Directory is
o=company, dc=domain name
Specify the values you used to define the
base DN. For example, if your company
name is mycompany and your domain
name is thisplanet.com, the DN is
o=mycompany, dc=thisplanet,
dc=com
Unrestricted user
distinguished name
(DN)

administrator uses to manage the
contents of the directory server with
unlimited privileges.
dc=domain name
unrestricted user DN. If your domain
name is thisplanet.com, the dc value is
dc=thisplanet, dc=com
Unrestricted user
password

password
Ticket server host

where the ticket server is installed.
Ticket server port
The port that is connected to the ticket

server.
Property
Value
Default Namespace
Name
The name of the default namespace to be

used by Cognos products. This
namespace is the one Access Manager
references.
The default name is default.
Default Namespace
Administrator Name
The name used by the administrator.
Default Namespace
The signon used by the administrator

when accessing the default namespace.
The default name is Administrator.
The default is Administrator.

Default Namespace
Administrator
Password
The password used by the administrator.

The default is to use no password.
7. In the Explorer window, click the General category, and from the Actions menu, click
Validate Selection.
A message indicates if the properties were validated successfully. If errors occurred, make
corrections and retry the validation.
8. From the Actions menu, click Apply.
9. Click Directory Server and type the following values for the corresponding property.
Property
Value
Host

where the directory server is installed.
Port/SSL Port
The port that is connected to the directory

server.
If you used a different port for the Active
Directory server, specify the new port
number.
Base DN
A distinguished name (DN) which will be

the first entry in the directory tree creating
a branch for your data.
The default DN used by Active Directory
o=company, dc=domain name
base DN. For example, if your company
name is mycompany and your domain
name is thisplanet.com, the DN is
o=mycompany, dc=thisplanet, dc=com
Timeout
The directory server timeout value.

The default value is 0.
Default Namespace
The name of the default namespace.

The default name is default.
Property
Value
Local Cache Enabled
Whether local authentication cache files

are stored on the local computer.
The default is Yes.
This value should be set to No if Cognos
application servers are installed on this
computer.
Local Cache File
The location and name of the local cache

file.
The default name is default.lac and the
file is located in the bin folder under the
installation_location where you installed
SSL Enabled
Whether the directory server has Secure

Sockets Layer enabled.
The default is No.
10. In the Explorer window, click the Directory Server category, and from the Actions menu,
click Validate Selection.
A message indicates if the properties were validated successfully. If errors occurred, make
corrections and retry the validation.
11. Click OK.
12. In the Explorer window, click the Services component, and from the Actions menu, click
Apply.
ADSI Patch for Windows 98 and Windows NT

If you are using Configuration Manager that is installed on a Windows 98 or Windows NT
computer to remotely configure Windows 2000 Active Directory, you may receive the following
error message after you apply your configuration settings:
We were not able to load the directory server configuration DLL. Please contact customer
support.
To correct this problem, you need to install an ADSI Runtime patch on the computer that
contains Configuration Manager. This patch enables Configuration Manager to remotely
configure Windows 2000 Active Directory. You can find the setup files in the \Support
Files\Microsoft\ADSI folder on the Cognos Supplementary Software CD.
Steps
Run the ADSI Runtime setup file that corresponds to the platform on which you have
Configuration Manager installed.
For Windows 98 computers, double-click ads95.exe.
For Windows NT computers, double-click ads.exe.
Install Adobe Acrobat Reader

Adobe Acrobat Reader is required to view the PDF online books provided with Cognos Series 7
products. The Acrobat 5.0.5 Accessibility and Forms patch provides enhanced accessibility
features when viewing and creating Adobe PDF files.
Note: You must install Adobe Acrobat 5.05 before installing the Accessibility and Forms patch.
Steps to Install Adobe Acrobat

click the Adobe and Acrobat folders, and then click rp505enu.exe.
If no installation menu appears, navigate to the Support Files\Adobe\Acrobat folder

on the CD and click rp505enu.exe.
If you are installing from your network, double-click rp505enu.exe in the folder where
your administrator copied the third-party support files.
Steps to Install Adobe Acrobat Accessibility and Forms Patch

click the Adobe and Acrobat folders, and then click rp505afp1.exe.
If no installation menu appears, navigate to the Support Files\Adobe\Acrobat folder

on the CD and click rp505afp1.exe.
If you are installing from your network, double-click rp505afp1.exe in the folder where
your administrator copied the third-party support files.
Appendix F: Installation Checklist for Windows
Check system requirements.

Verify that you have Administrator privileges on Windows (all products).
Create a TEMP system variable (all products).
Install a Directory Server (most products, not required for minimal installations or client
products).
Install ObjectStore (if required, not required for minimal installations).
Install Cognos Series 7 products.
Complete configuration tasks.
Test the installation.
Check System Requirements

For an up-to-date list of the software environments supported by Cognos products; including
database servers, OLAP servers, and more; see the Cognos support site.
Use the following checklist to record your specifications.
Computer/Server name:
_____________
Operating System
_____________
RAM
_____________MB
CPU
_____________
disk space for directory server
_____________MB
not required for minimal installations

disk space for ObjectStore data store. _____________MB
not required for minimal installations
Disk Space for all Cognos Series 7
products
_____________GB
Ping Server?
Yes / No
Ping Server-IP?
Yes / No
Check Additional System Requirements

Web browser and Web server (default port 80)
(for Cognos Series 7 Query, Reporting, Visualization, OLAP and
Alerts/Notifications, and Impromptu Administrator if using
PowerPrompts)
Yes / No
Adobe Acrobat Reader?
Yes / No
(available from CD installation menu, Support Files)

DCOM (only required if using Windows 98)
Yes / No
MDAC Service Pack (only required for product samples)
Yes / No
(available from CD installation menu, Support Files)

Java plug-in (for Cognos Query Administration tool)
Yes / No
printer driver
Yes / No
set up database connectivity
Yes / No
third-party database, Oracle, Informix, DB2, or Microsoft SQL

Server (for NoticeCast in Cognos Series 7 Alerts/Notifications)
Yes / No
database type
_____________
JDBC driver (for NoticeCast in Cognos Series 7

Alerts/Notifications)
driver file name
Microsoft Java Virtual Machine (JVM)

(for NoticeCast client on WIndows NT)
Yes / No
Access to email server (for NoticeCast Cognos Series 7

Alerts/Notifications)
SMTP server
name
_____________
_____________
SMTP Logon
name
_____________
SMTP Logon
password
_____________

Administrator privileges on Windows computer?
Yes / No
Create TEMP System Variable

TEMP system variable created?
Yes / No
TEMP directory location
____________
Install a Directory Server

This step applies to most Cognos Series 7 products. It does not apply for client products or
minimal installations. If you dont already have a Sun ONE Directory Server or Windows 2000
Active Directory installed, install from the Cognos Supplementary CD. Follow the instructions in
the Supplementary Software Installation Guide (for Sun ONE Directory Server) or in the
Additional Products and Services appendix in your Installation Guide (for Windows 2000 Active
Directory).
Configure a Domain Name System (DNS).
default DNS: yourcompany.com
____________________
Install Sun ONE Directory Server with default settings for use as the configuration directory.
Create a second directory server for use as the data directory.
Settings for Sun ONE Directory Server - Configuration Directory

Cognos
Default Value
Value you used
Server Identifier
(Server name)
computer name
_____________
Server Port
any available port, but we _____________

recommend saving port
389 for the data directory
Suffix
(Database Suffix)
o=Cognos, c=CA
_____________
Configuration Directory
Administrator ID
admin
_____________
Password
admin1234
_____________
Administration Domain
yourcompany.com
_____________
Option
Directory Manager (DN) cn=Directory Manager
_____________
Password for Directory

Manager
admin1234
_____________
Administration Port
20000
_____________
Settings for Sun ONE Directory Server - Data Directory
Option
Cognos
Default Value
Value you used
Server Identifier
(Server name)
computer name followed by a

number (as presented in the
user interface)
_____________
Network Port
port 389
_____________
Base Suffix
(Database Suffix)
o=Cognos, c=CA
_____________
Root DN
cn=Directory Manager
_____________
admin1234
_____________
(Directory Manager)
Password for Root DN
Install ObjectStore
This step applies to
Cognos Series 7 PowerPlay Transformer Edition if installing Architect (not provided with a
minimal installation)
Cognos Series 7 Impromptu Administrator if installing Architect (not provided with a minimal
installation)
Follow the installation instructions in "Preparing for the Installation" in your installation guide.

The following table shows the values used by a default installation.
Option
Default Value
Value you used
ObjectStore Ports
Server
Notifications
_____________
Transaction log file name
osserver.log
51025
51031
51041
51050
_____________
_____________
_____________
_____________

Install products
Impromptu Web Reports for Windows
Yes / No
Yes / No
Check that the following services are started.

Service
Started?
Cognos Impromptu Web Reporting Service

Manager
Yes / No
Yes / No
Yes / No
Yes / No
Cognos Upfront File Manager (shared)
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide.

Install products
Cognos Query for Windows
Yes / No
Cognos Query Modeling
Yes / No

Service
Started?
Yes / No
Yes / No
Cognos Query Server Manager
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
installation guide.

Install products
Yes / No
PowerPlay User
Yes / No

Service
Started?
Cognos PowerPlay Enterprise Server
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
installation guide.

Install products
Yes / No
Cognos Visualizer Authoring
Yes / No

Service
Started?
Cognos Visualizer Web Edition
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
installation guide.

Install products
PowerPlay Transformer Edition for Windows
Yes / No

Install products
Cognos NoticeCast for Windows
Yes / No
Cognos NoticeCast Authoring
Yes / No

Service
Started?
Cognos NoticeCast Dispatcher
Yes / No
Cognos NoticeCast Data Store
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
installation guide. For existing installations you can use Configuration Manager to generate
a report that includes details about your Cognos environment including port numbers.

This step applies to
Cognos Series 7 Impromptu Administrator if you installed PowerPrompts
Follow the instructions in the installation guide to create Web aliases for your specific Web
server.
You must substitute the installation_location in the Location column with the location where you
installed the Cognos product, for example d:\Program Files\Cognos.
Alias
Location
Permission
cognos
Read
Alias
Location
Permission
Execute
cognos/help
Read
Using Cognos Visualizer with iPlanet

If you are using Cognos Visualizer with iPlanet Web server, you must edit the iPlanet obj.conf
file and set up two additional aliases. The following aliases are not required by other Cognos
products, or if you are using Cognos Visualizer with a different Web server.
Alias
Location
Style
cognos/plugin
installation_location/webcontent/ Download
plugin
cognos/download
installation_location/webcontent/ Download
viz/download
Complete Required Product-Specific Configuration

Even if you did a default installation of all the components and accepted all default settings for
configuring your Cognos products, Cognos NoticeCast requires additional configuration.
Complete the NoticeCast Configuration.
Follow the instructions in "Finishing the Installation" in your installation guide.
Note: The remainder of the Installation Checklist is required only if you chose a custom
installation.

This step applies only to custom installations or upgrades whether you are using Sun ONE
Directory Server or Windows 2000 Active Directory with the following products:
Cognos Series 7 Impromptu Administrator (only for Impromptu Administrator if you installed
Architect and Access Manager components)
For this task, use Configuration Manager graphical user interface or command line interface to
configure the General properties in the Services, Access Manager - Directory Server
component. Specify the settings you used when installing your directory server so that Cognos
products know how to communicate with the directory server.
Note: By completing these steps, a namespace is automatically created in your directory server.
Configure the Authentication Source

This step applies only to custom installations whether you are using Sun ONE Directory Server
or Windows 2000 Active Directory with the following products
Cognos Series 7 Impromptu Administrator (only for Impromptu Administrator if you installed
Architect and Access Manager components)

For this task, use the Configuration Manager graphical user interface or command line interface
to configure the Authentication Source, Directory Server properties in the Services, Access
Manager - Runtime component. Specify the authentication source that the Cognos products use
to find security information (i.e., the directory server namespace).
Note: You must complete this task on every computer on which you installed Cognos
components.
Configure Server Locations for a Distributed Installation

This is a two-part configuration task and applies to all products if you are doing a distributed
installation. The components you would commonly install on a separate computer are the
directory server, ticket server, and the server gateways.
You can use Configuration Manager graphical user interface or command line interface to
specify the location of these distributed components so that communication can occur.
Follow the instructions in this guide to configure the applicable property value in the object
hierarchy.
You must ensure that each computer in the server environment has the same copy of the
server configuration file (cern.csx).
Follow the instructions in this guide to manage the file.
Apply Defaults or Change Product-Specific Configuration

You can simply complete the configuration of a Cognos product by applying the default values or
optionally change any setting before applying the configuration. For example, you may want to
change the default port number that is associated with a specific component.
Follow the instructions in this guide to configure component settings.
Start All Services and Processes

Use Configuration Manager to start all services in Windows and its command line interface to
start all processes on UNIX after you have completed all the required configuration and any
optional configuration you want to apply.
Follow the instructions in this guide to start services and processes. In a default installation, the
services and processes are started automatically.
Note: The testing task is optional, but can be completed whether you chose a default or custom
installation.
Test the Installation

Follow the instructions in "Testing the Installation" in your installation guide.
Index
Symbols
.ats script, 176
.ccs files, 194
.cfx files, 153
.csa files, 123
.dmd files, 142, 157, 184
.dmi files, 142, 157, 184
.dmp files, 142, 157, 184
.pkg files, 138
.ppx files, 153
.txt files
cfa-nnn.txt, 193
cfe-nnn.txt, 194
cmplst.txt, 194
tl-nnn.txt, 193
tl-nnn_summary-error.txt, 193
A
Access Manager
runtime, 90, 113
troubleshooting, 198
Access Manager Administration, 28, 31, 34, 36, 38, 42, 44,
46
adding connections, 122
testing ticket server, 123
Acrobat, See Adobe Acrobat Reader
Active Directory
configuring, 88, 110
configuring remotely, 90, 113
administration tools
Cognos Server Administration, 28, 31, 34, 44
NoticeCast, 38, 117
testing, 124
administrative installations
setting up, 178
administrator privileges, 100
verifying in Windows 2000, 62, 78, 100
verifying in Windows 2003, 12
verifying in Windows NT, 62, 78, 100
verifying in Windows XP, 62, 78, 100
Adobe Acrobat Accessibility and Forms Patch
installing, 209
Adobe Acrobat Reader
installing, 208, 209
Alerts/Notification
default ports for Windows, 51
aliases
Web server, 68, 84, 106
alternative upgrades
Cognos Visualizer, 183
PowerPlay Enterprise Server, 183
applying
configuration, 95, 119
Architect, 29, 31, 36, 41
testing with Impromptu, 125
upgrading, 166
assigning
themes to users, 141
authentication source
authoring tools
NoticeCast, 38
B
backing up
data in case of rollback, 132
C
cdmdefine, 145, 147, 159, 161, 185, 187, 188
cdmpack, 145, 159, 186
cdmunpack, 148, 162, 188
cern.csx files, 194
cfa-nnn.txt, 193
cfe-nnn.txt, 194
cgi-bin directory
creating in Windows 2003, 12
changing default values
checklists, 211-218
files for completing upgrade, 133
preparing for upgrade, 132
Cleanup utilities
client products
upgrading data, 165-166
cmplst.txt, 194
code examples, See samples
Cognos components
copying, 81, 103, 104
services, 96, 120
Cognos NoticeCast
administration, 117
authoring, 117
configuring, 17, 71, 91, 114
data store, 115
server, 114
services, 116
upgrading the data store, 116
Cognos OLAP
Cognos Query
add to 7.1 configuration, 143
data store, 30
dispatcher, 30
gateway, 30
packing metadata, 142-145
samples, 32
server, 30
tools, 32
upacking metadata, 145-148
Index
Cognos Query (cont'd)
upgrading, 142
Cognos Query Administration
testing, 125
Cognos security administration (.csa) file, 123
Cognos Series 7
upgrading, 103
tools, 28, 31, 34, 38, 44
Cognos services
stopping, 66, 81, 103
Cognos services, See services
Cognos Supplementary Software CD, 46
add to 7.1 configuration, 157
alternative upgrades, 183
authoring tool, 45
configuring iPlanet Web server, 71, 87
dispatcher, 43
gateway, 43
pack data, 158
pack data using 7.1 CDM, 157
query processor, 43
Quick Tour, 45
samples, 45, 46
testing server, 127
tools, 44, 46
unpack data, 160
unpack data using 7.1 CDM, 160
upgrading options, 156, 188
upgrading visualizations, 166, 189
Cognos Visualizer Server Administration
testing, 127
Cognos Visualizer Viewer, 45
Cognos Visualizer Web Client, 45
Cognos Visualizer Web Server
upgrading, 189
Cognos Windows Common Logon Server, 34
collating sequences
testing, 128
components
applying configuration, 119
in-place upgrades, 131
list file, 194
sequence for starting, 96, 119
services, 96, 120
shared, 56
staged upgrades, 131
stopping services, 66, 81, 103
uninstalling, 171
upgrading, 103
workstation installations, 179
configuration
activity report, 193
applying, 95, 119
error report, 194
specification file, 194
Windows 2003, 11
configuration files, 56
applying configuration, 95, 119
changing property values, 90, 113
disabling Upfront File Manager, 16
processes, 95, 119
Configuration Manager (cont'd)

services, 95, 119
setting docRoot, 15
setting the ODBC gateway on UNIX, 17
settings, 15
starting processes, 95, 119
starting services, 95, 119
troubleshooting, 193, 198
using, 84, 106
configuring
Active Directory, 88, 110
administration tools, 117
Cognos components, 83, 105
Cognos NoticeCast, 17, 71, 91, 114
component settings, 90, 114
components, 95, 119
components using unattended configuration, 177
data stores, 115
directory servers, 88, 110
domain name system in Windows 2003, 13
iPlanet for multiple NSAPI server groups, 18
iPlanet Web server for Cognos Visualizer, 71, 87
mixed version environments, 23, 56
mulltiple instances, 91
multiple server groups, 23
Netscape Directory Server, 88, 110
NoticeCast, 91, 114
NoticeCast authoring, 117
property values, 90, 113
relative URLs, 23
Web server, 68, 84
Web server in Windows 2003, 12
Windows 2000 Active Directory, 205
connectivity problems
conventions
used in upgrade instructions, 134
copying
Cognos components, 81, 103, 104
copyright, 2
creating
cgi-bin directory in Windows 2003, 12
help directory in Windows 2003, 13
TEMP system variable, 62, 78, 100
webcontent directory in Windows 2003, 12
current directory server schema version, 169
custom installations, 24, 77, 99
checklists, 211-218
D
data
backing up in case of rollback, 132
data store
users, 64, 79, 101
data stores
Cognos Query, 30
Impromptu Web Reports, 27
NoticeCast, 38, 115
packing Cognos Query, 144
packing Impromptu Web Reports, 148
packing Upfront, 138
unpacking Cognos Query, 146
unpacking Impromptu Web Reports, 149-152
unpacking Upfront, 139-141
Upfront, 27, 31, 33, 37, 43
upgrading NoticeCast, 116
Index
data stores (cont'd)
upgrading NoticeCast gateway URLs, 162
database users
creating for NoticeCast, 64, 79, 101
databases
setting environment variables, 64
DCOM, See Distributed Component Object Model
default installations, 23, 61-76
using with minor changes, 24
default response .ats file, 176
default settings
namespace, 48
user IDs and passwords, 47
dependencies
starting components, 96, 119
Deployment Manager
pack Cognos Visualizer data, 157
pack PowerPlay Enterprise Server data, 184
unpack Cognos Visualizer data, 160
unpack PowerPlay Enterprise Server data, 186
upgrading Cognos Query, 144, 146
upgrading Cognos Visualizer, 158, 160
upgrading PowerPlay Enterprise Server, 187
directory servers, 102
adding connections, 122
testing, 122
upgrading to current schema, 169
Windows 2000 Active Directory, 205
disabling
Upfront File Manager, 16
dispatcher
Cognos Query, 30
Distributed Component Object Model (DCOM)
installing, 203
distributed installations
dependencies, 96, 119
distributed sorting
testing, 128
DNS
configuring in Windows 2003, 13
docRoot property, 15
document
version, 2
dsdump, 149
dsload, 149, 150, 151
E
email address
NoticeCast, 72, 92, 115
environment variables
databases, 64
environments
mixed version, 55
supported, 99
error messages, See troubleshooting
examples
mixed version environment, 55, 56
examples, See samples
F
file extensions
alternate extensions for .cgi files, 14
file managers
Upfront, 28, 31, 33, 38
files
required for completing upgrade, 133
G
gateways
alternate file extensions for .cgi files, 14
Cognos Query, 30
ISAPI, 68, 84, 107
NSAPI, 68, 84, 107
updating URLs in NoticeCast, 162
updating URLs in Upfront, 163, 190
Upfront, 27, 31, 33, 37, 43
Geoset Manager, 46
H
help directory
hybrid installations, 25
I
Impromptu, 40
Quick Tour, 30, 41, 42
samples, 41, 42
testing, 125
tools, 40
upgrading, 165
Impromptu Administrator, 29
tools, 29, 41, 42
data store, 27
gateway, 27
packing data store, 148
samples, 30
server, 27
testing, 125
tools, 29
unpacking data store, 149-152
upgrading, 148-152
in-place upgrades, 131
installation kits
Netscape Directory Server, 46
installation types, 23-26
installations
checklist, 211-218
copying, 104
custom, 24, 77, 99
default, 23
determining types to perform, 9
minimal, 23
multi-platform, 25
preparing, 100
selecting type of, 23
setting up on the network, 178
setting up unattended, 175
to upgrade
unattended, 26
Windows 2003, 11
Index
installing
Adobe Acrobat Accessibility and Forms Patch, 209
Adobe Acrobat Reader, 208, 209
Distributed Component Object Model (DCOM), 203
Microsoft Data Access Components (MDAC), 203
Microsoft Java Virtual Machine (JVM), 204
ObjectStore, 65, 80, 102, 103
Sun ONE Directory Server, 65, 80
Internet Explorer
enhanced security settings in Windows 2003, 14
Internet Information Services Settings
iPlanet
configuring for multiple NSAPI server groups, 18
modifying the obj.conf file, 18
iPlanet Directory Server See Sun ONE Directory Server
iPlanet settings
changing, 18
ISAPI gateway, 68, 84, 107
configuring, 18
ISO 8859-15 encoding
PowerPlay, 195
iwrsetup.sh, 149, 161
JDBC driver
JDBC driver path
upgrading in NoticeCast, 163
JVM, See Microsoft Java Virtual Machine
namespace
default settings, 48
namespaces
upgrading to current schema version, 169
naming conventions, 54
Netscape Directory Server
installation kit, 46
Netscape Directory Server, See Sun ONE Directory Server
network installations
setting up, 178
NewsIndexes
upgrading Upfront, 139-141
NoticeCast
authoring tool, 38
database users, 64, 79, 101
samples, 39
testing, 127
tools, 39
upgrading, 162
upgrading gateway URLs, 162
upgrading JDBC driver path, 163
NoticeCast data store, 38
NoticeCast servers, 37
NSAPI gateway, 68, 84, 107
configuring, 18
load balancing
between different versions when upgrading, 55
log files
troubleshooting resources, 193
obj.conf file
modifying, 18
ObjectStore
installing, 65, 80, 102, 103
stop services, 173
testing, 121
testing in Windows, 121
uninstalling, 173
upgrading, 102
using with Architect, 65
using with Impromptu Web Reports, 65
ODBC gateway
setting on UNIX, 17
opening, See starting
M
macros
upgrading, 166
MDAC, See Microsoft Data Access Components
messages, error, See troubleshooting
metadata
packing Cognos Query, 142-145
unpacking Cognos Query, 145-148
upgrading PPES, 152-156
Microsoft Data Access Components (MDAC)
installing, 203
Microsoft Java Virtual Machine (JVM)
installing on Windows 2003
Microsoft Virtual Machine (JVM)
installing, 204
minimal installation, 23
mixed version environments
configuring, 23, 56
example, 55, 56
installing, 55
upgrading, 55
modeling tools, upgrading, 166
modifying
obj.conf file, 18
modifying, See changing
multi-platform installations, 25
multiple instances, 91
P
pack setting file (.dmi), 142, 157, 184
package definition file (.dmd), 142, 157, 184
package file (.dmp), 142, 157, 184
packing data stores
Upfront, 138
packing metadata
Cognos Query, 142-145
packlets folder, 142, 157
parameters
dsdump, 148
dsload, 150
ppserver, 154
UpfPack, 138
UpfUpgrade -database, 139
passwords
Index
patches
ADSI for Windows 2000 Active Directory, 208
planning
installations, 100
upgrades, 131
planning_upgrade
port numbers, 56
ports
Alerts/Notification default for UNIX, 51
Cognos OLAP default for Windows, 51
Cognos Query default for Windows, 50
Cognos Visualizer Server, 52
configuring multiple instances, 91
Impromptu Web Reports default for Windows, 49
PowerPlay Transformer default for Windows, 52
troubleshooting numbers, 194
PowerPlay, 34, 36, 39
ISO 8859-15 encoding, 195
Quick Tour, 40
Quick Tours, 35, 37
samples, 35, 40
tools, 35, 40
alternative upgrades, 183
Cleanup utility, 33
dispatcher, 32
gateway, 32
pack data using 7.1 CDM, 184
query and report processors, 33
testing, 126
tools, 34
unpack data using 7.1 CDM, 186
upgrading metadata, 152
upgrading options, 183
upgrading security, 153
Windows Launch Agent, 33
PowerPlay Enterprise Server Administration
testing, 126
PowerPlay for Excel, 35, 36, 39
testing, 127
upgrading, 165
PowerPlay Transformer, 35
Personal Edition, 35, 39
samples, 37
testing, 126
testing with Architect, 126
tools, 36
upgrading, 166
PowerPlay User
testing connections to PowerPlay Enterprise Server, 126
upgrading, 165
ppserver, 153-155
PPSRoot directory
copying files, 152
preparing
installations, 100
problems, See troubleshooting
processes, 134
locating in object hierarchy, 96, 120
product
version, 2
production environment
custom installations, 24
properties
changing values, 90, 113
Q
query processors
Quick Tours
Impromptu, 30, 41, 42
PowerPlay, 35, 37, 40
R
relative URL support
configuration, 23
report processors
report store directories, 150
S
samples
Cognos Query, 32
Cognos Visualizer, 45, 46
Impromptu, 41, 42
NoticeCast, 39
PowerPlay, 35, 40
Schema Version, 88, 111, 205
schema versions, 169
scripts
.ats, 176
security
Internet Explorer settings in Windows 2003, 14
Internet Information Services settings in Windows 2003,
13
options, 46
specifying, 97, 113
upgrading namespaces, 169
upgrading PowerPlay Enterprise Server, 153
selecting
installation type, 23
server configuration files (cern.csx)
server groups
configuring multiple groups, 23
servers
Cognos NoticeCast, 114
Cognos Query, 30
Cognos Windows Common Logon Server, 34
NoticeCast, 37, 117
Upfront, 27, 30, 33, 37, 43
Upfront event, 28, 31, 33, 37, 43
Windows Common Logon Server, 28, 31, 36, 38, 39, 42,
43, 46
services, 134
Cognos Series 7 Alerts/Notification, 53
Cognos Series 7 Impromptu Administrator, 53
Cognos Series 7 OLAP, 53
Cognos Series 7 PowerPlay Transformer Edition, 53
Cognos Series 7 Query, 52
Cognos Series 7 Reporting, 52
Configuration Manager, 95, 119
locating in object hierarchy, 96, 120
NoticeCast, 116
Index
services (cont'd)
starting, 95, 96, 119, 120
stop ObjectStore, 173
stopping, 66, 81, 103, 104
setting up
network installations, 178
unattended configuration, 177
unattended installation, 175
settings
Configuration Manager, 15
configuring, 114
database environment variables, 64
docRoot, 15
Internet Explorer in Windows 2003, 14
Internet Information Services in Windows 2003, 13
shared components
uninstalling, 171
SMTP Server Name, 72, 91, 115
staged upgrades, 131
starting
NoticeCast, 116
sequence for components, 96, 119
services, 95, 96, 119, 120
starting components
dependencies, 96, 119
stop services
ObjectStore, 173
stopping
Cognos services, 66, 81, 103
installing, 65, 80
Sun ONE directory server, 102
support files
configuring Windows 2000 Active Directory, 205
installing Distributed Component Object Model (DCOM),
203
installing Microsoft Data Access Components (MDAC),
203
installing Microsoft Virtual Machine (JVM), 204
third-party products
Adobe Acrobat Reader, 208
third-party products required, 47
supported software, 99
system requirements
checklist, 211
UNIX components, 61, 77, 99
T
TEMP system variable
creating in Windows 2000, 63, 79, 101
creating in Windows NT, 62, 78, 100
creating in Windows XP, 63, 79, 101
temporary files, 100
testing
Architect with Impromptu, 125
Architect with PowerPlay Transformer, 126
Cognos Query Administration, 125
Cognos Visualizer server, 127
Cognos Visualizer Server Administration, 127
collating sequences, 128
directory servers, 122
Impromptu, 125
Impromptu Web Reports, 125, 152
NoticeCast, 127, 164, 191
ObjectStore, 121
testing (cont'd)
ObjectStore in Windows, 121
PowerPlay Enterprise Server, 126, 156
PowerPlay Enterprise Server Administration, 126
PowerPlay for Excel, 127
PowerPlay User connections, 126
sorting, 128
ticket server, 123
Upfront Server Administration, 124
Upfront Web access, 124
Web servers, 121
themes
assigning to users, 141
upgrading Upfront, 141
third-party products
configuring Windows 2000 Active Directory, 205
installing Distributed Component Object Model (DCOM),
203
installing Microsoft Data Access Components (MDAC),
203
installing Microsoft Virtual Machine (JVM), 204
required support files, 47
ticket server, 28, 31, 34, 38, 43
testing, 123
tl-nnn.txt, 193
tl-nnn_summary-error.txt, 193
tools
Cognos Query, 32
Cognos Server Administration, 28, 31, 34, 44
Impromptu, 40
Impromptu Administrator, 29, 41, 42
NoticeCast, 38, 39
PowerPlay, 35, 40
transfer log, 193
transfer specification file (.ats)
setting up, 175
transfer summary error log, 193
transferring, See copying
troubleshooting
Access Manager service failure, 198
administration server has no access privileges, 198
administration server not authenticated, 198
cannot connect to NoticeCast data store, 199
cannot find samples, 196
cannot open files, 196
cannot start and stop ticket server, 198
changing default values, 194
configuration settings, 194
connectivity problems, 194
JDBC driver not included in class path, 201
port numbers, 194
relative URL support, 195
resources, 193
server configuration file, 194
services, 194
ticket server configuration values incorrect, 198
ticket server not installed, 199
ticket server not responding, 197
ticket server not running, 199
using log files, 193
using Windows Event Viewer, 193
Index
types of installations
upgrade, 25
U
unattended installations, 26
setting up, 175
uninstalling
ObjectStore, 173
shared components, 171
unique port numbers, 56
unpack Cognos Query, 145
unpacking data stores
Impromptu Web Reports, 149-152
Upfront, 139-141
unpacking metadata
Cognos Query, 145-148
UpfPack, 138
UpfPackage.pkg, 138
Upfront
data store, 27, 31, 33, 37, 43
event server, 28, 31, 33, 37, 43
file manager, 28, 31, 33, 38
gateway, 27, 31, 33, 37, 43
packing data store, 138
server, 27, 30, 33, 37, 43
unpacking data store, 139-141
updating gateway URLs, 163, 190
upgrading NewsIndexes, 139-141
upgrading process, 137
upgrading themes, 141
disabling, 16
testing, 124
updating Web aliases, 109
Upfront Web access
testing, 124
UpfUpgrade, 139-140
upgrade_ppsrv.sh, 156
upgrading
Architect, 166
browser users, 165
checklist to verify preparation, 132
client product data, 165-166
Cognos Query, 142
Cognos Series 7, 103
Cognos Visualizer Web Server, 189
components on a different computer, 131
components on the same computer, 131
conventions used, 134
custom macros, 166
data stores, 116
description of installation types, 25
files required, 133
Impromptu, 165
Impromptu Web Reports, 148-152
installations
load balancing between different versions, 55
macros, 166
mixed version environments, 55
namespaces to current schema version, 169
NoticeCast, 162
NoticeCast gateway URLs, 162
NoticeCast JDBC driver path, 163
ObjectStore, 102
one product at a time, 55
other applications, 166
upgrading (cont'd)
planning the process, 131
PowerPlay Enterprise Server, 152-156, 183
PowerPlay Enterprise Server security, 153
PowerPlay for Excel, 165
PowerPlay User, 165
Sun ONE directory server, 102
Upfront, 137
Upfront NewsIndexes, 139-141
Upfront themes, 141
Web server, 106
upgrading options
user IDs
V
variables
TEMP system, 100
verifying
administrator privileges, 12, 62, 78, 100
system requirements, 99
version
product, 2
versions
switching permanently to 7.1, 169
virtual directories
Web server, 68, 84, 106
W
Web access
testing for Upfront, 124
Web aliases, 56
updating in Upfront Server Administration, 109
Web servers
aliases, 68, 84, 106
configuring, 68, 84
configuring in Windows 2003, 12
configuring to upgrade, 106
IIS 4, 69, 85, 108
iPlanet 4, 70, 86, 109
Personal Web Server, 68, 85, 107
testing, 121
virtual directories, 68, 84, 106
webcontent directory
Windows
Access Manager, 90, 113
Windows 2000 Active Directory
ADSI patch for remote configuration, 208
configuring, 205
Windows 2003
configuration and installation, 11
configuring a DNS, 13
configuring your Web server, 12
creating the help directory, 13
creating the wcgi-bin directory, 12
creating the webcontent directory, 12
enhanced security settings, 13
Internet Explorer settings, 14
Internet Information Services settings, 13
verifying administrator privileges, 12
Windows Common Logon Server, 28, 31, 36, 38, 39, 42, 43,
46
Index
Windows default ports
Alerts/Notification, 51
Cognos OLAP, 51
Cognos Query, 50
Cognos Visualizer Server, 52
Windows Event Viewer
Windows installations
checklist, 211-218
Windows Launch Agent
workstation installations
setting up, 179

Cognos Installation Files

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cognos Installation Files

Uploaded by

Copyright:

Available Formats

<HEAD>

<meta name="last-review" content="24-01-2003">

<meta name="title" content="Installation Guide">

<meta name="product" content="Cognos BI">

Cognos Series 7 Solution

<meta name="version" content="2">

<meta name="prodversion" content="Cognos BI-2">

<meta name="area" content="support">

<meta name="classification" content="documentation">

Type the Title Bar text for online help

Part 2: Installing and Testing Cognos Series 7 59

4 Cognos Series 7 Solution for Windows

Configuring Cognos Series 7 105

Upgrading Cognos NoticeCast 162

6 Cognos Series 7 Solution for Windows

Common Problems 196

8 Cognos Series 7 Solution for Windows

What Is in This Document

What You Need to Know to Use This Document Effectively

How to use the product

Installation Testing and Samples Setup

How to plan for an

Planning Advanced Installations Guide

Configuration Manager User Guide

online book (PDF)

online book (PDF)

online book (PDF) and Windows help

How to package business Deployment Manager User Guide

10 Cognos Series 7 Solution for Windows

Chapter 1: MR1 Installation and Configuration

Windows Server 2003 Installation and Configuration

Java Virtual Machine Support for Windows Server 2003

Steps to Check Whether a JVM Is Installed

Steps to Install a JVM

If no installation menu appears, go to the Support Files\Microsoft\JVM folder on the CD

Chapter 1: MR1 Installation and Configuration Documentation Updates

Confirm Administrator Privileges for Windows Server 2003

Configure Your Web Server for Windows Server 2003

Steps for the Webcontent Directory

Steps for the cgi-bin Directory

12 Cognos Series 7 Solution for Windows

Chapter 1: MR1 Installation and Configuration Documentation Updates

Steps for the Help Directory

Configure a DNS for Your Sun ONE Directory Server

Configure Internet Information Server and Internet Explorer Security

Internet Information Services Settings

Steps to Allow All Unknown CGI Extensions

Chapter 1: MR1 Installation and Configuration Documentation Updates

Steps to Allow Cognos Web Service Extensions

Internet Explorer Settings

Alternate Extensions for Gateway Files

Default file extension

Alternate file extension

Impromptu Web Reports

PowerPlay Enterprise Server

Upfront File Manager

14 Cognos Series 7 Solution for Windows

Chapter 1: MR1 Installation and Configuration Documentation Updates

Steps to Change Gateway Properties in Configuration Manager

New Configuration Manager Properties

Webcontent Root Directory Property

Chapter 1: MR1 Installation and Configuration Documentation Updates

/cognos/cgi-bin/upfcgi.e The URL of the top-level