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.

Tip: This topic does not apply when an application uses only dynamic durables.

Dynamic durables are always simpler to use. Static durables continue to support existing projects.

Background

Each application process supplies either a unique durable name or a unique subscriber name in each create subscriber call. To understand this distinction, see “Durable Subscribers” in TIBCO FTL Development.

Durable Considerations

If the application supplies only durable names, the administrator need not define a mapping, because the mapping applies only to subscriber names.

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.

If you change the name of a currently deployed durable, you will receive a message like: Changing the name of a currently deployed durable will cause its stored message data to be deleted when the new realm configuration is deployed.

Subscriber Name Mapping

Note: Subscriber name mapping is an advanced topic.

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 Persistence Modifications: Store and Durable.