TCP

Description

The TCP service is made up of two components, a TCP server running on the Upstream DD Engine and a TCP client running on the Downstream DD Engine.

The server waits for connection requests from any remote host. When a connection has been established, incoming data is read and directly forwarded to the Downstream service. The server never writes any data back to the connected peer.

When the TCP client receives data from the Upstream service it will establish a connection to the pre-configured remote host, and forward the received data to it. For every unique connection that is opened to the server service, a corresponding connection is opened by the client service to the remote peer.

A protocol break is performed when transferring data through the service. This means that only the data section of each TCP segment is forwarded from the server service to the client service.

Configuration

In this section, the TCP service parameters are described in detail. Parameters are divided into sections, TCP Server Upstream and TCP Client Downstream, in the same way as they are displayed when configuring the service using the DD Manager.

note

In DD Manager, as well as in the parameter descriptions below, mandatory parameters are indicated by asterisks (*).

TCP Server Upstream

Parameter	Description	Format
Port *	The TCP port at which the service will listen for incoming connection requests.	Integer within range 1-65535

TCP Client Downstream

Parameter	Description	Format
Address *	Address of the remote host to which data will be forwarded, either an IP address or a hostname.	Internet host name, see RFC 1123, section 2.1
Port *	TCP port that the service will use to connect to the remote host.	Integer within range 1-65535
Automatic reconnect	When Enabled, automatic reconnect will make the service attempt to re-establish a broken connection to the remote host. If the remote host is unreachable during initial connection establishment, the service will wait for the host to become available, regardless of the value of this setting. The service will attempt to resend all data which has not been confirmed to reach the remote host. Automatic reconnect is useful when using protocols where the connection establishment, and the order of the following data, does not matter. For example, when forwarding syslog data. If setting the value to Disabled, no reconnection attempts will be made.	Available options: Disabled (default) and Enabled