LLP Client |
 | ||
|
This documentation page describes a feature of version 3.3 of Iguana. For information on how to configure the LLP Client destination component in version 4.0 or later of Iguana, see LLP Client. | ||
 |
In order to configure the LLP Client destination component described in the Channel Destination Components section of the manual, you must define the following properties:
| Property | Description |
|---|---|
| Host address* | IP address of the target application's machine. |
| Port* | Port that the target application is expecting to receive LLP encoded HL7 messages on. |
| ACKnowledgment verification | Set this to Any Message if you want to consider any message sent back from the target machine as a valid acknowledgment. Set this to Any ACK Message if you want to use the provided VMD (ack_verify.vmd) in the Iguana install directory to parse the ACK and ensure that it is an ACK HL7 message. When using this setting, Iguana checks if the acknowledgment is valid using only the message identity. The ack_verify.vmd has "ACK" listed as the message type, meaning Iguana will expect "ACK" to be the message type of the ACK message from the target machine. Set this to Verified ACK Message for the strictest ACKnowledgment checking. This ensures that the ACK sent back from the target machine is acknowledging the appropriate message. By default, Iguana expects the message type to be ACK. If the ACKs you are receiving from the target machine contain a different message type, you will receive an error since ACK is what Iguana is expecting. In these cases, you must change the identity of the ack_verify.vmd file (located in the Iguana install directory) accordingly. When this option is selected, the ack_verify.vmd is used to parse both the ACK message and the original message, and it compares the values in the messages. In the ack_verify.vmd file, there is a table called MSH. This table is used to compare the MessageControlID fields in the original and ACK messages. You can add even more control to the way that ACKs are verified by adding fields to the MSH table and mapping them to the fields that you want to compare. For example, you may want to compare the message type in the ACK to the message type in the original message. |
| ACK VMD path | Location of VMD to use for parsing the received ACK message to determine its validity. Default file is typically fine to use. |
| ACK timeout | Number of milliseconds to wait for an ACKnowledgment message back from the target application. After this expires, the message will be resent. Set this to 0 when you know you will not be receiving an ACKnowledgment from the target application. |
| Number of send retries | Number of times the HL7 message will be resent before the LLP Client gives up and informs the source component that the message was rejected by the target. Note that messages are only resent in the case where a positive ACK is not received within the ACK timeout period. If Iguana is unable to send a message, the channel will be stopped. |
| Disconnect between retries | If set to true, the channel will disconnect between each retry before attempting to reconnect. If a connection is successfully made, it tries sending the message again. If set to false, the channel will disconnect and stop after it reaches the specified Number of Retries. |
| Number of reconnection attempts | Specifies the maximum number of times the channel will attempt to connect to the remote host in the case where the connection is not established or dropped. Setting this field to -1 means that there is no limit to the number of reconnection attempts. |
| Reconnection interval | Milliseconds to wait between connection attempts. |
| Automatically purge error logs older than | Specify when error logs are stale and can be deleted. If this value is 0, then error logs will never be automatically purged. |