Home  Applications > Using Dashboard > Working with the Siebel Solution > Using the SARM - User Trace Breakdown Diagnostic Tool > Results - Analysis Page > Transaction



Transaction

Click the Transactions tab to open the transactions table.

Transaction table for SARM - User Breakdown Diagnostic tool

This view is provided only for the user used by the Business Process Monitor, and not for a real user, in order to be able to process this data (for details, see Adding and Editing Transaction Monitors in End User Management Data Collector Configuration). This way, all the requests that belong to that transaction are identified and data can be generated.

Note: You must enable Siebel breakdown for the Business Process Monitor script monitoring your Siebel application. This can be done while configuring the Business Process Monitor transaction in the Admin > Monitors, and selecting Enable Siebel breakdown in the Transaction Breakdown Settings area (for details, see Adding and Editing Transaction Monitors in End User Management Data Collector Configuration).

The page displays the following information for each transaction:

Drilling down a transaction will display all the requests that belong to that transaction (for details, see Requests).

Note: The BPM Time is displayed only when the SARM User Session Trace breakdown diagnostics has been run after invoking a BPM script monitoring the Siebel Application. Some additional tuning of Siebel Application\Web Server environment variables is required. This is due to the fact that the flush ratio of SARM files is approximately 5 times slower in the Web Server than in the Application Server, and therefore running SARM with the default value of SARM_MaxFileSize variable may not be enough for the SARM user trace breakdown diagnostic tool to return data (contact Mercury Customer Support for additional information).




Copyright 2006 Mercury Interactive Corporation