Hello, we've been tasked with fowarding some requests to our IIS6 sharepoint server to tomcat 5.5 for use with SSO for other Tomcat based authentication. The SSO piece of the puzzle is working fine. However, the request forwarding we are having major problems with.
We first installed Tomcat 5.5 and the Connecter 1.2.28 on a clean VMWare image running WSS 3.0. The connector worked flawlessly here, and the requests were forwarded appropriately, and the logs were generated. After the test run, we moved to our actual Sharepoint dev servers. We followed the same process to install the connector, as Tomcat itself was already installed, and then tweaked the configuration file to match the new environment. It came back with a 404 error for the contexts that should have been fowarded. We then attempted to make the two enviorments the same as far as Tomcat was concerned, moving the tomcat files from the location they were at on the working server. We then updated the configuration files to match the moved location of tomcat, as well as updating the Virtual Directory and ISAPI directory locations. After restarting both IIS and Tomcat, we were still given the same 404 error when accessing the forwarded contexts. We also tried a server restart at this point. After that failed, we tried making the configuration files identical to the ones from the working server, making sure that the contexts fowarded were the same (cutting the SSO servlet out of the picture). Still, it failed to work with the same symptoms. At this point, we decided to verify that the tomcat server installed could be accessed from the working server. We updated the configuration files on the clean box to forward to the dev server's IP address. Once that was done, we were able to forward requests to IIS on the clean box to the Tomcat instance on dev box. After this, we tried setting up the connector on several other dev boxes, and we were successful on none of them, using the identical configuration as the clean, working server. At this point, we started trying some more exotic solutions, including creating simple IIS websites without Sharepoint installed on the failing boxes, which produced the exact same failed result. We are using the properties file approach for the isapi_redirect.dll, rather than the registry. Below is the configuration from the only server that is working, as well as the configuration from one of the failing servers (as they are all identical). If anyone could give us a new place to look for the problem, we'd be appreciative, since without the log files, we're at a bit of a loss on where to go from here. isapi_redirect.dll (working): extension_uri=/jakarta/isapi_redirect.dll log_file=C:\tomcat\logs\isapi_redirect.log log_level=info worker_file=C:\tomcat\conf\workers.properties worker_mount_file=C:\tomcat\conf\uriworkermap.properties uriworkermap.properties (working): /admin/*=wlb /manager/*=wlb /servlets-examples/*=wlb /cas-server/*=wlb /jkmanager=jkstatus workers.properties (working): worker.list=wlb,jkstatus worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8009 worker.wlb.type=lb worker.wlb.balance_workers=ajp13w worker.jkstatus.type=status isapi_redirect.dll (failing): extentions_uri=/jakarta/isapi_redirect.dll log_file=C:\tomcat\isapi_redirect.log log_level=ALL worker_file=C:\tomcat\conf\workers.properties worker_mount_file=C:\tomcat\conf\uriworkermap.properties uriworkermap.properties (failing): /cas-server=wlb /cas-server/*=wlb /mywebapp=wlb /mywebapp/*=wlb /servlets-examples/*=wlb /jkstatus=jkstatus workers.properties (failing): worker.list=wlb,jkstatus worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8009 worker.wlb.type=lb worker.wlb.balance_workers=ajp13w worker.jkstatus.type=status
