Technical data

12 Installing and Configuring the Microsoft Internet Information Server (ISAPI) Plug-In
12-12 Administration Guide
<context-param>
<param-name>weblogic.httpd.clientCertProxy</param-name>
<param-value>true</param-value>
</context-param>
You can also use this parameter in a cluster as follows:
<Cluster ClusterAddress="127.0.0.1" Name="MyCluster"
ClientCertProxyHeader="true"/>
Proxying Servlets from IIS to WebLogic
Server
Servlets may be proxied 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
proxying by file type.To proxy servlets by file type:
1. Register an arbitrary file type (extension) with IIS to proxy the request to the
WebLogic Server, as described in step 7. under “Installing the Microsoft Internet
Information Server Plug-In” on page 12-3.
2. Register your servlet in the appropriate Web Application. For more information
on registering servlets, see Configuring Servlets at
http://e-docs.bea.com/wls/docs61/webapp/components.html#configu
ring-servlets
.
3. Invoke your servlet with a URL formed according to this pattern:
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.