Using Apache/IIS with LAMS (mod_jk)

Most production installations of LAMS have a webserver "in front" of JBOSS.

A step by step guide to setting up LAMS with Apache was written for LAMS 1.0.2. Most of the information will still apply although Step 7 is now a bit different. New instructions for Step 7 are given below. Some of the parameters in workers.properties may be outdated.

If you follow the instructions and find there are any other changes that need to be made, please let Fiona Malikoff know so she can add them here. Eventually the instructions from the old page will migrate to this page.

There is also mod_proxy_ajp that you can use with Apache 2.2 and it is supposed to be easier to set up,  but we don't have any instructions for that yet.

If you are still having problems, there is also a page on the JBOSS wiki that may help, or it might confuse matters even more!

Step #7: Configure Tomcat with JBOSS

To complete the configuration, we also need to name each node accordingly to the names specified in workers.properties.

Edit JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml

You may need to locate the <Engine...> element and add an attribute jvmRoute. We have found that we don't need to define the jvmRoute - it works as long as JBOSS and Apache both know to use the same port for communication (8009). If you do need to set the jvmRoute attribute then it must match the name specified in workers.properties.