Log out?

UDP Listener

The UDP Listener is used for receiving UDP messages on a given port.

UDP Basic Configuration Options for PilotFish Listener or Adapter.

On the Basic configuration tab, you should specify Listener Port – the UDP port to listen on.

UDP Advanced Configuration Options for PilotFish Listener or Adapter.

The Advanced tab allows you to 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 an error occurs.

FIFO Queue Name: The FIFO field 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.

UDP Transaction Logging Options for PilotFish Listener or Adapter.

Transaction Logging: This tab allows us to enable transaction events logging. That data can be logged by a TransactionEventListener.

The Transaction Logging Enable: This checkbox allows transaction events originating from this listener to be logged by a TransactionEventListener.

Log Transaction Data: If enabled, logs transaction data body.

Log Transaction Data Base64: If enabled, logs transaction data body as Base64.

Log Transaction Attribute: If enabled, logs transaction attributes.

Log All Attributes: If enabled, no attributes will be filtered.

Allowed Attributes: Attributes which are allowed to be logged.

This is a unique website which will require a more modern browser to work! Please upgrade today!

Thanks!

Our editors are notified.

Close