Stephen . wrote:
Hi,
thanks for your response.
However, I would need some more explanation.
Exactly where and how would I implement those "Tomcat Connectors" ?
Apparently, all I have is the Tomcat engine itself. So, what I need is an actual
"Apache" server. (Am I right?)
Another thing : I've had my Tomcat running for a while now. The application
which is running on the server is Sun's Identity Manager (IDM).
If I now place an Apache in front of it, would that, in any way, damage the web
application itself?
Hi Stephen.
Your questions are very wide-ranging, and apparently your knowledge of
this kind of configuration very limited. That makes it hard and
time-consuming to give you a comprehensive answer.
Even pointing you to the corresponding documentation is not going to
help a lot, if you are not willing to spend quite a bit of time on this.
Roughly, the kind of configuration of which it is question here looks
like this :
browser <-> Apache httpd server <- Apache/Tomcat connector -> Tomcat
Apache httpd is a "classic" webserver, serving static content and also
able to run miscellaneous "active content providers" such as programs
written in perl, php, python etc..
Apache Tomcat is a "servlet engine". Its main focus is to be an
environment to run web applications written in Java. But it can also
server as a "generic" webserver and serve static content, in most cases
as fast as Apache httpd. It is less good at running non-Java applications.
The "Apache/Tomcat connector" mentioned above is an add-on module within
Apache httpd, which allows Apache to receive requests from browsers,
examine them, and select some for processing by the back-end Tomcat.
These requests are then forwarded to Tomcat by the Connector, and the
Connector receives the Tomcat response and returns it to Apache httpd,
which returns it to the browser.
Using one such Connector, one can also use one Apache httpd to act as
front-end to several Tomcat back-end servers, for example for
load-balancing.
There are two different types of Apache/Tomcat Connectors : one is
called mod_jk; the other is called mod_prox/mod_proxy_ajp. They have
roughly the same capabilities, but they differ in the setup.
Placing an Apache httpd (with a Connector) in front of a Tomcat will not
"damage" the Tomcat web application in any way, if the configuration is
done correctly.
But this proper configuration can be anything from very simple to quite
complex, depending on what exactly you need to achieve.
So there is no "one size fits all".
What I would recommend if you want to know more about this, is that you
set up Tomcat and Apache httpd on a server (separately), with some
example Tomcat application.
Then come back here to get tips about which documentation to use, and
how to set things up to try this kind of configuration.
That will be better than another 10 pages of written introduction.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
