How do I change the Controller HTTP port, depending on whether or not it is discovered in the Enterprise Console?
This article includes the different steps for changing a Controller’s port, whether it is discovered in the Enterprise Console, or it isn’t.
In this article...
How do I change the Controller’s port when not discovered in the Enterprise Console?
To change the Controller from default port 8090 to an open HTTP port, make the following changes to file <controller>\appserver\glassfish\domains\domain1\config\domain.xml.
- Search for the following:
| <network-listener port="8090" protocol="http-listener-1" enabled="true" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener> |
- Edit it, replacing the former port=”8090” with the new port details, as shown below, where <new-port> contains the new port details.
<network-listener port="<new-port>" protocol="http-listener-1" enabled="true" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>
- In the same file— <controller>\appserver\glassfish\domains\domain1\config\domain.xml
—replace all occurrences of 8090 with the new port number.
- Restart the Controller app server using the relevant commands, from the steps below:
Windows
|
<Controller_Home>/bin/controller.bat stop-appserver
<Controller_Home>/bin/controller.bat start-appserver
|
Linux
|
<Controller_Home>/bin/controller.sh stop-appserver
<Controller_Home>/bin/controller.sh start-appserver
|
- After restarting the app server, access the Controller using the new port in the URL.
Example: http://<controller_hostname>:<new_port>/controller
Replace <controller_hostname> with the hostname of the controller and <new_port> with the new port number.
How do I change the Controller’s port when it is discovered in the Enterprise Console?
If the Controller is discovered in the Enterprise Console, change the Controller ports by following the steps outlined in the Documentation: Update platform configurations, "Controller Settings".
