Node Definitions

Node definitions define default parameters required by the platform server to interact with a remote system (node). The following information is included:
  • Node name
  • System type
  • IP address or host name
  • Port number
  • (Optional) Security compliance level
  • (Optional) Netmask for remote IP address
  • (Optional) Netmask6 for remote IPv6 address
  • (Optional) Use of SSL 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) Supported Command Center functions
  • (Optional) Maximum initiator transfers

After a node definition is created, you can specify the name of the node to be used when executing a transfer. The platform server consults the definition for the specified node to obtain the parameters required to execute a transfer.

Node definitions are stored in a file named cfnode.cfg located in the MFT Platform Server directory. You must use the cfnode command to update the cfnode.cfg file. MFT Command Center can also be used to update the cfnode.cfg file. Before cfnode updates any information in cfnode.cfg, a backup of this file is created called cfnode.bak.

The following example shows a sample node definition created by using the cfnode command: 
[dataServerA]
   
SystemType	= Windows
Protocol	= tcpip
RemoteLocation	= HostName
HostName	= 111.222.33.55
Compression	= RLE
Encryption	= NO
RemoteCTFile	= rmttrans.txt
Description	= This is a sample windows node definition

[dataServerB]
SystemType	= Linux
Protocol	= tcpip
HostName	= 111.222.33.44
Server	        = 56565
SSL	        = Y
Compression	= No
Encryption	= No
SecurityPolicy	= None
ResponderProfil = N
Description	= Sample TCP node
CommandSupport	= PING
Winners	        = 2