RE: Migration from Tomcat 4.1 to 6.0

[Jorge Medina <jm...@e-dialog.com>]

http://httpd.apache.org/docs/2.2/

Read "Compiling and Installing" section
You will need to undertand the modules and directives of several
modules.

You will find in the Apache site instructions for mod_proxy, but if you
decide mod_jk then here are the instructions

http://tomcat.apache.org/connectors-doc/webserver_howto/apache.html


http://www.linuxjournal.com/article/8561


"Can you please provide me step by step instruction..."

Don't expect the people in the list to do your work.  
Research, read, experiment! Then come back with specific questions.

-Jorge

-----Original Message-----
From: Rashid Malik [mailto:rmalik@dhmh.state.md.us] 
Sent: Wednesday, April 08, 2009 10:48 AM
To: Tomcat Users List
Subject: Re: Migration from Tomcat 4.1 to 6.0 <<<Urgent>>>

Chris/Chuck,

You are probably right about httpd.  Please see the attached images for
details.  The reason why I thought I had a 2.2 application is because
whenever I shutdown the 2.2 service, the main web site running on port
80 would not launch.  Please excuse my naiveness about our
configuration.  I just recently inherited this system and was not
provide any documentation.. so I am trying to figure it all out.
Anyway, I only need to keep the tomcat 6.0 version of the tomcat.  Can
you please explain how I should configure httpd to work with the tomcat
6.0 version of the application, not 4.1.  Chris provided me with the
following instructions.  It seems like I have to use mod_proxy_http or
mod_proxy_ajp.  Can you please provide me step by step instruction on
how I should change my existing configuration to work with the newer
application?  Thank you so so much.  God Bless...


Rashid,

On 4/7/2009 5:08 PM, Rashid Malik wrote:
> Hi, I changed port 8080 to 80 and I get page not found error.  Please 
> note that I have another website that is running on an older version 
> of tomcat.

Aah, you didn't mention that.

Only one process may bind to a particular interface/port combination. In
your case, port 80 is already taken (by Tomcat 4.1). If you want both
Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put
another piece of software out in front in order to play traffic cop and
properly route the requests to the appropriate server (app on TC4.1
versus app on TC6.0).

Apache httpd is a popular choice for accomplishing this.

You will have to:

1. Change Tomcat 4.1's configuration so that the HTTP port is
   something /other/ than port 80 (8080 is a popular choice) 2. Change
Tomcat 6.0's configuration so that the HTTP port is
   something /other/ than port 80 and 8080 (8081?) 3. Install Apache
httpd and have it listen on port 80 4. Configure httpd to send the
appropriate requests to the
   appropriate back-end server

To accomplish #4, you will need to use either mod_proxy_http,
mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a
separate download).

There is a lot of documentation for using mod_jk here:
http://tomcat.apache.org/connectors-doc/ 

If you use mod_proxy_http, you'll need to do:

ProxyPass /appA http://localhost:8080/appA ProxyPass /appB
http://localhost:8081/appB 

That should be enough to get you started.

- -chris


>>> Christopher Schultz <ch...@christopherschultz.net> 4/7/2009 6:03:42 
>>> pm >>>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rashid,

On 4/7/2009 5:45 PM, Rashid Malik wrote:
> What I mean here is that I have three 3 installations of tomcat not 2.

How many total web applications do you have?

Do any of them have any requirements for which Tomcat version on which
they are running?

It sounds like the answer is "I have 3 webapps and at least one of them
requires Tomcat 6.0". If there are no other constraints, then just move
all your webapps to Tomcat 6.0, uninstall Tomcat 4.1, and change Tomcat
6.0's <Connector> to port="80" as I said previously.

> There is tomcat 2.2 application (using port 80)

As Chuck suggests, that is probably Apache httpd, which might actually
make things easier. If this is the case, you have not correctly
configured httpd to support your new application. Go into httpd's
configuration and find out where your other application is configured.
Read and /understand/ the configuration before you start changing
things. Reading that configuration plus the config reference I already
posted should clear a lot of things up.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 

iEYEARECAAYFAknbzb4ACgkQ9CaO5/Lv0PCgngCeJLFU7QsoPwisTu7EVwvLHJ+g
3aEAoKgI0amw4JfW1BU0+5fbmG1rRO4G
=1bQY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org