H WebLogic Portal (WLP) Support

This appendix provides a detailed discussion of the support available for the accurate monitoring of WebLogic Portal (WLP)-based applications. Note that WLP support is provided as part of the default RUEI installation. No separate installation procedure needs to be applied.

H.1 Introduction

RUEI supports out-of-the-box monitoring of WLP applications. It automatically discovers WLP Web applications, and translates network objects to business functions. Using this support, individual user actions are automatically matched to the correct Web application, desktop, portal, book, and page to provide contextual analysis.

RUEI supports the monitoring of file-based portals as well as streaming portals. For the latter, the Disc framework must be enabled. For the monitoring of file-based portals with the Disc framework not enabled, additional information must be uploaded about the configuration of the monitored portal. This is described in Section H.3, "Synchronizing RUEI with your WLP Environment". Note that the monitoring of streaming portals that do not use the Disc framework is not supported.

The monitoring support described in the rest of this appendix has been verified against applications based on WLP version 10.3.

H.2 Creating WLP Suite Definitions

You can create suite definitions for WLP-based applications in the same way as for any other supported Oracle Enterprise architecture. The procedure to create suites is described in Section 6.5, "Working With Suites".

H.3 Synchronizing RUEI with your WLP Environment

If the monitored suite instance is a file-based portal with the Disc framework not enabled, RUEI needs to understand how the portal is implemented within your environment. Do the following:

Copy the create_WLP_info.pl script from the /var/opt/ruei/processor/local/download/wlp directory to the location where you intend to run the script. Copy to the same location the .portal file used by the monitored application.
Run the create_WLP_info.pl script on the Report system. This script creates translations for the monitored environment. The script must be run with the following required parameter:
```
perl create_WLP_info.pl -portal file.portal
```
where file is the name of the .portal file used by the monitored application.

In multiple instance environments, run the script for each required instance, and separately preserve their created .txt files. Create a separate suite definition for each instance, as described in Section H.2, "Creating WLP Suite Definitions". In addition, be aware that if you make any changes to the monitored application, you need to re-run the script, and re-import the generated .zip file.
The script creates a number of .txt files in the directory where the script is executed. All relevant .txt files are collected and stored in a .zip file. Copy this .zip file to a location that can be used for uploading the files to the RUEI Reporter system.
Select Configuration, then Applications, then Suites, and select the suite you defined earlier in Section H.2, "Creating WLP Suite Definitions,". Click Upload Configuration.
Specify the name of the .zip file containing the generated .txt files. To protect against receiving empty definitions, the upload will fail when it contains empty .txt files. When ready, click Upload.

H.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".

When creating a WLP suite instance, a preconfigured cookie for the WLP environment is automatically created. This is implemented as a custom cookie, with the name JSESSIONID. Because WLP is based on the WebLogic technology, it is likely that the preconfigured cookie is suitable for your WLP applications. However, depending on the configuration of your environment, you may need to modify this. In addition, to enable RUEI to monitor and track users over the complete session, you should ensure the cookie path is set to "/".

H.5 Configuring User Authentication

RUEI supports out-of-the-box monitoring of WLP applications that employ user authentication based on the REST framework. However, if the monitored portal uses some other user authentication mechanism, then this needs to be configured. The procedure to do so is described in Section 6.2.10, "Defining User Identification".

H.6 Verifying and Evaluating Your WLP Definitions

To ensure the quality of the data being collected and reported by RUEI for your WLP-based applications, it is strongly recommended you verify their reported details. You should pay particular attention to the number of associated pages detected for the defined suite(s).

Select Browse data, then select the All pages group, and then the Applications sub-group. Within the individual dimensions, such as Page views and hits, you can see page views are reported for several applications. The suite name in the definition is shown between brackets. An example shown in Figure H-1 is for a streaming portal.

Figure H-1 Suite Page Views

Description of "Figure H-1 Suite Page Views"

H.7 Suite Definition Mappings

A WLP application can be identified with a hostname. Generally, a WLP 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 H-1 shows how the dimensions of a WLP application are reported in RUEI.

Table H-1 WLP Definition Mappings.

Dimension level Content

Dimension level	Content
Application.name	For streaming portals: `web-app portal/desktop` (`suite_name`) For file-based portals: `portal` (`suite_name`)
Application. page-group	For streaming portals: `suite_name.web-app portal/desktop` » `book` For file-based portals: `suite_name.portal` » `book`
Application.page-name	For streaming portals: `suite_name.web-app portal/desktop` » `book` » `page.action` For file-based portals: `suite_name.portal` » `book` » `page.action`

Application.name

For streaming portals:

web-app portal/desktop (suite_name)

For file-based portals:

portal (suite_name)

Application. page-group

For streaming portals:

suite_name.web-app portal/desktop » book

For file-based portals:

suite_name.portal » book

Application.page-name

For streaming portals:

suite_name.web-app portal/desktop » book » page.action

For file-based portals:

suite_name.portal » book » page.action

Where:

action is the name of the (REST) action executed by the user. In the All pages group, only actions are reported. In the WLP group, there is also an report option for actions. At the lowest level of actions, information about the involved portlet (if available) is reported. See Section H.9, "Known Limitations" for important information.
book is the title of the book for which a page is requested.
desktop is the name for the desktop used for the portal.
page is the title for the page that is requested.
portal is the name for the portal used within the Web application.
web-app is the name for the Web application used.

Figure H-2 shows an example of how a streaming portal is reported in RUEI.

Figure H-2 Example of WLP Application Page Reporting

Description of "Figure H-2 Example of WLP Application Page Reporting"

H.8 Data Items

The WLP-specific data items shown in Table H-2 are reported by RUEI.

Table H-2 WLP-specific Data items

Item	Description
WLP suite/Code	The code of a WebLogic suite. This data makes it possible to distinguish between different monitored WebLogic suites.
WLP suite/Name	The name of a WebLogic suite, as defined in Configuration / Suites. This data makes it possible to distinguish between different monitored WebLogic suites.
WLP book/Name	Name of the WebLogic book, which contains pages with portlets
WLP desktop/Name	Name of the WebLogic desktop. Together with WebLogic portal, WebLogic web application and suite name (as defined in Configurations / Suites) makes up the application name in RUEI.
WLP page/Name	Name of the WebLogic page. On pages, portlets are located. The pages themselves are contained in WebLogic books
WLP portal/Name	Name of the WebLogic portal. Together with WebLogic desktop, WebLogic web application and suite name (as defined in Configurations / Suites) makes up the application name in RUEI.
WLP portlet/Name	Name of the WebLogic portlet.
WLP action/Action	Name of the action. WebLogic actions are performed on pages.
WLP action/Portlet	Name of the action involving a portlet. WebLogic actions are performed on pages, sometimes involving a portlet. This level shows the portlet involved when seen.
WLP Web application/Name	Name of the WebLogic web application. Together with WebLogic portal, WebLogic desktop and suite name (as defined in Configurations / Suites) makes up the application name in RUEI.

H.9 Known Limitations

Currently, RUEI does not support all WLP functionality. In particular, the following known limitations exist.

Reporting is based on the last activated area. Hence, when a end user is browsing simultaneously in multiple browser windows, the reported page name may contain incorrect information.
Reporting on portlet level is very limited. For streaming portals, when actions involve a portlet (such as "move portlet on page"), and the portlet definition label is found in the response content or the URL of the action, is the portlet definition label reported in the WLP group. In the All pages group, portlets are not reported.

For file-based portals, when the action involves a portlet, the instance label is reported because file-based portals do not have portlet definition labels. File-based portlet instance labels are only reported when a portal configuration file is upload (see Section H.3, "Synchronizing RUEI with your WLP Environment").
The monitoring of streaming portals with the Disc framework not enabled is not supported.