I thought this task was going to be harder than it actually was. I always found configuring the plug-in on IIS6 a bit hit and miss so expected more issues with IIS7.
I’ve not done this on any server products yet, so this is just on Windows Vista Business SP2.
Install ISAPI Filters Module on IIS
The first thing you need to do is ensure that you have installed the ISAPI filters module on IIS as per the details here: ISAPI Filters Module Installation
Just go down to the “How To” section of that page.
When you start the IIS configuration manager in Vista, you should end up with a screen which looks something like this, with the two new shortcuts for ISAPI configuration
You should have a default website enabled, and I’m going to assume that you want to proxy ALL requests which hit this IIS server through to a WebLogic server.
I’m also going to assume that you have a working IIS proxy configuration on an older version of IIS and are just moving to 7 as I don’t want to get into the nuts and bolts of configuring the IIS proxy!
The first thing I did was to set the home directory for my “Default Web Site” to be a folder where my iisforward.dll, iisproxy.dll & iisproxy.ini files were located. For this article I will assume this folder is c:\domains\iisplugin.
You get to this using the following screens using the right-click.
Select the advanced settings option and then set the property “Physical Path” to something like
Now, select the default web site and double click on the ISAPI Filters shortcut
You’ll be presented with an empty list. From here, if you right click and select Add, you’ll get the following.
Enter the following:
Filter Name: wlforward
Once that’s done, go back to the default website home, so you get the following screen
Double click, Handler Mappings and you’ll see something like this
From this screen, if you right click and select “Add Script Map”
you’ll get a screen as shown
Enter the following:
Request Path: *.wlforward
Name: IIS Proxy
You should then get a dialog box displayed which you should answer YES to.
Once you’ve done that, restart IIS and provided that the iisproxy.ini file is configured correctly, you should be able to access your weblogic server application.