• No results found

AppBoard TM 2.6. System Requirements. Technical Documentation. Version July 2015

N/A
N/A
Protected

Academic year: 2021

Share "AppBoard TM 2.6. System Requirements. Technical Documentation. Version July 2015"

Copied!
9
0
0

Loading.... (view fulltext now)

Full text

(1)

Technical Documentation

Edge Technologies

1881 Campus Commons Drive Suite 101

AppBoard

TM

2.6

System

Requirements

Version 2.6.0

July 2015

(2)

Table of Contents

Overview

... 3

Scope

... 3

Server Requirements

... 4

Supported Platforms

... 4

System Requirements

... 4

Client Browser Requirements

... 7

Mobile Client Requirements

... 8

(3)

Overview

AppBoard is a groundbreaking data integration/data visualization platform that dramatically redefines the cost/benefit equation for the development and deployment of real-time business systems

dashboards. AppBoard allows you to connect, integrate, visualize, and interact with your data in a simple, straight forward builder environment. The end result is powerful, compelling dashboards that summarize data from multiple sources and can be accessed from any device.

enPortal is a secure, vendor-neutral network management integration platform. With pre-built Product Integration Modules (PIMs) for common third-party applications, enPortal is a Commercial Off The Shelf (COTS) solution that quickly integrates these network management tools in a unified display. enPortal also provides advanced capabilities including Single Sign-On (SSO), multi-tenancy,

re-branding, HTML content manipulation / application "hardening" and role/domain-based access via a secure proxy.

Scope

This document provides the system requirements for AppBoard 2.6.

While the main purpose of the document is to address AppBoard-only configuration scenario, it also covers combined deployment scenario where enPortal and AppBoard are implemented and configured together, co-located on the same server.

For an enPortal-only deployment, please refer to the system requirements document dedicated to enPortal.

(4)

Server Requirements

Supported Platforms

The following table lists the operating systems supported by AppBoard, but in general AppBoard is supported on any 64- bit platform that can runJava 7 or later. AppBoard is also supported on virtualized environments such as VMware. enPortal supports the same platforms and is typically installed on the same server.

Vendor Platform Version(s)

Oracle/Sun Microsystems Solaris 8, 9, 10, 11 / SPARC or x86 / x86_64

Red Hat Enterprise Linux Linux 5.7+, 6, 7 (or equivalent for CentOS, Scientific Linux, Oracle Linux, and Amazon Linux)

SUSE Linux Enterprise Server Linux 10, 11

Microsoft Windows Windows 7, 8, 8.1, Server 2003 / R2, Server 2008 / R2, Server 2012 / R2

System Requirements

Typical system requirements for an AppBoard-only deployment are listed in the Table 1 below. Table 2 provides similar system requirements for a combined AppBoard and enPortal configuration.

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 includes enPortal exclusively and AppBoard is not planned to be added in a later phase, please refer to the System Requirements document dedicated to enPortal.

(5)

Example Deployment Scenarios

Component

Minimum Requirement (per AppBoard 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 7 (JRE) installed on AppBoard server (Java SE 8 recommended)

Database ** Recommended: use the embedded H2 database (1) OPTIONAL: external database; see below (2)

Recommended: use an

external, clustered RDBMS (3)

Table 1 - AppBoard-only Deployment System Requirements

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 4 CPU cores 4-8 CPU cores

Memory 4 GB RAM 4 GB RAM 8-16 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 7 (JRE) installed on AppBoard server (Java SE 8 recommended)

Database ** Recommended: use the embedded H2 database (1) OPTIONAL: external database; see below (2)

Recommended: use an

external, clustered RDBMS (3)

(6)

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

** Notes in regards to the 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: SQL Server, Oracle, SQL Anywhere, 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 enPortal servers.

(7)

Default Ports

Ports 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 8, 9, 10, 11

1024x768

- Adobe Flash Player 18 or greater

- other plug-ins as required by integrated applications

Mozilla Firefox 3.6.28+

(8)

Mobile Client Requirements

Vendor Device Operating Systems Additional

Requirements Vendors distributing Android-based devices

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

Various Phones/ Tablets Android 2.3.x, 4.x Adobe Air

(9)

About Edge Technologies, Inc.

Edge Technologies is an innovative and proven software company specializing in the combination of data integration and visualization. Through its core practices in Data Integration, Data Visualization, and Solutions Consulting, Edge products and services facilitate faster, more complete data integration; user-centric, customized visualizations; easy, secure information sharing; and enhanced operational awareness across a diverse set of information stakeholders. Edge has been delivering leading-edge solutions in many of the world’s most sophisticated network, intelligence, operational and logistics environments since 1993. Recognized for the ability to identify, adopt and deploy emerging technology platforms, Edge’s industry-leading products have proven to be ground breaking solutions that stand the test of time.

Edge’s technological expertise in developing lasting innovation is fortified by the company’s value-focused customer and partner relationships. Recognized for meticulous software engineering and a high-touch customer service approach, Edge’s success is built on innovative technology driven by experienced, customer-focused personnel.

The Edge Agile Development Methodology first identifies customer challenges, then applies design expertise and innovation to create better solutions and backs it all by the people and technology to ensure the solutions work in the real-world and for the long-haul.

Unlike competitive offerings, Edge’s products are designed with both the development staff and the executive team in mind. Edge software toolkits do the heavy lifting to streamline internal development efforts, accelerate time to market, and empower staff to focus on situational and operational objectives. What’s more, Edge’s advanced software

architecture enables its products to easily scale to handle hundreds of concurrent users.

Edge empowers businesses and government agencies to fulfill the potential of their network and business systems management assets to make better decisions faster.

Figure

Table 1 - AppBoard-only Deployment System Requirements

References

Related documents

Health and Human Development University Park, Altoona, Harrisburg, Fayette, New Kensington, Schuylkill, Shenango, Mont Alto, World Campus, Worthington Scranton

Occasional meetings on trade among senior staff of the IMF, World Bank, and WTO, and possibly other multilateral economic institutions will continue, and Fund staff will seek to

Drawing on and internalizing the work of the DGI, the Fund created the SDDS Plus in 2012, at the time of the Eighth Review of the Fund’s Data Standards Initiatives (IMF, 2012a).”

Note: Administrative codes and documentation requirements are drawn from 2015 Healthcare Effectiveness Data and Information Set (HEDIS) Volume 2 Technical Specifications.. Codes

The World Bank ICT Sector Unit and Esade have developed this understanding through collabo- rating with projects such as Open Cities, Com- mons for Europe / Code for Europe or City

Most of the guidelines indicate explicitly the use of the peak shear strength parameters in- stead of the residual shear strength parameters in the design of geosynthetic

• The program is an interdisciplinary team of public health, nursing, and social work students whose aim is to:.. • Provide evidence-based health information, screening,

The capability of sialic acids to block recognition of cells through masking of carbohydrate epitopes was demonstrated in chapter 3 when desialylation of