Boomi: Atom Message Queuing Part 2 – Atom Queue Connector

As mentioned in this blog, Boomi: Atom Message Queuing Part 1 – Overview, we now have an overview of Boomi Atom message queuing.

In this blog we are going to explore the essential components of the Atom Queue Connector:

  • Atom Queue Component
  • Atom Queue Connection
  • Atom Queue Operation


Atom Queue Component

The ‘Atom Queue Component’ is the most important part of Boomi Atom message queuing. Imagine this as a pipe that allows messages to be added by publishers. You can define Queue Name and choose the following Queue Type:

  • Point-to-point – This will guarantee all messages in the queue are delivered successfully to a single subscriber. A message remaining in the queue will only be removed when:
    • It is read and processed successfully
    • Deleted manually via Queue Management console
  • Publish/subscribe – This allows the publisher to add messages to the queue and the same copy of messages can be consumed by multiple subscribers. If there is no active subscriber, the message will be considered expired and removed from queue immediately.


Atom Queue Connection

This is used in a Boomi Atom Queue connector to define the connection to an Atom Queue.


Atom Queue Operation

There are 3 types of operation supported by Boomi Atom Queue connector:

  • Get – This is the normal operation that can be used at start shape and any part of the process to retrieve messages from Atom Queue. This can be considered as a non-real time operation as it will only read messages when the process is running.
  • Listen – This option is only available on start shape. This type of operation will stay active to retrieve messages from the queue for processing as soon as a message is added to a queue. This is similar to the web service listener in Boomi’s SOA Framework.
  • Send – This is used to add messages to a queue.


Considering that messages in Boomi Atom Queue can only be accessed within an atom, you would need to utilize the operations highlighted above to get/send messages from/to a queue.

For more configuration options in operations, you can refer to this official document.


In the next post, we will be discussing the differences between the operations in detailed. Stay tuned!