Open topic with navigation

# Many Publishers to Many Subscribers

In many-to-many, many publishers send messages to many subscribers and, potentially, every subscriber can receives messages from each of the publishers.

This example expands on the previous example by adding another publisher. In the following diagram, every subscriber receives messages from each of the publishers. As shown earlier, programs on the same host use shared memory transports and programs on separate hosts use multicast transports.

Although an increased number of transports is required, the programmer’s responsibility is the same as in the previous example, which is to implement EP1 and EP2. The administrator deploys the additional publishing program on Host 2, but the transport configuration remains the same. TIBCO FTL uses the configuration of the shared memory transport (T1) to automatically arrange two shared memory transports: T1a on Host 1 and T1b on Host 2. Similarly, TIBCO FTL software reuses the configuration of the multicast transport (T2) and integrates the new publisher into the existing transport.

Figure 8: Adding Another Publisher

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.