Start and use the J2EE Request Profiler

The J2EE Request Profiler provides a means of profiling the J2EE artifacts that are hosted on the WAS. The profiling perspective provides several views that allow you to visualize how your application is behaving. To profile the application server first install the IBM Agent Controller on the node where the server is running. After the IBM Agent Controller is running, simply attach to the J2EE Request Profiler agent using the Profile button on the toolbar. The profile button is available in the Java, Debug, and Profiling perspectives. If your application server install spans multiple nodes and processes, the J2EE Request Profiler captures interactions between your J2EE artifacts and render these interactions as UML sequence diagrams. Also, the J2EE Request profiler has the ability to follow a invocation path automatically using a dynamic discovery mechanism; simply attach to the presentation layer of your application and all down-stream invocations are captured provided the IBM Agent Controller is installed on each of the nodes that host the application you are profiling.

To obtain more information on starting and using the J2EE Request Profiler refer to the Application Profiling Guide contained in the Application Server Toolkit installation. To access the Application Profiling guide, start the Application Server Toolkit. From the menubar select Help --> Help contents, and then select the Application Profiling Guide