The log level defines which messages and TrueLogs are captured when recording an
Oracle Forms application.
-
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
from the menu bar.
The
Profile - [<profile name>] dialog box opens, and the
Replay category is displayed in the shortcut list on the left.
-
Select
Record in the shortcut list and click the
Oracle Forms icon.
-
Click the
Logging tab.
Here you can specify that additional properties have their values logged during recording.
-
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 recording 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.
-
Click
OK to save your settings.