Step 3. Run the application and recreate the problem
Click Run to open the New Configuration wizard. Double-click
on Java™ Application.
On the Main tab, ensure the application's main is selected.
On the Classpath tab, under User Entries, click Add External
JARs and add the following JAR files (where X:\inst_dir is the
toolkit installation directory and a.b.c is the version number on
the plug-in directory):
Note: The probe loads these be means of Java reflection
APIs so that there is only a runtime dependency, and the application's project
build path is not affected.
On the Profiling tab, click Add to add a new profiling
set. Then click Edit, and select the ARM instrumentation probe created
above. Because the probe defines the filtering via the target statements,
no further filtering set up is required here. Click Finish to exit
the profiling set editor.
Click Profile to launch the application.
Run the test steps to reproduce the performance problem. When finished,
stop monitoring by selecting Stop monitoring from the agent's pop-up
menu.
Once you have collected the performance data, you can begin
diagnosing the problem. You can view the data using several views including
statistics views and sequence diagrams of class and object interactions.