tomcat and iis

I had to look into some configuration issues which I had been delaying for the past few weeks. How to get iis to play nice with tomcat such that you can have two virtual iis servers forward stuff to one tomcat with again two virtual servers.
We have two tomcat applications that we need to shield from the outside world with a webserver like apache or iis. How this works is that the webserver forwards some urls to tomcat and acts as a proxy for those urls.

This is pretty routine stuff, the only problem is that it is not documented how one should do this. And lets face it, the apache jakarta people write beautiful code but their documentation is typically not that good. You can get started easily but the advanced stuff is understandably not documented well. I say understandably because I understand that developers have other priorities (like getting things to work) but still, it’s bloody unusable now.

But I figured it out today thanks to this page: http://tjworld.net/help/kb/0001_iis6-Tomcat5-JK2.html#conConnector. This page contained all the necessary information to get me started. I followed the instructions to the letter and ended up with a working iis-tomcat setup. From there it was easy, just add a few hosts to the tomcat server in server.xml (I’m going to experiment with the alias tag later on) and add a bunch of iis virtual services (all with the isapi filter active) for each of the tomcat hosts. Works just fine. I knew all along that it was possible to do this and now I have the proof :-).

subclipse

For the zillionth time I decided to spend some time trying to get subclipse (http://subclipse.tigris.org/) to play nice with our svn+ssh repository at work. For those scratching their heads: eclipse is a popular java development ide; subversion is a version management system and subclipse is a subversion backend for eclipse’s team synchronization functionality. Until recently subclipse did not support subversion repositories secured with ssh, which unfortunately is a very common type of subversion repsository (and also very easy to setup). So, no subclipse. The reason was that subclipse depends on a native subversion library which in turn depends on the presence of ssh. That’s a lot of dependencies and it doesn’t work without a lot of tinkering and even then it may not work.

But the good news is that the guys at http://tmate.org fixed things for the subclipse guys by providing a java only implementation of the svn library. I installed it today and it works beautifully. The eclipse team synchronization stuff looks really useful and with subclipse finally working I can now put it to work.