J2EE Request Profiler
The J2EE Request Profiler is an agent that resides within the application server process for the purpose of collecting data from the interception points of the e-business application's requests. The J2EE Request Profiler uses the Agent Controller to externalize this data so that it can be rendered by the various views provided by the Profiling and Logging perspective of the workbench.
Profiling of distributed e-business applications that run either within the boundaries of one machine or on a cluster of machines is accomplished by using either a single instance or several instances of the J2EE Request Profiler. Each J2EE Request Profiler is responsible for collecting profiling information for the application server process it resides within. Attaching to a number of J2EE Request Profilers on different application servers enables the collection of profiling data across these servers.
You have the choice as to the point in time within the application's execution period at which to attach. You can also select the J2EE Request Profiler that you attach to. Tracing of the application starts from the moment you attach to the J2EE Request Profiler, and start monitoring the application. As the execution of the application crosses the boundaries of a host, the remote discovery mechanism causes the attachment to other instances of the J2EE Request Profiler which represent remote WebSphereR Application Servers. These WebSphereR Application Servers host servlets and enterprise beans that participate in the application execution.
Note:
- There is only one instance of the J2EE Request Profiler that is active in a process that hosts the WebSphere Application Server.
- Whenever the J2EE Request Profiler is active in a process, it is active on the host that contains that process as well.
- There can be multiple instances of the J2EE Request Profiler that you are attached to.
You do not have to do anything to the application server to enable a profiler.
The J2EE Request Profilers collect data from requests arriving on EJB containers as well as web containers. This data collection mechanism enables the creation of sequence diagrams, which represent interactions among servlets, JSPs, and enterprise beans, while ignoring other artifacts of the application infrastructure that do not represent the business logic of the application. The collected data enables the creation of a variety of different diagrams, which are defined for specific levels of the profiling hierarchy (monitors, hosts, processes and agents). The Sequence Diagram views of the Profiling perspective offer the following currently implemented diagram types:
- Host interactions
- Process interactions
- Thread interactions
- Object interactions
- Class interactions
The Sequence Diagram view shows details about the application from the point in time at which you attach to the J2EE Request Profiler and start monitoring the application.
For information on the Profiling and Logging perspective, and profiling of applications, refer to the documentation for the Profiling tool.
Related tasks
Enabling the J2EE Request Profiler
Working in the Sequence Diagram views(C) Copyright IBMR Corporation 2000, 2003. All Rights Reserved.