Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide
Chapter 3: Installing ReportNet on Windows Requirement Web browser Other Specification For all Web browsers, the following enabled: • cookies • JavaScript For IE only, the following enabled: • Run ActiveX controls and plug-ins • Script ActiveX controls marked safe for scripting • Active scripting Microsoft Data Access Component (MDAC) 2.6 or later for use with product samples If you want to email reports, the ability to use a mail server A Web browser configured to accept cookies Database Connectivity for the Reporting Database The only service that accesses the query database (also known as reporting database) is the reporting engine that runs reports. Ensure that you install the database API software for your reporting sources on each ReportNet server computer. On Windows, the report server supports either native database connectivity or ODBC. On UNIX, the report server supports the native database connectivity. Also on UNIX, for Microsoft SQL Server only, the report server supports the Data Direct ODBC driver for Microsoft SQL Server. This driver is available from Data Direct. Database Connectivity for the Content Store Database The database client software for the database that is used as the content store must be installed and configured on the computer where you install Content Manager. For Oracle databases, Content Manager uses the JDBC thin client, classes12.jar. For DB2 databases, Content Manager uses the JDBC thick client. For Microsoft SQL Server, the data connectivity is included in ReportNet and no other connectivity is required. Supported Environments You can view an up-to-date list of environments supported by Cognos products, such as operating systems, patches, browsers, web servers, directory servers, and database servers on the Cognos support site (http://support.cognos.com). It is important to apply all required operating system patches and to use only the versions of third-party software that are supported for a Cognos product. Otherwise, your product may not work properly. Default Settings for Windows The following table lists the default ReportNet ports and URI settings. After installation, you can use the configuration tool to change the settings. You can also change them by editing the crnstartup.xml file in the crn_location/configuration directory. Setting Default Description Content Manager URI Gateway URI Dispatcher URI http://localhost:9300/p2pd /servlet http://localhost:80/crn/cgibin/cognos.cgi http://localhost:9300/p2pd /servlet/dispatch The URI to Content Manager The URI to the ReportNet gateway The URI to the dispatcher 26 Cognos ReportNet TM
Chapter 3: Installing ReportNet on Windows Setting Default Description SDK URI http://localhost:9300/p2pd /servlet/dispatch The URI to the dispatcher Log server port 9362 The port used by the local log server The following table lists the default settings used by ReportNet for Tomcat. The non-SSL and SSL connectors are automatically updated in the server.xml file when you use Cognos Configuration to change the dispatcher port (p. 40) or to enable the SSL protocol (p. 47). You can directly update the shutdown port using Cognos Configuration. . Setting Port Description Non-SSL Coyote HTTP/1.1 Connector SSL Coyote HTTP/1.1 connector 9300 The port Tomcat uses to pass requests from the Web server to ReportNet 9334 The port Tomcat uses to listen for secure connections Shutdown port 9399 The port Tomcat uses to listen for a shutdown command Create the Database for the Content Store You must create the database that is used for the content store using either Oracle, Microsoft SQL Server, or DB2 UDB. ReportNet uses this database to store, organize, and retrieve information. The database you create must use UTF-8 encoding. It is important to note that for each installation, ReportNet uses a single sort order that specifies the rules used by the database to interpret, collect, compare, and present character data. For example, a sort order defines whether the letter 'a' is less than, equal to, or greater than the letter 'b', whether the collation is case-sensitive; and whether the collation is accent-sensitive. Your database administrator must back up the ReportNet content store regularly because it contains all the ReportNet data. To ensure the security and integrity of the content store, it is also important to protect the database from unauthorized or inappropriate access. Steps for Microsoft SQL Server 1. If you performed a Typical installation of Microsoft SQL Server, after you install you must change the authentication mode to SQL Server and Windows. For more information, see the knowledge base article 269587 on the Microsoft Web site. 2. Create the database. If you modified the default settings when you installed Microsoft SQL Server, you must specify a database collation sequence for the content store that is case-insensitive. 3. Determine which user account ReportNet will use to access the content store. 4. Grant create and drop table privileges for the content store to the user account. Ensure that the user account is a member of the db_ddladmin role. Installation and Configuration Guide 27
- Page 1 and 2: COGNOS (R) ENTERPRISE BUSINESS INTE
- Page 3 and 4: Table of Contents Introduction 7 Ad
- Page 5 and 6: Chapter 10: Uninstalling Cognos Rep
- Page 7 and 8: Introduction This document is avail
- Page 9 and 10: Additional Materials In this guide,
- Page 11 and 12: Chapter 1: ReportNet Before impleme
- Page 13 and 14: Chapter 1: ReportNet Installing Rep
- Page 15 and 16: Chapter 1: ReportNet Framework Mana
- Page 17 and 18: Chapter 2: Installing ReportNet on
- Page 19 and 20: Chapter 2: Installing ReportNet on
- Page 21 and 22: Chapter 2: Installing ReportNet on
- Page 23 and 24: Chapter 2: Installing ReportNet on
- Page 25: Chapter 3: Installing ReportNet on
- Page 29 and 30: Chapter 3: Installing ReportNet on
- Page 31 and 32: Chapter 3: Installing ReportNet on
- Page 33 and 34: Chapter 4: Configuring ReportNet Af
- Page 35 and 36: Chapter 4: Configuring ReportNet St
- Page 37 and 38: Chapter 4: Configuring ReportNet 3.
- Page 39 and 40: Chapter 4: Configuring ReportNet Co
- Page 41 and 42: Chapter 4: Configuring ReportNet Wh
- Page 43 and 44: Chapter 4: Configuring ReportNet Th
- Page 45 and 46: Chapter 4: Configuring ReportNet St
- Page 47 and 48: Chapter 4: Configuring ReportNet 3.
- Page 49 and 50: Chapter 4: Configuring ReportNet 4.
- Page 51 and 52: Chapter 4: Configuring ReportNet St
- Page 53 and 54: Chapter 4: Configuring ReportNet 6.
- Page 55 and 56: Chapter 4: Configuring ReportNet Ad
- Page 57 and 58: Chapter 4: Configuring ReportNet Ex
- Page 59 and 60: Chapter 4: Configuring ReportNet Sp
- Page 61 and 62: Chapter 4: Configuring ReportNet 3.
- Page 63 and 64: Chapter 5: Installing Framework Man
- Page 65 and 66: Chapter 5: Installing Framework Man
- Page 67 and 68: Chapter 6: Configuring Framework Ma
- Page 69 and 70: Chapter 6: Configuring Framework Ma
- Page 71 and 72: Chapter 6: Configuring Framework Ma
- Page 73 and 74: Chapter 6: Configuring Framework Ma
- Page 75 and 76: Chapter 6: Configuring Framework Ma
Chapter 3: Installing ReportNet on Windows<br />
Setting Default Description<br />
SDK URI<br />
http://localhost:9300/p2pd<br />
/servlet/dispatch<br />
The URI to the dispatcher<br />
Log server port 9362 The port used by the local log<br />
server<br />
The following table lists the default settings used by ReportNet for Tomcat. The non-SSL <strong>and</strong><br />
SSL connectors are automatically updated in the server.xml file when you use <strong>Cognos</strong><br />
<strong>Configuration</strong> to change the dispatcher port (p. 40) or to enable the SSL protocol (p. 47). You<br />
can directly update the shutdown port using <strong>Cognos</strong> <strong>Configuration</strong>.<br />
.<br />
Setting Port Description<br />
Non-SSL Coyote HTTP/1.1<br />
Connector<br />
SSL Coyote HTTP/1.1<br />
connector<br />
9300 The port Tomcat uses to pass<br />
requests from the Web server<br />
to ReportNet<br />
9334 The port Tomcat uses to listen<br />
for secure connections<br />
Shutdown port 9399 The port Tomcat uses to listen<br />
for a shutdown comm<strong>and</strong><br />
Create the Database for the Content Store<br />
You must create the database that is used for the content store using either Oracle, Microsoft<br />
SQL Server, or DB2 UDB. ReportNet uses this database to store, organize, <strong>and</strong> retrieve<br />
information.<br />
The database you create must use UTF-8 encoding.<br />
It is important to note that for each installation, ReportNet uses a single sort order that specifies<br />
the rules used by the database to interpret, collect, compare, <strong>and</strong> present character data. For<br />
example, a sort order defines whether the letter 'a' is less than, equal to, or greater than the<br />
letter 'b', whether the collation is case-sensitive; <strong>and</strong> whether the collation is accent-sensitive.<br />
Your database administrator must back up the ReportNet content store regularly because it<br />
contains all the ReportNet data. To ensure the security <strong>and</strong> integrity of the content store, it is<br />
also important to protect the database from unauthorized or inappropriate access.<br />
Steps for Microsoft SQL Server<br />
1. If you performed a Typical installation of Microsoft SQL Server, after you install you must<br />
change the authentication mode to SQL Server <strong>and</strong> Windows.<br />
For more information, see the knowledge base article 269587 on the Microsoft Web site.<br />
2. Create the database.<br />
If you modified the default settings when you installed Microsoft SQL Server, you must<br />
specify a database collation sequence for the content store that is case-insensitive.<br />
3. Determine which user account ReportNet will use to access the content store.<br />
4. Grant create <strong>and</strong> drop table privileges for the content store to the user account.<br />
Ensure that the user account is a member of the db_ddladmin role.<br />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong> 27