Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide
Appendix A: Manually Configuring ReportNet 3. Add or modify the required element and attribute between the appropriate start and end tags. Type of Support Start Tag End Tag Language Content Locales Currency Product Locale Mapping Content Locale Mapping Fonts Tip: To remove support, delete the element. 4. Save and close the file. Tip: We recommend that use a validating XML editor to validate your changes against the rules in the crnstartup.xsd file, located in the crn_location/configuration. If you add a currency code that is not supported by Cognos, you must manually add it to the i18n_res.xml file in the crn_location/bin/ directory. Copy this file to each ReportNet computer in your installation. Run Cognos Configuration in Silent Mode Run Cognos Configuration in silent mode to apply the configuration settings on your computer if the console attached to your UNIX computer does not support a Java-based graphical user interface. Before you run the configuration tool in silent mode, you should use a validating XML editor to validate your changes against the rules in the crnstartup.xsd file, located in the crn_location/configuration. Steps 1. Ensure that the crnstartup.xml file in the crn_location/configuration directory on the local computer contains the property settings you want to use for your configuration. 2. Go to crn_location/bin. 3. Type the following configuration command ./crconfig.sh -s Tip: To view log messages that were generated files that were during an unattended configuration, see the crconfig_response.csv file in the crn_location/logs directory. Cognos Configuration applies the configuration settings specified in the local copy of crnstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts ReportNet service or process. 106 Cognos ReportNet TM
Appendix B: Troubleshooting Use this troubleshooting reference information and solutions as a resource to help you solve specific problems you may encounter during or after the installation of ReportNet components. Problems are characterized by their symptoms. Each symptom can be traced to one or more causes by using specific troubleshooting tools and techniques. After being identified, each problem can be fixed by implementing a series of actions. When you are troubleshooting, several files can help you: • The transfer log file This file records the activities that the installation wizard performed while transferring files. The transfer log file is located in the crn_location\instlog directory. The file name identifies the product name, version, and build number, and includes a time stamp. The following is an example of the file name format: tl-CRN-8-0-0-0-20021104_0942.txt • The transfer summary-error log file This file records the components you installed, disk space information, the selections you made in the transfer dialogs, and any errors the installation wizard encountered while transferring components. The transfer summary-error log file is located in the crn_location/instlog directory. The file name identifies the product name, version, and build number, and includes a time stamp. The following is an example of the file name format: tl-CRN-8-0-0-0-20021106_1122_summary-error.txt • The startup configuration file This file records your configuration choices each time you save your property settings. If you are unable to save your configuration, or are having problems you can revert to a previously saved configuration file. The backup configuration files are located in the crn_location/configuration directory. The following is an example of the file name format: crnstartup_200211231540.xml • The crnlocale.xml file This file records the configuration choices you make in Cognos Configuration for product and content locales, locale mapping, and currency support. If you experience problems with language support in the user interface or in reports, use these files to track your changes. The backup configuration files are located in the crn_location/configuration directory. The following is an example of the file name format: crnlocale_200211231540.xml • The default ReportNet log file named crnserver.log file, or other log files that you configure to receive log messages from the log server This file records information after you start the ReportNet service. Some log messages indicate problems. Most messages provide information only, but others can help you to diagnose problems in your run-time environment. • The cognos_uninst_log.htm file This file records the activities that the Uninstall wizard performed while uninstalling files. The log file is located in the Temp directory. You can use the log file to troubleshoot problems related to uninstalling ReportNet components. • The crconfig_response.csv file This file records the activities that Cognos Configuration performed while running in silent mode. This log file is located in the crn_location/logs directory. Another valuable troubleshooting tool is the Knowledge Base, which is available on the Cognos support site (http://suppport.cognos.com). The Knowledge Base is a database of problems and solutions for all Cognos products. Installation and Configuration Guide 107
- 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
- Page 101 and 102: Chapter 10: Uninstalling Cognos Rep
- Page 103 and 104: Appendix A: Manually Configuring Re
- Page 105: Appendix A: Manually Configuring Re
- 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
Appendix A: Manually Configuring ReportNet<br />
3. Add or modify the required element <strong>and</strong> attribute between the appropriate start <strong>and</strong> end<br />
tags.<br />
Type of Support Start Tag End Tag<br />
Language <br />
Content Locales <br />
Currency <br />
Product Locale<br />
Mapping<br />
Content Locale<br />
Mapping<br />
<br />
<br />
<br />
<br />
Fonts <br />
Tip: To remove support, delete the element.<br />
4. Save <strong>and</strong> close the file.<br />
Tip: We recommend that use a validating XML editor to validate your changes against the rules<br />
in the crnstartup.xsd file, located in the crn_location/configuration.<br />
If you add a currency code that is not supported by <strong>Cognos</strong>, you must manually add it to the<br />
i18n_res.xml file in the crn_location/bin/ directory. Copy this file to each ReportNet computer in<br />
your installation.<br />
Run <strong>Cognos</strong> <strong>Configuration</strong> in Silent Mode<br />
Run <strong>Cognos</strong> <strong>Configuration</strong> in silent mode to apply the configuration settings on your computer if<br />
the console attached to your UNIX computer does not support a Java-based graphical user<br />
interface.<br />
Before you run the configuration tool in silent mode, you should use a validating XML editor to<br />
validate your changes against the rules in the crnstartup.xsd file, located in the<br />
crn_location/configuration.<br />
Steps<br />
1. Ensure that the crnstartup.xml file in the crn_location/configuration directory on the local<br />
computer contains the property settings you want to use for your configuration.<br />
2. Go to crn_location/bin.<br />
3. Type the following configuration comm<strong>and</strong><br />
./crconfig.sh -s<br />
Tip: To view log messages that were generated files that were during an unattended<br />
configuration, see the crconfig_response.csv file in the crn_location/logs directory.<br />
<strong>Cognos</strong> <strong>Configuration</strong> applies the configuration settings specified in the local copy of<br />
crnstartup.xml, encrypts credentials, generates digital certificates, <strong>and</strong> if applicable, starts<br />
ReportNet service or process.<br />
106 <strong>Cognos</strong> ReportNet TM
Change language