The initial configuration of a new FTL channel automatically includes a dynamic TCP transport for the channel's application-facing endpoint. You can extend that transport on the FTL side in either of these two ways.
You can connect an FTL channel to applications on the FTL side in either of two ways:
Option
Description
Preferred
Share the dynamic TCP transport that implements the channel’s application-facing endpoint, so that it also implements the endpoint of the FTL application:
In the eFTL cluster grid, locate the channel’s application-facing endpoint in the Transport Name column, and note its name.
Each automatically generated name concatenates the prefix
eftl_channel_app_facing_transport_, the cluster name, and the channel name.
In the applications grid, locate the FTL application definition or application instance definition. Then locate the endpoint and select the transport you noted from the drop-down menu.
Alternative
Add a transport from the FTL application to the channel’s application-facing endpoint:
In the applications grid, locate the FTL application definition or application instance definition. Then locate the endpoint and note its transport name.
In the eFTL cluster grid, locate the channel, and select
Add Transport from the drop-down menu.
In the Transport Name column of the new row, select the transport you noted from the drop-down menu.
Important: Avoid crosstalk by ensuring that the FTL application does not share transports with more than one channel, nor with FTL applications on other channels. For more information, see
Cluster-Facing and Application-Facing Endpoints.
