This topic has not yet been written. The content below is from the topic description.
Setting up mod_cluster Mod_cluster requires modules to be added to Apache HTTPD as well as deploying a new application to your JBoss application instance. The following steps walk through getting these additional components, installing, and configuring them. Similar to how you downloaded EWS, download the mod_cluster modules from access.redhat.com (mod_cluster-native) Illustration 35: Downloading mod_cluster from rhn Depending on your installation route for Apache HTTPD (rpm or from EWS zip) – downloading this rpm may update your httpd modules instance for you. What you need to make sure you have is the following modules inside your httpd modules directory: mod_proxy.so mod_proxy_ajp.so mod_slotmem.so mod_manager.so mod_proxy_cluster.so mod_advertise.so Once these module are in the modules directory, we need to add the modules to our httpd.conf so that they are loaded when Apache starts up. LoadModule proxy_module /var/local/httpd/modules/mod_proxy.so LoadModule proxy_ajp_module /var/local/httpd/modules/mod_proxy_ajp.so LoadModule slotmem_module /var/local/httpd/modules/mod_slotmem.so LoadModule manager_module /var/local/httpd/modules/mod_manager.so LoadModule proxy_cluster_module /var/local/httpd/modules/mod_proxy_cluster.so LoadModule advertise_module /var/local/httpd/modules/mod_advertise.so With the modules added, we now show the minimal configuration needed to get mod_cluster running. Notice how different this is as compared to mod_proxy and mod_jk – we are not defining any workers or contexts. In the following example, we are setting up a new VirtualHost. The key here is to create a new socket for communication with the backend servers. We restrict access to a certain IP range (in this case, just local). Finally, we name our ManagerBalancer and tell it to advertise out, looking for backend connections. Listen 127.0.0.1:6666 Order deny,allow Deny from all Allow from 127.0.0. KeepAliveTimeout 60 MaxKeepAliveRequests 0 ManagerBalancerName mycluster ServerAdvertise On We do one more step – that is setup the mod_cluster manager so that we can verify mod_cluster is functioning properly. We do this by adding the following to our httpd.conf: SetHandler mod_cluster-manager Order deny,allow Deny from all Allow from 127.0.0.1 The above section simply restricts access to the mod_cluster-manager URI to only come from localhost. It defers handling of the requests to the mod_cluster_manager module. No other httpd configuration is necessary. Remember – mod_cluster dynamically (via the advertise channel) finds JBoss application servers as well as their context. Next, we need to make some changes to our JBoss application server instances. These changes are necessary to that the instances know to broadcast to mod_cluster. The changes are relatively simple and are easily repeatable. A best practice for dynamically adding instances to a cluster and having it picked up by mod_cluster would be to simply have these changes as part of your core JBoss instance that you create (copy) others from.