Managing Backend Services

From AgileApps Support Wiki
Revision as of 18:13, 21 September 2015 by imported>Aeric (→‎Configuring the Backend Services)

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.

Warn.png

Important:
All backend services are enabled by default. But...

  1. Backend services should not be enabled on a customer-facing web server.
  2. A backend service should not be enabled on more than one server.

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 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

Backend services are configured in the network.properties file. It looks like this:

After changing network.properties, restart the server.