RE: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache Server?)

2002-10-11 Thread Turner, John


I'm sure the developers would appreciate a patch if you don't think the
default server.xml is setup appropriately.  It doesn't matter to me one way
or the other...I just comment out the connectors I'm not using.

John

 -Original Message-
 From: Mark R. Diggory [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, October 10, 2002 6:13 PM
 To: Tomcat Users List
 Subject: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache
 Server?)
 
 
 Hi all,
 
 This is a little confusing, I notice that in 4.1's server.xml file it 
 still has the WARP connector as the default example of 
 connecting up 
 to apache. If what you say is the case, should this be mod_jk 
 instead? 
 i.e. Shouldn't this be a more appropriate connector example 
 that works 
 on both Windows and other platforms, expecially if mod_webapp is dead?
 
 Cheers,
 -Mark
 
   !-- The MOD_WEBAPP connector is used to connect Apache 
 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt 
 file coming with
the WebApp Module distribution on how to build it.
(Or check out the jakarta-tomcat-connectors/webapp 
 CVS repository)
 
To configure the Apache side, you must ensure that 
 you have the
ServerName and Port directives defined in 
 httpd.conf.  Then,
lines like these to the bottom of your httpd.conf file:
 
  LoadModule webapp_module libexec/mod_webapp.so
  WebAppConnection warpConnection warp localhost:8008
  WebAppDeploy examples warpConnection /examples/
 
The next time you restart Apache (after restarting 
 Tomcat, if needed)
the connection will be established, and all 
 applications you make
visible via WebAppDeploy directives can be accessed 
 through Apache.
   --
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




TOMCAT-STANDALONE needed with Apache Server?

2002-10-10 Thread Chris Wolcott

I'm new to the world of Apache and Jakarta. I notice TOMCAT by default 
has the TOMCAT-STANDALONE instance defined by default, and the 
TOMCAT-APACHE instance commented out with no connectors, etc defined. I 
loaded Apache 2.0 and TOMCAT 4.0 on my Win 2K Svr box. Do I NEED the 
stand-alone instance of TOMCAT? Do I need all those connectors on the 
different ports? What is used by the mod_jk interface from Apache to 
TOMCAT? I tried mod_webapp, but Apache said it could not find it even 
though I DL'd a win32 version of the .so and accompanying libapr.dll to 
the MODULES directory. (I went back to the mod_jk method)

I have read multiple pages on setting up TOMCAT, and all seem to be 
different or not appropriate for my needs. Anyone have a good page to 
help me setup Apache/Tomcat and JSP/SERVLETS/BEANS on a WINDOWS 2000 SERVER?

Thanks


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: TOMCAT-STANDALONE needed with Apache Server?

2002-10-10 Thread Turner, John


First, you don't need Apache.  Tomcat works just fine in stand-alone mode.
Don't bother with Apache and connectors unless you absolutely need it, or
have aversions to running Tomcat on port 80.

Second, stay away from mod_webapp (WARP).  AFAIK, it isn't active anymore,
and it wasn't finished when the activity stopped anyway.  The current stable
connector is mod_jk (JK/AJP13).  Also available is mod_jk2 (JK2), but that
has been designated as beta by the team.  Choose the one you want to use.

Third, there are several HOWTOs for Windows and other platforms, like this
one from Robert Sowders using JK2:
ftp://pokey.wr.usgs.gov/pub/rsowders/Apache2_Jk2_TC4.1.x_JSDK1.4.zip

Search the archives for others.

If you choose to use Tomcat in stand-alone, you don't need any of the other
connectors enabled in server.xml.  Conversely, if you do decide to go the
Apache + connector route, you don't need the stand-alone connector enabled
in server.xml.  Just comment out the connectors you don't need and restart
Tomcat.

The default connector for JK is port 8009, I believe.

John


 -Original Message-
 From: Chris Wolcott [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, October 10, 2002 11:50 AM
 To: Tomcat Users List
 Subject: TOMCAT-STANDALONE needed with Apache Server?
 
 
 I'm new to the world of Apache and Jakarta. I notice TOMCAT 
 by default 
 has the TOMCAT-STANDALONE instance defined by default, and the 
 TOMCAT-APACHE instance commented out with no connectors, etc 
 defined. I 
 loaded Apache 2.0 and TOMCAT 4.0 on my Win 2K Svr box. Do I NEED the 
 stand-alone instance of TOMCAT? Do I need all those connectors on the 
 different ports? What is used by the mod_jk interface from Apache to 
 TOMCAT? I tried mod_webapp, but Apache said it could not find it even 
 though I DL'd a win32 version of the .so and accompanying 
 libapr.dll to 
 the MODULES directory. (I went back to the mod_jk method)
 
 I have read multiple pages on setting up TOMCAT, and all seem to be 
 different or not appropriate for my needs. Anyone have a good page to 
 help me setup Apache/Tomcat and JSP/SERVLETS/BEANS on a 
 WINDOWS 2000 SERVER?
 
 Thanks
 
 
 --
 To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: 
 mailto:[EMAIL PROTECTED]
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache Server?)

2002-10-10 Thread Mark R. Diggory

Hi all,

This is a little confusing, I notice that in 4.1's server.xml file it 
still has the WARP connector as the default example of connecting up 
to apache. If what you say is the case, should this be mod_jk instead? 
i.e. Shouldn't this be a more appropriate connector example that works 
on both Windows and other platforms, expecially if mod_webapp is dead?

Cheers,
-Mark

  !-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
   as its servlet container. Please read the README.txt file coming with
   the WebApp Module distribution on how to build it.
   (Or check out the jakarta-tomcat-connectors/webapp CVS repository)

   To configure the Apache side, you must ensure that you have the
   ServerName and Port directives defined in httpd.conf.  Then,
   lines like these to the bottom of your httpd.conf file:

 LoadModule webapp_module libexec/mod_webapp.so
 WebAppConnection warpConnection warp localhost:8008
 WebAppDeploy examples warpConnection /examples/

   The next time you restart Apache (after restarting Tomcat, if needed)
   the connection will be established, and all applications you make
   visible via WebAppDeploy directives can be accessed through Apache.
  --

  !-- Define an Apache-Connector Service --
!--
  Service name=Tomcat-Apache

Connector className=org.apache.catalina.connector.warp.WarpConnector
 port=8008 minProcessors=5 maxProcessors=75
 enableLookups=true appBase=webapps
 acceptCount=10 debug=0/

Engine className=org.apache.catalina.connector.warp.WarpEngine
 name=Apache debug=0

  Logger className=org.apache.catalina.logger.FileLogger
  prefix=apache_log. suffix=.txt
  timestamp=true/

  Realm className=org.apache.catalina.realm.MemoryRealm /

/Engine

  /Service




Turner, John wrote:

First, you don't need Apache.  Tomcat works just fine in stand-alone mode.
Don't bother with Apache and connectors unless you absolutely need it, or
have aversions to running Tomcat on port 80.

Second, stay away from mod_webapp (WARP).  AFAIK, it isn't active anymore,
and it wasn't finished when the activity stopped anyway.  The current stable
connector is mod_jk (JK/AJP13).  Also available is mod_jk2 (JK2), but that
has been designated as beta by the team.  Choose the one you want to use.

Third, there are several HOWTOs for Windows and other platforms, like this
one from Robert Sowders using JK2:
ftp://pokey.wr.usgs.gov/pub/rsowders/Apache2_Jk2_TC4.1.x_JSDK1.4.zip

Search the archives for others.

If you choose to use Tomcat in stand-alone, you don't need any of the other
connectors enabled in server.xml.  Conversely, if you do decide to go the
Apache + connector route, you don't need the stand-alone connector enabled
in server.xml.  Just comment out the connectors you don't need and restart
Tomcat.

The default connector for JK is port 8009, I believe.

John


  

-Original Message-
From: Chris Wolcott [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 11:50 AM
To: Tomcat Users List
Subject: TOMCAT-STANDALONE needed with Apache Server?


I'm new to the world of Apache and Jakarta. I notice TOMCAT 
by default 
has the TOMCAT-STANDALONE instance defined by default, and the 
TOMCAT-APACHE instance commented out with no connectors, etc 
defined. I 
loaded Apache 2.0 and TOMCAT 4.0 on my Win 2K Svr box. Do I NEED the 
stand-alone instance of TOMCAT? Do I need all those connectors on the 
different ports? What is used by the mod_jk interface from Apache to 
TOMCAT? I tried mod_webapp, but Apache said it could not find it even 
though I DL'd a win32 version of the .so and accompanying 
libapr.dll to 
the MODULES directory. (I went back to the mod_jk method)

I have read multiple pages on setting up TOMCAT, and all seem to be 
different or not appropriate for my needs. Anyone have a good page to 
help me setup Apache/Tomcat and JSP/SERVLETS/BEANS on a 
WINDOWS 2000 SERVER?

Thanks


--
To unsubscribe, e-mail:   
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: 
mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

  






--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache Server?)

2002-10-10 Thread Craig R. McClanahan



On Thu, 10 Oct 2002, Mark R. Diggory wrote:

 Date: Thu, 10 Oct 2002 18:13:17 -0400
 From: Mark R. Diggory [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: Tomcat Users List [EMAIL PROTECTED]
 Subject: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache
 Server?)

 Hi all,

 This is a little confusing, I notice that in 4.1's server.xml file it
 still has the WARP connector as the default example of connecting up
 to apache. If what you say is the case, should this be mod_jk instead?
 i.e. Shouldn't this be a more appropriate connector example that works
 on both Windows and other platforms, expecially if mod_webapp is dead?

There is also a mod_jk connector in the default configuration (on port
8009).  The difference is that jk doesn't require a custom
service/engine/context hierarchy -- it uses the standard one.


 Cheers,
 -Mark

Craig


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache Server?)

2002-10-10 Thread Gary Henson

By default, the WARP connector, and Tomcat-Apache service are commented
out.

They are included as examples if you want to use them, but the default
connector is the Coyote/JK2 connector.

My suggestion would be to use JK or JK2 to connect Apache and Tomcat. It
is
a reasonably well documented process (compared to other connectors) and
there are a lot of examples available.

The other easy alternative is to change the connector for HTTP/1.1 from 
port 8080 to port 80, and only use Tomcat.

-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] 
Sent: Friday, 11 October 2002 11:24
To: Tomcat Users List
Subject: Re: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache
Server?)




On Thu, 10 Oct 2002, Mark R. Diggory wrote:

 Date: Thu, 10 Oct 2002 18:13:17 -0400
 From: Mark R. Diggory [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: Tomcat Users List [EMAIL PROTECTED]
 Subject: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache
 Server?)

 Hi all,

 This is a little confusing, I notice that in 4.1's server.xml file it
 still has the WARP connector as the default example of connecting up
 to apache. If what you say is the case, should this be mod_jk instead?
 i.e. Shouldn't this be a more appropriate connector example that works
 on both Windows and other platforms, expecially if mod_webapp is dead?

There is also a mod_jk connector in the default configuration (on port
8009).  The difference is that jk doesn't require a custom
service/engine/context hierarchy -- it uses the standard one.


 Cheers,
 -Mark

Craig


--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]