Transport chains

Transport chains represent a network protocol stack used for I/O operations within an application server environment. Transport chains are part of the channel framework function providing a common networking service for all components, including the service integration bus WebSphere Secure Caching Proxy, and the high availability manager core group bridge service. A transport chain consists of one or more types of channels. Network ports can be shared among all of the channels within a chain. The channel framework function automatically distributes a request arriving on that port to the correct I/O protocol channel for processing.

Transport channel types.

DCS channel

Transfer data, objects, or events among application servers. Used by the core group bridge service, the data replication service (DRS), and the high availability manager.

HTTP inbound channel

Enables communication with remote servers. Implements the HTTP 1.0 and 1.1 standards. Used by other channels, such as the web container channel, to serve HTTP requests and to send HTTP specific information to servlets expecting this type of information. HTTP inbound channels are used instead of HTTP transports to establish the request queue between a web server plug-in, and a web container in which the web modules of an application reside.

HTTP proxy inbound channel

Handles HTTP requests between a proxy server and application server nodes.

HTTP Tunnel channel

Provides client applications with persistent HTTP connections to remote hosts that are either blocked by firewalls or require an HTTP proxy server, including authentication, or both. An HTTP Tunnel channel enables the exchange of application data in the body of an HTTP request or response sent to or received from a remote server. An HTTP Tunnel channel also enables client-side applications to poll the remote host and to use HTTP requests to either send data from the client or to receive data from an application server. In either case, neither the client nor the application server is aware that HTTP is being used to exchange the data.

JFAP channel

Used by the Java Message Service (JMS) server to create connections to JMS resources on a service integration bus.

MQ channel

Used in combination with other channels, such as a TCP channel, within the confines of IBM MQ support to facilitate communications between a service integration bus and an IBM MQ client or queue manager.

SIP channel

Creates a bridge in the transport chain between a session initiation protocol (SIP) inbound channel, and a servlet and JavaServer Page engine.

SIP container inbound channel

Handles communication between the SIP inbound channel and the SIP servlet container.

SIP inbound channel

Handles inbound SIP requests from a remote client.

SSL channel

Associates an SSL configuration repertoire with the transport chain. This channel is only available when SSL support is enabled for the transport chain. An SSL configuration repertoire is defined in the administrative console, under...

Security | SSL configuration repertoires

TCP channel

Provides client applications with persistent connections within a Local Area Network (LAN) when a node uses transmission control protocol (TCP) to retrieve information from a network.

UDP channel

Provides client applications with persistent connections within a Local Area Network (LAN) when a node uses user datagram protocol (UDP) to retrieve information from a network.

Web container channel

Creates a bridge in the transport chain between an HTTP inbound channel and a servlet and JavaServer Page (JSP) engine.

Administer application servers

Configure transport chains

Transport chains collection