Appboard/old/multiple instances - Revision history

imported>Jason.nicholls: /* Configuring Dual-NIC Deployments */

2014-07-17T16:29:40Z

Configuring Dual-NIC Deployments

← Older revision		Revision as of 16:29, 17 July 2014
Line 41:		Line 41:
	=== Configuring Dual-NIC Deployments ===		=== Configuring Dual-NIC Deployments ===

	In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. For instructions on this, see [[~~Binding_To_A_Specific_IP~~\|Binding AppBoard/enPortal to a specific IP/Interface]].		In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. For instructions on this, see [[appboard/old/tomcat_binding\|Binding AppBoard/enPortal to a specific IP/Interface]].

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

2014-07-17T11:28:32Z

Port Configuration

← Older revision		Revision as of 11:28, 17 July 2014
Line 23:		Line 23:
	When installing more than one instance of AppBoard on the same server, the most important item to configure is the ports. There are two ports used by each instance, and they must be unique for each system. If you start an AppBoard system, and it tries to use a port that is already in use, you will receive a JVM Bind Error, and the system will not start.		When installing more than one instance of AppBoard on the same server, the most important item to configure is the ports. There are two ports used by each instance, and they must be unique for each system. If you start an AppBoard system, and it tries to use a port that is already in use, you will receive a JVM Bind Error, and the system will not start.

	Refer to the [[~~Runtime_Options~~\|Runtime Options]] page to make changes, specifically the <tt>HTTP_PORT</tt> and <tt>SHUTDOWN_PORT</tt> settings.		Refer to the [[appboard/old/runtime_options\|Runtime Options]] page to make changes, specifically the <tt>HTTP_PORT</tt> and <tt>SHUTDOWN_PORT</tt> settings.


	=== Memory Configuration ===		=== Memory Configuration ===

imported>Jason.nicholls at 05:42, 17 July 2014

2014-07-17T05:42:43Z

← Older revision		Revision as of 05:42, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:Installing Multiple Instances}}
			[[Category:AppBoard old]]
	There are some special cases where you may want to install more than one instance of AppBoard on the same server. This article details some special considerations to make this work properly.		There are some special cases where you may want to install more than one instance of AppBoard on the same server. This article details some special considerations to make this work properly.

imported>Jason.nicholls: moved Installing Multiple Instances to appboard/old/multiple instances

2014-07-17T05:41:52Z

moved Installing Multiple Instances to appboard/old/multiple instances

← Older revision	Revision as of 05:41, 17 July 2014
(No difference)

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

2014-07-17T05:09:57Z

Memory Configuration

← Older revision		Revision as of 05:09, 17 July 2014
Line 29:		Line 29:


	One way to limit the memory footprint of AppBoard is in the Tomcat [[~~Memory_Configuration~~\|memory configuration settings]]. For a dev or demo instance, you can typically lower the Java Virtual Machine (JVM) maximum heap size (-Xmx JVM parameter) to a low setting such as -Xmx512m. without any noticeable change in performance.		One way to limit the memory footprint of AppBoard is in the Tomcat [[appboard/old/memory configuration\|memory configuration settings]]. For a dev or demo instance, you can typically lower the Java Virtual Machine (JVM) maximum heap size (-Xmx JVM parameter) to a low setting such as -Xmx512m. without any noticeable change in performance.


	=== Database ===		=== Database ===

imported>Mike.berman: update for runtime options

2013-06-16T16:01:19Z

update for runtime options

← Older revision		Revision as of 16:01, 16 June 2013
Line 21:		Line 21:
	When installing more than one instance of AppBoard on the same server, the most important item to configure is the ports. There are two ports used by each instance, and they must be unique for each system. If you start an AppBoard system, and it tries to use a port that is already in use, you will receive a JVM Bind Error, and the system will not start.		When installing more than one instance of AppBoard on the same server, the most important item to configure is the ports. There are two ports used by each instance, and they must be unique for each system. If you start an AppBoard system, and it tries to use a port that is already in use, you will receive a JVM Bind Error, and the system will not start.

	~~Perform the following steps~~ to ~~adjust~~ the ~~AppBoard port configuration for each instance on the server:~~		Refer to the [[Runtime_Options\|Runtime Options]] page to make changes, specifically the <tt>HTTP_PORT</tt> and <tt>SHUTDOWN_PORT</tt> settings.


	~~# Open the following file in a text editor:~~ [~~APPBOARD_HOME~~]~~/server/bin/setenv.bat (Windows) or setenv.sh (Unix)~~
	~~# Search for the string "SHUTDOWN_PORT" to locate the configuration of the shutdown port. You should see a line such as the following:~~
	~~#: <tt>set SHUTDOWN_PORT=8005</tt>~~
	~~# Make sure this is set~~ to ~~a unique shutdown port value that is not already in use by another AppBoard instance or other Tomcat application on the same server. Change the port~~, ~~if needed by editing~~ the ~~file setenv-custom.bat (Windows) or setenv-custom.sh (Unix). For example, add:~~
	~~#: (Windows):~~ <tt>~~set SHUTDOWN_PORT=8006~~</tt>
	~~#: (Unix):~~ <tt>SHUTDOWN_PORT~~=8006~~</tt>
	~~# Search for "HTTP_PORT" to locate the configuration of the main Tomcat startup port. You should see a line such as the following:~~
	~~#: <tt>set HTTP_PORT=8080</tt>~~
	# Notice the port setting in the above example. Make sure this is set to a unique startup port value that is not already in use by another AppBoard instance or other Tomcat application on the same server. Change the port, if needed, by editing the file setenv-custom.bat (Windows) or setenv-custom.sh (Unix). For example, add:
	~~#: (Windows): <tt>set HTTP_PORT=8081</tt>~~
	~~#: (Unix): <tt>HTTP_PORT=8081</tt>~~


	{{Note\|The redirectPort is only used when SSL is enabled, to re-direct non-SSL requests to SSL. You can change this to a unique value also, to ensure that there will not be a conflict. However, unlike the shutdown and startup ports, you are able to start multiple instances that have the same redirectPort setting.}}

imported>Mike.berman: fix typo in Uses section

2012-09-04T15:31:04Z

fix typo in Uses section

← Older revision		Revision as of 15:31, 4 September 2012
Line 6:		Line 6:
	The following are some sample cases where you may want to install more than one instance of AppBoard on the same server:		The following are some sample cases where you may want to install more than one instance of AppBoard on the same server:

	* Testing - The test team needs to have multiple versions of the system available so they can validate the functionality and features ~~aainst~~ one another.		* Testing - The test team needs to have multiple versions of the system available so they can validate the functionality and features against one another.
	* Development - A developer is working on multiple AppBoard development projects at the same time.		* Development - A developer is working on multiple AppBoard development projects at the same time.
	* Staging - A production and dev system are both running on the production server. They can be swapped, for example, to make the dev system become the production system after validation is complete and certified.		* Staging - A production and dev system are both running on the production server. They can be swapped, for example, to make the dev system become the production system after validation is complete and certified.

imported>Mike.berman: update link for Dual NIC Deployment

2012-08-24T16:57:13Z

update link for Dual NIC Deployment

← Older revision		Revision as of 16:57, 24 August 2012
Line 57:		Line 57:
	=== Configuring Dual-NIC Deployments ===		=== Configuring Dual-NIC Deployments ===

	In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. For instructions on this, see [[~~Dual_NIC_Deployment~~\|~~Dual NIC Deployment~~]].		In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. For instructions on this, see [[Binding_To_A_Specific_IP\|Binding AppBoard/enPortal to a specific IP/Interface]].

imported>Cmace: includes dual-nic

2012-07-19T16:40:41Z

includes dual-nic

← Older revision		Revision as of 16:40, 19 July 2012
Line 53:		Line 53:

	If your system is configured to access an external database, such as Oracle or MySQL, then care must be taken. If you have two systems running locally that are accessing the same database, unpredictable results may occur. For example, if you add a test User on the dev instance, and this is connected to the same database as the production instance, the test User will also appear in the production instance.		If your system is configured to access an external database, such as Oracle or MySQL, then care must be taken. If you have two systems running locally that are accessing the same database, unpredictable results may occur. For example, if you add a test User on the dev instance, and this is connected to the same database as the production instance, the test User will also appear in the production instance.


			=== Configuring Dual-NIC Deployments ===

			In some cases, you may want to run two AppBoard applications on the same server that bind to different IP addresses. For instructions on this, see [[Dual_NIC_Deployment\|Dual NIC Deployment]].

imported>Mike.berman: edit to add Unix differentiation and new location of config files

2012-06-25T14:54:03Z

edit to add Unix differentiation and new location of config files

← Older revision		Revision as of 14:54, 25 June 2012
Line 24:		Line 24:


	# Open the following file in a text editor: [APPBOARD_HOME]/server/~~conf~~/setenv.bat (Windows) or setenv.sh (Unix)		# Open the following file in a text editor: [APPBOARD_HOME]/server/bin/setenv.bat (Windows) or setenv.sh (Unix)
	# Search for the string "SHUTDOWN_PORT" to locate the configuration of the shutdown port. You should see a line such as the following:		# Search for the string "SHUTDOWN_PORT" to locate the configuration of the shutdown port. You should see a line such as the following:
	#: <tt>set SHUTDOWN_PORT=8005</tt>		#: <tt>set SHUTDOWN_PORT=8005</tt>
	# Make sure this is set to a unique shutdown port value that is not already in use by another AppBoard instance on the same server. Change the port, if needed. For example, ~~change to~~:		# Make sure this is set to a unique shutdown port value that is not already in use by another AppBoard instance or other Tomcat application on the same server. Change the port, if needed by editing the file setenv-custom.bat (Windows) or setenv-custom.sh (Unix). For example, add:
	#: <tt>set SHUTDOWN_PORT=8006</tt>		#: (Windows): <tt>set SHUTDOWN_PORT=8006</tt>
			#: (Unix): <tt>SHUTDOWN_PORT=8006</tt>
	# Search for "HTTP_PORT" to locate the configuration of the main Tomcat startup port. You should see a line such as the following:		# Search for "HTTP_PORT" to locate the configuration of the main Tomcat startup port. You should see a line such as the following:
	#: <tt>set HTTP_PORT=8080</tt>		#: <tt>set HTTP_PORT=8080</tt>
	# Notice the port setting in the above example. Make sure this is set to a unique startup port value that is not already in use by another AppBoard instance on the same server. Change the port, if needed. For example, ~~change to~~:		# Notice the port setting in the above example. Make sure this is set to a unique startup port value that is not already in use by another AppBoard instance or other Tomcat application on the same server. Change the port, if needed, by editing the file setenv-custom.bat (Windows) or setenv-custom.sh (Unix). For example, add:
	#: <tt>set HTTP_PORT=8081</tt>		#: (Windows): <tt>set HTTP_PORT=8081</tt>
			#: (Unix): <tt>HTTP_PORT=8081</tt>