In this application, Tomcat is the sole server running on the machine. I have Apache running on another machine to serve basic web pages, but the two are not connected at all. The Apache/web/server listens on port 80, while the Tomcat/servlet/server listens on 443 (https). That separation keeps things clean and simple.
I went this route about 2 years ago after load testing showed the Apache server was using significant CPU cycles (when both were on the same machine).
So, whether for good or bad, Tomcat is solely responsible for it's "fate".
Cheers,
-Richard
I am by no means a network configuration specialist, so take what I say with
a grain of salt :)
You havn't mentioned how Tomcat is accessed from the internet, such as do you have a Apache or IIS, server acting as a proxy/redirector to tomcat, or whether tomcat itself is internet facing. If you have a separate web server infront of tomcat, then the web server only needs to be configured with the URI's to pass through to tomcat for your web application AND NOT specify those URIs for the manager app. That way you can access the manager app from the internal network by directly going to tomcat, but the external internet users will never be able to access it, because no path exists to it for them.
If however you tomcat is internet facing (not an option I would recommend)
then I wouldn't know how you should properly deal with that. At least have a
good password :)
Regards, Shane
-----Orig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
