Specifications

Transactions Not Recognized
3. Double-click the transaction in the results pane again to see all of its
matching events.
Warning: Module "xxxx" has more than one transaction defined--this
feature is being deprecated.
4. This warning appears on the eHealth console and in arcontrol.log. BT
Studio issues this warning when you add transaction definitions to an
application rule set, and more than one transaction is assigned to the
same module.
5. In prior versions of BT Studio, you could use modules as a way to group
several transactions together for reporting purposes. In eHealth 5.7 and
later, this is still permitted, but the warning informs you that CA plans to
deprecate this feature. In a future release of eHealth, you will not be able
to assign multiple transactions to one module name.
6. Instead of using modules to group together transactions for reporting, you
can now use module sets.
Transactions Not Recognized
If you test transaction rules against an event log and find that BT Studio is not
recognizing defined transactions, do the following:

Make sure that the application is enabled. BT Studio cannot recognize
transactions for a disabled application rule set.

Make sure that you modified the correct rule set. In addition to enabling
the application, you must display the correct rule set in the rules pane
before editing it.

Make sure that the event log file includes application activity for the
startup of the application. If BT Studio does not observe the application
starting, it does not begin to monitor the application's transactions. To
record the startup of the application in the event log file, exit the
application, start event recording, and then start the application and
perform the transactions to be monitored. Test the rules against the new
version of the event log file.

Check the resource definitions for the application rule set.

The require section must list the processes that indicate a running instance
of the monitored application. Without properly defined required resources,
Application Response cannot recognize a running instance of the
application and so cannot monitor the application’s transactions.

The additional section must list the resource types that match the event
types used in the event specifications. For example, if a transaction rule
uses the Web BeginLoad and Endload events and the Windows MouseClick
and ButtonPress events, the additional section must include the Web and
Windows resources.
242 BTStudio Administration Guide