Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 4: Configuring ReportNet<br />
3. From the Actions menu, click Start.<br />
It may take a few minutes for the ReportNet service to start.<br />
4. Open a Web browser.<br />
5. Start ReportNet by typing one the following, where crn is the virtual directory you created<br />
when you configured the Web server.<br />
For the CGI gateway:<br />
http://server_name/crn<br />
For an ISAPI gateway:<br />
http://server_name/crn/isapi<br />
For Apache Connector on Windows:<br />
http://server_name/crn/cgi-bin/mod_cognos.dll<br />
For Apache Connector on Solaris <strong>and</strong> AIX:<br />
http://server_name/crn/cgi-bin/mod_cognos.so<br />
For Apache Connector on HPUX:<br />
http://server_name/crn/cgi-bin/mod_cognos.sl<br />
For a gateway servlet:<br />
http://server_name:9300/ServletGateway/servlet/Gateway<br />
It may take a few minutes for the Web page to open.<br />
If you see the Welcome page of <strong>Cognos</strong> Connection, your installation is working.<br />
The configuration of a single computer installation is now complete. You can perform additional<br />
configuration tasks to customize the behavior of ReportNet components to better suit your<br />
reporting environment (p. 40). If you are satisfied with your configuration, you can install <strong>and</strong><br />
configure the Windows modeling tool, Framework Manager.<br />
Configuring Distributed <strong>Installation</strong>s<br />
To improve performance or to enhance security, you can install any one the following<br />
components on a separate computer:<br />
• gateway<br />
• report server<br />
• Content Manager<br />
For information about planning a distributed installation, see the Architecture <strong>and</strong> Planning<br />
<strong>Guide</strong>.<br />
You can install the report server or gateway on multiple computers. You can install Content<br />
Manager on only one computer.<br />
If you install ReportNet components on more than one computer, some configuration tasks are<br />
required so that the components can communicate with each other <strong>and</strong> work in your reporting<br />
environment. Other configuration tasks, such as using an authentication provider (p. 41) or<br />
enabling <strong>and</strong> disabling services (p. 53) are optional <strong>and</strong> change the default behavior of<br />
ReportNet to better suit your reporting objectives.<br />
Communication Between Distributed Components<br />
If you install ReportNet components on more than one computer, you must configure<br />
environment properties so that the distributed components can communicate with each other:<br />
• The Content Manager computer must know the location of the content store.<br />
• The gateway computer must know the location of a dispatcher.<br />
The dispatcher can be located on the Content Manager or report server computer.<br />
• The report server computer must know the location of Content Manager.<br />
You must also configure cryptographic properties to ensure that each computer uses the same<br />
settings.<br />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong> 37
Change language