Introduction: Web servers

An application server works with a web server to handle requests for dynamic content, such as servlets, from web applications. A web server uses a web server plug-in to establish and maintain persistent HTTP and HTTPS connections with an application server.

The Supported Hardware and Software web page provides the most current information about supported web servers.

Implement a web server plug-in describes how to set up the web server and web server plug-in environment and how to create a web server definition. The web server definition associates a web server with a previously defined managed or unmanaged node. After defining the web server to a node, we can use the administrative console to perform the following functions for that web server.

If a web server is defined to a managed node, we can:

• Check the status of the web server
• Generate a plug-in configuration file for that web server.
• Propagate the plug-in configuration file after it is generated.

(Dist) If the web server is an IBM HTTP Server and the IBM HTTP Server Administration server is installed and properly configured, we can also:

• Display the IBM HTTP Server Error log (error.log) and Access log (access.log) files.
• Restart the server.
• Display and edit the IBM HTTP Server configuration file (httpd.conf).

If the web server is defined to an unmanaged node, we can:

• Check the status of the web server
• Generate a plug-in configuration file for that web server.

If the web server is an IBM HTTP Server and the IBM HTTP Server Administration server is installed and properly configured, we can also:

• Display the IBM HTTP Server Error log (error.log) and Access log (access.log) files.
• Restart the server.
• Display and edit the IBM HTTP Server configuration file (httpd.conf).
• Propagate the plug-in configuration file after it is generated.

(Dist) We can not propagate an updated plug-in configuration file to a non-IBM HTTP Server that is defined to an unmanaged node. We must manually install an updated plug-in configuration file to a web server that is defined to an unmanaged node. Web servers defined to an unmanaged node are typically remote web servers. Remote web servers are web servers that are not located on the same machine as the WebSphere Application Server.

After setting up the web server and web server plug-in, whenever we deploy a web application, specify a web server as the deployment target that serves as a router for requests to the Web application. The configuration settings in the plug-in configuration file (plugin-cfg.xml) for each web server are based on the applications that are routed through that web server. If the web server plug-in configuration service is enabled, a web server plug-in's configuration file is automatically regenerated whenever a new application is associated with that web server.

Before starting the web server, make sure we are authorized to run any Application Response Measurement (ARM) agent associated with that web server.

Refer to the web server documentation for information on how to administer that web server. For tips on tuning the web server plug-in, see Web server plug-in tuning tips.

Implement a web server plug-in