To LLP
The To LLP component sends messages to a port using the LLP protocol. It receives data from an upstream component.
Running the Component
The below steps assume an existing port is available to connect to and the necessary firewall permissions are in place on the client and server.
STEP 1: Import the To LLP component
Using +COMPONENT, import the To LLP component. Since it is a destination component, you will need to Edit Connections to link it to a source component that will push it data to send to the server port.
STEP 2: Set up the component configurations
Bolded fields are required, otherwise default values defined in config.json are used:
Connection Configurations:
Field | Description | Default Value |
|---|---|---|
Host | The IP address or domain name of the target machine. |
|
Port | The port number of the target machine. |
|
Persistent Connection | Whether or not to persistently connect to the remote host. |
|
Connection Retry Count | Number of reconnect attempts if the connection is lost. |
|
Retry Pause (s) | Length of pause between reconnect attempts in seconds. |
|
ACK Configurations:
Field | Description | Default Value |
|---|---|---|
Wait For Ack | Wait for an ACK before sending the next message. If false, all settings below are ignored. |
|
Ack Timeout (s) | Number of seconds to wait for an ACK. |
|
Disconnect Between Resends | Disconnect from the server between resend attempts. |
|
Message Retry Count | Number of attempts to resend data until ACK is received. |
|
Security Configurations:
Field | Description | Default Value |
|---|---|---|
Enable SSL | Enable to receive messages securely using SSL. |
|
Certificate Authority File (Optional) | Path to Certificate Authority File. If path is blank, Verify Peer will be disabled. If path is entered, Verify Peer will be enabled. |
Message Configurations:
Field | Description | Default Value |
|---|---|---|
LLP Prefix | Prefix to use in LLP data. Should be in the form of an escaped hex value. |
|
LLP Suffix | Suffix to use in LLP data. Should be in the form of an escaped hex value. |
|
Message Encoding | The encoding used in the input data. List of available encodings is available when you click to change the encoding. |
|
Component Configurations:
Field | Description | Default Value |
|---|---|---|
Ack Error Handling | Error handling option if ACK is not received. Options: Stop the component. Skip the message. |
|
Print Debug Logs | Enable/disable logging of additional debug information. |
|
STEP 3: Start the component and verify data is being received on target server
Start the component.
Once inbound data is processed, check that the target server is receiving the data as expected.
Adapting the Component
There are a few ways you can adapt and expand this component for more complex workflows:
ACK Verification
By default, the To LLP component assumes that an ACK received from the target server is valid and verification is not needed. In some cases, additional ACK verification may be required.
Logic can be added to the ACKverify function to verify the ACK data. The function should return true/false based on the result of the verification.
