Open topic with navigation

# FTL Server: Message Broker

Default values configure an FTL server to operate as a message broker.

That is, when you run one FTL server without supplying any configuration file, it automatically operates as a message broker. Moreover, when you run three FTL servers without supplying any configuration file, they automatically join together to operate as a message broker.

- Each FTL server provides a realm service and a persistence service.
- The persistence services arrange themselves in a default cluster.
- The default realm definition includes a set of default persistence stores.
- The realm defines a default application which defines several endpoints, offering a mix of store and durable types.
- Any application definition can define an endpoint that uses one of the default persistence stores. Additionally, for message broker operation, the endpoint should have no direct path transport (in the administrative GUI the absence of a direct-path transport is displayed as a "Server" transport). An application that uses an endpoint like this will automatically connect with the persistence services of the default message broker. For more information, see Configuring Persistence.
- Clients connecting to any of the FTL servers can send and receive messages through the message broker.

## Non-Default Message Broker

To use a non-default message broker, see:

- Persistence Services and Clusters

- Configuring Persistence

- Stores for Message Broker

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.