MQ File Mover Overview
The MQ File Mover v3.2.1 (MQFM) application is a software package that is designed to move files using WebSphere MQ (aka MQSeries). MQFM processes “Action” commands which are controlled through an MQFM Workflow XML file. The user combines a series of Action commands to create the MQFM Workflow XML file.
- The MQFM Workflow XML Action framework currently contains 11 Action commands:
- Send - Sends 1 or more files as individual messages via MQ
- Watch - Monitors for a particular file or monitor a directory for files to appear and then send the file (can be run as a daemon or as a Windows service)
- Receive - Receives an incoming message and write it to a file (can be run as a daemon or as a Windows service)
- PutQuit - Puts a 'Quit' message on a queue
- Execute - Runs an external program / application
- Append - Appends a file to another file
- Copy - Copies 1 or more files from a directory to another directory
- Move - Moves 1 or more files from a directory to another directory
- Delete - Deletes 1 or more files in a directory
- Rename - Renames a file
- Zip - Compresses a file, many files or a directory of files into a Zip archive
- MQFM can connect to a queue manager in 3 possible ways:
- Locally in binding mode
- Remotely using a Client Channel Definition Table (CCDT)
- Remotely using a MQ XML file
- MQFM supports both forms of MQ security:
- SSL for connecting to remote queue managers
- 3rd party security exit for connecting to remote queue managers
MQ File Mover is licensed under Apache License 2. It is free to use but support is not included. A support license may be purchased.
| Context Diagram (Logical View) | Description |
|
The Send Action will read the contents of a file and place it on a queue as a message. The Send Action will include Path and Filename information in the message's MQMD. This information details the file's location on the remote system. The Send Action can handle a file up to 100 MB* in size as a message to a queue (*WMQ message size limitation). Send Action supports both string and binary message formats. The Send Action can also specify an Execute that will be executed on the remote server. The Send Action supports a wildcard (i.e. *.txt) in the filename that will send multiple files as separate messages in a single execution. The Send Action can compress the message data to accommodate file sizes larger than 100MB. Once the data is compressed, there is no conversion between different platforms (i.e. ASCII to EBCDIC). The Send Action can launch a local external program after putting the message on the queue. It can also delete or archive the file after the message has been put on the queue. |
|
The Receive Action will retrieve a message from a queue and write it to a file. The Receive Action can be run in 1 of 4 modes: one-time, triggered, as a daemon or as a Windows service. The Receive Action retrieves the message and writes it to a file under a Unit of Work (UOW). If the incoming message is not a MQFM message and the user did not specify the Default File name, the Receive Action will use the following format for the file name: MQFM_####.txt (where #### is the message count number). If the Receive Action detects a compressed incoming message, it will decompress the message before writing it to the output file. If the incoming message has a specified Execute, the Receive Action will launch an external program after retrieving the message from the queue. The user can assign a default Execute to the Receive Action, so that an external program will be launched when a message is retrieved. If the Receive Action has a problem with a message (invalid filename or invalid directory), the message will be backed out and the Receive Action will abnormally terminate. In order to avoid termination when a problem message is encountered, the user needs to specify a backout queue name (BackOutQName). As a result, the Receive Action will move the problem message to the backout queue and process the next message. |
|
The Watch Action will monitor for a particular file or monitor a directory for a file(s) to appear. The Watch Action can be run in 1 of 3 modes: triggered, as a daemon or as a Windows service The Watch Action will read the contents of a file and place it on a queue as a message. The Watch Action will include Path and Filename information in the message's MQMD. This information details the file's location on the remote system. The Watch Action can handle a file up to 100 MB* in size as a message to a queue (*WMQ message size limitation). Watch Action supports both string and binary message formats. The Watch Action can also specify an Execute that will be executed on the remote server. The Watch Action supports a wildcard (i.e. *.txt) in the filename that will send multiple files as separate messages in a single execution. The Watch Action can compress the message data to accommodate file sizes larger than 100MB. Once the data is compressed, there is no conversion between different platforms (i.e. ASCII to EBCDIC). The Watch Action can launch a local external program after putting the message on the queue. It can also delete or archive the file after the message has been put on the queue. |
- Prerequisite:
- WebSphere MQ v5.3 or higher
- Java Runtime Environment (JRE) 1.5 or higher
Optional Support Subscription for MQ File Mover
| Product | Price (USD) * | Ordering |
| MQ File Mover (Single Support Subscription license per year) | $15.00 | Order Now |
* Volume discounts available for as low as $12.00 USD per license per year.
** Each support subscription license is licensed on a per queue manager basis per year.
- Each support subscription license provides for:
- Product support and updates
- Free email support
- Free forum support
| Enterprise Support Subscription License for MQ File Mover: |
| The Yearly Enterprise Support Subscription License for MQ File Mover sells for $999.00 USD per year. The company is provided with support for an unlimited number end-users and/or applications using MQ File Mover at an unlimited number of locations. |