David Whitehurst wrote:
Chuck:
Could you elaborate on what those parameters would be? A port is just a number. I'm trying to understand the history, but I would appreciate your comments on the other things required to make Tomcat production ready on top of just changing the Coyote connector from 8080 to 80 and 8443 to 443?
The history is relatively clear. Normal Internet ports for HTTP/S are 80 and 443. Since Tomcat is usually running first as a test project on some machine that already has a web server, in order to avoid conflicts or (which may even be worse in test situations) having ot connect Apache and TC, it is most reasonable to shift those ports.
Since TCP:0-1024 is already overbooked with registered services and TCP:1024-x has a lot other registered services, it seamed reasonable to place it at 8000 + 80,443.
As for production, you have several things to consider. Do you want to run TC standalone or behind Apache? Most likely you will not want TC to run as root, so you will have a dedicated account for TC, like "tomcat" or "tomcat4" or "tomcat5". You need to setup file permissions so that TC can access the files it needs.
If it is running standalone, you need to allow TC to bind to ports 80 and 443, something best accomplished via Apache Jakarta-Commons Daemon and JSVC.
If it is running behind Apache, you need to setup a connector, like WARP (mod_webapp - prehestoric, but the ISP I'm working for at this moment uses it), JK2 (good, but abandoned and merged into JK) or JK.
And all of this needs setting up.
Nix.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
