Profiling the application using the WebSphere test environment
A process object, along with the associated agents is visible
in the Profiling Monitor view of the Profiling and Logging perspective each time you profile a Java
process. This workbench process object is a logical representation of a Java process
rather than a system process. It is identified both by name and a process ID
number (PID).
Follow these steps to profile an application using the WebSphere test environment:
- Associate the project that you want to profile with a server and its configuration.
For information on how to do this refer to the documentation for the WebSphere test environment.
- Ensure that the server is running.
- Click the list button (arrow to the right) of the Profile button
(on the main toolbar), and from the menu list, select Attach > Java
Process.
Note: You selected the local process; not Attach > Remote Process
because the test environment is on your local machine.
The Attach to Java Process wizard opens to the Agent page.
- Use this page to select the agents and their corresponding processes that
you want to attach your Java process to.
Notes:
- Only agents that are active and to which no client is attached are
listed in the Agents list.
- The list includes logging agents only if you selected the Enable
logging check box on the Profiling preferences page (Window >
Preferences > Profiling and Logging). Similarly, the list includes
profiling agents only if you selected the Enable profiling check box
on the Profiling preferences page.
- You can use the Refresh Data button to perform a new query
on the host in order to get all relevant processes that are running at that
point in time. For example, if a process starts running after you opened
the wizard, you can click Refresh Data to refresh the list.
- Click Next. The Destination page opens.
- Specify the project and monitor that are to be used to store data from
this profiling session.
- Click Next. The Profiling Filters page opens. Use it to specify
new profiling filters, or modify the default
profiling filters.
- Click Next. The Profiling Options page opens.
- Here, you can specify time and event profiling options, and whether you
want the profiling data to include execution flow data, and data about the
boundary classes; and if you want instance-level information to be collected.
See the related task Specifying profiling preferences.
- Click Finish.
- If you have completed these steps from any one of the Java, Server, or
Debug perspectives, the Profiling and Logging perspective opens at this point.
- Since you are attaching to the agents, you must manually start monitoring
the agents. Click the Start Monitoring button
from the Profiling Monitor view toolbar.
The agents that are monitored appear in the Profiling Monitor view with the Monitor
symbol:
.
- You can now analyze the collected data using the different profiling views.
- By default, the Profiling and Logging perspective first shows the Class Methods
Statistics view when you double-click the selected agent.
- To populate the view with profiling data that was collected from your
Java process, click the Refresh Views button
,
or select Refresh Views from the context menu of the view.
Tip:
Instead of following the instructions in step 3, you can also
select the host from which you want to launch the process, in the Profiling Monitor
view, and from its pop-up menu, select Attach to Agents. The Attach to Java
Process wizard opens to the Agents page.
Related concepts
Profiling resources
Related tasks
Setting profiling preferences
Specifying profiling filters
Saving profiling resources
Profiling an application in
stand-alone mode
Related reference
Profiling Monitor view
(C) Copyright IBM Corporation 2000, 2005. All Rights
Reserved.