Appboard/2.4/system requirements: Difference between revisions

imported>Jason.nicholls
No edit summary
imported>Jason.nicholls
 
(7 intermediate revisions by the same user not shown)
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 6 or later. AppBoard is also supported on virtualized environments such as VMware.
<br>
 
<br>
{|class="wikitable"
{|class="wikitable"
!Vendor
!Vendor
Line 25: 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
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 79: Line 75:
|-
|-
|Java
|Java
|colspan="4"|JRE 1.6+ installed on enPortal server (JRE 1.7+ recommended)
|colspan="4"|Java SE 6 (JRE) installed on AppBoard server (Java SE 7 recommended)
|-
|-
|Database **
|Database **
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, MySQL and DB2.
:<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.


==== Combined AppBoard & enPortal Deployments ====
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 ===
<br>
 
{|class="wikitable"
{|class="wikitable"
!Component
!Component
Line 106: Line 107:
|8080
|8080
|HTTP
|HTTP
|enPortal server via client host
|AppBoard/enPortal server via client host
|-
|-
|Tomcat Shutdown Port
|Tomcat Shutdown Port
Line 124: Line 125:


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

Latest revision as of 11:34, 10 July 2014


This document provides the system requirements for AppBoard 2.4.

For an enPortal-only deployment, please refer to the enPortal System Requirements page.

Server Requirements

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 6 or later. AppBoard 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 AppBoard-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).

Example Deployment Scenarios
Component Minimum
Requirement
(per 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 Java SE 6 (JRE) installed on AppBoard server (Java SE 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, 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.
(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 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

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

Component Port Protocol Scope/Accessibility
Tomcat Web Server 8080 HTTP AppBoard/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=3038"