Manycom FTP Client Automation and Security
Example Use Cases
Manycom FTP Client Automation and Security is typically integrated to customer applications for sending and retrieving automatically orders, order confirmations, customs declarations, invoices, product information, image files to web sites, etc., and starting the related pre and post processes.
On the user interface screens, the configured solution users can create new and work with existing one-time and periodical transfer requests. Operators and administrators can follow and control the traffic.
The FTP partner system can be any system running FTP server. Support to CCSID-to-CCSID and customer specific EBCDIC-to-ASCII character code conversion, support to special conversions between the traditional OS/400 and i5/OS file formats and other file formats, as well as support to binary transfer allow exchanging files between any applications – be the partner system another iSeries, UNIX, Windows, Linux or IBM host.
In a typical customer environment, there are usually need for both one-time transfer requests and periodical transfer requests. Periodical transfer requests are started and executed automatically after the configured time intervals to send or retrieve files. Typical interval is 15 minutes, two hours or one day, but it can be as well one minute, one week or one month.
Error retry limit and interval is commonly used with both the one-time and periodical transfer requests for autonomously retrying the transfer (and the related processes), if the transfer job ends in error.
In a typical customer environment, there is a need to transfer specific files (i.e. create transfer requests with specific file path names), but there is also a need to execute ‘directory transfer’ operations, e.g. send all files starting with the given characters and locating in the given local directory to the desired remote system’s directory – and vice versa – there is need to retrieve all files starting with the given characters and locating in the given remote system and directory to the desired local directory.
The file to send can be the original file, but it is recommended - and this is the default - to let MCM FTP Client Automation (FTPCA) copy the original file to a work file. Depending on the needed conversions, FTPCA can then convert the file to the desired format by starting the configured local process before the transfer, and/or the OS/400 or i5/OS FTP client feature can perform the character code conversion during the transfer. Accordingly, when retrieving files, the local process can be called to copy and convert the retrieved files to the desired directories, rename the local files, remove the remote files after the successful transfer, etc.
It is also possible to create a transfer request, where specific or generic files are retrieved from a FTP server, are then processed, e.g. converted in the local system, and then a new transfer job is created for sending the files to another FTP server.
Because of the modular and flexible structure of the script language and the entire solution, the number of different use cases is countless.