Open topic with navigation

# Endpoints

An endpoint is an abstraction that represents a set of publishers and subscribers in communicating programs.

## Programming

Within an application program, an endpoint begins as a name. Program code uses the endpoint name to create endpoint instances, that is, publisher and subscriber objects. Then programs use the publishers to send messages, and the subscribers to receive messages.

Each subscriber object and each call to a publisher send method introduces an ability requirement (see Abilities). Application architects and developers record these requirements in endpoint coordination forms. See the "Endpoint Coordination Form" in the FTL Product Guides list.

Tip: For many applications or communicating application suites, a single endpoint name suffices.

## Configuration

Administrators configure transport connectors to satisfy those ability requirements. Connectors bind transports to endpoints. Those transports implement the endpoints, transferring message data from publishers to subscribers.

Administrators can also view an endpoint as a complex entity, embracing four separate communication abilities. A transport connector can separately enable any subset of those four abilities.

Tip: The default application definition is a valid configuration for applications that use only one endpoint.

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.