|Oracle® Real User Experience Insight User Guide
Release 4.5.1 for 64-bit Intel Linux
Part Number E12486-02
Oracle Real User Experience Insight (RUEI) provides you with powerful analysis of your network and business infrastructure. You can monitor the real-user experience, set Key Performance Indicators (KPIs) and Service Level Agreements (SLAs), and trigger alert notifications for incidents that violate them.
This guide is intended for all users of RUEI. These can be the Administrator, Security Officers, and Business and IT users. These roles are explained in Section 1.3, "Understanding User Roles".
This guide is directly relevant to the following users:
The Administrator responsible for maintaining the RUEI installation. This includes monitoring the system's health status, performing configuration backups, and for defining the scope of network operations that will be monitored. They are also responsible for creating and maintaining user authorizations.
The Security Officer responsible for managing security-related issues. These include defining which sensitive information (such as credit card details) are omitted from logging, and the installation and management of SSL keys to monitor encrypted data.
All other system users. These can be defined as business or IT users (or both), and their assigned privileges determine the access available to them. This is fully explained in Section 1.3, "Understanding User Roles".
Although no specific technical knowledge is required, some familiarity with network and Web technology is assumed. However, some organizational knowledge is required. In particular:
The Administrator should have a firm understanding of network topology, and a good operational knowledge of their organization's network and application environment. In addition, the individual assigned to this role should have a good understanding of RUEI.
Security Officers should possess a firm understanding of security-related issues. Moreover, they should be able to accurately assess the impact of network organizational changes.
As explained earlier, different levels of business and IT users can be defined. Their assigned permissions determine both the level of data to which they have access, and the configuration tasks they can perform. This could include identifying the monitored Web pages, and specifying how visitors to the Web site are identified. Additional activities could include configuring RUEI to reflect the monitored Web site's functional architecture, the definition of Key Performance Indicators (KPIs), and the creation of custom reports. In all cases, the permissions assigned to users should reflect both the appropriate access they require, and their organizational knowledge.
This guide is organized as follows:
Chapter 1 introduces you to RUEI. It explains the roles and permissions used within RUEI, the appearance of the RUEI interface, and how you can customize it. It should be read by all users.
Chapter 2 describes the standard report library provided with RUEI, as well as describing how you can create and modify your own reports. It should be read by all users who work with reports.
Chapter 3 describes the use of the data browser. It is directly relevant to both business and IT users authorized to access it.
Chapter 4 describes the use of KPI overviews and alert lists.
Chapter 5 describes how to set up KPIs and SLAs, and how to define alert schedules and notifications for them.
Chapter 6 describes how to define the pages that will be monitored, how to define the Web pages for which you want additional information to be available, the logical sequence of pages in transactions to be monitored, and those pages that should be monitored for the occurrence of specific text strings.
Chapter 7 describes how to manage the basic Web site configuration used for monitoring. This includes the required Web sites, the page naming to be used, and the page content and site error checks to be implemented.
Chapter 8 describes how to configure and manage the security-related settings used by RUEI. It is directly relevant to Security Officers.
Chapter 9 describes how to monitor the status of the system, perform backups and upgrades, issue messages to system users, manage users, and export data from RUEI. This chapter is directly relevant to the Administrator.
Appendix A provides a detailed description of the page tagging schemes supported for use with RUEI.
Appendix B provides an overview of the cookie technologies that RUEI supports.
Appendix C highlights the most common problems encountered when using RUEI, and offers solutions to quickly locate and correct them.
Appendix D presents a brief explanation of the dimension labels used in RUEI.
Appendix E provides an extended explanation of the HTTP result codes, generated by the Web server, that can be send to visitors as replies to requests.
Appendix B provides a detailed explanation of the support available within RUEI for the use of XPath queries.
Appendix G contains licensing information about certain third-party products included with RUEI.
Information on a wide variety of topics is available via the Oracle Web site (
http://www.oracle.com/enterprise_manager/user-experience-management.html). It is recommended that you visit it regularly for support announcements.
In addition, detailed technical information is available via the Support Web site (
https://metalink.oracle.com). This includes FAQs, training material, tips and tricks, and the latest version of the product documentation. A valid user name and password is required to access this Web site.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.
For more information, see the following documents in the Oracle Real User Experience Insight (RUEI) documentation set:
Oracle Real User Experience Insight Installation Guide.
The following text conventions are used in this document:
|boldface||Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.|
|italic||Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.|
||Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.|