Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » extending TPTP UI
extending TPTP UI [message #82322] Fri, 01 September 2006 15:24 Go to next message
Vsevolod Sandomirskiy is currently offline Vsevolod SandomirskiyFriend
Messages: 21
Registered: July 2009
Junior Member
I've read a very informative article at
http://www.eclipse.org/tptp/platform/documents/tutorials/dat acollection/launch-extensions/extending-launch-configuration .html
but still have few questions. I'd appreciate if you could help.

Basically, we have a custom data collector with some custom analysis
types. We have an agent, and we want to attach to this agent. Agent
sends data very similar to TPTP trace, so reusing TPTP views would be
nice. While TPTP provides many extension points and all the
functionality is there, it's not clear how to reach our goal.

> 2.2 Implementing a Launch Delegate
What does 'mutual' means? Can I use
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate to
attach to an agent? Should I use IDataCollectorAgentLauncher? Docs say:

/**
* Prepares the model entity representing the agent that will be a
result of the
* launch.
*
* @param trcProcessProxy The model entity representing a process.
* @return The primary launcher doesn't use the returned value. In
fact the
* returned value can be null if contributors choose not to use the
execution
* framework.
*/
public Agent createAgent(TRCProcessProxy trcProcessProxy) throws
CoreException;

What exactly means "prepare"? Does it have to create TRCAgent, etc?

Profiling Monitor on the figure 2.7 shows a node and an agent. I'd
expect to see the data collector and the analysis type (selected in the
launch configuration) underneath the agent. Or it doesn't work that way?
How do an analysis type and TRCAgent get associated?

I've read 'Working with the Application Context Extension sample' from
the online help. Is the 'Application Context' associated with an agent,
or a data collector, or an analysis type? How to activate it? How to
make, say, Execution Statistics view use it?

Thanks.

Vsevolod
Re: extending TPTP UI [message #82351 is a reply to message #82322] Fri, 01 September 2006 18:30 Go to previous message
No real name is currently offline No real nameFriend
Messages: 404
Registered: July 2009
Senior Member
Hi Vsevolod,

> What does 'mutual' means? Can I use
> org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate to
> attach to an agent? Should I use IDataCollectorAgentLauncher? Docs say:


A mutual launcher is a launch delegate that can co-exist with other launch
delegates. You can think of each data collector as a separate launcher.
Multiple mutual launchers will be able to be invoked simultaneously without
one interrupting the operation of the other launchers.
The PrimaryLaunchDelegate is the delegate that should be associated with
your launch type. It's this launch delegate that will do the lookup of the
data collector launch delegates (aka secondary launch delegates) and will
invoke them using the decision tree shown here:
http://www.eclipse.org/tptp/platform/documents/tutorials/dat acollection/launch-extensions/extending-launch-configuration .html#2.2

The type of a launch delegate interface that you use is really dependent on
what your data collector needs to launch. I would encourage you to view the
source under org.eclipse.hyades.trace.ui. Look under the following package:
org.eclipse.tptp.trace.ui.internal.launcher.deleg.applicatio n
The JVMPI launch delegate names all have "PI" as their prefix. There is
also a set of "Agent Discoverer" launch delegates that have the prefix
"AgentDiscoverer".

> What exactly means "prepare"? Does it have to create TRCAgent, etc?

The internal comment is misleading. In TPTP, we have a set of interfaces
defined to represent an agent, process, node, etc... in the execution
framework. We also have interfaces defined in the hierarchy model to
represent a monitor, node, process, and agent (these are the entities you
see in the profiling monitor view). "Agent" is the interface defined in the
execution framework that is mapped to "TRCAgentProxy" in the hierarchy
model. What createAgent(...) is expected to return is an implementation of
the "Agent" interface in the execution framework.

> Profiling Monitor on the figure 2.7 shows a node and an agent. I'd expect
> to see the data collector and the analysis type (selected in the launch
> configuration) underneath the agent. Or it doesn't work that way?


Figure 2.7 shows the process and the agent. The agent is the data collector
that you selected under the monitor tab and the analysis type should appear
underneath the agent. If you use TPTP 4.2.1 or later, you will see the
analysis type appear under the agent.

> How do an analysis type and TRCAgent get associated?

The primary launch delegate will associate an analysis type to the agent
that is created as a result of the launch.

> I've read 'Working with the Application Context Extension sample' from the
> online help. Is the 'Application Context' associated with an agent, or a
> data collector, or an analysis type? How to activate it? How to make, say,
> Execution Statistics view use it?

This set of extension points are different than the launch configuration
extension points. These don't have any associations with data collectors or
analysis types. I believe the sample illustrates how they can be used to
change the context of the stat views. If you have any specific questions,
then post them as a separate thread to trigger the attention of the
devleoper who has implemented them.

"Vsevolod Sandomirskiy" <vss@ocsystems.com> wrote in message
news:ed9jqp$2d2$1@utils.eclipse.org...
> I've read a very informative article at
> http://www.eclipse.org/tptp/platform/documents/tutorials/dat acollection/launch-extensions/extending-launch-configuration .html
> but still have few questions. I'd appreciate if you could help.
>
> Basically, we have a custom data collector with some custom analysis
> types. We have an agent, and we want to attach to this agent. Agent sends
> data very similar to TPTP trace, so reusing TPTP views would be nice.
> While TPTP provides many extension points and all the functionality is
> there, it's not clear how to reach our goal.
>
> > 2.2 Implementing a Launch Delegate
> What does 'mutual' means? Can I use
> org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate to
> attach to an agent? Should I use IDataCollectorAgentLauncher? Docs say:
>
> /**
> * Prepares the model entity representing the agent that will be a
> result of the
> * launch.
> *
> * @param trcProcessProxy The model entity representing a process.
> * @return The primary launcher doesn't use the returned value. In
> fact the
> * returned value can be null if contributors choose not to use the
> execution
> * framework.
> */
> public Agent createAgent(TRCProcessProxy trcProcessProxy) throws
> CoreException;
>
> What exactly means "prepare"? Does it have to create TRCAgent, etc?
>
> Profiling Monitor on the figure 2.7 shows a node and an agent. I'd expect
> to see the data collector and the analysis type (selected in the launch
> configuration) underneath the agent. Or it doesn't work that way? How do
> an analysis type and TRCAgent get associated?
>
> I've read 'Working with the Application Context Extension sample' from the
> online help. Is the 'Application Context' associated with an agent, or a
> data collector, or an analysis type? How to activate it? How to make, say,
> Execution Statistics view use it?
>
> Thanks.
>
> Vsevolod
Previous Topic:Test TPTP menu options not available
Next Topic:Error finding piAgent
Goto Forum:
  


Current Time: Thu Mar 28 19:32:55 GMT 2024

Powered by FUDForum. Page generated in 0.01501 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top