Specifications

Monitor Multiple Application Versions
Monitor Multiple Application Versions
When you develop rules for an application, you specify the particular events
that characterize each transaction. If your users use different versions of an
application and/or different versions of an operating system, the specific
events of a transaction may differ. For example, screen titles or button titles
may change from one version to the next, or the workflow to perform a
particular task may change. If you plan to monitor transactions for two or
more versions of an application simultaneously, you must write the rules to
reflect these differences.
To monitor multiple versions of an application
1. Generate an event log file for each combination of application version and
operating system version.
For example, suppose that you want to monitor a custom Windows
application called EmpMgt, and your users are currently using two versions
of the software. In addition, some users use Windows NT and others use
Windows 2000. To ensure that you capture all relevant events that may
need to be included in the transaction rules, you must generate four event
log files: EmpMgt Version 1 on Windows NT, EmpMgt Version 2 on
Windows NT, EmpMgt Version 1 on Windows 2000, and EmpMgt Version 2
on Windows 2000.
2. Develop rule sets that define the transactions you want to monitor.
3. Test the rules against all of the event log files that you generated to
ensure that BT Studio can recognize the transactions for each version of
the application and/or operating system.
4. If the rules fail to recognize certain transactions when played against a
particular event log file, do the following:
5. Examine the log file to determine which events may be different for that
application version.
6. Refine the rules to ensure that all versions of the application and/or
operating system are supported. For example, you may want to use the
choice statement to indicate that an event may occur in two different
ways, or define two separate transactions: one for the first application
version, and another for the second application version.
7. Test the rules again to ensure that they work for all versions.
8. Save changes to the rule set and upload them to Application Response.
9. Whenever you upgrade the application or operating system, use it to
generate a new event log file for the monitored transactions and test the
existing rules against it. If BT Studio cannot recognize the transactions,
refine the rules to accommodate the changes, test them, save the
changes, and upload them.
The BT Studio Tool Set 25