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; i.e., clients never participate in an auto transport bus together (no "peer-to-peer"). Any communication occurs indirectly via FTL server components, e.g. the persistence service ("server-based" only).