Installing and configuring web server plug-ins

WebSphere® Application Server supplies 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.

About this task

This article describes installing and configuring web server plug-ins for WebSphere Application Server. WebSphere Application Server products supplies 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.

The Web Server Plug-ins Configuration Tool configures the web server and the application server to allow communication between the servers.

Tip: As an alternative to using the Web Server Plug-ins Configuration Tool, you can use the pct command-line tool with a response file to configure a web server. Read Configuring a web server plug-in using the pct tool for more information.

Select one of the following topology scenarios and follow the steps after the diagram to install the plug-in and configure both the web server and the application server.

When multiple profiles exist, you can select the profile that the Web Server Plug-ins Configuration Tool configures. See Plug-ins configuration for a description of the flow of logic that determines how to select the profile to configure.

• Scenario 1: 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 2: 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 3: 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 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.