Installing and Configuring the Microsoft Internet Information Server Plug-In
To install the Microsoft Internet Information Server Plug-In:
Copy the iisproxy.dll and iisforward.dll files from
"<your servers drive letter>:\bea\weblogic81\server\bin" directory to
"<your servers drive letter>:\bea\click2gov\common"
Start the IIS Internet Service Manager by selecting it from the Microsoft IIS Start menu.
In the left panel of the Service Manager, select your website (the default is "Default Web Site").
Stop the website by Selecting Action from the menu and then "Stop" from the drop down menu list.
Open the Properties for the selected website by holding the right mouse button down over the website selection in the left panel and clicking the "Properties" menu option. The Web Site Properties form will be displayed.
In the Properties panel, select the Home Directory tab (1), and click the Configuration(2) button in the Applications Settings section. The Application Configuration form will be displayed.
On the configuration form click on the "Add" button (3). The Add/Edit Application Extension form will be displayed.
On the Add/Edit Application Extension Mapping form click on the browse button (4) and find the iisproxy.dll file. It should be located at: "<your servers drive letter>:\bea\click2gov\common"
In the "Extension" field, type "wlforward". Then click the "OK" button. In the Application Configuration form, the wlforward extension should now be listed. Close this form by clicking the "OK" button. You should now be back at the Web Site Properties form.
Click on the ISAPI Filters tab and add the iisforward.dll file as a filter service.
Create the "IISProxy.ini" file
The iisproxy.ini file contains name=value pairs that define configuration parameters for the plug-in. The parameters are listed in General Parameters for Web Server Plug-Ins.
Note: Changes in the parameters will not go into effect until you restart the "IIS Admin Service" (under services, in the control panel).
BEA recommends that you locate the iisproxy.ini file in the same directory that contains the iisproxy.dll file.
<your servers drive letter>:\bea\click2gov\common
Sample .ini file
Use the text below to copy and paste into your own iisproxy.ini file.
[config]
WebLogicHost=htec2gdT (change this to your WebLogic server
hostname )
WebLogicPort=7001
ConnectTimeoutSecs=10
ConnectRetrySecs=2
WlForwardPath=
[end config]
Once you have created your own iisproxy.ini file review and change the following parameters as necessary:
WebLogicHost - The hostname of the WebLogic Server.
( usually, for click2gov, the same machine you are currently working on ).
WebLogicPort - The listen port configured in for your WebLogic Server. Default is 7001.
ConnectTimeoutSecs - Amount of time before a timeout occurs when IIS is attempting to forward a request to WebLogic.
ConnectRetrySecs - Amount of time to wait before attempting to send the request again.
WlForwardPath - The application paths for all installed Click2Gov applications. For example. If Click2GovCX is the only application installed. The path would be "/Click2GovCX,". If multiple applications were installed, the path may look like this:
"/Click2GovCX,/Click2GovBPPDA,/Click2GovTX,/Click2GovPZ,"
The application names should be entered as they are referenced by WebLogic. Meaning, that if you called Click2GovCX , "C2GCX30" when setting up the application in WebLogic, then the path would be "/C2GCX30,"
Save the iisproxy.ini file. We will need to re-start the IIS WebSite before the changes take effect.
Finally, start the website by Clicking on the Website in the Internet Services Manager. Select Action from the Internet Services Manager menu and then "Start" from the drop down menu list.
Once these configuration changes have been made to IIS, you should be able to acces the Click2Gov applications via the IIS Web Server.
Using SSL with the Microsoft Internet Information Server Plug-In
You can use the Secure Sockets Layer (SSL) protocol to protect the connection between WebLogic Server and the Microsoft Internet Information Server Plug-In. The SSL protocol provides confidentiality and integrity to the data passed between the Microsoft Internet Information Server Plug-In and WebLogic Server. In addition, the SSL protocol allows the Microsoft Internet Information Server Plug-In to authenticate itself to the Microsoft Internet Information Server to ensure that information is passed to a trusted principal.
The Microsoft Internet Information Server Plug-In does not use the transport protocol (http or https) to determine whether the SSL protocol will be used to protect the connection between the proxy plug-in and the Microsoft Internet Information Server. In order to use the SSL protocol with the Microsoft Internet Information Server Plug-In, configure the WebLogic Server instance receiving the proxied requests to use the SSL protocol. The port on the WebLogic Server that is configured for secure SSL communication is used by the Microsoft Internet Information Server Plug-In to communicate with the Microsoft Internet Information Server.
To use the SSL protocol between Microsoft Internet Information Server Plug-In and WebLogic Server:
WebLogicHost=myweblogic.com WebLogicPort=7002 SecureProxy=ON
Proxying Servlets from IIS to WebLogic Server
You can proxy servlets by path if the iisforward.dll is registered as a filter. You would then invoke your servlet with a URL similar to the following:
http://IISserver/weblogic/myServlet
To proxy servlets if iisforward.dll is not registered as a filter, you must configure servlet proxying by file type.To proxy servlets by file type:
http://www.myserver.com/virtualName/anyfile.ext
where virtualName is the URL pattern defined in the <servlet-mapping> element of the Web Application deployment descriptor (web.xml) for this servlet and ext is a file type (extension) registered with IIS for proxying to WebLogic Server. The anyfile part of the URL is ignored in this context.