Not that critical, especially at the OS level.

Building the connector from source is fairly easy.  Assuming a GNU build
environment (check my Solaris HOWTO for details, linked off the same URL),
building mod_jk is:

Localhost #: ./configure --with-apxs=/some/path/to/apache/bin/apxs
--with-java=${JAVA_HOME}

Localhost #: make
Localhost #: make install

There should be a mod_jk.so file on your system at that point.  Then you are
good to go.  My RH and Solaris HOWTOs all detail how to build the connector.

John


-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 11, 2002 4:19 PM
To: Tomcat Users List
Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3

John:

Thanks, I'll try it.  

But, your website matrix of connectors/OSs/server versions just misses 
my setup on each detail---I'm running Apache 1.3.27 and Tomcat 4.1.12 on 
Red Hat Linux 7.1; your matrix shows Apache 1.3.26, Tomcat 4.1.10, 
RHLinux 7.2.  

How critical are version numbers?

Jerry

Turner, John wrote:

>Mod_webapp is deprecated, and has some fairly serious limitations.
>
>JK/JK2 is the better choice if you are concerned with future growth.
>
>If you're having problems, perhaps my HOWTOs will help:
>
>http://www.johnturner.com/howto
>
>John
>
>-----Original Message-----
>From: Jerry Ford [mailto:[EMAIL PROTECTED]] 
>Sent: Wednesday, December 11, 2002 3:15 PM
>To: Tomcat Users List
>Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3
>
>Denise:
>
>I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work.
>
>Answers to your questions are yes, and yes.  You need a connector 
>between them, and mod_jk.so is one such connector.
>
>However, I had a devil of a time locating any connector on the 
>apache.org website, and I never was able to make mod_jk work (I tried 
>using the version that did work with my Tomcat 3.2 installation, but it 
>did not work with 4.1 and I was not able to locate mod_jk---any 
>version---on the apache website in order to rebuild).
>
>I ended up using mod_webapp.so, which is another connector.
>
>It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which 
>you can download from 
>http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ 
>(the same directory as tomcat itself).
>
>When you unpack it, look for README.txt in the webapp directory. It will 
>tell you how to build the connector from CVS.  Follow the directions in 
>the readme.  They're clear, straightforward, and the build process was 
>smooth and routine, for me at least.  
>
>Jerry
>
> 
><http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ja
k
>arta-tomcat-connectors-4.1.12-src.tar.gz>
>
>
>
>Denise Mangano wrote:
>
>  
>
>>Hi all,
>>
>>I am fairly new to using Apache / Tomcat. I currently have my website set
>>    
>>
>up
>  
>
>>in Apache, running in the /var/html directory. I have installed Tomcat
>>because I have a form page (HTML) that I want to run a servlet with to
>>process a credit card payment with an outside payment processor. I have
>>    
>>
>seen
>  
>
>>some instances that people have stated I have to do some special
>>configuration in order to use both Apache and Tomcat together. Is this so?
>>If so, then are there any good resources for this?
>>
>>Perhaps using JSP for the form will be better because I want a custom page
>>to display depending on what error message will come back from the payment
>>engine.  If that is the case then wouldn't I need the connection between
>>Apache and Tomcat? (the images I will need for the JSP page is stored in
>>apache web directory as well).  Is this the mod_jk plug in? (I am running
>>RedHat Linux 7.3)
>>
>>Thanks in advance!
>>
>>Denise Mangano
>>Help Desk Analyst
>>Complus Data Innovations, Inc.
>>
>>
>>--
>>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]>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
> 
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
> 
>
>--
>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]>

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

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

Reply via email to