Appboard/2.4/system requirements - Revision history

imported>Jason.nicholls: /* System Requirements */

2014-07-10T11:34:10Z

System Requirements

← Older revision		Revision as of 11:34, 10 July 2014
Line 75:		Line 75:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|JRE ~~1.6+~~ installed on AppBoard server (~~JRE 1.~~7+ recommended)		\|colspan="4"\|Java SE 6 (JRE) installed on AppBoard server (Java SE 7 recommended)
	\|-		\|-
	\|Database **		\|Database **

imported>Jason.nicholls: /* Supported Platforms */

2014-07-10T11:33:14Z

Supported Platforms

← Older revision		Revision as of 11:33, 10 July 2014
Line 10:		Line 10:
	=== Supported Platforms ===		=== Supported Platforms ===

	The following table lists the operating systems supported by AppBoard, but in general AppBoard is supported on any 32- or 64- bit platform that can run Java ~~Runtime Environment (JRE) 1.~~6 or later. AppBoard is also supported on virtualized environments such as VMware.		The following table lists the operating systems supported by AppBoard, but in general AppBoard is supported on any 32- or 64- bit platform that can run Java 6 or later. AppBoard is also supported on virtualized environments such as VMware.

	{\|class="wikitable"		{\|class="wikitable"
Line 23:		Line 23:
	\|Red Hat Enterprise Linux		\|Red Hat Enterprise Linux
	\|Linux		\|Linux
	\|5.7+, 6+ (or equiv for CentOS, Scientific Linux, Oracle Linux, and Amazon Linux)		\|5.7+, 6 (or equiv for CentOS, Scientific Linux, Oracle Linux, and Amazon Linux)
	\|-		\|-
	\|SUSE Linux Enterprise Server		\|SUSE Linux Enterprise Server

imported>Jason.nicholls: /* System Requirements */

2014-06-10T15:57:25Z

System Requirements

← Older revision		Revision as of 15:57, 10 June 2014
Line 87:		Line 87:
	<nowiki>**</nowiki> Regarding database requirements:		<nowiki>**</nowiki> Regarding database requirements:
	:<sup>(1)</sup> By default, AppBoard (and enPortal) includes an in-memory H2 database for configuration data to maintain the mappings between users, roles and proxied content. For most deployment scenarios - excluding High Availability (HA), clustered architectures - Edge recommends using this embedded H2 database. This will simplify the deployment and lower hardware cost as the H2 database will be installed on the same physical or logical server as the AppBoard application.		:<sup>(1)</sup> By default, AppBoard (and enPortal) includes an in-memory H2 database for configuration data to maintain the mappings between users, roles and proxied content. For most deployment scenarios - excluding High Availability (HA), clustered architectures - Edge recommends using this embedded H2 database. This will simplify the deployment and lower hardware cost as the H2 database will be installed on the same physical or logical server as the AppBoard application.
	:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and ~~MySQL~~.		:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, MySQL and DB2.
	:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.		:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.

imported>Jason.nicholls: /* Combined AppBoard & enPortal Deployments */

2014-01-27T19:30:13Z

Combined AppBoard & enPortal Deployments

← Older revision		Revision as of 19:30, 27 January 2014
Line 92:		Line 92:
	==== Combined AppBoard & enPortal Deployments ====		==== Combined AppBoard & enPortal Deployments ====

	~~Foo Bar~~		The AppBoard server includes all enPortal components already and it's a matter of licensing that determines whether the enPortal features can be used.

			In environments where both AppBoard and enPortal capabilities are being used then the overall system requirements may need to be increased over the example deployment scenarios above. A good starting point would be to increase CPU and Memory by 50%.

	=== Default Network Ports ===		=== Default Network Ports ===

imported>Jason.nicholls: /* System Requirements */

2014-01-27T19:20:56Z

System Requirements

← Older revision		Revision as of 19:20, 27 January 2014
Line 89:		Line 89:
	:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.		:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.
	:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.		:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.

			==== Combined AppBoard & enPortal Deployments ====

			Foo Bar

	=== Default Network Ports ===		=== Default Network Ports ===

imported>Jason.nicholls: /* System Requirements */

2014-01-27T19:19:34Z

System Requirements

← Older revision		Revision as of 19:19, 27 January 2014
Line 75:		Line 75:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|JRE 1.6+ installed on ~~enPortal~~ server (JRE 1.7+ recommended)		\|colspan="4"\|JRE 1.6+ installed on AppBoard server (JRE 1.7+ recommended)
	\|-		\|-
	\|Database **		\|Database **
Line 89:		Line 89:
	:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.		:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.
	:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.		:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.


	=== Default Network Ports ===		=== Default Network Ports ===

imported>Jason.nicholls: /* Default Network Ports */

2014-01-27T04:19:51Z

Default Network Ports

← Older revision		Revision as of 04:19, 27 January 2014
Line 92:		Line 92:

	=== Default Network Ports ===		=== Default Network Ports ===
	~~<br>~~
	{\|class="wikitable"		{\|class="wikitable"
	!Component		!Component

imported>Jason.nicholls at 04:17, 27 January 2014

2014-01-27T04:17:15Z

← Older revision		Revision as of 04:17, 27 January 2014
Line 2:		Line 2:
	[[Category:AppBoard 2.4]]		[[Category:AppBoard 2.4]]

			This document provides the system requirements for AppBoard 2.4.

	~~This page provides the system requirements for enPortal 5.4 and is specific to~~ an enPortal-only deployment ~~scenario.~~		For an enPortal-only deployment, please refer to the [[enportal/5.4/overview/system_requirements\|enPortal System Requirements]] page.
	If the enPortal deployment is meant to evolve in a later phase with the addition of AppBoard, then it is recommended to adhere to the system requirements of AppBoard in the initial enPortal-only phase rather than upgrade the system later. Therefore, please refer to the ~~system requirements document dedicated to AppBoard~~.
	~~<br>~~

	== Server Requirements ==		== Server Requirements ==
	~~<br>~~
	=== Supported Platforms ===		=== Supported Platforms ===
	~~<br>~~
	The following table lists the operating systems supported by ~~enPortal~~, but in general ~~enPortal~~ is supported on any 32- or 64- bit platform that can run Java Runtime Environment (JRE) 1.6 or later. ~~enPortal~~ is also supported on virtualized environments such as VMware.		The following table lists the operating systems supported by AppBoard, but in general AppBoard is supported on any 32- or 64- bit platform that can run Java Runtime Environment (JRE) 1.6 or later. AppBoard is also supported on virtualized environments such as VMware.
	~~<br>~~
	~~<br>~~
	{\|class="wikitable"		{\|class="wikitable"
	!Vendor		!Vendor
Line 36:		Line 34:
	\|}		\|}

			=== System Requirements ===

			Typical system requirements for an AppBoard-only deployment are listed in the table below.

	~~<br>~~		In addition, you will find examples of system configurations specific to different deployment scenarios such as Dev or Test Lab / Proof of Concept (POC), Network Operations Center (NOC), or Managed Services Providers (MSPs).

	~~=== System Requirements ===~~
	~~<br>~~
	Typical system requirements for an enPortal-only deployment are listed in the table below. In addition, you will find examples of system configurations specific to different deployment scenarios such as Dev or Test Lab / Proof of Concept (POC), Network Operations Center (NOC), or Managed Services Providers (MSPs). If the current deployment also includes (or plans to include) AppBoard, please refer to the System Requirements document dedicated to AppBoard.
	~~<br>~~
	~~<br>~~
	{\|class="wikitable"		{\|class="wikitable"
	!colspan ="2" style="border: 0px solid #000000; background-color:#fafafa"\|		!colspan ="2" style="border: 0px solid #000000; background-color:#fafafa"\|
Line 49:		Line 45:
	\|-		\|-
	!style="width: 20%;"\|Component		!style="width: 20%;"\|Component
	!style="width: 20%;"\|Minimum <br/> Requirement <br/>(per ~~enPortal~~ server)		!style="width: 20%;"\|Minimum <br/> Requirement <br/>(per server)
	!style="width: 20%;"\|Dev <br> or <br> Test Lab		!style="width: 20%;"\|Dev <br> or <br> Test Lab
	!style="width: 20%;"\|Internal use <br/>(NOC, SOC, etc)		!style="width: 20%;"\|Internal use <br/>(NOC, SOC, etc)
Line 90:		Line 86:

	<nowiki>**</nowiki> Regarding database requirements:		<nowiki>**</nowiki> Regarding database requirements:
	:<sup>(1)</sup> By default, enPortal includes an in-memory H2 database for configuration data to maintain the mappings between users, roles and proxied content. For most deployment scenarios - excluding High Availability (HA), clustered architectures - Edge recommends using this embedded H2 database. This will simplify the deployment and lower hardware cost as the H2 database will be installed on the same physical or logical server as the ~~enPortal~~ application.		:<sup>(1)</sup> By default, AppBoard (and enPortal) includes an in-memory H2 database for configuration data to maintain the mappings between users, roles and proxied content. For most deployment scenarios - excluding High Availability (HA), clustered architectures - Edge recommends using this embedded H2 database. This will simplify the deployment and lower hardware cost as the H2 database will be installed on the same physical or logical server as the AppBoard application.
	:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.		:<sup>(2)</sup> Optionally, if it is desired to use an external database for this configuration data, Edge supports the following databases: Hypersonic, SQLServer, Oracle, SQLAnywhere, PostgreSQL, and MySQL.
	:<sup>(3)</sup> For High Availability (HA), clustered ~~enPortal~~ architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the ~~enPortal~~ servers. Because the size of the database needed by enPortal will be minimal (typically in the 10's of MBs), using an existing customer-supplied, clustered database from the list in (2) above is encouraged to keep costs low and to minimize deployment efforts.		:<sup>(3)</sup> For High Availability (HA), clustered architectures, it is required to use an external database on separate hardware to avoid a single point of failure and ideally this database will be installed on an HA database cluster that has a high bandwidth, low latency network connection to the AppBoard servers.


Line 106:		Line 102:
	\|8080		\|8080
	\|HTTP		\|HTTP
	\|enPortal server via client host		\|AppBoard/enPortal server via client host
	\|-		\|-
	\|Tomcat Shutdown Port		\|Tomcat Shutdown Port
Line 124:		Line 120:

	== Client Browser Requirements ==		== Client Browser Requirements ==
	~~<br>~~
	{\|class="wikitable"		{\|class="wikitable"
	!Vendor		!Vendor
Line 162:		Line 158:
	\| Android 2.3.x, 4.x		\| Android 2.3.x, 4.x
	\| Adobe AIR		\| Adobe AIR

	\|-		\|-
	\|Apple		\|Apple

imported>Jason.nicholls at 04:00, 27 January 2014

2014-01-27T04:00:57Z

Show changes

imported>Jason.nicholls at 06:38, 14 December 2013

2013-12-14T06:38:15Z

← Older revision		Revision as of 06:38, 14 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:System Requirements}}		{{DISPLAYTITLE:System Requirements}}
			[[Category:AppBoard 2.4]]

	==Server Requirements==		==Server Requirements==