|Oracle® Real User Experience Insight Accelerator for Oracle E-Business Suite Guide
Release 1.1 for Linux x86-64
Part Number E13494-06
This appendix highlights the most common problems encountered when installing the RUEI accelerator for Oracle E-Business Suite. The information in this appendix should be reviewed before contacting Customer Support.
As explained in Section 1.9, "Creating the EBS Suite Definition", it can take up to five minutes after the installation of the accelerator package before the Suites option becomes available in the Reporter interface.
However, it is possible that, even after waiting, this option does not appear. This problem is caused by an absence of measured data. It is recommended that, before starting to configure the suite definitions, you ensure network traffic is actually being seen by the system. To do so, you should select System, then Status, and then Collector status. The use of this facility is fully explained in the Oracle Real User Experience Insight User Guide.
If necessary, you can force the database RPMs to be applied immediately. To do so, logon as the
moniforce user, and issue the following command:
In the event that expected network traffic does not appear to be reported, it is recommended that you review the following points:
RUEI can monitor EBS applications based on the OA, JTT, PLS, Oracle Forms, and servlet frameworks. Generally, suites are configured to run on a specific port which differs per installation. These also need to be specified in RUEI. Select Configuration, then Security, and then Protocols. Review the defined port settings, and ensure they meet the requirements of your EBS applications.
Once data starts arriving into the RUEI system, it is not reported automatically. At least one application must be defined. At a minimum, this application must contain the relevant domain name, and the unique page-identification scheme within that domain.
If the monitored traffic includes VLAN-encapsulated traffic, ensure this is configured within RUEI. Select System, then Configuration, then Security, then Network filters, and then VLAN traffic, to review the defined settings. The use of this facility is fully described in the Oracle Real User Experience Insight User Guide.
Be aware there is no suitable out-of-the-box cookie available for session tracking in EBS. Therefore, a cookie needs to be created on the login page. This should cover the complete application. By default, the
Jession cookie only covers the application links, and not the images, CGIs, and libraries. While the
oracle.uix cookie does cover all hits, it is not unique for each visitor.
Be aware that because the Traffic summary facility (select System, then Status, and then Data processing) is based on application logic, non-application traffic (such as suites, services, and SSOs) is not represented in the traffic overviews.
It is strongly recommended that after installing the EBS accelerator, you login to the EBS application, and execute a critical path through the application. Then, you should search for recorded action within RUEI, and use the Session Diagnostics facility to verify that it is correctly reported. In particular:
Verify that descriptions are reported, and not codes. If codes are reported instead of application names, or page-group level codes instead of page-group names, it indicates that the information derived from the
create_EBS_info.sh script is not activated correctly.
A large number of reported short sessions indicates that Forms traffic is not being measured.
A large number of reported .
jsp files indicates the need for manual page naming (if required by the customer).