The following sections describe how to install and configure the Oracle WebLogic Server Proxy Plug-In for Microsoft IIS Web Server:
Download the Oracle WebLogic Server Proxy Plug-In for IIS Web Server, as described in Section 1.2, "Availability of Oracle WebLogic Server Proxy Plug-In 12c (12.2.1)." The zip file contains these files:
Information specific to the distribution, late-breaking updates, and other errata.
orapki tool for configuring Oracle wallets
orapki helper Java libraries
WebLogic proxy module
This section describes how to install and configure the plug-in for Microsoft IIS 7.0.
This section describes how to set up the Microsoft Internet Information Server plug-in for IIS 7.0.
To set up the Microsoft Internet Information Server plug-in for IIS 7.0, follow these steps:
Download and install Microsoft IIS 7.0.
Ensure that all of the necessary features of Microsoft IIS 7.0 are enabled.
Download and install the latest Oracle WebLogic Server Proxy Plug-In zip file.
Create a web application in IIS Manager by right clicking on Web Sites > Add Web Site.
Fill in the Web Site Name with the name you want to give to your web application; for example,
MyApp. Select the physical path of your web application Port (any valid port number not currently in use).
Click OK to create the web application.
If you can see the name of your application under Web Sites it means that your application has been created and started running. Click the MyApp node under Web Sites to see all of the settings related to the MyApp application, which you can change, as shown in Figure 5-1.
Click Handler Mappings to set the mappings to the handler for a particular MIME type.
Click the StaticFile and change the Request path from * to *.*. Click OK.
Click MyApp and then click Add Script Map on the right-hand side menu options. Enter * for the Request path.
Browse to the iisproxy.dll file and add it as the executable. Name it
Click Request Restrictions and deselect Invoke handler only if the request is mapped to.
Click OK to add this Handler mapping. Click Yes on the Add Script Map dialog box.
To configure proxying by path, see Section 5.1.3, "Using Wildcard Application Mappings to Proxy by Path".
Click the Root node of the IIS Manager tree and click the ISAPI and CGI Restrictions. Make sure to check Allow unspecified ISAPI modules.
Create a file called iisproxy.ini with the following contents and place it in the directory with the plug-in:
WebLogicHost= @hostname@ WebLogicPort= @port@ ConnectRetrySecs=5 ConnectTimeoutSecs=25 Debug=ALL DebugConfigInfo=ON KeepAliveEnabled=true WLLogFile=@Log file name@ SecureProxy=OFF
Open the Internet Explorer browser and enter
http://<hostname>:<port>. You should be able to see the Medrec Sample Application from your Oracle WebLogic Server.
To run the plug-in SSL mode, change the value of WeblogicPort to the SSL port of your application, change the
SecureProxy value to ON, and set
WLSSLWallet to the location of the wallet. For more information on SSL parameters, see Section 8.2, "SSL Parameters for Web Server Plug-Ins".
Follow these steps to have IIS serve all static content that could be included on a web application that is to be served by WebLogic Server.
Configure your application by setting up Oracle WebLogic Server Proxy Plug-In for Microsoft IIS Web Server on IIS Web Server as described in Section 5.1.1, "Installing and Configuring the Microsoft IIS 7.0 Plug-In."
Assume that you created a Handler Mapper named proxy as described in the Oracle documentation.
Important:Do not use
WLEXCLUDEPATHORMIMETYPEproperty inside your proxy setup. It is not required neither useful here and can only confuse the understanding of the flow.
In IIS Manager, display the home page by clicking the Virtual Directory or Application created in Step 1.
Double-click the Handling Mappers and then click View Ordered List on the right side pane. An ordered list of Handler Mappings appears.
Select proxy and drag it below StaticFile handler mapping (in other words the StaticFile handler mapping should appear above the proxy handler mapping.)
Edit the Static File and change the request path to: *.jpg. Save the file.
Configure IIS to serve types of static files, for example, PNGs, GIFs, or CSS files.
On IIS Manager, display the home page by clicking the Virtual Directory or Application created in Step 1.
Double click the Handling Mappers and then click Add Module Mapping on the right side pane.
Choose a Request Path of desired type: for PNGs use *.png, for GIFs use *.gif and so on. For Module, choose StaticFileModule, enter a name, and click OK.
You can configure a website or virtual directory to run an Internet Server API (ISAPI) application at the beginning of every request to that website or virtual directory, regardless of the extension of the requested file. You can use this feature to insert a mapping to iisproxy.dll and thereby proxy requests by path to WebLogic Server.
The following steps summarize the instructions available at "Add a Wildcard Script Map" for IIS (
http://technet.microsoft.com/en-us/library/cc754606(WS.10).aspx) to add a wildcard script map to do proxy-by-path with ISAPI in IIS:
Open IIS Manager and navigate to the level you want to manage.
For information about opening IIS Manager, see "Open IIS Manager" at
For information about navigating to locations in the UI, see "Navigation in IIS Manager" at
In Features View, on the server, site, or application Home page, double-click Handler Mappings.
On the Handler Mappings page, in the Actions pane, click Add Wildcard Script Map.
In the Executable box, type the full path or browse to the
iisproxy.dll that processes the request. For example, type
In the Name box, type a friendly name for the handler mapping.
Optionally, on the Handler Mappings page, select a handler to lock or unlock. When you lock a handler mapping, it cannot be overridden at lower levels in the configuration. Select a handler mapping in the list, and then in the Actions pane, click Lock or Unlock.
After you add a wildcard script map, you must add the executable to the ISAPI and CGI Restrictions list to enable it to run. For more information about ISAPI and CGI restrictions, see "Configuring ISAPI and CGI Restrictions in IIS 7" at
Note:If you are proxying a request to multiple IIS applications within the same IIS site, to prevent the subsequent request from proxying to the first website only, create each IIS application and assign a unique application pool to each IIS application.
With IIS 7.x, you cannot assign application pools to virtual directories.
To proxy requests from multiple websites (defined as virtual directories in IIS) to WebLogic Server:
Create a new directory for the virtual directories. This directory will contain .dll and .ini files used to define the proxy.
Extract the contents of the plug-in .zip file to a directory.
For each virtual directory you configured, copy the contents of the plug-in \lib folder to the directory you created in step 1.
Create an iisproxy.ini file for the virtual websites, as described in Section 220.127.116.11, "Sample iisproxy.ini File". Copy this iispoxy.ini file to the directory you created in Step 1.
Copy iisproxy.dll to the directory you created in Step 1.
Create a separate application pool for each virtual directory.
As described in "Creating Application Pools (IIS 6.)" (
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/93275ef2-2f85-4eb1-8b92-a67545be11b4.mspx?mfr=true), you can isolate different Web applications or websites in pools, which are called application pools. In an application pool, process boundaries separate each worker process from other worker processes so that when an application is routed to one application pool, applications in other application pools do not affect that application.
Note:Step 6 only applies to IIS 6.0 as there is no Application Protection option with IIS 7.0.This step will work with IIS 7.0, except that exactly one IIS virtual directory exists within a particular IIS site. The limitation exists because, with IIS 7.0, it is impossible to assign a unique application pool to each virtual directory, thus the subsequent requests are always proxied to the first
The following sample iisproxy.ini file can be used with a single, non-clustered WebLogic Server. Comment lines are denoted with the "#" character.
# This file contains initialization name/value pairs # for the IIS/WebLogic plug-in. WebLogicHost=localhost WebLogicPort=7001 ConnectTimeoutSecs=20 ConnectRetrySecs=2
The following sample iisproxy.ini file can be used with clustered WebLogic Servers. Comment lines are denoted with the "#" character.
# This file contains initialization name/value pairs # for the IIS/WebLogic plug-in. WebLogicCluster=myweblogic.com:7001,yourweblogic.com:7001 ConnectTimeoutSecs=20 ConnectRetrySecs=2
Note:If you are using SSL between the plug-in and WebLogic Server, the port number should be defined as the SSL listen port.
ACLs will not work through the Oracle WebLogic Server Proxy Plug-In 12c (12.2.1) for Microsoft IIS Web Server if the Authorization header is not passed by IIS. Use the following information to ensure that the Authorization header is passed by IIS.
Ensure that the user is logged on with local log-on rights when using Basic Authentication.
Grant each user account the Log On Locally user right on the IIS server. To enable the use of Basic Authentication, Two problems may result from Basic Authentication's use of local logon:
If the user does not have local logon rights, Basic Authentication does not work even if the FrontPage, IIS, and Windows NT configurations appear to be correct.
A user who has local log-on rights and who can obtain physical access to the host computer running IIS will be permitted to start an interactive session at the console.
To enable Basic Authentication, in the Directory Security tab of the console, ensure that the Allow Anonymous option is "on" and all other options are "off".
Follow these steps to ensure that the Microsoft IIS plug-in has been installed, configured, and deployed successfully.
Make sure WebLogic Server and IIS are running.
Save a JSP file into the document root of the default Web Application.
Open a browser and set the URL to the IIS plus filename.jsp, as shown in this example:
If filename.jsp is displayed in your browser, the plug-in is functioning.
This section describes how to install and configure the plug-in for Microsoft IIS 7.5.
Follow these steps to install and configure the Microsoft IIS 7.5 Plug-In.
Install Microsoft IIS 7.5.
Ensure that all of the necessary features of Microsoft IIS 7.5 are enabled.
From the Start menu, choose Control Panel, then Programs and Features. Select Internet Information Services (IIS) 7+ Manager. Click Turn Windows features on or off.
Expand the entire tree beneath Internet Information Services and ensure all of the subfeatures are selected.
Download and install the latest Oracle WebLogic Server Proxy Plug-In zip file.
iisproxy.ini file with the following content in the
WebLogicHost=URL_of_WebLogic_Host WebLogicPort=WebLogic_Port Debug=ALL DebugConfigInfo=ON WLLogFile=C:\Temp\wl-proxy.log
Ensure that the
%\lib folder is included in the system
PATH (select Control Panel, then System, then System Properties, then Environment Variables, then System Properties, then PATH).
Open IIS Manager (select Start, then All Programs, then Administrative tools, then Internet Information Services Manager).
Create a new Web Site in IIS. See the IIS Help system for more information.
Click the site name, open Handler Mappings and add a script map (set the Extension to a value such as
.jsp, set Executable to
\iiproxy.dll, and assign a value to Name).
Click MIME Types and ensure a MIME type has been defined for the extension. Add the MIME type and its definition if it is not present.
Click the site name, open Directory browsing and enable the feature.
Start IIS (enter
services.msc at the command prompt and go to "World Wide Web Publishing Services" at the bottom and restart it. Also restart the web site).
Test your configuration by sending a request to
/ from the browser and validate the response.
iishost is the URL of the IIS server and
iisport is the port number. Note that the iisport number should be different from the port number of the WebLogic Server.
After configuring the WLS plug-in and confirming it works (see Section 5.2.1, "Installing and Configuring the Microsoft IIS 7.5 Plug-In") follow these steps to serve static files.
Right click Default web site and then click Add Virtual Directory.
In the Alias field enter
static and set the physical path to the location of the static files, for example
c:\inetpub\wwwroot\static. Click OK. A static folder will appear under Default Web Site.
Note: The physical path may be different in your case if the files are in a different location. Modify the path accordingly.
Click static under Default Web Site to open the static Home page.
On the static Home page click Handler Mappings and then click View Ordered List on the right-side pane. You will see an ordered list of Handler Mappings.
Click Add Script Map. Set Request Path to "*", set Executable to
\iiproxy.dll, and assign the value
proxy to Name). Click OK.
Click View Ordered List to re-order the list of handlers.
Click the proxy script map and move it down below the StaticFile handler mapping. (That means the StaticFile handler mapping should appear above the proxy handler mapping.)
static folder under
c:\inetpub\wwwroot and copy an HTML file into it, for example
Restart IIS 7.5 by restarting the "World Wide Web Publishing Service" under services (see Figure 5-11).
Test your work. Access the
index.html file by accessing:
Suppose you want to serve the static files such as
*.png images for the request "http://localhost:80/console" from the IIS and other dynamic content from the backend WebLogic Server. Follow these steps in addition to Section 5.2.2, "Serving Static Files with IIS 7.5."
Complete the steps described in the Section 5.2.2, "Serving Static Files with IIS 7.5."
Right-click the "Default web site", then click "Add Virtual Directory", and then enter the following in the Add Virtual Directory dialog box.
In this example, the physical path to the console is
Click OK. You will see a "
console" entry in the left pane under the Default Web Site.
Click "console" under "Default Web Site". A "console Home" will open on the right side.
Click "Handler Mappings" on the "console Home" pane
Right-click StaticFile and select Edit.... Update the fields as follows in the Edit Module Mapping dialog box:
Request Path—*.png (that is, change "*" to "*.png")
Module— StaticFileModule, DefaultDocumentModule, DirectoryListingModule (should be the default)
Executable—not required. Leave it blank.
Name—StaticFile (it is not possible to change Name here)
Click Request Restrictions. In the Mapping tab of the Request Restrictions dialog box, ensure that Invoke Handler only if the request is mapped to is selected, then select File or Folder. Click OK and OK to dismiss the dialog boxes.
The above step is to serve the *.png from the IIS server.
To serve other image files, such as *.gif files, do the following.
Under "Console Home" click "Handler Mappings", then click on "Add Module Mapping" on the right side and then enter the following.
Module—StaticFileModule, DefaultDocumentModule, DirectoryListingModule
Executable—not required. Keep it blank
Click "Request Restrictions". Under "Mapping" make sure the "Invoke Handler only if the request is mapped to" is selected and then select the "File or Folder" and then click "OK" and "OK"
Arrange the order of the handlers.
Click on "console" under "Default web site" and then click on "Handler Mappings" and then "View Ordered List" on the right side
Select "proxy" and move it down till the "proxy" is below the "StaticFile" and "StaticFileForGIF. That is, the order should be like below.
StaticFile StaticFileForGIF proxy
Copy all of the static files that belong to
/console request from WebLogic Server to IIS.
Restart the service, then restart the web site.
The images (
*.gif) are now served by IIS and dynamic content by Weblogic server.
For example, for the request
http://localhost:80/console the images for console are served by the IIS and all other requests other than
*.gif are served by Weblogic Server.