Adapter Rendezvous Side
The adapter's Rendezvous side translates Rendezvous messages into FTL messages, and transmits them to FTL clients.
The adapter's Rendezvous side begins by listening for connections from Rendezvous clients. Clients connect to the adapter daemon as they would connect to any TIBCO Rendezvous daemon.
Rendezvous clients send messages. The daemon delivers each message within its Rendezvous network. In addition, the adapter processes each message as follows.
Each time a Rendezvous message matches the subject specification in one of the configuration’s tags, the adapter attempts to translate it to an FTL message. The tag guides the translation.
- The adapter translates and stores the Rendezvous subject.
- If the Rendezvous subject is a multicast subject name, the adapter stores its elements in FTL fields.
- If the Rendezvous subject is an inbox name, the adapter maps it to an FTL inbox and stores the FTL inbox in an FTL field.
- Then the adapter attempts to fill each of the remaining fields of the FTL format with values from the Rendezvous message.
The adapter attempts to get a Rendezvous field with the same name as the FTL field.
- If the Rendezvous field type maps to an FTL field data type, then the adapter translates the Rendezvous field value to an FTL field value of the appropriate data type.
- If the Rendezvous field type does not map to an FTL field data type, then the adapter either discards the entire message, or skips the field, depending on the attribute of the tag.
(See Adapter Data Type Mapping.)
-
After translating all the FTL fields, the adapter publishes the translated FTL message on the relevant FTL endpoints.
Rendezvous Unnamed Fields
Rendezvous messages support unnamed fields, accessed only by index or field identifier. In contrast, FTL messages do not support unnamed fields.
The adapter does not translate unnamed fields. When translating a Rendezvous message, the adapter ignores unnamed fields.