I Oracle ADF Support

This appendix provides a detailed discussion of the support available for the accurate monitoring of Oracle Application Development Framework (ADF)-based applications. Note Oracle ADF support is provided as part of the default RUEI installation. No separate installation procedure needs to be applied.

I.1 Introduction

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.

I.2 Creating Oracle ADF Suite Definitions

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 6.4, "Working With Suites".

I.3 Enabling Monitoring of ADF Applications

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>

I.4 Specifying the Cookie Technology

As explained previously, session information is based on cookies. The procedure to specify the cookie technology used by your applications is fully explained in Section 7.1, "Specifying Cookie Technology".

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.

I.5 Suite Definition Mappings

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
Application.page-group	application » view
Application.page-name	application » view » action

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

I.6 Known Limitations

Currently, RUEI does not support all Oracle ADF functionality. In particular, the following known limitation exists:

• Reporting on regions, taskflows, and client-rendered-times is not supported.