• Configure IIS Version 7.0.

Avoid trouble: Before starting this step, verify that you are using a Version 6.1.0.9, or later,
Web server plug-in. Earlier versions of the plug-in do not support the Windows Server 2008
operating system.
1. Install IIS Version 7.0 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 7.0 with the necessary IIS
Version 6.0 Management Compatibility components.
a. Complete the following steps to bring up the Server Manager window on
Windows Server 2008:
i. Click Start > Administrative Tools > Server Managers.
ii. Click Action > Add Roles, and then click Next.
iii.On the Select Server Roles page, select the Web Server (IIS) role, and
then click Next.
iv. If a prompt for the Windows Process Activation Service feature displays,
click Add Feature > Next, and then click Next on the IIS introduction
page
b. When the Role Services window displays, verify that the following options are
selected in addition to the default options that are already selected.
i. Internet Information Services: Management Tools
ii. 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
iii.Application Development: ISAPI Extensions, ISAPI Filters
c. Click Next to enable the selected options, and then click Install on the next
window to perform the installation.
d. When the installation finishes, click Close on the Installation Results window.
2. Use the Windows Installer to install the Web server plug-ins.
If you are using an already installed Web server plug-in, go to the next step, and
reconfigure IIS Version 7.0 to use that Web server plug-in.
The Windows Installer is provided with WebSphere Application Server. Complete the
following steps to install the Web server plug-ins:
a. 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, you can use
the launchpad utility to install the Web server plug-ins if you login using the
administrator account that is provided.
b. Accept all of the settings on the security dialog, and system prerequisite checking
pages that display.
c. Select Microsoft Internet Information Services Version 6.0 as the Web server to
configure.
d. If necessary, configure a Web server definition as described in the plug-ins
configuration.
3. Optional: Reconfigure IIS Version 7.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 you are reconfiguring IIS Version 7.0 to use
an existing Web server plug-in.
Complete the following steps to reconfigure IIS Version 7.0:
a. Click 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 WebSphere Application Server. These
instructions assume that you are using the Default Web site.
b. Expand the tree on the left until you see Default Web Site.
c. Right-click Default Web Site > Add Virtual Directory to create the directory with
a default installation.
d. Type sePlugins in the Alias field on the Virtual Directory Alias window of the
Virtual Directory Creation Wizard.
e. Browse to the plugins_root\bin\IIS_Web_server_name directory in the Physical
Path field of the Web Site Content Directory window of the wizard, and then
click OK. For example, select the C:\Program Files\IBM\WebSphere\Plugins\bin\
IIS_webserver1 directory.
f. 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.
g. Click OK to add the sePlugins virtual directory to your default Web site.
h. In the navigation tree, select the sePlugins virtual directory that you just created.
i. On the Features panel, double-click Handler Mappings, and then click Edit
Feature Permissions on the Actions panel.
j. Select Script and Execute, if they are not already selected.
k. Click OK.
l. 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.
m. Return to the IIS Manager window, and expand the Web Sites folder in the left-
hand navigation tree of that window.
n. Select Default Web Sitein the navigation tree.
o. Add the Internet Services Application Programming Interface (ISAPI) filter into
the IIS configuration.
On the Default Web Site Properties panel, complete the following steps:
i. Double-click the ISAPI Filters tab.
ii. Click to open the Add/Edit Filter Properties dialog window.
iii.Type iisWASPlugin in the Filter name field.
iv. Click Browse to select the plug-in file located in the plugins_root \bin\
IIS_web_server_name\iisWASPlugin_http.dll directory.
v. Click OK to close the Add/Edit Filter Properties dialog window.
p. In the navigation tree, select the top level server node.
q. 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.
r. 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

s. Restart IIS Version 7.0 and your WebSphere Application Server profile.
• Enable IIS Version 6.0 or IIS Version 7.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.0 to run the Web server
plug-in under a 32-bit worker process:
1. Launch the IIS Version 7.0 administrative console.
2. On the connections page, expand the Sites node, and select the Web site that is intended
for the Web server plug-in.
3. On the actions page, click Basic Settings, and make a note of the Application Pool name.
 4. Click Cancel , and then select the Application Pools node on the connections page.
5. On the features page, right-click the application pool that you noted in the earlier step,
and then choose Advanced Settings.
6. Set the Enable 32-bit Applications property to True.
7. Click OK to complete the configuration change.
8. Restart the corresponding application pool.
• Optional: Configure multiple Web sites. Given:
1. There are two Web sites defined: website1, website2.
2. The DLL files are already created as bin/website1/iisWASPlugin_http.dll and
bin/website2/iisWebsite2/iisWASPlugin_http.dll.
3. The plugin-cfg.loc files are created in the same folder as the DLL files.
4. Run IIS in worker process isolation mode (default).
To enable worker process in isolation mode:
a. Open the IIS Manager console and expand the local computer by clicking the
plus sign.
b. Expand the Web Sites folder, then right-click the Default Web Sites folder.
c. Click Properties, then click the Service tab.
d. Under Isolation mode, clear the Run Web service in IIS 5.0 isolation mode check
box to enable worker process isolation mode.
5. Define two application pools; one for website1 and the other for website2. Do not use
the pre-defined application pool DefaultAppPool.
6. Define the two Web sites, including the filter setting, virtual host setting, and extension
settings.
7. Assign an application pool for each Web site.
a. Under each Web site folder, right click on the Web site name.
b. Click Property, and select the Home Directory tab. 2.
c. 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.
d. Click OK.
e. Repeat the previous steps for the second Web site and select the application pool
you defined for Web site 2.
8. Start the IIS service and start each Web site.

Results
This procedure results in reconfiguring the Internet Information Services (IIS) Web server.
Note: 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:
1. Open a Windows Explorer window.
2. Browse to the plugins_root\logs\web_server_name directory.
3. Share the folder and give full-control permission to everyone.

What to do next
You can now install applications on the configured Web server. See the Applications section of the
information center for more information.