Note: Used in conjunction with TransporterReceiver.
To transport features from one FME process to another: use the TransporterSender transformer in the source FME workspace to send features to a TransporterReceiver transformer in the receiving FME workspace.
This transformer accepts any feature.
This transformer has no output ports.
Specify how you want to transfer data. The transfer mode must be the same for both the TransporterSender and the TransporterReceiver.
- Stream: Feature data is transferred over the network connection as raw binary data.
- TCP/IP: All feature data will be transferred over the network connection.
- TCP/IP (Attribute): Only the value of a selected attribute is streamed.
- File: The feature data will be saved to disk and the location of the file will be sent over the TCP/IP connection.
The Initiation Sequence specifies which Transporter endpoint is responsible for establishing the Transport stream (ESTABLISH), and which is responsible for connecting (CONNECT).
Note: The workspace that establishes the transfer mode must be running before the connecting workspace. The transfer mode must be consistent if there are multiple transport streams between two workspaces.
This parameter is only needed by the workspace with the Initiation Sequence parameter set to CONNECT, and only when the workspaces are running on different machines.
One of the primary uses for this parameter will be local to a machine in order to partition large workspaces into smaller components that each have their own address space.
Specify either a port number or a service (for example, http, ftp, telnet, imap, gopher, pop3, www, and smtp are services that are typically associated with well-known port numbers).
The default value is 8586.
This parameter is only used when Transfer Mode is set to File. It specifies the base file name to use.
Each file that is created will have a -<integer> appended to the end of the name to keep all files unique.
Example: If the File Name is features.fft, the first file created is features-0.fft, the second file created is features-1.fft, and so on. The full path of the file will be passed to the receiver and the receiver must be able to access the file from the same path (drive letter included).
This parameter is only used when Transfer Mode is set to File. It specifies how many features to write to a file before sending the location of the file to the receiver.
This parameter specifies the name of the output attribute. It is required only when the Transfer Mode is set to TCP/IP (Attribute).
- One workspace is the designated "establisher" of the transport stream. If there are multiple transport streams between workspaces, one workspace must be the establisher of all the streams, and the other will connect to those transport streams. This is regardless of whether the individual transporters are sending or receiving data.
- The establishing workspace must be started before the workspace that is connecting. A transporter cannot successfully connect to a transport stream that is not already established.
- For each transport channel, there must be a different port that is used for each server machine.
- You can use an arbitrary number of transporters within a workspace.
- Supports IPv6.
Editing Transformer Parameters
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
FME Licensing Level
FME Professional edition and above
Search FME Knowledge Center
Search for samples and information about this transformer on the FME Knowledge Center.