Open topic with navigation

# Concept Review

Review the concepts to solidify your understanding of TIBCO FTL software.

Messages are sent in message streams from publishers to subscribers. There are several publish-subscribe models:

- One Publisher to Many Subscribers (TIBCO FTL’s main paradigm)

- Many Publishers to Many Subscribers

- One-to-One Communication utilizing an inbox

- Request/Reply with Inbox Tokenutilizing an inbox

- Distinct Endpoints in One Program

Message streams travel from publishers to subscribers over a transport which is a shared communication medium. TIBCO FTL supports a variety of transport types to use based on messaging requirements and environment. See Transport Types.

A messaging broker is a intermediate persistence store (or store) which temporarily holds messages. An FTL server can act as a broker. FTL may operate with broker messaging or brokerless messaging.

A persistence store (also called a store) temporarily holds a message stream sent by a publisher and held for the subscriber. Each store collects and maintains exactly one message stream and can collect the stream from one or more publishers. The store can maintain that message stream for one or many subscribers. Administrators can configure stores within a persistence service.

A durable is the data structure within a store that maintains subscriber interest, forwards messages, and tracks delivery acknowledgments. There are different types of durables. See Persistence: Stores and Durables.

An endpoint is the connection point between a transport and the publisher, subscriber, or broker. An endpoint contains transport details and insulates programs, and their designers/users, from those details. This enables separation of responsibilities between developers and administrators. Many publishers and many program processes may publish on one publishing endpoint. One subscriber may consume from more than one publishing endpoint. A program can have more than one endpoint to tap into more than one transport message stream

Messages travel from publishers to subscribers over a transport which is a shared communication medium. TIBCO FTL supports a variety of Transport Types to use based on messaging requirements and environment. Each transport is a separate communication medium, insulated against crosstalk from other transports.

A content matcher is a pattern matching template for message fields and values. A subscriber can use a content matcher to narrow its interest to a subset of a message stream.

A format defines the set of fields that a message can contain, including field names and data types. The format is available to cooperating programs before they exchange messages. Messages only carry data, which reduces both the message size, transport bandwidth, and processing time.

Viewing an application as a collection of endpoints, an application instance definition configures endpoints for use by application processes in a specific context, for example, a process that runs on a specific host computer or supplies an application instance identifier.

A realm embraces all the administrative definitions and configurations that enable communication among a set of cooperating programs.

See for a review of your role and helpful forms to coordinate between programmers and administrators.

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.