Use this page to view or manage transport chains for the on demand router (ODR). Transport chains enable communication through transports, or protocol stacks, which are usually socket based.
A transport chain consists of one or more types of channels, each of which supports a different type of I/O protocol, such as TCP or HTTP. 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.
The Transport chains page lists the transport chains defined for the selected application server. Transport chains represent network protocol stacks operating within this application server.
To view this administrative console page, click . Click View associated transports for the port whose transport chains you want to view.
To change the ODR settings, you must have administrator or configurator administrative privileges.
Specifies a unique identifier for the transport chain. The transport name must be unique within a configuration. Click the name of a transport chain to change its configuration settings.
When set to true, the transport chain is activated at application server startup.
Specifies the host internet protocol address to bind for transport. If the application server is on a local machine, the host name might be localhost.
Specifies the port to bind for transport. The port number can be any port that currently is not in use on the system, might be localhost or the wildcard character * (an asterisk). The port number must be unique for each application server instance on a given machine
Maximum number of connections that can be open at one time on an inbound channel.
Amount of time (in seconds) that a socket can remain inactive before timing out read or write requests. Once the initial data is read, this is sometimes overridden by other channels later in the transport chain.
Name of the SSL (secure sockets layer) configuration that this channel is to use. SSL settings are used by this channel to negotiate handshakes, decrypt data, and encrypt data on connections created by a client.
When sending an outgoing HTTP message, this controls whether or not to default to allowing persistent connections (Keep-Alive) as opposed to a connection that close after the request/ response exchange. While this might be enabled, the setting of the maximum persistent requests to 1 or 0 disables persistent connections.
Maximum time in seconds to wait while performing a read of data on a socket.
Maximum time in seconds to wait while performing a write of data on a socket.
Maximum idle time in seconds on a socket between client requests. Once this timeout is passed, the connection is closed.