Skip Headers
Oracle® Real User Experience Insight Accelerator for Siebel Guide
Release 5.1 for Linux x86-64

Part Number E14824-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

2 Monitoring and Reporting Considerations

This chapter explains how information within Siebel-based applications is captured and reported by RUEI. Information about specific mechanisms or characteristics to be aware of when monitoring Siebel-based applications are also highlighted. It is recommended that you review this information to better understand the reporting of Siebel applications within RUEI.

2.1 Hostnames and URL Prefixes

An Siebel implementation is analyzed by examining all traffic that passes between the Web server and the clients, either visitor browsers or software that accesses the Siebel Enterprise Application Integration (EAI) interface.

This traffic has the following structure:


Table 2-1 explains the above elements.

Table 2-1 Siebel Suite Definitions mapping

Element Content


The protocol used (sometimes HHTPS).


The server (host) name used to make the connection.


The port used to make the connection.


The name of the application (such as sales, eService, callcenter, and so on).


The language identifier, such as enu (English), deu (German), and so on.


The parameters specified to access certain functions. Currently, these are used to identify certain actions, and find business valuable names for these actions. The following parameters are recognized:

  • SWEScreen

  • SWEView

  • SWEApplet

  • SWEMethod

  • SWECmd

  • SWEExtCmd

  • SWEUserName

Figure 2-1 shows an example of how a Siebel application is reported in RUEI.

Figure 2-1 Siebel Application Reporting

Description of Figure 2-1 follows
Description of "Figure 2-1 Siebel Application Reporting"

2.2 Sessions

The recognition of individual visitor sessions is based on session cookies. By default, the session cookie used is _sn. If this cookie is used not used, it can be removed, and a custom cookie defined with the required name. Note that it is not possible to recognize cookies based on parameters in the URL.

It is strongly recommended that you ensure that the cookie name is correctly specified within RUEI to track visitor sessions.

2.3 Actions and Pages

The actions executed by the user are tracked by RUEI. The actions are recognized by their call to the Siebel server (a list of known parameters is used in that call). Looking at one user session, all hits are set in a time-ordered line. The recognized hits are marked as user actions, the others as elements of that action (such as images/objects/activeX-component loading/javascript-library-loading). The reported loading times per page are the calculated based on the action, and include all elements.

2.4 Reported Application Names

The application names reported in RUEI are based on the following format:

suite » application » screen » view » applet » action

The information is based on the parameter information that passes by on the line, and is preserved in the session, as long as it is valid.

2.5 Functional Error Recognition

Siebel errors are recognized as page elements when they start with SBL-string, where string is an 8-character code. These errors are reported as functional errors. In addition, it is also possible to define strings manually on the page that should be classified as functional errors.

2.6 Data Items

The Siebel-specific data items shown in Table 2-2 are reported in RUEI.

Table 2-2 Siebel-Specific Data Items

Item Description


The applet in which the end user was navigating. Applets allow access to the data in order to create, view, and modify.


The technical action that the end user was performing (if any).


The Siebel module that the end user was browsing. For example, Callcenter, HR, Marketing, and CRM.


The screens used within the Suite. A screen is a logical collection of views. It is not a visual construct in itself; rather, it is a collection of views that the menu bar and view bar can display.


The Siebel suite name, as specified in its configuration definition. This data makes it possible to distinguish between different monitored Siebel suites.


Similar to seen Siebel-Views. A view is a collection of applets which appear on screen at the same time.