Installation Cognos Reportnet

NN44480-306
Nortel Cognos 1.1.4

Installation Guide
Product release 6.5 and 7.0 Standard 01.04 November 2009

Nortel Cognos 1.1.4
Installation Guide
Publication number: NN44480-306

Product release: 6.5 and 7.0
Document release: Standard 01.04
Date: November 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
While the information in this document is believed to be accurate and reliable, except as otherwise
expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY
OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products
described in this document are subject to change without notice.
Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.

Contents
Getting Started 7
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How to get Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing Cognos ReportNet 11

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing Cognos ReportNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Validation Checkpoint: Cognos ReportNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Troubleshooting Installation Problems 23

InstallShield Unresponsive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
InstallShield Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Failed to create Content Store database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Maximum number of database connections reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Setting the Connection to the Mail Server 31

Setting up a Connection to the Mail Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Cognos Performance Tuning 33

Modifying the Cognos ReportNet Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Modifying Cognos Server settings in Cognos Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Modifying Windows Virtual Memory settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Determining MS SQL Server TCP Port Numbers 41

Determining and Configuring MS SQL Server TCP Port Numbers . . . . . . . . . . . . . . . . . . . . . . 42
Configuring Cognos ReportNet for HTTP or HTTPS protocol 45

Configuring Cognos ReportNet to Use HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring Cognos ReportNet to Use HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Verifying the Cognos Content Store Connection 49

Setting the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Using a CA Certificate 51
Preparing and Obtaining the CA Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Moving the Content Store Database 55

Moving Content Store DB to another instance/server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Modifying Data Execution Prevention Settings 57

Modifying Data Execution Prevention Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Installation Guide v
Contents Standard 01.04
Index 61
vi Nortel Cognos 1.1.4

Chapter 1
Getting Started
In this chapter
About this guide 8
How to get Help 9
Installation Guide 7
Getting Started Standard 01.04
About this guide
The Nortel Cognos 1.1.4 Installation Guide provides instructions for installing and setting up the
Cognos ReportNet components. This document also provides general product information as
well as recommendations for product deployment.
There is one Cognos Installation DVD.
Intended audience
This guide is designed to be used by:
Nortel and Business Partner professional services staff responsible for planning and setting
up systems.
Customers’ IT staff responsible for system maintenance.
8 Nortel Cognos 1.1.4

November 2009 Getting Started
How to get Help
This section explains how to get help for Nortel products and services.
Finding the latest updates on the Nortel Web site

The content of this documentation was current at the time the product was released. To check for
the latest updates to the Nortel Contact Recording and Quality Monitoring documentation, go to
http://www.nortel.com/documentation and navigate to the Contact Recording suite.
Getting help from the Nortel Web site

The best way to get technical support for Nortel products is the Nortel Support Web site:
http://www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and tools to address issues
with Nortel products. From this site, you can:
download software and related tools
download technical documents, release notes, and product bulletins
sign up for automatic notification of new software and documentation
search the Support Web site and Nortel Knowledge Base for answers to technical issues
open and manage technical support cases
Getting help over the phone from a Nortel Solutions Center

If you do not find the information your require on the Nortel Technical Support Web site, and
you have a Nortel support contract, you can also get help over the phone from a Nortel Solutions
Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the Web site below to obtain the phone number for your region:
http://www.nortel.com/callus
Getting help from a specialist by using an Express Routing Code

You can use an Express Routing Code (ERC) to more quickly route your call to the appropriate
support specialist. To locate the ERC for your product or service, go to:
http://www.nortel.com/erc
Getting Started Standard 01.04
Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor or authorized
reseller, you can contact the technical support staff for that distributor or reseller.

Chapter 2
Installing Cognos ReportNet
In this chapter
Prerequisites 12
Installing Cognos ReportNet 13
Validation Checkpoint: Cognos ReportNet 21
Installing Cognos ReportNet Standard 01.04
Prerequisites
If Microsoft Firewall Client exists, you must remove it and restart Windows before
installing Cognos.
If your instance of SQL Server is using a dynamic port, it must be configured to use a static
port. For more information, please refer to the Appendix “Determining MS SQL Server
TCP Port Numbers” on page 41.
Before installation, you must change your Windows setting for Data Execution Prevention
on the Cognos server. Please refer to “Modifying Data Execution Prevention Settings” on
page 57.
Be sure that the following system variables are removed (if any exist): JAVA_HOME,
JAVA_OPTS, _JAVA_OPTIONS, CATALINA_HOME and CATALINA_OPTS.
To locate the variables, right-click on My Computer and select Properties. On the Advanced
tab, select Environment Variables and check the list of System Variables in the dialog
displayed.

November 2009 Installing Cognos ReportNet
Installing Cognos ReportNet
1 On the Cognos DVD, locate and double-click on the setupwin32.exe from the folder CD #1
to start the installation.
You can also run the install.htm page located on the DVD and launch the installer from the
browser page.
The Welcome screen is displayed.
2 Click Next to continue.
The installer will check the system to see if the following system variables currently exist:
JAVA_HOME, JAVA_OPTS, _JAVA_OPTIONS, CATALINA_HOME and
CATALINA_OPTS.
If any of them exist, the installer displays the following message:
Click OK to stop the installer, then remove all of those system variables manually. Restart
the machine and run the installer again.
If none exist, the Destination screen is displayed.
3 Use the Browse button to change the Drive location from C:\ to D:\.
4 Click Next.
The Administrative Account screen is displayed.
The admin account name defaults to radmin for the administrator account, with password
DreamLiner787.
5 Leave these default values.
6 Click Next to proceed.
The Gateway Setting dialog is displayed.

7 Complete the information on the gateway setting dialog:

Enter the name of the server that will be used to connect to the ReportNet Gateway. It is
typically the name of the machine, but could also be the fully qualified Internet domain
name which is mapped to this server (such as reportserver.yourcompany.com). The
default value for this field is the computer name.
Choose to set up this ReportNet Gateway to run on HTTP or HTTPS.
Enter the port number for the ReportNet Gateway. The default value is 8383 if you use
HTTP and 8387 if you use HTTPS.
When you choose HTTPS, an option to use a 3rd party certificate (Trusted CA's
certificate) is displayed. The option is not selected by default; the server uses an in-
house certificate.
If you choose to use a 3rd party certificate, specify the path to the certificate’s key store
file and the password of that key store file. For information on how to prepare and obtain
a certificate to use with ReportNet Gateway, please refer to the Appendix “Preparing and
Obtaining the CA Certificate” on page 52.
8 Click the Next button.
The installation program validates all the information you have entered. You are prompted
to correct any incorrect or missing information.
The Content Store Database dialog is displayed.
9 Select the database type. Currently, only MS SQL is supported.

10 Complete the additional information on the Content Store database dialog.
Enter the Server Name. This is the name of the SQL Server.
Enter the Database Port (the default is 1433). For more information, refer to the
Appendix “Determining MS SQL Server TCP Port Numbers” on page 41. Please note
that the instance must be configured to use a static port as described in the appendix.
Choose to Create New Database (for new installations) or Use Existing Database.
If you choose to Create New Database:
Enter the Database Admin ID.This account is used by the installer to create the content
store database for the ReportNet Gateway; therefore, it must have permissions to create
database, users, tables, views, and stored procedures on the database server. A
database system administrator account like sa should be used here.
Enter the Database Admin Password. Provide the password of administrative account.
If you choose to Use Existing Database, the fields change:
Enter the Database Name.

Enter the Database User ID, which is the database owner name.
Enter the Database User Password, which is the database owner password.


The ReportNet logging Database screen is displayed.
12 Configure the ReportNet logging database.

The logging database is created on the same server as the Content Store database.
If you choose to Create New Database, the administrative account information is populated
from the data you entered in the previous step.
If you choose to Use Existing Database:
Enter the Database Name.
Enter the Database User ID, which is the database owner name.
Enter the Database User Password, which is the database owner password.
13 Click Next.
The Mail server configuration screen is displayed.
14 Complete the information on Mail server dialog.

Enter the SMTP Host name.
Enter the SMTP Port.
Enter the User Name and Password of a mail account that will be used to connect to
the mail server.
If the SMTP mail server doesn't require a login, you can leave these fields empty.
Enter the Sender Email address to be used as from address when sending an email.
If the connection information is valid, you will receive a test email sent from the sender to
the <user name> mail box. Otherwise, a message is displayed. You can either correct the
problem, or skip the test and configure the mail server at a later time.
For more information about how to set up your mail server manually, please refer to the
Appendix “Setting up a Connection to the Mail Server” on page 32.

The interactive report service processes screen is displayed.
16 Specify the Maximum number of interactive report service processes.

As a guideline, the number of report service processes should be set to two times the
number of CPUs to optimize performance.
This number of processes may be increased if any of the following applies:
a. The clock rate of CPUs are high (e.g. 3.0 GHz or higher)
b. There are many long running queries in progress where most of the processing occurs
on the database server.
Note: Do not add processes "just in case." Additional processes can interfere with Quality
Monitoring recording, playback, evaluations, etc.
17 Click Next.
18 Click the Install button. The installer begins copying files.
Note: It can take anywhere from 15 to 30 minutes to install the ReportNet Gateway.
When the installation has successfully completed, you will see the following:
19 Click Finish to complete the installation.

Validation Checkpoint: Cognos ReportNet
1 Run {http|https}://<servername>:<port>/ServletGateway
+ http: if you chose HTTP while installing
+ https: if you chose HTTPS while installing
+ <servername>: installed machine
+ <port>: ReportNet Gateway port (8383 http default or 8387 https default)
Note: ServletGateway is case-sensitive.
2 You can log in using the administrative account created during the installation:
User ID: radmin
Password: DreamLiner787
A valid installation displays the following screen:

Appendix A
Troubleshooting Installation Problems
In this chapter
InstallShield Unresponsive 24
InstallShield Error 25
Failed to create Content Store database 26
Maximum number of database connections reached 28
Troubleshooting Installation Problems Standard 01.04
InstallShield Unresponsive
When the installation is started, the InstallShield becomes unresponsive and a blank dialog box
appears as follows:
Error
There is a problem with the InstallShield. It does not respond, and there is no way of continuing
with the installation.
Resolution
Minimize the dialog and restore it.

November 2009 Troubleshooting Installation Problems
InstallShield Error
During the installation, the following InstallShield error appears:
Error
The version of Windows Installer on the target machine is not recent enough.
Resolution
Click the OK button and save the new file to c:\
Failed to create Content Store database
During Cognos installation, the error “Failed to create Content Store database” occurs.
Error
Installer failed to create Content Store and Audit data / log files due to existence of file names at
the default data file location.
Resolution
Carefully verify and delete all unused files in the default data file location on the database server.
The Cognos ReportNet Content Store database name usually follows the naming conventions
CRN_CS, or CRN_CS1, or similar convention.
The Cognos ReportNet Audit database name usually follows the naming conventions
CRN_AUDIT, CRN_AUDIT1, or similar convention.
Steps to perform:
1 In the database server, launch Microsoft SQL Server Management Studio.
2 Verify that a Content Store or Audit database does not exist.
The following image shows a Content Store database properties and its data files location.

3 Launch Windows Explorer, and go to SQL server default data file location, typically at
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.
4 Determine if any files follow the Content Store or Audit filename convention mentioned
above, and NOT associate with any databases. If yes, back up them to a safe place and
remove.
The installer can now create the Cognos databases. Please launch the Cognos installer and try
again.
Maximum number of database connections reached
An error related to number of database connections can frequently occur when using Cognos
ReportNet.
Error
QE-DEF-0370 Maximum number of database connections (n) has been reached
Resolution
There are two areas that need to be reviewed in a ReportNet installation if this error message
occurs frequently.
The Cognos Query Engine component (CQE) of the Report Server has a database connection
pool that is governed by two parameters:
Pool size - This is set to 20 by default.
If there are 20 active connections, further requests for new connections will be rejected.
Timeout - This is set to 900 seconds (15 minutes) by default.
Free connections will linger for this Timeout value before they are closed. If a new request
matches a free connection in terms of database sign on, the free connection will be re-used
(same DB attach). Otherwise, the new request will take a free connection by closing and re-
attaching to the database using the new database sign on.
The above settings are in the file crn/configuration/CQEConfig.xml.
ReportNet by default does not have the CQEConfig.xml file installed; the file is installed as
CQEConfig.xml.sample. To activate it, you need to copy it, rename it, and modify the values.
The Report server itself maintains a pool of active requests, governed by three parameters:
RequestCacheLength - This is set to 10 by default. This means that it will keep the last 10
requests in case the user does, for example, a next page operation. Each cached request will
hang on to the CQE connection, so those connections will still be marked as active.
RequestReleaseTimeout - This is set to 300 seconds (5 minutes) by default. Cached
requests that are waiting for the next user action will be timed out and released based on this
value. This will also release the CQE connection, marking those as free.
RequestCleanupInterval - This is set to 60 seconds (1 minute) by default. Cached requests
are examined as candidates for release as we process new requests, but if the system is idle,
they are still examined once per this interval.
In ReportNet, the above settings are in the file crn/configuration/warpproperties.xml.
ReportNet, by default, does not have the warpproperties.xml file installed; the file is installed
as warpproperties.xml.sample.

To activate the file, you need to copy it, rename it, and modify the values.
Note that depending on the active requests, connections might not be freed up for up to 21
minutes after the requests are done (RequestCleanupInterval + RequestReleaseTimeout +
Timeout).

Appendix B
Setting the Connection to the Mail Server
In this appendix
Setting up a Connection to the Mail Server 32
Setting the Connection to the Mail Server Standard 01.04
Setting up a Connection to the Mail Server
To set up a connection to your mail server:

1 Open the Cognos configuration by choosing Programs > Cognos ReportNet > Cognos
Configuration from the Start menu.
2 Select Notification in the left pane.
3 In central pane, enter the following information:
SMTP mail server: Enter your mail server and port number with server_name:port_number
format.
Account and password: (If required in user’s environment.) Click on the Edit button at the
end of the row. A pop up window will display. Enter the User ID. Password and Confirm
password. Click OK.
Default sender: This email address will be used to send notification.
4 Click Save and then Restart to restart Cognos service.
Tip: You can enter the same information as you did for Email Notifiers in the Quality
Monitoring configuration.

Appendix C
Cognos Performance Tuning
In this appendix
Modifying the Cognos ReportNet Service Configuration 34
Modifying Cognos Server settings in Cognos Connection 36
Modifying Windows Virtual Memory settings 37
Cognos Performance Tuning Standard 01.04
Modifying the Cognos ReportNet Service

Configuration
This section provides further performance enhancements to your current Cognos settings. A
recommendation of 1536 MB is suggested for dispatcher maximum memory to optimize your
Cognos ReportNet.
The following are the steps to be performed:

1 On your Cognos ReportNet server, click Start > Programs > Cognos ReportNet >
Cognos Configuration.
2 In the Explorer on the left pane of Cognos Configuration, expand Environment >
ReportNet service > Cognos ReportNet.
3 Stop the service by clicking the Stop button at the top-left corner.
4 In the Cognos ReportNet configuration properties at the right-hand side:
Verify its Type of Large configuration
Note the current value of Dispatcher maximum memory in MB and modify as required.
The recommended value is 1536 MB.
Note: With a large configuration and 1536 MB defined, on some specific server
environments / settings, even though there is enough free RAM, the Java Virtual Machine
(JVM) may not be able to allocate the amount on RAM. The JVM needs a coherent address
space to allocate the memory. Usually on Windows systems the setting of 1536 MB works,
but if there are other blocked parts in the address space of the memory, this configuration
will not. Verify the checkpoint after the modification to ensure your system does not suffer
the issue.

November 2009 Cognos Performance Tuning
5 Click on the Save button to commit your change and click the Start button to start the
service.
6 Checkpoint: launch
http://<Cognos ReportNet server>:<port>/ServletGateway or
https://<Cognos ReportNet server>:<port>/ServletGateway depending on your
installation, typically the HTTP port is 8383 and HTTPS port is 8387.
7 Successfully log on using the radmin account to ensure that your modification completed.
Otherwise, you will need to repeat the above steps to rollback to your former setting, or try
with another lower memory amount for your dispatcher.
Modifying Cognos Server settings in Cognos

Connection
To optimize the performance of Cognos interactive report service, it is recommended by Cognos

to set the value for the Maximum number of interactive report service processes setting to 2
times the number of processors in the server where Cognos is installed.
To change this Cognos server setting, follow these steps:

1 Log on to Cognos Connection as an administrator. Click on the Server Administration link.
2 Click on the Action icon of the target server. Then click on the “Settings” tab.
3 Change the value of Maximum number of interactive report service processes to 2

times the number of processor on this server.
4 4 Check the Delete the configuration settings of all child entries checkbox. Click OK.

Modifying Windows Virtual Memory settings
It is recommended by Cognos to increase the size of the Windows virtual memory on the server
in order to improve Cognos performance. The recommended value is 1.5 times the amount of
RAM on the server.
To change this Windows setting, follow these steps:

1 From Start menu, select Settings > Control Panel.
2 Double-click the System icon. Click on the Advanced tab, and then click on the Settings
button in Performance section.
3 In Performance Options window, click on Advanced tab, and then click on Change
button.
4 In this example, there are 4GB of RAM on the server.

In the Virtual Memory window, change the values in Initial size and Maximum size to 6144
(1.5 times the amount of RAM on the server).

Click OK.

Appendix D
Determining MS SQL Server TCP Port
Numbers
In this appendix
Determining and Configuring MS SQL Server TCP Port Numbers 42
Determining MS SQL Server TCP Port Numbers Standard 01.04
Determining and Configuring MS SQL Server TCP Port

Numbers
Enterprise Reporting requires working with database server via TCP-protocol connection
configured with a static port. This appendix provides instructions to determine and configure on
which port your Microsoft SQL Server is listening.
To determine / configure TCP port number:

1 On the database server, launch SQL Server Configuration Manager.
2 2 In the left pane, expand SQL Server 2005 Network Configuration, and select Protocol
for <your server instance>.
3 On the right pane, right-click TCP/IP protocol, and then click Properties.
4 The TCP/IP Properties dialog is displayed as follows:
Enabled: Select Yes to assure the protocol is used.

Listen All: Specify whether SQL Server will listen on all the IP addresses that are bound
to network cards on the computer. (Default is Yes).

November 2009 Determining MS SQL Server TCP Port Numbers
If set to No, configure each IP address separately for each IP address. If set to Yes, the settings of
the IP All properties will apply to all IP addresses.
5 Select IP Addresses tab.
6 To configure for an IP address:

IP Address. View or change the IP address used by this connection.
Enabled. Enable or disable this connection.
Active. Indicates SQL Server is listening on the designated port
TCP Dynamic Ports. Set to blank to disable dynamic ports. (To use dynamic ports, set to
0).
TCP Port (default is 1433). View or change the port on which SQL Server listens.
For more information, search Books Online for the topic SQL Server 2005 Network.
7 Click OK to apply your changes if any.
8 In the left pane of SQL Server Configuration Manager, select node SQL Server 2005
Services, and in the other pane, locate SQL Server (your server instance) and restart it for
your changes to take effect.Configuration.
Determining MS SQL Server TCP Port Numbers Standard 01.04

Appendix E
Configuring Cognos ReportNet for HTTP or
HTTPS protocol
In this appendix
Configuring Cognos ReportNet to Use HTTPS 46
Configuring Cognos ReportNet to Use HTTP 47
Configuring Cognos ReportNet for HTTP or HTTPS protocol Standard 01.04
Configuring Cognos ReportNet to Use HTTPS
To configure Cognos ReportNet to use HTTPS:

9 Open a Windows console and change to:
<ReportNet install folder>\config-tools
10 Execute the command:
switch-to-https.bat -commonName <your server> [-httpPort <httpPort>] [-httpsPort
<httpsPort>]
[-keystoreFile <keystoreFile>] [-keystorePass <keystorePassword>]
Parameter Value
-commonName Typically the name of the machine, but

could also be the fully qualified Internet
domain name mapped to this server,
ex:
reportserver.yourcompany.com. The
default is the computer name.
-httpsPort Optional. The port number on which

Cognos ReportNet runs using HTTPS.
The default value is 8387.
-keystoreFile Optional. The path and file name to the

key store file that is storing the
certificate. Specify this parameter along
with -keystorePass to use your CA's
certificate. Otherwise, the server will be
using an in-house certificate.
-keystorePass Optional. The password of that key

store file.

November 2009 Configuring Cognos ReportNet for HTTP or HTTPS protocol
Configuring Cognos ReportNet to Use HTTP
To configure Cognos ReportNet to use HTTP:

1 Open a Windows console and change to:
<ReportNet install folder> \config tools
2 Execute the command:
switch-to-http.bat [-httpPort <httpport>]
Parameter Value
-httpPort Optional. The port number on which

Enterprise Reporting runs using HTTP.
The default value is 8383.
Configuring Cognos ReportNet for HTTP or HTTPS protocol Standard 01.04

Appendix F
Verifying the Cognos Content Store
Connection
In this appendix
Setting the Connection 50
Verifying the Cognos Content Store Connection Standard 01.04
Setting the Connection
To verify and configure the setting for connection to Cognos Content Store:
1 On the Cognos server, click Start > Programs > Cognos ReportNet > Cognos
Configuration to launch the tool.
2 In the Explorer tree on the left pane, expand Data Access > Content Manager > Content
Store. The right pane details the database resource properties.
3 To correct the setting, click the Stop button to shutdown the service first, and modify the
fields as required and click Save. Then restart the service for the change to take effect.
4 Open Internet Explorer and browse to the following URL:
http://<server>:<port>/ServletGateway/servlet/Gateway
Or
https://<server>:<port>/ServletGateway/servlet/Gateway
The default port is 8383 for HTTP, or 8387 for HTTPS.
A login screen will confirm that the configuration is completed.

Appendix G
Using a CA Certificate
In this appendix
Preparing and Obtaining the CA Certificate 52
Using a CA Certificate Standard 01.04
Preparing and Obtaining the CA Certificate
To prepare and obtain the CA certificate, you must complete the following steps:
1 Install J2SDK1.4 or later to some temporary folder on your machine, referred to in this
section as <TEMP_JDK_HOME>.
2 Make a copy of file <TEMP_JDK_HOME>\jre\lib\security\cacerts and name it anything
you like. Let's name it <TEMP_JDK_HOME>\jre\lib\security\crn.keystore.
3 The default password of your key store file
<TEMP_JDK_HOME>\jre\lib\security\crn.keystore is changeit, you can keep using it, but
it's recommended you change it to your own password for security reasons executing the
following command from a command prompt window:
"<TEMP_JDK_HOME>\bin\keytool" -storepasswd -new "<your new key store
password>" -storepass changeit -keystore
"<TEMP_JDK_HOME>\jre\lib\security\crn.keystore"
4 Create a new self-signed certificate by executing the following command from a command
prompt window:
"<TEMP_JDK_HOME>\bin\keytool" -genkey -alias crngateway -keyalg RSA -
storepass "<your key store password>" -keypass <your key store password> -
keystore "<TEMP_JDK_HOME>\jre\lib\security\crn.keystore"
The tool will ask you to enter information for the certificate as detailed below:
Enter Distinguished Name (DN) information
First and last name - This is the Common Name: It's the name you will use to access the
server you plan to install CRN on. It can be name of that server or a fully Internet domain
name mapped to that server. Do not enter your personal name in this field.
Organizational unit - Use this field to differentiate between divisions within an
organization. For example, "Engineering" or "Human Resources." If applicable, you may
enter the DBA (doing business as) name in this field.
Organization - The name under which your business is legally registered. The listed
organization must be the legal registrant of the domain name in the certificate request. If
you are enrolling as an individual, please enter the certificate requestor's name in the
"Organization" field, and the DBA (doing business as) name in the "Organizational Unit"
field.
City/Locality - Name of the city in which your organization is registered/located. Please
spell out the name of the city. Do not abbreviate.
State/Province - Name of state or province where your organization is located. Please
enter the full name. Do not abbreviate.
Country code - The two-letter International Organization for Standardization- (ISO-)
format country code for the country in which your organization is legally registered.
Confirm that the Distinguished Name information is correct.
5 Create a certificate request by executing the following command from a command prompt
window:

November 2009 Using a CA Certificate
"<TEMP_JDK_HOME>\bin\keytool" -certreq -keyalg RSA -alias crngateway -

storepass "<your key store password>" -file
"<TEMP_JDK_HOME>\jre\lib\security\crn.csr" -keystore
6 Take file <TEMP_JDK_HOME>\jre\lib\security\crn.csr and go to the CA of your choice to
buy a certificate. If asked, indicate you're buying certificate for a Tomcat5 server. The CA
will send you back the signed certificate in a file. Let's call file <signed-cert-file>. Copy
<signed-cert-file> to <TEMP_JDK_HOME>\jre\lib\security directory.
7 Import <signed-cert-file> to your key store file by executing the following command from a
command prompt window:
"<TEMP_JDK_HOME>\bin\keytool" -import -alias crngateway -storepass "<your key
store password>" -file
"<TEMP_JDK_HOME>\jre\lib\security\<signed-cert-file>" -keystore
Note: Depending on what Certification Authority you chose to buy the certificate from, you
may have to import several other immediate CA certificates to your key store file before you
can import your signed certificate. The CA will supply you with those immediate certificates
and instructions to import them.
8 Now you can use <TEMP_JDK_HOME>\jre\lib\security\crn.keystore while installing
CRN. You should back up that file to some safe place. If you lose it, there is no way to
recover it from somewhere and you will need to buy a new one.
Using a CA Certificate Standard 01.04

Appendix H
Moving the Content Store Database
In this appendix
Moving Content Store DB to another instance/server 56
Moving the Content Store Database Standard 01.04
Moving Content Store DB to another instance/server
This document does not force specific steps to migrate the Content Store database in WCI 1.1.2;
however it provides the following suggestion that may be useful. The detail instructions on the
back up/restore or export/import task are not in the scope of this document, but can be found on
the database vendor’s documentation.
WARNING
The target database must be qualified for the prerequisites

. stated previously.
On the existing server/instance, backup the Content Store database and the login SID of the
user that owns the database.
Restore Content Store database to the target system and create login with the backup SID,
then assign access and grant db_owner privilege for the Content Store database.
Launch Cognos Configuration to modify the connection settings. For more information,
please refer to the section “Setting the Connection” on page 50.

Appendix I
Modifying Data Execution Prevention
Settings
In this appendix
Modifying Data Execution Prevention Settings 58
Modifying Data Execution Prevention Settings Standard 01.04
Modifying Data Execution Prevention Settings
From Window 2003 Server Service Pack 1, programs that use system memory are monitored by
Data Execution Prevention (DEP), which will close programs that attempt to run code (malicious
or not) from a protected location.
To install Cognos successfully, you must change the Windows setting to apply DEP on Window
programs and services only; otherwise, DEP will stop the Cognos executable during the
installation.
After Cognos installation, you can change the setting back so that DEP can monitor all processes
in the system except the Cognos executable.
Changing the DEP Setting Before Cognos Installation

On the Cognos sever, perform the following steps:
1 Open on Windows > Settings > Control Panel > System.
2 Select the Advanced tab.
3 Click on Settings in the Performance section, then click on the Data Execution Prevention
tab.
4 Choose Turn on DEP for essential Windows programs and services only.
5 Click OK twice to apply the new setting.

November 2009 Modifying Data Execution Prevention Settings
Reversing the DEP Setting After Cognos Installation

On the Cognos sever, perform the following steps:
1 Open Windows > Settings > Control Panel > System.
2 Select the Advanced tab.
3 Click on Settings in the Performance section, then click on the Data Execution Prevention
tab.
4 Choose Turn on DEP for all programs and services except those I select.
5 Click the Add button and browse to
<Cognos install folder>\ReportNet\crn\bin\crconfigw.exe.
6 Click Open.
7 Click the Add button and browse to
<Cognos install folder>\ReportNet\crn\bin\jre\1.3.1\bin\java.exe.
8 Click Open.
9 Click OK twice to apply setting.
Modifying Data Execution Prevention Settings Standard 01.04

November 2009 Index
Index
A J
about this guide 8 JAVA_HOME 12, 13
JAVA_OPTS 12, 13
C
CATALINA_HOME 12, 13
L
CATALINA_OPTS 12, 13 logging database 17
Cognos Installation DVD 8
Cognos installation DVD 13
Cognos performance 37
Cognos Performance Tuning 33
M
Cognos Query Engine 28 Maximum number of database connections 28
Configuring Cognos ReportNet for HTTP or HTTPS Maximum number of interactive report service
protocol 45 processes 19, 36
Content Store 50 Microsoft Firewall Client 12
Content Store database 15, 26 Modifying Data Execution Prevention Settings 57
CQEConfig.xml 28 Moving Content Store DB to another instance/server 56
CRN_AUDIT 26
CRN_CS 26
N
Nortel Solutions Center 9
D Nortel Web site 9
Data Execution Prevention 12
Database Port 15
default port 50 P
default ports 15
Determining and Configuring MS SQL Server TCP Port password 14
Numbers 42 performance enhancements 34, 37
Dispatcher maximum memory 34 Pool size 28
Drive location 13 Preparing and Obtaining the CA Certificate 52
Prerequisites 12
F R
Failed to create Content Store database 26
radmin account 14, 21, 35
ReportNet Gateway server 15
H
HTTP 15, 47 S
HTTPS 15, 46
ServletGateway 21
Setting up a Connection to the Mail Server 32
setupwin32.exe 13
I SMTP Host 18
InstallShield problems 24, 25 SMTP mail server 32
Intended audience 8 SMTP Port 18
intended audience 8 static port 12
system variables 12
November 2009 Index
T
Timeout 28
V
Validation Checkpoint 21
Verifying the Cognos Content Store Connection 49
Virtual Memory 38
W
warpproperties.xml 28
Windows Installer version 25
Nortel Cognos 1.1.4
Installation Guide
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
While the information in this document is believed to be accurate and reliable, except as otherwise
expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY
OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products
described in this document are subject to change without notice.
Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.
To provide feedback or report a problem with this document, go to

www.nortel.com/documentfeedback.
Publication number: NN44480-306

Product release: 6.5 and 7.0
Document release: Standard 01.04
Date: November 2009

Installation Cognos Reportnet

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Installation Cognos Reportnet

Enviado por

Direitos autorais:

Formatos disponíveis

NN44480-306

Nortel Cognos 1.1.4

Product release 6.5 and 7.0 Standard 01.04 November 2009

Publication number: NN44480-306

Copyright © 2008-2009 Nortel Networks. All Rights Reserved.

All other trademarks are the property of their respective owners.

Installing Cognos ReportNet 11

Troubleshooting Installation Problems 23

Setting the Connection to the Mail Server 31

Cognos Performance Tuning 33

Determining MS SQL Server TCP Port Numbers 41

Configuring Cognos ReportNet for HTTP or HTTPS protocol 45

Verifying the Cognos Content Store Connection 49

Moving the Content Store Database 55

Modifying Data Execution Prevention Settings 57

vi Nortel Cognos 1.1.4

About this guide

There is one Cognos Installation DVD.

8 Nortel Cognos 1.1.4

How to get Help

Finding the latest updates on the Nortel Web site

Getting help from the Nortel Web site

Getting help over the phone from a Nortel Solutions Center

In North America, call 1-800-4NORTEL (1-800-466-7835).

Getting help from a specialist by using an Express Routing Code

Getting help through a Nortel distributor or reseller

10 Nortel Cognos 1.1.4

12 Nortel Cognos 1.1.4

Installing Cognos ReportNet

14 Nortel Cognos 1.1.4

7 Complete the information on the gateway setting dialog:

9 Select the database type. Currently, only MS SQL is supported.

 Enter the Database Name.

16 Nortel Cognos 1.1.4

11 Click Next to continue.

12 Configure the ReportNet logging database.

The Mail server configuration screen is displayed.

14 Complete the information on Mail server dialog.

18 Nortel Cognos 1.1.4

The interactive report service processes screen is displayed.

16 Specify the Maximum number of interactive report service processes.

19 Click Finish to complete the installation.

20 Nortel Cognos 1.1.4

Validation Checkpoint: Cognos ReportNet

A valid installation displays the following screen:

22 Nortel Cognos 1.1.4

24 Nortel Cognos 1.1.4

During the installation, the following InstallShield error appears:

Failed to create Content Store database

26 Nortel Cognos 1.1.4

Maximum number of database connections reached

The above settings are in the file crn/configuration/CQEConfig.xml.

In ReportNet, the above settings are in the file crn/configuration/warpproperties.xml.

28 Nortel Cognos 1.1.4

30 Nortel Cognos 1.1.4

Setting up a Connection to the Mail Server

To set up a connection to your mail server:

32 Nortel Cognos 1.1.4

Modifying the Cognos ReportNet Service

The following are the steps to be performed:

34 Nortel Cognos 1.1.4

Modifying Cognos Server settings in Cognos

To optimize the performance of Cognos interactive report service, it is recommended by Cognos

To change this Cognos server setting, follow these steps:

Enter the Database Name.

Enabled: Select Yes to assure the protocol is used.