Specifying the J2EE Request Profiler as the data collection agent

The J2EE Request Profiler is used to collect execution data from distributed applications, which may span multiple processes and hosts. This collected data can be viewed as sequence diagrams. In order to use the J2EE Request Profiler for this purpose, first enable it (see the related task), and then specify it as the agent of choice.

  1. Start the application if not executing yet.
  2. From the main toolbar in the Profiling and Logging perspective, click the Profile button

     .

  3. Double-click on Attach - Java Process to create a new profile configuration.
  4. Specify a name for the configuration in the Name field.
  5. In the Hosts tab, if the workbench is remote to the process of the application that you want to attach to, add the remote host. Ensure that the correct host is selected on this page. Click Apply.
  6. Select the Agents tab.
  7. Select the J2EE Request Profiler from the Agents list using the arrow keys.
  8. Select the Profiling tab.
  9. Select the Execution History profiling set and click Edit.
  10. In the Edit Profiling Set dialog, select Execution Time Analysis. The Execution Time Analysis options are displayed in the right pane.
  11. Select Show execution flow graphical details. This option allows you to use the different graphical profiling views to examine the collected data.
  12. Click Next.
  13. Select WebSphere J2EE from the profiling set list.
  14. Click Finish.
  15. Click Profile to begin profiling the application. The profiling agent is displayed in the Profiling Monitor view.
  16. In the Profiling Monitor view, right-click on the profiling agent and select Start Monitoring. Data will now be collected.

You can now proceed with application execution. Whenever the execution of the application crosses boundaries of an ORB, an additional corresponding instance of the J2EE Request Profiler will automatically appear in the Monitors view.

Note: A monitor can have multiple hosts and each of those hosts can have multiple processes. Each process will contain only one J2EE Request Profiler.

At this point everything is set for you to view the sequence diagrams. See the related task: Displaying sequence diagrams using the J2EE Request Profiler.

Note: A J2EE Request Profiler sample is shipped with the product. For instructions on how to use it, refer to its readme (File > New > Example > J2EE Request Profiler > Next > Finish).

Related tasks
Enabling the J2EE Request Profiler
Displaying sequence diagrams using the J2EE Request Profiler
Viewing trace interactions using Sequence Diagram views

Reserved.