This appendix provides a detailed discussion of the support available for the accurate monitoring of Oracle WebCenter Portal and Oracle WebCenter Sites applications.
You can create suite definitions for WebCenter-based applications in the same way as for any other supported Oracle Enterprise architectures, however there are two types of WebCenter suites:
WebCenter Portal
WebCenter Sites
The procedure to create suites is fully described in Section 10.1.1, "Creating Suite Definitions".
WebCenter Portal suites work similarly to the ADF suites as described in Appendix I, "Oracle ADF Support".
To use WebCenter Sites suites, you must apply the templates as described in the WebCenter Quick Start Guide that is supplied with WebCenter or from a demonstration application, for example:
http://www.oracle.com/technetwork/middleware/webcenter/avitek-sample-portal-086834.html
Previous releases of RUEI included support for creating a WebCenter suite (not specifying Portal or Sites). This option is still available, however it does not provide the same level of reporting.
To ensure the reporting of all WebCenter Sites dimensions edit the elements/Head_MP template to add the following line:
<render:callelement elementname="Utilities/RUEI/HttpHeaders" args="c,cid,site,siteLocale,d"/>
This line must be added before the line containing <render:calltemplate tname='Head${args.sitepfx}'args="c,cid,p,siteLocale,d,deviceid,packedargs" style="element"/> so that the end of the element is similar to the following:
<render:callelement elementname="Utilities/RUEI/HttpHeaders" args="c,cid,site,siteLocale,d"/>
<render:calltemplate tname='Head${args.sitepfx}' args="c,cid,p,siteLocale,d,deviceid,packedargs" style="element"/>
</cs:ftcs>
If you want to monitor an Oracle WebCenter Portal application, note that 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 WebCenter is based on the Java technology, it is most likely that your Oracle WebCenter 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 WebCenter 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 Session Tracking Mechanism" for more information on cookie configuration.
For information on WebCenter specific data items, see Table V-14, "WebCenter Applications".
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