Cna't get IIS 4.0 to WebLogic 6.0 proxying to work

Question

          Hi all,
          It seems this post adds to many similar ones - the issue being that of successfully
          deploying iisproxy.dll, iisforward.dll and iisproxy.ini. I have IIS 4.0 running
          on NT 4.0 Server, and WebLogic 6.0 SP1 running on a seperate machine under Windows
          2000.
          I can proxy by file type no problem, it's proxying by path/proxying servlets that's
          biting me.
          I have followed the instructions at http://e-docs.bea.com/wls/docs60/adminguide/isapi.html#100367.
          Here are the instructions and what I've done in response to them:
          "1. Place the iisforward.dll file in the same directory as the iisproxy.dll file
          and add the iisforward.dll file as a filter service in IIS"
          I copied iisforward.dll and iisproxy.dll from my weblogic machine to C:\WINNT\system32\inetsrv
          on the IIS machine.
          I added iisforward.dll as a filter service in MS Management Console by choosing
          properties > ISAPI FIlters tab > Add. Here I browsed to iisforward.dll and named
          the filter WebLogic Filter Servlet (The name is not important, right?)
          "2. Register .wlforward as a special file type to be handled by iisproxy.dll."
          So, in MS Management Console I chose properties > home directory > Configuration
          > Add and browsed to iisproxy.dll and registered it with the file type .wlforward.
          "3. Define the property WlForwardPath in iisproxy.ini. WlForwardPath defines the
          path that is proxied to WebLogic Server."
          So I added the following line to iisproxy.ini on the WebLogic machine AND on the
          IIS machine:
          WLForwardPath=/CIM2WebApplication
          My web app is in exploded directory form at E:\bea\wlserver6.0sp1\config\terrance\applications\CIM2WebApplication
          (where CIM2WebApplication is the root directory of the app in which WEB_INF and
          my jsps and html files are located.)
          In addition, in web.xml, I have defined a servlet as follows:
          <servlet>
          <servlet-name>register</servlet-name>
          <servlet-class>net.companyname.cimsweb.RegisterUser</servlet-class>
          </servlet>
          <servlet-mapping>
          <servlet-name>register</servlet-name>
          <url-pattern>/register</url-pattern>
          </servlet-mapping>
          (Excuse all this the verbosity, but hopefully no-one will wonder what exactly
          I did!)
          When I use the following URL http://iiserverip/CIMS2WebApplication/register I
          get a 404 from IIS (i.e. nothing at all is getting proxied to WL, not even a wrong
          url)
          OK, I've finished! If someone would like to catch their breath and help me out
          I'd be extremely grateful! Thanks so much.
          Terrance
          

Answer 1

"V. Bell" wrote:
>>> I'm running Windows NT 4.0 (SP6). I have a AT-MIO-16E-10 board and I'm>>trying
to use it with NIDAQ 6.7, which should support that board, according>>to
the NIDAQ "readme" file. I followed all of NI's troubleshooting tips>on>>their
website, but nothing works: Windows NT completely ignores the board.>>I
have exactly the same problem with the same board and NT 4 (using NIDAQ>6.5.1).
The driver for NT is installed, but Biobench does not recognise the>card
is installed. The various instructions for configuring the board do>not seem
to be relevant under NT as no such option is given. The NT plug>and play
driver is installed and active and the BIOS is set to recognise>plug and
play cards.>>>>
V. Bell,
Since this board is a plug and play device, Windows needs to recognize it
when the board is first installed. One of the major issues here is that
Windows NT was not originally plug and play. ISAPNP is supposed to take
care of this. One thing you can double check is to make sure that you have
the following path when you go to edit your registry by typing 'regedt32'
from the Start>>Run prompt: HKEY_LOCAL_MACHINE >> SYSTEM >> CurrentControlSet
>> Enum >> ISAPNP .
Many times even though PnP ISA shows as being enabled under Devices it still
may not be installed properly and the ISAPNP directory will not appear in
the above path. To insure that it has been installed properly, reinstall
the driver from your Windows NT system CD from the \Drvlib\Pnpisa\X86 directory.
You may then try booting the machine without the board installed once and
then shut the machine down again and install the board and reboot.
Regards,
Craig Claassen
Applications Engineer
National Instruments