Configure Microsoft Internet Information Services (IIS)
Configure Microsoft Internet Information Services (IIS)
This topic describes manual configuration settings for Internet Information Services (IIS).
When you install the Web server plug-ins for WebSphere Application Server, as described in Installing Web server plug-ins, the Plug-ins installation wizard configures the Web server.
This topic describes how to configure the Internet Information Services (IIS)
Web server. Other procedures in Editing Web server configuration files describe configuring other supported Web servers.
You must have read/write access to the plugins_install_root directory to perform this task.
Use the following procedure to manually reproduce how the Installation wizard configures the Microsoft Internet Information Services Web server.
(dependent on configuration)
Configure IIS V5.0.
Start the IIS application and create a new virtual directory for the Web site instance that you intend to work with WebSphere Application Server. These instructions assume that you are using the Default Web Site.
Expand the tree on the left until you see Default Web Site.
Right-click Default Web Site , then click New > Virtual Directory to create the directory with a default installation.
Type sePlugins in the Alias to be used to Access Virtual Directory field.
Browse to the WebSphere Application Server install_root\bin directory in the Enter the physical path of the directory containing the content you want to publish field.
Select the Allow Execute Access check box in the What access permissions do you want to set for this directory field.
Click Finish to add the sePlugins virtual directory to your default Web site.
Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration.
Right-click the host name in the tree on the left and click Properties .
In the Properties dialog...
Click the Internet Information Services tab.
Click WWW Service in the Master properties window.
Click Edit to open the WWW Service master properties window.
Click ISAPI Filters > Add to open the Filter properties window.
Type iisWASPlugin in the Filter Name field.
Click Browse in the Executable field.
Browse to the Plugins_install_root\bin directory.
Click the iisWASPlugin_http.dll file.
Click OK until all the open windows close.
Configure IIS V6.0.
Start the IIS application and create a new virtual directory for the Web site instance that you intend to work with WebSphere Application Server. These instructions assume that you are using the Default Web Site.
Expand the tree on the left until you see Default Web Site.
Right-click Default Web Site , then click New > Virtual Directory to create the directory with a default installation.
Type sePlugins in the Alias to be used to Access Virtual Directory field.
Browse to the WebSphere Application Server install_root\bin directory in the Enter the physical path of the directory containing the content you want to publish field.
Select the Allow Execute Access check box in the What access permissions do you want to set for this directory field.
Click Finish to add the sePlugins virtual directory to your default Web site.
Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration.
Right-click Default Web Site in the tree on the left and click Properties . In the Properties panel...
Click the Internet Information Services tab.
Click the ISAPI Filters tab.
Click Add to open the Filter properties window.
Type iisWASPlugin in the Filter Name field.
Click Browse in the Executable field.
Browse to the plugins_install_root\bin directory.
Click the iisWASPlugin_http.dll file.
Click OK until all the open windows close.
Copy the plug-in binaries to the directory C:\program files\WebSphere\Plugins\bin\iis_webserverName
The plugin-cfg.loc file resides in this directory. The first line of the plugin-cfg.loc file is the location of the plugin-cfg.xml file.
Set the value of the Plugin Config variable to the location of the configuration file, which is the plugins_install_root\config\webserver_name\plugin-cfg.xml directory.
The location varies, depending on how you have configured your system.
If the Web server and the Application Server are on separate machines, you have a remote installation.
If the two servers are on the same machine,
you have a local installation.
If the two servers are on the same machine and the Application Server is a managed node, you have a local distributed installation.
Local distributed example: