we're evaluating Solace in combination with Boomi. What are the differences between the Boomi Generic JMS Connector or the Boomi Solace JMS Connector?
Hello and a Happy New Year to you,
It really depends on the use case which connector is more appropriate to use - the differences are:Generic JMS Connector:
Solace branded JMS Connector
If your use case allows to define all destinations up-front and requires transactions / persistence you would use the generic connector.
If you use fine grained topics in your use case you most likely will need to use dynamic destinations or wildcards on subscribers and hence you would use the Solace branded connector.
Finally you can also use MQTT and HTTP/REST connectors in Boomi to connect to Solace - this may appropriate in certain situations as well - e.g. HTTP/REST could be useful in situations where you need to connect through firewalls.
It depends on the use case which connector is appropriate - I'll list the differences below and add a few comments ..
Generic JMS Connector
Dynamic Req/Reply cannot be used
Solace JMS Connector
Does not use JNDI, Supports dynamic queue/topic creation
Finally - you can also use the HTTP/REST and MQTT connectors in Boomi to connect to Solace. For example - the HTTP protocol may be appropriate if you need to connect across firewalls/network zones. Solace also supports publishing messages to REST services exposed by Boomi using REST Delivery Points (RDP).
Solace JMS Connector
@swenhelge is this something you could assist with?
Hope this helps, sjaak
Sorry for my late reply but I recently joined this community. It appears that I haven't received email notifications of your replies.
Looking at it, the way we want to work with Boomi and Solace is support for dynamic queue/topic creation. The reason is simple: that is exactly what Boomi does already when you use the Boomi MQ solution. So that is why I tested the branded Solace connector. Thanks!
@sjaak Did your question get answered? If yes, please accept the answer by clicking "Yes" in the line above "Did this answer the question?". Thanks!
hi @hong, done