EXCELLENT! Almost there now! Just one more thing. I have it serving to http://proj-name and it is coming up with the tomcat default page. I have to be missing something.
I have: <Engine name="Catalina" defaultHost="proj-name"/> and a <Host> defined as: <Host name="proj-name" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false"> <Alias>proj-name</Alias> </Host> should the appBase be defined as: /webapps/proj-name folder? - Thank you all for partially jump starting my brain. On Wed, Jan 5, 2011 at 4:27 PM, André Warnier <a...@ice-sa.com> wrote: > Josh Gooding wrote: > >> Hey guys and gals, it's been a while, but I have a question for you. I am >> setting up a new Tomcat 6.0.29 installation that is for project management >> software. >> >> Here's the scenario. On this server we are currently running Apache 2.2 >> for >> our companies wiki on port 80. This is bound to a specific IP address and >> we can navigate to 'Wiki' in the address of the web browser and viola, it >> appears. >> >> With that in mind, can I: >> >> Have tomcat serve on port 80 (bound to a different IP address than the >> Apache 2.2 installation) on the same machine, and when 'this-name' is >> entered into the web browser, it will serve it? >> > > Yes, provided : > - the browser, through a query for "this-name" to its name resolution > mechanism (usually DNS), obtains an IP address which actually corresponds to > an interface on the server > - and the tomcat on that server is actually listening on that IP address > > As a general proviso, you cannot have two processes on the same host which > open the same listening port on the same IP address. > > > I am aware that I can > >> forward the tomcat serving through the httpd server, but I am not willing >> to >> (unless it's the only way to do so.) >> >> Would this be in the virtual hosting section of the documentation by >> chance? >> >> > No, because it has essentially nothing to do with "virtual" hosts in the > HTTP sense. > But explaining that would take us much further than needed to answer your > question above and would be quite Off-Topic for this list.(*) > > The scheme you propose above is more similar to the case where you would > actually have two separate physical hosts, one running httpd and the other > running tomcat. > Each would have its own separate IP address, and name. > You are just bringing them together into one machine, and setting up two > network interfaces on that one machine. > > > > (*) read here for more details : > http://httpd.apache.org/docs/2.2/vhosts/ > (The "name-based" part) > > EXCELLENT! Almost there now! Just one more thing. I have it serving to http://proj-name and it is coming up with the tomcat default page. I have to be missing something. I have: <Engine name="Catalina" defaultHost="proj-name"/> and a <Host> defined as: <Host name="proj-name" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false"> <Alias>proj-name</Alias> </Host> should the appBase be defined as: /webapps/proj-name folder? - Thank you all for partially jump starting my brain.