Server IP binding is an advanced system task that is generally reserved for network managers. Do not change values on this page without the assistance of the appropriate administrators.
By default, all of the trading engine internal socket servers (for example, HTTP, SMTP) are bound to all network interfaces of the computer used as the application server. This allows clients to connect to the servers on any of the IP addresses associated with the network interfaces in a given machine. For example, if a machine has two network interfaces having IP addresses 10.10.1.1 and 10.10.1.2, the HTTP server for the user interface would be available on both IP addresses at the default port of 6080. The same would apply to the HTTP server for trading (if configured), but at the default port of 4080. Note that all servers also would be available on the loop-back interface, 127.0.0.1, as well (if available). For the majority of users, the default behavior of binding to all available IP addresses is satisfactory.
The other option is to bind only to the IP address of the application server identified by the CYC_NETWORK_NAME property. This property is in the <machine_name>_environment file, in <interchange_install directory>\bin.
To bind only to CYC_NETWORK_NAME, go to the System management page in the user interface and click Configure server IP binding. Select the CYC_NETWORK_NAME option and click Save changes. Restart the server for the change to take effect.
There is a command-line tool in the application’s tools directory named netInfo that you can use to identify the network interfaces on the application server. Note that it may report more than one IP address per network interface, depending on how your network is configured. The tool also reports the value of CYC_NETWORK_NAME. Run the script without parameters from the tools directory.