Durable Subscribers

A durable subscriber is a subscriber object in an application process that maintains its identity even if the process exits and restarts. It can receive messages from a durable in a persistence store.

A durable is a data structure within a store. Within a store, each durable has a unique name.

When a program creates a subscriber object, it can link that subscriber to a durable in either of two ways:
Durable Name
The program supplies a durable name in the create subscriber call. This name is a request to link the subscriber with a specific durable. Supply the name as the value of the durable name property.

If a durable with that name already exists, the subscriber links to that durable.

Otherwise, the store dynamically creates a durable with that name, and the subscriber links to that new durable. (Pre-requisite: The administrator has enabled dynamic durables.)

Tip: Using durable names is simpler than using subscriber names, because you need not define a subscriber name mapping.
Subscriber Name
Note: Subscriber name mapping is an advanced topic.
Within an application instance, the administrator defines a mapping from subscriber names to durable names. The program supplies a subscriber name in the create subscriber call, and the mapping determines the durable for the subscriber. Supply the name as the value of the subscriber name (or name) property.

The durable must already exist: that is, the administrator must define it as a static durable.

Tip: For flexibility, design applications can obtain their durable names and subscriber names from an external source, such as a command line argument or configuration file. Do not hard-code these names into application programs..

Developers and administrators coordinate the details of durable subscribers (see TIBCO FTL Durable Coordination Form).

Related concepts
Related reference