Can jOAI be configured to run through an Apache web server (httpd)?
Yes. Running jOAI through an Apache web server provides additional functionality that is not available through Tomcat alone. For example, Apache provides robust support for SSL, user authorization and authentication, access control by IP address, virtual host support, web logging, URL redirection, and other functionality. By configuring Tomcat to run through Apache, all of Apache’s functionality becomes available. This may be especially convenient for web administrators who are already familiar with Apache. One of two Apache modules may be used to connect Apache with Tomcat: mod_proxy or mod_jk.
Yes. Running jOAI through an Apache web server provides additional functionality that is not available through Tomcat alone. For example, Apache provides robust support for SSL, user authorization and authentication, access control by IP address, virtual host support, web logging, URL redirection, and other functionality. By configuring Tomcat to run through Apache, all of Apache’s functionality becomes available. This may be especially convenient for web administrators who are already familiar with Apache. To configure jOAI to run with Apache, use the Apache Tomcat Connector (mod_jk) in conjunction with Tomcat. The connector allows rules to be defined that say, for example, ‘for all requests that come to Apache at the web address http://oai.somewhere.edu, forward them to Tomcat installed at http://www.somewhere.edu:8080/oai/’. Information for setting up mod_jk is provided in the Apache Tomcat Connector documentation. A typical configuration scenario would be to use Apache to provide S
