Getting started: Creating a profiling configuration for run-time problem determination
A profiling configuration controls data collection during profiling. Create a profiling configuration using the Profile dialog box in the Profiling and Logging perspective.
The steps presented here are intended to get you started with profiling. They include information about creating a profiling configuration to profile a Java application in a project that is open in your workspace. For information about profiling Java 2 Enterprise Edition (J2EE) applications and applets, see instead Getting started: Profiling J2EE applications.
Prerequisite: Agent Controller must be running on the machine on which you are collecting data. For information, refer to the installation guide.
To create a profiling configuration:
- Open a project.
- Open the Profiling and Logging perspective: Select Window > Open Perspective > Other . . ., and then in the Select Perspective dialog box, select Profiling and Logging.
- Open the Profile dialog box: Select Run > Profile . . .
- Create a profiling configuration for profiling your project: Double-click the Java Application entry to create a New_configuration entry.
- Enter a descriptive name for the profiling configuration in the Name field.
- Define the profiling configuration by specifying the following:
Tab
Java Application configuration
Main
Specify the project to profile; then search for eligible main classes and select one of them.
Arguments
Specify any arguments that your program or VM requires.
Classpath
Add any necessary projects, JARs, folders, variables, or libraries that your project requires.
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 specific 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 File > Import 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.
- For the next steps, refer to the Getting Started topic for the type of profiling you want to perform.
Note: You can also set default profiling preferences for all profiling runs. To display the Preferences pages, select Window > Preferences. In the Preferences page tree, expand the Profiling and Logging entry and select the appropriate page for the settings you intend to make.
Parent topic
Getting started with 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