Specifications

How Transaction Limits Work
processes exist, then Application Response begins to monitor SAP
transactions. As soon as either process terminates, Application Response will
cease to monitor the application.
In the additional section, the resource definitions for Windows and Connection
indicate that Application Response will monitor these types of activity for the
required SAP processes and that transaction definitions can use these event
types, in addition to the Process event type listed in the require section.
Furthermore, the Connection resource permits Application Response to
measure network and server response times for the application’s transactions.
How Transaction Limits Work
Sometimes a particular transaction may take so long to complete that its total
response time skews the average response time for that transaction. Or some
other aspect of the transaction may be so unusual that its response time data
is not helpful in understanding your IT environment. These anomalies can
result in inaccurate interpretations of overall transaction response time trends.
For example, suppose that one transaction is performed 10 times. Most of the
time, the transaction takes one second to complete, but occasionally
something happens to make the transaction take 10 minutes (600 seconds) to
complete. Normally, the average response time is one second, but the
abnormally long transaction response time skews the average, giving the
impression that the overall average response time for the transaction is more
than one minute. To avoid such occurrences, you can set transaction time
limits or other constraints. When it observes a transaction whose response
time exceeds an upper limit, Application Response counts the transaction as
"timed-out" and stores this data for reporting purposes. If a transaction does
not meet some other constraint, Application Response ignores the transaction
and discards its response time data. In this way, the spurious transactions do
not skew the average response time to produce misleading results. You can
define these limits at the application level or the transaction level. You can
define multiple limits for each application and transaction.
Eliminating Transactions with No Server Activity
A typical transaction involves an action performed at the client, which sends a
request over the network to an application server. If Application Response
does not observe any network activity, it assumes that the application is local
to the client, and so the transaction has no server activity to measure. Many
Application Response customers prefer to omit such information from their
reports, choosing to focus instead on the response time of applications and
transactions that involve measurable amounts of server and network time.
204 BTStudio Administration Guide