Configuration of Durable Subscribers in an Application or Instance
When developing new applications that use static durables, application developers and administrators coordinate to determine either durable names or subscriber names. Administrators must configure the realm accordingly.
Dynamic durables are always simpler to use. Static durables continue to support existing projects.
Background
Similarly, if the application uses only dynamic durables, the administrator need not define a mapping, because the mapping applies only to static durables. See instead, Enabling Dynamic Durables.
Subscriber Name Mapping
If the application program supplies subscriber names, the administrator must define a mapping from each subscriber name to a durable name: that is, to a static durable defined within the store. Administrators configure this mapping in the endpoint details panel.
The subscriber name and the durable name may be either identical strings or different strings. For administrative simplicity, use identical strings if possible.
For consequences of modifying this mapping, see Store and Durable Modifications.
- Instance Matching for Subscriber Name Mapping
The FTL server's instance matching algorithm determines the mapping from subscriber names to durables. - Configuring a Default Durable
To configure the default durable on an endpoint, open the endpoint's detail panel, add a subscriber name mapping, and supply _default as the subscriber name.