Hello Ali,
That sample is exactly what I was looking for.
In fact I took your original CustomDelegate example, modified it
to use IDataCollectorAgentLauncher and almost achieved the
same result except I could not get the control provider listener
working (and everything was 3 times longer).
Thank you very much!
Henk Aling
Sr Member of Technical Staff
201 Moffett Park Drive
Sunnyvale, CA 94089
Tel: (408) 542-1828
www.windriver.com
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ali Mehregani
Sent: Tuesday, April 10, 2007 9:32 AM
To: TPTP Tracing and Profiling Tools Project developer
discussions
Subject: Re: [tptp-tracing-profiling-tools-dev] Launch
frameworkforprocess-less data collectors
Hi Henk,
> I read the Word attachment related to enhancement 139085
> where you propose to remove the "Monitor" tab in favor of
> the "Agents" tab. Is that only for the "Attach" launch
> configuration, or for all?
Yes, the current plan is to only remove the monitor tab for the
attach launch configuration type.
> Our tools typically launch an agent (not a process) and
> attach to it.
The secondary launch delegates are not required to launch a
process. There is a notion of an "agent launcher" (see
IDataCollectorAgentLauncher). I have baked up a sample to illustrate
how you can have your agent appear in the profile monitor view without
having a process launched. See the attached zip file. The plug-in was
developed using TPTP-4.4.0-200703260100.
> Is there
> a document that describes the relationships between agents,
> processes, data collectors, analysis types and launch items?
At this point the document that you have already reviewed is the
only material available.
> Is there a way to attach directly to an agent while avoiding
> using the Agent Controller?
Yes, you can avoid the agent controller. The launch
configuration framework is only tied in with the execution framework
interfaces ( i.e. Node, Process, Agent, etc...). You'll need to provide
your own implementation of these interfaces if you intend to provide a
custom back-end data collector/controller.
> Can this also be done using the "Attach" scenario as you
> suggested (the Java-attach case uses the AC)?
Yep. The same is true for the attach scenario.
I hope the sample will help,
Ali Mehregani
On 4/9/07, Aling, Henk <[EMAIL PROTECTED]> wrote:
Hello Ali,
I read the Word attachment related to enhancement 139085
where you propose to remove the "Monitor" tab in favor
of
the "Agents" tab. Is that only for the "Attach" launch
configuration, or for all?
Our tools typically launch an agent (not a process) and
attach to it. We are also trying to define our own
common data
format for our analysis tools. The concept of data
collectors,
analysis types and the associated profiling UI seemed to
fit
nicely.
It becomes confusing when there are agents that don't
have a data collector, like the logging agents. Is there
a document that describes the relationships between
agents,
processes, data collectors, analysis types and launch
items?
I found the launch entities diagram helpful, some
additional
explanation would be even more helpful.
Is there a way to attach directly to an agent while
avoiding
using the Agent Controller? I was hoping that the
IDataCollectorAgentLauncher interface would let us do
that.
Can this also be done using the "Attach" scenario as you
suggested (the Java-attach case uses the AC)?
Thanks again, and also for improving the Attach scenario
Henk Aling
Sr Member of Technical Staff
201 Moffett Park Drive
Sunnyvale, CA 94089
Tel: (408) 542-1828
www.windriver.com
________________________________
From:
[EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED] On Behalf
Of Ali Mehregani
Sent: Monday, April 09, 2007 7:24 AM
To: TPTP Tracing and Profiling Tools Project
developer
discussions
Subject: Re: [tptp-tracing-profiling-tools-dev]
Launch framework
forprocess-less data collectors
Hi Henk,
There is actually a process that is launched by
the Agent
Discoverer. The process that is launched is
periodically queried to
determine if there are any agents associated with it.
As soon as an
agent is discovered, it is automatically attached and
monitored.
I believe your use case is different. You
intend to use the
launch configuration to only discover an agent that is
already running
on a particular host. Although this is currently
possible (using the
Attach - Java Process launch configuration type), the
use case is a bit
obscure and it is being redone in 4.4. Please see the
following
enhancement:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=139085
Thanks,
Ali Mehregani
On 4/9/07, Aling, Henk
<[EMAIL PROTECTED]> wrote:
My goal is to use the launch framework
for
configurations
that attach to agents without launching
a process. I
started
looking at The Agent Discoverer as a
sufficiently close
example.
Unfortunately I got confused by the
logic that is
executed for
this case (I use the "Java Application"
launch
configuration):
The confusing thing is that, even though
the Agent
Discoverer
is really an agent object, in this
particular case the
agent
returned to the primary launch delegate
must be null.
Then,
even though no process is associated
with it, a dummy
process
of class CustomProcess must be created
to circumvent
some
problem with the RAC. Then later a dummy
agent of class
DummyAgent is created to simulate an
active event, in a
rather obscure place/logic path.
What I would expect in this case is just
the opposite,
namely that a non-null agent is returned
to the primary
launch delegate, and that the logic of
how to launch a
process-less data collector is
implemented in the
primary
launch delegate itself, without a need
for a dummy agent
and a dummy process.
I tried modifying the CustomDelegate
example documented
under "Registering a Custom Data
Collection Mechanism
with
TPTP's Launch Configuration Framework "
by implementing
IDataCollectorAgentLauncher instead of
subclassing off
AbstractProcessLauncher but then no tree
node
representing
an agent shows up in the profile
monitor.
Thanks in advance for any advice,
Henk Aling
Wind River
_______________________________________________
tptp-tracing-profiling-tools-dev mailing
list
tptp-tracing-profiling-tools-dev@eclipse.org
<mailto: tptp-tracing-profiling-tools-dev@eclipse.org
<mailto:tptp-tracing-profiling-tools-dev@eclipse.org> >
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-de
v
--
Ali Mehregani
Test & Performance Tools Platform
http://www.eclipse.org/tptp
_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-de
v
--
Ali Mehregani
Test & Performance Tools Platform
http://www.eclipse.org/tptp
_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
