Configuring Agent Controller Transport Layers

It will be necessary to change Transport Layer configuration in order to run multiple, concurrent Agent Controllers.  Each Transport Layer has different items that can be configured.  Generally, these configuration items all relate to how other components can connect to the Agent Controller through the transport layer being configured.  For example, the <Port> element of the TPTP_SOCKET configuration specifies which port a client can use to create a socket connection with that transport layer.

One important reason for changing the default settings of the transport layer configuration elements is to enable multiple instances of the Agent Controller to run on the same machine. If you want to run multiple instances of the Agent Controller, each will need its own serviceconfig.xml file and the transport layers will need to be configured to use unique values for TPTP_SOCKET port, TPTP_NAMEDPIPE pipe name and TPTP_SHAREDMEM shared memory name.

The agent compatibility layer (see Backward Compatibility in the Agent Controller) has no configurable elements and requires a fixed pipe name.  Therefore, it is not possible to run two instance of the Agent Controller with compatibility layers.  If you wish to run a second instance of the Agent Controller on a machine for use with the new protocol, the compatibility transport layers must be removed from the configuration file of the second instance.

For a detailed description of all available configuration option see The serviceconfig.xml File.
 

Argomenti correlati

Backward Compatibility in the Agent Controller
The serviceconfig.xml File

Attivitą correlate
Individuazione dei file di configurazione
Configurazione delle comunicazioni esterne
Gestione di Agent Controller
 

Copyright (C) 2005, 2006 Intel Corporation.