Appboard/old/tomcat binding

Revision as of 16:57, 24 August 2012 by imported>Mike.berman ((created page (was Dual NIC Deployment)))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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:


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.


How to configure AppBoard to listen on a single IP address on a Dual NIC system:


  1. Shutdown the AppBoard Server.
  2. Clone the Appboard server to a secondary instance by copying the [AppBoard_Home] directory to a second instance.
  3. Edit one of the following files (this step is only required on one of the instances).
    • (UNIX)
      1. Edit the shell script: [AppBoard_Home]/server/bin/setenv-custom.sh
      2. Uncomment the line rem SHUTDOWN_PORT=8006 by removing the ‘rem’ and changing the port to 8008 or another unused port.
      3. Uncomment the line rem set HTTP_ADDRESS=x.x.x.x by removing the ‘rem’ and changing the x.x.x.x to the ip address that you want AppBoard to bind to.
      4. Save the file.
    • (Windows)
      1. Edit the batch script: [AppBoard_Home]\server\bin\setenv-custom.bat
      2. Uncomment the line rem set SHUTDOWN_PORT=8006 by removing the ‘rem’ and changing the port to 8008 or another unused port.
      3. Uncomment the line rem set HTTP_ADDRESS=x.x.x.x by removing the ‘rem’ and changing the x.x.x.x to the ip address that you want AppBoard to bind to.
      4. Save the file.
  4. Restart the server.
  5. Verify that the system is only responding to requests made to the specified IP address.
  6. Repeat for the other server.