IIS

Finally we come to IIS. IIS is a popular Web server in the Microsoft environment, though it still lags well behind Apache in terms of overall popularity. This section discusses the process of configuring WebLogic to work with IIS.

Installation

First you need to install the IIS extension. Under the directory in which IIS is installed, create a subdirectory called WebLogic . Copy the file iisproxy.dll from the /bin directory under your WebLogic server installation to that directory. Make sure that the new directory is accessible to IIS.

Next, select the Web instance on which you want to enable WebLogic from the left pane of your IIS service manager. Click the Play arrow in the toolbar to start the Web site. Right-click on the Web site and select Properties. Click on the Home Directory tab. Click the Configuration button.

To enable proxying, click on the App Mappings tab. Click the Add button and specify the file extensions that you want WebLogic server to handle. Click the Browse button and locate the iisproxy.dll file that you installed under the IIS directory. Make sure that the Script Engine check box is selected and the "Check that file exists" check box is not selected.

Configuration

Next, you need to create a configuration file that the IIS plug-in can use to find the servers to which it will be relaying requests . This file must be called iisproxy.ini . It is best to locate it in the same subdirectory as the IIS extension .dll file.

If you are proxying to a single server, the file should contain the name of the server and the port that the WebLogic server monitors for incoming requestsfor example:

 WebLogicHost=192.168.0.1 WebLogicPort=7001 

Note that the WebLogic server to which you are proxying may be on the local host, as in the example below. However, in production systems, it is best if the WebLogic server has its own more-or-less dedicated CPU.

 WebLogicHost=localhost WebLogicPort=7001 

If you are proxying to a cluster, you should use a WebLogicCluster directive in place of the WebLogicHost directive, as in the example below. The WebLogicCluster directive takes as a parameter a comma-separated list of all the members of the cluster. It will proxy to each member of the list in round- robin order.

 WebLogicCluster=NT4-server.com:7001,RHat72-server.com:7001 

IIS Proxying by Path

The phrase "proxying by path" means redirecting requests from your IIS server to a WebLogic server or cluster based on some characteristic of the path of the resource the client requested from the IIS server. Usually this means sending all traffic containing a particular character sequence (e.g., "/weblogic," "/dynamic") to the WebLogic server/cluster.

As with Apache and Netscape, you can do this with IIS but not with your IIS GUI.