Author: rjung
Date: Tue Sep 1 14:28:04 2015
New Revision: 1700572
URL: http://svn.apache.org/r1700572
Log:
(Very) minor docs improvements.
Modified:
tomcat/jk/trunk/xdocs/webserver_howto/apache.xml
tomcat/jk/trunk/xdocs/webserver_howto/iis.xml
tomcat/jk/trunk/xdocs/webserver_howto/nes.xml
Modified: tomcat/jk/trunk/xdocs/webserver_howto/apache.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/webserver_howto/apache.xml?rev=1700572&r1=1700571&r2=1700572&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/webserver_howto/apache.xml (original)
+++ tomcat/jk/trunk/xdocs/webserver_howto/apache.xml Tue Sep 1 14:28:04 2015
@@ -30,8 +30,9 @@
<body>
<section name="Introduction">
<p>
-This document explains how to connect Tomcat to the popular open source web
server, Apache httpd.
-You can use mod_jk, the Tomcat redirector module, with any version of Apache
starting with 1.3.
+This document explains how to connect Tomcat to the popular open source web
server, Apache HTTP Server.
+You can use the connection module mod_jk with any version of Apache starting
with 1.3 and any version
+of Tomcat starting with (at least) 3.2.
</p>
<p>
@@ -44,12 +45,12 @@ For more detailed configuration informat
and <a href="../reference/apache.html">Apache</a>.
</p>
-<p><b>Waring: If Apache HTTP Server and Tomcat are configured to serve content
from
-the same filing system location then care must be taken to ensure that httpd is
+<p><b>Warning: If Apache and Tomcat are configured to serve content from
+the same file system location then care must be taken to ensure that Apache is
not able to serve inappropriate content such as the contents of the WEB-INF
-directory or JSP source code.</b> This could occur if the httpd DocumentRoot
+directory or JSP source code.</b> This could occur if the Apache DocumentRoot
overlaps with a Tomcat Host's appBase or the docBase of any Context. It could
-also occur when using the httpd Alias directive with a Tomcat Host's appBase or
+also occur when using the Apache Alias directive with a Tomcat Host's appBase
or
the docBase of any Context.
</p>
@@ -93,7 +94,7 @@ supporting Apache 1.3 and/or 2.x
WinNT4.0-i386 SP4/SP5/SP6a (should be able to work with other service packs),
Win2K and WinXP and Win98
</li>
<li>
-Cygwin (until you have an apache server and autoconf/automake support tools)
+Cygwin (until you have an Apache server and autoconf/automake support tools)
</li>
<li>
Netware
@@ -108,27 +109,20 @@ Tomcat 3.2 to Tomcat 8.
</p>
<p>
-The redirector uses <b>ajp12</b> and <b>ajp13</b> to send requests to the
Tomcat containers. There is also an option to use Tomcat in process,
-more about the in-process mode can be found in the in process howto.
+The mod_jk module uses the AJP protocol to send requests to the Tomcat
containers.
+The AJP version typically used is <b>ajp13</b>.
</p>
</subsection>
-<subsection name="Who support ajp protocols ?">
+<subsection name="Who supports AJP protocols?">
<p>
-The ajp12 protocol is only available in Tomcat 3.2.x and 3.3.x.
+Tomcat supports ajp13 since Tomcat 3.2.
+Others servlet engines such as <b>Jetty</b> or <b>JBoss</b> also support the
ajp13 protocol
</p>
<p>
-The <b>ajp12</b> has been <b>deprecated</b> with Tomcat 3.3.x and you should
use instead
-<b>ajp13</b> which is the only ajp protocol known by Tomcat 4 and above.
-</p>
-
-<p>
-Of course Tomcat 3.2.x and 3.3.x also support ajp13 protocol.
-</p>
-
-<p>
-Others servlet engines such as <b>jetty</b> have support for ajp13 protocol
+The <b>ajp12</b> protocol has been <b>deprecated</b> and you should no longer
use it.
+The <b>ajp14</b> protocol is considered experimental.
</p>
</subsection>
@@ -226,8 +220,8 @@ A sample workers.properties can be found
</p>
<p>
-Also as with other Apache HTTP Server modules, mod_jk should be first
installed on the modules directory of your
-Apache webserver, ie : /usr/lib/apache and you should update your
<b>httpd.conf</b> file.
+Also as with other Apache modules, mod_jk should be first installed on the
modules directory of your
+Apache HTTP Server, ie: /usr/lib/apache and you should update your
<b>httpd.conf</b> file.
</p>
@@ -247,8 +241,9 @@ The mod_jserv configuration directives a
</subsection>
<subsection name="Using Tomcat auto-configure">
+<warn>Tomcat auto-configure is deprecated and has been removed in Tomcat 7 and
later.</warn>
<p>
-The auto-configure works only for a single Tomcat running on the same machine
where Apache HTTP Server is running.
+The auto-configure works only for a single Tomcat running on the same machine
where the Apache HTTP Server is running.
The simplest way to configure Apache HTTP Server to use mod_jk is to turn on
the Apache HTTP Server auto-configure setting
in Tomcat and put the following include directive at the end of your Apache
httpd.conf file
(make sure you replace $TOMCAT_HOME with the correct path for your Tomcat
installation:
@@ -264,7 +259,7 @@ Note: this file may also be generated as
</p>
<p>
-This will tell Apache HTTP Server to use directives in the
<b>mod_jk.conf-auto</b> file in
+This will tell the Apache HTTP Server to use directives in the
<b>mod_jk.conf-auto</b> file in
the Apache configuration. This file is created by enabling the Apache
auto-configuration by creating your workers.properties file at
$TOMCAT_HOME/conf/jk/workers.properties and adding the listener to the Engine
@@ -285,7 +280,7 @@ element in the server.xml file as per th
<p>
Then restart Tomcat and mod_jk.conf should be generated. For more information
on
this topic, please refer to the API documentation at the
-<a
href="http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/jk/config/ApacheConfig.html";>
+<a
href="http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/jk/config/ApacheConfig.html";>
Tomcat docs website</a>.
</p>
@@ -293,7 +288,7 @@ Tomcat docs website</a>.
<subsection name="Custom mod_jk configuration">
<p>
-You should use custom configuration when :
+You should use custom configuration when:
</p>
<ul>
<li>
@@ -305,7 +300,7 @@ Another case for custom configuration is
each one having it's own configuration, a general case in ISP hosting
</li>
<li>
-Also all Apache webmaster will retain custom configuration to be able to tune
the settings
+Also most Apache web masters will retain custom configuration to be able to
tune the settings
to their real needs.
</li>
</ul>
@@ -330,10 +325,8 @@ Here is a simple configuration:
JkLogFile /var/log/httpd/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
- # Send servlet for context /examples to worker named worker1
- JkMount /examples/servlet/* worker1
- # Send JSPs for context /examples to worker named worker1
- JkMount /examples/*.jsp worker1
+ # Send requests for context /examples to worker named worker1
+ JkMount /examples/* worker1
</source>
</subsection>
@@ -377,7 +370,7 @@ be used for piped logging:
<p>
<b>JkLogLevel</b>
-set the log level between :
+set the log level between:
</p>
<ul>
@@ -404,7 +397,7 @@ set the log level between :
<p>
<b>JkLogStampFormat</b> will configure the date/time format found on mod_jk
logfile.
-See the mod_jk <a href="../reference/apache.html">Apache HTTP server
reference</a> for details.
+See the mod_jk <a href="../reference/apache.html">Apache HTTP Server
reference</a> for details.
</p>
<source>
@@ -418,9 +411,9 @@ See the mod_jk <a href="../reference/apa
<p>
You can log mod_jk information using the Apache standard module
<b>mod_log_config</b>.
-The module sets several notes in the Apache httpd notes table.
+The module sets several notes in the Apache notes table.
Most of them are are only useful in combination with a load balancer worker.
-See the mod_jk <a href="../reference/apache.html">Apache HTTP server
reference</a> for details.
+See the mod_jk <a href="../reference/apache.html">Apache HTTP Server
reference</a> for details.
</p>
<source>
@@ -439,7 +432,7 @@ You can also log a request protocol in t
the access log. This is not recommended and mostly a backward compatibility
feature. The directive <b>JkRequestLogFormat</b> will configure the format
of this protocol. It gets configured and enabled on a per virtual host basis.
-See the mod_jk <a href="../reference/apache.html">Apache HTTP server
reference</a> for details.
+See the mod_jk <a href="../reference/apache.html">Apache HTTP Server
reference</a> for details.
</p>
<source>
@@ -487,7 +480,7 @@ options(vhost) = plus_options(global) -
<p>
Using JkOptions <b>ForwardURIProxy</b>, the forwarded URI
-will be partially reencoded after processing inside Apache httpd and
+will be partially reencoded after processing inside Apache and
before forwarding to Tomcat. This will be compatible with local
URL manipulation by mod_rewrite and with URL encoded session ids.
@@ -515,7 +508,7 @@ will not work.
</p>
<p>
Using JkOptions <b>ForwardURICompat</b>, the forwarded URI will
-be decoded by Apache httpd. Encoded characters will be decoded and
+be decoded by Apache. Encoded characters will be decoded and
explicit path components like ".." will already be resolved.
This is less spec compliant and is <b>not safe</b> if you are using
prefix JkMount. This option will allow to rewrite URIs with
@@ -603,7 +596,7 @@ bypassing your unmount rules.
<p>
JkOptions <b>ForwardDirectories</b> is used in conjunction with
<b>DirectoryIndex</b>
-directive of Apache web server. As such mod_dir should be available to Apache,
+directive of Apache. As such mod_dir should be available to Apache,
statically or dynamically (DSO)
<br/>
<br/>
@@ -644,9 +637,9 @@ file that Tomcat normally serves - for i
<p>
Setting JkOptions <b>ForwardLocalAddress</b>, you ask mod_jk to send the local
address
-of the Apache web server instead of remote client address. This can be used by
-Tomcat remote address valve for allowing connections only from registered
Apache
-web servers.
+of the Apache HTTP Server instead of remote client address. This can be used by
+Tomcat remote address valve for allowing connections only from configured
Apache
+servers.
<source>
JkOptions +ForwardLocalAddress
@@ -731,7 +724,7 @@ This flag shouldn't be set when servlet
</p>
<p>
-JkOptions <b>ForwardSSLCertChain</b>, you ask mod_jk, when using ajp13,
+JkOptions <b>ForwardSSLCertChain</b>, you ask mod_jk, when using ajp13,
to forward SSL certificate chain (off by default).
Mod_jk only passes the <code>SSL_CLIENT_CERT</code> to the AJP connector. This
is not a
problem with self-signed certificates or certificates directly signed by the
@@ -802,7 +795,7 @@ You can use the JkMount directive at the
<subsection name="Configuring Apache to serve static web application files">
<p>
-If the Tomcat Host appBase (webapps) directory is accessible by the Apache web
server,
+If the Tomcat Host appBase (webapps) directory is accessible by the Apache
HTTP Server,
Apache can be configured to serve web application context directory static
files instead
of passing the request to Tomcat.
</p>
@@ -810,8 +803,8 @@ of passing the request to Tomcat.
<p>
Caution: For security reasons it is strongly recommended that JkMount is used
to
pass all requests to Tomcat by default and JkUnMount is used to explicitly
-exclude static content to be served by httpd. It should also be noted that
-content served by httpd will bypass any security constraints defined in the
+exclude static content to be served by Apache. It should also be noted that
+content served by Apache will bypass any security constraints defined in the
application's web.xml.
</p>
@@ -820,11 +813,11 @@ document space for a VirtualHost:
</p>
<source>
- # Static files in the examples webapp are served by apache
+ # Static files in the examples webapp are served by Apache
Alias /examples /vat/tomcat3/webapps/examples
# All requests go to worker1 by default
JkMount /* worker1
- # Serve html, jpg and gif using httpd
+ # Serve html, jpg and gif using Apache
JkUnMount /*.html worker1
JkUnMount /*.jpg worker1
JkUnMount /*.gif worker1
@@ -846,7 +839,7 @@ directive when jk and alias/userdir URLs
ServerName testxxx.mysys
DocumentRoot /www/testxxx/htdocs
- # Use SetEnvIf to st no-jk when /home/ is encountered
+ # Use SetEnvIf to set no-jk when /home/ is encountered
SetEnvIf Request_URI "/home/*" no-jk
# Now /home will goes to /home/dataxxx/
@@ -877,12 +870,12 @@ or a Web Archive *.war within the Tomcat
</p>
<source>
- # Static files in all Tomcat webapp context directories are served by apache
+ # Static files in all Tomcat webapp context directories are served by Apache
JkAutoAlias /var/tomcat3/webapps
# All requests go to worker1 by default
JkMount /* ajp13
- # Serve html, jpg and gif using httpd
+ # Serve html, jpg and gif using Apache
JkUnMount /*.html ajp13
JkUnMount /*.jpg ajp13
JkUnMount /*.gif ajp13
@@ -891,7 +884,7 @@ or a Web Archive *.war within the Tomcat
<p>
If you encoded all your URLs to contain the session id
(<code>;jsessionid=...</code>), and you later decide, you want to
-move part of the content to Apache httpd, you can tell
+move part of the content to Apache, you can tell
mod_jk to strip off all session ids from URLs for
those requests, that do not get forwarded via mod_jk.
</p>
@@ -913,7 +906,7 @@ The mod_jk build use the widely used con
In case you get source from subversion, ie without an existing configure
script,
you should have autoconf for configuration and installation.
<p>
-To create tomcat-connectors's autoconf script, you will need libtool
+To create the mod_jk autoconf script, you will need libtool
1.5.2, automake 1.10 and autoconf 2.59 or newer. The use of more recent
versions is encouraged, e.g. for reliable detection of the features of
recent version of operating systems.
@@ -922,7 +915,7 @@ Those tools will not be required if you
they are only required for developers.
</p>
<p>
-To create the configure script just type :
+To create the configure script just type:
<screen>
<type>./buildconf.sh</type>
@@ -933,7 +926,7 @@ To create the configure script just type
<subsection name="Using configure to build mod_jk">
<p>Here's how to use configure to prepare mod_jk for building, just type:
<source>
-./configure [autoconf arguments] [tomcat-connectors arguments]
+./configure [autoconf arguments] [mod_jk arguments]
</source>
</p>
@@ -946,27 +939,28 @@ You could set <b>CFLAGS</b> and <b>LDFLA
</screen>
<p>
-If you want to build mod_jk for different version of Apache httpd, like 1.3 or
2.x,
+If you want to build mod_jk for different versions of the Apache HTTP Server,
like 1.3 or 2.x,
you need to go through the full build process for each of them.
-Please note, that httpd 2.0, 2.2 or 2.4 modules are <b>not</b> binary
compatible.
+Please note, that Apache 2.0, 2.2 or 2.4 modules are <b>not</b> binary
compatible.
You have to compile the module using the Apache version you plan to run it in.
-The mod_jk build directory used is "apache-2.0" for all 2.x builds.
+The mod_jk build directory used is "apache-2.0" for all 2.x builds. The source
code
+is compatible with Apache HTTP Server 2.0, 2.2 and 2.4.
<ul>
<li>
-use configure and indicate the correct Apache httpd apxs location (--with-apxs)
+use configure and indicate the correct Apache HTTP Server apxs location
(--with-apxs)
</li>
<li>
use make
</li>
<li>
copy the resulting mod_jk.so binary from the apache-1.3 or apache-2.0
subdirectory
-to the Apache httpd modules location.
+to the Apache HTTP Server modules location.
</li>
<li>
make clean (to remove all previously compiled object files)
</li>
<li>
-Start over with the apxs location for your next Apache httpd version.
+Start over with the apxs location for your next Apache HTTP Server version.
</li>
</ul>
@@ -984,25 +978,25 @@ It builds a shared Apache module. It det
(2.x and 1.3)</td>
</tr>
<tr valign="top"><td>--with-apache=DIR</td>
- <td>DIR is the path where apache sources are located.
-The apache sources should have been configured before configuring mod_jk.
+ <td>DIR is the path where Apache sources are located.
+The Apache sources should have been configured before configuring mod_jk.
DIR is something like: /home/apache/apache_1.3.19
It builds a static Apache module.</td>
</tr>
<tr valign="top"><td>--enable-EAPI</td>
<td>This parameter is needed when using Apache-1.3 and mod_ssl, otherwise
you will get the error message:
-"this module might crash under EAPI!" when loading mod_jk.so in httpd.
+"this module might crash under EAPI!" when loading mod_jk.so in Apache.
Not needed when --with-apxs has been used</td>
</tr>
<tr valign="top"><td>--enable-prefork</td>
<td>
-In case you build mod_jk for a multi-threaded Apache httpd 2.x MPM
(Multi-Processing Module),
+In case you build mod_jk for a multi-threaded Apache HTTP Server 2.x MPM
(Multi-Processing Module),
some areas of mod_jk code need to be synchronised to make it thread-safe.
Because configure can not easily detect, whether your are using a
multi-threaded MPM,
-mod_jk by default is always build thread-safe for Apache httpd 2.x.
+mod_jk by default is always build thread-safe for Apache HTTP Server 2.x.
If you are sure, that your MPM is not multi-threaded, you can use
"--enable-prefork"
to force the removal of the synchronisation code (thus increasing performance
a bit).
-For instance, the prefork MPM is not multi-threaded. For Apache httpd 1.3
+For instance, the prefork MPM is not multi-threaded. For Apache HTTP Server 1.3
this flag will be set automatically.</td>
</tr>
<tr valign="top"><td>--disable-trace</td>
@@ -1018,10 +1012,10 @@ will still be possible.</td>
</tr>
<tr valign="top"><td>--enable-api-compatibility</td>
<td>
-Only use httpd API functions available in all httpd production releases
-of the chosen major httpd release branch. This improves binary
-compatibility of module builds with httpd releases older than the release
-against mod_jk is build (only between minor httpd versions).</td>
+Only use Apache API functions available in all Apache production releases
+of the chosen major Apache release branch. This improves binary
+compatibility of module builds with Apache releases older than the release
+against mod_jk is build (only between minor Apache versions).</td>
</tr>
<tr valign="top"><td>--enable-flock</td>
<td>
@@ -1080,10 +1074,10 @@ An example on how to build mod_jk for Ap
<note>Set location for Apache 1.3 sources</note>
<typedos>set APACHE1_HOME=c:\apache13</typedos>
<note>Change directory to the mod_jk module for Apache 1.3</note>
-<typedos>cd c:\home\apache\jk\native\apache-1.3</typedos>
+<typedos>cd c:\tomcat-connectors-xxx-src\native\apache-1.3</typedos>
<note>Build the sources using MSDEV</note>
<typedos>MSDEV mod_jk.dsp /MAKE ALL</typedos>
-<note>Copy the dll to your apache modules directory</note>
+<note>Copy the dll to your Apache modules directory</note>
<typedos>cp release\mod_jk.so c:\apache13\modules\</typedos>
</screen>
@@ -1094,10 +1088,10 @@ An example on how to build mod_jk for Ap
<note>Set location for Apache 2.x sources</note>
<typedos>set APACHE2_HOME=c:\apache20</typedos>
<note>Change directory to the mod_jk module for Apache 2.x</note>
-<typedos>cd c:\home\apache\jk\native\apache-2.0</typedos>
+<typedos>cd c:\tomcat-connectors-xxx-src\native\apache-2.0</typedos>
<note>Build the sources using MSDEV</note>
<typedos>MSDEV mod_jk.dsp /MAKE ALL</typedos>
-<note>Copy the dll to your apache modules directory</note>
+<note>Copy the dll to your Apache modules directory</note>
<typedos>cp release\mod_jk.so c:\apache20\modules\</typedos>
</screen>
@@ -1114,7 +1108,7 @@ An alternative will be to open mod_jk.ds
<section name="Building mod_jk for Apache on System I - i5/OS (OS400)">
<p>
Since OS400 V4R5, System I (AS/400) has used Apache 2.0 as their primary web
server,
-replacing the old IBM webserver.
+replacing the old IBM web server.
It's now possible to build mod_jk on System I thanks to the help of the IBM
Rochester Labs which has provided information and patches to adapt mod_jk to
i5/OS.
</p>
@@ -1133,7 +1127,7 @@ NB: The latest mod_jk known to work on i
New in i5/OS V5R4, UTF is required, also for Apache modules, as such Apache
modules do not require
translations to/from EBCDIC but works should be done to port mod_jk 1.2.23
(and higher) to V5R4.
-From the V5R4 Infocenter :
+From the V5R4 Infocenter:
As of i5/OS(tm) V5R4, modules must be recompiled with a UTF locale. This
creates an environment where locale-dependent C runtime functions assume
that string data is encoded in UTF-8. Any hardcoded constants can be encoded
in UTF-8 by adding a #pragma convert(1208) statement in the module.
@@ -1158,7 +1152,7 @@ Create a directory in IFS, ie /home/apac
Send the whole jk source directory to System I directory via FTP.
</li>
<li>
-Then go to the System I command line :
+Then go to the System I command line:
</li>
</ul>
<screen>
@@ -1172,7 +1166,7 @@ Then go to the System I command line :
<type5250>STRSEU MOD_JK/QSRVSRC MOD_JK</type5250>
</screen>
<p>
-In the edited file, specify that only jk_module should be exported :
+In the edited file, specify that only jk_module should be exported:
<screen>
<note> Columns . . : 1 71 Edit
MOD_JK/QSRVSRC </note>
<note> SEU==>
MOD_JK </note>
@@ -1219,10 +1213,10 @@ Next, you should restart your Apache 2.0
<section name="Building mod_jk for Apache on MacOS/X">
<p>
-Mac OS X (10.2.x) build notes :
+Mac OS X (10.2.x) build notes:
</p>
<p>
-Assuming that you are root :
+Assuming that you are root:
</p>
<screen>
<note>For Apache 1.3:</note>
@@ -1242,25 +1236,25 @@ Assuming that you are root :
<section name="Getting mod_jk linked statically with Apache">
<p>
mod_jk allows to install mod_jk in the Apache source tree to get a statically
-linked mod_jk. Having mod_jk in the httpd executable brings some performance
+linked mod_jk. Having mod_jk in the Apache executable brings some small
performance
improvements. The configure option --with-apache prepare mod_jk to install it
in the Apache source tree.
The option --with-apache works both for Apache 1.3 and Apache 2.x.
-The examples below show how to get mod_jk in the httpd process.
+The examples below show how to get mod_jk in the Apache process.
</p>
-<subsection name="Installation in Apache-2.x">
+<subsection name="Installation for Apache-2.x">
<screen>
-<note> /home/apache20/httpd-2.0.43 is the directory where the httpd-2.0 sources
+<note> /home/apache24/httpd-2.4.12 is the directory where the Apache HTTP
Server sources
are located. </note>
-<type>./configure --with-apache=/home/apache20/httpd-2.0.43</type><br/>
+<type>./configure --with-apache=/home/apache24/httpd-2.4.12</type><br/>
<type>make</type><br/>
<note>Install the mod_jk library and other files in
-/home/apache20/httpd-2.0.43/modules: </note>
+/home/apache24/httpd-2.4.12/modules: </note>
<type>make install</type><br/>
<note> It is not possible to configure Apache directly because the config.m4
of mod_jk must
be added to the configure of httpd-2.x. </note>
-<type>cd /home/apache20/httpd-2.0.43</type>
+<type>cd /home/apache24/httpd-2.4.12</type>
<type>sh buildconf</type>
<type>configure ... --with-mod_jk</type>
<type>make</type>
@@ -1272,7 +1266,7 @@ allow static linking of mod_jk.
</p>
</subsection>
-<subsection name="Installation in Apache-1.3">
+<subsection name="Installation for Apache-1.3">
<screen>
<note> /home/apache/apache_1.3.27 is the directory where the apache-1.3 sources
are located. </note>
Modified: tomcat/jk/trunk/xdocs/webserver_howto/iis.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/webserver_howto/iis.xml?rev=1700572&r1=1700571&r2=1700572&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/webserver_howto/iis.xml (original)
+++ tomcat/jk/trunk/xdocs/webserver_howto/iis.xml Tue Sep 1 14:28:04 2015
@@ -22,7 +22,7 @@
limitations under the License.
</copyright>
<properties>
-<title>IIS HowTo</title>
+<title>ISAPI redirector for Micrsoft IIS HowTo</title>
<author email="[email protected]">Henri Gomez</author>
<author email="[email protected]">Gal Shachor</author>
<author email="[email protected]">Yoav Shapira</author>
@@ -31,12 +31,12 @@
<body>
<section name="Introduction">
<p>
-This document explains how to set up IIS to cooperate with Tomcat.
+This document explains how to set up the ISAPI redirector for IIS to cooperate
with Tomcat.
</p>
<p>
Normally IIS can not execute Servlets and Java Server Pages (JSPs),
-configuring IIS to use the JK ISAPI redirector plugin will let IIS send
servlet and
+configuring IIS to use the ISAPI redirector plugin will let IIS send servlet
and
JSP requests to Tomcat (and this way, serve them to clients).
</p>
@@ -77,7 +77,7 @@ A worker is defined to be a tomcat proce
<subsection name="Supported Configuration">
<p>
-The IIS-Tomcat redirector works for:
+The IIS to Tomcat redirector works for:
<ul>
<li>
WinNT4.0-i386 SP4/SP5/SP6a (should be able to work with other service packs),
Win98, WinXP, Win2K,
@@ -93,8 +93,8 @@ Tomcat 3.2 to Tomcat 8.
</p>
<p>
-The redirector uses <b>ajp12</b> and <b>ajp13</b> to send requests to the
Tomcat containers. There is also an option to use Tomcat in process,
-more about the in-process mode can be found in the in process howto.
+The mod_jk module uses the AJP protocol to send requests to the Tomcat
containers.
+The AJP version typically used is <b>ajp13</b>.
</p>
</subsection>
@@ -123,22 +123,15 @@ because the library is not loadable into
</p>
</subsection>
-<subsection name="Who support ajp protocols ?">
+<subsection name="Who supports AJP protocols?">
<p>
-The ajp12 protocol is only available in Tomcat 3.2.x and 3.3.x.
+Tomcat supports ajp13 since Tomcat 3.2.
+Others servlet engines such as <b>Jetty</b> or <b>JBoss</b> also support the
ajp13 protocol
</p>
<p>
-The <b>ajp12</b> has been <b>deprecated</b> with Tomcat 3.3.x and you should
use instead
-<b>ajp13</b> which is the only ajp protocol known by Tomcat 4 and above.
-</p>
-
-<p>
-Of course Tomcat 3.2.x and 3.3.x also support ajp13 protocol.
-</p>
-
-<p>
-Others servlet engines such as <b>jetty</b> have support for ajp13 protocol
+The <b>ajp12</b> protocol has been <b>deprecated</b> and you should no longer
use it.
+The <b>ajp14</b> protocol is considered experimental.
</p>
</subsection>
@@ -147,7 +140,7 @@ Others servlet engines such as <b>jetty<
<p>
<ol>
<li>
-The IIS-Tomcat redirector is an IIS plugin (filter + extension), IIS load the
redirector plugin and calls its
+The ISAPI redirector is a Microsoft IIS plugin (filter + extension). IIS loads
the redirector plugin and calls its
filter function for each in-coming request.
</li>
<li>
@@ -170,18 +163,16 @@ The extension collects the response from
<section name="Installation">
<p>
-A pre-built version of the ISAPI redirector server plugin, isapi_redirect.dll,
is available under
-the win32/i386 directory of tomcat-connectors distribution.
-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.
+A pre-built version of the ISAPI redirector plugin, isapi_redirect.dll, is
available under
+the win32/i386 directory of the Tomcat Connectors distribution.
-You can also build a copy locally from the source present in tomcat-connectors
distribution.
+You can also build a copy locally from the Tomcat Connectors source
distribution.
-The Tomcat redirector requires three entities:
+The ISAPI redirector requires three entities:
<ul>
<li>
-<b>isapi_redirect.dll</b> - The IIS server plugin, either obtain a pre-built
DLL or build it yourself (see the build section).
+<b>isapi_redirect.dll</b> - The ISAPI redirector for Microsoft IIS plugin,
either obtain a pre-built DLL or build it yourself (see the build section).
</li>
<li>
<b><a href="../reference/workers.html">workers.properties</a></b> - A file
that describes the host(s) and port(s) used by the workers (Tomcat processes).
@@ -259,7 +250,7 @@ you need to insert the full path to isap
<li>
If you're using IIS 6.0 you must also do the following:
<br />
-Using the IIS management console, add the Tomcat Isapi Redirector to the Web
+Using the IIS management console, add the ISAPI Redirector to the Web
Service Extensions.
<ol>
<li>Right-click on Web Service Extensions and choose Add a new Web Service
@@ -280,8 +271,8 @@ PWS will still keep the DLLs in memory.
</p>
<p>
That's all, you should now start Tomcat and ask IIS to serve you the /examples
context.
-Try <a
href="http://localhost/examples/jsp/index.html";>http://localhost/examples/jsp/index.html</a>
for example and
-execute some of the JSP examples.
+Try <a href="http://localhost/examples/";>http://localhost/examples/</a> for
example and
+execute some of the Servlet or JSP examples.
</p>
<p>
If this does not work successfully, refer to the Troubleshooting section below
for help on correcting the problem.
@@ -338,7 +329,7 @@ even if these files are part of a contex
Tomcat somewhat, by using it only to process requests that only Tomcat can
handle (e.g. requests to JSP pages and java servlets).
</p>
<p>
-For example, consider the html and gif files in the examples context : you
could serve these files directly
+For example, consider the html and gif files in the examples context: you
could serve these files directly
with IIS; there is no need to serve them from the Tomcat process.
</p>
<warn>However, you should be very careful when you implement the following
configuration style, because by doing so you are
@@ -365,7 +356,7 @@ For example adding a /example IIS virtua
<p>
Configuring the redirector is somewhat harder, you will need to specify the
exact
URL-Path pattern(s) which you want Tomcat to handle (usually only JSP files
and servlets).
-This requires a change to the uriworkermap.properties :
+This requires a change to the uriworkermap.properties:
<source>
For the examples context it requires to replace the following line
@@ -386,12 +377,12 @@ whose name ends with .jsp.
You can even be more explicit and provide lines such as:
<source>
- /example/servletname=defworker
+ /example/servlets/chat=defworker
</source>
</p>
<p>
-that instructs the redirector to redirect all requests whose URL-path matches
the leading string "/example/servletname"
+that instructs the redirector to redirect all requests whose URL-path matches
the leading string "/example/servlets/chat"
to the worker named defworker.
</p>
@@ -407,8 +398,8 @@ In particular, each servlet application
which contains sensitive configuration data and Java classes, and which should
always be kept hidden from web users.
Using the IIS management console it is possible to protect the WEB-INF
directory from user access, but considering that
this is a general requirement, and considering that it is easy to forget to
implement this protection
-at the IIS level, the redirector plugin does it automatically for you, and it
will reject any request
-which contains WEB-INF in its URL-path.
+at the IIS level, the ISAPI redirector plugin does it automatically for you,
and it will reject any request
+which contains WEB-INF in its URL path. It will also reject any request which
contains META-INF in its URL path.
</p>
</subsection>
@@ -468,23 +459,23 @@ to perform a custom build. You should al
The steps that you need to take are:
<ul>
<li>
-Change directory to the isapi plugins source directory.
+Change directory to the ISAPI redirector source directory.
</li>
<li>
Make the source with MSDEV
</li>
</ul>
<screen>
-<note>Change directory to the isapi plugins source directory</note>
-<typedos>cd c:\home\apache\jk\iis</typedos>
+<note>Change directory to the ISAPI redirector source directory</note>
+<typedos>cd c:\tomcat-connectors-xxx-src\native\iis</typedos>
<note>Build the sources using MSDEV</note>
<typedos>MSDEV isapi.dsp /MAKE ALL</typedos>
</screen>
</p>
<p>
If msdev is not in your path, enter the full path to msdev.exe.
-This will build both release and debug versions of the redirector plugin.
-An alternative will be to open the isapi workspace file (isapi.dsw) in msdev
and
+This will build both release and debug versions of the ISAPI redirector plugin.
+An alternative will be to open the ISAPI redirector workspace file (isapi.dsw)
in msdev and
build it using the build menu.
</p>
</section>
@@ -540,17 +531,17 @@ Check the log_file setting for typos, na
If the above are set correctly, the ISAPI redirector should be able to create
the log file.
</ul>
<p>
-Invoke the URL <a
href="http://localhost/examples/jsp/index.html";>http://localhost/examples/jsp/index.html</a>
+Invoke the URL <a
href="http://localhost/examples/";>http://localhost/examples/</a>
in your browser.
Case is important in Tomcat. The characters following "localhost" 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 :
+Then examine the last line in the IIS log file in found in
SYSTEM/LogFiles/W3SVC1:
</p>
<p>
If the last line contains:
</p>
<source>
- GET "/examples/jsp/index.html HTTP/1.1" 404
+ GET "/examples/ HTTP/1.1" 404
</source>
<p>
then the ISAPI redirector is not recognising that it should be handling
requests for the "/examples" context.
@@ -582,7 +573,7 @@ but is not successful at getting Tomcat
</p>
<p>
-You should check the HTTP error code following GET "/..." :
+You should check the HTTP error code following GET "/...":
</p>
<source>
@@ -613,7 +604,7 @@ Make sure the extension_uri data begins
Make sure that "isapi_redirect.dll" follows "/jakarta/" in the extension_uri
setting.
</li>
<li>
-Check the workers.properties file and make sure the port setting for
worker.ajp12.port is the same as the port specified in the server.xml for the
"Apache AJP12 support".
+Check the workers.properties file and make sure the port setting for
worker.ajp13.port is the same as the port specified in the server.xml for the
"AJP" connector.
</li>
</ul>
@@ -632,7 +623,7 @@ for the jakarta virtual directory in the
<p>
If the above settings are correct, the index.html page should appear in your
browser.
-You should also be able to click the Execute links to execute the JSP examples.
+You should also be able to click the links to execute some Servlet or JSP
examples.
</p>
</subsection>
@@ -673,7 +664,7 @@ If the above are set correctly, the gree
</ul>
<p>
-Invoke the URL <a
href="http://localhost/examples/jsp/index.html";>http://localhost/examples/jsp/index.html</a>
+Invoke the URL <a
href="http://localhost/examples/";>http://localhost/examples/</a>
in your browser. Case is important in Tomcat. The characters following
"localhost" 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.
</p>
@@ -684,7 +675,7 @@ which indicates the ISAPI redirector is
</p>
<p>
-You should check the HTTP error code following GET "/..." :
+You should check the HTTP error code following GET "/...":
</p>
<source>
@@ -711,7 +702,7 @@ Make sure the virtual directory created
Make sure that the extension_uri setting is correct.
</li>
<li>
-Check the workers.properties file and make sure the port setting for
worker.ajp12.port is the same as the port specified in the server.xml for the
"Apache AJP12 support".
+Check the workers.properties file and make sure the port setting for
worker.ajp13.port is the same as the port specified in the server.xml for the
"AJP" connector.
</li>
</ul>
@@ -730,7 +721,7 @@ Advanced Options of the Personal Web Man
<p>
If the above settings are correct, the index.html page should appear in your
browser.
-You should also be able to click the Execute links to execute the JSP examples.
+You should also be able to click the links to execute some Servlet or JSP
examples.
</p>
</subsection>
Modified: tomcat/jk/trunk/xdocs/webserver_howto/nes.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/webserver_howto/nes.xml?rev=1700572&r1=1700571&r2=1700572&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/webserver_howto/nes.xml (original)
+++ tomcat/jk/trunk/xdocs/webserver_howto/nes.xml Tue Sep 1 14:28:04 2015
@@ -22,7 +22,7 @@
limitations under the License.
</copyright>
<properties>
-<title>SunOne -- Netscape/iPlanet HowTo</title>
+<title>Planet web server HowTo</title>
<author email="[email protected]">Henri Gomez</author>
<author email="[email protected]">Jim Jagielski</author>
<author email="[email protected]">Gal Shachor</author>
@@ -32,13 +32,15 @@
<body>
<section name="Introduction">
<p>
-This document explains how to set up Sun ONE Web Server previously known as
-Netscape web servers to cooperate with Tomcat.
+This document explains how to set up the iPlanet Web Server
+to cooperate with Tomcat. The iPlanet Web Server was previously known under
+various names, including Netscape Enterprise Server, SunOne Web Server and
+Sun Enterprise System web server.
</p>
<p>
-Normally the Sun ONE Web Servers come with their own Servlet engine,
-but you can also configure them to send servlet and JSP requests to Tomcat
+Normally the iPlanet Web Server comes with its own Servlet engine,
+but you can also configure it to send servlet and JSP requests to Tomcat
using the NSAPI redirector plugin.
</p>
@@ -67,14 +69,14 @@ ${tomcat_home}\bin - Where you place web
</p>
<p>
In all the examples in this document ${tomcat_home} will be <b>c:\tomcat</b>.
-A worker is defined to be a tomcat process that accepts work from the Sun ONE
Web Server.
+A worker is defined to be a tomcat process that accepts work from the iPlanet
Web Server.
</p>
</subsection>
<subsection name="Supported Configuration">
<p>
-The NSAPI-Tomcat redirector was developed and tested on:
+The NSAPI redirector was developed and tested on:
<ul>
<li>
WINNT 2000/XP/2003 (should be able to work with other service packs) and some
Unixes
@@ -89,52 +91,43 @@ Tomcat 4.1 to Tomcat 8.
</p>
<p>
-The redirector uses <b>ajp12</b> and <b>ajp13</b> to send requests to the
Tomcat containers.
-There is also an option to use Tomcat in process,
-more about the in-process mode can be found in the in process howto.
+The redirector uses the AJP protocol to send requests to the Tomcat containers.
+The AJP version typically used is <b>ajp13</b>.
</p>
</subsection>
-<subsection name="Who support ajp protocols ?">
+<subsection name="Who supports AJP protocols?">
<p>
-The ajp12 protocol is only available in Tomcat 3.2.x and 3.3.x.
+Tomcat supports ajp13 since Tomcat 3.2.
+Others servlet engines such as <b>Jetty</b> or <b>JBoss</b> also support the
ajp13 protocol
</p>
<p>
-The <b>ajp12</b> has been <b>deprecated</b> with Tomcat 3.3.x and you should
use instead
-<b>ajp13</b> which is the only ajp protocol known by Tomcat 4 and above.
-</p>
-
-<p>
-Of course Tomcat 3.2.x and 3.3.x also support ajp13 protocol.
-</p>
-
-<p>
-Others servlet engines such as <b>jetty</b> have support for ajp13 protocol
+The <b>ajp12</b> protocol has been <b>deprecated</b> and you should no longer
use it.
+The <b>ajp14</b> protocol is considered experimental.
</p>
</subsection>
-
<subsection name="How does it work ?">
<p>
<ol>
<li>
-The NSAPI-Tomcat redirector is an Netscape service step plugin,
-Netscape load the redirector plugin and calls its service handler
-function for request that are assigned to the "servlet" configuration object.
+The NSAPI redirector is a web server plugin based on the NSAPI web server API.
+The web server loads the NSAPI redirector plugin and calls its service handler
+function for all requests that are assigned to the "servlet" configuration
object.
</li>
<li>
-For each in-coming request Netscape will execute the set of NameTrans
directives
-that we added to obj.conf, the assign-name function will check if it's from
+For each in-coming request the web server will execute the set of NameTrans
directives
+that we added to obj.conf, the assign-name function will check if it's
<code>from</code>
parameter matches the request URL.
</li>
<li>
If a match is found, assign-name will assign the servlet object name to the
request.
-This will cause Netscape to send the request to the servlet configuration
object.
+This will cause the web server to send the request to the servlet
configuration object.
</li>
<li>
-Netscape will execute our jk_service extension. The extension collects the
+The web server will execute our jk_service extension. The extension collects
the
request parameters and forwards them to the appropriate worker using the ajp13
protocol
(the worker="defworker" parameter in jk_service inform it that the worker for
this request is named <b>defworker</b>).
the workers properties files, <b>workers.properties</b>, will indicate that
defworker use ajp13 protocol.
@@ -151,21 +144,19 @@ The extension collects the response from
<section name="Installation">
<p>
A pre-built version of the NSAPI redirector, nsapi_redirect.dll, may be
available under
-the win32/i386 directory of tomcat-connectors distribution.
-For those using Netscape as your browser, try downloading a zip version of the
file, if available.
-
-You can also build a copy locally from the source present in tomcat-connectors
distribution.
-
-
-The Tomcat redirector requires two entities:
+the win32/i386 directory of the Tomcat Connectors distribution.
+You can also build a copy locally from the Tomcat Connectors source
distribution.
+</p>
+<p>
+The NSAPI redirector requires two files:
<ul>
<li>
-nsapi_redirect.dll (Windows) -or- nsapi_redirector.so (Unix) - The NSAPI
server plugin, either obtain a pre-built DLL/so or build it yourself
+nsapi_redirect.dll (Windows) -or- nsapi_redirector.so (Unix) - The NSAPI web
server plugin, either obtain a pre-built DLL/so or build it yourself
(see the build section).
</li>
<li>
workers.properties - A file that describes the host(s) and port(s) used by the
workers (Tomcat processes).
-A sample workers.properties can be found under the conf directory.
+A sample workers.properties can be found under the conf directory of the
source distribution.
</li>
</ul>
@@ -174,10 +165,10 @@ The installation includes the following
<ul>
<li>
Configuring the NSAPI redirector with a default /examples context and checking
that you can serve servlets
-with Netscape.
+with your browser.
</li>
<li>
-Adding more contexts to the configuration.
+Adding your own contexts to the configuration.
</li>
</ul>
@@ -196,7 +187,7 @@ and you created a log directory <b>c:\jk
If the built in servlet support is working disable it.
</li>
<li>
-Add the redirector plugin into the Netscape server configuration.
+Add the NSAPI redirector plugin into the iPlanet Web Server configuration.
Edit your server <b>magnus.conf</b> and add the following lines:
</li>
</ul>
@@ -217,8 +208,7 @@ Edit your server <b>obj.conf</b> and add
In the default object NameTrans section
<Object name="default">
- NameTrans fn="assign-name" from="/servlets-examples(|/*)" name="jknsapi"
- NameTrans fn="assign-name" from="/jsp-examples(|/*)" name="jknsapi"
+ NameTrans fn="assign-name" from="/examples(|/*)" name="jknsapi"
....
</Object>
@@ -249,12 +239,12 @@ Edit your worker definition file <b>work
<ul>
<li>
-Restart Web Server (stop and start the server)
+Restart the web server (stop and start the server)
</li>
</ul>
<p>
-That's all, now you should start tomcat and ask for
http://server:port/servlets-examples/
+That's all, now you should start tomcat and ask for
http://server:port/examples/
</p>
<warn>
The file <b>obj.conf</b> seems to be sensitive to leading white space in
lines, especially in
@@ -282,41 +272,41 @@ all you need to do is to edit <b>obj.con
</p>
<source>
- NameTrans fn="assign-name" from="/<context name>/*" name="jknsapi"
+ NameTrans fn="assign-name" from="/<context_name>/*" name="jknsapi"
</source>
<p>
-After saving <b>obj.conf</b> restart Netscape and it will serve the new
context.
+After saving <b>obj.conf</b> restart the web server and it will serve the new
context.
</p>
</subsection>
<subsection name="Advanced Context Configuration">
<p>
-Sometimes it is better to have Netscape serve the static pages (html, gif,
jpeg etc.)
-even if these files are part of a context served by Tomcat. For example,
consider the html and gif files in the examples context, there is no need to
serve them from the Tomcat process, Netscape will suffice.
+Sometimes it is better to have the web server serve the static pages (html,
gif, jpeg etc.)
+even if these files are part of a context served by Tomcat. For example,
consider the html and gif files in the examples context, there is no need to
serve them from the Tomcat process. The web server can do it on its own.
</p>
<p>
-Making Netscape serve static files that are part of the Tomcat contexts
requires the following:
+Making the web server serve static files that are part of the Tomcat contexts
requires the following:
</p>
<ul>
<li>
-Configuring Netscape to know about the Tomcat contexts
+Configuring the web server to know about the Tomcat contexts
</li>
<li>
-Make sure that the WEB-INF directory is protected from access.
+Make sure that the WEB-INF and META-INF directories are protected from access.
</li>
<li>
-Configuring Netscape to assign the NSAPI redirector only specific requests
that requires JSP/Servlet handling.
+Configuring the web server to assign the NSAPI redirector only specific
requests that requires JSP/Servlet handling.
</li>
</ul>
<p>
-Adding a Tomcat context to Netscape requires the addition of a new Netscape
virtual directory
+Adding the contents of a Tomcat context to the web server requires the
addition of a new virtual directory
that covers the Tomcat context.
</p>
<p>
-For example, adding a /example Netscape virtual directory that
+For example, adding a /example virtual directory that
covers the <b>c:\tomcat\webapps\examples</b> directory.
</p>
@@ -331,17 +321,20 @@ To add a new virtual directory add the f
<p>
WEB-INF protection requires some explanation; Each servlet application
(context) has a special directory named <b>WEB-INF</b>,
this directory contains sensitive configurations data and Java classes and
must be kept hidden from web users.
-WEB-INF can be protected by adding the following line to the PathCheck section
in the default configuration object:
+A second directory that should be protected is META-INF.
+Those directories can be protected by adding the following line to the
PathCheck section in the default configuration object:
</p>
<source>
PathCheck fn="deny-existence" path="*/WEB-INF/*"
-
- This line instructs the Netscape server to reject any request with a URL
that contain the path /WEB-INF/.
+ PathCheck fn="deny-existence" path="*/META-INF/*"
</source>
+These lines instruct the web server to reject any request with a URL that
contains the path /WEB-INF/
+or /META-INF/.
+
<p>
-Configuring Netscape to assign the NSAPI redirector only specific requests is
somewhat harder,
+Configuring the web server to assign the NSAPI redirector only specific
requests 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).
</p>
@@ -363,7 +356,7 @@ This requires a change to NameTrans port
<p>
As you can see the second configuration is more explicit, it actually
instructs
-Netscape to assign the redirector with only requests to resources under
+the web server to assign the redirector with only requests to resources under
<b>/examples/servlet/</b> and resources under <b>/examples/</b> whose name
ends with <b>.jsp</b>.
</p>
@@ -372,9 +365,9 @@ You can be even more explicit and provid
</p>
<source>
- NameTrans fn="assign-name" from="/examples/servletname" name="jknsapi"
+ NameTrans fn="assign-name" from="/examples/servlets/chat" name="jknsapi"
- Instructs Netscape to assign the redirector request whose URL-Path equals
/example/servletname
+ Instructs the web server to assign the redirector requests whose URL path
equals /example/servlets/chat
</source>
</subsection>
@@ -434,18 +427,18 @@ and in the <a href="../reference/workers
</section>
-<section name="Building NSAPI DLL redirector for Windows">
+<section name="Building the NSAPI redirector for Windows">
<p>
The redirector was developed using Visual C++ Ver.6.0, so having this
environment is a prereq if you want
-to perform a custom build. You should also have NES developer SDK
+to perform a custom build. You should also have web server developer SDK for
your version of the web server.
The steps that you need to take are:
<ul>
<li>
-Change directory to the nsapi plugins source directory.
+Change directory to the <code>native/netscape</code> source directory.
</li>
<li>
-Edit <b>nsapi.dsp</b> and update the include and library path to reflect your
own Netscape server installation
+Edit <b>nsapi.dsp</b> and update the include and library path to reflect your
own web server installation
(search for a <b>/I compiler</b> option and <b>/libpath</b> linker option)
</li>
<li>
@@ -453,37 +446,40 @@ Make the source with MSDEV
</li>
</ul>
<screendos>
-<notedos>Change directory to the nsapi plugins source directory</notedos>
-<typedos>cd c:\home\apache\jk\nsapi</typedos>
+<notedos>Change directory to the NSAPI redirector source directory</notedos>
+<typedos>cd c:\tomcat-connectors-xxx-src\native\netscape</typedos>
<notedos>Build the sources using MSDEV</notedos>
<typedos>MSDEV nsapi.dsp /MAKE ALL</typedos>
</screendos>
</p>
<p>
If msdev is not in your path, enter the full path to msdev.exe.
-This will build both release and debug versions of the redirector plugin.
+This will build both release and debug versions of the NSAPI redirector plugin.
An alternative will be to open the nsapi workspace file (nsapi.dsw) in msdev
and
build it using the build menu.
</p>
+<p>
+After the build, you will have the required nsapi_redirect.dll plugin.
+</p>
</section>
-<section name="Building NSAPI so plugin redirector for Unix">
+<section name="Building the NSAPI redirector for Unix">
<p>
The redirector requires either gcc (Linux) or gcc or the Sun cc compiler
(Solaris).
The steps that you need to take are:
<ul>
<li>
-Change directory to the nsapi plugins source directory (src/native).
+Change directory to the <code>native</code> source directory.
</li>
<li>
-configure for Netscape/iPlanet/SunONE webserver.
+configure for the iPlanet Web Server.
</li>
<li>
-Change directory to the nsapi netscape directory (./netstape).
+Change directory to the <code>netscape</code> sub directory.
</li>
<li>
Set environment variables JAVA_HOME resp. SUITSPOT_HOME to the location of
your Java installation
-resp. Netscape server installation. Depending on the web server version, you
must add the subdirectory
+resp. web server server installation. Depending on the web server version, you
must add the subdirectory
"plugins" to SUITSPOT_HOME.
The variable is correct, if the file $SUITSPOT_HOME/include/nsapi.h exists.
</li>
@@ -497,11 +493,11 @@ Make the source with gmake.
</li>
</ul>
<screendos>
-<notedos>Change directory to the nsapi plugins source directory</notedos>
+<notedos>Change directory to the NSAPI redirector source directory</notedos>
<typedos>cd /usr/local/src/tomcat-connectors-xxx-src/native</typedos>
-<notedos>configure for Netscape/iPlanet/SunONE webserver</notedos>
+<notedos>configure for iPlanet Web Server</notedos>
<typedos>./configure --enable-netscape</typedos>
-<notedos>Change directory to the nsapi netscape directory</notedos>
+<notedos>Change directory to the netscape directory</notedos>
<typedos>cd netscape</typedos>
<notedos>Set JAVA_HOME (ksh example)</notedos>
<typedos>export JAVA_HOME=/path/to/my/java</typedos>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
