Open topic with navigation

TIBCO Flogo® Connector for Microsoft Azure Service Bus 1.4.3

# Microsoft Azure Service Bus QueueReceiver

The QueueReceiver trigger is used to poll a particular queue for any messages that may be posted by one or more publishers in a one-to-one message delivery pattern. Messages posted to the queue by publishers are received by polling Queue receivers in a First In First Out format and only one queue receiver can retrieve any one message. All queue receivers to a particular queue within a namespace compete with each other to retrieve messages from the head of the queue. When creating a queue, you can check the box to specify whether to enable sessions.

You can enable Application properties for some fields by turning on the toggle if one is available. Application properties allow you to provide values for configuration fields.

## Trigger Settings

The Trigger Settings tab has the following fields.

Field | Description
--- | ---
AzureServiceBus Connection | The AzureServiceBus Connection chosen for the QueueReceiver while creating the trigger is displayed here automatically. If you wish to choose a different AzureServiceBus Connection than what was chosen in the settings page of Trigger creation, you can click the dropdown and choose a different one.
Queue | Name of the queue to poll continuously for messages. A queue by that name must exist in the namespace of the broker. Application Properties has been enabled for this field.
DeadLetter Subscription | The possible values are true or false. When you set the DeadLetter Subscription value as "true", the unsuccessfully processed messages are stored in the dead letter queue and can be retrieved as needed.
SessionId | Name of the session from which to receive messages. When enabled, allows the QueueReceiver to listen for messages from the specified SessionID. If a queue is session-enabled, but a SessionID is not specified, then the QueueReceiver does not send any message.
Receive Mode | Determines the quality of service while receiving messages from a queue. ReceiveAndDelete: Messages are consumed and marked acknowledge on a trigger itself. ModePeekLock: This allows consumers to peek at a message from the queue or subscription and then lock it for processing.
Timeout | Timeout in milliseconds for the operation of an activity.
Retry Count | The number of times the flow attempts to run the trigger. Default: 0 Note: The Retry Count value can also be set from the connections details, but the value set here are preferred.
Retry Interval | The time (in milliseconds) to wait in between each attempt to run the trigger. Default: 0 milliseconds Note: The Retry Interval value can also be set from the connections details, but the value set here are preferred.

## Output Settings

The Output Settings tab has the following field:

Field | Description
--- | ---
Custom Properties | User can add the custom properties while receiving the messages.

## Map to Flow Inputs

The Map to Flow Inputs tab displays the schema in a tree format. The output is read-only. The following elements are present in the output schema:

1. output: The root of the output
   1. messageString: The string representation of the byte array of the received message.
   2. brokerProperties: A complex object that acts as a container for broker properties of the received message. The QueueReceiver trigger displays the following broker properties of a received message if available:
      - ContentType
      - CorrelationId
      - Label
      - PartitionKey
      - ReplyTo
      - SessionId
      - TimeToLive
      - To
      - DeliveryCount
      Note: For more information about `brokerproperties`, see the Microsoft Azure Service Bus documentation.
   3. deadLetter:
      - reason, description: These properties are populated when the message is read from the deadLetter queue. These are enabled when the DeadLetter Subscription property value is set as true on the Trigger Settings tab.
   4. customProperties: These properties are populated when you add custom properties on the Output Settings tab of the QueueReceiver trigger.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Flogo® Connector for Microsoft Azure Service Bus

Copyright © 2018-2025. Cloud Software Group, Inc. All Rights Reserved.