The API Gateway ships with in-built support for TIBCO Enterprise Messaging System (EMS) and TIBCO Rendezvous enterprise-level products. The API Gateway can both produce and consume messages for both systems. This topic describes how to integrate with both TIBCO EMS and TIBCO Rendezvous. The reader is advised to follow the relevant links for more information on each of the steps involved.
The API Gateway can act as both a producer and consumer of TIBCO Rendezvous messages. In both cases, a Rendezvous daemon must be configured, which is responsible for communicating with other Rendezvous programs on the network.
Producing TIBCO Rendezvous Messages:
The following steps must be configured in order to produce messages and send them to another Rendezvous program. Follow the links below to learn more about how to configure each of the steps involved.
Consuming TIBCO Rendezvous Messages:
A TIBCO Rendezvous Listener can be configured at the API Gateway instance level in order to consume Rendezvous messages. The following steps must be followed in order to consume Rendezvous messages. Take a look at the help pages for the steps below for more complete information.
The API Gateway can also be configured to produce and consume messages for TIBCO Enterprise Messaging Service (EMS) product. The first step in configuring either a producer or consumer or EMS messages is to configure a TIBCO Connection. The producer or consumer can then be configured.
Producing EMS Messages:
The following steps must be configured in order to send messages to an EMS Server. Follow the links below to learn more about how to configure each of the steps involved.
Consuming TIBCO EMS Messages:
A TIBCO EMS Consumer can be configured at the API Gateway instance level to consume messages from a queue or topic on an EMS Server. The following steps must be followed to consume EMS messages. For more details, see the following topics:
