Open topic with navigation

# Stores Grid

The Stores grid presents persistence store definitions and their details. In edit mode, you can add and delete store definitions, and modify existing store definitions.

For consequences of modifying a store definition, see Persistence Modifications: Store and Durable.

## Levels

- Store
- Durable
- Content Matcher

## Store Level

From the left menu, select Stores.

Column | JSON Attribute | Description
--- | --- | ---
Store | `name` | Required. Name of the store. Store names must be unique within a cluster. All names are limited to maximum length of 256 characters.
Scope |  | Required. Select either cluster or zone from the drop-down menu.
Cluster/Zone |  | Required. Assign the store to a persistence cluster or forwarding zone. The drop-down menu offers the available clusters or zones, depending on the value in the scope column.
Publisher Mode | `publisher_settings` | This parameter 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.
Replicated | `replicated` | When enabled, the cluster replicates the store across its persistence services. When disabled, the cluster does not replicate the store. Only one persistence service holds the store’s data.
Store Size Limit | `bytelimit` | The store may 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 is a special value, indicating no limit. The store may grow until it exhausts available memory of any one of its services. See Size Units Reference.
Last Modified |  | This timestamp indicates the date and time of the most recent change to this store definition.

## Durable Level

The durable level presents the definitions of static durables and dynamic durable templates in the store.

From the left menu, select Stores. Click the expand button by Durable Name to display the following information for the durable.

Column | JSON Attribute | Description
--- | --- | ---
Durable Name | `name` | Required. Name of the static durable or dynamic durable template. (The name of an individual dynamic durable comes from subscriber create call, and not from administrative configuration.) Names must be unique within each persistence store. All names are limited to maximum length of 256 characters.
Durable Type | `type` | Select the type of durable definition from the drop-down menu. You may define either a static durable or a dynamic durable template of the following types: Standard The durable retains a message stream for exactly one durable subscriber. Shared Many subscribers can share this durable, which distributes each message to only one of those subscribers. Last-Value The durable retains only the most recent message for each sub-stream. For background information, see Durable Behavior.
Acknowledgment | `ack_settings` | Select an acknowledgment mode from the drop-down menu. This parameter applies only to standard and shared durables. When a subscriber finishes processing a message, the client library sends an acknowledgment to the durable. This interaction can be either Synchronous or Asynchronous. For complete details, see Acknowledgment Mode.
Interest | `interest` | Message interest determines a stream of messages: Store All Messages The durable collects the full message stream. (This behavior is available only for standard durables and shared durables.) Store Matching Messages The durable collects a sub-stream determined by a content matcher. Store Messages with Key The durable collects the sub-stream of messages that contain a key field. You must specify the Key Field Name parameter. This behavior is available only for last-value durables. Select a type of message interest from the drop-down menu.
Key Field | `key_field_name` | Required. Applies only to static last-value durables. Supply the name of the key field. The durable stores only the most recent message for each distinct value of that key field. Developers and administrators coordinate to determine the appropriate behavior (see TIBCO FTL Durable Coordination Form). When you set the durable type to static last-value, the GUI automatically sets this parameter value to the placeholder value `default-key`. You must explicitly change this placeholder to the actual key field name.

## Content Matcher Level

This level applies only to static durables, and only when the Interest column is Store Matching Messages.

Developers and administrators coordinate to determine the appropriate behavior (see TIBCO FTL Durable Coordination Form).

Administrators configure a content matcher at this level to implement that behavior. A content matcher can match one or more fields.

For background information, see Message Interest.

Column | Description
--- | ---
Match Field | Enter a field name. For static last-value durables, one matcher clause must test the existence of the key field.
Match Type | Select a data type or a field-existence predicate from the drop-down menu.
Match Value | Enter a value to match.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.