Skip Headers
Oracle® Real User Experience Insight User Guide
Release 4.5.1 for 64-bit Intel Linux

Part Number E12486-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page

9 Monitoring and Maintaining the System

This chapter explains the tasks performed by the Administrator. These include monitoring the status of the system, performing backups and upgrades, working with the log file, and issuing messages to system users.

9.1 Monitoring the Status of the System

The Administrator can check the system's condition, and receive automatic status monitoring messages on the Status page. To reach this page, select System, and then Status. An example is shown in Figure 9-1:

Through the Status page, you can the status of the attached Collectors and the log file process, the current level of processing within the system, and the error log. You can also configure which users are notified (and how) about a system status error.

9.1.1 Temporary Delays and Alerts

Be aware that the system status indicator shown in Figure 9-1 is only updated when the browser screen is refreshed. If one or more of the system processes are found to be failing, a system alert can be generated (as described in Section 9.3, "Configuring System Failure Alerts"). Therefore, the situation can arise that a process is shown temporarily as failing (with a red cross), but no alert is generated. This is because the system status indicator has returned to normal by the time the system processes are checked.

Due to this design, when an alert is triggered, it is recommended that you regard it as a warning that the system is starting to fail. A failure can be the result of a system delay that is larger than the boundaries set the default (such as the latency between a hit on the monitored line, and the moment the information based on that hit is available in the Reporter, may not be long enough). This latency may be out of boundary within a high-traffic environment. A failure may also be the result of a temporary peak in traffic. However, if this condition persists, it is recommended that you review the monitored traffic level.

9.2 Viewing the Status of the Collectors

You can view the status of each Collector attached to the system by selecting System, then Status, and then Collector status. It opens the Network data Collectors window. An example is shown in Figure 9-2.

Figure 9-2 Network Data Collectors

Description of Figure 9-2 follows
Description of "Figure 9-2 Network Data Collectors"

The System (localhost) refers to the Collector instance on the Reporter system. Other Collectors within the network are represented by their IP address. For each Collector, the following menu options are available:

9.2.1 Working With the Collector Statistics Window

The information shown in this window (Figure 9-3) refers to the traffic monitored since midnight for the selected Collector, or the counters were reset. The Uptime field in the bottom left-hand corner of the window shows the time the Collector has been running. The uptime is reset when the Collector is restarted to update its configuration. You can reset all HTTP request counters shown in the window by selecting Reset counters from the View menu. Note that the counters will be reset the next time a network packet is detected. Hence, on an installation with no network traffic, the counters will never be reset. The display is automatically refreshed every two seconds.

Figure 9-3 Collector Statistics Window

Description of Figure 9-3 follows
Description of "Figure 9-3 Collector Statistics Window"

The tabs available in the top-left part of the part of the window provide a detailed breakdown of the traffic monitored by the selected Collector. They are explained in Table 9-1:

Table 9-1 Collector Statistics Report Tabs

Tab Description


Provides information on the available network interfaces for data collection. The number of interfaces and their status depends on the system configuration. Note that you will not see any "normally" configured interfaces. For each available interface, the name (in the form ethx), utilization (that is, current bandwidth), and state are displayed. For each interface, the state can be indicated as "OK", "Down", "Not configured", "Not active", or "Not promiscous" (the network adapter is only able to see traffic sent to its MAC address).


Provides a breakdown of the raw packet data transmitted over the monitored ports in terms of its protocols (such as IPv4 and ARP), and the number of measured frames. The "Truncated" listing indicates corrupted or dropped frames.


Provides an analysis of the TCP stream. The following counters are reported:

  • In progress: the number of currently active TCP sessions. These are sessions for which there is currently data transfer, or which are still in the connection establishment stage, or sessions for which the disconnect procedure has been initiated, but has not yet completed. This counter is a direct indication of the network load.

  • Max simultaneous: the maximum number ever attained by the In progress counter since the Collector was started.

  • Connection reset: the number of sessions that were terminated with a TCP RESET segment. Such sessions are immediately dropped by both parties: no further data (including a disconnect procedure) can be sent on such a session.

  • Connection refused: the number of sessions that could not be established because the requested service was missing. This happens if a peer tries to establish a connection on a system to a port on which no one is listening.

  • Total: the total number of sessions that have taken place since the Collector was start.

The following network error meters are also shown:

  • Out of sequence: indicates the segments which are received out of sequence. A high level of errors could indicate a problem in the quality of the underlying network between peers, which is usually the Internet between a client PC and a server.

  • Bad checksum: indicates corrupted segments en route. A high number of issues can indicate either a hardware, wiring, or network problem.

  • Bad offset and/or length: indicates the number of packets that had an incorrect length compared to their advertised length, and indicates a corrupt packet.

  • Dropped segments: indicates the total value of segments dropped for any unexpected reason, such as bad checksum, length, and so on. Check your hardware and network architecture when this value becomes high.


Provides an analysis of the monitored HTTP stream. In particular, the type of requests (such as GET or POST) they contain.

SSL connections

Reports the encryption method used for packets of encrypted data. In particular:

  • SSLv2: number of SSL version 2 connections (the Collector has no support for tracking these connections).

  • SSLv23: number of mixed mode SSL connections (that is, sessions that start as SSL version 2, but are scaled up to version 3 during the connection establishment phase).

  • SSLv3: number of SSL version 3 connections.

  • TLSv1: number of TLS version 1 connections.

  • Other: number of other connections (those connections that do not fit into one of above categories).

Errors related to SSL key management are reported. In particular:

  • No server key: the private SSL key for the requested server connection has not been made available to the Collector.

  • No master key: number of connections dropped because the master key for a connection could not be computed.

  • No session key: number of connections dropped because the session key for a connection is missing.

Information about (currently) unsupported encryption:

  • Pure SSLv2: client is using pure SSL version 2 protocol. This is not supported by the Collector.

  • Ephemeral: session relies on ephemeral keys for encryption. Such keys cannot be made known to the Collector and, as a result, such sessions cannot be tracked.

  • Anonymous DH: Session relies on anonymous Diffie-Hellman key negotiation. Such keys are unknown to the Collector and, as a result, such sessions cannot be tracked.

The Decrypt errors gauge indicates the connections which could not be decrypted. This can be caused by several reasons, such as the master key could not be decrypted, session keys were incorrectly computed, or a segment could not be decrypted.

SSL encryption

Provides a breakdown of the monitored encrypted data in terms of the employed encryption algorithm. The Used column indicates the amount (percentage) of total monitored SSL encrypted traffic that used an encryption algorithm, and the Errors column indicates the percentage of measured SSL encryption which failed (that is, could not be read).


Reports on the impact to the Collector. Note that if the peak load nears 100%, immediate action should be taken to prevent data being dropped by the Collector. See Section 8.2.2, "Limiting Overall Traffic" about traffic sampling. If this does not provide a solution, it is also recommended that you contact Customer Support.

9.2.2 Attaching New Collectors

To attach a new Collector to the system, select Register remote Collector from the Configuration menu. The Register Collector dialog shown in Figure 9-4 appears.

Figure 9-4 Register Collector dialog

Description of Figure 9-4 follows
Description of "Figure 9-4 Register Collector dialog"

Specify the IP address of the new system and, optionally, a brief description. When ready, click Register. See the Oracle User Experience Insight Installation Guide for more information about the configuration requirements for Collector systems.


This facility is also available by selecting System, then Status, and then Collector status. Note that users who are not authorized as the Administrator will receive a read-only version of this interface.

9.3 Configuring System Failure Alerts

In addition to being notified about KPI and SLA violations, you can also configure alerts for system failure. It is strongly recommended that you do so to ensure prompt action in the case of system problems. To do so, select System, then Status, and then Status notification. The dialog that appears is similar to that described in Section 5.5.1, "Alert Profiles".


The system status alerting does not consider any alerting schedules or escalation levels. When configuring alerts, ensure all user information (such as e-mail addresses and telephone numbers) is correctly specified for the people who should be notified in case of system status failures. Note also that the system status check is run every 10 minutes. Hence, if a system failure is indicated in Figure 9-1, you may not immediately receive an alert about it, but when the scheduled system check is run.

9.4 Viewing a Traffic Summary

You can open an overview of the monitored network traffic by selecting System, then Status, and then Data processing. This provides you with immediate information about hits, pages, and session processing, as well as the system load. An example is shown in Figure 9-5:

Figure 9-5 Data Processing Dialog

Description of Figure 9-5 follows
Description of "Figure 9-5 Data Processing Dialog"


In order for RUEI to correctly report on monitored traffic, it is strongly recommended that you regularly review this traffic summary. If necessary, review the RUEI configuration accordingly. For example, add additional cookie technologies. In addition, if the system is unable to track sessions, proper tracking of transactions will also not be available because transaction reporting requires session tracking.

9.5 Creating and Restoring Configuration Backups

You can create backups of your system's current configuration, and restore it if necessary. It is recommended that you regularly make backups. Note that backups only contain the system settings. For security reasons, SSL keys and collected data are not included.

To create or restore a backup, do the following:

  1. Select System, then Maintenance, and then Backup and restore. The Backup and restore dialog shown in Figure 9-6 appears.

    Figure 9-6 Backup and Restore Dialog

    Description of Figure 9-6 follows
    Description of "Figure 9-6 Backup and Restore Dialog"

  2. Use the radio buttons to selected the required operation. When ready, click Next.

  3. You are prompted to specify the location for the created or restored file.


    The generated backup file contains large amounts of information intended for Customer Support use only. Do not try to modify the file's contents.

9.6 Issuing Messages to System Users

You can issue messages to system users to keep them informed about important system events or operational issues. For example, scheduled maintenance periods, installation of service packs, or reported problems. The messages you post are displayed in the Messages area of the user's dashboard (see Figure 1-2). You can create new messages, or re-configure existing messages.

9.6.1 Creating Messages

To create a system message, do the following:

  1. Select System, then Messaging, and then New message. The dialog shown in Figure 9-7 appears:

    Figure 9-7 New Message Dialog

    Description of Figure 9-7 follows
    Description of "Figure 9-7 New Message Dialog"

  2. Specify a brief descriptive title for the message.

  3. Specify the content of the message. It is recommended that you try to keep this as brief as possible.

  4. Use the Date fields to specify when the message should appear on users' message areas. Note the last three messages in the user's message stack are displayed. Hence, the message will remain on users' screens until either three new messages have been displayed, or you explicitly remove the message.

  5. Use the Recipients field to specify the user roles that will receive the message. By default, messages are sent to all system users.

    Figure 9-8 Message Components

    Description of Figure 9-8 follows
    Description of "Figure 9-8 Message Components"

  6. When ready, click Save to create the message, or Cancel to discard the message.

The message is displayed in the Messages section of the appropriate users' dashboard (see Figure 1-2).

9.6.2 Modifying Messages

To change an existing message (for example, to modify its text or recipients), right click the message, and select Edit from the menu. You can then modify the message's properties using the dialog shown in Figure 9-7.

9.6.3 Removing Messages

To remove a displayed message from the users' message area, right click the required message, and select Remove from the menu. You are prompted to confirm the removal.

9.7 Working with the Error Log

In addition to the status information described in Section 9.1, "Monitoring the Status of the System", RUEI maintains an error log. This file contains a record of all system events. Normally, it should be empty. If any error is reported in the file, you should contact Customer Support.

To view the error log, select System, then Status, and then Error log. A listing of the file's current contents appears. Within the error log, you can select the following options from the File menu:

9.8 Configuring Text Message Providers

RUEI supports the use of text message notifications. In order to make use of this facility, all text message providers that you are planning to use must be configured and known to the system. To manage your provider information, select System, then Maintenance, and then Text message providers. The dialog shown in Figure 9-9 appears.

Figure 9-9 Text Message Accounts Dialog

Description of Figure 9-9 follows
Description of "Figure 9-9 Text Message Accounts Dialog"

Do the following:

  1. Click « Add new account » to define a new text message provider. The dialog shown in Figure 9-10 appears.

    Figure 9-10 Select Text Message Provider Dialog

    Description of Figure 9-10 follows
    Description of "Figure 9-10 Select Text Message Provider Dialog"

  2. Select the required text message provider from the list. It contains a number of predefined supported services. Each of these require an account with the associated provider. When ready, click Next. A dialog similar to the one shown in Figure 9-11 appears.


    If you specify a local GSM modem, a GSM modem must be installed on the system. The installed local modem must be a USB or serial GSM ETSI 07.05-compliant modem.

    Figure 9-11 Account Detail Dialog

    Description of Figure 9-11 follows
    Description of "Figure 9-11 Account Detail Dialog"

  3. The exact fields available within the dialog depend on the provider selected in Figure 9-10. For example, if you selected a local GSM modem, you are required to specify the local port and baud rate for the modem. If not known, automatic detection is available. Optionally, you can also specify a SIM PIN (if one is required).

  4. If you selected the predefined Mollie or Clickatell services, you are required to specify the user name, password, originator, API ID, and protocol sending method used for the account. These should have been given to you by your account provider. When ready, click Save. You returned to the dialog box shown in Figure 9-9.

  5. Right click the providers in the list and use the Move up and Move down options to control a provider's position in the list. Providers are tried in the order they appear in the list. Hence, the first account is tried and, on failure, the second one, and so on.

  6. When ready, click Close to leave the dialog.

9.9 Creating Helpdesk Reports

If you experience problems with the use or operation of RUEI, you can contact Customer Support. However, before doing so, it is strongly recommended that you create a Helpdesk report file of your system. To do so, select System, then Configuration, and then Helpdesk report. You are then prompted to specify a location to which the file should be downloaded.

This file contains extended system information that is extremely useful to Customer Support when handling any issues that you report.

Please note that this file contains software proprietary information. Do not try to modify its content.

9.10 Adding Network Data Collectors

To view the status of network data collectors, or to add new ones, select System, then Maintenance, and then Network Data Collectors. The use of this facility is the same as that described in Section 9.2, "Viewing the Status of the Collectors".

9.11 Performing Software Checks

The RUEI software uses core components of the underlying operating system, together with core functionality based on third-party software. To view the status of this underlying layer, select System, then Maintenance, and then Environment check. A window similar to the one shown in Figure 9-12 appears.

Figure 9-12 Environment Check Dialog

Description of Figure 9-12 follows
Description of "Figure 9-12 Environment Check Dialog"

This window provides you with an overview of the available external components and their status. For each component there is a status indicator, and a short description of what was found on the system. Ensure that all components are indicated as status OK. If necessary, resolve any reported errors with your system administrator. When ready, click Close.

9.12 Resetting the System

If you experience unexplained problems, you can restart processing to ensure that it is operating properly and synchronized. Note that selection of this option will result in a temporary delay in data availability and monitoring.

In the last resort, you can remove all collected data from the system. Alternatively, you can reset all parameters (such as created users and environment parameters) to their out-of-the-box default values.

To reset the system, do the following:

  1. Select System, then Maintenance, and then System reset. The System reset wizard shown in Figure 9-13 appears.

    Figure 9-13 System Reset Wizard

    Description of Figure 9-13 follows
    Description of "Figure 9-13 System Reset Wizard"

  2. Select the required option:

    • Restart system processing to reactivate system processing. This is the default.

    • Purge collected data to remove all collected data from the system.

    • Reset to factory defaults to remove all collected data and SSL keys, and resets all system parameters to their default values.

      When ready, click Next.


The Purge collected data and Reset to factory defaults options are irreversible. All collected data will be erased. In the case of Reset to factory defaults, all system settings will also be returned to their original state. Therefore, a complete initial configuration will be required before you have access to the Reporter interface. If you have previously created a backup (described in Section 9.5, "Creating and Restoring Configuration Backups"), you can restore this backup after initial configuration. This initial configuration is described in the Oracle Real User Experience Insight Installation Guide.

9.13 Managing the E-Mail Configuration

As explained in Section 2.2, "Using the Mailing Facility", RUEI can send automatic e-mails of requested reports. This facility uses the information specified during the initial configuration phase (described in the Oracle Real User Experience Insight Installation Guide). However, this configuration can be changed by selecting System, then Maintenance, and then Mail setup. The Mail setup dialog shown in Figure 9-14 appears.

Figure 9-14 Mail Setup Dialog

Description of Figure 9-14 follows
Description of "Figure 9-14 Mail Setup Dialog"

Use this dialog to specify the following information:

9.14 Setting System-Wide Preferences

As explained in Section 1.6, "Customizing Your Environment", users can customize the formatting settings used in their sessions. They can specify the characters used for the decimal point indicator and the thousand separator, and the date format that should be used. The administrator can also specify defaults for these settings on a system-wide basis by selecting System, then Maintenance, and then Formatting preferences.

9.15 Managing Users and Permissions

To start working with user definitions, select System, and then User management. The screen shown in Figure 9-15 appears.

Figure 9-15 User Management

Description of Figure 9-15 follows
Description of "Figure 9-15 User Management"

This screen lists the currently defined system users. The role and status of each registered user is shown through the color-coded scheme explained in Figure 9-16:

Figure 9-16 User Roles and Status

Description of Figure 9-16 follows
Description of "Figure 9-16 User Roles and Status"

9.15.1 Adding New Users

To create a new user, do the following:

  1. Select System, then User management, and click the Add new user button at the top of the user list (see Figure 9-15). The New user dialog box shown in Figure 9-17 appears:

    Figure 9-17 New User Dialog

    Description of Figure 9-17 follows
    Description of "Figure 9-17 New User Dialog"

  2. Within the Details tab, enter the user name by which the user will be known within your RUEI installation. This must be a unique name.

  3. Enter the user's full name.

  4. Enter the user's e-mail address. This is the address to which reports and e-mail alerts will be sent. Ensure it is correct.

  5. Specify and confirm a password for the new user. Note that after initial creation, the user is required to change their password within seven days. For further information on password security policies, see Section 9.15.4, "Enforcing Password Security Policies".


    Within RUEI, passwords are case sensitive, while user names are not. It is recommended that you do not include any diacritic characters, such as u-umlaut.
  6. Optionally, use the Disabled check box to disable the user at this time. You are free to enable them later.

    Figure 9-18 New User (Permissions) Dialog

    Description of Figure 9-18 follows
    Description of "Figure 9-18 New User (Permissions) Dialog"

  7. Within the Permissions tab shown in Figure 9-18, use the check boxes and radio buttons to specify the permissions to be assigned to the new user. The Business and IT access rights are described in Table 1-3.

  8. Click Save to create the user definition. You are returned to the user list shown in Figure 9-15.


    In addition to the settings described above, there are a number of additional settings (such as language, mailing type, and so on) that are set to their default values when a user is created. These additional settings can also be modified using the procedure described in Section 1.6, "Customizing Your Environment".

9.15.2 Modifying Existing Users

To modify a user definition, select System, and then User management. The User management panel shown in Figure 9-15 appears. Right click the appropriate user. The menu shown in Figure 9-19 appears:

The following options are available:

  • Edit: allows you modify a user's definition. This is described in Section 9.15.3, "Modifying a User's Settings".

  • Enable/Disable account: allows you to enable or disable the user account at this time.

  • Switch to: allows you to temporarily change to the selected user. This is useful if you want to view the modules and reports that they are authorized to see. Select Switch back from the View menu to return to your own role.

  • Remove: deletes the selected user from the system's user administration. Note that any private reports that the user created are also deleted. However, public reports created by the user remain available to other users.

9.15.3 Modifying a User's Settings

To change the settings for an existing user, do the following:

  1. Select the required user within the user list shown in Figure 9-15. The Edit user dialog shown in Figure 9-20 appears:

    Figure 9-20 Edit User Dialog

    Description of Figure 9-20 follows
    Description of "Figure 9-20 Edit User Dialog"

  2. Optionally, modify any of the displayed information. Note that the fields shown with a red asterisk indicate they are mandatory. That is, they can not be left blank. You can use the Disabled check box to prevent the user from using this account. You are free to enable them later. The Locked check box is normally activated automatically after a user has failed to correctly enter their password on five successive attempts. Password security is fully described in Section 9.15.4, "Enforcing Password Security Policies". You can use this check box to unlock the user's account.

  3. Click the Settings tab to view the user settings dialog shown in Figure 9-17:

    Figure 9-21 User Settings Dialog

    Description of Figure 9-21 follows
    Description of "Figure 9-21 User Settings Dialog"

  4. Within the Settings tab, you can modify the following:

    • Language: this is the language in which system messages and prompts appear. Currently, only English is available.

    • Mailing type: specifies whether the reports the user receives are sent in multiple e-mails (one for each report) or bundled into a single e-mail. The default is multiple e-mails.

    • Startup module: specifies the module in which the user starts their session. (For example, Reports, System, or User management). The default is the user's home page.

  5. Optionally, click the Permissions tab, and use the check boxes and radio buttons to specify the permissions to be assigned to the user. These are explained in Section 1.3, "Understanding User Roles"Section 9.15.1, "Adding New Users".

  6. When ready, click Save for the changes you have made to take effect. Otherwise, click Cancel to discard your changes.

Resetting the Administrator Password

In the event that you need to reset the admin user password, you can do so with the use of the set-admin-password script. This is described in the Oracle Real User Experience Insight Installation Guide.

9.15.4 Enforcing Password Security Policies

Each user must be defined and authorized to work with RUEI. The procedure to do this is fully explained in Section 9.15, "Managing Users and Permissions". In order to optimize the security of your installation, you can use the password settings facility to enforce your organization's security policies. Specifically, you can control the maximum length of user passwords, and how often users are required to change their passwords.

To control your installation's password enforcement, do the following:

  1. Select System, then User management, and click Password settings. The dialog shown in Figure 9-22 appears.

    Figure 9-22 Password Settings

    Description of Figure 9-22 follows
    Description of "Figure 9-22 Password Settings"

  2. Use the Password length field to specify the minimum number of characters that user passwords must contain. The minimum length is eight characters, and the maximum length is 255 characters.

  3. Use the Duration field to specify how often users are required to change their passwords. This should be between 7 and 60 days. The default is 60 days.

  4. When ready, click Save.

Password Enforcement

When creating and authorizing users, the following rules are automatically enforced:

  • User accounts are locked after five failed attempts. The account must be unlocked before the user can logon again (see Section 9.15.3, "Modifying a User's Settings"). However, locked users will continue to receive mailed reports and alerts.

  • A user password must have a minimum of eight characters. It must contain one or more non-alphanumeric characters (such as $, @, &, and !).

  • A password cannot include the defined user name, or their first and last name. In addition, the user's last three passwords are also remembered, and cannot be re-used.

  • Passwords are case sensitive.

9.16 Exporting Enriched Data

The Enriched data exchange facility enables the alternative analysis of the data collected by RUEI. In particular, it allows you to combine the data collected by RUEI with other data warehouse data. For example, a Customer Relationship Management (CRM) or Business Intelligence (BI) system. Using this facility, you can extract a rich set of collected data, such as product names, shopping basket values, and address information.

While the facility described in Section 2.11, "Exporting Report Data" is limited to report data, the enriched data exchange facility allows the export of all page-based data. In addition, report data export is based on HTTPS transfer, and enriched data exchange is based on SFTP file transfer. As described later, you can also customize the content of the exported data to include header information not normally collected by RUEI. Because the exported data is page-based, the available is restricted to applications, and does not include service-related data.

Enabling and Disabling Enriched Data Exchange

To enable Enriched data exchange, do the following:

  1. Select Configuration, then Applications, and then Enriched data exchange. The window shown in Figure 9-23 appears.

    Figure 9-23 Enriched Data Exchange

    Description of Figure 9-23 follows
    Description of "Figure 9-23 Enriched Data Exchange"

  2. Use the Enabled check box to enable or disable the Enriched data exchange facility. By default, it is enabled.

  3. Optionally, you can define additional data items to be included in the exported data. Typically, these are elements in the client request or server response headers that are not normally collected by RUEI, but which you want included in the exported data. To do so, click «Add new item». The dialog shown in Figure 9-24 appears.

    Figure 9-24 Add Enriched Data Export Item

    Description of Figure 9-24 follows
    Description of "Figure 9-24 Add Enriched Data Export Item"

  4. Specify the name to be assigned to the data item. This become the item's element name. For example, if specify the name "product", any matched data will appear in the export file with the label <product>.

  5. Use the Search type menu to define how the required item should be identified within the data collected by RUEI, and the scope of the search. You can specify to search within the client request header or server response header, using either a literal search or an XPath expression, or to search within a custom page-tagging implementation for a specific tag. Further information about support for custom page-tagging schemes is available in Appendix A, "Tagging Conventions".

  6. When ready, click Save. The new data item, if found in the monitored traffic, will start to be reported in the exports within 5 to 10 minutes.

    Existing data can be modified by right-clicking it, and selecting Edit. You can also select Remove to delete it, or select Remove all to delete all currently items.

XML Structure

The exported data is based on pageviews, and is in XML format. This enables its immediate importation into a wide variety of systems. An XSD file defines the structure of the exported XML. The XML schema is shown in Figure 9-25:

For an explanation of the standard data items featured in the schema, see Appendix D, "Summary of Data Items".

File location and Naming Structure

When enabled, the Enriched data export facility creates an export file every five minutes. The files are located in the directory /home/moniforce/websensor/xml-events/wg/xml-sespage/. Each file within this directory has the following name structure:



Exports are retained for a period of seven days before they are automatically deleted. In order to access these files, you will need a working FTP file transfer connection to the Reporter system. Consult your System Administrator for further information on this facility.

If required, you can use a symbolic link definition to change the location to which files are exported. Consult your System Administrator for further information on the use of this facility.

Security Considerations

While access to the data generated by the Enriched data exchange facility can be controlled in several different ways at the operating system level, it is recommended that you use SCP/SFTP and create a separate OS user with minimal access rights to the directory containing the exported data. You can then use an scp command to copy the data to a local system. For example:

scp -r <OS user>@Reporter:/home/moniforce/websensor/xml-events/wg/xml-sespage/20080903 .

Oracle BI

Oracle BI is based on the Oracle Business Intelligence Enterprise Edition (OBI EE), a comprehensive, innovative, and leading BI foundation. For further information, go to hhtp://