Open topic with navigation

# Auto Transport

An Auto transport bus, like a DTCP transport, establishes a set of TCP connections dynamically, decoupling the transport definitions from specific hosts and ports. However, with an Auto transport, in the simplest configuration, you don't need to specify listen or connect ports; a transport name is all that is required. An Auto transport can only be server-based and is typically used for persistence service transports, eFTL service transports, and group server transports. One main difference between DTCP transport and Auto transport is that DTCP transports require additional ports to be open if running behind a load balancer or a firewall, whereas Auto transports redirect all communication via the FTL server port.

## Scope of an Auto Transport

Auto transports may only be used to communicate with FTL server components. Auto transports cannot be configured on a client's endpoint. For example, clients never participate in an auto transport bus together (no "peer-to-peer"). Any communication occurs indirectly via FTL server components, for example, the persistence service ("server-based" only).

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.