Specifications

Resource Definitions
resource Process { ExecutableName="NOTES" }
resource Process { ExecutableName="NLNOTES" }
}
additional
{
resource Windows { }
resource Connection { }
}
}
In this resource definition, the require section uses the one keyword,
indicating that Application Response will recognize any one of the listed
processes (NOTES or NLNOTES) as a separate running instance of the
application, and will monitor each separately. The
ExecutableName=$(Application Executable) syntax allows administrators to
add or remove executable names in the application’s list of required resources
using the eHealth Web interface.
In the additional section, the resource definitions for Windows and Connection
indicate that Application Response will monitor these types of activity for the
required Notes 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.
Example 2
The following is a slightly more complicated sample resource definition for
SAP.
resources
{
require all
{
resource Process { ExecutableName=$(Application Executable) }
resource Process { ExecutableName="FRONT" }
resource Process { ExecutableName="SAPGUI" }
}
additional
{
resource Windows { }
resource Connection { }
}
}
In this resource definition, the require section uses the all keyword to indicate
that both processes, FRONT and SAPGUI, must be running before Application
Response recognizes a running instance of the SAP application. When both
BT Language Reference 203