Does Solace tibco EMS supports JavaRTO as consumer?

Options
simply_sameer
simply_sameer Member Posts: 2

Hi Team,

We are planning to migrate from TIBCO EMS to Solace. We have done some PoC and planning to Java RTO Messaging API.

We have a use case where we need to sync data between Solace consumers and TIBCO Producers. We heard that Solace provides the connector for this but we are not sure if we can use it where the producer is using TIBCO EMS but the consumer is based on JavaRTO.

Based on the documentation we have seen like TIBO EMS connector is suitable when the Solace consumer is based on JMS API, Please confirm. Thanks

Best Answer

  • JamilAhmed
    JamilAhmed Member, Employee Posts: 18 Solace Employee
    #2 Answer ✓
    Options

    Hi @simply_sameer, welcome to the community!

    We heard that Solace provides the connector for this but we are not sure if we can use it

    You have heard correctly indeed, Solace do have a connector to TIBCO EMS, as well as various other target systems such as IBM MQ, Snowflake, SAP, etc. You will find all the options in the Integration Hub here: https://solace.com/integration-hub/

    The architecture is that one side connects to Solace, and the other side to your third-party system. (TIBCO EMS in this case.) Once messages from EMS have been read and published to Solace by the connector, how your application then chooses to consume it is completely independent. So could be a JMS consumer, .NET or JavaRTO. You are not coupled to how the connector itself is doing the message bridging or the third-party system the original message came from.

    Based on the documentation we have seen like TIBO EMS connector is suitable when the Solace consumer is based on JMS API, Please confirm. Thanks

    In other words, just because your original publisher is staying as JMS to TIBCO EMS, completely independently messages can be bridged over from EMS to Solace, and then you can consume that message however you wish. Perhaps even bridge it again somewhere else, such as to a Kafka topic using the Integrated Kafka bridging capability within the broker.

    Hope that helps clarify.

    Thanks.

Answers

  • JamilAhmed
    JamilAhmed Member, Employee Posts: 18 Solace Employee
    #3 Answer ✓
    Options

    Hi @simply_sameer, welcome to the community!

    We heard that Solace provides the connector for this but we are not sure if we can use it

    You have heard correctly indeed, Solace do have a connector to TIBCO EMS, as well as various other target systems such as IBM MQ, Snowflake, SAP, etc. You will find all the options in the Integration Hub here: https://solace.com/integration-hub/

    The architecture is that one side connects to Solace, and the other side to your third-party system. (TIBCO EMS in this case.) Once messages from EMS have been read and published to Solace by the connector, how your application then chooses to consume it is completely independent. So could be a JMS consumer, .NET or JavaRTO. You are not coupled to how the connector itself is doing the message bridging or the third-party system the original message came from.

    Based on the documentation we have seen like TIBO EMS connector is suitable when the Solace consumer is based on JMS API, Please confirm. Thanks

    In other words, just because your original publisher is staying as JMS to TIBCO EMS, completely independently messages can be bridged over from EMS to Solace, and then you can consume that message however you wish. Perhaps even bridge it again somewhere else, such as to a Kafka topic using the Integrated Kafka bridging capability within the broker.

    Hope that helps clarify.

    Thanks.