Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide
Chapter 4: Configuring ReportNet A local log server is automatically installed when you install Content Manager or the report server. The log server can send log messages to any number of storage media including the following: • file • database • UNIX syslog • NT Event log The log server can also send messages to a remote log server. If a remote log server is unavailable, log messages are redirected to recovery files on the local computer in the crn_location/logs/recovery/remote location. These recovery files have timestamp information in their file names, and are not readable like regular log files. These files are created until the remote log server becomes available. After the remote log server becomes available, an automatic recovery process starts. For more information, see the Architecture and Planning Guide. By default, the log server sends log messages to the crnserver.log file located in the crn_location/logs directory. Tip: The logging database has the same configuration and user account requirements as described when you created the database for the content store. Steps 1. On the computers where you installed Content Manager or the report server, start Cognos Configuration. 2. In the Explorer window, under Environment, click Logging. 3. In the Properties window, set the log server properties. Tip: To use SSL protocol for communication between ReportNet components and the log server, set the Enable TCP property and Enable SSL properties to true. 4. In the Explorer window, under Environment, right-click Logging, and click New resource, Destination. 5. In the Name box, type the name of the storage media or remote log server. 6. In the Type list, click the appropriate type and then click OK. 7. To configure a database: • Right-click the database, and click New resource, Database. • In the Name box, type the name of the database. • In the Type list, click the database type, and then click OK. 8. In the Properties window, type the appropriate values for the mandatory and optional properties. 9. Repeat steps 4 to 8 for each destination to which you want the log server to send messages. 10. From the File menu, click Save. If you use a DB2 or Oracle database to store the log messages, you must now set up the database client software or the JDBC 2.0 driver. Set Up the Database Client for the Log Database After you configure a database as the output device for your log messages, if you use Oracle or DB2 as the database server, additional steps are required. If you use an Oracle database, you must set up the JDBC driver. If you use a DB2 database, you must set up the database client software and the JDBC 2.0 driver. If you use a Microsoft SQL Server database, the JSQLConnect.jar file is installed to the appropriate location by default and no additional steps are required. 50 Cognos ReportNet TM
Chapter 4: Configuring ReportNet Steps for Oracle 1. On the computer where Oracle is installed, go to the ORACLE_HOME/jdbc/lib directory. 2. Copy the classes12.zip file to the crn_location/webapps/p2pd/WEB-INF/lib directory on the computer where you configured the log database. 3. Rename the classes12.zip file to classes12.jar. Steps for DB2 1. Install the DB2 UDB client software on the computer where the log database is located. 2. Run the DB2 Client Configuration Assistant to configure a database alias to the log database. 3. On Windows, stop the DB2 services and the HTML Search Server. 4. Go to the appropriate directory to copy the JDBC2 driver: • For version 7.2, on Windows, go to DB2_installation\java12 directory and run the usejdbc2.bat script. This copies the JDBC2 driver, db2java.zip, to the DB2_installation/java directory. • For version 7.2, on UNIX, go to the DB2_installation/java12 directory. • For version 8, go to the DB2_installation/java directory. 5. Copy the db2java.zip file to the crn_location/webapps/p2pd/WEB-INF/lib directory. 6. Rename the db2java.zip file to db2java.jar. 7. On Windows, restart the DB2 services and the HTML Search Server. 8. On UNIX, for version 7.2, ensure that you include the DB2_installation/java12 directory in the library path environment variable and that it comes before the DB2_installation/lib directory. Configure ReportNet to Use Alternate Gateways To improve Web server performance, you can configure ReportNet to use alternate gateways that replace the default CGI program. You can use one of the following gateways: • Microsoft Internet Application Programming Interface (ISAPI) to support Microsoft Internet Information Services on Windows • apache_mod to support Apache Web Server • servlet Before you configure an alternate gateway, we recommend that you first check that the ReportNet CGI gateway and your configuration work in your environment. Steps to configure apache_mod gateway 1. Stop Apache Web Server. 2. Append the crn_location/bin/cgi-bin directory to the appropriate environment variable: • On Solaris, LD_LIBRARY_PATH • On HPUX, SHLIB_PATH • On AIX, LIBPATH 3. On HPUX, ensure that the LD_PRELOAD environment variable points to the location of the shared libraries in the system directory (usually /usr/lib or /usr/lib/libcl.2) so that the Apache server can load the Cognos connector. 4. On the Apache Web Server computer, go to the Apache_installation/conf directory. 5. Open the httpd.conf file in an editor. Installation and Configuration Guide 51
- 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: Chapter 2: Installing ReportNet on
- Page 21 and 22: Chapter 2: Installing ReportNet on
- Page 23 and 24: Chapter 2: Installing ReportNet on
- Page 25 and 26: Chapter 3: Installing ReportNet on
- Page 27 and 28: Chapter 3: Installing ReportNet on
- Page 29 and 30: Chapter 3: Installing ReportNet on
- Page 31 and 32: 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 45 and 46: Chapter 4: Configuring ReportNet St
- Page 47 and 48: Chapter 4: Configuring ReportNet 3.
- Page 49: Chapter 4: Configuring ReportNet 4.
- Page 53 and 54: Chapter 4: Configuring ReportNet 6.
- 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 61 and 62: Chapter 4: Configuring ReportNet 3.
- 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 69 and 70: Chapter 6: Configuring Framework Ma
- Page 71 and 72: Chapter 6: Configuring Framework Ma
- Page 73 and 74: Chapter 6: Configuring Framework Ma
- Page 75 and 76: Chapter 6: Configuring Framework Ma
- Page 77 and 78: Chapter 7: Advanced Configuration O
- Page 79 and 80: Chapter 7: Advanced Configuration O
- Page 81 and 82: Chapter 7: Advanced Configuration O
- Page 83 and 84: Chapter 7: Advanced Configuration O
- Page 85 and 86: Chapter 7: Advanced Configuration O
- Page 87 and 88: Chapter 7: Advanced Configuration O
- Page 89 and 90: 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
Chapter 4: Configuring ReportNet<br />
A local log server is automatically installed when you install Content Manager or the report<br />
server.<br />
The log server can send log messages to any number of storage media including the following:<br />
• file<br />
• database<br />
• UNIX syslog<br />
• NT Event log<br />
The log server can also send messages to a remote log server. If a remote log server is<br />
unavailable, log messages are redirected to recovery files on the local computer in the<br />
crn_location/logs/recovery/remote location. These recovery files have timestamp information in<br />
their file names, <strong>and</strong> are not readable like regular log files. These files are created until the<br />
remote log server becomes available. After the remote log server becomes available, an<br />
automatic recovery process starts. For more information, see the Architecture <strong>and</strong> Planning<br />
<strong>Guide</strong>.<br />
By default, the log server sends log messages to the crnserver.log file located in the<br />
crn_location/logs directory.<br />
Tip: The logging database has the same configuration <strong>and</strong> user account requirements as<br />
described when you created the database for the content store.<br />
Steps<br />
1. On the computers where you installed Content Manager or the report server, start <strong>Cognos</strong><br />
<strong>Configuration</strong>.<br />
2. In the Explorer window, under Environment, click Logging.<br />
3. In the Properties window, set the log server properties.<br />
Tip: To use SSL protocol for communication between ReportNet components <strong>and</strong> the log<br />
server, set the Enable TCP property <strong>and</strong> Enable SSL properties to true.<br />
4. In the Explorer window, under Environment, right-click Logging, <strong>and</strong> click New resource,<br />
Destination.<br />
5. In the Name box, type the name of the storage media or remote log server.<br />
6. In the Type list, click the appropriate type <strong>and</strong> then click OK.<br />
7. To configure a database:<br />
• Right-click the database, <strong>and</strong> click New resource, Database.<br />
• In the Name box, type the name of the database.<br />
• In the Type list, click the database type, <strong>and</strong> then click OK.<br />
8. In the Properties window, type the appropriate values for the m<strong>and</strong>atory <strong>and</strong> optional<br />
properties.<br />
9. Repeat steps 4 to 8 for each destination to which you want the log server to send<br />
messages.<br />
10. From the File menu, click Save.<br />
If you use a DB2 or Oracle database to store the log messages, you must now set up the<br />
database client software or the JDBC 2.0 driver.<br />
Set Up the Database Client for the Log Database<br />
After you configure a database as the output device for your log messages, if you use Oracle or<br />
DB2 as the database server, additional steps are required.<br />
If you use an Oracle database, you must set up the JDBC driver.<br />
If you use a DB2 database, you must set up the database client software <strong>and</strong> the JDBC 2.0<br />
driver.<br />
If you use a Microsoft SQL Server database, the JSQLConnect.jar file is installed to the<br />
appropriate location by default <strong>and</strong> no additional steps are required.<br />
50 <strong>Cognos</strong> ReportNet TM