Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 2: Installing ReportNet on UNIX<br />
Default Settings for UNIX<br />
The following table lists the default ReportNet ports <strong>and</strong> URI settings. After installation, you can<br />
use the configuration tool to change the settings. You can also change them by editing the<br />
crnstartup.xml file in the crn_location/configuration directory.<br />
Setting Default Description<br />
Content Manager URI<br />
Gateway URI<br />
Dispatcher URI<br />
SDK URI<br />
http://localhost:9300/p2pd<br />
/servlet<br />
http://localhost:80/crn/cgibin/cognos.cgi<br />
http://localhost:9300/p2pd<br />
/servlet/dispatch<br />
http://localhost:9300/p2pd<br />
/servlet/dispatch<br />
The URI to Content Manager<br />
The URI to the ReportNet<br />
gateway<br />
The URI to the dispatcher<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 />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong> 19