Create / Edit Service Test - Forms Transaction Page

Forms Server URL

The URL of the Forms server on which the recorded transaction is to be played back.

Success / Failure String

You can specify one or more strings separated by semi colons (;). These strings are used to validate the text found in each Forms window. Each Success String must appear at least once within a transaction. Failure Strings should not appear within a transaction. If a Failure String appears within a transaction, or a Success String does not appear within a transaction, it is considered to be unsuccessful.

This is the method used to connect to the server and can be:

• HTTP / HTTPS

• Socket

Most Forms applications can be accessed only by authorized users. This field indicates the method used to log into the Forms application and can be either one of the following:

• Forms Login - Login occurs within the Forms application.

• Single Sign-On (SSO) - This option lets you access multiple accounts and applications with a single password, entered during a single connection.

• Oracle Applications Login - This option provides access to the Oracle E-Business Suite Home Page, which provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications.

Enter the System Identifier for the Forms transaction. If you are logging in using the Oracle Applications Login and it fails, check the Forms SID and try to login again.

This field is auto-populated by the Recorder and we recommend that it should not be changed. You can change it if you are sure that the SID is different.

The status of the Forms transaction. This can be Up or Down.

A high login time indicates that the authentication
server is overloaded. This might be the same as Forms server (in which case, you are likely to see a high forms elapsed time as well) or a different machine (usually the case with Oracle Applications Login or Single Sign-On login)

A high Forms Time might indicate network problem or problem with an unusually slow Forms server.

User Action: Check the network time in order to further diagnose the problem. A high Forms Time might further be diagnosed if the server is enabled for End-User Performance Monitoring.

The Total Time required for the Forms transaction. This is equal to to the Login Time + Forms Time.

User Action: If its value is unusually high, look at the more specific metrics to see where most of the time is spent. A high total time does not necessarily indicate that there is a problem. The transaction might be too long to execute in a short time. If the Total Time is too high, check the values in the Average Time Per Message metric.

This is the ratio between total time and the length of transaction. A high average time is usually an
indication of a slow down on the server side.

User Action: Use this metric to compare transactions running on the same server rather than total time.

A high slowest message time usually does not indicate a problem and is merely additional information to show the user which message took the longest time.

User Action: If the average time per message is unusually high, the user can look here to see how much
time is spent on the slowest block. If this metric is a
significant chunk of Forms elapsed time, the user can look to the alert message which came when any of these metrics went above the threshold. The alert message would contain a description for the slowest message which might be helpful in identifying the bottleneck.

If the status is down, the status description provides a detailed explanation for this status.

The server time required to perform certain Forms actions such as Commit, Query, Runform and others. The server time may be high if there is a high load on the Forms server.

User Action: Check whether the server processes are consuming most of the machine resources.

The database time required to perform certain Forms actions such as Commit, Query, Runform and others.

User Action: A high database time indicates that the database on which the Forms server is working has slowed down due to high load or other reasons.

The network latency between the client and the server. A high network time indicates a problem with the
connection between the beacon and the Forms server. It can be due to slow routers, overloaded network traffic etc.

User Action: We recommend running other network problem diagnosis software to resolve this issue.