Configuration Guide › CA SiteMinder Integration › Install the Proxy Plugin › Install the Proxy Plug-In on WebSphere › Complete the Configuration on IIS
Complete the Configuration on IIS
After you have configured the IBM HTTP server and the proxy plug-in, you make sure the proxy plugin-cfg.xml is in the right location and perform steps to configure an additional plugin file.
Follow these steps:
- Copy the plugin-cfg.xml as follows:
- Log in to the system where the web agent is installed.
- Create a folder with no spaces under the C: drive. For example: C:\plugin.
- Copy the plugin-cfg.xml file to the C:\plugin folder.
- Create a file called plugin-cfg.loc in the C:\plugin folder and add the following line into the file:
C:\plugin\plugin-cfg.xml
- Download the Websphere Plugin installer from www.ibm.com to the system where WebSphere is installed.
- In a command prompt, go to the location of the WebSphere Plugin installer.
- Generate the iisWASPlugin_http.dll file by using this command:
install is:javahome "c:\IBM\WebSphere\AppServer\Java
Respond to the questions presented based on your configuration.
When the wizard ends, the iisWASPlugin_http.dll file is saved in the C:\IBM\WebSphere\Plugs\bin folder. Look for a 32-bit of 64-bit subfolder.
- Copy the iisWASPlugin_http.dll file to the C:\plugin folder on the system with the web agent.
- Create a virtual directory as follows:
- Open the IIS Manager.
- Right click Default web sites.
- Click New virtual directory and supply these values:
Alias = sePlugins (it is case-sensitive.)
Path = c:\plugin
Permission = Read + Execute (ISAPI or CGI)
- Add an ISAPI filter as follows:
- Right click Default web site.
- Click properties.
- On the ISAPI filter tab, click Add.
- Supply these values:
Filter name = sePlugins
Executable = c:\plugin\ iisWASPlugin_http.dll
- Create a web service extension as follows:
- In IIS6 Manager, expand the computer name.
- Create a Web Service Extension and set it to allowed.
Extension name = WASPlugin
Path = C:\plugin\ iisWASPlugin_http.dll
- Right click each Web Service Extension to change it to Allowed Status.
- Restart the IIS Web server.
In the master WWW service, ensure that the WebSphere plug-in (sePlugin) appears after the SiteMinder Web Agent plug-in and that the WebSphere plug-in started successfully.