AgileApps Support Wiki Pre Release

Difference between revisions of "Platform Components"

From AgileApps Support Wiki
imported>Aeric
m (Text replace - 'Category:System Administration' to 'Category:Installation')
 
imported>Aeric
Line 1: Line 1:
===Platform Software Stack===
===Platform Software Stack===


This diagram shows how the server processes that make up the LongJump Platform relate to one another:
This diagram shows how the server processes that make up the platform relate to one another:


:[[File:server_processes.png]]
:[[File:server_processes.png]]


;LongJump Application:The LongJump Application Server is a web app that runs in the Apache Tomcat container, so it can be deployed as a standalone web server. That configuration is useful for testing, experimentation, and other low-volume scenarios:
;Application Server:The Application Server is a web app that runs in the Apache Tomcat container, so it can be deployed as a standalone web server. That configuration is useful for testing, experimentation, and other low-volume scenarios:


::[[File:LongJump_as_WebServer.png]]
::[[File:LongJump_as_WebServer.png]]


;(Optional) Apache HttpD:Alternatively, the Apache <tt>httpd</tt> web server can be used to serve static content. In that case, LongJump acts as the application server behind the Apache <tt>httpd</tt> web server. Those instances can be running on the same server, or on different servers, so either of these configurations is possible:
;(Optional) Apache HttpD:Alternatively, the Apache <tt>httpd</tt> web server can be used to serve static content. In that case, the platform runs as an application server behind the Apache <tt>httpd</tt> web server. Those instances can be running on the same server, or on different servers, so either of these configurations is possible:


::[[File:LongJump_with_Apache_WebServer.png]]
::[[File:LongJump_with_Apache_WebServer.png]]
Line 18: Line 18:


;Memcached:The MEMory CACHE Daemon (<tt>[http://memcached.org/ memcached]</tt>) is an optional, but highly recommended process that stores frequently-accessed data in memory, so it can be retrieved with maximum speed.
;Memcached:The MEMory CACHE Daemon (<tt>[http://memcached.org/ memcached]</tt>) is an optional, but highly recommended process that stores frequently-accessed data in memory, so it can be retrieved with maximum speed.
 
<noinclude>


[[Category:Installation]]
[[Category:Installation]]
</noinclude>

Revision as of 23:55, 22 June 2011

Platform Software Stack

This diagram shows how the server processes that make up the platform relate to one another:

File:Server processes.png
Application Server
The Application Server is a web app that runs in the Apache Tomcat container, so it can be deployed as a standalone web server. That configuration is useful for testing, experimentation, and other low-volume scenarios:
File:LongJump as WebServer.png
(Optional) Apache HttpD
Alternatively, the Apache httpd web server can be used to serve static content. In that case, the platform runs as an application server behind the Apache httpd web server. Those instances can be running on the same server, or on different servers, so either of these configurations is possible:
File:LongJump with Apache WebServer.png
MySQL Database
MySQL is a relational database with capacities for redundancy, failover, backup, distributed access, and transactional integrity. That platform makes data look like Java objects to application developers. That makes applications easier to develop. But under the covers, the reliability and robustness of a mature relational database provides for data safety and rapid access.
Replicated Database
Database replication is a virtual necessity for any successful deployment. It safeguards data, and it allows for efficient backup and reporting from the replicated database, to minimize response time to users.
Memcached
The MEMory CACHE Daemon (memcached) is an optional, but highly recommended process that stores frequently-accessed data in memory, so it can be retrieved with maximum speed.