Difference between revisions of "Managing Backend Services"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 27: | Line 27: | ||
|- | |- | ||
|Quartz||Enabled||Time keeper for all scheduled events. | |Quartz||Enabled||Time keeper for all scheduled events. | ||
|} | |} | ||
<noinclude> | <noinclude> | ||
Revision as of 22:58, 18 September 2015
The AgileApps Cloud platform has several backend services. Each of them can be run on a different server, to improve performance and scalability. They can be disabled, as well, if they are not used.
It is highly recommended that the customer-facing web server is not used for the backend services. Instead, they should run in one or more dedicated instances of the platform, running on one more separate servers.
Important: Each of the services should enabled on only one server--not on multiple servers.
About the Backend Services
An Application Server instance can run one or more of the following services. Enabling and disabling them determines which instance they run in--or whether they are available at all.
Service Default Status Description Report Scheduler Disabled Runs scheduled reports when they're due Import Disabled Imports of data into the database Export Disabled Exports data from the database Memcached Disabled Data caching mechanism (installed separately) Marketing Disabled Handles email campaigns Bounce Disabled Handles bounced emails that result from such campaigns Quartz Enabled Time keeper for all scheduled events.