This function has two use cases.
Use case 1
If a is a client connection (see TCP connections), payload b is sent there.
The return value of the function is the Response as a string.
NOTE: If the connection uses a ByteHandler, the response is a Base64 string. See also function decode Base64().
Use case 2
If a is a server connection (see TCP connections) and a is used in the Profile in a TCP Input agent, b is sent as a response to the TCP Client that called the profile.
Parameters
Parameter | Description |
|---|
a | The TCP alias of the connection (see TCP connections). |
b | If a uses a StringHandler, specify a normal string. If a uses a ByteHandler, a Base64 value must be specified. Use function convert hex to base64() to generate the value. |
The response determines how a profile sends processed data. In Phase 6, a response determines how and where the output data is sent or stored, e.g., via FTP, HTTP or e-mail. A profile can use several responses in parallel.
A profile is the central configuration unit in the Lobster Data Platform. It receives data, processes it, and forwards it. Configuration is done graphically, with no programming required.
The input agent receives data in Phase 1 and starts a job for further processing. It works either as event based (passively waits for data) or scheduled (actively fetches data).
An organizational unit that enables multi-client functionality in the Lobster Data Platform. Each client manages its own profiles, partners, users, and resources in isolation from other clients. This allows for the operation of multiple independent environments on a single instance.