On Wed, 30 Oct 2002, Wendy Smoak wrote: > We've currently got Apache running on HP-UX 11. Now I'm developing > a Struts webapp that will need to go on the same box. HP hasn't > released Tomcat 4 yet, so we'll have to get it to work ourselves. > > Since the Struts app has no static content, is there any reason to > put ourselves through the pain of convincing Apache and Tomcat to > play nicely together? Or can the two run on the same machine with > no knowledge of one another? > > The only disadvantage I see is that my Tomcat URL's will have to > include a port number, since Apache is already listening on port 80. > > Anything else I should know?
Sounds like you've got a handle on it, and yes, you can very well run both Tomcat standalone and Apache independently on a machine. This has come up before on the list (especially regarding the pros/cons of running Tomcat standalone vs. integrated with Apache). It may not be a consensus, but there is a good strong core feeling here that running Tomcat standalone is a very good option, and perhaps even is worth trying first to see how it works for you. If you stay on this list awhile, you'll see that the most common problems brought up here have to do with integrating Tomcat and Apache, so if you can avoid that, you're a step ahead :-). Also, while there are many advantages to running Tomcat integrated with Apache, performance on dynamic content is not one of them, so if you have mostly/all dynamic content, you'll likely get better performance with Tomcat standalone. Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
