Oracle® Real User Experience Insight User's Guide 12c Release 1 for Linux x86-64 Part Number E35689-02 |
|
|
PDF · Mobi · ePub |
This appendix provides a detailed discussion of the support available for the accurate monitoring of Oracle Application Development Framework (ADF)-based applications.
RUEI supports out-of-box monitoring of Oracle ADF applications. It automatically discovers Oracle ADF applications, and translates network objects to business functions. Using this support, individual user actions are automatically matched to the correct Web application, task flow, and view.
The monitoring support described in the rest of this appendix has been verified against applications based Oracle ADF version 11g.
You can create suite definitions for Oracle ADF-based applications in the same way as for any other supported Oracle Enterprise architectures. The procedure to create suites is fully described in Section 10.1.1, "Creating Suite Definitions".
The adf-faces-databinding-rt.jar
file provides a DMS-based implementation for the ExecutionContextProvider(oracle.adfinternal.view.faces. context.AdfExecutionContextProvider)
class. The implementation class has been pre-registered in the .jar
file, but the feature itself can only be enabled by specifying the following application context parameter in the web.xml
file:
<context-param> <description>This parameter notifies ADF Faces that the ExecutionContextProvider service provider is enabled. When enabled, this will start monitoring and aggregating user activity information for the client initiated requests. By default, this param is not set or is false. </description> <param-name>oracle.adf.view.faces.context.ENABLE_ADF_EXECUTION_CONTEXT_PROVIDER</param-name> <param-value>true</param-value> </context-param>
Because Oracle ADF is based on the Java technology, it is most likely that your Oracle ADF applications will use the JSESSIONID
state cookie. To enable RUEI to monitor and track users over the complete session, you should ensure the cookie path is set to "/". If your Oracle ADF application uses another cookie name for state tracking, you need to update the application definition to reflect this. In addition, be aware that user name recognition is based on the j_username
construction. See Section 12.2, "Specifying the Cookie Technology" for more information on cookie configuration.
An Oracle ADF application can be identified with a hostname. Generally, an ADF 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 I-1 shows how the dimensions of an ADF application are reported in RUEI.
Table I-1 Oracle ADF Suite Definition Mappings
Dimension level | Content |
---|---|
Application.name |
|
Application.page-group |
|
Application.page-name |
|
Where:
action
is the component display name (if available). Otherwise, it is the event type plus the component.
application
is the module name within the ADF environment.
view
is the view ID.
For example:
ADF.StoreFrontModule » myorders-task-flow/myOrders » valueChange
The ADF-specific data items shown in Table I-2 are reported by RUEI.
Table I-2 ADF-Specific Data Items
Item | Description |
---|---|
ADF suite/Code |
The code of an ADF framework suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored ADF framework suites. |
ADF suite/Name |
The name of an ADF framework suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored ADF framework suites. |
ADF action/Name |
The action that was triggered by this hit (such as view, action, dialog, focus, disclosure, launch, query, sort, valueChange, and so on). |
ADF application/Name |
The name of the application module within the ADF framework. |
ADF component client ID/Name |
An unique identifier of the element clicked by the end-user on the (previous) page. |
ADF component display name/Name |
The display name of the component that was activated by the (previous) end-user action. |
ADF component type/Name |
The type of the component that was activated by the (previous) end-user action. |
ADF Region/Name |
The name of the last active region within which the (previous) end-user action took place. |
ADF view ID/Name |
The identifier of a (part of) the screen where the (previous) end-user action took place. |
Detailed information about the architecture and functionality of Oracle ADF can be obtained from the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework. This is available at the following location:
http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/title.htm