Appboard/2.4/software components: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
| Line 8: | Line 8: | ||
[[File:AppBoardComponents.png]] | [[File:AppBoardComponents.png]] | ||
== Main Components == | |||
=== Apache Tomcat Server === | |||
=== Configuration Database === | |||
In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or ports. | |||
In clustering or high-availability environments AppBoard can be configured to use an external configuration database. This is via a JDBC driver and requires network connectivity to the external database. | |||
=== AppBoard Clients === | |||
AppBoard clients are supported Web Browsers running the '''Builder''' or '''Viewer''' in an Adobe Flash Player plug-in. | |||
All rendering takes place within the client and this is comprised of native flash content (via the flash plugin) and HTML frames (via the browser). The AppBoard server communicates with the client over HTTP or HTTPS for all resources, data communications, and enPortal proxied content. | |||
== Additional Credits == | == Additional Credits == | ||
AppBoard incorporates the use of some 3rd party libraries. See the [[appboard/2.4/license_credits|License Credits]] page for more information. | AppBoard incorporates the use of some 3rd party libraries. See the [[appboard/2.4/license_credits|License Credits]] page for more information. | ||
Revision as of 07:50, 11 July 2014
Overview
AppBoard consists of a number of software components working together to deliver the overall features. In actual deployments the architecture may also include some custom (external to AppBoard) components in addition to the core AppBoard product, and any external product integrations.
This page details the individual software components. For a more general overview of how AppBoard works, refer to the Overview page.
Main Components
Apache Tomcat Server
Configuration Database
In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or ports.
In clustering or high-availability environments AppBoard can be configured to use an external configuration database. This is via a JDBC driver and requires network connectivity to the external database.
AppBoard Clients
AppBoard clients are supported Web Browsers running the Builder or Viewer in an Adobe Flash Player plug-in.
All rendering takes place within the client and this is comprised of native flash content (via the flash plugin) and HTML frames (via the browser). The AppBoard server communicates with the client over HTTP or HTTPS for all resources, data communications, and enPortal proxied content.
Additional Credits
AppBoard incorporates the use of some 3rd party libraries. See the License Credits page for more information.
