Defining a Request/Transaction Analysis report

About this task

The Request/Transaction Analysis report provides a whole picture about the behavior on the application server. After defining the request/transaction analysis, several reports become available: Trend report, Decomposition report, Request report detail, and Trace report. Each of these reports provides more specific data for understanding the application performance at every level.

To define a Request/Transaction Analysis report:

Procedure

From the top navigation, click Performance Analysis> Create Application Reports > Request/Transaction.
The Create report page opens.
Select yes or no to decide if you want the report to recur and click Next.
For these instructions, we are selecting no. If you want further instructions on scheduling reports, see Defining a Schedule report.
Select the group and the server from the box.
Click Next to continue creating the report.
The Report Filtering options page opens. It displays the options based on the Report Type you select.
Set the following options to filter the records returned in the report:
- Metric - Throughput per Hour, Throughput per Second, Throughput per Minute, Response Time, and CPU Time.
- Request Type - All, EJB, JSP, Servlet, SCA, CICS®, Web Service, OTMA, VTAM®, BTAM, APPC, Portal, and RMI-IIOP.
- Request Name - Unless you know the exact request string, always leave the field blank to return all requests or type the specific request name.
Click Next to continue creating the report.
The Date Range settings page opens.
Set the parameters to restrict the data returned in your report. For detailed instructions, see Understanding the Date Range settings.
Click View Report to view the report. To get a second data set for comparative analysis, click Next to open the Report Comparison page.
The Report Comparison page opens.
Select a report comparison type and view the comparison report by clicking View Report.
To save the report, click Save. For more information, see Viewing saved reports.