Oracle Forms-specific settings allow you to modify how
Silk Performer interacts with
Oracle Forms clients during replay.
In
Silk Performer, expand the
Profiles node in the
Project tree.
Right-click the profile that you want to configure and choose
Edit Profile.
Tip: Alternatively, you can choose
Settings
> Active Profile from the menu bar.
The
Profile - [<profile name>] dialog box opens, and the
Replay category is displayed in the shortcut list on the left.
In the shortcut list, click the
Oracle Forms icon.
On the
General page, select a
Connection mode setting that reflects which type of connection the
Oracle Forms server accepts.
Oracle Forms clients can communicate with servers via
Sockets,
HTTP, or
HTTPS.
Note: This setting can be overridden by the
OraFormsSetConnectMode(connectMode) BDL function call.
Click the
Socket mode option button when the
Oracle Forms server is set up for socket mode.
Click the
HTTP mode option button for
Oracle Forms servers that are configured for HTTP connections.
Click the
HTTPS mode option button for
Oracle Forms servers that are configured for secure HTTP connections.
In the
Connection timeout text box, specify a timeout period (in seconds) to specify how long emulated clients should attempt to establish communication
with the server before they report an exception.
To configure additional runtime settings, you can optionally have the virtual user send a heartbeat message to the server
at a specified interval. This is useful when the
Oracle Forms client is not communicating with the server for a long period of time, for example during a long think time period. Check
the
Enable heartbeat with frequency of check box and enter an interval (in seconds) in the
sec field.
Check the
Automatically wait for application timers check box to direct the replay engine to wait for application timers to expire after each function call.
The
Application timer and window timeout text box specifies the maximum wait time for expiration of application timers and appearance of windows. Enter a timeout
setting (in seconds).
The replay engine waits for timers to expire after each function call. The function
OraFormsWaitForTimer can be used to make an application wait for timers to expire. Maximum wait time is specified by this setting. The function
OraFormsWaitForWindow may be used to have an application wait for windows to appear. This setting specifies the maximum wait time for window appearance.
Oracle Forms servers can allow certain client releases. Use the
Oracle Forms setting to specify the
Oracle Forms client version.
Oracle Forms clients send the required version when connecting to the
Oracle Forms server. Create profiles and change this setting when testing applications deployed on different server versions.
Note: This setting can be overridden by the BDL function call
OraFormsSetInt("INITAL_VERSION", theVersion).
Click the
Logging tab.
Here you can specify that additional properties have their values logged during replay.
From the
Log level list box, select the log level for virtual user logging:
None - TrueLogs will be generated, though no Oracle Messages will be logged and no detailed information about controls in the
log file will be written.
Error - In addition to the
None log level, errors that occur during replay are logged.
Normal - In addition to the
Error log level, Oracle messages are logged to the TrueLog and the log file.
Debug - In addition to the
Normal log level, detailed information about control messages is logged, for example in the
In Body and
Out Body tab in
TrueLog Explorer. This information is helpful for customizing and debugging your script when comparing it with Try Script runs. This option
should also be used when you encounter a problem during replay and you must send your log files to
Micro Focus SupportLine for analysis.
Additional properties to be logged in the TrueLog for each control in your application can also be defined. Such properties
are
Oracle Forms internal properties that must be defined using their internal names. In most cases you will not need to use this feature,
as default properties (name, value) are logged for each control. The
OraForms.bdh file contains a complete list of all internal properties, most of which are not used by controls and so will generally be
ignored if you define them.
In the
Additional properties text box, you can specify other properties for which virtual users are to log values.
Click
Add to open the
Additional Properties dialog box and add a property that is to have its value logged during replay.
Click
Edit to open the
Additional Properties dialog box and edit the selected property.
Click
Remove to remove a selected property. Click
Yes on the deletion confirmation dialog. No further values will be logged for this property.
Click the
Measuring tab.
Here you can specify a custom measurement level. By default, all available performance metrics are collected during test runs.
Check the
Enable all timers and counters for all controls check box to enable all timers and counters for all actions on controls during replay.
Alternatively, uncheck the
Enable all timers and counters for all controls check box and select a specific control from the
Control list box and select the specific timer/counter types that you want to have applied to that control:
Enable timers - Measure how long it takes to complete an action on the selected control.
Count round trips - Count the round trips for each action on the selected control.
Count bytes - Count the bytes sent and received for each action on the selected control.
Count messages - Count the messages sent and received for each action on the selected control.
Note: Alternatively, you can click the
Apply to All Controls button to apply your timer/counter settings to all controls.