Open topic with navigation

# Message Merging

Many publishers and many program processes may publish on one endpoint and the messages are merged. Neither the publisher or the publisher program is identified to the subscriber.

## Direct and Indirect Paths Example

In the following diagram, messages from all publishers are merged and are made available to all subscribers.

- Direct path: Network D uses of direct path transports (gray arrows) that connect every publishing endpoint to every subscribing endpoint. Each direct path transport merges message streams. Many publishers and many program processes may publish on Endpoint30. Messages received by the subscribers do not include identifying information for the publisher or the publishing program.
- Indirect path: Store4 merges the message streams from Endpoint30 and Endpoint31. Store4 backs messages from all publishers and makes them available to all subscribers. Store4 is an intermediate hop, part of several parallel, indirect paths in Network D. When a message eventually arrives at a subscriber, the message does not include identification of the publisher or the publishing program.

Figure 6: Network of Endpoints and Direct Paths

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.