QUEUE_LISTENER service’s application configuration
Name Type Description Mandatory Default value

amqpServerConnection

object

The configuration for the AMQP server connection.

No

This can be defined as a shared configuration.

sourceName

string

The name of the AMQP queue from which to consume messages.

Yes

n/a

diffusionTopicTemplate

string

The Diffusion topic template to use for creating Diffusion topics. The template can include any message headers, such as '${JMSDestination}', or user-specified property keys, such as '${aCustomPropertyKey}', as placeholders. The placeholder for a message header will be replaced with the corresponding header value retrieved from the AMQP message, and the placeholder for a property will be replaced with the value of the specified property key. For example, if this configuration’s value is 'queue/${JMSDestination}/${location}', the 'JMSDestination' value is 'country', and the property key 'location' has the value 'london' in a message, the resulting Diffusion topic will be 'queue/country/london'. If such placeholders are included in the template, a new Diffusion topic will be created for each message, which may introduce overhead during message processing. If this parameter is not specified, the value of 'sourceName' will be used instead. If the value of a specified property key is not found or is empty, the service will fail to process the message and will be paused.

No

The value specified in the 'sourceName'

messageSelector

string

An optional SQL-like expression used to filter messages based on their properties. The selector determines which messages are delivered to the consumer. Only messages that match the specified condition will be received. E.g., 'priority > 5 AND color = 'red''.

No

""

noLocal

boolean

A boolean value to specify whether to inhibit the delivery of messages published through its own connection.

No

false

acknowledgeMode

string

The acknowledgement mode used to confirm the processing of messages. Supported values are AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, and DUPS_OK_ACKNOWLEDGE. These correspond to the session acknowledgement modes supported by the JMS API.

No

AUTO_ACKNOWLEDGE