Defining Formats

Administrators define the set of formats in a realm. Administrators also regulate the subset of formats available to each application.

1. Coordinate with developers.

   The first step is to consult with developers to determine the format requirements. To begin the discussion, the developer completes the TIBCO FTL Format Coordination Form. Then developer and administrator review the forms together, and modify them to reflect your agreement.

2. Define managed formats in the realm.

   Define the managed formats as specified in the final consensus revision of the coordination forms. Use the configuration interface to define the formats (see Formats Grid).

3. Preload formats.

   When you define the application, add managed formats to the Preload Formats column. When a suite of application programs must exchange messages, ensure that each application definition preloads the formats that the program sends and receives.

   The term preload implies that the application loads these formats when it connects to the realm server. Furthermore, the only managed formats that an application can use are its preload formats.

   The list of preload formats does not affect built-in formats nor dynamic formats. You need not include built-in formats in the list of preload formats, as built-in formats are always available to all applications.

4. Allow or disallow dynamic formats.

   When the message structure and content are highly variable, and applications cannot determine or limit that content in advance, dynamic formats might be appropriate.

   If developers and administrators agree that the application requires dynamic formats, and that this will not degrade the performance of other applications in the realm (for example, by consuming bandwidth) then administrators can permit dynamic formats. (See Message Formats Administration.)

Copyright © Cloud Software Group, Inc. All rights reserved.