TIBCO Rendezvous Adapter overview
The TIBCO Rendezvous Adapter facilitates mapping of data to and from the TIBCO Rendezvous product, as well as launching maps based upon a message arrival from a TIBCO Rendezvous messaging system.
The TIBCO Active Enterprise Release 7 or later, including Rendezvous, provides a substantial improvement in transport stability and efficiency as compared to previous releases. A main feature is that the Rendezvous sub-system is completely thread-aware, whereas, in previous releases the system was thread-safe, but not thread-aware. This necessitated adapter dependence upon an existing operating system transport such as TCP or pipes to implement thread-safe behavior. This restriction has been removed in the latest release.
Several central features of earlier releases have been made obsolete in TIBCO Rendezvous Release 7 or later: sessions, event manager contexts, signal events, and unitary message (that is, a message containing a single datum and no fields).
In earlier releases, the session was a key architectural element, encapsulating a TIBCO Rendezvous daemon connection, an event manager context, an event queue, and an event dispatcher-all in a single object. Release 6 separates these roles for greater flexibility and ease of use:
- Programs (the adapter) create transport objects to send outbound messages and receive inbound messages. Some types of transport connect to the TIBCO Rendezvous daemon; others do not.
- Programs (the adapter) create event queues for inbound messages and other events.
- The TIBCO Rendezvous event driver places events on the correct event queues.
- Programs (the adapter) dispatch events from their event queues.
When a program from an earlier release sends a unitary message and a program using Release 6 or later receives it, the receiver reformats the inbound message, placing the single datum in a field named _data_ with no field identifier.
The subject of a message defines a mailbox name for which a message listener will accept and process received messages. To receive messages, a TIBCO Rendezvous listener must be registered to receive a subject of interest. The subject name might consist of a single element subject (mySubject) or hierarchical multiple element subjects (mySubject.myData.myName). Wildcards are supported for use with the Subject Name adapter command (-SBN). Subject names are, at most, 255 characters in length. The maximum element length is 252 characters.
The TIBCO Rendezvous Adapter supports both regular and certified message delivery based upon the specified adapter commands and the capability of the installed TIBCO Rendezvous product.