Monday, January 29, 2007
IIS6 and Tomcat
This is a little bit off topic as OAM goes but everytime I want a quick OAM / Servlet container working environment, it takes me too long to discover this info. So, here it is in a nutshell:
The quickest, cheapest, most readily available solution to getting OAM up and running with a servlet container as the server side technology is to use IIS6 on Win2K3 and Tomcat 5.5. The crux is that you want to be able to stick a webgate in front of the container resources (by default, on port 8080). Now, there is a ton of info on the web about how to do this. But the one resource that you need is here:
http://wiki.apache.org/tomcat/Tomcat_and_IIS_Howto
There is an MSI package that will do most of the picky IIS and registry config for you (link near the top of the page)
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.15/isapi_redirect.msi
The setup program is a great help but there is one final detail (mentioned thanks to someone who added a note to the page) that reads:
The only other note I have is that all the documentation talks about the workers.properties file. Be aware that the setup program referenced here creates a file called workers.properties-minimal. This is ok as it also writes the same filename value into the registry. Just good to be aware that both the registry key and the filename need to jive before you go renaming it.
The quickest, cheapest, most readily available solution to getting OAM up and running with a servlet container as the server side technology is to use IIS6 on Win2K3 and Tomcat 5.5. The crux is that you want to be able to stick a webgate in front of the container resources (by default, on port 8080). Now, there is a ton of info on the web about how to do this. But the one resource that you need is here:
http://wiki.apache.org/tomcat/Tomcat_and_IIS_Howto
There is an MSI package that will do most of the picky IIS and registry config for you (link near the top of the page)
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.15/isapi_redirect.msi
The setup program is a great help but there is one final detail (mentioned thanks to someone who added a note to the page) that reads:
The setup file included here and the script to add the ISAPI filter work just fine in IIS6, but there is one additional step needed. You must also allow access to the filter through the Web Service Extensions part of IIS. To do this graphically, do the following:
1) open the IIS Manager and go to the Web Service Extensions item under the appropriate server 2) Click the "Add a new Web service extension" item under "Tasks" 3) Give it a name like "jakarta" 4) Browse to the isapi_redirect.dll file you installed above as a "Required File" 5) Check the box to enable this extension.
The only other note I have is that all the documentation talks about the workers.properties file. Be aware that the setup program referenced here creates a file called workers.properties-minimal. This is ok as it also writes the same filename value into the registry. Just good to be aware that both the registry key and the filename need to jive before you go renaming it.
