Persistence Store Configuration
Creating a Persistence Store
To create a store on a cluster, enter Edit Mode, navigate to the cluster Stores Tab, and click the New Store button. Inside this dialog, all you need to do to create a new persistence store is provide a name. You can edit the replication mode for the store as well. When store replication is enabled, the cluster replicates the store across its persistence services; otherwise, the cluster does not replicate the store and only one persistence service holds the store data. To modify additional persistence store properties, toggle the Advanced Edit View. For more information, see Advanced Persistence Store Configuration.
Editing a Persistence Store
To edit a configured persistence store, click the three vertical dots in the store row in the Stores Tab and select Edit Store. To modify a Persistence Store properties other than those outlined in Creating a Persistence Store, toggle the Advanced Edit View. For more information, see Advanced Persistence Store Configuration.
Deleting a Persistence Store
To delete a configured Persistence Store, open the actions menu for that store row, and select Delete Store.
Advanced Persistence Store Configuration
Enable Advanced View in the create or edit Store Dialog to modify the following Advanced Persistence Store properties:
| Property | Description |
|---|---|
| Publisher Mode | Governs communication among publisher send calls, the store, and the endpoint’s regular transports to produce different qualities of service. For complete details, see Publisher Mode in TIBCO FTL® - Enterprise Edition Administration. |
| Store Size Limit |
The store can grow until it exhausts available memory or disk of any one of its persistence services. This parameter limits the volume of message data in the store. If publishing another message would exceed this limit, the store rejects that message. Zero indicates no limit. The store can grow until it exhaust available memory of any one of its services. See Size Units Reference in TIBCO FTL® - Enterprise Edition Administration. |
| Dynamic Durables Limit |
Optional. Limits persistence service memory growth by restricting the number of dynamic durables that the store can create. When a program attempts to create a dynamic durable in excess of this maximum, the create subscriber call throws an exception. Zero indicates no limit. When absent, the default value is 0. For more information, see Persistence Limits. |
| Maximum Message Limit |
Limits the number of messages that can be held by the store. When the limit is reached, the client receives an exception on Note: Even when messages are stored on disk, message metadata is still stored in memory. Use this setting to constrain memory use.
Zero is a special value indicating no limit. The store can grow until it exhausts available memory or disk of any one of its persistence services. |
| Maximum Message Size | Optional. Set the maximum allowed message size. If the application's message exceeds the configured limit, tibPublisher_ Send/tibPublisher_SendMessages calls get an exception (if the store publisher mode is confirm_send). See Maximum Message Size in TIBCO FTL® - Enterprise Edition Administration for more information. |
| Swap Byte Limit |
Optional. If message swapping is enabled, set a byte quantity threshold for the store above which messages are swapped to disk to keep store memory use limited. Valid values are The default is |