Appboard/2.4/system requirements: Difference between revisions

imported>Jason.nicholls
No edit summary
imported>Jason.nicholls
No edit summary
Line 2: Line 2:
[[Category:AppBoard 2.4]]
[[Category:AppBoard 2.4]]


==Server Requirements==


=== Supported Operating Systems ===
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.
<br>
 
== Server Requirements ==
<br>
=== 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.
<br>
<br>
{|class="wikitable"
{|class="wikitable"
!Vendor
!Vendor
Line 10: Line 19:
!Versions
!Versions
|-
|-
|Sun Microsystems
|Oracle/Sun Microsystems
|Solaris
|Solaris
|8, 9, 10, 11 - SPARC or x86 / x86_64
|8, 9, 10, 11 - SPARC or x86 / x86_64
Line 26: Line 35:
|Windows 7, 8, Server 2003, Server 2008 R2, Server 2012
|Windows 7, 8, Server 2003, Server 2008 R2, Server 2012
|}
|}
AppBoard/enPortal is supported on any Platform and Operating System that can run the Java Development Kit.  This includes many 32-bit and 64-bit systems.  For a complete list of supported environments, see [http://www.oracle.com/technetwork/java/javase/system-configurations-135212.html Oracle Certified System Configurations]
 
 
<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.
<br>
<br>
{|class="wikitable"
{|class="wikitable"
!Component
!colspan ="2" style="border: 0px solid #000000; background-color:#fafafa"|
!Requirements
!colspan ="3"|Example Deployment Scenarios
|-
!style="width: 20%;"|Component
!style="width: 20%;"|Minimum <br/> Requirement <br/>(per enPortal server)
!style="width: 20%;"|Dev <br> or <br> Test Lab
!style="width: 20%;"|Internal use <br/>(NOC, SOC, etc)
!style="width: 20%;"|External use <br/>(MSP customer-facing)<br/> 2+ servers in a cluster
|-
|-
|Hardware
|CPU
|Minimum: Single-CPU, 32-bit OS
|Single CPU
Recommended: Dual-CPU+, 64-bit OS
|Single CPU
|2+ CPU cores
|4-8 CPU cores
|-
|-
|Memory
|Memory
|Minimum: 2GB
|4 GB RAM
Recommended: 4GB+ (64-bit OS and JRE required)<br />
|4 GB RAM
''* note: see the [[Memory_Configuration|Memory Configuration]] page for additional information as actual memory usage will depend on many factors.''
|4-8 GB RAM
|16-32 GB RAM
|-
|Storage *
| 1 GB disk
| 1 GB disk
| 2 GB disk
| 2 GB disk
|-
|-
|Storage
|Operating System
|Minimum: 1.0 GB<br/>
|32 or 64 bit O/S
''* note: actual storage requirements will depend on implementation, but as AppBoard typically accesses data from remote sources and keeps it in-memory storage requirements are low''
|32 or 64 bit O/S
|64 bit O/S
|64 bit O/S
|-
|-
|Software
|Java
| Minimum: Java SE JRE version 6, 32-bit
|colspan="4"|JRE 1.6+ installed on enPortal server (JRE 1.7+ recommended)
Recommended: Latest 64-bit JRE (currently version 7)
|-
|-
|Database
|Database **
| A relational database management system (RDBMS)
|colspan="3"|'''Recommended''':  use the embedded H2 database <sup>(1)</sup>
''* note: AppBoard includes an in-memory H2 database for configuration data. In HA or load balanced deployments an external configuration database may be used as supported by EclipseLink: Microsoft SQL Server, Oracle, Sybase SQL Anywhere, PostgreSQL, Hypersonic, and MySQL.''
'''OPTIONAL''': external database;  see below <sup>(2)</sup>
|'''Recommended''':  use an external, clustered RDBMS <sup>(3)</sup>
|}
|}
<nowiki>*</nowiki> AppBoard storage requirements are very low as only configuration information and assets are stored locally. However, ultimately this will depend on the implementation and whether any custom solutions are making use of the local filesystem.<br/>
<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>(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. 


=== Default Network Ports ===
=== Default Network Ports ===
<br>
{|class="wikitable"
{|class="wikitable"
!
!Component
!Port
!Port
!Protocol
!Protocol
!Scope
!Scope/Accessibility
|-
|-
|Tomcat Web Server
|Tomcat Web Server
|8080
|8080
|HTTP
|HTTP
|*
|enPortal server via client host
|-
|-
|Tomcat Shutdown Port
|Tomcat Shutdown Port
Line 71: Line 112:
|N/A
|N/A
|localhost
|localhost
|-
|embedded H2 database
|N/A
|JDBC/ System File
|runs in the Tomcat process
|-
|(optional - if used) external database
|colspan="3"|Refer to specifications outlined by the vendor of the database of choice.
|-
|-
|}
|}


== Desktop Client Requirements ==
== Client Browser Requirements ==
 
<br>
{|class="wikitable" border="1" style="background-color:#eeeeee;"
{|class="wikitable"
!Vendor
!Vendor
!Platform
!Platform
!Version(s)
!Version(s)
!Plug-In
!style="width: 6em"|Minimum Screen Resolution
!style="width: 14em"|Plug-Ins
|-
|-
|Microsoft
| Microsoft  
|Internet Explorer
| Internet Explorer  
|7, 8, 9, 10
| 7, 8, 9, 10, 11
|[[Flash_Player_Version|Adobe Flash Player 11]]
|rowspan="3" style="text-align: center"|1024x768
|rowspan="3"|<ul><li>Adobe Flash Player 11+</li>
<li>other plug-ins as required by integrated applications</li>
</ul>
|-
|-
|Mozilla
|Mozilla
|Firefox
|Firefox
|3+
|3.6.28+
|[[Flash_Player_Version|Adobe Flash Player 11]]
|-
|-
|Google
|Google
|Chrome
|Chrome
|4+
|18+
|[[Flash_Player_Version|Adobe Flash Player 11]]
|}
|}


== Mobile Client Requirements ==
== Mobile Client Requirements ==


{|class="wikitable" border="1" style="background-color:#eeeeee;"
{|class="wikitable"
!Vendor
!Device
!Device
!Operating System
!Operating System
!style="width: 6em"|Additional Requirements
|-
|-
|Various Phones / Tablets
|Vendors distributing Android-based devices
|Android 2.3.x, 4.x
(Samsung, HTC, Google, Sony, etc...)
''also requires Adobe AIR''
|Various Phones/Tablets
| Android 2.3.x, 4.x
| Adobe AIR
 
|-
|-
|Apple iPhone / iPad / iPod Touch
|Apple
|iPhone, iPad, iPod Touch
|iOS 6, iOS 7
|iOS 6, iOS 7
|}
<!--
== SDK Developer Requirements ==
{|class="wikitable"
!Software
|
|
*Java SE JDK 6+
*Adobe Flash Builder 4.5.1
*Adobe Flex SDK 4.5.1
*Adobe Flex 4.5.1 Data Visualization Components for Flash Builder 4.5.1
|}
|}
-->

Revision as of 04:00, 27 January 2014


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.

Server Requirements


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.

Vendor Platform Versions
Oracle/Sun Microsystems Solaris 8, 9, 10, 11 - SPARC or x86 / x86_64
Red Hat Enterprise Linux Linux 5.7+, 6+ (or equiv for CentOS, Scientific Linux, Oracle Linux, and Amazon Linux)
SUSE Linux Enterprise Server Linux 10, 11
Microsoft Windows Windows 7, 8, Server 2003, Server 2008 R2, Server 2012



System Requirements


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.

Example Deployment Scenarios
Component Minimum
Requirement
(per enPortal server) 		Dev
or
Test Lab 		Internal use
(NOC, SOC, etc) 		External use
(MSP customer-facing)
2+ servers in a cluster
CPU Single CPU Single CPU 2+ CPU cores 4-8 CPU cores
Memory 4 GB RAM 4 GB RAM 4-8 GB RAM 16-32 GB RAM
Storage * 1 GB disk 1 GB disk 2 GB disk 2 GB disk
Operating System 32 or 64 bit O/S 32 or 64 bit O/S 64 bit O/S 64 bit O/S
Java JRE 1.6+ installed on enPortal server (JRE 1.7+ recommended)
Database ** Recommended: use the embedded H2 database (1)

OPTIONAL: external database; see below (2)

Recommended: use an external, clustered RDBMS (3)

* AppBoard storage requirements are very low as only configuration information and assets are stored locally. However, ultimately this will depend on the implementation and whether any custom solutions are making use of the local filesystem.

** Regarding 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.
(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.


Default Network Ports


Component Port Protocol Scope/Accessibility
Tomcat Web Server 8080 HTTP enPortal server via client host
Tomcat Shutdown Port 8005 N/A localhost
embedded H2 database N/A JDBC/ System File runs in the Tomcat process
(optional - if used) external database Refer to specifications outlined by the vendor of the database of choice.

Client Browser Requirements


Vendor Platform Version(s) Minimum Screen Resolution Plug-Ins
Microsoft Internet Explorer 7, 8, 9, 10, 11 1024x768
  • Adobe Flash Player 11+
  • other plug-ins as required by integrated applications
Mozilla Firefox 3.6.28+
Google Chrome 18+

Mobile Client Requirements

Vendor Device Operating System Additional Requirements
Vendors distributing Android-based devices

(Samsung, HTC, Google, Sony, etc...)

Various Phones/Tablets Android 2.3.x, 4.x Adobe AIR
Apple iPhone, iPad, iPod Touch iOS 6, iOS 7
Retrieved from "http://ab.edge-technologies.com/docs/index.php?title=Appboard/2.4/system_requirements&oldid=3030"