Specifications

Syntax for Resource Definitions
Use the selection-kind qualifier to specify how many of the specified resources
must exist before Application Response recognizes that the application is
running. Valid values are as follows:
one – Each resource matching one of the resource specifications should be
considered a separate running instance of the application (for example, an
application with multiple GUI executables).
any – Any resource matching one of the resource specifications should be
considered part of a single instance of the application, although perhaps
resources matching all of the specifications may not be active at the same
time (for example, an application with multiple processes that come into
and go out of existence).
all – Resources matching all of the resource specifications must exist
simultaneously for Application Response to recognize that the application
is running (for example, an application with separate GUI and networking
executables).
resource
Use the resource keyword to identify the type of resource that must exist for
the application to be considered to be running and any resource-specific
parameters that further qualify the resource.
additional
Use the additional keyword to tell Application Response what types of activity
to monitor for the application.
Names for Transactions, Modules, and Failures
When creating names for transactions, modules, and failures in transaction
definitions, note the following restrictions:

Do not include spaces.

Do not include the following characters:
& * " \ ~ ` ! @ # $ % ^ , ( ) + = [ ] { } | ; ' < > ?
Use module names that are 15 characters or less, so that response path
names in reports are easy to read and do not get truncated. (Transaction and
failure names do not have this restriction, since they are not used in response
path names.)
BT Language Reference 115