TCP transport channel settings

Use this page to view and configure an TCP transport channels. This type of transport channel handles inbound TCP/IP requests from a remote client.

To view this administrative console page, click Servers > Application servers > server_name > Ports > . Click on View associated transports for the port associated with the TCP transport channel whose settings you want to view.

Transport channel name

The name of the TCP transport channel.

This name must be unique across all channels in a WebSphere Application Server environment. For example, a TCP transport channel and an HTTP transport channel cannot have the same name if they reside within the same system.

Port

The TCP/IP port this transport channel uses to establish connections between a client and an application server. The TCP transport channel binds to the hostnames and ports listed for the Port property. You can specify the wildcard * (an asterisk), for the hostname if you want this channel to listen to all hosts that are available on this system. However, before specifying the wildcard value, make sure this TCP transport channel does not have to bind to a specific hostname.

Thread pool

Select from the drop-down list of available thread pools the thread pool you want the TCP transport channel to use when dispatching work.

Maximum open connections

The maximum number of connections that can be open at one time.

Data type Integer between 1 and 20,000 inclusive
Default 20,000

Inactivity timeout

The amount of time, in seconds, that the TCP transport channel waits for a read or write request to complete on a socket.

Note: The value specified for this property might be overridden by the wait times established for channels above this channel. For example, the wait time established for an HTTP transport channel overrides the value specified for this property for every operation except the initial read on a new socket.

Data type Integer
Default 60 seconds

Address exclude list

Lists the IP addresses that are not allowed to make inbound connections. Use a comma to separate the IPv4 or IPv6 or both addresses to which you want to deny access on inbound TCP connection requests.

All four numeric values in an IPv4 address must be represented by a number or the wildcard character * (an asterisk). Following are examples of valid IPv4 addresses that can be included in an Address exclude list :

*.1.255.0
254.*.*.9
1.*.*.*

Note: The Address include list and Host name include list are processed before the Address exclude list and the Host name exclude list . If all four lists are defined:

An address that is defined on either inclusion list will be allowed access provided it is not included on either of the exclusion lists.
If an address is included in both an inclusion list and in an exclusion list, it will not be allowed access.

Address include list

Lists the IP addresses that are allowed to make inbound connections. Use a comma to separate the IPv4 addresses to which you want to grant access on inbound TCP connection requests.

All four numeric values in an IPv4 address must be represented by a number or the wildcard character * (an asterisk). Following are examples of valid IP addresses that can be included in an Address include list :

 *.1.255.0
 254.*.*.9
 1.*.*.*

Note: The Address include list and Host name include list are processed before the Address exclude list and the Host name exclude list . If all four lists are defined:

An address that is defined on either inclusion list will be allowed access provided it is not included on either of the exclusion lists.
If an address is included in both an inclusion list and in an exclusion list, it will not be allowed access.

Host name exclude list

List the host names that are not allowed to make connections. Use a comma to separate the URL addresses to which you want to deny access on inbound TCP connection requests.

A URL address can start with the wildcard character * (an asterisk) followed by a period; for example, *.Rest.Of.Address. If a period does not follow the wildcard character, the asterisk will be treated as a normal non-wildcard character. The wildcard character can not appear any where else in the address. For example, ibm.*.com is not a valid hostname. Following are examples of valid URL addresses that can be included in a Host name exclude list :

*.ibm.com www.ibm.com *.com

Note: The Address include list and Host name include list are processed before the Address exclude list and the Host name exclude list . If all four lists are defined:

An address that is defined on either inclusion list will be allowed access provided it is not included on either of the exclusion lists.
If an address is included in both an inclusion list and in an exclusion list, it is not allowed access.

Host name include list

Lists the host names that are allowed to make inbound connections. Use a comma to separate the URL addresses to which you want to grant access on inbound TCP connection requests.

*.ibm.com www.ibm.com *.com

Note: The Address include list and Host name include list are processed before the Address exclude list and the Host name exclude list . If all four lists are defined:

An address that is defined on either inclusion list will be allowed access provided it is not included on either of the exclusion lists.
If an address is included in both an inclusion list and in an exclusion list, it is not allowed access.

Data type	Integer between 1 and 20,000 inclusive
Default	20,000