- server.xml configures Tomcat.

- mod_jk.conf-auto is created by Tomcat based on your 
  server.xml configuration and can be included in Apache's
  httpd.conf.

        or

- My preferred way is to put all of the mod_jk directives in 
  httpd.conf myself and maintain them manually...no surprises, 
  but others have luck with the automated method.

- workers.properties is used by mod_jk to figure out how to 
   connect to Tomcat (IP address, port number, load balancing, 
   etc.).  If everything's on the same machine, the default file 
   is fine.  You can use ajp12 or ajp13 workers by those names
   from the default settings.

- uriworkermap.properties is IIS/ISAPI only...I think.  No need to 
  worry about it.

The only other file I've had to mess with is tomcat-users.xml to set 
up authentication through Tomcat on one site where a webapp 
relied on it.  Otherwise, I just stick to Apache's security.

Hope that helps.

Best Regards,

Jason Koeninger
J&J Computer Consulting
http://www.jjcc.com


On Mon, 02 Jul 2001 19:26:59 -0600, Joseph A. Noble wrote:

>
>to get Tomcat (3.2.2) and Apache (1.3.20) working on Win98SE, WinNT, and Solaris
>2.7 machines nothing I change other than replacing mod_jk.conf-auto seems to
>change anything.  Can someone explain what files impact the Apache/Tomcat
>configuration or what they do?  Here's the list of files in the conf directory:
>
>build.xml
>iis_redirect.reg-auto
>jni_server.xml
>jni_workers.properties
>manifest.servlet
>mod_jk.conf
>mod_jk.conf-auto
>obj.conf
>obj.conf-auto
>server.xml
>test-tomcat.xml
>tomcat-apache.conf
>tomcat-users.xml
>tomcat.conf
>tomcat.policy
>tomcat.properties
>uriworkermap.properties
>uriworkermap.properties-auto
>web.dtd
>web.xml
>workers.properties
>wrapper.properties
>
>I'm assuming I can ignore all the IIS files, but I'm beginning to even doubt
>that.  If someone could just tell me which files are involved, and in what
>hierarchy or sequence they are used I could proceed on my own.  It seems like
>nothing I change, like trying to use ajp13 instead of ajp12 works. Which of the
>above files impact my configuration and which can I ignore?  Any documentation
>project should outline what the files are for and what they do.
>
>The cause of my frustration is that we (I) convinced our customer that we didn't
>need or want to use Oracle 9iAS Application Server, after 6 months of using it,
>and to use Apache/Tomcat instead.  Since they were convinced, I've run into
>nothing but frustrations trying to get Tomcat/Apache to work together.  I've
>posted three previous messages to the list, including the one below, and
>received no response.
>
>HELP!!!
>-joe-
>
>"Joseph A. Noble" wrote:
>> 
>> Hi,
>> 
>> I'm trying to get Apache (1.3.20) and Tomcat (3.2.2) to recognize
>> "similar" URL's.  By this I mean, get rid of the /servlet in the
>> Apache mapping.  The only way I've found to do this is to copy mod_jk.
>> conf-auto to another file, I called it my_mod_jk.conf and change
>> the JkMount lines.
>> For example, I changed:
>> 
>>    JkMount /admin/servlet/* ajp12
>>    JkMount /admin/*.jsp ajp12
>> 
>> to:
>>    JkMount /admin/* ajp13
>> 
>> It works fine, except everything in the admin directory, even the
>> html is served by Tomcat I believe.  Is there a better way?  What's
>> the purpose of Apache in this case, unless I use unique subdirectories
>> for static html files? Or is Apache picking up the html files?  How
>> can I tell which one serves the html files with the /admin/* mapping?
>> 
>> Also, although I configured Tomcat's server.xml to recognize Ajpv13,
>> I noticed it was still using Ajpv12.  Why?
>> 
>> Any help would be much appreciated.
>> 
>> THANKS
>> -joe-



Reply via email to