Hi,
we have 3rd party system where it is having JMS server . so from JMS queue messages need to push into solace queue. can we use solace JMS API option and will it directly connect to 3rd party JMS system?
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 
. If my response doesn’t make sense for your topic, please react to it with a 
.
Looking at the provided documentation, I cannot find specific information about connecting a third-party JMS server to a Solace software event broker queue using the Solace JMS API. The documentation primarily covers how to use the Solace JMS API to connect to Solace event brokers, not how to connect to third-party JMS servers.
You might find relevant information in the following sources:
I recommend searching the Solace documentation for specific integration scenarios with third-party JMS servers.
Hello,
JMS (Java Messaging System) is an interface definition, it is not a network protocol. JMS providers, like Solace and your third party system, commit to providing that interface so applications can be easily developed and ported. However the underlying implementation must by definition be tailored to the the provider system. The Solace JMS provides an interface to the Solace Message Format and that ability to send messages to the Solace Broker. Other JMS implementations exist for common message protocols like QPID-JMS (for AMQP) and MQTT. There are JMS implementations that target most third-party messaging systems as well. However each is unique to the system.
So Solace JMS will not work with your third-party system. However as the Solace Broker also supports MQTT and AMQP, those JMS implementations may work with Solace and your third-party system if it supports either AMQP or MQTT. Your mileage may vary, and Solace does not directly provide support for third-party JMS implementations.
You may also choose incorporate both JMS implementations into your app and bridge from your server to the broker that way.
Regards
Ragnar
You didn’t mentioned the 3rd party JMS provider name like IBM MQ, Tibco, anyways you can look at the Solace Integration Hub and specifically look for the generic JMS Microintegration. The purpose of the JMS MI is to bring the messages from 3rd party JMS provider to Solace queue.
Also there is dedicated MIs for IBM MQ, Tibco EMS
Hi Ragnar,
Thank you very much for your reply.
In nutshell, solace JMS API will not support directly to connect with 3rd party system. But AMQP or MQTT are options to connect 3rd party if it supports. please let me know if my understanding is correct.
Can we consider JMS JNDI also in this case?
Regards,
Janardhan
In your original post, you asked
will it directly connect to 3rd party JMS system
the answer is no as this implies a server-to-server communication which is not part of JMS.
What you will need is to have something like this:
3rd-party JMS Server → JMS Consumer (using 3rd-party provider → Solace Producer (using Solace native or JMS provider → Solace PubSub+ broker
Solace has such a thing available, assuming you can acquire the 3rd-party JMS provider, as part of our Micro-Integrations product line. There is a self-managed PubSub+ Connector for JMS that you could use to be that bridge between the 2 servers. This would address your use case.
Andrew
Hi Janardhan,
Please see Andrew and Mayur’s more complete posts above about possible routes to take when integrating with third-party JMS providers. Solace does have solutions for some third-party integrations and there is always the ability to develop your own.
Ragnar
Hi Andrew,
Thank you very much for your reply. I have checked with source system and currently they are connected through JMS JNDI to TIBCO system. As per my understanding to connect from 3rd party Jms to solace with JMS JNDI also there should be micro integration bridge is required.
If the solution needs to be straight forward then AMQP or REST API ( if application supports) are feasible options.
Please suggest on this.