To define the characteristics of the connections between that plug-in and the Web container, you must configure the request queue (the HTTP transport) between a WebSphere Application Server plug-in for a Web server, and a Web container in which the Web modules of an application reside.
The use of IPv6 (Internet Protocol Version 6) and WS-AT (Web Services Atomic Transactions) are not supported on HTTP transports; they are only supported on HTTP transport channel chains.
An HTTP transport is the request queue between a WebSphere Application Server plug-in for Web servers and a Web container in which the Web modules of an application reside. To define the characteristics of the connections between that plug-in and the Web container, you must specify:
For example, you must specify the number of concurrent requests that is to be allowed.
If the Web server is located on a machine remote from the Application Server but is defined on a managed node, the updated plugin-cfg.xml is automatically propagated to the Web server.
If the Web server is defined on an unmanaged node and is not an IBM HTTP Server V6.0 Web server, copy the updated plugin-cfg.xml file to the remote Web server and replace the file that is there.
If the Web server is an IBM HTTP Server V6.0 Web server, is located on a machine remote from the Application Server, and is defined on an unmanaged node, you can configure the plugin-cfg.xml file so that whenever it is updated, it is automatically propagated to the remote IBM HTTP Server.
In this information ...Related concepts
| IBM Redbooks, demos, education, and more(Index) |