Realm Properties Details Panel

Client - FTL Server Intervals

GUI Parameter	Description
Heartbeat	The interval at which a client application sends a heartbeat to the FTL server process. Client heartbeats also carry monitoring data. The default is 60 seconds.
Timeout	The amount of time a client waits for a response to the heartbeat sent before closing the existing connection to the FTL Server and initiating a client reconnect. When a client does not receive server heartbeats for this interval, the client actively attempts to reconnect to a server. If the server is part of a fault tolerant cluster, the client can failover to another core server in the local cluster. The default is 180 seconds.

GUI Parameter

Description

Heartbeat

The interval at which a client application sends a heartbeat to the FTL server process. Client heartbeats also carry monitoring data.

The default is 60 seconds.

Timeout

The amount of time a client waits for a response to the heartbeat sent before closing the existing connection to the FTL Server and initiating a client reconnect.

When a client does not receive server heartbeats for this interval, the client actively attempts to reconnect to a server. If the server is part of a fault tolerant cluster, the client can failover to another core server in the local cluster.

The default is 180 seconds.

FTL Server - Client Intervals

GUI Parameter	Description
Heartbeat	The FTL server sends heartbeats to its clients at this interval, in seconds. The default is 60 seconds.
Timeout	The amount of time a FTL server waits for a heartbeat from the client application process. If no heartbeat is seen, the FTL server closes the existing connection. The default is 3600 seconds (1 hour) to allow FTL server to maintain connections with transient clients as needed.

GUI Parameter

Description

Heartbeat

The FTL server sends heartbeats to its clients at this interval, in seconds. The default is 60 seconds.

Timeout

The amount of time a FTL server waits for a heartbeat from the client application process. If no heartbeat is seen, the FTL server closes the existing connection.

The default is 3600 seconds (1 hour) to allow FTL server to maintain connections with transient clients as needed.

Statistics Settings

GUI Parameter	Description
Client sampling interval	Clients take samples of their operating metrics at this interval, in seconds. Zero is a special value, instructing all clients to disable the monitoring feature. Metrics are sent to FTL server as part of client heartbeats.

GUI Parameter

Description

Client sampling interval

Clients take samples of their operating metrics at this interval, in seconds. Zero is a special value, instructing all clients to disable the monitoring feature.

Metrics are sent to FTL server as part of client heartbeats.

Persistence Settings

GUI Parameter	Description
Unlimited persistence retry	Persistent publisher operations, subscriber operations, and map operations require access to the persistence service. When they cannot access the persistence service (usually because of network failure or quorum unavailability), they can automatically retry the interaction. By default the Unlimited persistence retry toggle switch is enabled so that clients retry persistence interactions indefinitely. To disable, click the Unlimited persistence retry toggle switch to disable retry for persistence operations. This value only affects newly created subscribers, publishers, or map objects. Applications may override the default persistence retry duration when creating any of these objects.
Default to non-inline persistence sends	When enabled, persistent publishers will send messages non-inline. This offers the potential for increased throughput at the cost of higher latency. It also changes the semantics of the send call, since the application may return from the send call before the message is stored. This value only affects newly created publishers. Application code may override the default send policy when creating a publisher. For more information, see Publishers.
Prevent local message delivery	When enabled, newly created subscriptions enable no-local message delivery by default. This means that messages published using a client connection are not delivered to subscribers on that same client connection. The client’s application code may override. For more information, see No-Local Message Delivery in Development Guide.

GUI Parameter

Description

Unlimited persistence retry

Persistent publisher operations, subscriber operations, and map operations require access to the persistence service.

When they cannot access the persistence service (usually because of network failure or quorum unavailability), they can automatically retry the interaction.

By default the Unlimited persistence retry toggle switch is enabled so that clients retry persistence interactions indefinitely. To disable, click the Unlimited persistence retry toggle switch to disable retry for persistence operations.

This value only affects newly created subscribers, publishers, or map objects. Applications may override the default persistence retry duration when creating any of these objects.

Default to non-inline persistence sends

When enabled, persistent publishers will send messages non-inline. This offers the potential for increased throughput at the cost of higher latency. It also changes the semantics of the send call, since the application may return from the send call before the message is stored.

This value only affects newly created publishers. Application code may override the default send policy when creating a publisher.

For more information, see Publishers.

Prevent local message delivery

When enabled, newly created subscriptions enable no-local message delivery by default. This means that messages published using a client connection are not delivered to subscribers on that same client connection.

The client’s application code may override.

For more information, see No-Local Message Delivery in Development Guide.

General Settings

GUI Parameter	Description
Enable user and role permissions	Disabled: When the checkbox is clear, permissions are not enabled for the FTL realm. If authorization is required for any eFTL channels, the legacy method might be used: Set Publish Group and Subscribe Group to the appropriate values for each eFTL channel on the channel details page. Select the Authentication checkbox on the eFTL clusters grid. See eFTL Clusters Grid. Enabled: When the checkbox is selected, permissions are enabled for the FTL realm. Access to persistence clusters, persistence stores, destinations, and eFTL channels can be controlled by assigning permissions on the Users and Roles grids. Ensure that all persistence transports are secure. Ensure that the Authentication checkbox is selected for eFTL clusters (if used). See eFTL Clusters Grid.
Allow dynamic message formats	When the Allow dynamic message formats checkboxis selected, applications might use any formats, including dynamic formats. When the Allow dynamic message formats checkbox is clear, it restricts the formats available to applications. The only available formats are preload formats and built-in formats. For complete information, see Message Formats Administration.
Default to no-inline peer-to-peer sends	When enabled, peer-to-peer publishers (publishers that do not use a persistence store) send messages non-inline by default. This offers the potential for increased throughput at the cost of higher latency. Applications may override this setting.

GUI Parameter

Description

Enable user and role permissions

Disabled: When the checkbox is clear, permissions are not enabled for the FTL realm. If authorization is required for any eFTL channels, the legacy method might be used:

Set Publish Group and Subscribe Group to the appropriate values for each eFTL channel on the channel details page.
Select the Authentication checkbox on the eFTL clusters grid. See eFTL Clusters Grid.

Enabled: When the checkbox is selected, permissions are enabled for the FTL realm. Access to persistence clusters, persistence stores, destinations, and eFTL channels can be controlled by assigning permissions on the Users and Roles grids.

Ensure that all persistence transports are secure.
Ensure that the Authentication checkbox is selected for eFTL clusters (if used). See eFTL Clusters Grid.

Allow dynamic message formats

When the Allow dynamic message formats checkboxis selected, applications might use any formats, including dynamic formats.

When the Allow dynamic message formats checkbox is clear, it restricts the formats available to applications. The only available formats are preload formats and built-in formats.

For complete information, see Message Formats Administration.

Default to no-inline peer-to-peer sends

When enabled, peer-to-peer publishers (publishers that do not use a persistence store) send messages non-inline by default. This offers the potential for increased throughput at the cost of higher latency.

Applications may override this setting.