Open topic with navigation

# Bridges among Dynamic TCP Meshes

You can use transport bridges to link the disjoint mesh topologies that a dynamic TCP mesh transport establishes in satellite locations.

A dynamic TCP mesh definition establishes a bus with full mesh topology among all its endpoints, as long as their applications connect to a localized cluster of FTL servers. When your enterprise uses satellite FTL servers, a single dynamic TCP transport definition establishes a separate mesh in each localized satellite cluster. Each mesh includes all the applications that are clients of any FTL server in the local cluster (and that use that dynamic TCP transport). You can use transport bridges to link those otherwise disjoint meshes.

You can define a transport bridge to interconnect dynamic TCP meshes similarly to other bridges.

For more background information, see Dynamic TCP Transport.

## Principles of Operation

The following diagram depicts the general use case of a dynamic TCP bridge.

Figure 52: Bridging for Dynamic TCP Meshes

This enterprise includes three locations: the primary location (left) and two satellite locations (right). Each location has an affiliated FTL server cluster. At least one FTL server in each cluster provides a bridge service. The realm defines a single dynamic TCP transport definition, which establishes a mesh at each location. The meshes are disjoint from one another.

To bridge the meshes requires a bridge service at each location (orange), and a bridge definition that links the locations using a pair of static TCP listen and connect definitions. Include the listen end at the primary location, and the connect end at the satellite locations. The resulting pair connections link each of the satellite bridge services to the primary bridge service (solid lines). (Ensure that the static TCP port is open on the bridge service host computers.)

To extend to a fault-tolerant scenario, add redundant bridge services to FTL servers at each location (light orange). Configure these additional bridge services in the FTL server configuration files. Specify the identical bridge names. You can configure any number of redundant bridge services at each location (one per FTL server) even though the diagram shows only one redundant service per location.

Figure 53: Example

To implement the preceding example (that is, the simple case, without fault tolerance), define two bridge definitions in the realm, Primary Location and Satellite Location:

- The Primary Location, Bridge Service P, has two transport sets.
  - Set A contains only the Dynamic TCP Mesh Transport Definition.
  - Set B contains only the listen end of a static TCP pair.
- The Satellite Location, Bridge Service S, has two transport sets.
  - Transport Set A contains only the Dynamic TCP Mesh Transport Definition.
  - Transport Set B contains only the connect end of the static TCP pair.

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.