[Updated in July 2013]Configure IIS Version 8.x.
Supported configurations Supported configurations: You can use IIS Version 8 with Windows Server 2012.
Install IIS Version 8.x with the necessary IIS Version 6.0 Management Compatibility components.
IIS Version 6.0 Management Compatibility components are not automatically installed by default. Complete the following steps to install IIS Version 8.x with the necessary IIS Version 6.0 Management Compatibility components.

Complete the following steps to install IIS Version 8.x on Windows Server 2012:
Bring up the Server Manager
Select the installation type based on your environment and then click Next.
Select the server that will receive the installation and then click Next.
When the Server Roles window displays, verify that the following options are selected in addition to the default options that are already selected.
Management Tools: IIS Management Console
IIS Version 6.0 Management Compatibility: IIS Version 6.0 Management Console, IIS Version 6.0 Scripting Tools, IIS Version 6.0 WMI Compatibility, and IIS Metabase compatibility
IIS Management Scripts and Tools
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.
Install the web server plug-ins.
If you are using an already installed web server plug-in, go to the next step, and re-configure IIS Version 8.x to use that web server plug-in.

Optional: Re-configure IIS Version 8.x 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 you are re-configuring IIS Version 8.x to use an existing web server plug-in.

Complete the following steps to re-configure IIS Version 8.x:

Click the Tools> Internet Information Services (IIS) Manager within the Server Manager screen. This action starts the IIS application, and creates a new virtual directory for the website instance that you intend to use with WebSphere Application Server. These instructions assume that you are using the default website.
Expand the tree on the left until you see Default Web Site.
Right-click Default Web Site > Add Virtual Directory to create the directory with a default installation.
Type sePlugins in the Alias field on the Virtual Directory Alias window.
Browse to the plugins_root\bin\IIS_web_server_name directory in the Physical Path field of the Web Site Content Directory window, and then click OK. For example, select the C:\Program Files\IBM\WebSphere\Plugins\bin\IIS_webserver1 directory.
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.
Attention: When you click the Test Settings button, you might encounter the following warning message if you use the default "Pass-thru authentication" setting:
Cannot verify access to path
For more information, refer to the Microsoft information on this subject.
Click OK to add the sePlugins virtual directory to your default website.
In the navigation tree, select the sePlugins virtual directory that you just created.
On the Features panel, double-click Handler Mappings, and then click Edit Feature Permissions on the Actions panel.
Select Script and Execute, if they are not already selected.
Click OK.
Manually copy the plug-in binaries to the plugins_root\bin\IIS_web_server_name directory. For example, copy the plug-in binary files to the C:\Program Files\IBM\WebSphere\Plugins\bin\IIS_webserver1 directory.
The plugin-cfg.loc file resides in this directory. The first line of the plugin-cfg.loc file identifies the location of the plugin-cfg.xml file.

Return to the IIS Manager window, and expand the Web Sites folder in the left-hand navigation tree of that window.
Select Default Web Site in the navigation tree.
Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration.
On the Default Web Site Properties panel, complete the following steps:
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 the plugins_root \bin\IIS_web_server_name\iisWASPlugin_http.dll directory.
Click OK to close the Add/Edit Filter Properties dialog window.
In the navigation tree, select the top level server node.
On the Features panel, double-click ISAPI and CGI Restrictions, and then, on the Actions panel, click Add.
To determine the value to specify for the ISAPI or CGI Path property, browse to, and then select the same plug-in file that you selected in the previous step. For example:
plugins_root\bin\IIS_web_server_name\iisWASPlugin_http.dll
Then type WASPlugin in the Description field, select Allow extension path to execute, and then click OK to close the ISAPI and CGI Restrictions 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:\Program Files\IBM\WebSphere\Plugins\config\IIS_webserver1\plugin-cfg.xml
The location varies depending on how you have configured your system. If the web server, and WebSphere Application Server are on separate machines, you have a remote installation. If the web server, and WebSphere Application Server are on the same machine, then you 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 application server is federated, you 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 Version 8.x and your WebSphere Application Server profile.
[Updated in July 2013]
Enable IIS Version 6.0, IIS Version 7.x, or IIS Version 8.0 to communicate with a web server plug-in that is 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 Version 6.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 Version 7.x to run the web server plug-in under a 32-bit worker process:

Launch the IIS Version 7.x or IIS Version 8.0 administrative console.
On the connections page, expand the Sites node, and select the website 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.
Optional: Configure multiple websites. Given:
There are two websites defined: website1 and 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 predefined application pool DefaultAppPool.
Define the two websites, including the filter setting, virtual host setting, and extension settings.
Assign an application pool for each website.
Under each website folder, right click on the website name.
Click Property, and select the Home Directory tab. 2.
At the bottom of the application settings, select the application pool you defined for website 1 from the dropdown list of application pools.
Click OK.
Repeat the previous steps for the second website and select the application pool you defined for website 2.
Start the IIS service and start each website.