Enabling Persistence

You can enable persistence for individual channels.

1. Define requirements.
   Consult the application developer and the FTL administrator, and together complete the forms:

   • TIBCO eFTL Application Coordination Form
   • TIBCO FTL Durable Coordination Form
2. Ensure that an FTL persistence store is configured.
3. Ensure that an FTL persistence server cluster is running.
4. Configure a persistence store for the channel, and select it in the eFTL clusters grid.
5. Configure the store's Publisher Mode to Store -> Send -> No Confirm.
   For best throughput performance, use this publisher mode to prevent the eFTL server from blocking when it publishes a message to the store.
6. Optional. Configure the channel's dynamic durable template.
   Set the Acknowledgment Mode of the template to Asynchronous.

   Note: Asynchronous acknowledgments prevent the eFTL server from blocking when it acknowledges inbound messages from the store. (This setting does not apply to last-value durables and templates.)
7. Optional. Configure a mapping from durable names to static durables for the channel.
   Note: Subscriber name mapping is an advanced topic.

   The static durable must already be defined in the store.
   For each of those static durables, set the Acknowledgment Mode to Asynchronous. (For details, see the preceding note.)