Specifications

Record Events and Annotate the Log

Perform the transaction in different ways. Be sure to perform the
transaction using all methods that users are likely to use. (For example,
add a record using menu commands, and add a record by importing data
from a file.) This will help you to identify important events relating to the
transaction, regardless of the method used. It may also help you decide
whether to monitor each method of performing the transaction
individually, or to monitor all methods of performing the transaction
together within one transaction rule. Be sure to annotate the fact that it is
the same transaction performed in a different way.

Create separate directories and event logs for different applications. If you
will be developing rules for several applications, create a separate working
directory for each one (for example, directories named OutlookEvents and
SAPevents), use the recording agent to create a separate event log file for
each application, and store the event logs in the appropriate directories.
Also, you can rename the event log file using the file name format
events.version.btl, where version is a meaningful indicator of a particular
version of the event log. This allows you to store multiple btl files in the
same directory.

Create one event log file for each application version and operating system
version. This will allow you to develop transaction rules that can monitor
multiple application versions.
To generate an event log file for use with BT Studio
1. Set up the recording agent.
2. Record events in the event log file.
3. Stop the recording of events.
4. Transfer the event log file to the BT Studio system.
Record Events and Annotate the Log
After reading Helpful Hints for Recording Events, follow this procedure to
record application activity in the event log file.
To record events
1. If the target application (to monitor) is already running on the client
system, close it. This ensures that the recording agent is able to record all
aspects of application activity in the event log file, including the
application’s startup activities.
2. If any other applications are currently running on the client system, close
them. This ensures that the event log file contains information only about
the target application. Extraneous data about other applications can make
it difficult to find the needed information in the event log.
3. Start BT Marker, using either of the following methods:
36 BTStudio Administration Guide