Technical data

Proxying Multiple Virtual Websites from IIS
Administration Guide 12-7
Note: The only time you need to use HTTP-tunneling is when you connect
through an applet through IIS/NES to WebLogic Server and and use http
as the protocol instead of t3. (For example, http:// as the protocol in the
provider URL instead of t3://.)
12. Set any additional parameters in the
iisproxy.ini file. A complete list of
parameters is available in the appendix “General Parameters for Web Server
Plug-Ins” on page -2.
13. If you are proxying servlets from IIS to WebLogic Server and you are not
proxying by path, please read the section “Proxying Servlets from IIS to
WebLogic Server” on page 12-12.
Proxying Multiple Virtual Websites from
IIS
To proxy multiple Websites (defined as virtual servers in IIS) to WebLogic Server:
1. Create a new directory for each virtual server. This directory will contain
dll and
ini files used to define the proxy.
2. Copy
iisforward.dll to each of the directories you created in step1.
3. Register the iisforward.dll for each Website with IIS.
4. Create a file called
iisforward.ini. Place this file in the same directory that
contains
iisforward.dll. This file should contain the following entry for each
virtual website defined in IIS:
vhostN=websiteName:port
websiteName:port=dll_directory/iisproxy.ini
Where:
l N is an integer representing the virtual website. The first virtual website you
define should use the integer 1 and each subsequent website should
increment this number by 1.
l websiteName is the name of the virtual website as registered with IIS.