...
Once the Apache HTTP Server
...
is installed, it can be configured to operate as Load Balancer.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Code Block |
---|
LoadModule jk_module modules/mod_jk.so
# JK/Worker configuration
# Where to find workers.properties
JkWorkersFile conf/workers.properties
# Where to put jk logs
JkLogFile logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
JkMount /* loadbalancer
# In case you want to be able to monitor JK status
# <Location /jkmanager/>
# JkMount jkstatus
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
# </Location>
|
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Wiki Markup |
---|
You have a possibility to monitor and control worker activity by uncommenting the "jkstatus" related comments in *worker.properties* and *httpd.conf* and accessing "_\[randd:yourServerUrl\]/jkmanager/_". This page will also allow you to activate/disable workers. You should add a worker for each Servoy Application Server that you will possibly start in your cluster, even if you do not plan to have them started all at once. There is no problem if only a part of those Servoy Application Servers are started. Load-balancing will work on servers defined in the *worker.properties* file that are also available. If you do define workers for Servoy Application Servers that are not started, disable them from the jkmanager page in order to avoid delays caused by load-balancer trying to check the availability of these workers. |
This will describe how to set up the two Tomcat Servers in your Servoy installations as used by original worker.properties file above. You can adapt it when using more Servoy installations.
Wiki Markup |
---|
In \[randd:servoy_install_folder\]/application_server/server/conf/server.xml: |
Code Block |
---|
<Connector port="8009"
enableLookups="false" maxThreads="500" connectionTimeout="60000"
redirectPort="8443" useBodyEncodingForURI="true" protocol="AJP/1.3"/>
|
...
It's possibility to monitor and control worker activity by uncommenting the "jkstatus" related comments in worker.properties and httpd.conf and accessing <loadBalancerUrl>/jkmanager/. This page will also allows to activate/disable workers. A worker should be added for each Servoy Application Server that will possibly be started in the cluster, even when not planning to have them started all at once. There is no problem if only a part of those Servoy Application Servers are started. Load-balancing will work on servers defined in the worker.properties file that are also available. If workers are defined for Servoy Application Servers that are not started, disable them from the jkmanager page in order to avoid delays caused by load-balancer trying to check the availability of these workers.