tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lar...@locus.apache.org
Subject cvs commit: jakarta-tomcat/src/doc Tomcat-Workers-HowTo.html tomcat-netscape-howto.html tomcat-iis-howto.html NT-Service-howto.html in-process-howto.html
Date Mon, 16 Oct 2000 02:20:13 GMT
larryi      00/10/15 19:20:11

  Modified:    src/doc  Tag: tomcat_32 Tomcat-Workers-HowTo.html
                        tomcat-netscape-howto.html tomcat-iis-howto.html
                        NT-Service-howto.html in-process-howto.html
  Log:
  Update to identify web site as the dowload location for connectors, etc.
  Remove mention of connectors being part of the source distribution.
  
  Updated JDK and Tomcat default locations.  Now assumes JDK is installed
  at its default location, for example c:\jdk1.2.2, and Tomcat binary distribution
  is unzipped to the root of the same drive, i.e. c:\jakarta-tomcat.
  
  Other miscellaneous corrections.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.2   +10 -7     jakarta-tomcat/src/doc/Tomcat-Workers-HowTo.html
  
  Index: Tomcat-Workers-HowTo.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/Tomcat-Workers-HowTo.html,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- Tomcat-Workers-HowTo.html	2000/09/04 21:10:01	1.1.2.1
  +++ Tomcat-Workers-HowTo.html	2000/10/16 02:20:06	1.1.2.2
  @@ -1,7 +1,7 @@
   <html>
   
   <head>
  -    <!-- $Id: Tomcat-Workers-HowTo.html,v 1.1.2.1 2000/09/04 21:10:01 larryi Exp $ -->
  +    <!-- $Id: Tomcat-Workers-HowTo.html,v 1.1.2.2 2000/10/16 02:20:06 larryi Exp $ -->
       <!-- Copyright 1999, Apache Software Foundation -->
   
       <meta http-equiv=Content-Type content="text/html">
  @@ -471,13 +471,16 @@
     <p>The cmd_line property can be given in multiple lines. In
     this case the jk environment will concatenate all the cmd_line entries
     together by putting spaces between the entries.</p>
  +
  +  <p><b>Note:</b> The cmd_line string doesn't support embedded spaces.
This is
  +  mostly likely to affect path specifications.  On Windows, you can use the
  +  MS-DOS 8.3 name for directories that would otherwise contain a space.</p>
     </td>
     <td>
     <p>worker.localjni.cmd_line=-config</p>
     <p>worker.localjni.cmd_line=path-to-tomcats-server.xml-file</p>
     <p>worker.localjni.cmd_line=-home</p>
     <p>worker.localjni.cmd_line=-path-to-tomcat-home</p>
  -
     </td>
    </tr>
    <tr>
  @@ -546,8 +549,8 @@
   them while constructing other properties. For example the following fragment:</p>
   
   <pre>
  -workers.tomcat_home=d:\tomcat
  -workers.java_home=d:\sdk\jdk1.2.2
  +workers.tomcat_home=c:\jakarta-tomcat
  +workers.java_home=c:\jdk1.2.2
   ps=\
   worker.inprocess.class_path=$(workers.tomcat_home)$(ps)classes
   worker.inprocess.class_path=$(workers.java_home)$(ps)lib$(ps)tools.jar
  @@ -557,8 +560,8 @@
   worker.inprocess.class_path properties</p>
   
   <pre>
  -worker.inprocess.class_path= d:\tomcat\classes
  -worker.inprocess.class_path=d:\sdk\jdk1.2.2\lib\tools.jar
  +worker.inprocess.class_path= c:\jakarta-tomcat\classes
  +worker.inprocess.class_path=c:\jdk1.2.2\lib\tools.jar
   </pre>
   
   <h2>The sample worker.properties</h2>
  @@ -588,7 +591,7 @@
   
   <ul>
    <li>workers.tomcat_home
  -     - Have it point to your tomcat_home. E.g. wrkers.tomcat_home=d:\tomcat</li>
  +     - Have it point to your tomcat_home. E.g. wrkers.tomcat_home=c:\jakarta-tomcat</li>
    <li>workers.java_home
        - Have it point to where you placed your JDK. E.g.
        workers.java_home=c:\jdk1.2.2</li>
  
  
  
  1.1.2.2   +10 -19    jakarta-tomcat/src/doc/tomcat-netscape-howto.html
  
  Index: tomcat-netscape-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/tomcat-netscape-howto.html,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- tomcat-netscape-howto.html	2000/10/12 06:22:53	1.1.2.1
  +++ tomcat-netscape-howto.html	2000/10/16 02:20:07	1.1.2.2
  @@ -26,7 +26,7 @@
     <li>&lt;tomcat_home&gt;\bin - Where you place web server plugins </li>
   </ol>
   
  -<p>In all the examples in this document &lt;tomcat_home&gt; will be d:\tomcat.</p>
  +<p>In all the examples in this document &lt;tomcat_home&gt; will be c:\jakarta-tomcat.</p>
   
   <p>A <tt>worker</tt> is defined to be a tomcat process that accepts work
from
   the Netscape server.</p>
  @@ -49,20 +49,11 @@
   <h2>Installation</h2>
   
   <p>As of Tomcat 3.2, a pre-built version of the Netscape redirector server plugin
  -for Win32, <tt>nsapi_redirect.dll</tt>, is available from two locations.  First,
  -it may be found under the win32/i386 directory where you got the
  -<a href="http://jakarta.apache.org/downloads/binindex.html"> Tomcat binary
  -distribution.</a> Second, it may be found in the Tomcat source distribution under
  -jakarta-tomcat\bin\netscape\nt4\i386.  The <tt>nsapi_redirect.dll</tt>
  -may be used on Win98 systems in spite of the "nt4" in the sequence of subdirectories.
  -For those using Netscape as your browser, your best bet is to download the Tomcat
  -source distribution since there have been reported problems with Netscape downloading
  -DLLs directly.</p>
  -
  -<p>A pre-built version of the Netscape redirector server plugin for Linux,
  -<tt>nsapi_redirect.so</tt>, is available in the Tomcat source distribution
  -under jakarta-tomcat\bin\netscape\linux\i386.  (Though this Linux version is available,
  -the OS dependent instructions below refer only to Windows NT.)</p>
  +for Win32, <tt>nsapi_redirect.dll</tt>, is available under the win32/i386
  +directory where you downloaded the <a href="http://jakarta.apache.org/downloads/binindex.html">
  +Tomcat binary distribution.</a> For those using Netscape as your browser, try
  +downloading a zip version of the file, if available. There can be problems using
  +Netscape to download DLL files.</p>
   
   <p>You can also build a copy locally from the source in Tomcat's source
   distribution.</p>
  @@ -88,8 +79,8 @@
   <h3>Configuring the NSAPI Redirector</h3>
   
   <p>In this document I will assume that nsapi_redirect.dll is placed in
  -d:\tomcat\bin\netscape\nt4\i386\nsapi_redirect.dll and that you created the
  -properties files are in d:\tomcat\conf.</p>
  +c:\jakarta-tomcat\bin\win32\i386\nsapi_redirect.dll and that you created the
  +properties files are in c:\jakarta-tomcat\conf.</p>
   
   <ol>
     <li>If the Netscape built in servlet support is working disable it.</li>
  @@ -205,12 +196,12 @@
   
   <p>Adding a Tomcat context to Netscape requires the addition of a new Netscape 
   virtual directory that covers the Tomcat context. For example, adding a 
  -/example Netscape virtual directory that covers the d:\tomkat\webapps\examples 
  +/example Netscape virtual directory that covers the c:\jakarta-tomcat\webapps\examples

   directory.
   
   To add a new virtual directory add the following line to your obj.conf:</p>
   
  -<p><tt>NameTrans fn=pfx2dir from=/examples dir=&quot;d:/tomcat/webapps/examples&quot;</tt></p>
  +<p><tt>NameTrans fn=pfx2dir from=/examples dir=&quot;c:/jakarta-tomcat/webapps/examples&quot;</tt></p>
   
   <p>WEB-INF protection requires some explanation; Each servlet application (context)
has a
   special directory named WEB-INF, this directory contains sensitive configurations data
and
  
  
  
  1.1.2.2   +29 -40    jakarta-tomcat/src/doc/tomcat-iis-howto.html
  
  Index: tomcat-iis-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/tomcat-iis-howto.html,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- tomcat-iis-howto.html	2000/10/12 06:21:26	1.1.2.1
  +++ tomcat-iis-howto.html	2000/10/16 02:20:07	1.1.2.2
  @@ -26,7 +26,7 @@
     <li>&lt;tomcat_home&gt;\bin - Where you place web server plugins </li>
   </ol>
   
  -<p>In all the examples in this document &lt;tomcat_home&gt; will be d:\tomcat.</p>
  +<p>In all the examples in this document &lt;tomcat_home&gt; will be c:\jakarta-tomcat.</p>
   
   <p>A <tt>worker</tt> is defined to be a tomcat process that accepts work
from the IIS
   server.</p>
  @@ -50,14 +50,11 @@
   <h2>Installation</h2>
   
   <p>As of Tomcat 3.2, a pre-built version of the ISAPI redirector server plugin,
  -<tt>isapi_redirect.dll</tt>, is available from two locations.  First, it may
be found under
  -the win32/i386 directory where you got the <a href="http://jakarta.apache.org/downloads/binindex.html">
  -Tomcat binary distribution.</a> Second, it may be found in the Tomcat source
  -distribution under jakarta-tomcat\bin\iis\nt4\i386.  The <tt>isapi_redirect.dll</tt>
  -may be used on Win98 systems in spite of the "nt4" in the sequence of subdirectories.
  -For those using Netscape as your browser, your best bet is to download the Tomcat
  -source distribution since there have been reported problems with Netscape downloading
  -DLLs directly.</p>
  +<tt>isapi_redirect.dll</tt>, is available under the win32/i386 directory where
you
  +downloaded the <a href="http://jakarta.apache.org/downloads/binindex.html">
  +Tomcat binary distribution.</a> For those using Netscape as your browser, try
  +downloading a zip version of the file, if available. There can be problems using
  +Netscape to download DLL files.</p>
   
   <p>You can also build a copy locally from the source in Tomcat's source
   distribution.</p>
  @@ -86,8 +83,8 @@
   <h3>Configuring the ISAPI Redirector</h3>
   
   <p>In this document I will assume that isapi_redirect.dll is placed in
  -d:\tomcat\bin\iis\i386\isapi_redirect.dll and that you created the properties
  -files are in d:\tomcat\conf.</p>
  +c:\jakarta-tomcat\bin\win32\i386\isapi_redirect.dll and that you created the properties
  +files are in c:\jakarta-tomcat\conf.</p>
   
   <ol>
     <li>In the registry, create a new registry key named <br>
  @@ -96,25 +93,25 @@
     <li>Add a string value with the name <tt>extension_uri</tt> and a value
of
       /jakarta/isapi_redirect.dll</li>
     <li>Add a string value with the name <tt>log_file</tt> and a value
pointing
  -    to where you want your log file to be (for example <tt>d:\tomcat\isapi.log)</tt>.</li>
  +    to where you want your log file to be (for example <tt>c:\jakarta-tomcat\logs\isapi.log)</tt>.</li>
     <li>Add a string value with the name <tt>log_level</tt> and a value
for
       your log level (can be <tt>debug</tt>, <tt>info</tt>, <tt>error</tt>
   	  or <tt>emerg</tt>). </li>
     <li>Add a string value with the name <tt>worker_file</tt> and a value
which
       is the full path to your workers.properties file (for example
  -    <tt>D:\tomcat\conf\workers.properties</tt>)</li>
  +    <tt>c:\jakarta-tomcat\conf\workers.properties</tt>)</li>
     <li>Add a string value with the name <tt>worker_mount_file</tt> and
a value
       which is the full path to your uriworkermap.properties file (for example
  -    <tt>D:\tomcat\conf\uriworkermap.properties</tt>)</li>
  +    <tt>c:\jakarta-tomcat\conf\uriworkermap.properties</tt>)</li>
     <li>Using the IIS management console, add a new virtual directory to your
       IIS/PWS web site. The name of the virtual directory must be jakarta. Its
   	physical path should be the directory where you placed isapi_redirect.dll
  -	(in our example it is d:\tomcat\bin\iis\i386). While creating this new
  +	(in our example it is c:\jakarta-tomcat\bin\win32\i386). While creating this new
   	virtual directory assign it with execute access.</li>
     <li>Using the IIS management console, add isapi_redirect.dll as a filter
       in your IIS/PWS web site. The name of the filter should reflect its task
   	(I use the name jakarta), its executable must be our
  -	<tt>d:\tomcat\bin\iis\i386\isapi_redirect.dll</tt>. For PWS, you'll need 
  +	<tt>c:\jakarta-tomcat\bin\win32\i386\isapi_redirect.dll</tt>. For PWS, you'll
need 
   	to use regedit and add/edit the "Filter DLLs" key under 
   	HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters. This key 
           contains a "," separated list of dlls ( full paths ) - you need to insert the 
  @@ -216,7 +213,7 @@
   
   <p>Adding a Tomcat context to IIS requires the addition of a new IIS virtual directory
   that covers the Tomcat context. For example adding a /example IIS virtual directory that
  -covers the d:\tomcat\webapps\examples directory. </p>
  +covers the c:\jakarta-tomcat\webapps\examples directory. </p>
   
   <p>Configuring the redirector is somewhat harder, you will need to specify the exact
   URL-Path pattern(s) that you want Tomcat to handle (usually only JSP files and servlets).
  @@ -293,7 +290,8 @@
   <p><b>Note:</b> These steps assume your <tt>worker_mount_file</tt>
setting points
   to an unmodified copy of the uriworkermap.properties file. Results may be misleading
   if <tt>worker_mount_file</tt> points to a modified uriworkermap.properties
or
  -the uriworkermap.properties-auto file.</p>
  +the uriworkermap.properties-auto file.  It is also assumed that the "/examples"
  +context works correcly if you access Tomcat directly.</p>
   
   <h3>Win98</h3>
   
  @@ -319,9 +317,9 @@
       the log file.</li>
     <li>Invoke the URL &quot;http://localhost/examples/jsp/index.html&quot;
in your
       browser. Case is important in Tomcat 3.2.  The characters following
  -    &quot;localhost&quot; must be lower case. If the page fails to appear, stop
  -    the IIS service (required to view the IIS log file).  Then examine the last line
  -    in the IIS log file in found in SYSTEM/LogFiles/W3SVC1.
  +    &quot;localhost&quot; in the URL must be lower case. If the page fails to
  +    appear, stop the IIS service (required to view the IIS log file).  Then
  +    examine the last line in the IIS log file in found in SYSTEM/LogFiles/W3SVC1.
       <ol type="A">
         <li>If the last line contains: <tt>GET &quot;/examples/jsp/index.html
HTTP/1.1&quot; 404</tt>,
           then the ISAPI redirector is not recognizing that it should be handling
  @@ -341,6 +339,7 @@
             <li>If the number following <tt>GET &quot;/...&quot;</tt>
is 404, check
               the following:
               <ol type="a">
  +              <li>Make sure you entered the URL correctly.</li>
                 <li>Make sure the virtual directory created was called &quot;jakarta&quot;.
                   It should display in Personal Web Manager as &quot;/jakarta&quot;
                   (without the quotes).</li>
  @@ -398,34 +397,24 @@
       even if the other settings are wrong.</li>
     <li>Invoke the URL &quot;http://localhost/examples/jsp/index.html&quot;
in your
       browser. Case is important in Tomcat 3.2.  The characters following
  -    &quot;localhost&quot; must be lower case. If the page fails to appear, examine
  -    the last line in the IIS server log file in found in SYSTEM32/LogFiles/W3SVC1.
  +    &quot;localhost&quot; in the URL must be lower case. If the page fails to
  +    appear, examine the last line in the IIS server log file in found in
  +    SYSTEM32/LogFiles/W3SVC1.
       <ol type="A">
  -      <li>If the last line contains: <tt>GET &quot;/examples/jsp/index.html
HTTP/1.1&quot; 404</tt>,
  -        then the ISAPI redirector is not recognizing that it should be handling requests
  -        for the &quot;/examples&quot; context. Check the the <tt>extension_uri</tt>
  -        name for typos. If this is set correctly, the ISAPI redirector should
  -        recognize that it should handle requests requests for the &quot;/examples&quot;
  -        context.</li>
  -      <li>If the last line contains something like: <tt>GET &quot;/jakarta/isapi_redirect.dll
  -        HTTP1.1&quot;</tt>, then the ISAPI redirector is recognizing that it
should
  -        handle the request, but is not successful at getting Tomcat to service
  -        the request.
  +      <li>The last line should contain something like: <tt>GET &quot;/jakarta/isapi_redirect.dll
  +        HTTP1.1&quot;</tt>, which indicates the ISAPI redirector is recognizing
  +        that it should handle the request.
           <ol>
             <li>If the number following <tt>GET &quot;/...&quot;</tt>
is 404, check
               the following:
               <ol type="a">
  -              <li>Make sure the virtual directory created was called &quot;jakarta&quot;.
  -                It should display in Personal Web Manager as &quot;/jakarta&quot;
  -                (without the quotes).</li>
  -              <li>Make sure the <tt>extension_uri</tt> data begins with

  -                &quot;/jakarta/&quot; (without the quotes).</li>
  +              <li>Make sure you entered the URL correctly.</li>
               </ol></li>
             <li>If the number following <tt>GET &quot;/...&quot;</tt>
is 500, check
               the following:
               <ol type="a">
  -              <li>Make sure that &quot;isapi_redirect.dll&quot; follows
  -                &quot;/jakarta/&quot; in the <tt>extension_uri</tt>
setting.</li>
  +              <li>Make sure the virtual directory created was called &quot;jakarta&quot;.</li>
  +              <li>Make sure that the <tt>extension_uri</tt> setting is
correct.</li>
                 <li>Check the workers.properties file and make sure the port setting
for
                   <tt>worker.ajp12.port</tt> is the same as the port specified
in the server.xml
                   for the &quot;Apache AJP12 support&quot;.</li>
  
  
  
  1.2.2.3   +13 -8     jakarta-tomcat/src/doc/NT-Service-howto.html
  
  Index: NT-Service-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/NT-Service-howto.html,v
  retrieving revision 1.2.2.2
  retrieving revision 1.2.2.3
  diff -u -r1.2.2.2 -r1.2.2.3
  --- NT-Service-howto.html	2000/10/12 06:35:05	1.2.2.2
  +++ NT-Service-howto.html	2000/10/16 02:20:08	1.2.2.3
  @@ -1,8 +1,8 @@
   
   <!--
  -$Header: /home/cvs/jakarta-tomcat/src/doc/NT-Service-howto.html,v 1.2.2.2 2000/10/12 06:35:05
larryi Exp $
  -$Revision: 1.2.2.2 $
  -$Date: 2000/10/12 06:35:05 $
  +$Header: /home/cvs/jakarta-tomcat/src/doc/NT-Service-howto.html,v 1.2.2.3 2000/10/16 02:20:08
larryi Exp $
  +$Revision: 1.2.2.3 $
  +$Date: 2000/10/16 02:20:08 $
   --!>
   
   <html>
  @@ -29,11 +29,11 @@
        hold on the NT executable (jk_nt_service.exe)</li>
    <ul>
     <li>Download
  -      the executable from <a
  -      href="http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/bin/nt_service/jk_nt_service.exe?rev=1.1.2.1">http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/bin/nt_service/jk_nt_service.exe?rev=1.1.2.1</a>
  -      and save it under the name jk_nt_service.exe.<br>
  -      As of the Tomcat 3.2 release, jk_nt_service.exe may also be found in the Tomcat
  -      source distribution under jakarta-tomcat\bin\nt_service.</li>
  +      the executable from the win32/i386 directory  found where you downloaded the
  +      <a href="http://jakarta.apache.org/downloads/binindex.html"> Tomcat binary
  +      distribution.</a> For those using Netscape as your browser, try downloading
  +      a zip version of the file, if available. There can be problems using Netscape
  +      to download DLL files.</li>
    </ul>
    <li>Customize
        a properties file that provides the service with Tomcat information
  @@ -69,6 +69,9 @@
     <li>From
         the NT services applet, highlight your service and press start.</li>
    </ul>
  + <b>Note:</b> If the log file location in your wrapper.properties file points
to
  + the <tt>logs</tt> directory, and the <tt>logs</tt> directory doesn't
yet exist,
  + manually create it before starting the service.
    <li>Stop
        Tomcat as a service.</li>
    <ul>
  @@ -85,6 +88,8 @@
   defined in your server.xml. In the absence of a configured AJPV12 port the
   Tomcat service will kill Tomcat abruptly (that is murder it) without giving it
   a chance to clean up. </p>
  +
  +<p>To remove the installed service, execute jk_nt_service -R &lt;name of service&gt;</p>
   
   <h1>Advance Setup</h1>
   
  
  
  
  1.1.2.1   +42 -28    jakarta-tomcat/src/doc/in-process-howto.html
  
  Index: in-process-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/in-process-howto.html,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- in-process-howto.html	2000/05/03 12:48:19	1.1
  +++ in-process-howto.html	2000/10/16 02:20:08	1.1.2.1
  @@ -43,7 +43,7 @@
     <li>&lt;tomcat_home&gt;\bin - Where you place web server plugins </li>
   </ol>
   
  -<p>In all the examples in this document &lt;tomcat_home&gt; will be d:\tomcat.</p>
  +<p>In all the examples in this document &lt;tomcat_home&gt; will be c:\jakarta-tomcat.</p>
   
   <p>A <tt>worker</tt> is defined to be a Tomcat process that accepts work
from
   the web server.</p>
  @@ -53,19 +53,22 @@
   <p>For in-process operation you will have to use the Netscape/IIS
   redirectors, look at their supported configuration sections.
   
  -<p>The in-process adapter was tested using JDK1.1.7b/IBM's JDK 1.1.7/JDK1.2.2.</p>
  +<p>The in-process adapter has been tested using JDK 1.1.7b, IBM's JDK 1.1.7, JDK
1.1.8,
  +JDK 1.2.2., and JDK 1.3.</p>
   
   <h2>Installation</h2>
   
  -<p>The in-process adapter is not part of the "official" build of Jakarta, You
  -can obtain the code and binaries needed for it by accessing
  -http://jakarta.apache.org/builds/tomcat/release/v3.1_beta_1/bin/win32/i386/.
  -The adapter related file is <tt>jni_connect.dll</tt>.</p>
  +<p>As of Tomcat 3.2, a pre-built version of the in-process adapter,
  +<tt>jni_connect.dll</tt>, is available under the win32/i386 directory where
you
  +downloaded the <a href="http://jakarta.apache.org/downloads/binindex.html">
  +Tomcat binary distribution.</a> For those using Netscape as your browser, try
  +downloading a zip version of the file, if available. There can be problems using
  +Netscape to download DLL files.</p>
   
   <p>The Tomcat JNI adapter requires the following actions:
   
   <ol>
  -  <li>Putting jni_connect.dll in the bin directory - jni_connect.dll is used
  +  <li>Putting jni_connect.dll under the bin directory - jni_connect.dll is used
     to issue callbacks from Tomcat back to the web server, either obtain a
     pre-built DLL or build it yourself (see the build section).</li>
     <li>Update <tt>workers.properties</tt> and add the JNI worker - The
JNI worker
  @@ -81,16 +84,18 @@
   </ol>
   
   
  -<h3>Putting jni_connect.dll in the bin directory</h3>
  +<h3>Putting jni_connect.dll under the bin directory</h3>
   
   <p> Put jni_connect.dll inside 
  -    <tt>&lt;tomcat_home&gt;\bin\i386\</tt>.
  +    <tt>&lt;tomcat_home&gt;\bin\win32\i386\</tt>.
   </p>
   
  -<h3>Update worker.properties and add the JNI worker</h3>
  +<h3>Update workers.properties and add the JNI worker</h3>
   <p> You should provide the JNI worker with several settings, some are
   mandatory and some are an option...
   </p>
  +<p><b>Note:</b> The following instructions assume Tomcat is installed
at c:\jakarta-tomcat.
  +Adjust them appropriately to your Tomcat installation directory.</p>
   <ol>
     <li>You <b>should</b> define a JNI worker.<br>
     Set the <tt>worker.list</tt> property to point on a worker named <tt>jni</tt>:
  @@ -100,42 +105,48 @@
     <li>You <b>should</b> set a classpath to be use by the in-process Tomcat.<br>
     To set the classpath use the <tt>worker.name.class_path</tt> property,
     for example:<br>
  -  <tt>worker.jni.class_path=d:\tomcat\classes</tt><br>
  -  <tt>worker.jni.class_path=d:\tomcat\lib\xml.jar</tt><br>
  -  <tt>worker.jni.class_path=d:\tomcat\lib\jasper.jar</tt><br>
  -  <tt>worker.jni.class_path=d:\tomcat\lib\servlet.jar</tt><br>
  -  <tt>worker.jni.class_path=d:\tomcat\lib\webserver.jar</tt><br>
  -  <tt>worker.jni.class_path=d:\sdk\jdk1.2.2\lib\tools.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\classes</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\lib\jaxp.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\lib\parser.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\lib\jasper.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\lib\servlet.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jakarta-tomcat\lib\webserver.jar</tt><br>
  +  <tt>worker.jni.class_path=c:\jdk1.2.2\lib\tools.jar</tt><br>
     <b>Note</b>: Do not forget to include the JDK's tools.jar in your classpath.
     </li>
     <li>You <b>should</b> provide a full path to the dll implementing the
JVM.
     For JDK1.1.x it is javai.dll, for JDK1.2.x it is jvm.dll. For example:<br>
  -  <tt>worker.jni.jvm_lib=d:\sdk\jdk1.2.2\jre\bin\classic\jvm.dll</tt>
  +  <tt>worker.jni.jvm_lib=c:\jdk1.2.2\jre\bin\classic\jvm.dll</tt>
     </li>
     <li>You <b>should</b> provide command line options for Tomcat; you
must provide
     a -config option to specify your JNI configured server.xml. For example:<br>
     <tt>worker.jni.cmd_line=-config</tt><br>
  -  <tt>worker.jni.cmd_line=d:\tomcat\conf\jni_server.xml</tt>
  -  </li>
  +  <tt>worker.jni.cmd_line=c:\jakarta-tomcat\conf\jni_server.xml</tt><br>
  +  <b>Note:</b> The cmd_line string doesn't support embedded spaces. If the
  +  path to the jni_server.xml file includes spaces, use the DOS 8.3 name for
  +  directories that would otherwise contain a space.</li>
     <li>You <b>should</b> specify the tomcat home location as a Java system
     properties. For example:<br>
  -  <tt>worker.jni.sysprops=tomcat.home=d:\tomcat</tt>
  +  <tt>worker.jni.sysprops=tomcat.home=c:\jakarta-tomcat</tt>
     </li>
     <li>You can specify additional Java system properties. For example:<br>
     <tt>worker.jni.sysprops=java.compiler=NONE</tt>
     </li>
     <li>You can specify files to by used by the JVM for stdout and stderr.
     For example:<br>
  -  <tt>worker.jni.stdout=d:\jvm.stdout</tt><br>
  -  <tt>worker.jni.stderr=d:\jvm.stderr</tt>
  +  <tt>worker.jni.stdout=c:\jakarta-tomcat\logs\jvm.stdout</tt><br>
  +  <tt>worker.jni.stderr=c:\jakarta-tomcat\logs\jvm.stderr</tt>
     </li>
     <li>You can specify additional PATH, to be use when loading dlls (useful
     when you are using native code). For example:<br>
  -  <tt>worker.jni.ld_path=d:\SQLLIB\bin</tt><br>
  -  <tt>worker.jni.ld_path=d:\my\native\code</tt>
  +  <tt>worker.jni.ld_path=c:\SQLLIB\bin</tt><br>
  +  <tt>worker.jni.ld_path=c:\my\native\code</tt>
     </li>
   </ol>
  -You can find a sample worker file (<tt>jni_workers.properties</tt>)  under
<tt>tomcat/conf</tt>.
  +<p>You can find a sample worker file (<tt>jni_workers.properties</tt>)
under
  +<tt>jakarta-tomcat/conf</tt>. The contents of this file assume that Tomcat
is
  +installed at c:\jakarta-tomcat.  Modify as needed if Tomcat is installed at a
  +different location.</p>
   
   <h3>Update server.xml</h3>
   <p>
  @@ -149,9 +160,12 @@
     lines (note that you will need to update the area marked
     with &lt;tomcat_home&gt;)
     <pre>
  -    &lt;!-- New JNI, you need to compile the new/experimental module --&gt;
  -    &lt;Connector className="org.apache.tomcat.service.JNIEndpointConnector"&gt;
  -        &lt;Parameter name="native_lib" value="&lt;tomcat_home&gt;\bin\i386\jni_connect.dll"/&gt;
  +    &lt;!-- JNI connector, make sure that you update the native_lib
  +             Parameter to point to your jni_connect.dll
  +     --&gt;
  +    &lt;Connector className=&quot;org.apache.tomcat.service.JNIEndpointConnector&quot;&gt;
  +        &lt;Parameter name=&quot;native_lib&quot;
  +            value=&quot;&lt;tomcat_home&gt;/bin/win32/i386/jni_connect.dll&quot;/&gt;
       &lt;/Connector&gt;
     </pre>
     These lines add a JNI connector to Tomcat.
  
  
  

Mime
View raw message