Difference between revisions of "Managing Backend Services"
imported>Aeric |
imported>Aeric |
||
Line 33: | Line 33: | ||
===Configuring the Backend Services=== | ===Configuring the Backend Services=== | ||
Backend services are configured in the [[networking.properties]] file. | Backend services are configured in the [[networking.properties]] file. | ||
After changing <tt>networking.properties</tt>, restart the server. | After changing <tt>networking.properties</tt>, restart the server. |
Revision as of 22:27, 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, to avoid performance problems.
- A backend service should not be enabled on more than one server, to avoid errors.
Immediately after installing a server, then, it is necessary to disable all backend services, except for those services that are intended to run on the current server--and then only if the current server is intended to be a backend server.
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 Default Port Description Report Scheduler Enabled __TBD__ 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
Backend services are configured in the networking.properties file.
After changing networking.properties, restart the server.