If required, you can override the global settings for the Oracle Forms protocol analysis with specific settings for a particular user-defined software service. You have the choice of defining an Oracle Forms software service over HTTP, HTTPS, TCP, or SSL.
Before You Begin
It is assumed for this task that you have already created a user-defined software service for this protocol and have specified one or more rules containing the essential components such as the IP address and port of the software service to be monitored. For more information, see
Configuring User-Defined Software Services in the RUM Console Online Help and Configuring Rules for User-Defined Software Services in the Data Center Real User Monitoring
Citrix/Windows Terminal Services Monitoring User Guide.
To specify protocol-specific settings:
1. Configure the Oracle Forms user identification for the service.
Open the User Recognition tab on the rule screen for the service. If you wish to override the global settings, clear the Use global settings box, and then choose one of the following methods of user identification:
Login method
Specify the request method for the login URL using one of the following methods:
Used for user login detection in web traffic. This setting defines an HTTP method in a request that contains a client username. The available values are: GET, POST, or no entry.
GET or POST
Used for user login detection in an Oracle Forms binary stream. Select this option to configure user detection based on Oracle Forms internal login. Selecting OFLogin disables the Login URL parameter.
OFLogin
Used for user detection in an Oracle Forms 6i mixed environment where the user login exists in web traffic and the Oracle Forms session ID exists in a pure binary ICXLogin
stream. To produce the user name of the Oracle Forms operation,
add
both the web server and all Oracle Forms servers when defining services in the software service rule configuration, as shown in the following graphic.
The web traffic contains the user login and ICX Ticket data, and the Forms binary traffic contains a corresponding ICX ticket, which is used to associate the user login contained in the web traffic with the data in the Oracle Forms binary stream: NOTE
Another method for identifying user names for traffic data records that do not have an associated user name is to configure the CAS to map the monitored user's name between analyzers for a given client IP address. For more information, see Overriding User
Name Mappings for the Same Client IP (CAS Only) in the Data Center Real User Monitoring Administration Guide.
Login URL
Defines the URL in an HTTP request containing a client username.
For an HTTP-based login, the login URL is the base URL where the username value is found in the trace file.
For an Oracle Applications/EBS login, the login URL is typically /OA_HTML/OA.jsp/. This field is redundant when extracting the user name directly from Oracle Forms traffic, so it is disabled if the OFLogin method is selected.
Login name parameter
This property is used for searching for a user name in HTTP requests.
For an HTTP-based login, this is the POST parameter key for the username found in the login URL. It typically has a value containing a username string.
For an Oracle Applications/EBS login, the username key is typically usernameField. For a Forms-based login, this is the label used for the username in the Forms login. Typically, this value is username.
Identification cookie pattern
This property helps to identify the cookie used for user assignment. Setting this properly helps AMD software match user names to TCP sessions.
For an HTTP-based login, this is the cookie key for a Forms session. Typically, it follows the JSessionID cookie for the login URL in the capture file, and the same cookie key is also found in the POST request for the Forms servlet.
For an Oracle Applications/EBS login, the key is usually customized.
For a Forms-based login, this is the cookie key for a Forms session. Typically, it is JSessionID.
Default: JServSessionIdroot
2. Specify an operation load time threshold per individual operation.
Open the Oracle Form Monitoring tab on the rule screen for the service. Right-click the Oracle Form Definitions table and select Add or Open. In the Oracle Form Operation dialog, provide a regular expression to match the operation of your interest and its human readable name. If you wish to override the operation load time threshold for this particular service, deselect Inherit from rule setting and provide a desired value in seconds. 3. Open the Availability tab and choose the specific types of failures to display in DMI reports.
For more information, see Configuring Oracle Forms Availability [p. 48].
4. Open the Options tab on the rule screen for the service and select or clear the following check boxes and enter the required information, according to your monitoring needs. Enable monitoring of persistent TCP sessions
When this is selected, TCP sessions that do not start with SYN packets are monitored. By default, this is selected.
Persistent TCP sessions are TCP sessions for which the start was not recorded. They are also referred to as non-SYN sessions. These sessions can be included in the TCP statistics, based on the configuration properties you enable in RUM Console. The inclusion of these sessions may render the statistics somewhat inaccurate and must be undertaken with care.
Operation load time threshold
An operation that takes more than this many seconds is considered slow. When Inherit from global setting is selected, the global setting is used. The global threshold value depends on the analyzer.
Generate sequenced transactions and ADS data
Select this option to provide data to the report server that consists of low-level protocol information, such as raw HTTP traffic data, which enables you to view the full HTTP request-response dialog.
5. Save or publish your changes.
For more information, see Configuring Rules for User-Defined Software Services in the
Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide.