Universal File Mover (UFM) manages the transfer of files. The user combines a series of Action commands to create the UFM Workflow XML file. These Action commands define which actions are to be taken, the order of the actions, and how errors are to be handled. UFM processes the Action commands as per the UFM Workflow XML file. UFM currently contains 40 Action commands. These action commands fall into five categories: WebSphere MQ Actions, Network Actions, File Actions, Control Actions, and Other Actions. UFM can transfer files in one of five ways, using WebSphere MQ, FTP, SFTP, SCP, or HTTP.
|Tags||WebSphere MQ MQSeries FTP SFTP SCP http|
|Operating Systems||AIX HP-UX IBM i (OS/400) Linux Mac OS X Solaris Windows|
Release Notes: This release fixes a null pointer exception when the Status element is not specified within the Global element. It adds a wait in MQReceive Action for the child thread to close the queue and disconnect from the queue manager when run as a daemon or Windows Service.
Release Notes: This release MQ reconnection logic to MQReceive Action and to the StatusQueue functionality. The onerrorfail attribute is now updated for each action in the UFM_Workflow.dtd file to allow the onerrorfail attribute from the Global element to be used.
Release Notes: This release fixes an issue with the Action's checkObject not setting the error text in the GlobalErrorText.
Release Notes: This release fixes an issue with the MQReceive action when the same file is received again but is smaller than the original.
Release Notes: This release adds a new ReEncode Action to change the character encoding of a file and fixes an issue with the MQReceive action using run="S" and sending an empty message to the backout queue.