View source for Managing Backend Services

<includeonly>=== Managing Backend Services ===</includeonly>
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, to avoid performance problems.<br>(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.

:{| border="1" cellpadding="5" cellspacing="0"
!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}}
{{:Configuring Backend Services}}
<noinclude>

[[Category:Installation]]
</noinclude>