Users who do not wish to delete http-listener-1 because they may want to use it later can disable the HTTP listener.
Note: Starting Controller v4.4+, the changes need to be done using the Enterprise Console.
Editing Controller Port Configurations
<network-listener port="8090" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>
<network-listener port="8090" enabled="false" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>\
Note: The port number 8090 is used for representation purposes. Actual port for http-listener-1 might differ if a different port is selected during installation.
Hello, is this article still relevant for 4.5 Controller Installations using Enterprise Console? I see Enterprise Console has a set of configuration settings available in the UI. Can the same be done through the EC UI?
What if we implement the above changes on the domain.xml? Does the EC UI overwrite those changes if any change was made later on through the UI?
You can modify connection settings through the Enterprise Console UI. The Enterprise Console will automatically update all occurrences in the controller for you. You do not need to manually update all the files and manage the sequence to restart services.
You can also edit the ports manually by editing configuration files used by the application server for the Controller domain. Updating the ports manually, however, will cause the Enterprise Console to have no visibility into the updates and cause health check errors.