Clustering WildFly Applications - Java EE 7 Development with WildFly - page 406

The subsystem contains just a bare-bones configuration that references its socket binding
through the advertise-socket element:
<socket-binding name="modcluster" port="0"
multicast-address="224.0.1.105" multicast-port="23364"/>
On the Apache web server side, we have to install the core libraries that are used to inter-
act with mod_cluster . This is a very simple procedure; just point the browser to the
latest mod_cluster release at http://www.jboss.org/mod_cluster/downloads . Be sure to
choose a version that suits your operating system and architecture (x86 or x64).
Once the binaries are downloaded, extract the archive to a folder; then, navigate to the ex-
tracted folder. The mod_cluster binaries essentially consist of a bundled Apache web
server with all the required libraries installed. To preconfigure your installation, be sure to
run the \httpd-2.2\bin\installconf.bat file.
Note
It is possible to use your own Apache web server 2.2 installation; just pick up the modules
from the mod_cluster bundle and copy them to the modules folder of your Apache
web server.
If you choose to use your own Apache web server over the bundled one, you have to load
the following libraries into your httpd.conf file (the same set is used in the bundled
Apache HTTP):
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
LoadModule manager_module modules/mod_manager.so
LoadModule slotmem_module modules/mod_slotmem.so
LoadModule advertise_module modules/mod_advertise.so
Each of these modules covers an important aspect of load balancing, listed as follows:
• mod_proxy , mod_proxy_http , and mod_proxy_ajp : These are the core
modules that forward requests to cluster nodes using either the HTTP/HTTPS or
AJP protocol