Configure the Agent's Data Channel

In some scenarios, it may be necessary to provide some buffering between the agent and the Agent Controller. Buffering is done by using a data channel between the agent and the Agent Controller. Data channels are desirable in situations where agent performance is highly important. Without a buffer, it is possible that the agent may become blocked when performing output as the test client may not be able to process the output as quickly as required.

The data channel is configured with the <Agent> element in the configuration file of the plug-in containing the agent. For example, the data channel for the Java Profiling Agent is configured by changing its <Agent> element in plugins/org.eclipse.tptp.platform.collection.framework_<version>/config/pluginconfig.xml.

To modify the <Agent> element in the configuration file:

  1. Locate the configuration file containing the element to be modified. It will either be the serviceconfig.xml file or the pluginconfig.xml file for the plug-in containing the agent. See the related task.

  2. Open it in an editor, and search for the <Agent> element.
  3. Modify the value of the dataChannelSize attribute.

    For example, on Windows to specify that a data channel of 64 megabytes is to be used when the Java Profiling Agent is actively profiling, change the value of the dataChannelSize attribute to 64 MB. 

    <Agent name="Java Profiling Agent" type="Profiler" 
      dataChannelSize="64MB"> 
</Agent>    

      

    To allow the Agent Controller to communicate with a large number of agents simultaneously, the IPCSHMNSEGS parameter in the MVS BPXPRMxx parmlib member must be set to an appropriate value. The IPCSHMNSEGS parameter specifies the maximum number of attached shared memory segments or data channels for each address space. The default value is 10. A value of 50 would enable 50 agents to communicate with the Agent Controller simultaneously.

Related tasks
Locating the configuration files
Administering the Agent Controller
 

Copyright (C) 2006 Intel Corporation.


Error 404 - Not Found

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.