tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From john Matlock <johndmatl...@gmail.com>
Subject Re: Moving Tomcat to work externally.
Date Thu, 11 Jul 2013 21:43:22 GMT
You say:

Remove the ROOT directory from Tomcat's webapps directory, replacing it
with your webapp renamed to ROOT.war (or, if it's already an expanded .war
file, put it in the ROOT directory under webapps).

Do I understand that you are telling me to put the whole web application
into the webapps/ROOT directory?  That's a couple of hundred pages and
several sub-directories just for the main application.  And I have to move
another half dozen applications to Tomcat as well.  Further these are
almost all dynamic pages, and I may be incorrect, but I've read that .war
files can only contain static web pages.  These are all in ColdFusion.  Is
my understanding incorrect, and somehow this can connect to Railo to handle
the database interaction?

You then ask:

What URL did you try to use?  -- www.books-on-line.com

Where is the "other machine" located relative to the one Tomcat is running
on? -- I'm in a room with the on-line server, the new server and a half
dozen other machines.  The on-line server is about six and a half inches
from the new server.  I used one of the other machines to browse to
www.books-on-line.com.  It was 8 or ten feet away.

What port is specified in server.xml? -- 80 -- localhost:80 works,
localhost:8080 doesn't.

Is there a firewall blocking that port? -- There's a hole in the firewall
to let page requests through to the on-line server.

Be specific when reporting problems. -- I thought I had been.

Register the DNS name for your server with your DNS providers. -- This site
is about 17 years old with several million home page hits.  I think it is
registered.

I asked and you answered:

Did I do something stupid? -- Not terribly, other than not reading the real
Tomcat doc before making changes. -- I've tried to read the real Tomcat doc
without success.  I've worked in a dozen or so languages, but the Java
world is new to me and it uses a lot of jargon making trying to get
anything out of it very difficult.


On Wed, Jul 10, 2013 at 7:09 PM, Mark Eggers <its_toasted@yahoo.com> wrote:

> On 7/10/2013 6:08 PM, Caldarale, Charles R wrote:
>
>> From: john Matlock [mailto:johndmatlock@gmail.com**] Subject: Moving
>>> Tomcat to work externally.
>>>
>>
>>  Following instructions found in various places I added the
>>> following to the server.xml file and restarted Tomcat:
>>>
>>
>> If you followed something that said to put a <Context> element in
>> server.xml, you need to stop going to those places and read the real
>> Tomcat doc.
>>
>>
> Sadly, the three documents I read concerning Railo and Tomcat all have
> this same exact syntax.
>
> The rest of the instructions concerning integrating Tomcat and Railo are
> pretty much on par with this.
>
>
>  <users@tomcat.apache.org>
>>>
>>
>> The above has no business being anywhere in a config file.
>>
>>  <Host name="books-on-line.com" appBase="webapps"> <Context path'""
>>> docBase="C:\inetpub\wwwroot\" />
>>> <Alias>www.books-on-line.org</**Alias>
>>> <Alias>www.books-on-line.net</**Alias> </Host>
>>>
>>
>> Take out all of the above; none of it is needed or desirable.
>>
>> Remove the ROOT directory from Tomcat's webapps directory, replacing
>> it with your webapp renamed to ROOT.war (or, if it's already an
>> expanded .war file, put it in the ROOT directory under webapps).
>>
>>  Chrome, Firefox and even tried IE from another machine -- all say
>>> they can't connect.
>>>
>>
>> What URL did you try to use?  Where is the "other machine" located
>> relative to the one Tomcat is running on?  What port is specified in
>> server.xml?  Is there a firewall blocking that port?  Be specific
>> when reporting problems.
>>
>>  Tomcat version: Whatever comes with Railo 4
>>>
>>
> It comes with some (undefined) version of Tomcat 7.
>
>
>
>> If you don't know what it is, remove it, and install a real one from
>> tomcat.apache.org; otherwise, you're just shooting in the dark.
>>
>>  Is there something else I'm supposed to do?
>>>
>>
>> Register the DNS name for your server with your DNS providers.
>>
>>  Did I do something stupid?
>>>
>>
>> Not terribly, other than not reading the real Tomcat doc before
>> making changes.
>>
>> - Chuck
>>
>
> In the original author's defense, the railo documentation is . . .
> unpleasant.
>
> Here's what I did to get it running quickly:
>
> 1. Download a copy of Tomcat from tomcat.apache.org
>
> Grab the zip file and unpack it somewhere. Right now you don't need to run
> it as a service, nor do you need to even use the manager application.
>
> 2. Download the WAR file for railo
>
> I believe the current production version is 4.0.4. The WAR file will be
> named railo-4.0.4.001.war
>
> 3. Copy it as railo.war to the webapps directory
>
> You'll find that directory in apache-tomcat-7.0.42\webapps, wherever
> you've unpacked the zip file.
>
> 4. Double-click on startup.bat
>
> You'll find that in apache-tomcat-7.0.42\bin, wherever you've unpacked the
> zip file.
>
> 5. Browse to localhost:8080/railo and confirm that it works.
>
> 6. Remote machine access
>
> Now, either update DNS to point to your machine as books-on-line.com, or
> go and edit a remote machine's host file to have books-on-line.com with
> your IP address.
>
> Make sure your machine's firewall allows port 8080.
>
> Now browse to books-on-line.com:8080/railo and make sure you can connect.
>
> Now to make the Railo environment the default application:
> ------------------------------**----------------------------
>
> 1. Stop Tomcat
>
> Double-click on shutdown.bat found in apache-tomcat-7.0.42\bin, wherever
> you've unpacked the Tomcat zip file.
>
> 2. Back up Tomcat's original ROOT application
>
> It's found in apache-tomcat-7.0.42\webapps, wherever you've unpacked the
> Tomcat zip file.
>
> 3. Rename railo.war to ROOT.war
>
> Please note that case is important, even on Windows
>
> 4. Delete the railo directory that was created
>
> It's found in apache-tomcat-7.0.42\webapps, wherever you've unpacked the
> Tomcat zip file.
>
> 5. Start up Tomcat
>
> 6. Browse to localhost:8080/
>
> You should see the railo application
>
> 7. From a remote machine, browse to books-on-line.com:8080
>
> You should see the railo application
>
> Added Feature 1 - Run on Port 80
> ------------------------------**--
>
> 1. Stop Tomcat
>
> Double-click on shutdown.bat found in apache-tomcat-7.0.42\bin, wherever
> you've unpacked the Tomcat zip file.
>
> 2. Edit server.xml - changing port 8080 to port 80
>
> The file is found in apache-tomcat-7.0.42\conf, wherever you've unpacked
> the Tomcat zip file
>
> You're looking for the following entry to change:
>
>     <Connector port="8080" protocol="HTTP/1.1"
>                connectionTimeout="20000"
>                redirectPort="8443" />
>
> 3. Make sure port 80 is not being used
>
> This is usually means that IIS or Apache HTTPD is running. Stop them. You
> can open up a cmd.exe and type the following:
>
> netstat -ano
>
> This will list all of the ports, and the process ID accessing the ports.
> If there's 0.0.0.0:80 or [::]:80, find the process and stop it.
>
> 4. Start up Tomcat
>
> 5. Browse to localhost/
>
> You should see the railo application
>
> 6. From a remote machine, browse to books-on-line.com
>
> You should see the railo application
>
> Added Feature 2 - Run as a service
> ------------------------------**----
>
> Repeat the above exercise, with the following exceptions.
>
> 1. Install the service
>
> Install the service in a path with no spaces. Tomcat is fine with spaces,
> some less well-behaved applications may not be.
>
> I usually put the service in C:\ASF\apache-tomcat-x.y.z to mimic the zip
> style of naming
>
> Give the Tomcat service a name rather than taking the default name.
>
> I usually append the version numbers to it - for example Tomcat742.
>
> 2. Proceed stepwise as above.
>
> You'll use the Tomcat Monitor application to start and stop Tomcat instead
> of the .bat files
>
> Added Feature 3 - Production Environment
> ------------------------------**----------
>
> 1. Remove examples and docs apps from default Tomcat install
> 2. Manager application
>    a. easiest is to remove
>    b. can configure it to only accept connections from localhost
>    c. discussion of option b is left for another message
>
> I think that's about it
>
> . . . . just my two cents (and dinner entertainment)
> /mde/
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org<users-unsubscribe@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message