Destination Configuration

All configured destinations have a name, which possibly includes a wildcard. See Destination Name Syntax.

This section summarizes the remaining destination parameters. See FTL Server GUI: Configuration or FTL Server Web API for details on how to create or modify destinations.

For information on how destination properties are handled for overlapping destinations in the configuration, see Inheritance.

Persistence Store and Cluster

All configured destinations must specify a persistence store and persistence cluster.

A persistence store is a set of messages with a common configuration (relating to storage limits, routing of messages, delivery assurance, and so on).

A persistence store is managed by a persistence cluster. A persistence cluster is a set of persistence services, running in FTL servers, that cooperate to provide fault tolerance and storage of messages for all persistence stores associated with the persistence cluster. See Persistence: Stores and Durables for more information.

See FTL Server GUI: Configuration for information on specifying the persistence store and cluster.

Subscription Properties

There are a number of properties used when the persistence cluster creates a topic subscription, queue, or map. Note that, in the case of topic subscriptions, these properties apply to the subscription, not the topic as a whole. For example, if “bytelimit” is set, the bytelimit is applied to each subscription separately; there is no bytelimit for the topic as a whole.

See Destination Details Panel for the full set of subscription properties.

Access Control

When an application program performs an operation on a destination (for example, subscribe or publish), and you have enabled permissions in the FTL realm, FTL server will check that the application has permission to perform the requested operation on the specified destination. Specifically, FTL server will match the specified destination to a configured destination, then consult the access control list for the configured destination.

To define allowed operations on a destination, you may create an access control list for each configured destination. The access control list specifies which users or groups are allowed to perform certain actions.

By default, the access control list is empty, meaning nothing is allowed.

See Authorization and Configuring Permissions.