Configuration Guide › CA SiteMinder Integration › Install the Web Proxy Server Plug-in › Install the Proxy Plug-In on WebLogic › Configure the Proxy Plug-in for IIS (7.x)
Configure the Proxy Plug-in for IIS (7.x)
The following procedure walks through the deployment and configuration of the WebLogic proxy plug-in for IIS 7.x.
Note: These instructions are for 32-bit operating environments. The same instructions apply for 64-bit operating environments. The location of the installation .dll file is different:
- %WL_HOME%server\plugin\win\32\
- %WL_HOME%server\plugin\win\64\
Follow these steps:
- Install Web agent and configure it on IIS7.
- Create a folder with the name ‘plugin’ in ‘C’ drive.
- Copy the following files to the plugin folder:
- lisforward.dll
- Iisproxy.dll
- iisproxy.ini
You can find these files at \\lodimmaple.ca.com\RegressionHarness\thirdparty\weblogic\Weblogic_Proxy_Files_IIS7.
- Install the Application Development and Management Tools role services on IIS7.
- Open Inet Manager and select the Default Web site.
- Click Handler Mappings.
- Double click Static File and modify the Request path to *.*.
- Click the Request Restrictions button.
- On the Mappings tab select Invoke handler only if the request is mapped to a File or folder.
- In Handler Mappings dialog click Add Script Map… on the right-hand side menu options. Enter the following values:
- Request path : *
- Executable: iisProxy.dll
- Name: proxy
- Click the Request Restrictions button.
- Clear Invoke handler only if the request is mapped to.
- Click Yes to the prompt about allowing this IASPI extension.
- Click the Root node (Machine name) of the IIS Manager tree and click ISAPI and CGI Restrictions.
- Click Add in Actions pane and enter the following values:
- ISAPI or CGI Path: C:\plugin\ iisproxy.dll.
- Description: Weblogic
- Select Allow extension path to execute.
- Click the Root node (Machine name) of the IIS Manager tree and click on the "ISAPI and CGI Restrictions". Select the option "Weblogic" and click on "Edit Feature Settings" at the right side pane.
- Select Allow unspecified ISAPI modules and Allow unspecified CGI modules.
- Do the same for Webagent.
- In Features View, on the ‘Default Web Site’, double-click Handler Mappings.
- On the Handler Mappings page, in the Actions pane, click Add Script Map and the following values:
- Request path : .jsp
- Executable : iisproxy.dll
- Name : JSP
- Click Request restrictions.
- On the Mapping tab select Invoke handler only if request is mapped to File.
- Click OK.
- Click Add Script Map and the following values:
- Request path : .do
- Executable : C:\plugin\iisproxy.dll
- Click Request restrictions. The settings are the same .jsp.
- Click OK.
- Click Add Script Map and enter the following values:
- Request path : .wlforward
- Executable : C:\plugin\iisproxy.dll
- Click Request restrictions. The settings are the same as for .jsp.
- Click Default Web Site and double click ISAPI Filters.
- Click View Order List on the right-side pane.
- Place the SiteMinder Agent executable in second place in the list. After this entry, only the Weblogic executable is in the list.
Note: If SiteMinder Agent executable appears after the Weblogic executable, then move the SiteMinder Agent using MOVE UP action.
- Click Application pools and change the Default App Pool to Classic mode.
The WebLogic plug-in is configured.
Copyright © 2013 CA.
All rights reserved.
|
|