Business Transaction Management (BTM) helps you manage IT based on your business. It tracks technical data within business transactions across applications. End users benefit through good service quality and improved application effectiveness. BTM bridges the gap between an application's technical and business aspects.
A business transaction is a set of automated interactions between IT systems that execute a business task or business process. In AppMon, a business transaction is a categorization of PurePaths defined by filter or grouping parameters. When a PurePath matches those parameters, one or more evaluation metrics are calculated to create the result set of the business transaction.
You can use Business Transactions to track special transactions such as login and buy in the application under diagnosis.
For example, you can track the number and response time of a login action for a specific user group for the application. The Business Transaction consists of a filter measure that checks for the occurrence for a specific user tag, such as a tagged web request measure. The default response time and count are selected by default. The splitting measure is application, which is also the default.
Business Transactions Visualization
The metrics associated with Business Transactions can be used for charting. See Charting for detailed information about charting of measures.
Evaluating Business Transactions generates or updates entries in the Business Transaction view, described in Business Transactions dashlet. An entry is created the first time you pass a Business Transaction filter. Subsequent positive filter evaluations increase the entry count and updates the displayed PurePath-related timing information.
New measurement value occurrences of measures used for splitting also create a new entry if the filter criteria are fulfilled. Recurring values update the entry representing the splitting criteria. Evaluation functions also generate or update entries within the Business Transaction view.
Business Transactions on stored sessions
You can reconfigure Business Transactions and the underlying measures in stored and offline sessions. For example, you can add PurePath-related measures, configure new thresholds, and you can create or change Business Transactions on new measures.
After making configuration changes to the System Profile, all stored session PurePaths must be reanalyzed to reflect configuration changes that result in new measurements for charting and Business Transaction values. Select Process Configuration Changes from the context menu to do this. This stores new measurements and Business Transactions to the analyzed session.
Use this to analyze stored session data from different perspectives by using new or changed business cases.
In the resulting measurements for the examples, boldfaced values are processed by the Time Series Center.
A PurePath contains different logging calls that contribute to a configured Logging Count measure.
+ doFoo - 10ms - MyApp + log - - Log4J + ... + log - - Log4J + log - - Log4J
count = 3, sum = 3, avg = 1, min = 1, max = 1
A single request results in multiple nodes with attachments. For web requests and web services, recursion detection filters nested calls. In this example, the
doFilter calls the
doGet that is suppressed.
+ doFilter - 10ms - Servlet (index.htm) + doGet - 8ms - Servlet (index.htm)
count = 1, sum = 10, avg = 10, min = 10, max = 10