Sevenval FIT uses an Apache Web server to process HTTP client requests. As of release 14.1.0, FIT uses the Apache Web server supplied by the respective Linux distribution instead of shipping its own HTTP daemon package.
Even though FIT uses the Apache system package, it comes with its own configuration.
When you start the Web server with
service fit14apache start (or the
/opt/sevenval/fit14/sbin/apachectl script) the server root will be automatically set to
/opt/sevenval/fit14/and the configuration will be taken from
This also happens when
/etc/init.d/fit14apache starts the Web server at boot time.
Therefore, the FIT Apache Web server does not interfere with any other Web services being operated on the same system.
As with older versions of Sevenval FIT, the configuration of the Apache Web server is split across multiple files.
You should not change the
conf/httpd.conf file and the files in the
directory, as they will get overwritten on software updates. Also do not edit
the files in
conf/vhosts/ as they are generated from the
Instead, put your customizations
conf/include.global/ directory which is intended for global configuration
options affecting all virtual hosts.
.conf files therein are included
conf/httpd.conf and allow you to add or override certain configuration
settings. A second directory (
conf/include.local/) is provided for
customization of certain virtual hosts. Both directories contain some example files.
All supported Linux distributions include an Apache 2.4 Web server.
Thus, if you customize the Apache configuration as described above or include
httpd-conf sections in the
make sure that the syntax is compatible with Apache 2.4.
For scalability reasons, FIT uses the threaded worker multi-processing module (MPM).
The threaded Apache may hold thousands of open TCP connections which allows long
Keep-Alive timeouts without allocating huge amounts of RAM.
The server limits may be customized using the file
To do so, copy the example file
conf/include.global/limits.conf and adjust parameters like
ServerLimitfits into memory together with the running PHP-FPM processes.
MaxClientsshould be large enough to allow clients to keep their TCP connections open for a relatively long time (at most
ThreadsPerChildsetting should not be significantly larger than 128. Otherwise the performance may decrease due to access conflicts within the underlying OpenSSL library.
FIT_FETCH_MAX_TIMEOUTare increased significantly, the
ProxyTimeoutmay have to be adjusted accordingly.
Don’t forget to restart the Web server to activate the changes.
You should monitor the number of running
httpd processes. It should
at least be
MinSpareThreads divided by
as specified in
It also should be significantly lower than the
The Apache module
mod_status can provide detailed
information on the current system status under the URI
A configuration example for
is included in the