Melanie wrote:
Thanks Cyrille for the information. This looks like it's a quick fix but
there is still another issue.
The Tomcat Startup Page is now being served, but not the actual springapp
J2EE web application that is located in the Tomcat directory --->
/usr/java/tomcat-5.5/webapps/springapp
Do you know the way to bring up the actual J2EE webpage instead of the
Tomcat Startup Page when the URL
http://www.robotronics.org is served by Apache and Tomcat?
Melanie,
backing up a little bit..
According to your various posts, originally, you have, on the same host :
- an Apache httpd, answering on http://www.robotronics.org (port 80),
which serves html and javascript documents
- a Tomcat engine and an application in it, answering on
http://www.robotronics.org:9080/Robotronics (thus port 9080, and a URI
"/Robotronics"), but this application is located in the directory
/usr/java/tomcat-5.5/webapps/springapp.
and you would apparently like that "everything" would answer to the URL
http://www.robotronics.org (port 80).
That is feasible, but the above is composed of several parts, and there
are several ways to configure the individual parts.
So you have to be a bit systematic in the approach, and do one thing at
a time.
A couple of questions to answer first are :
1) do you want to leave the html and javascript part under the Apache
httpd server, or not ?
2) do you need this Apache httpd server for other things, apart from
this specific case ?
The reason for these questions is that the easiest and simplest setup
would be
- to move the html and javascript part onto the Tomcat server
- to eliminate the Apache httpd server
- to change the Tomcat server so that it responds to port 80 instead of
port 9080
- to change the Tomcat configuration so that your webapp application
becomes the "default" application of Tomcat, and thus answers to the URL
http://www.robotronics.org, without the "/Robotronics" prefix.
But, this simple setup would not be the right one if you want to keep
the front-end Apache httpd, because for example you need it for other
things (other virtual sites, other applications, etc..).
In that case, we would then recommend some form of "proxying" between
Apache httpd and Tomcat. And there are several possibilities there too.
Which is why I mention the need to take this one bit at a time..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
