AMQP listener
AMQP Listener
AMQP stands for Advances Messaging Queing Protocol.
The AMQP listener can be used to read from an AMQP destination. This destination can be a queue or topic in an AMQP environment. The connection factory determines which AMQP environment will be used.
This is a Message-driven consumer, which means that when a messsage arrives at the destination queue or topic, the consumer will be activated and the message will be consumed.
The ObjectToConnectMessageTransformer converts the message from the destination to a MessagePart and will write it to a new ConnectMessage.
The AMQP headers will be copied to the ConnectMessage.
In the table below, you will find an explanation of these properties. All attributes with a ‘*’ are mandatory.
Attribute |
Description |
Name* |
By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional. |
Enabled |
Set this value to true if you want this consumer to be enabled. |
Consumer Autostart |
Consumer will be started at startup of the interface. |
Request Queue Names* |
Names of the queues to receive from. |
Reply Queue Name |
Default queue to send reply to if sync=true and no header attribute amqp_replyTo. |
Synchronized |
Defines the consumer as request-response(true) or fire-forget(false). The default is false. |
Timeout |
Time-out in miliseconds. After time-out has passed response will be sent to Reply To. |
MessagePart Name |
Name of the MessagePart in a ConnectMessage where the content of the file is being stored. |
Connection Factory |
A connection factory determines which AMQP environment is used. By default we will use a connection factory incorporated as a Spring Bean with the name amqpConnectionFactory. If a different connection factory is desired, you may enter the name of another connection factory. This is a Spring reference. |
Concurrent Consumers |
Specify the number of concurrent Consumers to create. The default value is 1. Specifying a higher value for this setting will increase the standard level of scheduled concurrent Consumers at runtime: This is effectively the minimum number of concurrent Consumers which will be scheduled at any given time. This is a static setting. Raising the number of concurrent Consumers is recommended in order to scale the consumption of messages coming in from a queue. However, note that any ordering guarantees are lost once multiple Consumers are registered. |
Mapped Request Headers |
A comma separated list of headers to be mapped from the AMQP message to the ConnectMessage. The default are the standard AMQP properties. |
Description |
Description of the specific consumer. This is for documentation purposes. |