Transfer Using Nodes

Using pre-defined node definitions for remote systems, you do not have to constantly provide information to TIBCO MFT Platform Server when conducting transfers with remote systems. We suggest using node and profile definitions to predefine the connectivity and authentication parameters. This makes the transfer more secure and less prone to errors.

The settings for each remote system are stored in a clear text file named cfnode.cfg located in the $CFROOT/config or the shared HA configuration directory. Once a node definition is created, you can specify the name of the node to perform a transfer as opposed to using numerous transfer parameters to get the same results for a file transfer. TIBCO MFT Platform Server checks the definition for the specified node to obtain the required parameters to perform a transfer.

Node definitions define default parameters required by TIBCO MFT Platform Server to interact with a remote system (node). This information includes:

• Node name
• System type (for information purposes only)
• IP address or host name
• Port number
• Optional: security compliance level (used for HIPAA and FIPS mode transfers)
• Optional: netmask for incoming remote IP address
• Optional: netmask6 for incoming remote IPv6 address
• Optional: use of TLS/SSL and Tunnel mode for secure communications
• Optional: default compression type
• Optional: default encryption type
• Optional: default local translation file
• Optional: default remote translation file
• Optional: whether responder profiles are used
• Optional: whether verified users are accepted
• Optional: text description for the node
• Optional: CRC checking
• Optional: Supported Command Center functions