Enportal/5.4/overview/system requirements - Revision history

imported>Jason.nicholls: Undo revision 8131 by Jason.nicholls (Talk)

2014-07-23T12:03:46Z

Undo revision 8131 by Jason.nicholls (Talk)

← Older revision		Revision as of 12:03, 23 July 2014
Line 4:		Line 4:
	This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.		This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.
	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.		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 enPortal, but in general enPortal is supported on any 32- or 64- bit platform that can run Java 6 or later. enPortal is also supported on virtualized environments such as VMware.
	~~<br>~~
	~~<br>~~		{\|class="wikitable"
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"
	!Vendor		!Vendor
	!Platform		!Platform
Line 24:		Line 22:
	\|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
Line 35:		Line 33:
	\|}		\|}

			=== 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.

	~~=== System Requirements ===~~		{\|class="wikitable"
	~~<br>~~		!colspan ="2" style="border: 0px solid #000000; background-color:#fafafa"\|
	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~~" border="1" style="text-align:center; background-color:#eeeeee;~~"
	!colspan ="2" style="border~~-top: 0px solid #000000; border-left: 0px solid #000000; border-right: 0px solid #000000; border-bottom~~: 0px solid #000000; background-color:#~~eeeeee~~"\|
	!colspan ="3"\|Example Deployment Scenarios		!colspan ="3"\|Example Deployment Scenarios
	\|-		\|-
Line 78:		Line 72:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|JRE ~~1.6+~~ installed on enPortal server (~~JRE 1.~~7+ recommended)		\|colspan="4"\|Java SE 6 (JRE) installed on enPortal server (Java 7 recommended)
	\|-		\|-
	\|Database <nowiki>*</nowiki>		\|Database <nowiki>*</nowiki>
Line 85:		Line 79:
	\|'''Recommended''': use an external, clustered RDBMS (3)		\|'''Recommended''': use an external, clustered RDBMS (3)
	\|}		\|}
	~~<br>~~

	<nowiki>*</nowiki> Notes in regards to the database requirements:		<nowiki>*</nowiki> Notes in regards to the database requirements:
	:(1) 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.		:(1) 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.
	:(2) 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~~.		:(2) 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.
	:(3) 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.		:(3) 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.

			=== Default Network Ports ===

	~~=== Default Network Ports ===~~		{\|class="wikitable"
	~~<br>~~
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"
	!Component		!Component
	!Port		!Port
Line 122:		Line 114:

	== Client Browser Requirements ==		== Client Browser Requirements ==
	~~<br>~~
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"		{\|class="wikitable"
	!Vendor		!Vendor
	!Platform		!Platform
Line 144:		Line 136:
	\|18+		\|18+
	\|}		\|}
	~~<br>~~
	<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.		<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.
	~~<br>~~

imported>Jason.nicholls: Reverted edits by Jason.nicholls (Talk) to last revision by Mylene.stolpe

2014-07-23T12:01:43Z

Reverted edits by Jason.nicholls (Talk) to last revision by Mylene.stolpe

← Older revision		Revision as of 12:01, 23 July 2014
Line 4:		Line 4:
	This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.		This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.
	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.		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 6 or later. enPortal is also supported on virtualized environments such as VMware.		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.
			<br>
	{\|class="wikitable"		<br>
			{\|class="wikitable" border="1" style="text-align:center; background-color:#eeeeee;"
	!Vendor		!Vendor
	!Platform		!Platform
Line 22:		Line 24:
	\|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
Line 30:		Line 32:
	\|Microsoft		\|Microsoft
	\|Windows		\|Windows
	\|7, 8~~, 8.1~~, Server 2003 ~~/ R2~~, Server 2008 / R2, Server 2012 ~~/ R2~~		\|Windows 7, 8, Server 2003, Server 2008 R2, Server 2012
	\|}		\|}


			<br>

	=== System Requirements ===		=== 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.		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>
	{\|class="wikitable"		<br>
	!colspan ="2" style="border: 0px solid #000000; background-color:#~~fafafa~~"\|		{\|class="wikitable" border="1" style="text-align:center; background-color:#eeeeee;"
			!colspan ="2" style="border-top: 0px solid #000000; border-left: 0px solid #000000; border-right: 0px solid #000000; border-bottom: 0px solid #000000; background-color:#eeeeee"\|
	!colspan ="3"\|Example Deployment Scenarios		!colspan ="3"\|Example Deployment Scenarios
	\|-		\|-
Line 72:		Line 78:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|~~Java SE~~ 6 ~~(JRE)~~ installed on enPortal server (~~Java~~ 7 recommended)		\|colspan="4"\|JRE 1.6+ installed on enPortal server (JRE 1.7+ recommended)
	\|-		\|-
	\|Database <nowiki>*</nowiki>		\|Database <nowiki>*</nowiki>
Line 79:		Line 85:
	\|'''Recommended''': use an external, clustered RDBMS (3)		\|'''Recommended''': use an external, clustered RDBMS (3)
	\|}		\|}
			<br>

	<nowiki>*</nowiki> Notes in regards to the database requirements:		<nowiki>*</nowiki> Notes in regards to the database requirements:
	:(1) 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.		:(1) 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.
	:(2) 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~~.		:(2) 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.
	:(3) 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.		:(3) 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.


	=== Default Network Ports ===		=== Default Network Ports ===
			<br>
	{\|class="wikitable"		{\|class="wikitable" border="1" style="text-align:center; background-color:#eeeeee;"
	!Component		!Component
	!Port		!Port
Line 114:		Line 122:

	== Client Browser Requirements ==		== Client Browser Requirements ==
			<br>
	{\|class="wikitable"		{\|class="wikitable" border="1" style="text-align:center; background-color:#eeeeee;"
	!Vendor		!Vendor
	!Platform		!Platform
Line 136:		Line 144:
	\|18+		\|18+
	\|}		\|}
			<br>
	<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.		<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.
			<br>

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

2014-07-23T12:00:46Z

Supported Platforms

← Older revision		Revision as of 12:00, 23 July 2014
Line 30:		Line 30:
	\|Microsoft		\|Microsoft
	\|Windows		\|Windows
	\|~~Windows~~ 7, 8, Server 2003, Server 2008 R2, Server 2012		\|7, 8, 8.1, Server 2003 / R2, Server 2008 / R2, Server 2012 / R2
	\|}		\|}

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

2014-07-10T11:34:38Z

System Requirements

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

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

2014-07-10T11:33:34Z

Supported Platforms

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

	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 enPortal, but in general enPortal is supported on any 32- or 64- bit platform that can run Java 6 or later. enPortal is also supported on virtualized environments such as VMware.

	{\|class="wikitable"		{\|class="wikitable"
Line 22:		Line 22:
	\|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
Line 32:		Line 32:
	\|Windows 7, 8, Server 2003, Server 2008 R2, Server 2012		\|Windows 7, 8, Server 2003, Server 2008 R2, Server 2012
	\|}		\|}


	=== System Requirements ===		=== System Requirements ===

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

2014-06-10T15:57:44Z

System Requirements

← Older revision		Revision as of 15:57, 10 June 2014
Line 83:		Line 83:
	<nowiki>*</nowiki> Notes in regards to the database requirements:		<nowiki>*</nowiki> Notes in regards to the database requirements:
	:(1) 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.		:(1) 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.
	:(2) 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~~.		:(2) 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.
	:(3) 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.		:(3) 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.


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

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

2014-01-27T04:10:54Z

← Older revision		Revision as of 04:10, 27 January 2014
Line 4:		Line 4:
	This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.		This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.
	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.		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 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.
	~~<br>~~
	~~<br>~~		{\|class="wikitable"
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"
	!Vendor		!Vendor
	!Platform		!Platform
Line 36:		Line 34:


	~~<br>~~		=== System Requirements ===

	~~=== 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.		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~~" border="1" style="text-align:center; background-color:#eeeeee;~~"		!colspan ="2" style="border: 0px solid #000000; background-color:#fafafa"\|
	!colspan ="2" style="border~~-top: 0px solid #000000; border-left: 0px solid #000000; border-right: 0px solid #000000; border-bottom~~: 0px solid #000000; background-color:#~~eeeeee~~"\|
	!colspan ="3"\|Example Deployment Scenarios		!colspan ="3"\|Example Deployment Scenarios
	\|-		\|-
Line 85:		Line 80:
	\|'''Recommended''': use an external, clustered RDBMS (3)		\|'''Recommended''': use an external, clustered RDBMS (3)
	\|}		\|}
	~~<br>~~

	<nowiki>*</nowiki> Notes in regards to the database requirements:		<nowiki>*</nowiki> Notes in regards to the database requirements:
Line 94:		Line 88:

	=== Default Network Ports ===		=== Default Network Ports ===
	~~<br>~~
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"		{\|class="wikitable"
	!Component		!Component
	!Port		!Port
Line 122:		Line 116:

	== Client Browser Requirements ==		== Client Browser Requirements ==
	~~<br>~~
	{\|class="wikitable~~" border="1" style="text-align:center; background-color:#eeeeee;~~"		{\|class="wikitable"
	!Vendor		!Vendor
	!Platform		!Platform
Line 144:		Line 138:
	\|18+		\|18+
	\|}		\|}
	~~<br>~~
	<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.		<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.
	~~<br>~~

imported>Mylene.stolpe at 19:37, 23 January 2014

2014-01-23T19:37:59Z

← Older revision		Revision as of 19:37, 23 January 2014
Line 40:		Line 40:
	=== System Requirements ===		=== System Requirements ===
	<br>		<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.		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>
	<br>		<br>
Line 78:		Line 78:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|JRE 1.6+ installed on enPortal server		\|colspan="4"\|JRE 1.6+ installed on enPortal server (JRE 1.7+ recommended)
	\|-		\|-
	\|Database <nowiki>*</nowiki>		\|Database <nowiki>*</nowiki>

imported>Mylene.stolpe at 00:08, 22 January 2014

2014-01-22T00:08:47Z

← Older revision		Revision as of 00:08, 22 January 2014
Line 3:		Line 3:

	This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.		This page provides the system requirements for enPortal 5.4 and is specific to an enPortal-only deployment scenario.
	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 ~~instead~~.		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>		<br>

Line 10:		Line 10:
	=== Supported Platforms ===		=== Supported Platforms ===
	<br>		<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 (~~JDK~~) 1.6 or later. enPortal is also supported on virtualized environments such as VMware.		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.
	<br>		<br>
	<br>		<br>
Line 78:		Line 78:
	\|-		\|-
	\|Java		\|Java
	\|colspan="4"\|~~JDK~~ 1.6+ installed on enPortal server		\|colspan="4"\|JRE 1.6+ installed on enPortal server
	\|-		\|-
	\|Database <nowiki>*</nowiki>		\|Database <nowiki>*</nowiki>
Line 88:		Line 88:

	<nowiki>*</nowiki> Notes in regards to the database requirements:		<nowiki>*</nowiki> Notes in regards to the database requirements:
	:(1) 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 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.		:(1) 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.
	:(2) 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.		:(2) 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.
	:(3) For 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.		:(3) 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.

imported>Mylene.stolpe at 18:53, 13 January 2014

2014-01-13T18:53:03Z

← Older revision		Revision as of 18:53, 13 January 2014
Line 10:		Line 10:
	=== Supported Platforms ===		=== Supported Platforms ===
	<br>		<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 (JDK) 1.6 or later. enPortal is also supported on virtualized environments such as ~~VMWare~~.		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 (JDK) 1.6 or later. enPortal is also supported on virtualized environments such as VMware.
	<br>		<br>
	<br>		<br>
Line 60:		Line 60:
	\|-		\|-
	\|Memory		\|Memory
	\|1 GB RAM		\|4 GB RAM
	\|2 GB RAM		\|4 GB RAM
	\|4-8 GB RAM		\|4-8 GB RAM
	\|16-32 GB RAM		\|16-32 GB RAM
Line 127:		Line 127:
	!Platform		!Platform
	!Version(s)		!Version(s)
			!Minimum <br> Screen Resolution
	!Optional Plug-Ins*		!Optional Plug-Ins*
	\|-		\|-
	\|Microsoft		\| Microsoft
	\|Internet Explorer		\| Internet Explorer
	\|7, 8, 9, 10, 11		\| 7, 8, 9, 10, 11
			\|rowspan="3"\|1024x768
	\|rowspan="3"\|as required by integrated applications		\|rowspan="3"\|as required by integrated applications
	\|-		\|-
	\|Mozilla		\|Mozilla
	\|Firefox		\|Firefox
	\|3+		\|3.6.28+
	\|-		\|-
	\|Google		\|Google
	\|Chrome		\|Chrome
	\|4+		\|18+
	\|}		\|}
	<br>		<br>
	<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.		<nowiki>*</nowiki> If enPortal is deployed in conjunction with AppBoard, then the Adobe Flash Player is required for any client browser used.
	<br>		<br>