This section describes the following topics:
Viewing J2EE Diagnostics Data
You view transaction breakdown data using the J2EE Diagnostics tab in the Controller. To open the J2EE Diagnostics tab, perform one of the following:
The J2EE Diagnostics tab opens.
To display the list of available diagnostics graphs, right-click in the graph and choose Show Available Graphs. The list of available graphs is displayed with the current graph outlined.
Note: The J2EE Transaction Breakdown Diagnostics Module graphs are only available if there is an active connection between the application server and the mediator.
Understanding the J2EE Diagnostics Tab View
The J2EE Diagnostics tab displays the following J2EE transaction breakdown information:
J2EE Transaction Breakdown graphs: Display the J2EE transaction breakdown information in graph format.
Connection Statistics/Status bar: Displays the name of the application server and the mediator, their connection status, and the number of errors in this scenario.
Transaction for breakdown: Enables you to choose a transaction for breakdown. You can use this to switch from any level of detail within one transaction to the same level of detail in a different transaction without requiring you to move up and down the entire breakdown chain.
Legend: The legend displays statistics on the data displayed in the graph. By default, the legend is sorted according to descending average response time. As this value is updated at every refresh period, the component order can change often, making it difficult to track components. To keep the components sorted in the current order, right-click in the legend area and choose Keep the Legend Sorted, or choose J2EE > Keep Legend Sorted.
Showing J2EE Measurement Breakdown
You can break down the transactions displayed in the Transaction Response Time whole scenario graph. From the transaction level, you can break down successively to the layer, class, and method level.
To view transaction breakdown graphs:
Note: For nested transactions, for example when transaction B is a subtransaction within transaction A, the subtransaction finishes earlier than the parent, and is therefore, reported to the Controller earlier than the parent transaction. This may cause data that is displayed for a parent transaction and a subtransaction not to be vertically aligned on the graph.
Viewing Call Chains and Call Stack Statistics
You can view the chain of calls for transactions and methods. The chain of calls answers the question “Who did I call?” You can also view the call stack statistics for methods. Call stack statistics answer the question “Who called me?” Chain of call and call stack statistics data are shown in the Calls window. The title of the window changes depending on which kind of data you are viewing.
To change the point to which the Calls window relates, drag the red time line to the desired spot.
Understanding the Call Windows
You use the Call Chain window to view the components that the selected transaction called. In the following one, all the calls in the critical path of the Action_Transaction.look_at_fish transaction are displayed.
You use the Call Stack Statistics window to view which components called the selected component. In the following figure, the executeQuery.SELECT COUNT query was called by __product._jspService, which was called by __template._jspService, and so on, down to the transaction at the bottom of the chain.
Switch to Method Chain of Calls: When the Call Stack Statistics data is displayed, displays the method Chain of calls data (only if the root is a method).
Switch to Method Call Stack Statistics: When the method Chain of calls data is displayed, displays the method Call Stack Statistics data (only if the root is a method).
Show Method Chain of Calls: Displays the Chain of Calls window.
Show Method Call Stack Statistics: Displays the Call Stack Statistics window.
Properties: Hides or displays the properties area (lower pane).
Columns: Enables you to select the columns shown in the Calls window. To display additional fields, drag them to the desired location in the Calls window. To remove fields, drag them from the Calls window back to the Columns chooser.
Measurement: Name of the method, displayed as classname.methodname. In the case of a database call, query information is also displayed. The percent shown indicates the percent of calls to this component from its parent.
% of Transaction (or Root Method): Percentage of the total time of the transaction (or method) from the total time of the root tree item.
No of Calls: Displays the amount of times that this transaction or method was executed.
Avg Response Time: Response time is the time from the beginning of execution until the end. Average response time is the total response time divided by the number of hits.
STD Response Time:The standard deviation response time.
Min Response Time: The minimum response time.
Max Response Time: The maximum response time.
% of Called: Displays the execution time, as a portion of the time of the calling component.
Total time: Displays the total method execution time, including the child execution time.
Expand Tree: Expands the entire tree.
Contract Tree: Contracts the entire tree.
Expand Worst Path: Expands only the parts of the path on the critical path.
Method Properties Area: Displays the full properties of the selected method.
SQL Query: Displays the SQL query for the selected method. (For Database only.)
Example Transaction Breakdown
The following graphs illustrate the breakdown of a transaction to its layer, class, and methods.
The following figure displays the top level Transaction Response Time graph. The graph displays three transactions:
The following figure displays the breakdown of the Action_Transaction.look_at_fish transaction into its layers:
The top of each breakdown graph displays the name of the graph and the name of the parent component. In this Time Spent on Each Layer graph, the Action_Transaction.look_at_fish transaction has been broken down to its layers (DB, EJB, JNDI, and Web). In Web transactions, the database (DB) layer is generally the largest.
The following figure displays the breakdown of the DB layer into classes:
In this Time Spent on Each JDBC Component graph, the DB layer of the Action_Transaction.look_at_fish transaction has been broken down to its classes. The Legend displays data on the classes.
The following figure displays the breakdown of a class into its methods:
In this Time Spent in Component Method graph, the SerialStatement class of the DB layer of the Action_Transaction.look_at_ fish transaction has been broken down to its methods. The Legend displays numerous method lines, differentiated by their SQL statements. When you point to a method line, its properties are displayed in a pop-up window.
J2EE Transaction Breakdown Diagnostics Graphs
You can view J2EE transaction breakdown data in the following graphs:
Transaction Layer Graphs
The class graphs can be displayed for Web server (SERVLET), application server (EJB), database (JDBC), or naming server (JNDI) classes:
LoadRunner Related Interview Questions
|SILK TEST Interview Questions||QTP Interview Questions|
|JMeter Interview Questions||Performance Testing Interview Questions|
|Rational Functional Tester Interview Questions||Function Point Analysis Interview Questions|
|Server Load Balancing Interview Questions||Sql Loader Interview Questions|
|HP QuickTest Professional Interview Questions||Performance Management Interview Questions|
Load Test Planning
The Loadrunner Controller At A Glance
Creating A Manual Scenario
Creating A Manual Scenario Using The Percentage Mode
Creating A Goal-oriented Scenario
Scheduling A Scenario
Using Rendezvous Points
Configuring A Scenario
Preparing To Run A Scenario
Managing Scenarios Using Quality Center
Running A Scenario
Viewing Vusers During Execution
Using Firewalls In Loadrunner
Running Vusers Over A Firewall
Monitoring Over A Firewall
J2ee Diagnostics Module
Erp/crm Diagnostics Modules
Configuring Online Graphs
Remote Performance Monitoring
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.