CFT is used for machine to machine file transfer with remote control for resuming interrupted transfers. CFT can also trigger remote processes, rename files according to a specific protocol, apply security constraints and implement the encoding conversion.
Use
Each site wishing to exchange a file is called a partner, regardless of the platform. Any partner wishing to send or receive data from another partner must be declared in “the partners file” or “CFT directory”. To share files, CFT must be installed on each platform. A platform that wants to send a file to a remote partner sends a request over the network by specifying the remote platform through its partner name. When the remote partner receives the request, it verifies that it is the correct destination and creates a record in its local catalogue that lists all requests. When it’s the request’s turn to be processed, the partner establishes a remote connection protocol with the push partner and announces it is ready to receive. The sending partner sends the file content that the receiving partner mirrors to a local directory. The sending partner doesn’t decide where the file is written on the receiving partner. He can not force the receiving partner to receive data. CFT indicates the status of each transfer at all times: pending, in progress, aborted or completed successfully. CFT is a licensed product. It is used with a software key that limits the use of CFT to a type of machine and a maximum number of simultaneous transfers. In the case of a UNIX Sun Solaris box, the CFT should be installed on both the sender and the receiver machines. There are two main config files for XFB namely locpart.smp and chkusr.txt. locpart.smp stores the destination server's IP address, protocol intended, port to be used and other such information. TCP and FTP are the basic protocols used here. The file chkusr.txt contains information specific to authorization and proxy. If a user is sending files to a receiver, the latter should have an A entry in its chkusr.txt file to authorize the user to send files. It should also contain the landing directory to which the files should be written in the receiving system. The sending machine also has an agent file named .perm, where the file name to be sent is configured and which contains the node name.
