Transferring text files between Connect:Direct and MFT

Text transfer involves converting the code page of a file from one code page to another. Text file transfer also involves converting CRLF (carriage return line feed) characters between systems. This topic summarizes text file transfer behavior in transfers between a Managed File Transfer Agent and a Connect:Direct® node.

For information about the behavior of text transfers in Managed File Transfer, see Transferring text files with MFT.

• Ensure that the network map of the Connect:Direct bridge node and any Connect:Direct nodes that are used as a transfer destination include the correct platform description.
  • If your Connect:Direct bridge node is on a Windows system, ensure that for each remote node in your network map you select the correct value from the Operating System list.
    • If the remote node is on a Windows system, select Windows.
    • If the remote node is on a UNIX or Linux system, select UNIX.
    • If the remote node is on a z/OS® system, select OS/390.
    Transfers to remote nodes on other operating systems are not supported by the Connect:Direct bridge.
  • Ensure that for each remote node you transfer a file to or from, you specify the operating system type of the remote Connect:Direct node in the ConnectDirectNodeProperties.xml file in the Connect:Direct bridge agent configuration directory. For more information, see Configure the ConnectDirectNodeProperties.xml file to include information about the remote Connect:Direct nodes and Connect:Direct node properties file format.
  Connect:Direct uses the network map information to determine which line ending to use.
• If the destination of a transfer is a Managed File Transfer Agent, this agent performs the line ending conversion.
• If the destination of a transfer is a Connect:Direct node, the Connect:Direct bridge agent performs the line ending conversion.