Specifications

Define Resources to Monitor Transactions Based on Keystrokes
5. Stop the recording of events.
6. Transfer the event log file to the BT Studio system.
7. Develop rule sets for the target application.
 The resource definitions will be similar to those for GUI applications.
 The transaction definitions will use Windows KeyPress events,
Connection Request and Response events, and possibly other events
to identify transactions.
8. Update Application Response with the new rule set.
Define Resources to Monitor Transactions Based on
Keystrokes
When developing an application rule set that monitors transactions based on
keystrokes, define the resources as you would for a Windows-based
application.

In the require section, specify the processes that are required to indicate
that an instance of the application is running.

In the additional section, specify Windows (so that you can recognize
keystrokes) and Connection (to include network and server time in
response time measurements for transactions). You can also specify other
resource types as appropriate for the application.
Example
The following rule set for Remedy (whose executable name is aruser) shows
the resources required to track transaction response times when customer
service representatives log in.
[
BytesSent > 0
ServerName != "No-Server"
]
resources
{
require one
{
resource Process { ExecutableName=$(Application Executable) }
resource Process { ExecutableName="aruser"
}
additional
{
resource Windows { }
resource Connection { }
96 BTStudio Administration Guide