The attached TXT file is what I used to get it to work for me. I wrote it step by step when I was configuring my server here.

I kept getting errors with the ISAPI_Redirector2.dll file, so I went back to the older version and it worked fine for me with Tomcat 5.0.12

The TXT file is a little sparse and not 100% cleaned up, but you should get the general idea.

Whenever I tried to use the ISAPI2 redirector, it would just come back with a Server connection or DNS error, but when I changed it to the older version of the ISAPI DLL, it worked fine.

See if this helps you at all.

Richard Norman
Web/Application Developer


----Original Message Follows---- From: "Januski, Ken" <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Subject: RE: IIS 5.1 and Tomcat 4 Date: Tue, 23 Sep 2003 14:31:36 -0400

Jon,

I think that the log is telling you just what it should. Tomcat looks for a
mapping of server name to servlet in web.xml. So it won't find one for
localhost or machine name but that's really not important. It will find
nothing for them and move on. What it should find and does is the mapping
from servlet name to servlet. So it seems to me that it is finding the
mapping correctly. The problem is that nothing is happening after that.

Have you looked at the IIS logs to see what they say? They should include
line for isapi_redirect or isapi_redirecto2.dll and SHOULD have a 200 as
server response, e.g.

POST /jakarta/isapi_redirector2.dll - 200 0 4096 690

When I was trying this it took me forever to get it to change from 400/500
to 200 I believe. Unfortunately this won't solve your problem but it may
move you further toward a solution.

Ken

-----Original Message-----
From: Jon Skeet [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 5:42 AM
To: Tomcat Users List
Subject: RE: IIS 5.1 and Tomcat 4


<snip log>


> It seems like /mobilizer/mobilizer/ finds its way through,
> but the path  /localhost/mobilizer/mobilizer doesn't. Is that correct?
What
> is the path starting with /localhost, is this really your intention?

There shouldn't be any path starting with /localhost. I'm visiting the
URL

http://localhost/mobilizer/mobilizer

but the localhost part is the servername, not the path.

This appears to be consistent with the log I get when I use the name of
the computer rather than localhost, eg:

[Tue Sep 23 10:40:11 2003]  [jk_uri_worker_map.c (351)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Tue Sep 23 10:40:11 2003]  [jk_uri_worker_map.c (368)]: Attempting to
map URI '/treebeard/mobilizer/mobilizer/'
[Tue Sep 23 10:40:11 2003]  [jk_uri_worker_map.c (456)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match

My guess is that it's something IIS is doing for the sake of virtual
hosting, but I wouldn't like to say for sure.

The /mobilizer/mobilizer path is the correct one - but I don't know why
it's then not getting any further than it is doing.

Jon

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


Sincerely,


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
{         Richard Norman          }
{      Big Brother "Jazzy"        }
{                                 }
{  "The Brother with the Smooth   }
{    moves and Mellow grooves"    }
{                                 }
{Kappa Alpha Psi Fraternity, Inc. }
{      Beta Omega Chapter         }
{                                 }
{  Nemesis - "Kan't Be Faded!!!"  }
{      Ace Klub - Fall 94         }
#################################
  "Training For Leadership!!!"
"Many are Kalled but Few are Chosen!!"

WebSite (new): http://Jazzynupe.no-ip.com

_________________________________________________________________
Add MSN 8 Internet Software to your existing Internet access and enjoy patented spam protection and more. Sign up now! http://join.msn.com/?page=dept/byoa
Install Tomcat to work with IIS as web server
[EMAIL PROTECTED]


step 1: Install Tomcat From my example I installed to c:\Tomcat\Tomcat-[version]

Step 2: Copy ISAPI extension to bin\ISAPI folder (you must create the ISAPI folder)
You can copy both versions if you wish for easy switching (isapi_redirector2.dll and isapi_redirect.dll)


Step 3: Create this folder as a web virtual directory named "jakarta" with "Run executables" permissions

******* In conf\server.xml file *******
Step 4: configure host to include IIS root as appBase
        ******* example *******
        <Host appBase="e:/inetpub/wwwroot" name="localhost">
        ***********************
        use forward slashes instead of back slashes for directory
        seperation.

Step 5: Include any other Application contexts you wish
******* example *******
<Context displayName="Tomcat Sample Applications" docBase="C:/Tomcat/Tomcat-5.0/webapps/jsp-examples" path="/jsp-examples" />
***********************


Step 6: configure the AJP 1.3 listener to listen on the port you require.
******* example *******
<Connector port="40100" protocol="AJP/1.3" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" redirectPort="8443">
***********************
Make a note of this port for use later.


******* In conf\catalina\localhost\admin.xml file *******
Step 7: set context of administration pages to the location of the admin JSP files
******* example *******
<Context displayName="Tomcat Administration Application" docBase="C:/Tomcat/Tomcat-5.0/server/webapps/admin" path="/admin" privileged="true">
***********************
The absolute path is best so that the appBase does not cause problems.


******* In conf\catalina\localhost\manager.xml file *******
Step 8: set context of management pages to the location of the manager JSP files
******* example *******
<Context displayName="Tomcat Manager Application" docBase="C:/Tomcat/Tomcat-5.0/server/webapps/manager" path="/manager" privileged="true">
***********************


******* In conf\jk2.properties file *******\
step 9: in jk2.properties file, make sure that the handler list is uncommented and the port you specified previously is set for the AJP 1.3 connection
******* example *******
# Set the desired handler list
handler.list=request,channelSocket
#
# Override the default port for the socketChannel
channelSocket.port=40100
channelSocket.address=localhost


        request.tomcatAuthentication=true
        ***********************

If you are using the newer JK2 ISAPI extension, follow the steps below (the isapi_redirector2.dll file).
(http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/jk2/installhowto.html)
******* In conf\workers2.properties file *******
Step10: in workers2.properties, configure the port you specified previously on the worker like in the example below. Also configure any URI mappings you want handled by the ISAPI DLL in the file as well.


******* example *******
# Example socket channel, override port and host.
[channel.socket:localhost:8019]
port=8019
host=127.0.0.1
# define the worker
[ajp13:localhost:8019]
channel=channel.socket:localhost:8019
# Uri mapping
[uri:/examples/*]
worker=ajp13:localhost:8019
***********************
In the example above, the port was specified as 8019, but that port could be any you wish.


******* In the registry *******
Step11: in the registry configure the following keys as listed here.
"HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0"
Once those keys are created (with the Tomcat installer for Windows, only the ISAPI and the 2.0 keys are not created), create string values as follows
serverRoot (should equal tomcat home directory), extensionUri (http path to ISAPI DLL file configured previously), workersFile (path to workers2.properties file), logLevel (one of 3 levels, DEBUG, INFO or ERROR)


If you are using the older version of the ISAPI extension follow the steps here (the isapi_redirect.dll file).
(or do both and you can switch between the two if you have issues)
******* In conf\workers.properties file *******
Step10: The workers.properties file tells the ISAPI extension how to connect to Tomcat running in the background.


        ******* example *******
        workers.tomcat_home=C:\Tomcat\Tomcat-5.0
        workers.java_home=C:\JDK\j2sdk1.4.2_01
        ps=\
        worker.list=ajp13
        worker.ajp13.port=40100
        worker.ajp13.host=localhost
        worker.ajp13.type=ajp13
        worker.ajp13.lbfactor=1
        ***********************

******* In conf\uriworkermap.properties file *******
step11: The uriworkermap.properties file tells the ISAPI extension the actual paths and file perameters that are sent to the Tomcat process from the ISAPI extension.


        ******* example *******
        default.worker=ajp13
        /jsp-examples/*.jsp=$(default.worker)
        /*/*.jsp=$(default.worker)
        ***********************

******* In the registry *******
Step12: in the registry configure the following keys as listed here.
"HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0"
Once those keys are created (with the Tomcat installer for Windows, only the ISAPI and the 1.0 keys are not created), create string values as follows
serverRoot (should equal tomcat home directory), extension_uri (http path to ISAPI DLL file configured previously), log_file (path and filename where logfile should be created), worker_file (path to workers.properties file), worker_mount_file (path to uriworkermap.properties file), log_level (one of 4 levels, debug, info, error, or emerg)


******* In IIS *******
step : Configure an ISAPI extension named anything you wish. As the executable select the ISAPI redirector you wish (isapi_redirector2.dll or isapi_redirect.dll).


step : once complete, try to navigate to a JSP context you configured (such as /admin or /jsp-examples)

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

Reply via email to