1. Using Oracle WebLogic Server Proxy Plug-Ins
  2. Configuring the Plug-In for Microsoft IIS Web Server

4 Configuring the Plug-In for Microsoft IIS Web Server

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 Availability of Oracle WebLogic Server Proxy Plug-In. The zip file contains the following files:

Table 4-1 Files Included in the Microsoft IIS Plug-In Zip

(path)/filename Description

README.txt

Information specific to the distribution, late-breaking updates, and other errata.

bin/orapki.bat

orapki tool for configuring Oracle wallets

jlib/*.jar

orapki helper Java libraries

iisproxy.dll

WebLogic proxy module

lib/*.dll

Helper libraries

WebLogic Server Proxy Plug-in 12.2.1.0.0 and later version builds are moved from Intel compiler to MSVC Compiler. When Microsoft IIS Web Server is used as a front end with WebLogic Server Proxy Plug-in, the plug-in library depends on the two dlls — msvcp110.dll and msvcr110.dll, provided by Microsoft. These dlls are available with Microsoft Visual C ++ 2012 Redistributable Package for x64.

For information about the specific versions of Microsoft IIS Web Server that are supported, see the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network.

Learn about how to install and configure the plug-in for Microsoft IIS Web Server in the following sections:

Installing and Configuring the Plug-In for Microsoft Internet Information Server

Microsoft Internet Information Server (IIS) plug-in is supported on Microsoft Windows client and Microsoft Windows server OS.

Refer to the following topics based on your use case:

Installing and Configuring the Plug-In for Microsoft IIS on Windows Client OS

Follow these steps to install and configure the Plug-In for Microsoft Internet Information Server (IIS) on Windows client OS:

  1. Install Microsoft IIS.

  2. Ensure that all of the necessary features of Microsoft IIS are enabled.

    1. In the Start menu, select Control Panel, and then select Programs and Features.

    2. Select Internet Information Services (IIS) Manager.

    3. Click Turn Windows features on or off.

    4. Expand the entire tree beneath Internet Information Services and ensure all of the sub-features are selected.

      Figure 4-1 Windows Features for Internet Information Services

      Description of Figure 4-1 follows
      Description of "Figure 4-1 Windows Features for Internet Information Services"

  3. Download and install the latest Oracle WebLogic Server Proxy Plug-In zip file.

  4. Create an iisproxy.ini file with the following content in the %PLUGIN_HOME%\lib\ folder: 

    WebLogicHost=URL_of_WebLogic_Host
    WebLogicPort=WebLogic_Port
    Debug=ALL
    DebugConfigInfo=ON
    WLLogFile=C:\Temp\wl-proxy.log

  5. Ensure that the %PLUGIN_HOME%\lib folder is included in the system PATH. (Select Control Panel, select System select System Properties, select Environment Variables, select System Properties, and then select PATH.

  6. Open IIS Manager. Select Start, select All Programs, select Administrative Tools, and then select Internet Information Services Manager.

  7. Create a new Web Site in IIS. See the IIS Help system for more information.

  8. Click the site name, open Handler Mappings and add a script map (set the Request Path to a value such as .jsp, set Executable to %PLUGIN_HOME%\lib\iisproxy.dll, and assign a value to Name).

  9. 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.

  10. Click the site name, open Directory browsing and enable the feature.

  11. 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.

    Figure 4-2 Windows Services Window

    Description of Figure 4-2 follows
    Description of "Figure 4-2 Windows Services Window"

  12. Test your configuration by sending a request to http://iishost:iisport/application_name/ from the browser and validate the response.

    Here, 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.

Installing and Configuring the Plug-In for Microsoft IIS on Windows Server OS

Follow the steps to install and configure the Plug-In for Microsoft Internet Information Server (IIS) on Windows Server OS:

  1. Open Server Manager. Click Manage and then click Add Roles and Features. This opens the Add Roles and Features wizard.
  2. On the Before you begin page, click Next.
  3. Select Role-based or feature-based installation as the installation type, and click Next.
  4. On the Select destination server page, select the appropriate server. The local server is selected by default. Click Next.
  5. In the list of Roles, enable Web Server (IIS), and click Next.
  6. Click Add Features on the confirmation window to add features that are required for Web Server (IIS).
  7. On the Select features page, click Next as no additional features are necessary to install the Web Adaptor.
  8. On the Web Server Role (IIS) dialog box, click Next.
  9. On the Select role services dialog box, verify that the web server components listed below are enabled, and click Next.
  10. Verify that your settings are correct and click Install.
  11. When the installation completes, click Close to exit the wizard.
  12. Download and install the latest Oracle WebLogic Server Proxy Plug-In zip file.
  13. Create an iisproxy.ini file with the following content in the %PLUGIN_HOME%\lib\ folder:
    WebLogicHost=URL_of_WebLogic_Host
    WebLogicPort=WebLogic_Port
    Debug=ALL
    DebugConfigInfo=ON
    WLLogFile=C:\Temp\wl-proxy.log
  14. Ensure that the %PLUGIN_HOME%\lib folder is included in the system PATH. (Select Control Panel, select System select System Properties, select Environment Variables, select System Properties, and then select PATH.
  15. Open IIS Manager. Select Start, select All Programs, select Administrative Tools, and then select Internet Information Services Manager.
  16. Create a new Web Site in IIS. See the IIS Help system for more information.
  17. Click the site name, open Handler Mappings and add a script map (set the Request Path to a value such as .jsp, set Executable to %PLUGIN_HOME%\lib\iisproxy.dll, and assign a value to Name).
  18. 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.
  19. Click the site name, open Directory browsing and enable the feature.
  20. 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.

    Figure 4-3 Windows Services Window

    Description of Figure 4-3 follows
    Description of "Figure 4-3 Windows Services Window"
  21. Test your configuration by sending a request to http://iishost:iisport/application_name/ from the browser and validate the response.
    Here, 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.

Serving Static Files with IIS

After configuring the WLS plug-in and confirming it works (see Installing and Configuring the Plug-In for Microsoft Internet Information Server) complete the following steps to serve static files:

  1. Right click Default web site and then click Add Virtual Directory.
  2. 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.

    Description of add_vir_dir.png follows
    Description of the illustration add_vir_dir.png
  3. Click static under Default Web Site to open the static Home page.
  4. 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.
  5. Click Add Script Map. Set Request Path to "*", set Executable to %PLUGIN_HOME%\lib\iisproxy.dll, and assign the value proxy to Name). Click OK.
  6. Click View Ordered List to re-order the list of handlers.
  7. 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.)
  8. Create a static folder under c:\inetpub\wwwroot and copy an HTML file into it, for example index.html.
  9. Restart IIS by restarting the "World Wide Web Publishing Service" under services.
  10. Test your work. Access the index.html file by accessing: http://localhost:80/static/index.html

Serving Static Files and Dynamic Content From the Same Request with IIS

Suppose you want to serve the static files such as *.gif , *.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 Serving Static Files with IIS.

  1. Complete the steps described in the Serving Static Files with IIS.

  2. Right-click the Default web site, then click Add Virtual Directory, and then enter the following in the Add Virtual Directory dialog box.

    • Alias—console

    • Physical Path—C:\path_to_the_wls_plug-in\console

    In this example, the physical path to the console is C:\OHS_Plugin_IIS\console.

    Description of vir_dir_console.png follows
    Description of the illustration vir_dir_console.png

    Click OK. You will see a consoleentry in the left pane under the Default Web Site.

  3. Click console under Default Web Site. A console Home opens on the right side.

  4. Click Handler Mappings on the console Home pane.

  5. 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)

      Description of edit_module_map.png follows
      Description of the illustration edit_module_map.png

  6. 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.

    Description of request_restrict.png follows
    Description of the illustration request_restrict.png

    The above step is to serve the *.png from the IIS server.

  7. To serve other image files, such as *.gif files, do the following.

    1. Under "Console Home" click "Handler Mappings", then click on "Add Module Mapping" on the right side and then enter the following.

      Request Path—*.gif

      Module—StaticFileModule, DefaultDocumentModule, DirectoryListingModule

      Executable—not required. Keep it blank

      Name—StaticFileForGIF

    2. 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"

  8. Arrange the order of the handlers.

    1. Click on "console" under "Default web site" and then click on "Handler Mappings" and then "View Ordered List" on the right side

    2. 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
      Description of handler_arrange.png follows
      Description of the illustration handler_arrange.png

  9. Copy all of the static files that belong to http://loclhost:<iis-port>/console request from WebLogic Server to IIS.

  10. Restart the service, then restart the web site.

The images (*.png and *.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 *.png and *.gif are served by Weblogic Server.

Using Wildcard Application Mappings to Proxy by Path

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.

Adding a Wildcard Script Map for IIS

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:

  1. Open IIS Manager and navigate to the level you want to manage.

    For information about opening IIS Manager, see Open IIS Manager at http://technet.microsoft.com/en-us/library/cc770472(WS.10).aspx.

    For information about navigating to locations in the UI, see Navigation in IIS Manager at http://technet.microsoft.com/en-us/library/cc732920(WS.10).aspx.

  2. In Features View, on the server, site, or application Home page, double-click Handler Mappings.
  3. On the Handler Mappings page, in the Actions pane, click Add Wildcard Script Map.
  4. In the Executable box, type the full path or browse to the iisproxy.dll that processes the request. For example, type systemroot\system32\inetsrv\iisproxy.dll.
  5. In the Name box, type a friendly name for the handler mapping.
  6. Click OK.
  7. 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.
  8. 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 at http://technet.microsoft.com/en-us/library/cc730912(WS.10).aspx.

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.

Proxying Requests from Multiple Virtual Web Sites to Different WebLogic Servers

A virtual directory is a directory name (also referred to as path) that you specify in IIS and map to a physical directory on a local or remote server. Virtual directory name becomes a part of URI. Different URI can be mapped to different WebLogic back end server by providing back server details in iisproxy.ini file.

To proxy requests from multiple websites (defined as virtual directories in IIS) to different WebLogic Servers, do the following:

Note:

You need one Virtual Directory for each context root, for example, /console, /ShoppingCart, /forms, /reports, /ords, and /i. IIS filters the request by the alias of the Virtual Directory.
  1. Create a new directory for each virtual directory.
  2. Create a virtual directory for your website. To do this:
    1. Right click on your website.
    2. Click Add Virtual Directory.
    3. Specify Alias for your website. For example, console.
    4. Provide the absolute path to the new directory that you created in Step 1, in the Physical Path field.
    5. Click OK.
  3. Extract the contents of the plug-in .zip file to a directory.
  4. For each virtual directory you configured, copy the contents of the plug-in \lib folder to the directory you created in Step 1.
  5. Create an iisproxy.ini file for the virtual websites, as described in Sample iisproxy.ini File.
  6. Copy the iisproxy.ini file to the directory you created in Step 1.
  7. Click the virtual directory under your website on the left navigation pane. This open the virtual directory Home.
  8. Click Handler Mappings on the virtual directory Home page.
  9. Click Add Script Map on right pane, and do the following:
    1. Set Request Path to *.
    2. Set Executable to the absolute path to iisproxy.dll in the directory that you copied in Step 4.
    3. Specify a Name for this mapping.
    4. 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 not selected, and click OK.
    5. Click OK on the Add Script Map window.
    6. Click Yes on the confirmation dialog box.
  10. Access your website URL. For example:
    http://localhost:80/console

Sample iisproxy.ini File

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.

Creating ACLs Through IIS

ACLs will not work through the Oracle WebLogic Server Proxy Plug-In 12c (12.2.1.4.0) 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.

  1. Ensure that the user is logged on with local log-on rights when using Basic Authentication.
  2. 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.

  3. 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".

Testing the Installation

Follow these steps to ensure that the Microsoft IIS plug-in has been installed, configured, and deployed successfully.

  1. Make sure WebLogic Server and IIS are running.
  2. Save a JSP file into the document root of the default Web Application.
  3. Open a browser and set the URL to the IIS plus filename.jsp, as shown in this example:
    http://myiis.server.com/filename.jsp

    If filename.jsp is displayed in your browser, the plug-in is functioning.