Message Format

In FTL every message has a format. A format is a set of field names and types that characterize the structure of a message.

Simple Use Case

In the simple use case, you can supply any non-null format name when you create a message. Subsequently, you can safely ignore that name. Nonetheless, it is good practice to adhere consistently to one of the following conventions for format names:
  • Use only one format name for all messages within a suite of communicating applications.
  • Use a small number of format names, and use the same format name for all messages with similar structure (that is, field names and types).

However, if you use the JMS BytesMessage type, consider using a built-in opaque format in FTL; see "Built-In Formats Reference" in TIBCO FTL Development.

Format Optimizations

Adhering to one of those conventions from the start ensures that, later, you can transition easily to a more complex use case, in which FTL uses formats to automatically optimize messages. These optimizations can result in smaller messages and faster lookup of fields. When the need for message optimizations becomes apparent, see the following topics:
  • "Formats" in TIBCO FTL Concepts
  • "Formats: Managed, Built-In, and Dynamic" in TIBCO FTL Development
  • "Formats Grid" in TIBCO FTL Administration
  • "Defining Formats" in TIBCO FTL Administration