Install and Configure the JBoss HTTP Connector on a JBoss Enterprise Application Platform Node
Follow this procedure to install the JBoss HTTP Connector on a JBoss Enterprise Application Platform node and configure it for non-clustered operation. Task Prerequisites You must meet the following conditions before continuing with this task: Install a supported JBoss Enterprise Application Platform. Deploy the worker node service Copy mod-cluster.sar from the JBOSS_EAP_DIST/mod_cluster directory to jboss-as/server/PROFILE/deploy. Add a Listener to JBoss Web Add the following Listener element beneath the other Listeners in JBOSS_EAP_DIST/jboss-as/server/PROFILE/deploy/jbossweb.sar/server.xml: Configure the service dependency Add the following depends element beneath the other depends elements in JBOSS_EAP_DIST/jboss-as/server/PROFILE/deploy/jbossweb.sar/META-INF/jboss-beans.xml: ModClusterService Give the worker a unique identity Edit the file JBOSS_EAP_DIST/jboss-as/server/PROFILE/deploy/jbossweb.sar/server.xml and add a jvmRoute attribute and value to the Engine element, as shown: Use a unique jvmRoute value for each node. Optional: Configure firewall to receive Proxy Server advertisements A proxy server using the JBoss HTTP Connector can advertise itself via UDP multicast. To enable the worker node to dynamically discover proxy servers, open port 23364 for UDP connections on the worker node's firewall. For example, using the command: /sbin/iptables -I INPUT -p udp -d 224.0.1.0/24 -j ACCEPT -m comment --comment "receive mod_cluster proxy server advertisements". If you are not using Automatic Proxy Discovery (see Automatic Proxy Discovery), configure worker nodes with a static list of proxies. Refer to Section 6.1, “Static Proxy Configuration� for directions. In this case you can safely ignore the following warning message: [warning] mod_advertise: ServerAdvertise Address or Port not defined, Advertise disabled!!!