Specifications

Open an Event Log
e. On the Agent Properties page, click Configure Agent.
f. Click Export Agent Files.
g. On the Export Agent Files dialog box, do the following:
h. Specify a target directory.
i. Select the Export check box for Recording File.
j. Click OK.
3. Copy the event log file to the target directory on the BT Studio system.
You may want to rename the event log to reflect the application whose
activity it records (for example, eventsOutlook.btl). If you create separate
event logs for different applications or different versions of one application,
this prevents one log file from overwriting another, and reminds you of the
contents of each log file.
Open an Event Log
The default event log file is named events.btl. After recording events, you
transferred this or another event log to a directory on the BT Studio system.
To use the information recorded in the event log file to develop rule sets, you
must open the event log in BT Studio.
To open an event log
1. Start BT Studio.
2. Select File, Open or click Open Event Recording.
3. In the Open dialog box, use the Look In field to navigate to the directory
containing the desired event log file.
4. Select the file name or type it in the File name field.
5. Click Open.
6. Events recorded in the log file appear in the events pane of the BT Studio
window. Use the divider bar between the events pane and the rules pane
to expand the events pane.
7. Take a few moments to examine the information displayed in the events
pane. Each event is described on one line. For each event, BT Studio
shows a line number, the event type (such as Windows, Process, or
Connection), the event action (such as ButtonPress or MouseClick), and
more information about that event. Annotations created using BT Marker
appear on separate lines in the Engine State column. You will use this
information when developing rules.
Hint: When you first open an event log, test it against the default application
rules to make sure that BT Studio can recognize default transactions and that
you have the correct application rules enabled and displayed.
Generate an Event Log File 39