How to Trigger Downstream Actions in Boomi from Solace PubSub+ Events?

Connectors & Integrations
1

Hello

I am currently working on a workflow where I want Boomi to perform downstream actions whenever a specific event is published in Solace PubSub+. :smiley:The challenge I am facing is figuring out the most reliable and low-latency method to ensure Solace events can trigger Boomi processes without polling / delay. :upside_down_face:

Is there a native connector or preferred integration pattern for this? Should I use a middleware layer like webhooks / Azure Event Grid to bridge the two? :upside_down_face: I have seen documentation around Solace & Boomi independently but not much on how they can interact directly in event-driven architectures. Checked Event-Driven Integration with Solace and Boomi | Solace guide for reference.

While exploring event-driven integrations; I also came across a similar use case involving Azure Databricks, which made me wonder what is Azure Databricks really capable of when combined with Solace for real-time data processing? :innocent:

If anyone has experience building such an integration pipeline / even partial steps like consuming Solace messages in Boomi using a JMS or REST API please share your insights.

I am particularly interested in real-world use cases that maintain message order & guarantee delivery.

Thank you !! :smiley:

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Based on the documentation and community discussion, I can provide information about integrating Solace PubSub+ software event broker with Boomi. However, there is no direct information about Azure Databricks integration in the provided documentation.

For Boomi integration:

The documentation shows a pattern for handling delayed message processing with Boomi that involves:

  1. Using separate queues with different configurations:

    • Queue A: For sales order created messages with TTL of 15 minutes
    • Queue B: For sales order cancelled messages
    • Queue C: For “approved” sales orders

  2. Two Boomi processes:

    • A scheduled process that consumes messages with TTL
    • A listener process that handles cancellations by:
      • Listening to queue B for cancellations
      • Using a selector to consume related orders from queue A

This approach:

  • Maintains state in the event broker rather than requiring external storage
  • Provides guaranteed message delivery
  • Allows for message correlation between create and cancel operations
  • Supports the 15-minute cancellation window requirement

Relevant sources:

For Azure Databricks integration, I don’t have enough information in the provided documentation to provide specific guidance. You would need to consult the Solace documentation for details about integrating with Azure services.

3

HI,

You just need the native Solace connector available within Boomi.

https://help.boomi.com/docs/Atomsphere/Integration/Connectors/int-Solace_PubSub_connector_b38dbd64-539a-40f5-854b-1efd40b4477d

Use the listen operation as a start activity in your Boomi flow:
https://help.boomi.com/docs/Atomsphere/Integration/Connectors/int-Solace_PubSub_operation_cb98e0ea-7e6f-4d26-bcfd-8b857a07820c#listen

No need for REST/polling or generic JMS connections (although you could use the JMS listen operation as well - it’s a bit harder to set up and limited in functionality compared to the native connector).
A Boomi process with the listen operation creates a listener on the Boom runtime that receives message in real-time/low latency from the broker it is connected to.

Since you want reliable delivery you need to consume messages from a queue. This article may be helpful:

Important - the pattern to use is “publish to topic, consume from queue”. Solace queues can subscribe to topics which means you can easily combine the “one to many” pattern of topics with a guaranteed delivery of relevant events to a client.

See Topic to Queue Mapping