TIBCO FTL
TIBCO FTL® messaging products are used for sending messages from one point to another. For Release 5.2, TIBCO BusinessEvents has added support for sending and receiving events using TIBCO FTL as the medium.
TIBCO BusinessEvents can now receive incoming TIBCO FTL messages and send TIBCO FTL messages across TIBCO BusinessEvents.
The purpose of the TIBCO FTL API is to demonstrate the use of TIBCO FTL as a means to send and receive TIBCO BusinessEvents events, which can be done with ease.
TIBCO FTL Terminology
A publisher sends a particular form of message. The message format is defined using a JSON file.
A subscriber listens to the endpoint and receives messages. The information of a subscriber is also in the JSON file in TIBCO BusinessEvents.
The publisher and subscriber both have a particular endpoint similar to a destination in TIBCO BusinessEvents.
Endpoints can send different types of messages. Endpoints also simplify the arrangements when multiple transports carry the same message stream. An endpoint abstracts all of the transport details into a simple name, which insulates application programs from those details.
Transports immediately carry messages from publishers to subscribers. Messages do not pass through an intermediary, such as a server. Transports neither store messages in transit, nor forward them later.
Sometimes a small enterprise needs only one communication fabric. However, at other times development and test environments are needed, which must not interfere with a production environment. Each of these environments requires a separate communication fabric, and isolating their communication from one another must not occur. In TIBCO FTL, a realm represents one communication fabric, with its endpoints, applications, application instances, transports, stores and formats.
A content matcher selects a subset of messages from a message stream according to the fields and values in those messages. A subscriber uses a content matcher to express interest in the subset of messages that the content matcher specifies. Therefore, without a content matcher, a subscriber receives all of the messages that arrive at its endpoint. Thus, by using a content matcher, a subscriber receives only a subset of those messages, specifically those messages that fit the matcher's specifications.
For more information regarding concepts and definitions related to TIBCO FTL, see TIBCO FTL® Concepts.
- Using TIBCO FTL in TIBCO BusinessEvents
TIBCO BusinessEvents makes use of event objects to communicate with TIBCO FTL. For maximum performance, you must have the TIBCO FTL application, define endpoints, transport names, define whether the transports will send or receive, and figure out the format.