Difference between revisions of "Managing Backend Services"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 2: | Line 2: | ||
The {{enterprisebrand}} 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. | The {{enterprisebrand}} 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. | ||
{{Important| <br>All backend services are enabled by default. ''But...'' | |||
# Backend services should ''not'' be enabled on a customer-facing web server. | |||
# A backend service should ''not'' be enabled on more than one server. | |||
}} | |||
Do ''not'' use for 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.}} | {{Important | Each of the services should enabled on only one server--not on multiple servers.}} | ||
| Line 8: | Line 12: | ||
==== About the Backend Services ==== | ==== 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. | 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. | ||
:{| border="1" cellpadding="5" cellspacing="0" | :{| border="1" cellpadding="5" cellspacing="0" | ||
| Line 14: | Line 19: | ||
!Description | !Description | ||
|- | |- | ||
|Report Scheduler|| | |Report Scheduler||Enabled||Runs scheduled reports when they're due | ||
|- | |- | ||
|Import|| | |Import|| Enabled||Imports of data into the database | ||
|- | |- | ||
|Export|| | |Export||Enabled||Exports data from the database | ||
|- | |- | ||
|Memcached || | |Memcached ||Enabled||Data caching mechanism (installed separately) | ||
|- | |- | ||
|Marketing|| | |Marketing||Enabled||Handles email campaigns | ||
|- | |- | ||
|Bounce|| | |Bounce||Enabled||Handles bounced emails that result from such campaigns | ||
|- | |- | ||
|Quartz||Enabled||Time keeper for all scheduled events. | |Quartz||Enabled||Time keeper for all scheduled events. | ||
Revision as of 18:10, 21 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.
Important:
All backend services are enabled by default. But...- Backend services should not be enabled on a customer-facing web server.
- A backend service should not be enabled on more than one server.
Do not use for 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 Enabled Runs scheduled reports when they're due Import Enabled Imports of data into the database Export Enabled Exports data from the database Memcached Enabled Data caching mechanism (installed separately) Marketing Enabled Handles email campaigns Bounce Enabled Handles bounced emails that result from such campaigns Quartz Enabled Time keeper for all scheduled events.
Configuring the Backend Services
__TBD__