Primary FTL Request, Secondary Rendezvous Reply to an Inbox

An FTL program sends a request message. The adapter detects that it is a request message because it meets all of these criteria.

  • The format of the message matches the format of a configuration tag.
  • The of that tag specifies the name of an FTL field, called the reply field.
  • The realm defines the format such that the reply field has type TIB_FIELD_TYPE_INBOX.
  • That reply field is present in the message.
  • The of the tag specifies the name of an FTL format, called the reply format. The requestor expects a reply message in this reply format.
  • The realm must define the reply format.

To configure this case, ensure that the adapter configuration meets these six criteria.

The adapter arranges a mechanism through which a Rendezvous program can reply to the FTL request:

  1. The adapter gets the value of the reply field, namely, the FTL inbox where the requestor awaits a reply.
  2. The adapter maps that FTL inbox to a Rendezvous inbox within the adapter.
  3. In the Rendezvous translation of the request message, the adapter sets the reply subject to that Rendezvous inbox.
  4. Later, when a Rendezvous program sends a reply to that inbox, the adapter receives it, translates it to an FTL message using the reply format, and forwards it to the FTL inbox where the requestor awaits the reply.