Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide
Glossary Credentials are created for the components of ReportNet. If a user schedules or programs an action, then credentials must be stored in the content store. data source connection The named information that defines the type of the data source, its physical location, and any signon requirements. A data source can have more than one connection. data source A named set of connections to physical databases. Framework Manager uses the name of the data source for models. The ReportNet server uses the data source connections to access the physical databases. deployment archive A file used for deployment. A deployment archive contains the data from the content store that is being moved. gateway An extension of a Web server program that transfers information from the Web server to another server. Gateways are often CGI programs, but may follow other standards such as ISAPI and NSAPI. glyphs An image of a character in a font. Letters are glyphs, but in most cases, the term is used in discussions of non-alphabetic writing systems. HTTPS A secure version of HTTP that incorporates secure sockets layer (SSL) security. HTTPS is designed to transmit individual messages securely. The URL-accessed method is https://. The default HTTPS port number is 443. This default number is assigned by the Internet Assigned Numbers Authority. Cognos products use HTTPS and SSL to encrypt and transmit passwords securely over the Internet. job A group of reports and other jobs in ReportNet that you run and schedule as a batch. job step The smallest part of a job that can be run separately. Usually, a job step is a report. A job step can also be another job. locale A code that is used to set • the language or dialect used for browsers, report text, and so on • the regional preferences, such as formats for time, date, money, money expressions, and time of day In ReportNet, you can specify a locale for the product interface (product locale) and for the data in the report (content locale). A locale is also stored to record what locale an author used to create a report specification or a Framework Manager project. namespace In security, a collection of user accounts and user groups from an authentication provider. In XML, namespaces uniquely identify element types and attributes. An XML namespace is defined by a URI (Uniform Resource Identifier) whose purpose is to name the namespace, not necessarily to identify a location from which to obtain information. 122 Cognos ReportNet TM
Glossary In Framework Manager, namespaces uniquely identify query items, query subjects and so on. You import different databases into separate namespaces to avoid duplicate names. passport Information about the authentication of a user. ReportNet creates a passport each time a user logs on. The passport is retained until the session ends, either when the user logs off, or after a specified period of inactivity. A passport is a reference to a set of credentials maintained on the ReportNet server, not the credentials themselves. product locale The code or setting that specifies what language and regional settings to use for parts of the product interface, such as menu commands. response file An ASCII file that contains the setup data that is needed to automate an installation. In Cognos ReportNet, the response file automates only the process of copying files with the default configuration. role A special group that users can choose when they log on to change what groups they are authenticated as members of, so that they change what data they have authorization for. security provider A service that authenticates and defines users and the groups of which they are members. Installation and Configuration Guide 123
- 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 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: Glossary anonymous access A method
- 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
Glossary<br />
Credentials are created for the components of ReportNet. If a user schedules or programs an<br />
action, then credentials must be stored in the content store.<br />
data source connection<br />
The named information that defines the type of the data source, its physical location, <strong>and</strong> any<br />
signon requirements. A data source can have more than one connection.<br />
data source<br />
A named set of connections to physical databases. Framework Manager uses the name of the<br />
data source for models. The ReportNet server uses the data source connections to access the<br />
physical databases.<br />
deployment archive<br />
A file used for deployment. A deployment archive contains the data from the content store that is<br />
being moved.<br />
gateway<br />
An extension of a Web server program that transfers information from the Web server to another<br />
server. Gateways are often CGI programs, but may follow other st<strong>and</strong>ards such as ISAPI <strong>and</strong><br />
NSAPI.<br />
glyphs<br />
An image of a character in a font.<br />
Letters are glyphs, but in most cases, the term is used in discussions of non-alphabetic writing<br />
systems.<br />
HTTPS<br />
A secure version of HTTP that incorporates secure sockets layer (SSL) security. HTTPS is<br />
designed to transmit individual messages securely. The URL-accessed method is https://. The<br />
default HTTPS port number is 443. This default number is assigned by the Internet Assigned<br />
Numbers Authority.<br />
<strong>Cognos</strong> products use HTTPS <strong>and</strong> SSL to encrypt <strong>and</strong> transmit passwords securely over the<br />
Internet.<br />
job<br />
A group of reports <strong>and</strong> other jobs in ReportNet that you run <strong>and</strong> schedule as a batch.<br />
job step<br />
The smallest part of a job that can be run separately. Usually, a job step is a report. A job step<br />
can also be another job.<br />
locale<br />
A code that is used to set<br />
• the language or dialect used for browsers, report text, <strong>and</strong> so on<br />
• the regional preferences, such as formats for time, date, money, money expressions, <strong>and</strong><br />
time of day<br />
In ReportNet, you can specify a locale for the product interface (product locale) <strong>and</strong> for the data<br />
in the report (content locale). A locale is also stored to record what locale an author used to<br />
create a report specification or a Framework Manager project.<br />
namespace<br />
In security, a collection of user accounts <strong>and</strong> user groups from an authentication provider.<br />
In XML, namespaces uniquely identify element types <strong>and</strong> attributes. An XML namespace is<br />
defined by a URI (Uniform Resource Identifier) whose purpose is to name the namespace, not<br />
necessarily to identify a location from which to obtain information.<br />
122 <strong>Cognos</strong> ReportNet TM
Change language