In either case a JBoss or Tomcat collector, under localhost or a remote host,
represents a source of valuable performance data about that application. The
next step is to view that performance data using the RTI Console, and from there
you can request more or different data to dig deeper.
In general, we refer to this process as "Analyzing" and cover it in the next
chapter, Chapter 2, Analyzing Application Performance with RTI. The basic steps are listed briefly
below, with links to the sections that describe them in detail.
-
View Lightweight Transaction Profiling - By default, RTI is continuously profiling every Java application it is applied to. From the console, just click the blue clock icon, choose the collector of interest, and click OK. You'll get a Call Profile Snapshot table summarizing the execution profile for the past 10 minutes. If you're integrated with JBoss ON, you'll also see related resource charts for the same period.
-
Collect, Download and Analyze Deep Dive Performance Diagnostics - From the Call Profile Snapshot you can choose some transactions of interest, and launch a "deep dive" instance-level trace to better understand what's happening in your application. There are other ways to initiate trace data, and at any time you can "Transfer deep-dive performance data" to analyze what has been collected so far.
-
Add End-User Experience Data - As described in the previous section, RTI can also monitor your browser, Java test drivers, JMeter, and LoadRunner. When these collectors appear in your RTI Console, you can transfer deep-dive performance data from all of them, providing and end-to-end trace.
 |  |  |
| 1.6.1. Connecting to a Remote Performance Collector |  | 1.7. Troubleshooting Installation and Configuration |
