Cognos ReportNetTM Installation and Configuration Guide

More documents

Recommendations

Info

Chapter 7: Advanced Configuration Options Configuring ReportNet to Use An Alternative Application Server Instead of using Tomcat, the default servlet container included with ReportNet, you can configure ReportNet to use either a WebSphere or a WebLogic application server. This optional configuration may be appropriate if you want to use an existing application server implementation. It may provide greater flexibility for supporting additional applications. Before you configure ReportNet to use an alternative application server, do the following: ❑ Install ReportNet and select the components that will run on each computer. ❑ If required, the Oracle and DB2 clients must be installed and set up prior to running ReportNet. The appropriate environment variables must be set prior to starting the application server. For information about setting up the database client on UNIX, see "Set Up the Database Client for the Content Store Database" (p. 23), or on Windows, see "Set Up the Database Client for the Content Store Database" (p. 30). ❑ Install the application server or identify an existing application server that you can use for ReportNet. ❑ If you have WebLogic 6.1 SP4 or WebLogic 7.0 SP2, add the chunking patch to the WebLogic installation. • For WebLogic 6.1 SP4, add CR102751_61sp4.jar to WebLogic_location /wlserver6.1/lib, or upgrade to SP5. • For WebLogic 7.0 SP2, add CR100172_70sp2.jar to WebLogic_location/weblogic700/common/lib. This patch corrects a servlet container issue where HTTP chunked requests are not handled properly. Tip: To obtain the required chunking patch for the servlet container issue, contact BEA support. ❑ On UNIX, to avoid file permission conflicts, create a new UNIX group. You could call this group reportnet. This group must contain the user that starts WebSphere or WebLogic and the user that owns the ReportNet files. Change the group ownership of the ReportNet files to the reportnet group and change the file permissions for all ReportNet files to GROUP READABLE/WRITABLE/EXECUTABLE. ❑ If ReportNet was previously configured to use Tomcat, you must complete additional steps to prepare the ReportNet installation (p. 86). Configure ReportNet to Use a WebSphere Application Server You can use a WebSphere application server instead of Tomcat, the default. The following steps are based on a default WebSphere installation. You can also configure a customized environment (p. 81). Steps 1. If ReportNet was previously configured to use Tomcat, you must stop the ReportNet service and then delete the cryptographic keys (p. 86). 2. On each computer that includes ReportNet and WebSphere, from the crn_location/bi/jre1.3.1/lib/ext directory, copy the contents of the ext directory to WebSphere_location/java/jre/lib/ext. Important: Some or all of the jar files may already exist in the WebSphere ext directory. If so, do not overwrite the WebSphere versions of the files. 78 Cognos ReportNet TM
Chapter 7: Advanced Configuration Options 3. Set the JAVA_HOME environment variable: • On Windows, set a system environment variable. • On UNIX, from crn_location/bin, edit crconfig.sh. Operating System Windows UNIX Environment Variable Command set JAVA_HOME= WebSphere_location\AppServer\java\jre For csh: setenv JAVA_HOME= WebSphere_location/AppServer/java/jre For ksh: JAVA_HOME= WebSphere_location/AppServer/java/jre export JAVA_HOME For sh: JAVA_HOME= WebSphere_location/AppServer/java/jre export JAVA_HOME 4. From the crn_location/bin, start Cognos Configuration: • On Windows, type crconfigw.exe -java:env • On UNIX, type crconfig.sh 5. In the Explorer window, expand Environment and then change the following properties to use the WebSphere port number and host name. The WebSphere default port is 9080. • Internal Dispatcher URI • External Dispatcher URI • Content Manager URI • SDK URI 6. Under Environment, ReportNet Service, right-click Cognos ReportNet, and then click Delete. Now ReportNet will not run as a service, which is not required for WebSphere. 7. Complete other required configuration changes such as • specifying properties for the Content Manager database • entering user IDs and passwords If you used the default settings for the ReportNet installation, you may only have to make minor changes to the default configuration settings (p. 40). You can review the configuration for single computer installations (p. 33), or for distributed installations (p. 37), to determine if there are any additional changes required. 8. Save the configuration and close Cognos Configuration. If you are prompted to start the ReportNet service, click No. Cryptographic keys are created using the WebSphere JVM. 9. From WebSphere_location/AppServer/bin, open the startServer.bat file (Windows) or startServer.sh file (UNIX) in an editor. Installation and Configuration Guide 79
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:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28: 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 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 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 77: Chapter 7: Advanced Configuration O
Page 81 and 82: Chapter 7: Advanced Configuration O
Page 91 and 92: Chapter 8: Setting Up the Samples Y
Page 93 and 94: Chapter 8: Setting Up the Samples 7
Page 95 and 96: Chapter 8: Setting Up the Samples S
Page 97 and 98: Chapter 9: Setting Up an Unattended
Page 99 and 100: Chapter 9: Setting Up an Unattended
Page 101 and 102: Chapter 10: Uninstalling Cognos Rep
Page 103 and 104: Appendix A: Manually Configuring Re
Page 105 and 106: Appendix A: Manually Configuring Re
Page 107 and 108: Appendix B: Troubleshooting Use thi
Page 109 and 110: Appendix B: Troubleshooting Unable
Page 111 and 112: Appendix B: Troubleshooting For Con
Page 113 and 114: Appendix B: Troubleshooting 2. If y
Page 115 and 116: Appendix B: Troubleshooting Databas
Page 117 and 118: Appendix C: Database Schema for Log
Page 119 and 120: Appendix D: Database Clean Up Scrip
Page 121 and 122: Glossary anonymous access A method
Page 123 and 124: Glossary In Framework Manager, name
Page 125 and 126: Index A adding resources, 103 AIX e
Page 127 and 128: Index Framework Manager components,
Page 129 and 130:
Index server administration logging
show all

Cognos ReportNetTM Installation and Configuration Guide

Create successful ePaper yourself

Delete template?

Save as template?