HL7 LLP Listener – Monitors a specified TCP socket for HL7 messages.
Select the HL7 LLP Listener from the Listener Type drop-down. There are 4 tabs: Basic, Advanced, Mode and Compliance.
1. Basic: In the Basic tab you can specify:
Port: Specifies the TCP port to listen at, modified by application server.
Synchronous: Specifies if a Synchronous Response transport will be used to provide ACK responses.
Timeout: Specifies how long the Listener should wait for messages which are interrupted before timing out the connection.
Validate Messages: If selected, messages will be validated by HL7 HAPI library before starting processing.
2. Advanced: at the Advanced tab you can specify:
Initialize on trigger only: If enabled, the Listener doesn’t start up until a trigger initializes it.
Allow command-line invocation: If enabled, the Listener can be invoked using the CLI client application.
Restart on listening error: If enabled, the Listener will be restarted after error occurs.
FIFO Queue Name: The FIFO stuff enables a “First In, First Out” queuing mechanism between Listeners and Transports. If a “FIFO Queue Name” is provided, that name will be used as a key for a queue Transactions & will be pushed into before reaching a transport. They’ll be ordered in this queue according to when the Listener created them.
FIFO Queue Delay: It is the interval between updates/checks against that queue. Providing a queue name guarantees that a given Transport sends transactions in the same order the Listener created them in.
Ignore Inbound Ack: Ignore the Ack response.
3. Transaction Logging – This tab allows us to enable transaction events logging. That data can be logged by a TransactionEventListener.
The Transaction Logging Enable checkbox allows transaction events originating from this listener to be logged by a TransactionEventListener.
Log Transaction Attribute – if enabled, logs transaction attributes.
Log Transaction Data – if enabled, logs transaction data body.
Log Transaction Data Base64 – if enabled, logs transaction data body as Base64.
4. Mode: In the Mode tab, you can specify acknowledgement conditions. It can be Never, Always, Error/Reject Only or Success Only.
4. Compliance: This tab allows you to specify the following:
2.7 Compliance Mode: If enabled, switches to an alternative processing mode.
Invalid Character Handling: Behavior for unexpected, non-erroneous whitespace.
Disconnect on Error: Specifies if a client should be disconnected when it sends erroneous data.