Workflow Description for Creating and Analyzing a JRA Recording

This section is a workflow description of how to use the JRA system to find problems and improvement areas with your Java application and BEA JRockit. JRA is excellent to use when tuning your system, for example when looking for performance bottlenecks, such as latencies. The typical workflow when working with the JRA is described in Figure 2-1.

Figure 2-1 Typical workflow for comparing different settings of JRockit and Java application

The first steps are to start BEA Mission Control and then start you application so that you can start a JRA recording. The JRA recording takes a snapshot of the system's runtime behavior during the time period that you specify, typically a few minutes. As soon as the recording is complete, it opens in the JRA Tool where it can be analyzed "offline". If you want to, you can perform changes to your application or change command-line options for JRockit and create a new recording. This way, you have a chance to compare and contrast how different settings affect your application.

The steps for creating and comparing and contrasting a JRA recording are detailed in the following topics:

1. Start BEA JRockit Mission Control

2. Start Your Java Application

3. Create JRA Recording

4. View Your JRA Recording in the JRA Tool

5. Perform Changes in Application or Use Other Command-line Options for BEA JRockit

6. Create a New JRA Recording

7. Compare and Contrast Two Recordings in the JRA Tool