Open topic with navigation

# Endpoint Details Panel

In the Endpoint field on the Applications Grid, click ... then click View Details. The Endpoint details panel presents the parameters that apply to an individual endpoint in an application or in an application instance. In edit mode, you can modify the parameter values.

The title of the panel indicates the location of the endpoint definition:

- Application / Endpoint
- Application / Instance / Endpoint

GUI Parameter | Description
--- | ---
Store | Optional. You can associate at most one persistence store with an application endpoint. Select the store from the dropdown menu. (Instance endpoints inherit the persistence store associated with the corresponding application endpoint.) For background information, see Persistence: Stores and Durables.
Dynamic Durable Template | Optional. You can associate at most one dynamic durable template with an application endpoint or an instance endpoint. Select the store from the dropdown menu. The menu offers the templates defined in the persistence store associated with the endpoint.
Inbox Template | The default inbox template is a standard durable template with prefetch and is configured for async acknowledgments.
Subscriber Name Mapping for Static Disables | Optional. Note: Subscriber name mapping is an advanced topic. You can map any number of subscriber names to static durable. Select static durables from the dropdown menu. The menu offers the static durables defined in the persistence store associated with the endpoint. Although dynamic durables are simpler to use, this mapping continues to support existing projects. Note: If you change the name of a static durable while client are connected and messages are pending, messages are lost and the client must reconnect to the renamed static durable. For background information, see Configuration of Durable Subscribers in an Application or Instance.
Endpoint Abilities | Receive, Send, Receive Inbox, Send Inbox Each row denotes a transport connector, and specifies the ability that the transport carries for the endpoint. You must enable at least one ability for each transport. (A new transport connector is automatically configured with all abilities disabled.) For details, see Abilities, and Implementation: Endpoints (Micro).

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.