Profiling Monitor view
A project, complete with all the other resources required for
profiling,
is shown in the Profiling Monitor view whenever you launch either a
local
Java process or a remote one.
The Profiling Monitor view displays the profiling resources that get
created during a profiling session. These resources are organized in a
tree with the project being the root:
-
Projects and folders

-
Monitors

-
Hosts

-
Processes

-
Agents (profiling and logging)

It is possible to keep profiling resources in any type of project or
folder. Except for the project, the profiling objects are not directly
related to a workbench resource.
Once you have profiled your application, you can open various
Profiling
and Logging views from any of the profiling resources in the Profiling
Monitor view as indicated in the illustration. The hierarchical level
of
the resource in this view determines the type of information that is
displayed
in these views. For example, opening the Profiling and Logging views
from
the monitor rather than from an agent gives you a global, aggregated
view
of all the profiling data contained under this monitor. Views opened
from
the monitor level enable you to see the data from multiple hosts,
processes
and agents.
Whenever you launch or attach to a Java process, a logical
representation
of the Java process is created in the Profiling Monitor view. This
representation,
the process object, is identified both by name and an ID number (PID)
that
appears in the view along with the associated agents. The agents
collect
profiling data from your Java process, and this data can be analyzed.
The Profiling Monitor view is launched when you select the Profiling
and Logging perspective. Use this view to administer your
profiling
activity.
Controls
There are three groups of controls in the Profiling Monitor view:
-
The menu to
select objects
-
The process controls
-
The objects controls
Menu to select
objects
Use this menu to select the objects that appear in the view.
Notice
the objects appearing in the view, organized according to their
position
in the hierarchy.
Process controls
These frequently-used controls of the profiling process are available
from
near the top of the Profiling Monitor view.

- Start monitoring a paused process

- Pause the monitoring of a process

- Run garbage collection

- Collect object references (if available)

- Refresh the Profiling Monitor view
Objects controls
These controls are obtained by selecting an object, right-clicking,
then
selecting the action. The choices of action available vary depending on
what type of object is chosen (for example, only agents and processes
can
be terminated).
Attach to, or detach from, an agent
See details about Launching or
attaching
a Java process.
Reset Data 
Select this action to set a new base line for the profiling data. After
running this action, a new trace agent will be created under the
existing process item and profiling data will be collected by this
agent.
Run Garbage Collection
Determine the memory that the process is no longer using, and recycle
it
for other use. This control is the same as:
Collect Object References
If available, depict references to or from a set of objects. This is
useful
for locating objects that still have references to them, which might
explain
why garbage collection cannot occur for those objects. This
control
is the same as:
Launch or attach

See details about Launching or
attaching
a Java process.
Terminate 
You can terminate a process that is either running locally on your
machine
or one that is running on a remote host. Right click the process,
then select Terminate.
The process is unconditionally terminated. There is no way to
reverse
this action. It is better to terminate the process in the way the Java
program would normally expect it to be terminated, if such a way
exists.
Relaunch 
After a process has terminated you can re-launch it with the same same
conditions as previously. Right click the process, then select Relaunch.
A process with a new ID and associated agents is created, and appears
in
the view.
Open With

Open the selected object into the selected view.
Refresh Views

Refresh all views that are open.
Save

See details about Saving profiling
resources.
To recover such saved resources, see Importing
profiling resources.
Reload from Local

Load the saved information about the selected object, from the local
file
system. Use this to recreate the data collected during a previous
profiling
session.
Refresh

Refresh the Profiling Monitor view.
Delete

To delete a monitor, host, process object, or agent, right click it,
then
select Delete. Select whether to delete from the view
only
or from the file system. The selected item is deleted with all
the
objects below it in the hierarchy.
Properties

To view the properties of a specific monitor, host, process, or agent,
right click it, then select Properties. A preferences
page
appears.
A completed process, a terminated agent, and the associated monitor
cannot be modified because there would be no point in doing
so.
Otherwise, when you modify the information on this page, it takes
effect
the next time the associated package or host is used.
Many of the properties that you see here are also found in Windows
>
Preferences. Whichever was the more recent property setting takes
precedence.
Import and Export

See details about Importing or
Exporting
profiling resources.
Add JET Nature 
This feature is inherited from the base Eclipse system. It
creates
a templates\.jetproperties XML file:
<?xml version="1.0" encoding="UTF-8"?>
<jet-settings>
<template-container>templates</template-container>
<source-container></source-container>
</jet-settings>
Team > Apply Patch

This feature is related to CVS use and is inherited from the base
Eclipse
system. See Working with patches.
Team > Share Project 
This feature is related to CVS use and is inherited from the base
Eclipse
system. See Sharing a new project using CVS.
Compare With > Each Other 

This feature is related to CVS use and is inherited from the base
Eclipse
system. See Comparing Resources.
Replace With 

This feature is related to CVS use and is inherited from the base
Eclipse
system. Replacing resources in the Workbench.
Restore from local history 

This feature is related to CVS use and is inherited from the base
Eclipse
system. Restoring deleted resources from local history
Related concepts
Overview
of the Profiling Tool
Related tasks
Profiling an application
Related references
Profiling console view
(C) Copyright IBM Corporation 2000, 2004. All
Rights
Reserved.