Cognos ReportNetTM Installation and Configuration Guide

More documents

Recommendations

Info

Chapter 2: Installing ReportNet on UNIX 9. Grant create and drop table privileges on the content store to the user account. Ensure that the user account has CREATETAB, CONNECT and IMPLICITSCHEMA privileges for the content store. Ensure that the user account has USE privileges for the USER TEMPORARY tablespace and other appropriate tablespaces associated with the content store. For Windows XP, ensure that the user account has GRANT privileges for the USER TEMPORARY tablespace. Install ReportNet on UNIX Use the installation wizard to select the components you want to install and the location on your computer where you want to install them. Only the components that you choose to install are copied from the CD to your computer. Tip: You can install the gateway and Report Server components on multiple computers. You install Content Manager on only one computer. Install ReportNet components using either a character-based interface or a graphical user interface. To run graphical-mode installation, the console attached to your UNIX computer must support a Java-based graphical user interface. ReportNet respects the file mode creation mask (umask) of the account running the installation program. This affects only the installation directories. It does not affect the file permissions within the directories. However, run-time generated files, such as logs, respect the umask. We recommend umask 022 on the installation directory. Ensure that you verified your system requirements (p. 17) and that you created the database for the content store. Ensure also that required third-party software, such as a Web server and a Java Virtual Machine, is available. Ensure that if ReportNet uses a relational database as a data source for metadata, you set the environment variables for these databases. Tip: If you plan to use ReportNet with a third party application server, such as WebSphere or WebLogic, to avoid file permission conflicts, create a new UNIX group. You could call this group reportnet. This group must contain the user that starts the application server 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. Steps 1. Set the JAVA_HOME environment variable to point to the location of your Java Runtime Environment (JRE). 2. Mount the ReportNet CD with Rock Ridge file extensions. Important: To mount the Cognos CD on HP-UX, do the following: • Confirm that the pfs_mount daemons are running by typing ps | grep pfs • If the pfs_mount daemons are not running, type bg pfs_mountd bg pfsd • Type pfs_mount -t rrip /Device Name/cd-rom • Type pfs_umount • Stop the pfsd and pfs_mountd daemons to unmount the CD. 22 Cognos ReportNet TM
Chapter 2: Installing ReportNet on UNIX 3. Go to the directory that is appropriate for your operating system and start the installation: • If you use XWindows, type ./xstartup • If you do not use XWindows, type ./xwsetup 4. Follow the directions in the installation wizard and copy the required files to your computer. 5. Choose how to proceed in the Finish page of the installation wizard: • We recommend that you do not configure ReportNet immediately because you must do other tasks first to ensure that your environment is properly set up. However, if the console attached to your computer supports a Java-based graphical user interface, you can click Start Cognos Configuration • If you want to see late-breaking information about Cognos ReportNet, select View the Readme and then select Finish. Tip: For character-mode installations on UNIX, close the readme text file by pressing Crtl + C or q. • If the console attached to your computer does not support a Java-based graphical user interface or if you want to configure ReportNet later, click Finish. You can later configure ReportNet using Cognos Configuration by starting crconfig.sh in the crn_location/bin directory, or editing crnstartup.xml in crn_location/configuration directory. 6. On HPUX, append the crn_location/bin directory to the SHLIB_PATH environment variable. If you use Oracle or DB2, you can now set up the database client for the content store. You must update your Java security framework. Set Up the Database Client for the Content Store Database If you use Oracle or DB2 as the database server for the content store, additional steps are required after you install ReportNet before you can configure ReportNet. If you use an Oracle database for the content store, you must set up the JDBC driver. If you use a DB2 database for the content store, 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. 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 Content Manager is installed. 3. Rename the classes12.zip file to classes12.jar. Steps for DB2 1. Install the DB2 client software on the computer where Content Manager is installed. 2. Run the DB2 Client Configuration Assistant to configure a database alias to the content store. 3. On Windows, stop the DB2 services and the HTML Search Server. Installation and Configuration Guide 23
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 21: Chapter 2: 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 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:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
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

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

Delete template?

Save as template?