Cognos ReportNetTM Installation and Configuration Guide

More documents

Recommendations

Info

Appendix A: Manually Configuring ReportNet You should now use a validating XML editor to validate your changes against the rules in the crnstartup.xsd file, located in the crn_location/configuration. Add a Component to Your Configuration The crnstartup.xml file contains configuration settings used by ReportNet and by default third-party components.You can change the components that ReportNet uses by copying XML elements from sample files into the crnstartup.xml file. You can then edit the configuration values to suit your environment. For example, to use an Oracle database instead of a Microsoft SQL Server database for the content store, you can use the ContentManager_language code.xml sample file to replace the default database connection information. ReportNet can use only one instance at a time of the following elements: • the database for the content store • a cryptographic provider • a configuration template for the ReportNet service You should be familiar the structure of XML files before you start editing them. Steps 1. Go to the crn_location/configuration/samples directory. 2. Choose a sample file to open in an editor: • To use Oracle or DB2 for the content store, open the ContentManager_language_code.xml file. • To use an authentication provider, open the Authentication_language_code.xml file. • To use a third-party cryptographic provider, open the Cryptography_language_code.xml file. • To send log messages somewhere other than a file, open the Logging_language_code.xml file. • To use a medium or large template for the amount of resources the ReportNet process uses, open the ReportNetService_language_code.xml file. 3. Copy the elements that you need. Tip: Ensure that you copy the code including the start and end tags for the element. For example, look for the (Begin of) and (End of) comments: ... 4. Go to the crn_location/configuration directory. 5. Open the crnstartup.xml file in an editor. 6. Paste the code from the sample file to the crnstartup.xml file and replace the appropriate element. 7. Change the values of these new elements to suit your environment. For the element, don’t change the class attribute. You can change the name attribute to suit your environment. For example, if you use an Oracle database for the content store, change only the name attribute to suit your environment. 8. Save and close the file. 104 Cognos ReportNet TM
Appendix A: Manually Configuring ReportNet 9. Run Cognos Configuration in silent mode by typing the following command: ./crconfig.sh -s This ensures that the file is valid and that passwords are encrypted. Manually Change the Global Settings If the console attached to your UNIX computer does not support a Java-based graphical user interface, you must manually edit the crnlocale.xml file located in the crn_location/configuration directory. You change global settings • to specify the language used in the user interface when the language in the user’s locale is not available • to specify the locale used in reports when the user’s locale is not available • to add currency or locale support to report data and metadata • to add language support to the user interface By default, ReportNet ensures that all locales, which may come from different sources and in various formats, use a normalized form. That means that all expanded locales conform to a language and regional code setting. Before you can add language support to the user interface, you must use the ReportNet Localization Kit to translate the strings that appear in the ReportNet user interface. You must also install the language files on all computers in your distributed installation. For more information, contact your Cognos support representative. Example 1 A report is available in Content Manager in two locales, such as en-us (English-United States) and fr-fr (French-France), but the user locale is set to fr-ca (French-Canadian). ReportNet uses the locale mapping to determine which report the user sees. First, ReportNet checks to see if the report is available in Content Manager in the user’s locale. If it is not available in the user’s locale, ReportNet maps the user’s locale to a normalized locale configured on the Content Locale Mapping tab. Because the user’s locale is fr-ca, it is mapped to fr. ReportNet uses the mapped value to see if the report is available in fr. In this case, the report is available in en-us and fr-fr, not fr. Next, ReportNet maps each of the available reports to a normalized locale. Therefore, en-us becomes en and fr-fr becomes fr. Because both report and the user locale maps to fr, the user having the user locale fr-ca will see the report saved with the locale fr-fr. Example 2 The user’s locale and the report locales all map to the same language. ReportNet chooses which locale to use. For example, if a user’s locale is en-ca (English-Canada) and the reports are available in en-us (English-United States) and en-gb (English-United Kingdom), ReportNet maps each locale to en. The user will see the report in the locale setting that ReportNet chooses. Example 3 The report and the user locales do not map to a common language. ReportNet chooses the language. In this case, you may want to configure a mapping. For example, if a report is available in en-us (English-United States) and fr-fr (French-France), but the user locale is es-es (Spanish-Spain), ReportNet chooses the language. Steps 1. On the computer where you installed Content Manager, go to the crn_location/configuration directory. 2. Open the crnlocale.xml file in an editor. Installation and Configuration Guide 105
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:
Page 29 and 30:
Page 31 and 32:
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:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
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 77 and 78: 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: 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?