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 Availability of Oracle WebLogic Server Proxy Plug-In. The zip file contains these files:
Table 5-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 |
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:
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 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.
Note:
Do not use WLEXCLUDEPATHORMIMETYPE
property 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.
Ensure that as stated in step 4, the newly created HandlerMapping is ordered before the proxy Handler Mapping defined in Step 1.
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:
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:
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 website(virtual directory)
.
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.1.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.
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.
Figure 5-9 Windows Features for Internet Information Services
Download and install the latest Oracle WebLogic Server Proxy Plug-In zip file.
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
Ensure that the %
PLUGIN_HOME
%\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).
Figure 5-10 Internet Information Services Manager Window
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 %
PLUGIN_HOME
%\lib
\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 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.
After configuring the WLS plug-in and confirming it works (see Installing and Configuring the Microsoft IIS 7.5 Plug-In) follow these steps to serve static files.
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 7.5.
Complete the steps described in the 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.
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
.
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.
Request Path—*.gif
Module—StaticFileModule, DefaultDocumentModule, DirectoryListingModule
Executable—not required. Keep it blank
Name—StaticFileForGIF
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 http://loclhost:
<iis-port>
/console
request from WebLogic Server to IIS.
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.