20.07.2014 Views

Cognos ReportNetTM Installation and Configuration Guide

Cognos ReportNetTM Installation and Configuration Guide

Cognos ReportNetTM Installation and Configuration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 6: Configuring Framework Manager<br />

3. In the Properties window, in the Gateway URI box, type the appropriate value.<br />

• To use ISAPI, replace cognos.cgi with cognosasapi.dll.<br />

• To use apache_mod, replace cognos.cgi with mod_cognos.dll.<br />

• To use a servlet gateway, use the following syntax:<br />

http[s]://host:port/contextName/servlet/Gateway<br />

Note: contextName is the name you assigned to the ServletGateway Web application<br />

when you deployed the ServletGateway WAR file.<br />

4. Change the host name portion of the Gateway URI from localhost to either the IP address<br />

of the computer or the computer name.<br />

5. Specify the value for the SDK URI:<br />

• If your Web server is configured not to allow anonymous access, type the Dispatcher<br />

URI, ensuring that you change the host name in the URI from localhost.<br />

• If your Web server supports chunking, type the Dispatcher URI, ensuring that you<br />

change the host name in the URI from localhost.<br />

• Otherwise, type the same value you specified for the Gateway URI, ensuring that you<br />

change the host name in the URI from localhost.<br />

6. In the Explorer window, under Cryptography, click <strong>Cognos</strong>, the default cryptographic<br />

provider.<br />

7. Under the Certificate Authority settings property group, for the Password property, type<br />

the same password you configured on the Content Manager computer.<br />

8. From the File menu, click Save.<br />

Framework Manager is now configured to communicate with ReportNet. You can change default<br />

configuration settings if required for your environment, or test your installation <strong>and</strong> configuration.<br />

Changing Default <strong>Configuration</strong> Settings<br />

Change a Port<br />

When you install ReportNet components, the installation uses default configuration settings. If<br />

you have any reason not to use these default values, such as a port is being used by another<br />

process, use <strong>Cognos</strong> <strong>Configuration</strong> to change the value.<br />

If you change the value of a property, you must save the configuration <strong>and</strong> then restart the<br />

ReportNet service to apply the new settings to your computer.<br />

You can also change the default behavior of ReportNet. For example you can<br />

• change a port<br />

• configure SSL protocol<br />

• change temporary file properties<br />

• configure cryptographic settings<br />

• configure source control systems<br />

• change the Gateway URI to use an alternate gateway<br />

• setting up data sources<br />

If you have any reason not to use a default port, such as it is used by another process, you can<br />

change it.<br />

When you change the port used by the local dispatcher, you must change the value of the<br />

Internal dispatcher URI property. Because the change affects all the URIs that are based on the<br />

local dispatcher, you must change the URIs of all local components. By default, local<br />

components contain localhost in the URI.<br />

For example, if you install all components on one computer <strong>and</strong> you change the dispatcher port,<br />

you must also change the port in the local Content Manager URI <strong>and</strong> local SDK URI.<br />

If you change the dispatcher port in the local Dispatcher URI, ensure that you specify the new<br />

port numbers when you configure remote computers that use the Dispatcher URI, Content<br />

Manager URI, <strong>and</strong> SDK URI properties.<br />

68 <strong>Cognos</strong> ReportNet TM

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!