The essential components of the TPTP data collection framework include the Client (normally the Eclipse workbench), the Agent Controller, and the Agent(s). The Client resides on the Source Machine. The Agent and Agent Controller reside on the Target Machine (which may or may not be the same as the Source Machine). Data is communicated between the Client and the Agent via the Agent Controller through three channels: the Control Channel, the Data Channel, and the Console Channel. The following diagram shows the data collection components and indicates their relationships.
Number | Text | Number | Text |
---|---|---|---|
1 | Source Machine | 6 | Target Machine |
2 | Client (e.g. Eclipse* Workbench) | 7 | Agent Controller |
3 | Control Channel | 8 | Agent |
4 | Data Channel | 9 | Application |
5 | Console Channel | 10 | To or From Additional Agents |
The three components of the TPTP data collection framework are inter-related. Data cannot be collected and visualized without the involvement of all three components.
The following relationships exist between the data collection components:
The Agent and the Agent Controller reside on the same machine (the target machine). The Client may reside in a different machine (with the Eclipse workbench), or on the same machine as the Agent Controller. In either case, the Client and Agent Controller communicate in the same manner as indicated in the diagram.
The channels indicated in the above diagram are logically separated to represent the kinds of information and the flow direction of that information between the components. The actual connections used between components is not a one-to-one mapping, and it is configurable. The channels are:
standard input
or standard output
or standard error
data flows across this channel.The data collection Client processes and displays data of interest to an end user. The Client is typically the Eclipse workbench, and the tools and services available within Eclipse are used to display the collected data.
The Client must attach to an Agent in order to begin receiving data. The Client can attach to an Agent that is already running, or it can launch an Agent using the Agent Controller. Once the Agent is activated, all Client or Agent communications happen via the Agent Controller.
An Agent is tightly coupled with the Agent Controller. It can be launched by the Agent Controller, by the Client, or manually. When launched, the Agent opens a known communication path and tries to register itself with the Agent Controller. Once registered, the Agent Controller manages communication between a Client and the Agent. The Agent typically initializes itself and then waits for control messages (commands).
All Agents respond to a small set of common control messages plus a set of additional control messages as defined by the individual Agent. For example, Agents that collect data wait to begin collecting and transferring data until after the Client sends the appropriate commands to the Agent. The Agent defines how the data gets sent across the channel. Some data might be a continuous stream that continues until the Client sends a "request to terminate". Other data might be sent in segments, on demand from the Client.
The Agent Controller provides a set of services that help the Client and Agent to work together. The following services are available from the Agent Controller:
Related tasks
Agent Controller Overview
Administering the Agent Controller
Copyright (C) 2005, 2010 Intel Corporation and others.