TIBCO FTL®
|
![]() ![]() | Asynchronous advisory messages carry information about the operation of FTL. Programs can receive this information through subscribers on the advisory endpoint |
![]() ![]() | Content matchers filter messages based on their content |
![]() ![]() | Exceptions capture error information during FTL calls |
![]() ![]() | Field references enable efficiency gains when accessing message fields |
![]() ![]() | Start and stop FTL Log levels |
![]() ![]() | The group facility can coordinate fault-tolerant operation, or distribute operating roles among application process instances |
![]() ![]() | Inbox objects address inbox subscribers |
![]() ![]() | This file defines constants related to LogStream data messages, their field names, and their field values |
![]() ![]() | Programs can use maps to store key/value pairs in a persistence store |
![]() ![]() | Map iterators iterate over the key/value pairs in a map |
![]() ![]() | This file defines constants related to monitoring data messages, their field names, and their field values |
![]() ![]() | Message objects contain fields with values |
![]() ![]() | Properties objects represent a set of configuration properties (name/value pairs) |
![]() ![]() | Publisher objects send messages |
![]() ![]() | Event queue objects hold message and timer events until callbacks can process them |
![]() ![]() | Realm objects contain definitions of message formats, endpoints and transport maps |
![]() ![]() | Subscribers express interest to receive inbound messages |
![]() ![]() | Cooperating application programs can use locks to implement exclusive access to a map within a persistence store |
![]() ![]() | FTL datatype definitions |