Skip Headers
Oracle® Real User Experience Insight Accelerator for JD Edwards EnterpriseOne Guide
Release 6.0.1 for Linux x86-64

Part Number E16356-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
View PDF

2 Monitoring and Reporting Considerations

This chapter explains how information within JD Edwards-based applications is captured and reported by RUEI. Information about specific mechanisms or characteristics to be aware of when monitoring JD Edwards-based applications are also highlighted. It is recommended you review this information to better understand the reporting of JD Edwards applications within RUEI.

2.1 Hostnames and URL Prefixes

A JD Edwards Implementation, and the JD Edwards instance, can be identified with a hostname. Generally, a JD Edwards suite can be accessed in two ways: using only the hostname, or using the fully-qualified hostname (including the domain). Generally, you only need to specify the domain.

Table 2-1 shows how an application's dimensions are reported in RUEI.

Table 2-1 JD Edwards Suite Definitions Mapping

Dimension level Content

productname (suite_name)

Application. page-group

suite_name.productcode » application name

suite_name.productcode » application code » formname.action


Figure 2-1 shows an example of how a JD Edwards application is reported in RUEI.

Figure 2-1 Example of JD Edwards Application Page-Group Reporting

Description of Figure 2-1 follows
Description of "Figure 2-1 Example of JD Edwards Application Page-Group Reporting"

2.2 Database Tables

The following JD Edwards database tables are used by the script to retrieve information about the customizations:

2.3 Data Items

The JD Edwards-specific data items shown in Table 2-2 are reported by RUEI.

Table 2-2 Dimensions

Item Description


In form/applications, people perform actions. These actions are monitored and reported here. (Most JD Edwards actions are encoded).


The name of the JD Edwards application used. The JD Edwards application name is based on the application code (P...) and the JD Edwards database configuration. It makes it possible to distinguish between the different applications monitored during sessions.


The environment selected when the user logged into JD Edwards.


The name of the JD Edwards form used. The JD Edwards form name is based on the form code (W...) and the JD Edwards database configuration. It makes it possible to distinguish between the different forms monitored during sessions


The JD Edwards product used. JD Edwards applications are part of a product which is shown here. JD Edwards products are sometimes referred to as system code or product code.


The name of an JD Edwards suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored JD Edwards suites.

2.4 Resources

You may find the following source useful: