Trace Results - Component Details Page

Use this page to view details about the performance of a particular server-side component that was invoked by a J2EE application. This page is part of the Interactive Tracing feature.

Usage Tips

Consider the following usage tips as you use this page to analyze the performance of the server-side components of your transaction.

Checking the URL Field

Before you begin using this page, check the Component Details section of the page and note the value of the URL field. If the URL field shows a specific URL, this page contains information about the performance of this component each time it was invoked by that specific URL.

On the other hand, if the URL field contains the string "All URLs," this page contains information about the performance of this component each time it was invoked by any URL throughout the entire transaction.

Understanding Invocation Path List

To make it easier to analyze the performance of the selected server component, Enterprise Manager shows the performance details of the component for each HTTP Server request completed during the transaction. For more information, see About Invocation Paths.

When you review the data in the Invocation Path List, consider the following table column definitions.

Column	Description
Total Time	The total time spent processing the selected component and its child components. For example, the total time spent processing a servlet includes the time spent processing any EJB or JDBC/SQL components that were called by the servlet.
Component Time	The total time, excluding the time spent processing child components. For example, the component time for a selected servlet would not include the time spent processing any EJB, JDBC/SQL, or other Servlet/JSP components that were called by the servlet.

Understanding the Invocation Path Details

To view the context of a particular invocation of the component, select the invocation path number in the Invocation Path Details section of the page. Enterprise Manager updates the Invocation Path table at the bottom of the page.

For example, if you are analyzing the performance of a particular SQL statement within a JDBC component, the Invocation Path table provides you with information about the context of the SQL component. The SQL component might be executed by a particular EJB, which in turn, might be executed by a Servlet. The hierarchy of the table allows you to compare the total time spent on the SQL component with the time spent on other components of the parent EJB. The time spent on other components is shown in the Other row.

To view all the components of the parent EJB, simply return to the Trace Results - Overview page and drill down to view the component details for the parent EJB.

Related Topics

About Web Application Management

About J2EE Web Application Transactions

Enterprise Manager Information Roadmap