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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 7: Advanced <strong>Configuration</strong> Options<br />

Preparing Your Environment If ReportNet Previously Used Tomcat<br />

If you previously configured ReportNet to run in your environment using Tomcat, the default<br />

servlet container, <strong>and</strong> now plan to use WebSphere or WebLogic, you must:<br />

❑ stop the <strong>Cognos</strong> ReportNet service<br />

❑ delete any existing cryptographic keys before you configure the alternative application<br />

server<br />

❑ unregister dispatchers that are no longer used after you configure ReportNet to run on<br />

WebSphere or WebLogic<br />

Delete Cryptographic Keys<br />

Before you configure ReportNet to use a third-party application server, ensure that any<br />

cryptographic keys that were previously created are deleted. This ensures that the correct<br />

security <strong>and</strong> Java environment is used.<br />

Remove Dispatchers<br />

Steps<br />

1. Stop the <strong>Cognos</strong> ReportNet service using <strong>Cognos</strong> <strong>Configuration</strong>.<br />

2. Save <strong>and</strong> close <strong>Cognos</strong> <strong>Configuration</strong>.<br />

3. Back up the contents of the following directories:<br />

• crn_location/configuration/csk<br />

• crn_location/configuration/encryptkeypair<br />

• crn_location/configuration/signkeypair<br />

4. Ensure that the startup configuration does not contain encrypted passwords:<br />

• If timestamped versions of the crnstartup.xml files are available in the<br />

crn_location/configuration directory, rename the crnstartup_timestamp.xml file with the<br />

earliest timestamp to crnstartup.xml.<br />

Note: To allow you to undo some configuration changes, ReportNet creates a<br />

timestamped version of crnstartup.xml before applying any changes to the file. The file<br />

with the earliest timestamp should be the original version of the file <strong>and</strong> does not<br />

contain encrypted passwords.<br />

• If the timestamped versions of the files are not available, in <strong>Cognos</strong> <strong>Configuration</strong>,<br />

re-enter the passwords for the following resources or components, if they exist: Content<br />

Manager database, the Notification database, the Notification mail server, log database,<br />

<strong>and</strong> your LDAP authentication source.<br />

5. Delete the csk, encryptkeypair, <strong>and</strong> signkeypair directories.<br />

After you start the application server, remove ReportNet services that have been previously<br />

registered <strong>and</strong> that are no longer used.<br />

To access the server administration tool, you must have execute permissions for the<br />

Administration secured function.<br />

Steps<br />

1. Open the ReportNet portal.<br />

2. On the portal toolbar, click Server Administration.<br />

3. Click the Monitor tab.<br />

4. Under Type, click Dispatchers.<br />

A list of dispatchers appears.<br />

5. Select the check box for the dispatcher you want to unregister <strong>and</strong>, on the toolbar, click the<br />

unregister button.<br />

Tip: You can also unregister dispatchers by clicking More in the Actions column.<br />

A message confirms the action.<br />

6. Click OK.<br />

86 <strong>Cognos</strong> ReportNet TM

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

Saved successfully!

Ooh no, something went wrong!