|
Hi,
Yes,
I've been meaning to post these for some time now. This setup seems to be
working out for us. If anyone has anything to add or modify here to make
it better - great! I cut and pasted this from our internal wiki - it looks
fine in my email client here but if it doesn't come across clear, let me know
and I'll reformat into something more standard.
Jason
Apache 2.0 +
JBoss 3.2.1 w/ Tomcat bundle Guide
A lot of my notes came (almost verbatim) from Jon Barnett's technote: http://www.amitysolutions.com.au/documents/JK2-technote.pdf (which doesn't seem to be there right now -- :(
Getting sources and buildingThis guide will show how to build all these packages from source distributions. If you find a binary file for the system you are interested in deploying on, great. But, be aware that some packages (especially the mod_jk packages) will require Apache and Tomcat source trees. Downloading All packages are assumed being placed into /usr/local/src Apache 2.0.x can be obtained from http://apache.mirror.digitalspace.net/httpd/ I am using Apache 2.0.47 in this guide. mod_jk2 can be obtained from http://apache.mirror.digitalspace.net/jakarta/tomcat-connectors/jk2/ I am using mod_jk2 2.0.2 in this guide. JBoss can be obtained from http://www.jboss.org/index.html?module=html&op=userdisplay&id=downloads I am using jboss 3.2.1 with Tomcat 4.1.24 integrated. (Starting with jboss 3.2.2, tomcat is part of the standard download.) Tomcat can be obtained from http://apache.mirror.digitalspace.net/jakarta/tomcat-4/ I am using tomcat 4.1.27 in this guide. Separate tomcat source tree is only necessary for mod_jk2 build. This instance of tomcat will not need to be built. Building Apache 2.0
If you want more details than this, consult the INSTALL file in the apache distribution. mod_jk2
JBoss
ConfiguringThe bundled tomcat is already setup to support AJP connections on port 8009 by default. We just need to tell Apache how to connect. We first need a workers2.properties file.
Running and TestingJBoss must be started first, followed by Apache
You should now be able to point your browser to the server (http://localhost/) and see the welcome Apache page. Click on the "documentation" link and you should see the Apache manual. This confirms that Apache is installed properly and running. Let's try accessing the JMX console. Point your browser to http://localhost/jmx-console/. You should see the JBoss JMX console. If not, you need to troubleshoot. If you are getting a "404 - File not found" from Apache, then either you mistyped the webapp name in the workers2.properties file or you misspelled or misplaced the "workers2.properties" file and apache cannot find it. Check the error_log in /usr/local/apache2/logs/error_log.
DeployingAfter all is well, you may want to deploy your webapp. You need to do two things:
|
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
