Difference between revisions of "Platform Components"
From AgileApps Support Wiki
imported>Aeric m (Text replace - 'Category:System Administration' to 'Category:Installation') |
imported>Aeric |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
===Platform | <includeonly>===Platform Components===</includeonly> | ||
These components that are part of a platform deployment: | |||
<blockquote> | |||
;Application Server:The Application Server is a web application that runs in the Common Tomcat Platform (CTP) container. | |||
;(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: | |||
;(Optional) Messaging Server:The messaging server <!--handles traffic generated by a [[Twitter Search]]. It also -->provides for on-screen notifications when people are viewing the same case. | |||
; | |||
;MySQL Database:[http://en.wikipedia.org/wiki/MySQL 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. | ;MySQL Database:[http://en.wikipedia.org/wiki/MySQL 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. | ||
| Line 18: | Line 13: | ||
;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. | ||
</blockquote> | |||
<noinclude> | |||
[[Category:Installation]] | [[Category:Installation]] | ||
</noinclude> | |||
Latest revision as of 10:11, 16 October 2019
These components that are part of a platform deployment:
- Application Server
- The Application Server is a web application that runs in the Common Tomcat Platform (CTP) container.
- (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:
- (Optional) Messaging Server
- The messaging server provides for on-screen notifications when people are viewing the same case.
- 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.