Appboard/2.4/admin/windows installation - Revision history

imported>Jason.nicholls: /* Installation Tasks */

2014-07-18T09:43:27Z

Installation Tasks

← Older revision		Revision as of 09:43, 18 July 2014
Line 22:		Line 22:
	# Save the license file into <tt>[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</tt>		# Save the license file into <tt>[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</tt>
	# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.		# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.
	# [optional] AppBoard comes with a pre-configured H2 database for storing configuration ~~although an~~ external database can be used ~~instead. See~~ the [[appboard/2.4/admin/configuration_database\|Configuration Database]] page for more information.		# [optional] AppBoard comes with a pre-configured H2 database for storing configuration. An external configuration database can also be used, see the [[appboard/2.4/admin/configuration_database\|Configuration Database]] page for more information.
	# Run the Tomcat startup executable in <tt>[INSTALL_HOME]\bin\startup.bat</tt>		# Run the Tomcat startup executable in <tt>[INSTALL_HOME]\bin\startup.bat</tt>
	# Validate the installation		# Validate the installation

imported>Jason.nicholls: /* Installation Tasks */

2014-07-18T09:42:08Z

Installation Tasks

← Older revision		Revision as of 09:42, 18 July 2014
Line 22:		Line 22:
	# Save the license file into <tt>[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</tt>		# Save the license file into <tt>[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</tt>
	# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.		# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.
	# [optional] AppBoard comes with a pre-configured H2 database for storing ~~basic system information, but this functionality~~ can be ~~achieved using other databases if desired~~. ~~To configure AppBoard to use your own database, follow the instructions on~~ the [[~~Database_Configuration~~\|Database ~~Connection Configuration~~]] page.		# [optional] AppBoard comes with a pre-configured H2 database for storing configuration although an external database can be used instead. See the [[appboard/2.4/admin/configuration_database\|Configuration Database]] page for more information.
	# Run the Tomcat startup executable in <tt>[INSTALL_HOME]\bin\startup.bat</tt>		# Run the Tomcat startup executable in <tt>[INSTALL_HOME]\bin\startup.bat</tt>
	# Validate the installation		# Validate the installation

imported>Jason.nicholls: /* Create an AppBoard Service */

2014-07-14T06:38:45Z

Create an AppBoard Service

← Older revision		Revision as of 06:38, 14 July 2014
Line 60:		Line 60:
	# If successful, the message should be displayed: "The service 'EdgeTomcat' has been removed."		# If successful, the message should be displayed: "The service 'EdgeTomcat' has been removed."

	The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge ~~Web Server~~", then choosing the desired startup type, such as "Automatic".		The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Tomcat", then choosing the desired startup type, such as "Automatic".


			{{Tip\|The command <tt>> tomcat7w.exe //MS//EdgeTomcat</tt> can be used to monitor the service and access the service configuration. Launching this utility will add an ''Edge Tomcat'' icon in the system tray. Right-click the icon to start/stop or further configure the service.}}

	=== Installing Service using JRE ===		=== Installing Service using JRE ===
Line 67:		Line 70:

	When using a JRE it is necessary to ''temporarily'' change the <tt>JAVA_HOME</tt> environment variable to <tt>JRE_HOME</tt>. After successful installation or removal of the service then change the environment variable back to <tt>JAVA_HOME</tt>.		When using a JRE it is necessary to ''temporarily'' change the <tt>JAVA_HOME</tt> environment variable to <tt>JRE_HOME</tt>. After successful installation or removal of the service then change the environment variable back to <tt>JAVA_HOME</tt>.


	== Stopping AppBoard ==		== Stopping AppBoard ==

imported>Jason.nicholls: /* Stopping AppBoard */

2014-07-14T06:37:23Z

Stopping AppBoard

← Older revision		Revision as of 06:37, 14 July 2014
Line 77:		Line 77:
	* Execute the shutdown script that is provided:		* Execute the shutdown script that is provided:
	*: <tt>[INSTALL_HOME]/server/bin/shutdown.bat</tt>		*: <tt>[INSTALL_HOME]/server/bin/shutdown.bat</tt>
	* If running as a service, stop the ~~AppBoard~~ service		* If running as a service, stop the ''Edge Tomcat'' service
	* In the console, enter CTRL-C		* In the console, enter CTRL-C

	{{Warning\|You must properly shut down Tomcat. Do not kill the process by clicking the window "close" button ("X") or by using the Unix kill command (kill -9 <processid>). If the database does not properly shut down, residual lock files have been documented to cause problems when restoring archives.}}		{{Warning\|You must properly shut down Tomcat. Do not kill the process by clicking the window "close" button ("X") or by using the Unix kill command (kill -9 <processid>). If the database does not properly shut down, residual lock files have been documented to cause problems when restoring archives.}}

imported>Jason.nicholls at 06:29, 14 July 2014

2014-07-14T06:29:07Z

← Older revision		Revision as of 06:29, 14 July 2014
Line 61:		Line 61:

	The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".		The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".

			=== Installing Service using JRE ===

			The <tt>service.bat</tt> script is sensitive to whether using a Java Runtime Environment (JRE) versus a full Java Development Kit (JDK).

			When using a JRE it is necessary to ''temporarily'' change the <tt>JAVA_HOME</tt> environment variable to <tt>JRE_HOME</tt>. After successful installation or removal of the service then change the environment variable back to <tt>JAVA_HOME</tt>.


	== Stopping AppBoard ==		== Stopping AppBoard ==

imported>Jason.nicholls: /* Create an AppBoard Service */

2014-07-14T06:26:10Z

Create an AppBoard Service

← Older revision		Revision as of 06:26, 14 July 2014
Line 46:		Line 46:
	{{Note\|		{{Note\|
	* It is '''required''' that you are the administrator when opening a console to install a service.		* It is '''required''' that you are the administrator when opening a console to install a service.
	* A 64-bit JVM must be used when running as a service on 64-bit Windows.}}		* A 64-bit JVM must be used when running as a service on 64-bit Windows.
			* See sub-section if using a JRE vs JDK}}

	The following steps detail how to create a Windows service for automated startup:		The following steps detail how to create a Windows service for automated startup:
Line 60:		Line 61:

	The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".		The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".

	{{Tip\|The command <tt>service.bat test</tt> will launch the service in a console window, with the same options as set for the service. This can allow you to observe startup issues without having to formally run the service.}}

	== Stopping AppBoard ==		== Stopping AppBoard ==

imported>Jason.nicholls at 06:24, 14 July 2014

2014-07-14T06:24:42Z

← Older revision		Revision as of 06:24, 14 July 2014
Line 6:		Line 6:
	== Prerequisites ==		== Prerequisites ==

	# Install ~~the~~ Java ~~Development Kit~~ (1.~~6 or later~~)		# Install Java (refer to the [[appboard/2.4/system_requirements\|System Requirements]] for supported versions)
	# Ensure JAVA_HOME system environment variable is configured		# Ensure <tt>JAVA_HOME</tt> system environment variable is configured
	## Start \| Right-click on Computer and "Properties" \| Advanced System Settings \| Environment Variables		## Start \| Right-click on Computer and "Properties" \| Advanced System Settings \| Environment Variables
	## Under "System Variables", if there is no "JAVA_HOME" variable set, click "New"		## Under "System Variables", if there is no "JAVA_HOME" variable set, click "New"
	## Set "Variable Name" to JAVA_HOME		## Set "Variable Name" to JAVA_HOME
	## Set "Variable Path" to the path to ~~the JDK~~		## Set "Variable Path" to the path to Java install path
	## ~~Example (Windows)~~: <tt>JAVA_HOME = C:\Program Files\Java\~~jdk1.6.0_10~~</tt>		## For example: <tt>JAVA_HOME = C:\Program Files\Java\jre7</tt>
	## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces.		## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces.

	== Installation Tasks ==		== Installation Tasks ==

	To install AppBoard~~/enPortal~~, perform the following steps on the server:		To install AppBoard, perform the following steps on the server:

	# Extract the turnkey installation file to any desired location on the server		# Extract the turnkey installation file to any desired location on the server
	# Save the license file into [INSTALL_HOME]~~/server/~~webapps/enportal/WEB-INF/config/license.properties		# Save the license file into <tt>[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</tt>
	~~# If you are running a 32-bit version of Windows, perform the following additional steps:~~		# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.
	~~## Navigate to [INSTALL_HOME]/server/bin/windows-x86 and copy the 32-bit Tomcat files from the /windows-x86 folder up one level to replace the default 64-bit versions in the /bin folder:~~		# [optional] AppBoard comes with a pre-configured H2 database for storing basic system information, but this functionality can be achieved using other databases if desired. To configure AppBoard to use your own database, follow the instructions on the [[Database_Configuration\|Database Connection Configuration]] page.
	~~### tcnative-1.dll~~		# Run the Tomcat startup executable in <tt>[INSTALL_HOME]\bin\startup.bat</tt>
	~~### tomcat7.exe~~
	~~## It may be necessary to reduce the memory usage, refer to next step and the [[appboard~~/~~2.4/admin/memory_configuration\|Memory Configuration]] page.~~
	# [optional] Ensure the default ports ~~AppBoard/~~enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.
	# Run the Tomcat startup executable in [INSTALL_HOME]/bin/startup.bat
	# Validate the installation		# Validate the installation
	## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard~~/enPortal~~ server: http://localhost:8080		## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard server: http://localhost:8080
	## When prompted, log in with the following default credentials:		## When prompted, log in with the following default credentials (case sensitive):
	### User ID: administrator		### User Name: '''administrator'''
	### Password: administrator		### Password: '''administrator'''
	### Domain: System		### Domain: '''System'''

	== ~~Create an AppBoard/enPortal Service~~ ==		=== 32-bit Systems ===

	After installing AppBoard, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.		By default the turnkey installation is configured with 64-bit executables. For 32-bit systems the following additional tasks must be performed:

			# Navigate to <tt>[INSTALL_HOME]\server\bin\windows-x86</tt> and copy the 32-bit Tomcat files from the <tt>\windows-x86</tt> folder up one level to replace the default 64-bit versions in the <tt>\bin</tt> folder:
			## tcnative-1.dll
			## tomcat7.exe
			# It may be necessary to reduce the memory usage, refer to next step and the [[appboard/2.4/admin/memory_configuration\|Memory Configuration]] page.

			== Create an AppBoard Service ==

			After installing AppBoard, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.

	{{Note\|		{{Note\|
	*It is '''required''' that you are the administrator when opening a console to install a service.		* It is '''required''' that you are the administrator when opening a console to install a service.
	*A 64-bit JVM must be used when running as a service on 64-bit Windows. }}		* A 64-bit JVM must be used when running as a service on 64-bit Windows.}}

	The following steps detail how to create a Windows service for automated startup:		The following steps detail how to create a Windows service for automated startup:

	# ~~Locate~~ the ~~subfolder under~~ <tt>[INSTALL_HOME]\server\bin</tt> ~~that matches your operating system.~~		# Open a ''Command Prompt'' as the administrator (right-click and ''Run as administrator'').
	~~#: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder.~~		# Navigate to <tt>[INSTALL_HOME]\server\bin</tt>
	~~# Copy the two files from this folder over the same files in [INSTALL_HOME]\server\bin~~
	~~# Open the DOS command window~~
	~~# Navigate to [INSTALL_HOME]\server\bin~~
	# Enter the following command to install the Windows service:		# Enter the following command to install the Windows service:
	#: <tt>> service install</tt>		#: <tt>> service install</tt>
Line 56:		Line 58:
	#: <tt>> service remove</tt>		#: <tt>> service remove</tt>
	# If successful, the message should be displayed: "The service 'EdgeTomcat' has been removed."		# If successful, the message should be displayed: "The service 'EdgeTomcat' has been removed."


	The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".		The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".


	{{Tip\|The command <tt>service.bat test</tt> will launch the service in a console window, with the same options as set for the service. This can allow you to observe startup issues without having to formally run the service.}}		{{Tip\|The command <tt>service.bat test</tt> will launch the service in a console window, with the same options as set for the service. This can allow you to observe startup issues without having to formally run the service.}}
Line 65:		Line 65:
	== Stopping AppBoard ==		== Stopping AppBoard ==
	To stop AppBoard, terminate the Tomcat process that is running on the AppBoard server.		To stop AppBoard, terminate the Tomcat process that is running on the AppBoard server.


	{{Warning\|When AppBoard is stopped, all current Users who are logged in to the system will receive an error message the next time they make a request to the AppBoard server. Subsequent Users will not be able to access the login page until AppBoard is re-started. If you are stopping a production instance of AppBoard, it is recommended that you schedule a maintenance window and send advance notification to Users of the system. You can check if there are any active Users logged in to AppBoard before stopping it, by using the [[appboard/2.4/builder/system_administration/manage_sessions\|Session Manager]].}}		{{Warning\|When AppBoard is stopped, all current Users who are logged in to the system will receive an error message the next time they make a request to the AppBoard server. Subsequent Users will not be able to access the login page until AppBoard is re-started. If you are stopping a production instance of AppBoard, it is recommended that you schedule a maintenance window and send advance notification to Users of the system. You can check if there are any active Users logged in to AppBoard before stopping it, by using the [[appboard/2.4/builder/system_administration/manage_sessions\|Session Manager]].}}


	There are several ways to terminate the Tomcat process:		There are several ways to terminate the Tomcat process:
Line 75:		Line 73:
	* If running as a service, stop the AppBoard service		* If running as a service, stop the AppBoard service
	* In the console, enter CTRL-C		* In the console, enter CTRL-C


	{{Warning\|You must properly shut down Tomcat. Do not kill the process by clicking the window "close" button ("X") or by using the Unix kill command (kill -9 <processid>). If the database does not properly shut down, residual lock files have been documented to cause problems when restoring archives.}}		{{Warning\|You must properly shut down Tomcat. Do not kill the process by clicking the window "close" button ("X") or by using the Unix kill command (kill -9 <processid>). If the database does not properly shut down, residual lock files have been documented to cause problems when restoring archives.}}

imported>Jason.nicholls: 1 revision

2014-07-14T06:15:09Z

1 revision

← Older revision	Revision as of 06:15, 14 July 2014
(No difference)

imported>Jason.nicholls: /* Create an AppBoard/enPortal Service */

2014-07-14T06:12:03Z

Create an AppBoard/enPortal Service

imported>Jason.nicholls: /* Create an AppBoard/enPortal Service */

2014-07-14T06:10:55Z

Create an AppBoard/enPortal Service

← Older revision		Revision as of 06:10, 14 July 2014
Line 6:		Line 6:
	== Prerequisites ==		== Prerequisites ==

	# Install Java (~~refer to the [[appboard/2~~.~~4/system_requirements\|System Requirements]] for supported versions~~)		# Install the Java Development Kit (1.6 or later)
	# Ensure ~~<tt>~~JAVA_HOME~~</tt>~~ system environment variable is configured		# Ensure JAVA_HOME system environment variable is configured
	## Start \| Right-click on Computer and "Properties" \| Advanced System Settings \| Environment Variables		## Start \| Right-click on Computer and "Properties" \| Advanced System Settings \| Environment Variables
	## Under "System Variables", if there is no "JAVA_HOME" variable set, click "New"		## Under "System Variables", if there is no "JAVA_HOME" variable set, click "New"
	## Set "Variable Name" to JAVA_HOME		## Set "Variable Name" to JAVA_HOME
	## Set "Variable Path" to the path to ~~Java install path~~		## Set "Variable Path" to the path to the JDK
	## ~~For example~~: <tt>JAVA_HOME = C:\Program Files\Java\~~jre7~~</tt>		## Example (Windows): <tt>JAVA_HOME = C:\Program Files\Java\jdk1.6.0_10</tt>
	## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces.		## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces.

	== Installation Tasks ==		== Installation Tasks ==

	To install AppBoard, perform the following steps on the server:		To install AppBoard/enPortal, perform the following steps on the server:

	# Extract the turnkey installation file to any desired location on the server		# Extract the turnkey installation file to any desired location on the server
	# Save the license file into ~~<tt>~~[INSTALL_HOME]\webapps\enportal\WEB-INF\config\license.properties</~~tt>~~		# Save the license file into [INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/license.properties
	# [optional] Ensure the default ports enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.		# If you are running a 32-bit version of Windows, perform the following additional steps:
	# [optional] AppBoard comes with a pre-configured H2 database for storing basic system information, but this functionality can be achieved using other databases if desired. To configure AppBoard to use your own database, follow the instructions on the [[Database_Configuration\|Database Connection Configuration]] page.		## Navigate to [INSTALL_HOME]/server/bin/windows-x86 and copy the 32-bit Tomcat files from the /windows-x86 folder up one level to replace the default 64-bit versions in the /bin folder:
	# Run the Tomcat startup executable in ~~<tt>~~[INSTALL_HOME]\bin\startup.bat~~</tt>~~		### tcnative-1.dll
			### tomcat7.exe
			## It may be necessary to reduce the memory usage, refer to next step and the [[appboard/2.4/admin/memory_configuration\|Memory Configuration]] page.
			# [optional] Ensure the default ports AppBoard/enPortal use are free or make changes to the listening ports, along with changes to other runtime options. Refer to the [[appboard/2.4/admin/runtime_options\|Runtime Options]] page for further information.
			# Run the Tomcat startup executable in [INSTALL_HOME]/bin/startup.bat
	# Validate the installation		# Validate the installation
	## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard server: http://localhost:8080		## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard/enPortal server: http://localhost:8080
	## When prompted, log in with the following default credentials ~~(case sensitive)~~:		## When prompted, log in with the following default credentials:
	### User ~~Name~~: ~~'''~~administrator~~'''~~		### User ID: administrator
	### Password: ~~'''~~administrator~~'''~~		### Password: administrator
	### Domain: ~~'''~~System~~'''~~		### Domain: System

	~~=== 32-bit Systems ===~~		== Create an AppBoard/enPortal Service ==

	~~By default the turnkey installation is configured with 64-bit executables. For 32-bit systems the following additional tasks must be performed:~~

	# Navigate to <tt>[INSTALL_HOME]\server\bin\windows-x86</tt> and copy the 32-bit Tomcat files from the <tt>\windows-x86</tt> folder up one level to replace the default 64-bit versions in the <tt>\bin</tt> folder:
	~~## tcnative-1.dll~~
	~~## tomcat7.exe~~
	~~# It may be necessary to reduce the memory usage, refer to next step and the [[appboard/2.4/admin/memory_configuration\|Memory Configuration]] page.~~

	== Create an AppBoard Service ==

	After installing AppBoard, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.

			After installing AppBoard/enPortal, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.

	{{Note\|		{{Note\|
	* It is ~~'''~~required~~'''~~ that you are the administrator when opening a console to install a service.		*It is required that you are the administrator when opening a console to install a service.
	* A 64-bit JVM must be used when running as a service on 64-bit Windows.}}		*A 64-bit JVM must be used when running as a service on 64-bit Windows. }}


	The following steps detail how to create a Windows service for automated startup:		The following steps detail how to create a Windows service for automated startup:

	# ~~Open~~ a ~~''Command Prompt'' as~~ the ~~administrator (right~~-~~click and ''Run as administrator'')~~.		# Locate the subfolder under [INSTALL_HOME]\server\bin that matches your operating system.
	# Navigate to ~~<tt>~~[INSTALL_HOME]\server\bin~~</tt>~~		#: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder.
			# Copy the two files from this folder over the same files in [INSTALL_HOME]\server\bin
			# Open the DOS command window
			# Navigate to [INSTALL_HOME]\server\bin
	# Enter the following command to install the Windows service:		# Enter the following command to install the Windows service:
	#: ~~<tt>~~> service install~~</tt>~~		#: > service install
	# If successful, the message should be displayed: "The service 'EdgeWebServer' has been installed."		# If successful, the message should be displayed: "The service 'EdgeWebServer' has been installed."
	# Enter the following command later if you need to remove the Windows service:		# Enter the following command later if you need to remove the Windows service:
	#: ~~<tt>~~> service remove~~</tt>~~		#: > service remove
	# If successful, the message should be displayed: "The service 'EdgeWebServer' has been removed."		# If successful, the message should be displayed: "The service 'EdgeWebServer' has been removed."

← Older revision		Revision as of 06:12, 14 July 2014
Line 37:		Line 37:
	== Create an AppBoard/enPortal Service ==		== Create an AppBoard/enPortal Service ==

	After installing AppBoard~~/enPortal~~, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.		After installing AppBoard, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.

	{{Note\|		{{Note\|
	*It is required that you are the administrator when opening a console to install a service.		*It is '''required''' that you are the administrator when opening a console to install a service.
	*A 64-bit JVM must be used when running as a service on 64-bit Windows. }}		*A 64-bit JVM must be used when running as a service on 64-bit Windows. }}

	The following steps detail how to create a Windows service for automated startup:		The following steps detail how to create a Windows service for automated startup:

	# Locate the subfolder under [INSTALL_HOME]\server\bin that matches your operating system.		# Locate the subfolder under <tt>[INSTALL_HOME]\server\bin</tt> that matches your operating system.
	#: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder.		#: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder.
	# Copy the two files from this folder over the same files in [INSTALL_HOME]\server\bin		# Copy the two files from this folder over the same files in [INSTALL_HOME]\server\bin
Line 51:		Line 51:
	# Navigate to [INSTALL_HOME]\server\bin		# Navigate to [INSTALL_HOME]\server\bin
	# Enter the following command to install the Windows service:		# Enter the following command to install the Windows service:
	#: > service install		#: <tt>> service install</tt>
	# If successful, the message should be displayed: "The service '~~EdgeWebServer~~' has been installed."		# If successful, the message should be displayed: "The service 'EdgeTomcat' has been installed."
	# Enter the following command later if you need to remove the Windows service:		# Enter the following command later if you need to remove the Windows service:
	#: > service remove		#: <tt>> service remove</tt>
	# If successful, the message should be displayed: "The service '~~EdgeWebServer~~' has been removed."		# If successful, the message should be displayed: "The service 'EdgeTomcat' has been removed."