WebSphere Application Server products supply a unique binary
plug-in module for each supported Web server. The plug-in configuration
file, which the WebSphere Application Server products create and maintain,
interacts with the binary module to provide information about the
application server configuration to the Web server. The Web server
uses the information to determine how to communicate with the application
server, but to locate specific applications on the application server.
Before you begin
See Web server plug-in policy for WebSphere® Application
Server for information about how to verify what Version 4.0,
Version 5.0, Version 5.1, Version 6.0, Version 6.1, and Version 7.0
plug-in versions are installed on local or remote Web servers, and
how to determine if the installation complies with supported configurations.
You
must install a supported Web server before you can install a plug-in
for the Web server. You are not required to install the application
server to install the plug-in. To create a Web server configuration
for unmanaged nodes, however, you must install the application server.
The
Plug-ins installation wizard installs the plug-in module, configures
the Web server for communicating with the application server, and
creates a Web server configuration definition in the application server,
if possible.
Some topologies, such as the Web server on one
system and the application server on another system, prevent the Plug-ins
installation wizard from creating the Web server definition in the
application server configuration on the remote system. In such a case,
the Plug-ins installation wizard creates a script that you can copy
to the application server system. Run the script to create the Web
server configuration definition within the application server configuration.
When
multiple profiles exist, the plug-ins installer configures only the
default profile. See Plug-ins configuration for a description of the
flow of logic that determines how the installer selects the profile
to configure.
Guidelines for installing the Microsoft® Internet Information Server (IIS) plug-in: To install the IIS Web server plug-in
for use with WebSphere Application Server Version 7.0, you must complete
the following steps. These same steps apply to both IIS V7 and 7.5.
- Install IIS 7.x with the necessary IIS 6 Management Compatibility
components. IIS 6 compatibility components are not automatically installed
by default.
- Start the Server Manager panel on Windows Server 2008 by performing
the following steps:
- Click
- Click .
- Click Next on the initial panel that displays.
- On the Select Server Roles panel, select the Web Server (IIS)
role and click Next.
- If a prompt for the Windows Process Activation Service feature
displays, then click .
- Click Next on the IIS introduction panel.
- When the Role Services panel displays, make sure that the following
options are selected in addition to the default options that are already
selected:
- Internet Information Services: Management Tools
- IIS 6 Management Compatibility: IIS 6 Management Console, IIS
6 Scripting Tools, IIS 6 WMI Compatibility, and IIS Metabase compatibility
- Application Development: ISAPI Extensions, ISAPI Filters
- Click Next to enable the selected options.
- Click Install on the next panel to perform
the installation.
- Click Close on the Installation Results
panel.
- Create a new IIS web site instance if the Default Web Site instance
no longer exists:
- Start the IIS application by clicking .
- Use the Add Web Site dialog to add a new Web site to your Web
server. Type the Site name and browse to the Physical
Path, click the Test Settings button.
If the settings test fails, then either change the permissions of
the physical directory or select Connect As.. and
have IIS connect as a Windows user account that has authority to files
in that physical path. Click OK to save changes.
- Install the Web server plug-ins using the Windows installer, which
is provided with WebSphere Application Server. Complete the following
steps to install the Web server plug-ins:
- To start the Web server plug-in installer, right-click the install.exe
shortcut in the plugin directory and select Run as Administrator.
Alternatively, use the launchpad utility to install the Web server
plug-ins when you are logged in as the built-in administrator account.
- Accept all of the security dialogs and system prerequisite checking
panels that are presented.
- Select Microsoft Internet Information Services V7 as
the Web server to configure.
- If necessary, configure a Web server definition as described in
the plug-ins configuration.
- Restart IIS 7.x and your WebSphere Application Server profile.
Restriction: Do not install Web server plug-ins into
directories with parentheses () characters in the path name. On Windows
Server 2008, for example, the plug-in installation fails if you use
the default installation path of
C:\Program Files (x86)\IBM\WebSphere\Plugins.
If you installed the Web server plug-in or IBM HTTP
Server into a directory that has parentheses in the path name, complete
one of the following actions:
- Uninstall the product and reinstall it to a directory location
that does not have parentheses in the path name.
- Manually update the following values with the correct path names:
- Update the ServerRoot, AuthUserFile, and Keyfile values in the
IHS_install_root\conf\admin.conf file.
- Update the ServerRoot .AfpaLogFile, DocumentRoot, Directory, Alias/icons/,
and ScriptAlias values in IHS_install_root\conf\httpd.conf file.
- Update the JAVA_HOME and GSK_HOME values in IHS_install_root\bin\ikeyman.bat
file.
- Update the shortcut key values with the correct path name. For
example, C:\Documents and Settings\All Users\Start Menu\Programs\IBM
HTTP Server V6.1.
About this task
This topic describes installing a Web server plug-in for WebSphere Application Server. WebSphere Application Server products supply
a unique binary plug-in module for each supported Web server. The
plug-in configuration file, which the WebSphere Application
Server products create and maintain, interacts with the binary module
to provide information about the application server configuration
to the Web server. The Web server uses the information to determine
how to communicate with the application server, but to locate specific
applications on the application server.
The Plug-ins installation
wizard installs required files and configures the Web server and the
application server to allow communication between the servers.
Select
one of the following topology scenarios and follow the steps below
the diagram to install the plug-in and configure both the Web server
and the application server.
When multiple profiles exist, the plug-ins installer
configures only the default profile. See Plug-ins configuration for a description
of the flow of logic that determines how the installer selects the
profile to configure.
Procedure
- Scenario 1: Remote The application server and the
Web server are on separate machines or logical partitions.
See Configuring a Web server and an application server on separate machines (remote) for
the procedure that explains how to create this Web server topology.
- Scenario 2: Remote Multiple standalone application
servers are on one system, and each application server has a dedicated
Web server on a separate system or logical partition.

See Configuring multiple Web servers and remote standalone application servers for
the procedure that explains how to create this Web server topology.
- Scenario 3: Local Application Server profile The
application server and the Web server are on a single system or logical
partition.

A local distributed installation
includes the Web server plug-in, the Web server, and a managed application
server on the same system:

See Configuring a Web server and an application server profile on the same machine for
the procedure that explains how to create this Web server topology
for an application server profile.
- Scenario 4: Local
custom profile A managed node and the Web server are on the same
system or logical partition.
A local distributed installation
includes the Web server plug-in, the Web server, and the managed custom
node on the same system:

See Configuring a Web server and a custom profile on the same machine for
the procedure that explains how to create this Web server topology
for a federated custom profile.
- Scenario
5: Local deployment manager profile A deployment manager node
and the Web server are on a single system or logical partition.
A local distributed installation includes the Web server
plug-in, the Web server, and the application server on the same system:

See Configuring a Web server and a deployment manager profile on the same machine for
the procedure that explains how to create this Web server topology
for a deployment manager profile.
- Scenario 6: Non-default profile Creating a Web server
definition for a profile that is not the default profile.

Results
You can install a Web server and the Web server plug-ins
for various standalone application server topologies by following
the procedures described in this topic.