Open topic with navigation

# Mesh from Pair Connections

You can explicitly assemble a mesh with four vertices. Configure the six pair connections (edges) using four transport definitions:

- T1 listens on port P1.
- T2 listens on port P2 and connects to port P1 on A1’s host computer.
- T3 listens on port P3 and connects to ports P1 on A1’s host computer, and to port P2 on A2’s host computer.
- T4 connects to ports P1 on A1’s host computer, and to port P2 on A2’s host computer, and to port P3 on A3’s host computer.

  Figure 32: Mesh Topology for Connection-Oriented Transport Protocols

Notice that all four processes necessarily use different transport definitions to join the bus. It cannot be otherwise, because connection-oriented transport definitions are fragmentary.

Also notice that the four transport definitions (T1 - T4) are each tied to specific host computers. In order to use them, the application process instances (A1 - A4) must run on those host computers, respectively. You can configure this constraint using application instance definitions that match the transport's host parameter.

Tip: It is easier to use a dynamic TCP mesh than to painstakingly assemble it from static TCP connections. The realm service automatically coordinates the host and port details for dynamic TCP transports.

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.