Open topic with navigation

# Persistence Service Details Panel

The Persistence Service details panel presents the details of a persistence service definition. In edit mode, you can modify the definition.

From the left menu, select Clusters, select the three dots above a cluster's Server Name, then select View Details.

The title of the panel indicates both the cluster and service names: Cluster / Service.

For background information, see Persistence Services and Clusters.

For consequences of modifying this configuration, see Persistence Modifications: Store and Durable.

## Service Parameters

GUI Parameter | Description
--- | ---
Server Weight | Optional. This value must be an integer in the range [1,10]. Larger values indicate greater preference that the service becomes the leader. When absent, the default weight is 10.

## Transports

Each persistence service definition must configure a cluster transport and a client transport.

You can also configure an alternate client transport, and a disaster recovery transport, each of which enables optional functionality.

Supply the transport parameters as needed. The available parameters depend on the transport protocol. In general, only a subset of parameters for that transport protocol are available, as the FTL server automatically supplies values for the remainder.

For transport parameter details, see Transport Concepts, and Transport Details Panel.

For background information, see Persistence Service Transports.

GUI Parameters Grouping | Description
--- | ---
Client Transport | Client applications communicate with persistence services in the cluster using this transport. Persistence services inherit the client transport protocol from the service set. Select the transport Protocol in the Client Protocol column in the clusters grid. Set other parameters in this section: The Backlog Buffer Size of the persistence client transport limits the number of messages that can be delivered at once. (Messages may also be limited by the prefetch count parameter. See Durable Prefetch Count.) Receive Spin Limit is an advanced function. See Receive Spin Limit. See also Client Transport and Non-Blocking Send.
Cluster Transport | Persistence services with the cluster communicate with one another using this transport. Persistence services inherit the cluster transport protocol from the service set. Select the transport protocol in the Cluster Protocol column of the clusters grid. Set other parameters in this section.
Alternate Client Transport | Optional. When defined, clients on the associated hosts communicate with this persistence service using the alternate transport. All other clients use the regular client transport defined for the cluster. To define an alternate client transport for clients on specific host computers, supply a transport protocol and other transport parameters. Add hosts to the list of Associated Client Host Names. For background information, see Alternate Client Transport. See also Client Transport and Non-Blocking Send.
Disaster Recovery Transport | Optional. When two persistence services need to communicate across the WAN for disaster recovery replication, they establish a transport using this definition. Persistence services inherit the disaster recovery transport protocol from the cluster. Select the transport protocol in the DR Protocol column of the clusters grid. Set other parameters in this section. For background information, see Disaster Recovery.
Zone Transport | Optional. When two persistence services need to communicate across the WAN to forward wide-area stores, they establish a transport bus using parameter values in this definition. You may modify the default parameter values in this section.

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.