Messages between eFTL Clients and EMS Clients
An EMS channel can forward messages between eFTL applications and a TIBCO Enterprise Message Service (EMS) server, which in turn provides access to EMS applications.
The following figure shows applications that publish and subscribe. Applications at the eFTL side connect to the eFTL service, while those at the EMS side connect to the EMS server. The eFTL service connects to the EMS server as a client.
eFTL clients can publish or subscribe to an EMS queue as well as a topic. To do this, the eFTL client prefixes the destination name with QUEUE: .
The EMS channel forwards messages in two ways:
- from eFTL publishers to EMS topics or queues in the EMS server.
EMS applications that subscribe to a topic receive its messages. The EMS server can also store messages for persistence (optional) using durables.
- from EMS topics to eFTL subscribers. The EMS channel subscribes to EMS topics or queues on behalf of eFTL subscribers.
Translation
When an EMS channel forwards a message, the eFTL service translates the message format appropriately; for details, see Message Translation TIBCO eFTL and TIBCO EMS.
Round-Trip Forwarding
All messages that flow through an EMS channel must pass through the EMS server, even messages that travel from eFTL publishers to eFTL subscribers. The EMS channel forwards messages to the EMS server, which delivers them back to the channel, which in turn forwards them back to the eFTL side.
The channel translates such messages twice: once in each direction, to and from the EMS server.