Realm Properties Details Panel

The Realm Properties details panel presents the global values of realm properties. In edit mode, you can modify the property values.

Intervals

Several intervals affect the operation of the FTL server and its interaction with clients.

GUI Parameter Description
Client to FTL Server Heartbeat The interval at which a client application sends a heartbeat to the FTL server process when no data flow is present. Default 60.

Zero is a special value, instructing the clients not to send heartbeats.

Client to FTL Server 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 reconnection. default 180 seconds (2.5 times the heartbeat interval)
FTL Server to Client Heartbeat The FTL server sends heartbeats to its clients at this interval, in seconds. Default 60.

Zero is a special value, instructing the FTL server not to send heartbeats.

FTL Server to Client Timeout

The amount of time a FTL server will wait for a response to the heartbeat from the client. If no response is seen, the FTL server closes the existing connection. Default 3600 (1 hour)

When a client does not receive server heartbeats for this interval, it 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.
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.

See TIBCO FTL Monitoring.

Dynamic Message Formats

Message formats can affect network bandwidth usage.

GUI Parameter Description
Dynamic Message Formats Restrict the formats available to applications.

When enabled, the only available formats are preload formats and built-in formats. For complete information, see Message Formats Administration.

Secure Communications

The FTL server can enforce TLS security in its communications with clients.

If the FTL server does not use secure communications, a warning appears at the top of this section.

GUI Parameter Description
Warn about insecure transports between clients When enabled, defining any transports that use non-secure protocols triggers a validation warning.

(This validation warning can trigger even if the FTL server does not enforce TLS communications.)

Persistence

Persistence operations

GUI Parameter Description
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.
  • Unlimited The default behavior. Persistence operation calls retry the interaction indefinitely. Calls return only upon success.
  • None Persistence operation calls that cannot access the persistence service raise an exception.

Properties of individual publishers, subscribers, and map objects within application programs supersede this global setting.

Note: In Release 6.0.0 the default behavior changed to Unlimited. In earlier releases the default behavior was None.

Subscription Statistics

You can control whether clients and services collect fine-grained monitoring metrics about subscriptions and message substreams. Note that these metrics produce a large volume of monitoring data.

GUI Parameter Description
Collect Subscription Statistics When enabled, clients gather monitoring metrics about subscriptions and message substreams, and send them to the FTL server.

When disabled, clients do not gather these metrics.

Related concepts
Related reference