Appboard/old/tomcat binding
In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. Or you may want the system to be accessible on one IP address, but not any other. For example, you may have a dual NIC deployment on the same server, consisting of a public AppBoard instance accessible on one IP address and a secure AppBoard instance on another private IP address. This article details how to configure this type of IP binding.
Configuring Binding To A Specific IP
This section outlines how to configure an AppBoard instance to bind to a specific IP Address, and how to change the shutdown port, so you can run multiple instances on the same port but different IP Addresses.
By default, AppBoard is configured to listen on IP address 0.0.0.0. This means that any IP address that maps to the server running AppBoard will be allowed to access the application (as long as the correct port number is used). For example, if you try to access AppBoard from a browser on the server itself, with the default settings, you may be able to use any of the following URLs:
- http://127.0.0.1:8080
- http://localhost:8080
- http://192.168.21.138:8080 (assuming this is the IP address of AppBoard server)
- etc.
However, if you were to configure the HTTP_ADDRESS of AppBoard to be 192.168.21.138, then it would no longer be accessible on 127.0.0.1, or any other IP address. Only 192.168.21.138 would be supported.
Configuration Steps
- Shutdown the AppBoard Server.
- Modify the HTTP_ADDRESS setting to the IP address you want AppBoard/enPortal to bind to. Also modify the SHUTDOWN_PORT if you will have multiple copies of AppBoard/enPortal running on this system to avoid a port conflict. Refer to the Runtime Options page for more information.
- Restart the server.
- Verify that the system is only responding to requests made to the specified IP address.
- In cases where you want multiple AppBoard/enPortal instances restricted to certain IPs, then repeat the process for each instance.
