![]() ![]() It is pretty painless to configure if you follow the docs, so I am not sure what you mean by "too complex" for your deployment - if you want Apache and have Tomcat already, it would seem only a matter of slight config changes to get mod_jk downloaded and installed.You will complete the steps below as necessary for your requirements for each environment: development, content management, and delivery. Mod_jk will simplify deployment and increase performance for placing Tomcat into an Apache server config. You could also proxy incoming requests via a CGI mechanism similarly, from Apache to Tomcat. this is a slower option performance-wise, as it adds slight overhead on everything you server up. you could achieve this type of forwarding through mod_rewrite. If you would like to serve up your Tomcat servlets under Apache, you could configure apache to forward a class of URIs to your tomcat server instances. Apache does this quite well, and the plugin you mention probably relies on this type of setup (everything gets wired through Apache) for its features/capabilities, based on your brief description of it. Typically, you have one outside facing server that shepherds everything through it. Having multiple web servers fielding independent requests is not recommended, especially if you want to use server-based authentication along with Apache. If you serve the JSP/servlets off of port 8080 and have it do things standalone, on the same host machine that Apache is running on, this can allow you to have them loosely coupled. It sounds like you may be currently running your Tomcat instance standalone. It can be hosted under Apache or IIS or quite a number of other external facing web servers. And you guessed it probably already, you can use HTTPD as a static content server for Geronimo as well. ![]() choose to embed Tomcat inside Geronimo to handle requests for JSP's and servlets where Geronimo does the more enterprisy stuff (LDAP, Messaging etc.). there is also a project called Geronimo which is a Java Enterprise server (J2EE). Tomcat will process the request and will hand the output back to HTTPD which in turn will send it to the client.Īpache has many interesting projects. Whenever a JSP page is requested, HTTPD will pass the request on to Tomcat. This way you can have HTTPD serve all static content, do URL rewriting and much more fancy stuff that the built in Tomcat web server can't do (or can't do very well). However, you can set up HTTPD and Tomcat so that they work together. Tomcat and HTTPD have nothing to do with each other. This project implements a Java servlet engine to serve JSP pages and servlets. In short the web server is called HTTPD (D as in daemon or Unix process). Many people think that Apache is a web server where in reality it is the name of an organization that has a web server project called " The Apache HTTP Server Project". If you can't do this, then you can't take advantage of Apache's plug-ins. The best solution would be to use Tomcat proxied by an Apache server. This makes it the most secure solution, since it is thoroughly tested and any discovered flaw is corrected very quickly. The big advantages of Apache are the numerous plug-ins available, which allows administrators to configure and monitor web sites any way they want and that is the most widespread server available. With this way dynamic content can be generated. Using the appropriate plug-ins, HTTP requests can be redirected to an application server (Tomcat, JBoss, Glassfish) or a script language interpreter (PHP). Secure connections are supported and the performance is also very good (comparable with the performance of HTTP server).Ī plain installation of Apache serves static content. ![]() It can sure serve static content - you can host a web application using only Tomcat. Tomcat is used for hosting Java Web Applications. Tomcat doesn't only serve static content, but it can also serve JSP pages and servlets. On the contrary Tomcat is now completely developed in Java. It is impossible to use a plugin for Apache HTTP server with Tomcat.Īpache HTTP server is developed in C and so are the plug-ins. Apache Tomcat and Apache HTTP are completely different server technologies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |