Integrated Agent Controller considerations

• Co-existence with the local Agent Controller (and another local Integrated Agent Controller)
  Either Integrated Agent Controller or the local Agent Controller may run at any given time. They cannot run concurrently. When Integrated Agent Controller is in use, the local Agent Controller may not be started and vice versa.  Furthermore, if Integrated Agent Controller is being used on a workbench,  another Integrated Agent Controller on a second workbench on the same machine cannot be used at the same time.
  
  
• Unsupported function
  Integrated Agent Controller does not support Peer Monitoring functions which are needed in the distributed profiling scenarios.
  
  
• Use filters when profiling
  While it is convenient to use Integrated Agent Controller for profiling and running TPTP tests locally, care must be taken to not overload the workbench with too much data. For example, the profiling agent may send a lot of data that will be buffered on the workbench side. This may add additional memory requirement for the workbench. In general, we recommend that proper filtering be used during profiling to minimize the data transfer and buffer requirement.  We also recommend the use of the standalone Agent Controller when the amount of data being collected is huge.
  
  
• If problems occur when using Integrated Agent Controller
  Check that the local Agent Controller is not running if a problem is reported when using Integrated Agent Controller.
  
  

Related tasks
Working with the Agent Controller
 

Related concepts
Integrated Agent Controller