Академический Документы
Профессиональный Документы
Культура Документы
for Windows
</HEAD>
Installation Guide
Installation Guide
24-01-2003
Cognos BI
2
Type the text for the HTML TOC entry
Type the text for the HTML TOC entry
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
Installation Guide 5
Installation Guide 7
Welcome
This document contains installation instructions for the suite of Cognos Series 7 products.
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.
Installation Guide 9
Welcome
The following documents contain related information, and may be referred to in this document.
Topic
Location
How to configure
components
Questions or Comments?
For additional technical information about using Cognos Series 7 products, visit the Cognos
support Web site (http://support.cognos.com).
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 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.
Installation Guide 11
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.
Location
Permission
cognos
installation_location\webcontent
Read
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
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.
Installation Guide 13
Cognos Query
cqcgi.exe
cqcgi.cgi
imrap.cgi
imrap.exe
ppdscgi.exe
ppdscgi.cgi
Upfront
upfcgi.exe
upfcgi.cgi
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
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.
Installation Guide 15
Default value
Description
Gateway URL
Steps
1. Start Configuration Manager.
2. Click Open the current configuration.
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
File Manager
Gateway
Enabled
True
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.
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
Installation Guide 17
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.
Prefix
Cognos Query
cq
imrap
ppds
viz
Upfront
upf
fm
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*"
Installation Guide 19
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.
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
Installation Guide 21
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).
Installation Guide 23
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.
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.
Installation Guide 25
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
The gateway component is, by default, a common gateway interface (CGI) program that handles
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.
Installation Guide 27
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.
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.
Installation Guide 29
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.
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
The gateway component is, by default, a common gateway interface (CGI) program that handles
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. Cognos Query and Upfront communicate with each other through their gateways.
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
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.
Installation Guide 31
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with Cognos Series 7 Query.
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.
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.
The Upfront server is not available with a minimal installation.
Upfront Gateway
The gateway component is, by default, a common gateway interface (CGI) program that handles
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. PowerPlay Enterprise Server and Upfront communicate with each other through their
gateways.
The Upfront gateway is not available with a minimal installation.
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.
Installation Guide 33
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.
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
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
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.
PowerPlay Transformer
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.
Installation Guide 35
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.
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:
It is not available for multi-byte locales.
It is not available with a minimal installation.
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with the products in Cognos Series 7 PowerPlay Transformer Edition.
Quick Tours
Quick Tours serve as online introductions to Cognos products. Quick Tours for PowerPlay for
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
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.
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
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
The gateway component is, by default, a common gateway interface (CGI) program that handles
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. Cognos server products communicate with Upfront through their gateways.
Installation Guide 37
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.
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.
NoticeCast Tools
The NoticeCast 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.
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with NoticeCast, Upfront, and the related administration tools.
Samples
Samples provide some representative data that you can use with tutorials and for testing your
installation. Access Manager and Upfront samples are provided with Cognos Series 7
Alerts/Notifications.
For more information about samples, see the Installation Testing and Samples Setup Guide.
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.
Installation Guide 39
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with Cognos Series 7 PowerPlay User.
Quick Tours
Quick Tours serve as online introductions to Cognos products. Quick Tours for PowerPlay for
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
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.
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
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.
Books
A complete PDF documentation set is provided for Impromptu and the related tools.
Quick Tours
Quick Tours serve as online introductions to Cognos products. The Impromptu Quick Tour is
available with Impromptu User. If you want to install the Quick Tour, you must do a custom
installation and select it.
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.
Impromptu Administrator
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:
It is not available for multi-byte locales.
It is not available with a minimal installation.
Installation Guide 41
Books
A complete PDF documentation set is provided for Impromptu Administrator and the related
tools.
Quick Tours
Quick Tours serve as online introductions to Cognos products. The Impromptu Quick Tour is
available with Impromptu Administrator. If you want to install the Quick Tour, you must do a
custom installation and select it.
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.
42 Cognos Series 7 Solution for Windows
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
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.
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.
Installation Guide 43
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
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
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 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.
Installation Guide 45
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.
Books
A complete PDF documentation set is provided to help installers, users, and administrators work
with Cognos Visualizer User Series 7.
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.
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.
Description
User ID
Password
admin
admin1234
cn=Directory
Manager
admin1234
Installation Guide 47
Logon to
Description
User ID
Password
Access Manager
Administration
cn=Directory
Manager
admin1234
Administrator
no password
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
389
Ticket server
9010
Web server
80
8020
4455
5000
Upfront dispatcher
8030
8031
8032
8150
8030
ObjectStore
Server
Cache Manager (server)
Cache Manager (client)
Notifications
PowerPrompts
Test server
Data access server
51025
51031
51041
51050
2424
2425
Installation Guide 49
Default port
389
Ticket server
9010
Web server
80
25000
24000
24997
24999
4455
5000
Upfront dispatcher
8030
8031
8032
8150
8030
ObjectStore
Server
Cache Manager (server)
Cache Manager (client)
Notifications
51025
51031
51041
51050
Default port
389
Ticket server
9010
Web server
80
8010
4455
5000
Upfront dispatcher
8030
8031
8032
8150
8030
Default port
389
Ticket server
9010
Web server
80
NoticeCast dispatcher
10998
10999
4455
5000
Upfront dispatcher
8030
8031
8032
8150
8030
Installation Guide 51
Default port
389
ObjectStore
Server
Cache Manager (server)
Cache Manager (client)
Notifications
51025
51031
51041
51050
Default port
389
Ticket server
9010
Web server
80
9041
8060
4455
5000
Upfront dispatcher
8030
8031
8032
8150
8030
Services
After the default installation, the following services for Cognos Series 7 are automatically
started. Some services are shared among Cognos products:
none
none
Installation Guide 53
none
Installation Guide 55
Upfront 7.1
Upfront 7.1
Directory Server (7.0 schema)
Installation Guide 57
Installation Guide 59
Installation Guide 61
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 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
receive a message telling you that you are not a member of the Administrator group.
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.
Steps in Windows XP
1. In the Control Panel, click Performance and Maintenance.
2. Click System.
3. Click the Advanced tab, and then click Environment Variables.
4. 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.
5. Under System Variables, click New.
The New System Variable dialog box appears.
6. In the Variable Name box, type TEMP
7. In the Variable Value box, type the location of the folder where you want to store temporary
files. For example F:\Temp.
8. Click OK.
9. In the Environment Variables dialog box, click OK.
10. In the System Properties dialog box, click OK.
Installation Guide 63
Oracle 9.2
client
NLS_LANG
The NLS_LANG
environment variable
uses the following
format:
NLS_LANG format =
<language>_<territory
>.<character set>
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 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.
Installation Guide 65
Notes
Stop Services
If you have other Cognos products installed, you must stop all Cognos services before you
install or uninstall another Cognos component.
Steps
1. Start Configuration Manager.
2. On the Welcome page, click the Start tab.
3. Click Open the current configuration.
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.
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 you are installing from your network, double-click Setup.exe in the folder where your
administrator copied the installation files.
4. In the Welcome dialog box of the Installation Wizard, read the message 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 Authentication Source dialog box, select Directory Server and click Next.
In the Directory Server Authentication dialog box, type the information for following
properties:
Base Distinguished Name (DN) which will be the first entry in the directory tree
creating a branch for your data
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.
Location
Permission
cognos
installation_location\webcontent
Read
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
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.
For Windows NT, under Access, select the Execute check box, clear the other check
boxes, and then click OK.
12. In the Virtual Directories box, select the cognos virtual directory and click Add.
13. In the Add Directory dialog box, click Browse and select the
installation_location\Documentation folder, and then click OK.
14. In the Alias box, type help
15. Under Access, select the Read check box, clear the other check boxes, and then click OK.
16. To set up your default document:
In the Advanced Options dialog box, select the Enable Default Document check box.
For Windows NT, click Start, Programs, Windows NT 4.0 Option Pack, Microsoft
Internet Information Server, Internet Service Manager.
For Windows 2000, click Start, Settings, Control Panel. Double-click Administrative
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.
You have completed configuration of one virtual directory.
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.
Installation Guide 69
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.
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.
Select the Enable Default Document check box, and click Add.
In the Default Document Name box, type default.htm and click OK twice.
Click the Apply link located in the top right corner to apply your changes.
Installation Guide 71
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
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
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, 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.
Steps
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. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
3. On the Start tab, Click Open the Current Configuration.
Configuration Manager opens.
4. In the Explorer window, expand Cognos NoticeCast
5. Expand the NoticeCast Data Store component.
The General category and four data store categories exist, one for each type of supported
database.
6. Click the General category.
The General - Properties window shows the properties that are currently configured for this
category.
7. 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
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
10. For the Data Store Logon ID property, type the user ID for the NoticeCast user.
11. For the Data Store Logon Password property, type the password for the NoticeCast user.
Confirm the password when prompted.
12. 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
13. In the Explorer window, expand Administration, and then expand the NoticeCast
Administration component.
14. Select the NoticeCast Administration category.
The Properties window shows the properties that are currently configured for this category.
15. For the NoticeCast Server Name property, verify that the Value box shows the name of the
computer running the NoticeCast server.
16. In the Explorer window, select the NoticeCast Administration component.
17. From the Actions menu, click Apply Selection, and then confirm the action.
This action configures your computer with the new settings.
Installation Guide 75
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).
Installation Guide 77
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 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
receive a message telling you that you are not a member of the Administrator group.
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.
Steps in Windows XP
1. In the Control Panel, click Performance and Maintenance.
2. Click System.
3. Click the Advanced tab, and then click Environment Variables.
4. 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.
5. Under System Variables, click New.
The New System Variable dialog box appears.
6. In the Variable Name box, type TEMP
7. In the Variable Value box, type the location of the folder where you want to store temporary
files. For example F:\Temp.
8. Click OK.
9. In the Environment Variables dialog box, click OK.
10. In the System Properties dialog box, click OK.
Installation Guide 79
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 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
1. Open the installation menu from your Cognos CD:
If you insert the CD, the installation menu should appear. Click Install ObjectStore.
If you are installing from your network, double-click Setup.exe in the folder where your
administrator copied the third-party support files.
Notes
Stop Services
If you have other Cognos products installed, you must stop all Cognos services before you
install or uninstall another Cognos component.
Steps
1. Start Configuration Manager.
2. On the Welcome page, click the Start tab.
3. Click Open the current configuration.
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.
Installation Guide 81
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 from the root of the CD.
If you are installing from your network, double-click Setup.exe in the folder where your
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 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.
11. In the Installation Location dialog box, click Next to accept or change the default locations
for components, and then click Next.
12. If prompted to create new folders, click Yes.
13. 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 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.
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.
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.
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.
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).
Installation Guide 83
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.
Location
Permission
cognos
installation_location\webcontent
Read
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
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).
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.
9. In the Add Directory dialog box, click Browse and select the
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.
12. In the Virtual Directories box, select the cognos virtual directory and click Add.
13. In the Add Directory dialog box, click Browse and select the
installation_location\Documentation folder, and then click OK.
14. In the Alias box, type help
15. Under Access, select the Read check box, clear the other check boxes, and then click OK.
16. To set up your default document:
In the Advanced Options dialog box, select the Enable Default Document check box.
For Windows NT, click Start, Programs, Windows NT 4.0 Option Pack, Microsoft
Internet Information Server, Internet Service Manager.
For Windows 2000, click Start, Settings, Control Panel. Double-click Administrative
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.
Installation Guide 85
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.
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.
Select the Enable Default Document check box, and click Add.
In the Default Document Name box, type default.htm and click OK twice.
Click the Apply link located in the top right corner to apply your changes.
Installation Guide 87
Value
Schema Version
Computer
Port
Property
Value
Base Distinguished
Name (DN)
Unrestricted User
Distinguished Name
(DN)
Unrestricted User
Password
Default Namespace
Name
Default Namespace
Administrator Name
Administrator
Installation Guide 89
Property
Value
Default Namespace
Administrator Signon
Administrator
Default Namespace
Administrator
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.
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, 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.
5. Click the General category.
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.
Installation Guide 91
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
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.
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
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, 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.
Installation Guide 93
Steps
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. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
3. On the Start tab, Click Open the Current Configuration.
Configuration Manager opens.
4. In the Explorer window, expand Cognos NoticeCast
5. Expand the NoticeCast Data Store component.
The General category and four data store categories exist, one for each type of supported
database.
6. Click the General category.
The General - Properties window shows the properties that are currently configured for this
category.
7. 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
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.
9. 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 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
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
13. In the Explorer window, expand Administration, and then expand the NoticeCast
Administration component.
14. Select the NoticeCast Administration category.
The Properties window shows the properties that are currently configured for this category.
15. For the NoticeCast Server Name property, verify that the Value box shows the name of the
computer running the NoticeCast server.
16. In the Explorer window, select the NoticeCast Administration component.
17. From the Actions menu, click Apply Selection, and then confirm the action.
This action configures your computer with the new settings.
Steps
Complete these steps on every Windows computer that contains a Cognos component.
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. In the Welcome dialog box, click the Start tab.
3. Click Open the Current Configuration.
Configuration Manager opens.
4. In the Explorer window, click the computer.
5. From the Actions menu, click Apply Selection.
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.
Installation Guide 95
Cognos PowerPlay
Enterprise Server
Cognos Query.Dispatcher
Cognos Query.Server
Cognos NoticeCast
Dispatcher
Cognos Noticecast.Noticecast.Data
Store
Cognos Upfront
Administration Service
Upfront.Shared.Server Administration
Upfront.Data Store
Upfront.Server
PowerGrid
Services.Powergrid
Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. In the Welcome dialog box, click the Start tab.
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).
Installation Guide 97
Installation Guide 99
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 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
receive a message telling you that you are not a member of the Administrator group.
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.
Steps in Windows XP
1. In the Control Panel, click Performance and Maintenance.
2. Click System.
3. Click the Advanced tab, and then click Environment Variables.
4. 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.
5. Under System Variables, click New.
The New System Variable dialog box appears.
6. In the Variable Name box, type TEMP
7. In the Variable Value box, type the location of the folder where you want to store temporary
files. For example F:\Temp.
8. Click OK.
9. In the Environment Variables dialog box, click OK.
10. In the System Properties dialog box, click OK.
Steps
1. Open the installation menu from your Cognos CD:
If you insert the CD, the installation menu should appear. Click Install ObjectStore.
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.
Stop Services
If you have other Cognos products installed, you must stop all Cognos services before you
install or uninstall another Cognos component.
Steps
1. Start Configuration Manager.
2. On the Welcome page, click the Start tab.
3. Click Open the current configuration.
4. At the top of the Explorer window, click your computer name.
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 from the root of the CD.
If you are installing from your network, double-click Setup.exe in the folder where your
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 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.
11. In the Installation Location dialog box, click Next to accept or change the default locations
for components, and then click Next.
12. If prompted to create new folders, click Yes.
13. 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 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.
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.
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).
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.
Location
Permission
cognos
installation_location\webcontent
Read
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
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
installation_location\webcontent
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.
Location
Permission
cognos/plugin
installation_location\webcontent\
plugin
Read
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 a name that is different from the one being used with the older
Cognos Series 7 products (for example, Cognosv2).
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.
9. In the Add Directory dialog box, click Browse and select the
installation_location\cgi-bin folder, and then click OK.
10. 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/cgi-bin).
11. To define the access level for the new cgi-bin virtual directory:
For Windows NT, under Access, select the Execute check box, clear the other check
boxes, and then click OK.
12. In the Virtual Directories box, select the cognos virtual directory and click Add.
13. In the Add Directory dialog box, click Browse and select the
installation_location\Documentation folder, and then click OK.
14. 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/help).
15. Under Access, select the Read check box, clear the other check boxes, and then click OK.
In the Advanced Options dialog box, select the Enable Default Document check box.
For Windows NT, click Start, Programs, Windows NT 4.0 Option Pack, Microsoft
Internet Information Server, Internet Service Manager.
For Windows 2000, click Start, Settings, Control Panel. Double-click Administrative
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.
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 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.
8. Click OK, and click Next.
9. Select Allow Read Access, clear the other check boxes, and then click Finish.
You have completed configuration of one virtual directory.
10. In the left pane of the console, right-click the folder called cognos and click New, Virtual
Directory.
11. 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/cgi-bin),
and click Next.
12. On the Website Content Directory page, next to the Directory box, click Browse and then
click the installation_location\cgi-bin folder.
13. Click OK, and click Next.
14. To define the access level for the cgi-bin virtual directory:
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.
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.
Select the Enable Default Document check box, and click Add.
In the Default Document Name box, type default.htm and click OK twice.
Click the Apply link located in the top right corner to apply your changes.
Value
Schema Version
Computer
Port
Property
Value
Base Distinguished
Name (DN)
Unrestricted User
distinguished name
(DN)
Unrestricted User
password
Default Namespace
Name
Default Namespace
Administrator Name
Administrator
Property
Value
Default Namespace
Administrator Signon
Administrator
Default Namespace
Administrator
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.
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, 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.
5. Click the General category.
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.
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
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
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, 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.
Steps
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. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
3. On the Start tab, Click Open the Current Configuration.
Configuration Manager opens.
4. In the Explorer window, expand Cognos NoticeCast
5. Expand the NoticeCast Data Store component.
The General category and four data store categories exist, one for each type of supported
database.
6. Click the General category.
The General - Properties window shows the properties that are currently configured for this
category.
7. 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
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
10. For the Data Store Logon ID property, type the user ID for the NoticeCast user.
11. For the Data Store Logon Password property, type the password for the NoticeCast user.
Confirm the password when prompted.
12. 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
13. In the Explorer window, expand Administration, and then expand the NoticeCast
Administration component.
14. Select the NoticeCast Administration category.
The Properties window shows the properties that are currently configured for this category.
15. For the NoticeCast Server Name property, verify that the Value box shows the name of the
computer running the NoticeCast server.
16. In the Explorer window, select the NoticeCast Administration component.
17. From the Actions menu, click Apply Selection, and then confirm the action.
This action configures your computer with the new settings.
Steps
Complete these steps on every Windows computer that contains a Cognos component.
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. In the Welcome dialog box, click the Start tab.
3. Click Open the Current Configuration.
Configuration Manager opens.
4. In the Explorer window, click the computer.
5. From the Actions menu, click Apply Selection.
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.
Cognos PowerPlay
Enterprise Server
Cognos Query.Dispatcher
Cognos Query.Server
Cognos NoticeCast
Dispatcher
Cognos Noticecast.Noticecast.Data
Store
Cognos Upfront
Administration Service
Upfront.Shared.Server Administration
Upfront.Data Store
Upfront.Server
PowerGrid
Services.Powergrid
Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, 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, 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).
120 Cognos Series 7 Solution for Windows
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.
Steps
1. Verify that you completed the test of the directory server and saved a .csa file.
2. From the Start menu, click Programs, Cognos Series 7 Version 2, Cognos Server
Administration, and then click Security to start Access Manager Administration.
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
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.
The Connect dialog box appears.
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.
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.
The Connect dialog box appears.
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.
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.
Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Cognos Server
Administration.
2. In the Cognos Server Administration window, click Alerts and Notifications to start
NoticeCast Server Administration.
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.
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.
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.
Upgrade Checklist
Use the following checklist to verify that you are prepared for the upgrade of your application
data.
File or folder
Typical 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
\cer2\Report Store
\cer2\bin\output.xml
PowerPlay
Metadata (7.0) folder
\cer2\ppserver\PPSRoot
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.
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.
UNIX process
ns-slapd.exe
ns-slapd
slapd.exe
slapd
ns-httpd.exe
ns-httpd
httpd.exe
uxwdog
Cognos PowerPlay
Enterprise Server
ppserver.exe
ppserver
cqdbsrv.exe
cqdbsrv
cqqrysvr.exe
cqqrysvr
cqdisp.exe
cqdisp
cqsvrmgr.exe
cqsvrmgr
UNIX process
TicketServer.exe
TicketServerd
Cognos Upfront
Administration Service
UpfrontAdministrati
on.exe
UpfAdmin
upfdbsrv.exe
upfdbsrv
(also starts rds.exe) (also starts rds)
UpfDispatcherServi UpfDispatcherSer
ce.exe
vice
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
osserver.exe
osserver
Powergrid
Not applicable
udanetd
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)
Description
-un
-pw
-d
-pn
-i
-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:
3. Use the 7.0 Access Manager Administration to ensure that your authentication source is
available and ticket server is running.
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.
Description
-database
-rollback
-p
-un
-pw
Parameter
Description
-d
-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 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
Configuration Manager:
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:
For example,
UpfUpgrade database p UpfUpgrade70.pkg un Administrator
pw mypassword
For example,
./run-upfupgrade database p UpfUpgrade70.pkg un Administrator pw mypassword
Steps
1. On your Upfront dispatcher computer, copy your template files.
2. On your Upfront gateway computer, copy your HTML style sheet and image files:
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.
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.
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.
14. Close Configuration Manager.
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.
16. Wait until the message Action completed successfully appears, and then close the dialog
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.
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.
2. Log on if required, and then click OK.
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]
For example, on Windows or UNIX, the following command uses default locations:
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]
For example, on Windows or UNIX, the following command uses default locations:
cdmpack -d cqpkg -p cqpkg
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/
4. Ensure that the following 7.1 services or corresponding processes are running by using
Configuration Manager:
5. To ensure that your authentication source is available and the ticket server is running, use
the 7.1 Access Manager Administration tool.
For example, on Windows or UNIX, the following command uses default locations:
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]
For example, on Windows or UNIX, the following command uses default locations:
cdmdefine -mp -d cqpack -p cqpkg
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -v -d cqpack -p cqpkg -u UpfServ:8030
One unpacking report is created in the directory where the package is located.
Installation Guide 147
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -d cqpack -p cqpkg -u UpfServ:8030
Description
-db
-fn
-v
-l
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.
4. Use the 7.0 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. On UNIX, ensure that you are in a Bourne shell before you set up your environment by
typing
sh
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
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
Description
-fn
-un
Username.
-pw
-v
-db
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 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.
5. Use the 7.1 Access Manager Administration to ensure that your authentication source is
available and the ticket server is running.
6. Open a command window or a terminal emulator session and go to the bin directory:
7. On UNIX, ensure that you are in a Bourne shell before you set up your environment by
typing
sh
For example, when the Impromptu Web Reports database is on the local computer:
dsload -fn myoutput.xml -un Administrator -pw mypassword
-db "C:\Program Files\Cognos\cer3\iwr\database\iwr71.db"
For example, when the Impromptu Web Reports database is on a remote computer (mars):
dsload -fn myoutput.xml -un Administrator -pw mypassword
-db "mars:C:\Program Files\Cognos\cer3\iwr\database\iwr71.db"
For example, when the Impromptu Web Reports database is on the local computer:
./dsload -fn myoutput.xml -un Administrator -pw mypassword
-db /usr/cognos/cer3/iwr/database/iwr71.db
For example, when the Impromptu Web Reports database is on a remote computer (mars):
./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
On Windows, to update the location of one report set at a time, use the following syntax:
On UNIX, to update the location of one report set at a time, use the following syntax:
On Windows, to update the location of all report sets at once use the following syntax:
On UNIX, to update the location of all report sets at once use the following syntax:
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
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:
Steps
1. Ensure that the following 7.1 service or corresponding process is running by using
Configuration Manager:
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
2. Use the 7.1 Access Manager Administration tool to ensure that your authentication source
is available and the ticket server is running.
3. Start the PowerPlay Enterprise Server Administration tool.
4. Secure the server by using the appropriate directory server and namespace.
Description
-d
-k
-v
-im
-i
-r
-u
[-un username]
[-pw password]
[searchFor
replaceWith]
-m
-un
-pw
-vm
-ppx
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 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
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
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.
3. Ensure that the corresponding process for this 7.1 service is stopped:
Cognos PowerPlay Enterprise Server (cer3)
You can also stop this 7.1 process by running the following script:
./stop_ppsrv.sh
4. Use the 7.1 Access Manager Administration tool to ensure that your authentication source
is available and the ticket server is running.
5. In the 7.1 bin directory, ensure that you are in a Bourne shell by typing
sh
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
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
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
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.
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.
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.
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.
13. Close Configuration Manager.
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.
Expand Dependent Components, and exclude all components except CogViz and
Access Manager Security Content.
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.
The New Package dialog box appears.
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.
15. Wait until the message Action completed successfully appears, and then close the dialog
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.
3. 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 vizpkg -u UpfServ:8030
If a port number is not specified, the default port for the 7.1 Upfront server, 8030, is
assumed.
4. Log on if required, and then click OK.
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 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]
For example, on Windows or UNIX, the following command uses default locations:
cdmdefine -md -d vizpkg
6. Use the following syntax to pack the data and to create the package file (.dmp):
cdmpack -d package_def_name [-dl package_def_location] -p packagename [-pl
package_location]
For example, on Windows or UNIX, the following command uses default locations:
cdmpack -d vizpkg -p vizpkg
3. To ensure that your authentication source is available and the ticket server is running, use
the 7.1 Access Manager Administration tool.
For example, on Windows or UNIX, the following command uses default locations:
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.
2. Log on if required, and then click OK.
Note: You must be a member of the root user class in Access Manager.
3. Open the unpack setting file (.dmu) in a text editor to change the mappings.
4. For each location identified in the unpack settings file, type an appropriate value for the
TargetValue attribute and save the file.
5. On UNIX, ensure that you are in a Bourne shell before you set up your environment by
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:
cdmdefine -mp -d definition -p packagename [-pl package_location]
For example, on Windows or UNIX, the following command uses this location:
cdmdefine -mp -d vizkg -p vizpkg
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -v -d vizpkg -p vizpkg -u UpfServ:8030
One unpacking report is created in the directory where the package is located.
9. To unpack the package, use the following syntax:
cdmunpack -d definition -p packagename [-pl package_location] -u
Upfront_server[:port]
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -d vizpkg -p vizpkg -u UpfServ:8030
Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Cognos Server
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
162 Cognos Series 7 Solution for Windows
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.
Steps
1. Use Configuration Manager to ensure that the following 7.1 services or corresponding
processes are running:
2. Use the 7.1 Access Manager Administration tool to ensure that your authentication source
is available and the ticket server is running.
Installation Guide 163
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.
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.
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.
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
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.
Description
-i or -input
-d or -dest
-h or -help
Steps
1. Open a command window or a terminal emulator session and go to the 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
UNIX
./vizupgrade -i /usr/cer2/Visualizations/Metrics.viz -dest /usr/cer3/Visualizations/
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.
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.
All the Cognos services used by Cognos Series 7 products are automatically stopped when you
uninstall Cognos components.
Steps
1. From the Start menu, click Settings, Control Panel.
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:
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
1. From the Start menu, click Settings, Control Panel.
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
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.
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.
Client
Workstation
6. In the section named [Component List], specify the components to install for a custom
installation.
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.
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],
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.
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.
Installation Guide 177
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.
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.
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. 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.
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.
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.
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. 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.
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.
2. In the Welcome dialog box of the Installation Wizard, read the message and click Next.
Installation Guide 179
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
Modification Required
Parameter
Determines
Modification Required
Description
The name
displayed in the
Windows Start
menu.
Folder
The name
displayed in
Windows for
Add/Remove
programs.
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.
Expand Dependent Components, and exclude all components except PPES and
Access Manager Security Content.
Leave the NewsIndex components as preselected or exclude any NewsBoxes that you
do not want to upgrade.
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).
2. Go to the cer3/bin directory, and create a package definition file (.dmd) and a pack setting
file (.dmi) by typing the following command 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 PPpack -u UpfServ:8030
If a port number is not specified, the default port for the 7.1 Upfront server, 8030, is
assumed.
For example, on Windows or UNIX, the following command uses default locations:
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
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):
cdmpack -d package_def_name [-dl package_def_location] -p packagename [-pl
package_location]
For example, on Windows or UNIX, the following command uses default locations:
cdmpack -d PPpack -p PPpack
For example, on Windows or UNIX, the following command uses default locations:
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.
You must be a member of the root user class in Access Manager.
4. 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.
5. Type the following command to modify the package file with the unpack setting file:
cdmdefine -mp -d definition -p packagename [-pl package_location]
For example, on Windows or UNIX, the following command uses default location:
cdmdefine -mp -d PPpack -p PPpack
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -v -d PPpack -p PPpack -u UpfServ:8030
One unpacking report is created in the directory where the package is located.
7. Type the following command to unpack the package:
cdmunpack -d definition -p packagename [-pl package_location] -u
Upfront_server[:port]
For example, on Windows or UNIX, the following command uses default locations:
cdmunpack -d PPpack -p PPpack -u UpfServ:8030
Windows
UNIX
Cognos Visualizer
vizwebsrv.exe
vizwebsrv
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.
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:
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.
Description
-i or -input
-d or -dest
-h or -help
Steps
1. Open a command window or a terminal emulator session and go to the 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
UNIX
./vizupgrade -i /usr/cer2/Visualizations/Metrics.viz -dest /usr/cer3/Visualizations/
Steps
1. Use Configuration Manager to ensure that the following 7.1 services or corresponding
processes are running:
2. Use the 7.1 Access Manager Administration to ensure that your authentication source is
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
Configuration Manager
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.
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
Appendix D: Troubleshooting
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.
Appendix D: Troubleshooting
If you use more than one version of the file some components may not be able to access
services on other servers.
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.
Appendix D: Troubleshooting
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.
Solution Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. Perform an Apply on Samples Database Information.
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.
Solution
Perform a custom installation of the Cognos samples files for the product.
Solution
Follow the upgrade procedures in the installation guide to make your data files compatible with
Cognos Series 7 products.
Appendix D: Troubleshooting
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.
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.
Solution
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
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.
Appendix D: Troubleshooting
8. Perform an Apply and a Start on Access Manager - Directory 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.
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.
3. Verify that the configuration values for the ticket server are correct and update them if
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.
Appendix D: Troubleshooting
Solution
1. Perform a custom installation of the ticket server.
2. Verify that the configuration values for the ticket server are correct and update them if
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.
Solution
Start the ticket server to ensure that it is running.
Appendix D: Troubleshooting
Solution
1. Verify the user logon ID and password for accessing the data store with your database
administrator.
2. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
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.
Solution
1. Verify the URL with your database administrator.
2. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
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.
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.
Appendix D: Troubleshooting
Solution
Ensure the database has been set up to contain the NoticeCast data store.
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 D: Troubleshooting
If you insert the CD, the installation menu should appear. Click Install Support Files,
and then double-click the Microsoft folder, DCOM folder, and 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.
If you insert the CD, the installation menu should appear. Click Install Support Files,
and then double-click the Microsoft folder, MDAC folder, and mdac_typ.exe.
If you are installing from your network, double-click mdac_typ.exe in the MDAC folder
where your administrator copied the third-party support files.
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 you are installing from your network, double-click msjavx86.exe in the JVM folder
where your administrator copied the third-party support files.
Steps
1. From the Start menu, click Programs, Cognos Series 7 Version 2, Tools, Configuration
Manager.
2. From the Welcome page, click the Start tab.
3. Click Open the current configuration.
Configuration Manager opens with your computers current configuration shown.
4. In the Explorer window, expand the Services, then expand Access Manager - Directory
Server.
5. Click the General category.
6. Type the following values for the corresponding General property.
Property
Value
Property
Value
Server Type
Computer
Port
Base distinguished
name (DN)
Unrestricted user
distinguished name
(DN)
Unrestricted user
password
Property
Value
Default Namespace
Name
Default Namespace
Administrator Name
Default Namespace
Administrator Signon
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
Port/SSL Port
Base DN
Timeout
Default Namespace
Property
Value
SSL Enabled
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.
13. Close Configuration Manager.
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.
If you insert the CD, the installation menu should appear. Click Install Support Files,
click the Adobe and Acrobat folders, and then 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.
If you insert the CD, the installation menu should appear. Click Install Support Files,
click the Adobe and Acrobat folders, and then 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.
_____________
Operating System
_____________
RAM
_____________MB
CPU
_____________
_____________MB
_____________GB
Ping Server?
Yes / No
Ping Server-IP?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
printer driver
Yes / No
Yes / No
Yes / No
database type
_____________
Yes / No
SMTP server
name
_____________
_____________
SMTP Logon
name
_____________
SMTP Logon
password
_____________
Yes / No
Yes / No
____________
Server Identifier
(Server name)
computer name
_____________
Server Port
Suffix
(Database Suffix)
o=Cognos, c=CA
_____________
Configuration Directory
Administrator ID
admin
_____________
Password
admin1234
_____________
Administration Domain
yourcompany.com
_____________
Option
_____________
admin1234
_____________
Administration Port
20000
_____________
Option
Cognos
Default Value
Server Identifier
(Server name)
_____________
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 Query
Cognos Series 7 Reporting
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.
Default Value
ObjectStore Ports
Server
Cache Manager (server)
Cache Manager (client)
Notifications
_____________
osserver.log
51025
51031
51041
51050
_____________
_____________
_____________
_____________
Yes / No
Impromptu Administrator
Yes / No
Started?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide.
Yes / No
Yes / No
Started?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide.
Yes / No
PowerPlay User
Yes / No
Started?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide.
Yes / No
Yes / No
Started?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide.
Yes / No
Yes / No
Yes / No
Started?
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
For a list of ports used by a default installation, see "Cognos Series 7 Components" in your
installation guide. For existing installations you can use Configuration Manager to generate
a report that includes details about your Cognos environment including port numbers.
Location
Permission
cognos
installation_location\webcontent
Read
Alias
Location
Permission
cognos/cgi-bin installation_location\cgi-bin
Execute
cognos/help
Read
installation_location\Documentation
Location
Style
cognos/plugin
installation_location/webcontent/ Download
plugin
cognos/download
installation_location/webcontent/ Download
viz/download
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
troubleshooting, 193
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
configuring, 97, 113
authoring tools
Cognos Visualizer, 45
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
troubleshooting, 194
checklists, 211-218
files for completing upgrade, 133
preparing for upgrade, 132
Cleanup utilities
PowerPlay Enterprise Server, 33
client products
upgrading data, 165-166
cmplst.txt, 194
code examples, See samples
Cognos components
configuring, 83, 105
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
default ports for Windows, 51
Cognos Query
add to 7.1 configuration, 143
data store, 30
default ports for Windows, 50
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
Cognos Server Administration
tools, 28, 31, 34, 38, 44
Cognos services
stopping, 66, 81, 103
Cognos services, See services
Cognos Supplementary Software CD, 46
Cognos Visualizer, 45
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
default ports for Windows, 52
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
configuring, 95, 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
troubleshooting, 194
Windows 2003, 11
configuration files, 56
Configuration Manager
applying configuration, 95, 119
changing property values, 90, 113
disabling Upfront File Manager, 16
processes, 95, 119
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
configuring, 88, 110
testing, 122
upgrading to current schema, 169
Windows 2000 Active Directory, 205
disabling
Upfront File Manager, 16
dispatcher
Cognos Query, 30
Cognos Visualizer, 43
PowerPlay Enterprise Server, 32
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
troubleshooting, 196
G
gateways
alternate file extensions for .cgi files, 14
Cognos Query, 30
Cognos Visualizer, 43
Impromptu Web Reports, 27
ISAPI, 68, 84, 107
NSAPI, 68, 84, 107
PowerPlay Enterprise Server, 32
updating URLs in NoticeCast, 162
updating URLs in Upfront, 163, 190
Upfront, 27, 31, 33, 37, 43
Geoset Manager, 46
H
help directory
creating in Windows 2003, 13
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
Impromptu Web Reports
data store, 27
default ports for Windows, 49
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
enhanced security settings in Windows 2003, 13
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
troubleshooting, 201
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
configuring, 88, 110
installation kit, 46
Netscape Directory Server, See Sun ONE Directory Server
network installations
setting up, 178
NewsIndexes
upgrading Upfront, 139-141
NoticeCast
administration tools, 38
authoring tool, 38
configuring, 91, 114
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
troubleshooting, 199
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
Impromptu Web Reports, 148
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
default settings, 47
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
PowerPlay Enterprise Server
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
default ports for Windows, 52
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
configuring, 90, 113
Q
query processors
Cognos Visualizer, 43
PowerPlay Enterprise Server, 33
Quick Tours
Cognos Visualizer, 45
Impromptu, 30, 41, 42
PowerPlay, 35, 37, 40
R
relative URL support
configuration, 23
troubleshooting, 195
report processors
PowerPlay Enterprise Server, 33
report store directories, 150
S
samples
Cognos Query, 32
Cognos Visualizer, 45, 46
Impromptu, 41, 42
Impromptu Web Reports, 30
NoticeCast, 39
PowerPlay, 35, 40
PowerPlay Transformer, 37
troubleshooting, 196
Schema Version, 88, 111, 205
schema versions, 169
scripts
.ats, 176
security
enhanced security settings in Windows 2003, 13
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)
troubleshooting, 194
server groups
configuring multiple groups, 23
servers
Cognos NoticeCast, 114
Cognos Query, 30
Cognos Windows Common Logon Server, 34
Impromptu Web Reports, 27
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
troubleshooting, 194
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
Sun ONE Directory Server
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
administration tools, 124
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 Transformer, 126
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
troubleshooting, 197
tl-nnn.txt, 193
tl-nnn_summary-error.txt, 193
tools
Cognos Query, 32
Cognos Server Administration, 28, 31, 34, 44
Cognos Visualizer, 44, 46
Impromptu, 40
Impromptu Administrator, 29, 41, 42
Impromptu Web Reports, 29
NoticeCast, 38, 39
PowerPlay, 35, 40
PowerPlay Enterprise Server, 34
PowerPlay Transformer, 36
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
Upfront File Manager
disabling, 16
Upfront Server Administration
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 Transformer, 166
PowerPlay User, 165
Sun ONE directory server, 102
Upfront, 137
Upfront NewsIndexes, 139-141
Upfront themes, 141
Web server, 106
upgrading options
Cognos Visualizer, 156, 188
PowerPlay Enterprise Server, 183
user IDs
default settings, 47
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
creating in Windows 2003, 12
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
Impromptu Web Reports, 49
PowerPlay Transformer, 52
Windows Event Viewer
troubleshooting, 193
Windows installations
checklist, 211-218
stopping services, 66, 81, 103
Windows Launch Agent
PowerPlay Enterprise Server, 33
workstation installations
setting up, 179