Client

When Lobster Integration acts as a TCP client, i.e. sends messages to a TCP server.

(1) Alias: The alias to be assigned for this connection.

(2) Host/IP: The URL/IP of the TCP server.

(3) Is an SSL connection: Set the checkbox and select a local certificate for an SSL connection. If necessary, specify passphrase (4).

(4) PassPhrase for SSL KeyStore: See (3).

(5) RequestHandler: Specifies for the StringRequestHandler what is appended as the end-of-message flag (6) to the requests sent to the server. Note: The value can also be specified in hexadecimal with the prefix 0x, e.g. 0x0a for a newline.

For the ByteRequestHandler, the length in bytes is specified in (6).

(6) Separator for requests: See (5).

(7) ResponseHandler: Specifies for the StringResponseHandler, what is interpreted as the end-of-message flag (8) in responses sent by the server. Note: The value can also be specified in hexadecimal with the prefix 0x, e.g. 0x0a for a newline.

For the ByteResponseHandler, the length in bytes is specified in (8).

(8) Data length for responses: See (7).

(9) Single Connect: If set, a connect/disconnect is performed on each request, otherwise standing connection (d efault is 60 minutes, but can be changed with system property hub.datawizard.tcp.handler.idletime). Note: See also function disconnect tcp-client().

Server

When Lobster Integration acts as a TCP server, i.e. receives messages from a TCP client.

The setting options are analogous to the client, but (2) cannot be changed because Lobster Integration acts as a TCP server and (9) is also not available.

See also

• disconnect tcp-client()

• send data with tcp-client()

• TCP (Input Agent)

• Response "TCP"