This page displays the performance and trace information for the transaction you just played using the Play with Trace button on the Web Transaction Home page. For more information about using the Play with Trace button, see Analyzing J2EE Web Application Transactions.
Note: The Play and Play with Trace Buttons are available only when you use Microsoft Internet Explorer 5.0 or later. In addition, you must have Operator privileges for this target in order to play the transaction; otherwise you will receive an insufficient privileges error. For more information, see About Administrators, Roles, and Privileges.
For each transaction you trace, the Trace Results - Overview page provides you with a high-level view of the time spent processing server-side components.
As you analyze the performance of the server-side components, consider the following methodology to locate performance bottlenecks:
Use the Transaction Total Time Overview chart to determine how much of the transaction time was spent processing server-side components as opposed to HTML and client requests.
Use the Server Side Overview chart to breakdown what server-side component types were invoked in this transaction and how much time was spent processing each component type.
Review the bar chart and table in the Details section of the page to determine which URLs spent the most time processing server-side components and which types of components they invoked.
You can then drill down for more information, using one of two approaches:
Click the response time value immediately below the Server Side Overview chart to view more information about the performance of a particular server-side component type. For example, the value for Servlet/JSP Time shows the total time spent processing servlets and JSPs during the entire transaction. Click the Servlet/JSP Time value to see a list of the application servlets or JSPs that were invoked by all the URLs in the transaction. The resulting page also shows how many times each servlet or JSP was invoked, as well as the context and response time for each invocation.
Click a value in the table to drill down to more details about how a component type was invoked for a particular URL within the transaction. For example, click the value in the JDBC/SQL column for a particular URL. Enterprise Manager displays the JDBC connection string used to invoke the SQL, as well as a list of the individual SQL statements invoked by the URL.
If you do not see any server data on this page:
The transaction may not involve any J2EE applications or database connections
JDBC/SQL Performance Details and Interactive Tracing may not be enabled for the OC4J instance where your applications are running. For more information, see Configuring OC4J for Middle Tier Request Performance Monitoring.
Related Topics
About J2EE Web Application Transactions
Configuring OC4J for Middle Tier Request Performance Monitoring
About Administrators, Roles, and Privileges
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.