Configuring external communications

For the Agent Controller to be visible to other hosts, it must open a device where it can be connected to remotely. This connection is established using a single port on the deployment host. By default, this port is number 10002 and it is specified in the configuration file, serviceconfig.xml. However, if the security was enabled during the installation of the Agent Controller, another port should be specified in the configuration file as the secure port. This port will only be opened for secure connections and is only available when the security for the Agent Controller has been enabled.

Specifying different ports for the Agent Controller

You can indicate that a different port is to be used by the Agent Controller by modifying the port attribute of the AgentControllerConfiguration element within the configuration file.

Follow these steps:

Locate the serviceconfig.xml configuration file. See the related task.
Open it in an editor, and search for the following XML fragment:
<AgentControllerConfiguration version="5.0.0" activeConfiguration="default" loggingLevel="WARNING" loggingDetail="LOW" port="10002" securePort="10003">
Change the value of the port attribute to the port number that you want the Agent Controller to use.

Note:

If the port number is changed by the administrator, then the port number will also need to be reflected in the Profiling and Logging preferences page of the workbench or the Agent Controller will appear not to be running on the deployment host. See the related task.
If the Agent Controller is to be contacted through a firewall, the system administrator must ensure that both of the configured ports are reachable by the test client.
Specifying the secureport in the configuration file indicates that you enabled the security during the Agent Controller installation process.