Response Route TCP


images/download/thumbnails/102597555/arrow_up-version-1-modificationdate-1656660209965-api-v2.png Introduction: You can find a description of this phase in section Phase 6 (Introduction).


images/download/thumbnails/102597555/image2020-3-19_16-10-26-version-1-modificationdate-1656660461567-api-v2.png

images/download/attachments/102597555/1183-version-3-modificationdate-1658825036103-api-v2.png


This Response Route has two use cases.

Use Case 1


If (1) is a client connection, the payload is sent there.

The response of the TCP server can be forwarded to a subsequent profile via Message (2). For setting details see Response Route Message. Note: If the connection uses a ByteHandler, the response is a Base64 string. See also function decode Base64(a, b).

Use Case 2


If (1) is a server connection and (1) is used in the profile in a TCP Input Agent, the payload is sent as a response to the TCP client that called the profile.

Payload


The payload is the content of the Response Route.

If (1) uses a StringHandler, specify a normal string.

If (1) uses a ByteHandler, a Base64 value must be specified. Use function convert hex to base64(a,b) to generate the value.

Input Agent


See section TCP (Input Agent).