So far you have performed the following:
  1. Installed at least one RTI Enterprise collector on an application server host.
  2. Enabled at least one Application for Monitoring.
  3. Installed the RTI Console in your desktop environment.
  4. Connected the RTI Console to a remote performance collector, if necessary.
  5. Optionally uploaded and added the RTI plug-ins to JBoss ON or RHQ, if you use one of those.
If you're integrating with JBoss Operations Network or RHQ, see Chapter 3, Integrating RTI and Extending JBoss Operations Network. Otherwise, read on.
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 Transaction Profile Snapshot table summarizing the execution profile since profiling began or was reset. 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 Transaction 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 soapUI. 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.

loading table of contents...