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-ins 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.
Communicating with Web servers describes how to set up your 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 you define the Web server to a node, you can use the administrative console to perform the following functions for that Web server. If a Web server is defined to a managed node, you can:
If the Web server is defined to an unmanaged node, you can:
After you set up your Web server and Web server plug-in, whenever you 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.
Note: Before starting the Web server, make sure you are authorized to run any Application Response Measurement (ARM) agent associated with that Web server.
Refer to your Web server documentation for information on how to administer
that Web server. For tips on tuning your Web server plug-in, see Web server plug-in tuning tips.