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

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. (The exception would be a single-user server used for development or proof of concept.) With the exception of memcached, 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	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)
Quartz	Enabled	Time keeper for all scheduled events.

Enabling and Disabling Backend Services

During installation, the networking.properties file is created. That file can be used to manually enable and disable backend services for an existing installation.

Important: Each background service should run on only one server.

To view the server list

1. Open {install-dir}/profiles/IS_default/configuration/tomcat/conf/RN/networking.properties

   Servers are listed in this format: xxxxx_manager_instance=1
   where "xxxxx" is one of "import", "report", etc.

To Disable a service

1. Add a "#" character before the xxxxx_manager_instance=1 command

   # report_manager_instance=1

2. Save the file
3. Restart the Application Server

To Enable a service

1. Remove the "#" character from the xxxxx_manager_instance=1 command

   report_manager_instance=1

2. Save the file
3. Restart the Application Server

Configuring Backend Services

During installs and upgrades, it is only necessary to enable or disable a service on a platform instance. The install/upgrade process takes care of making the connections.

To change a configuration for an existing installation, changes need to be made manually, by adjusting the networking.properties file(s) and restarting the Application Server(s).

Note: A change in the configuration for either memcached, quartz, or the document service requires a restart of all Application Servers.

The general process is:

1. Make the changes to the networking.properties files for all Application Servers.
2. Restart the Application Servers.

These sections describe the changes to make:

• Configuring Document Services
• Configuring the Quartz Scheduler
• Configuring memcached