Microsoft Internet Information Services (IIS)

Microsoft Internet Information Services (IIS)

+
Search Tips | Advanced Search

Overview

Use the following procedure to manually reproduce how the Installation wizard configures the Microsoft Internet Information Services Web server.
You must have read/write access to PLUGINS_ROOT to perform this task.

IIS V6.0

Start the IIS application

Programs | Administrative Tools | Internet Information Services (IIS) Manager

Expand the tree on the left until you see Default Web Site.

Default Web Site | New | Virtual Directory

Type sePlugins in the Alias field in the Virtual Directory Alias panel of the Virtual Directory Creation Wizard, then click Next.
Browse to...
PLUGINS_ROOT\bin\IIS_web_server_name

...in the Path field of the Web Site Content Directory panel of the wizard, then click Next.
For example, select...

C:\IBM\WebSphere\Plugins\bin\IIS_webserver1

Select the appropriate permission check boxes in the Virtual Directory Access Permissions panel of the wizard.
Select the Read check box and the Execute (such as ISAPI applications or CGI) check box, for example.
Click Next to add the sePlugins virtual directory to the default Web site.
Click Finish when the success message displays.
Copy the plug-in binaries to...

C:\IBM\WebSphere\Plugins\bin\IIS_webserver1

The plugin-cfg.loc file resides in this directory. The first line of the plugin-cfg.loc file identifies the location of plugin-cfg.xml.
Expand the Web Sites folder in the left pane navigation tree of the IIS Manager panel.
Right-click...

Default Web Site | Properties

In the Default Web Site Properties panel...

Click the ISAPI Filters tab.
Click Add to open the Add/Edit Filter Properties dialog window.
Type iisWASPlugin in the Filter name field.
Click Browse to select...

C:\IBM\WebSphere\Plugins\bin\IIS_webserver1\iisWASPlugin_http.dll

...for the value of the Executable field.
Browse to...
PLUGINS_ROOT\bin\IIS_Web_server_name

...to select the iisWASPlugin_http.dll file.
Click OK to close the Add/Edit Filter Properties dialog window.
Click OK to close the Default Web Site Properties window.

Set the value in the plugin-cfg.loc file to the location of the configuration file.
Set the location to...
PLUGINS_ROOT\config\webserver_name\plugin-cfg.xml...
...which might be...

C:\IBM\WebSphere\Plugins\config\IIS_webserver1\plugin-cfg.xml

The location varies depending on how we have configured the system. If the Web server and the appserver are on separate machines, we have a remote installation.
If the two servers are on the same machine, we have a local installation.
If the two servers are on the same machine and the appserver is federated, we have a local distributed installation.
Local distributed example:
"C:\IBM\WebSphere\AppServer\profiles\custom01\config\cells\dmgrcell\nodes\managed_node\servers\webserver1\plugin-cfg.xml"

Example:
"C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml"

Configure the Web server to run WAS extensions:

Expand the left pane navigation tree and click on the Web Service Extensions folder in the IIS Manager panel.
Click Add a new Web service extension to open the New Web Service Extension dialog window.
In the Extension name field, type WASPlugin as the name of the new Web service extension.
Click Add to open the Add file dialog window.
In the Path to file field, type the path or click Browse to navigate to the correct iisWASPlugin_http.dll file that the new Web service extension requires, and click OK.
Select the Set extension status to Allowed check box to automatically set the status of the new Web service extension to Allowed and click OK.

IIS V7.0

Install IIS V7.0 with the necessary IIS V 6.0 Management Compatibility components.
IIS V 6.0 Management Compatibility components are not automatically installed by default. Complete the following steps to install IIS V7.0 with the necessary IIS V6.0 Management Compatibility components.

Complete the following steps to bring up the Server Manager window on Windows Server 2008:

Go to...

Start | Administrative Tools | Server Managers | Action | Add Roles | Next | Select Server Roles | role | Next

If a prompt for the Windows Process Activation Service feature displays, click Add Feature > Next, and then click Next on the IIS introduction page

When the Role Services window displays, verify that the following options are selected in addition to the default options that are already selected.

Internet Information Services: Management Tools
IIS V6.0 Management Compatibility: IIS V6.0 Management Console, IIS V6.0 Scripting Tools, IIS V6.0 WMI Compatibility, and IIS Metabase compatibility
Application Development: ISAPI Extensions, ISAPI Filters

Click Next to enable the selected options, and then click Install on the next window to perform the installation.
When the installation finishes, click Close on the Installation Results window.

Use the Windows Installer to install the Web server plug-ins.
For an already installed Web server plug-in, go to the next step, and reconfigure IIS V7.0 to use that Web server plug-in.
The Windows Installer is provided with WAS. Complete the following steps to install the Web server plug-ins:

Right-click the install.exe shortcut in the plugin directory to start the Web server plug-in installer, and then select Run as Administrator. Alternatively, we can use the launchpad utility to install the Web server plug-ins if we login using the administrator account that is provided.
Accept all of the settings on the security dialog, and system prerequisite checking pages that display.
Select Microsoft Internet Information Services V6.0 as the Web server to configure.
If necessary, configure a Web server definition as described in the plug-ins configuration.

Reconfigure IIS V7.0 if the Web Server plug-in is already installed:

The following steps are completed automatically during Web server plug-in installation. You only need to complete these steps are if we are reconfiguring IIS V7.0 to use an existing Web server plug-in.
Complete the following steps to reconfigure IIS V7.0:

Go to...

Start | All Programs | Administrative Tools | Internet Information Services (IIS) Manager

...on a Windows Server 2008 operating system. This action starts the IIS application, and creates a new virtual directory for the Web site instance that you intend to use with WAS. These instructions assume that we are using the Default Web site.
Expand the tree on the left until you see Default Web Site.
Right-click...

Default Web Site | Add Virtual Directory

Type sePlugins in the Alias field on the Virtual Directory Alias window of the Virtual Directory Creation Wizard.
Browse to...
PLUGINS_ROOT\bin\IIS_Web_server_name

...in the Physical Path field of the Web Site Content Directory window of the wizard, and then click OK.
For example, select...

C:\IBM\WebSphere\Plugins\bin\IIS_webserver1

Click the Test Settings button. If the settings test fails, then either change the permissions of the physical directory, or select Connect As, and let IIS connect as a Windows user account that has authority to files in that physical path.
Click OK to add the sePlugins virtual directory to the default Web site.
Manually copy the plug-in binaries to...
PLUGINS_ROOT\bin\IIS_Web_server_name

For example, copy the plug-in binary files to...

C:\IBM\WebSphere\Plugins\bin\IIS_webserver1

The plugin-cfg.loc file resides in this directory. The first line of the plugin-cfg.loc file identifies the location of plugin-cfg.xml.
Return to the IIS Manager window, and expand the Web Sites folder in the left-hand navigation tree of that window.
Select Default Web Sitein the navigation tree.
Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration. On the Default Web Site Properties panel...

Double-click the ISAPI Filters tab.
Click to open the Add/Edit Filter Properties dialog window.
Type iisWASPlugin in the Filter name field.
Click Browse to select the plug-in file located in...
PLUGINS_ROOT \bin\IIS_web_server_name\iisWASPlugin_http.dll

Click OK to close the Add/Edit Filter Properties dialog window.

Set the value in the plugin-cfg.loc file to the location of the configuration file at PLUGINS_ROOT \config\ webserver_name\plugin-cfg.xml. Following is the default location:
C:\IBM\WebSphere\Plugins\config\IIS_webserver1\plugin-cfg.xml

The location varies depending on how we have configured the system.
If the Web server, and WAS are on separate machines, we have a remote installation. If the Web server, and WAS are on the same machine, then we have a local installation, and the correct location of the configuration file might be set. If the two servers are on the same machine, and the appserver is federated, we have a local distributed installation.
Local distributed example:
C:\IBM\WebSphere\AppServer\profiles\custom01\config\cells\dmgrcell\nodes\managed_node\servers\webserver1\plugin-cfg.xml

Local example:
C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml

Restart IIS V7.0 and the WAS profile.

Enable IIS to communicate with a Web server plug-in running in 32–bit mode

The Web server plug-in for IIS is available in both 32-bit, and 64-bit versions. When using the 32-bit version plug-in on a Microsoft Windows 64-bit operating system, the following steps should be taken to enable the native 64-bit IIS to run the plug-in under a 32-bit worker process.
The Windows Server TechNet topic Running 32-bit Applications on 64-bit Windows describes how to enable the native 64-bit IIS V6.0 to run the Web server plug-in under a 32-bit worker process.
Complete the following steps to enable the native 64-bit IIS V7.0 to run the Web server plug-in under a 32-bit worker process:

Launch the IIS V7.0 admin console.
On the connections page, expand the Sites node, and select the Web site that is intended for the Web server plug-in.
On the actions page, click Basic Settings, and make a note of the Application Pool name.
Click Cancel , and then select the Application Pools node on the connections page.
On the features page, right-click the application pool that you noted in the earlier step, and then choose Advanced Settings.
Set the Enable 32-bit Applications property to True.
Click OK to complete the configuration change.
Restart the corresponding application pool.

Configure multiple Web sites

Given:

There are two Web sites defined: website1, website2.
The DLL files are already created as bin/website1/iisWASPlugin_http.dll and bin/website2/iisWebsite2/iisWASPlugin_http.dll.
The plugin-cfg.loc files are created in the same folder as the DLL files.

Run IIS in worker process isolation mode (default).
To enable worker process in isolation mode:

Open the IIS Manager console and expand the local computer by clicking the plus sign.
Expand the Web Sites folder, then right-click the Default Web Sites folder.
Click Properties, then click the Service tab.
Under Isolation mode, clear the Run Web service in IIS 5.0 isolation mode check box to enable worker process isolation mode.

Define two application pools; one for website1 and the other for website2. Do not use the pre-defined application pool DefaultAppPool.
Define the two Web sites, including the filter setting, virtual host setting, and extension settings.
Assign an application pool for each Web site.

Under each Web site folder, right click on the Web site name.
Click Property, and select the Home Directory tab. 2.
At the bottom of the application settings, select the application pool you defined for Web site 1 from the drop-down list of application pools.
Click OK.
Repeat the previous steps for the second Web site and select the application pool you defined for Web site 2.

Start the IIS service and start each Web site.

On some editions of the Windows operating system, the http_plugin.log file is not created automatically when the plug-in is installed and the IIS Web server is started. If the http_plugin.log file is not created after performing the procedure described above, take the following steps:

Open a Windows Explorer window.
Browse to...
PLUGINS_ROOT\logs\web_server_name

Share the folder and give full-control permission to everyone.

Related tasks
Edit Web server configuration files