Profiling J2EE applications is similar to profiling Java™ applications, as described in the "Getting started" topics, but there are small differences, and you must perform special preliminary operations before you start.
You can profile J2EE applications either that are running within the Rational® Application Developer (RAD) environment, or that are that are running in stand-alone mode.
Parent topic: Getting started with run-time problem determination
Related tasks
Getting started: Creating a profiling configuration for run-time problem determination
Related information
Getting started: Memory leak analysis
Getting started: Performance bottleneck detection
Getting started: Thread bottleneck detection
Getting started: Code coverage monitoring
You can collect data from within the RAD environment for J2EE applications running on a different application server.
Refer to the "Getting started" section of the help to display and analyze the data you have collected.
You can collect data from J2EE applications that are outside RAD; for example, you can profile applications running on the WebSphere Application Server (WAS).
Tab |
Java Application configuration |
|
---|---|---|
Host |
Specify the target application server. |
|
Agent |
Specify the Java profiling agent. |
|
Profiling |
Overview sub-tab |
Select or add a profiling set. To collect data, each profiling set must include one or more profiling types, which are displayed in the text box in the lower half of the screen. For information about profiling types, refer to the Getting Started topic for the type of profiling you want to perform |
Profiling |
Limits sub-tab |
Set parameters if you want to limit data collection automatically. |
Profiling |
Destination sub-tab |
Define the profiling project and monitor, and, optionally, a .trcxml destination file for profiling output. (You can display this file by selecting from the main Profiling and Logging menu.) |
Source |
Not applicable. |
|
Common |
Specify the launch configuration for the program. The default is a local launch, with the program running in the background. |