Note
When referring to file and directory locations in this document, <install-home> is the directory where the Agent Controller package was unzipped.
You can reduce the system resources used by the Agent Controller if you know it will not be connected to by client applications that require old API's. Removing this backwards compatibility support results in fewer communication ports and less memory used by the Agent Controller.
Note
Since all of the tools included in the TPTP 4.3 release require backwards compatibility, this should only be done when using newly developed client applications. See "Backwards Compatibility in the Agent Controller" for more information.
To eliminate the backwards compatibility support you simply need to remove the special transport layers defined for that purpose from the serviceconfig.xml file. The easiest way to do that is to rename or delete the executable <installdir>/bin/RAServer and then run the SetConfig script from that same bin directory. The absence of the RAServer<.exe> file indicates that SetConfig should generate a serviceconfig.xml file that does not include the backwards compatibility transport layers. When the Agent Controller is next started, it will not load the extra libraries nor open the extra communication ports it uses to support interactions with clients that make requests using the old protocols.
Alternatively, you can manually edit the serviceconfig.xml as follows:
Related tasks
Administering the Agent Controller
Backwards Compatibility in the
Agent Controller
The serviceconfig.xml File
Copyright (C) 2007 Intel Corporation.