FTL Server and Services
Release 6.0 introduced a new FTL server component, which consolidates all of the separate executable components from earlier releases (such as the realm server, persistence server, and transport bridge). This topic defines the new terminology.
Terminology
- FTL Server
- An FTL server is the consolidated server executable or any process that executes it.
An FTL server can provide and manage one or more services. Management includes starting a service, and automatically restarting it when it is not running.
A set of server processes can coordinate to provide fault-tolerant services.
- Service
- Each service is a module that runs within an FTL server. Each service implements part of the functionality available in TIBCO FTL.
Examples of FTL services include the realm service, persistence service, transport bridge service, eFTL service, authentication service, and group service.
- Message Broker
- A message broker is an FTL server that provides server-based messaging using a message broker pattern.
- Core Server
- A
core server is an FTL server that you designate in the list of
core.servers.
A set of core servers forms a quorum.
A set of core servers can cooperate for fault tolerance, or a single core server can operate solo. The number of core servers must be odd.
A core server implicitly provides a group service.
- Auxiliary Server
- An
auxiliary server is an FTL server that you designate and configure for a specialized purpose, and do
not
specify in the list of
core.servers.
For example, an auxiliary server might provide an eFTL service to expand capacity, or a backup bridge service for fault tolerance. You can use auxiliary servers during migration procedures.