Announcing the New NFM
TPS^® Releases NFM 2.5

TPS^® Network File Manager is better than ever! Big companies and small use NFM for all their complex file distribution needs. Reviewed in IBM's System Magazine and endorsed by numerous companies, see how NFM can be the perfect fit for your company. Companies already using NFM can enjoy new features including support for:

Provide TPS^®/NFM with the ability to allow multiple TPS^®/NFM Servers to be viewed and worked with as a single “virtual” server. When utilizing a shared database, multiple servers now can be used to increase performance by distributing the connection work load.

  FTP-S Server/Client


TPS^®/NFM will support server side FTP-S to allow non-NFM FTP-S (and FTP) clients to connect to a TPS^®/NFM client node to submit or retrieve files and allow standard FTP-S commands. The TPS^®/NFM client will appear to FTP-S clients to be a normal FTP-S server.

TPS^®/NFM will support client side FTP-S to allow a TPS^®/NFM client node to communicate with a FTP-S server to allow standard FTP functionalities. The FTP-S Client will give the users the ability to incorporate FTP-S into TPS^®/NFM Plan functions. This will enable transparent file transfers to systems running FTP-S Servers.

TPS^®/NFM FTP-S Server/Client is based on FTP (RFC 959), Firewall-Friendly FTP (RFC 1579), FTP Security Extensions (RFC 2228), and Securing FTP with TLS (RFC 4217).


   Account Manager

TPS^®/NFM will allow for the creation of “account managers”. These are users who have the ability to change (add/update/delete) other user accounts but can be restricted from doing any other activity on the system. The System Administrator controls the settings of an “account manager”.

  RADIUS Authentication

TPS^®/NFM will support RADIUS for user authentication. As with LDAP and Active Directory, TPS^®/NFM will authenticate user ID/passwords for logging into TPS^®/NFM.

  Watchfiles

The TPS^®/NFM watch file feature combines a file discovery mechanism with automatic plan invocation to provide the ability to transfer files automatically when the files are placed in a predetermined location on the source node. The transfers rely on the conventional running of a plan, which allows the transfer process to be customized.

.