This topic describes manual configuration settings for
Internet Information Services (IIS).
Before you begin
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_root directory
to perform this task.
About this task
Use the following procedure to manually reproduce how the
Installation wizard configures the Microsoft Internet Information
Services Web server.
Procedure
- Configure IIS Version 5.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 plugins_root\bin\IIS_Web_server_name directory
in the Enter the physical path of the directory containing the content
you want to publish field.
- Select the appropriate Execute check
box (such as ISAPI applications or CGI) in the What access permissions
do you want to set for this directory field.
- Click Next to add the sePlugins virtual
directory to your default Web site.
- Click Finish.
- Right-click Default Web Site in
the navigation tree and click Properties.
- Add the Internet Services Application Programming Interface
(ISAPI) filter into the IIS configuration.
In the Properties
dialog, perform the following steps:
- 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_root\bin\IIS_Web_server_name directory.
- Click the iisWASPlugin_http.dll file.
- Click OK until all the open windows close.
- Configure IIS Version 6.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.
Click Programs > Administrative Tools
> Internet Information Services (IIS) Manager on a Windows
Server 2003 Standard Edition system, for example.
- Expand the tree on the left until you see Default
Web Site.
Right-click Default
Web Site > New > Virtual Directory to create the directory
with a default installation.
- Type sePlugins in the Alias field
in the Virtual Directory Alias panel of the Virtual Directory Creation
Wizard, then click Next.
- Browse to the plugins_root\bin\IIS_Web_server_name directory
in the Path field of the Web Site Content Directory panel of the wizard,
then click Next.
For example,
select the C:\Program Files\IBM\WebSphere\Plugins\bin\IIS_webserver1 directory.
- 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 your default Web site.
- Click Finish when the success
message displays.
- 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.
- Expand the Web Sites folder in
the left pane navigation tree of the IIS Manager panel.
- Right-click Default Web Site in
the navigation tree and click Properties.
- Add the Internet Services Application Programming Interface
(ISAPI) filter into the IIS configuration.
In the Default
Web Site Properties panel, perform the following steps:
- 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 the C:\Program
Files\IBM\WebSphere\Plugins\bin\IIS_webserver1\iisWASPlugin_http.dll file
for the value of the Executable field.
Browse
to your plugins_root \bin\IIS_web_server_name directory
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 the plugins_root \config\ webserver_name \plugin-cfg.xml file,
which might be C:\Program Files\IBM\WebSphere\Plugins\config\IIS_webserver1\plugin-cfg.xml file.
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.
Remote example:"C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml"
- Configure the Web server to run WebSphere Application
Server 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.
- 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:
- Launch the IIS Version 7.0 administrative 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.
- Optional: 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.
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:
- Open a Windows Explorer window.
- Browse to the plugins_root\logs\web_server_name directory.
- 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.