Displaying the data collected by the J2EE Request Profiler as sequence diagrams

The J2EE Request Profiler is used to collect execution data from distributed applications, which may span multiple processes and hosts.

The Profiling Monitor view of the Profiling and Logging perspective displays profiling objects such as projects, monitors, hosts, processes, and agents that get created during a profiling session. It is a representation of the profiling environment. So, in the case of distributed applications, multiple hosts, processes, and related objects are displayed. The proper usage of the Monitors view is critical to understanding these sequence diagrams. It provides a very powerful and logical filtering system, which corresponds to the distributed application infrastructure.

Using resources at a lower level than the monitor results in the generation of partial diagrams, which correspond to the data that is collected from that particular object. For example, opening any diagram from a host, results in the generation of a diagram, which contains all the execution data pertaining to the traced application and its activities on that particular host only. The same applies to processes.

This is in contrast to opening sequence diagrams from the different hierarchical levels of resources in the Profiling Monitor view when the Java™ Profiling Agent is used to collect the profiling data. Since the whole application executes in one process in this case, the sequence diagrams that are displayed are identical despite the resource levels from which they are opened.

Note: In the case of single process on a particular host, diagrams displayed from the level of the process and the host will be identical. For more information on how to view distributed and non-distributed applications, see the Displaying different layouts section in the Using the Profiling Monitor view topic.

For information on the Profiling and Logging perspective, and performance and memory profiling, refer to the documentation for the Monitoring and profiling applications.

The J2EE Request Profiler is automatically enabled for all WebSphere® Application Server profiles.

Prerequisites:

• Complete the task of profiling an application using the WAS.

To view sequence diagrams:

1. In the Profiling Monitor view, double-click the J2EE Request Profiler. Alternatively, you can right-click the J2EE Request Profiler and select

   Open With | UML 2 Class Interaction.

   Tip: Double-click the J2EE Request Profiler to open the UML2 Interactions view for visualizing the profiling data collected by the profiler. The

   Open with context menu action on a J2EE Request Profiler displays a complete list of profiling views in which only the UML2 Interactions views are applicable to such profiler. Opening non-applicable views from the

   Open with context menu can result in an error message indicating the view selected is not applicable to the J2EE Request Profiler. See the next steps, for details on how to display the different interaction views for the J2EE Request Profiler.

2. By default to the right of the Profile Monitor view, the UML2 Trace Interaction view opens with the Class Interactions sequence diagram type.

3. Additional interaction views are available.

   1. In the toolbar of the UML2 Trace Interaction view, select the

      View Menu button and from the context menu select

      Switch to.

   2. Select any of the following sequence diagram types:

      • Host interactions

      • Process interactions

      • Agent interactions

      • Thread interactions

      • Class interactions

      • Object interactions
      For more details about these interaction view, see the UML2 Trace Interaction views topic.

      Tip: To determine which interaction view you are looking at in the UML2 Trace Interaction view, find the label directly under the UML2 Trace Interaction page label. In this screen capture, the UML2 Trace Interaction view is focused on the Class Interactions sequence diagram type:

      

4. If there are additional data incoming or you want to populate the view with profiling data that was collected from your Java process, in the Profiling Monitor view click the

   Refresh Views button .

 

Related concepts

J2EE Request Profiler

---