Interoperation with Apache Pulsar

TIBCO Enterprise Message Service can exchange messages with supported versions of Apache Pulsar.

Note: This feature is only supported on Linux platforms.

EMS transports for Pulsar facilitate communication between EMS and Pulsar. They enable the EMS server to act as a Pulsar client, capable of connecting to and exchanging messages with Pulsar brokers.

The message flow between the EMS server and Pulsar brokers is described by the transport definitions in transports.conf (see Transports) and the EMS topics in topics.conf (see Topics). Each transport definition contains the URL of the Pulsar broker the transport will communicate with. EMS topics can be associated with these transport definitions using the import and export destination properties.

When an EMS topic is configured to import messages from a transport, the EMS server instructs the transport to listen for messages on the Pulsar topic with the same name as the EMS topic. Any Pulsar messages received by the transport are translated into Jakarta Messaging messages and imported to the EMS topic.

When an EMS topic is configured to export messages to a transport, the EMS server takes the Jakarta Messaging messages present on that topic, translates them into Pulsar messages and instructs the transport to publish the messages to the Pulsar topic with the same name as the EMS topic.

Warning: Do not configure EMS and Pulsar round-tripping. That is, do not send messages from EMS to Pulsar and then back to EMS, or the other way around.