I’ve been searching high and low for a couple of weeks but can’t find anything that helps with the problem I’m having. I have a Weblogic ISAPI filter registered on IIS6 (Win2k3 Server). Everything seems to be working with Weblogic, specifying port 7001 (default Weblogic port) on the URL works but the filter doesn’t seem to be working. I have checked the .ini file to make sure that the right port and forward path. The filter has a green arrow on IIS but I am getting a “page cannot be displayed” when the url is called without specifying the port. There are no errors in Event Viewer.
Since you seem to have a lot of knowledge about how ISAPI filters work in IIS, please point me in the right direction. Any help is greatly appreciated. Thank you!
Unfortunately, the correct answer here is for you to contact product support for WebLogic to determine if your version of WebLogic supports running on IIS6 and if so, what is the proper configuration. For a supported product configuration, WebLogic is obligated to give you this information. We should not be figuring this out at all.
It seems like the WebLogic filter is supposed to be stealing requests from IIS, forwarding a new request to port 7001, and then reverse-proxy the response back to the client. The green arrow simply indicates that at some point in the past, IIS6 successfully loaded the DLL as an ISAPI Filter. Obviously, it says nothing about whether the Filter logically functions, but then again, that is the responsibility of the filter, not IIS.
Now, you say that the filter is not working and you have not found obvious errors, log files, nor event log entries from WebLogic. Seems like your problem is with the undebuggable (to you) WebLogic filter and not with IIS.
I hope you understand that:
- When you have a question involving a product, you are supposed to first contact that product’s support personnel. There may be a monetary cost involved, but that is what you paid (or not paid) for.
- Unless you have paid support, all other forms of support are basically best-effort.
- I am not a free-substitute for a product support call. I know how IIS and its ISAPI Filter API works. I know nothing about how an arbitrary ISAPI Filter DLL works. Sure, I may be curious about some aspect of the issue and debug/reverse-engineer to figure out how a given arbitrary WebLogic ISAPI Filter is failing, but I really should not be doing that. That is what WebLog product support is *supposed* to do for you.