Administrative Concepts
A realm is a namespace that defines resources and configurations available to application programs. (Those resources include endpoints, transports, and formats.)
Administrators can use the following types of interfaces to define the realm:
| • | FTL Administrative GUI (Graphical User Interface) |
| • | REST API (either via a command line tool like curl, or the Swagger extension on the GUI: REST API Reference) |
| • | YAML file configuration options, which are read at FTL server startup |
| • | FTL server command-line options (typically within a script |
The TIBCO FTL base library caches the realm definition in a realm object and consults the local realm object for information about endpoints, transports, and message formats. Application programs connect to the realm service to read the relevant parts of the realm definition. If the realm definition changes, the realm service updates its application clients.
Realm definition parameters fall into the following categories:
| • | Realm Properties - General and common settings for the entire realm |
| • | Applications - Client programs that utilize publish, subscribe, monitoring, or other FTL client API features. |
| • | Transports - Note that transports are not visible to application developers, rather, they are strictly the responsibility of the administrator. From the developer’s perspective, these details are hidden behind endpoints. |
| • | Persistence - Configuration of stores, persistence clusters, and zones. |
| • | Bridges - A service that forwards messages among sets of transport buses. |
| • | Formats - Definitions of message formats |
Architects, administrators, and developers coordinate the detailed requirements of applications using coordination forms (see Coordination Forms).
When configuration changes are edited and stored, they then can be deployed, per a controlled deployment procedure.