🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Boomi/Solace: how to set dmq-eligeble=true by default for REST end points

sjaak
sjaak Member Posts: 109 ✭✭✭
in Connectors & Integrations #1

Hi,
We have the following use case

  • Apps are using Solace REST endpoints to send messages to Solace topics
  • Multiple queues are subscribed to this topic
  • It appears that REST clients need to set a HTTP header "Solace-DMQ-Eligible: [true|false]" in order to use the DMQ feature
    Question: can we somehow set the default to true for any Solace queue which are created? Just like with JMS, see JMS Connection Factories | /jms/cf/default settings on management console page.
Tagged:

Best Answer

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #2 Answer ✓

    Hi @sjaak,
    I can see the sense in what you're saying, so thanks for bringing this to our attention. I'll raise a product enhancement request.

Answers

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #3

    Hi @sjaak, I don't think there is a way to enforce a specific message property like this. You're right in that it's possible to force certain message properties using a JMS Connection Factory, one being DMQ eligibility, but this only applies to JMS.

    A quick and dirty workaround could be to create a service which consumes your REST messages and re-publishes them via JMS through such a connection factory... but that isn't really a production solution!

  • sjaak
    sjaak Member Posts: 109 ✭✭✭
    edited January 2021 #4

    Hi @TomF,
    Thanks. For this use case, we have decided to ask the customer to add the HTTP header "Solace-DMQ-Eligible: true". This will of course work. However, we also have use cases where messages are pushed to Solace REST end points using webhooks. In practice, webhooks are often limited in terms of configuration. So, adding HTTP headers is usually not possible.

    It would be good if the dmq-eligible functionality can be set globally so it behaves consistently and, if you wish, independently from the underlying interface (JMS, REST, etc).

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #5 Answer ✓

    Hi @sjaak,
    I can see the sense in what you're saying, so thanks for bringing this to our attention. I'll raise a product enhancement request.

  • sjaak
    sjaak Member Posts: 109 ✭✭✭
    #6

    That is great, thank you! :)

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #7

    @sjaak, a quick update: this feature has been added to our Feature Candidate List. We're just waiting for a slot to add it to the roadmap.

  • Chintan
    Chintan Member Posts: 2 ✭
    #8

    Hi @TomF As this is an old post, so I am expecting that this feature must be available now in Solace. Could you please guide me on how to enable this on console ? as our publisher is using webhooks to push the data to Solace and they don't have the possibility to use this header param "Solace-DMQ-Eligible: true".

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #9

    Hi @Chintan, we've had some discussions about implementation details, but it hasn't been delivered yet. Since you're a cloud customer, please submit a support ticket so your interest is tracked. The original enhancement request ticket number is 48481.

  • Chintan
    Chintan Member Posts: 2 ✭
    #10

    Thanks @TomF for your quick response ! I will get in touch with Solace support.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    edited August 29 #11

    I thought we eventually made that true by default for the REST API? Wow, that's too bad. I know it was made the default in our AMQP protocol implementation, and I convinced them to make it true for MQTT publishers as well. And our new "next-gen" APIs have this set by default.

    Thanks Tom for the RT number, I've commented on that ticket as well.

  • sjaak
    sjaak Member Posts: 109 ✭✭✭
    #12
    https://solace.community/discussion/comment/7245#Comment_7245

    Thanks for your support @Aaron 😊

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #13

    Hey @sjaak, no problem! I reached out to our Product Management team a couple weeks ago to get an update… apparently this feature is now imminent… being able to override the DMQe behaviour at either the queue/endpoint, or configurable within the client profile. So… hopefully by Christmas maybe? Stay tuned!

Categories

This Month's Leaders

This Week's Leaders