...
For some background on why you'd want to do this, and the principles behind
the configuration, see pages on Securing DSpace and Running DSpace on Standard Ports.
Note: These instructions are for Linux, and may be somewhat specific to Red Hat Enterprise Linux 3.2.3-52 and the following software versions (but hopefully they are still helpful for other distros)
- DSpace 1.3.x and above
- Apache HTTPD 2.0.46
- Tomcat 5.5.9 and above
Anyone who has successfully set up mod_jk
connector under different conditions should feel free to add their notes!
...
Once the mod_jk
connector has been installed, you will have to configure Apache to use this connector to communicate with Tomcat. First, modify the existing workers.properties.minimal
file (should be in /etc/httpd/conf/
, or whereever wherever you copied it to in Step 2 above):
You will need to modify the following Tomcat and Java home directories:
Code Block |
---|
workers.tomcat_home=tomcat workers.java_home=java |
Also add ajp13 to the worker list:
Code Block |
---|
worker.list=ajp13,lb,jk-status |
In addition, you may need to uncomment (and possibly change) the JVM for Unix:
Warning |
---|
For later versions of mod_jk (I installed 1.2.40) worker.iprocess.jvm_lib is deprecated and would throw an warning. I omitted this line with no problems. |
Code Block |
---|
# Unix - Sun VM or blackdown worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)lib$(ps)i386$(ps)server$(ps)libjvm.so |
...
However, the correct path of the libjvm.so
(at least for Red Hat) is java/jre/lib/i386/server/libjvm.so
(i.e. "server/libjvm.so
", not "classic/libjvm.so
")
Step 4 - Configure mod_jk connector
...
Hopefully everything works for you! If it doesn't, ask questions to the dspace-tech@lists.sourceforge.net DSpace-Tech mailing list Mailing Lists. If you find any problems with the above instructions, feel free to edit and enhance them!