Appboard/old/tomcat binding - Revision history

imported>Jason.nicholls at 16:29, 17 July 2014

2014-07-17T16:29:12Z

← Older revision		Revision as of 16:29, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:Binding to a Specific IP}}
			[[Category:AppBoard old]]
	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.		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.

imported>Jason.nicholls: moved Binding To A Specific IP to appboard/old/tomcat binding

2014-07-17T16:28:41Z

moved Binding To A Specific IP to appboard/old/tomcat binding

← Older revision	Revision as of 16:28, 17 July 2014
(No difference)

imported>Jason.nicholls: /* Configuration Steps */

2014-07-17T11:29:45Z

Configuration Steps

← Older revision		Revision as of 11:29, 17 July 2014
Line 21:		Line 21:

	# Shutdown the AppBoard Server.		# Shutdown the AppBoard Server.
	# Modify the <tt>HTTP_ADDRESS</tt> setting to the IP address you want AppBoard/enPortal to bind to. Also modify the <tt>SHUTDOWN_PORT</tt> if you will have multiple copies of AppBoard/enPortal running on this system to avoid a port conflict. Refer to the [[~~Runtime_Options~~\|Runtime Options]] page for more information.		# Modify the <tt>HTTP_ADDRESS</tt> setting to the IP address you want AppBoard/enPortal to bind to. Also modify the <tt>SHUTDOWN_PORT</tt> if you will have multiple copies of AppBoard/enPortal running on this system to avoid a port conflict. Refer to the [[appboard/old/runtime_options\|Runtime Options]] page for more information.
	# Restart the server.		# Restart the server.
	# Verify that the system is only responding to requests made to the specified IP address.		# 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.		# In cases where you want multiple AppBoard/enPortal instances restricted to certain IPs, then repeat the process for each instance.

imported>Mike.berman: update for runtime options

2013-06-16T16:03:47Z

update for runtime options

← Older revision		Revision as of 16:03, 16 June 2013
Line 18:		Line 18:


	~~How to configure AppBoard to listen on a single IP address on a Dual NIC system:~~		=== Configuration Steps ===


	# Shutdown the AppBoard Server.		# Shutdown the AppBoard Server.
	# ~~Clone the Appboard server to a secondary instance by copying~~ the <tt>~~[AppBoard_Home]</tt> directory to a second instance.~~		# Modify the <tt>HTTP_ADDRESS</tt> setting to the IP address you want AppBoard/enPortal to bind to. Also modify the <tt>SHUTDOWN_PORT</tt> if you will have multiple copies of AppBoard/enPortal running on this system to avoid a port conflict. Refer to the [[Runtime_Options\|Runtime Options]] page for more information.
	~~# Edit one of the following files (this step is only required on one of the instances).~~
	~~#* (UNIX)~~
	~~#*# Edit the shell script: <tt>[AppBoard_Home]/server/bin/setenv-custom.sh</tt>~~
	~~#*# Uncomment the line <tt>rem SHUTDOWN_PORT=8006</tt> by removing the ‘rem’ and changing the port to 8008 or another unused port.~~
	~~#*# Uncomment the line <tt>rem set~~ HTTP_ADDRESS~~=x.x.x.x~~</tt> ~~by removing the ‘rem’ and changing the x.x.x.x~~ to the ip address ~~that~~ you want AppBoard to bind to.
	~~#*# Save the file.~~
	~~#* (Windows)~~
	~~#*# Edit~~ the ~~batch script:~~ <tt>~~[AppBoard_Home]\server\bin\setenv-custom.bat~~</tt>
	~~#*# Uncomment the line <tt>rem set SHUTDOWN_PORT=8006<~~/~~tt> by removing the ‘rem’ and changing the port~~ to ~~8008 or another unused~~ port.
	~~#*# Uncomment the line <tt>rem set HTTP_ADDRESS=x.x.x.x</tt> by removing the ‘rem’ and changing the x.x.x.x~~ to the ~~ip address that you want AppBoard to bind to.~~
	~~#*# Save the file~~.
	# Restart the server.		# Restart the server.
	# Verify that the system is only responding to requests made to the specified IP address.		# Verify that the system is only responding to requests made to the specified IP address.
	# ~~Repeat~~ for ~~the other server~~.		# In cases where you want multiple AppBoard/enPortal instances restricted to certain IPs, then repeat the process for each instance.

imported>Mike.berman: (created page (was Dual NIC Deployment))

2012-08-24T16:57:50Z

(created page (was Dual NIC Deployment))

New page

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.

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

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