Why and when to perform this task
Note that 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:
Steps for this task
Remember, on a distributed platform, HTTP transport support is deprecated. Therefore you cannot view this administrative console page unless you are a V5.x user who, during the V6 migration process, indicated that you want to continue using the HTTP transports that are defined for your V5 environment.
What to do next
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. See Editing Web server configuration files for information about copying the plugin-cfg.xml and binary plug-in module to a remote Web server and configuring the Web server to use the files.
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.