The TCP Client communication point connects to a remote TCP server listening for connections on the port specified by the Remote Host and Remote Port properties. The optional properties Local Address and Local Port can be used to force the communication point to connect using a specific interface and local TCP/IP port number.
Messages on a TCP stream must be wrapped with a header and/or trailer in order to identify when a message starts and ends. The input and output Wrapper, Header, Trailer, and Endian-ness properties are used to configure message wrapping.
Supported Operational Modes: All
Input Mode Properties
Property |
Description |
---|---|
Remote Host |
The hostname or IP address of the remote system (a TCP server) to which the client will connect. This is required for a TCP client in order to make a connection. |
Remote Port |
The port number on the remote host to which the client will connect. |
Local Address |
The hostname or IP address of the local interface to bind the socket connection (all interfaces if empty). It generally should be left blank. It is usually only used if your Rhapsody server has multiple network interfaces (that is, multiple network cards, or network card and VPN connection, and so on) and you want to explicitly force the TCP client connection to use that particular network interface. There are generally very few scenarios where this is required. |
Local Port |
The port number to bind the local socket. If you do not set this, Rhapsody will pick an unused port. |
Use SSL |
Whether to use SSL:
It is recommended that you enable SSL for TCP Client communication points whenever it is supported by the remote server. Refer to TLS/SSL Support in Rhapsody for details. |
SSL Protocol Mode |
Refer to SSL Protocol Versions for details. |
SSL Cipher Suites |
Refer to SSL Cipher Suites for details. |
Use SSL Client Mode |
Whether to use SSL client mode:
Note that this is not the same as enabling client authentication: TLS client authentication is enabled by configuring one or more trusted certificates for the connection. Secure Keys configures the private key that each client-server side uses to authenticate itself to the other side; Trusted Certificates configures how each client-server side authenticates the other side. |
Secure Keys |
Identifies the private keys used for authenticating Rhapsody's end of the SSL connection. When configured with a private key, the SSL client supports SSL client authentication if requested by the SSL server. Refer to Client Authentication for details. |
Trusted Certificates |
Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is not configured with the SSL server's certificate, then this SSL client operates in anonymous server authentication mode. It is highly recommended that the server's certificate always be provided here to allow server authentication to be performed. Refer to Server Authentication for details. |
Connection Timeout (ms) |
The time in milliseconds to wait for a connection being established before aborting the connection attempt. A value of zero or less is treated as an infinite timeout. In most cases, this does not need to be changed as the connection either succeeds or fails prior to this timeout. The default value is |
Dynamic Connection Failed Action | Whether to treat errors as message or connection errors when the host or port uses properties or variables.
|
Log Connections |
Whether to log connections and disconnections:
|
Log Data |
Whether to log data:
|
Log Data As Hex |
Whether to log data in hexadecimal form:
|
Connection Log File |
The full file name (path and file name) of the file on the server to log the information to. |
Extra Information |
Whether to include extra log information:
|
Connection Mode |
The connection mode:
|
Incoming Wrapper |
Message wrapping around messages received over the socket connection.
Refer to Wrapper Options for details. |
Strip Wrapping |
Determines whether or not to strip the wrapping off received messages:
Refer to Strip Wrapping for details. |
Incoming Header |
This property defines the header that identifies the start of a message on the socket connection. Only available when Incoming Wrapper is set to |
Incoming Trailer |
This property defines the trailer that identifies the end of a message on the socket connection. Only available when Incoming Wrapper is set to |
Incoming Endian-ness |
Determines the incoming endian-ness:
Only available when Incoming Wrapper is set to |
Output Mode Properties
Property |
Description |
---|---|
Remote Host |
The hostname or IP address of the remote system to which the client will connect. |
Remote Port |
The port number on the remote host to which the client will connect. |
Local Address |
The hostname or IP address of the local interface to bind the socket connection (all interfaces if empty). |
Local Port |
The port number to bind the local socket. |
Use SSL |
Whether to use SSL:
It is recommended that you enable SSL for TCP Client communication points whenever it is supported by the remote server. Refer to TLS/SSL Support in Rhapsody for details. |
SSL Protocol Mode |
Refer to SSL Protocol Versions for details. |
SSL Cipher Suites |
Refer to SSL Cipher Suites for details. |
Use SSL Client Mode |
Whether to use SSL client mode:
Note that this is not the same as enabling client authentication: TLS client authentication is enabled by configuring one or more trusted certificates for the connection. Secure Keys configures the private key that each client-server side uses to authenticate itself to the other side; Trusted Certificates configures how each client-server side authenticates the other side. |
Secure Keys |
Identifies the private keys used for authenticating Rhapsody's end of the SSL connection. When configured with a private key, the SSL client supports SSL client authentication if requested by the SSL server. Refer to Client Authentication for details. |
Trusted Certificates |
Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is not configured with the SSL server's certificate, then this SSL client operates in anonymous server authentication mode. It is highly recommended that the server's certificate always be provided here to allow server authentication to be performed. Refer to Server Authentication for details. |
Connection Timeout (ms) |
The time in milliseconds to wait for a connection being established before aborting the connection attempt. A value of zero or less is treated as an infinite timeout. In most cases, this does not need to be changed as the connection either succeeds or fails prior to this timeout. The default value is |
Dynamic Connection Failed Action | Whether to treat errors as message or connection errors when the host or port uses properties or variables:
|
Log Connections |
Whether to log connections and disconnections:
|
Log Data |
Whether to log data:
|
Log Data As Hex |
Whether to log data in hexadecimal form:
|
Connection Log File |
The full file name (path and file name) of the file on the server to which you want to log the information. |
Extra Information |
Whether to include extra log information:
|
Connection Mode |
Determines the connection mode:
|
Outgoing Wrapper |
Message wrapping around messages received over the socket connection. Refer to Wrapper Options for details.
|
Outgoing Header |
Defines the header written to the socket connection before each message. Only available when Outgoing Wrapper is set to |
Outgoing Trailer |
Defines the trailer that is written to the socket connection after each message. Only available when Outgoing Wrapper is set to |
Outgoing Endian-ness |
Determines the outgoing endian-ness:
Only used when Outgoing Wrapper is set to |
Outgoing TCP Packets | Determines whether to include the wrapper in the same TCP packet:
Only applied when Outgoing Wrapper is not set to |
Bidirectional, In->Out and Out->In Mode
The configuration properties for the TCP Client communication point in Bidirectional, In->Out and Out->In modes is a combination of the properties described above.
Refer to Out->In and In->Out Properties for general details on a communication point's In->Out and Out->In modes.
Connection Monitoring
Refer to Connection Monitoring for details.