IBM MQ
IBM MQ bridge and gateway adapter
SFTPPlus MFT connects to an IBM MQ queue manager and exchanges files through point-to-point queues. It can put a file into a queue as a message or get a message from a queue and make its content available as a file.
SFTPPlus presents queues in a familiar directory-like structure. A single IBM MQ location can work with multiple queues, including separate queues for sending and receiving data. The IBM MQ C Client is included with SFTPPlus, so there is no separate client library to install.
This makes SFTPPlus a practical IBM MQ protocol bridge and gateway adapter. It connects applications that work with files to systems that exchange messages, without requiring either side to change its native interface.
See the IBM MQ transfer documentation for configuration details and current platform support.
TLS and mutual TLS
SFTPPlus supports TLS for IBM MQ connections, including mutual TLS authentication. Trusted certificate authorities can be stored as vault items and used to validate the IBM MQ server. For mutual TLS, store the client certificate and private key in a private-certificate vault item, then select it in the IBM MQ location configuration.
Certificate and private key management is handled within SFTPPlus, so you do not need external keystore tools to configure or maintain IBM MQ TLS connections. This keeps the connection security settings alongside the rest of the SFTPPlus configuration.
Edge protocol gateway
SFTPPlus can run at the network edge or in a DMZ, where external trading partners and legacy applications connect using standard protocols such as SFTP, FTPS, FTP, or HTTPS. After a partner uploads a file, SFTPPlus processes it through an automated transfer and writes its content to an internal IBM MQ queue.
The reverse workflow is also supported. SFTPPlus can get a message from a queue and publish its content as a file over SFTP, FTPS, FTP, HTTPS, or another supported destination.
The IBM MQ queue manager remains on the internal network and does not need to be exposed to external partners. SFTPPlus handles the public file transfer interface, user accounts, certificates, transfer automation, and audit records.
File-to-message conversion
SFTPPlus can monitor a local directory or a remote location, download each matching file, and put its content into an IBM MQ queue for downstream processing. Sources can include SFTP and FTPS servers, web servers, cloud storage, SharePoint, Windows shares, and other supported locations.
For message-to-file workflows, SFTPPlus gets messages from an IBM MQ queue and stores them temporarily before delivering them to the configured destination. This provides back-pressure when the destination is unavailable and avoids taking more messages than the transfer can process.
Compared with IBM MQ MFT
SFTPPlus MFT and IBM MQ Managed File Transfer (MQ MFT) can both move file content through an IBM MQ environment, but they are designed for different deployment needs.
| SFTPPlus MFT | IBM MQ Managed File Transfer | |
|---|---|---|
| Primary role | A protocol gateway between IBM MQ queues and file-based systems | Managed transfers between agents in an IBM MQ infrastructure |
| External access | Built-in SFTP, FTPS, FTP, HTTPS, and web file transfer services | Protocol bridge agents can connect an MQ MFT topology to FTP, FTPS, and SFTP servers |
| Deployment | A standalone gateway connected to an IBM MQ queue manager | An agent, command, and coordination topology integrated with IBM MQ |
| Administration | Web-based management for protocols, accounts, certificates, schedules, and auditing | Administration through IBM MQ MFT and MQ tooling |
| Deployment effort | Install one SFTPPlus service, configure the IBM MQ connection, and publish only the required file transfer protocols | Plan and deploy agents, coordination components, queues, channels, and the MQ MFT topology |
| Operational effort | Manage transfers, credentials, certificates, schedules, and audit records from one web interface | Operate the agent network and coordinate administration across MQ MFT and IBM MQ tooling |
| Total cost of ownership | Typically lower for a focused gateway because it uses one service and can run with standard IBM MQ | Depends on the MQ MFT topology, agent count, infrastructure, licensing, and operational staff |
| Typical use | Converting files to messages at the edge of an IBM MQ environment | Coordinating managed agent-to-agent transfers across an established MQ estate |
When the requirement is a focused file gateway rather than a complete MQ MFT topology, SFTPPlus can be a simpler and more cost-effective option. It can connect to an existing IBM MQ deployment without requiring an organization to upgrade its wider IBM MQ estate to IBM MQ Advanced solely to provide external file transfer interfaces.
SFTPPlus is not intended to replace every MQ MFT workflow. IBM MQ MFT can be a better fit when an organization already operates its agent topology and needs managed transfers between those agents.
When to choose SFTPPlus MFT
- External file exchange: Allow third parties to transfer files using SFTP, FTPS, FTP, or HTTPS without exposing internal IBM MQ queue managers to the internet.
- Cost efficiency: Add a file gateway to an IBM MQ deployment without introducing a complete IBM MQ MFT topology.
- Simplified management: Use a lightweight, web-managed service for file transfer interfaces, certificate management, automated directory polling, and delivery to IBM MQ.
- Protocol consolidation: Manage IBM MQ alongside other file transfer and storage connections from the same SFTPPlus installation.
IBM MQ transfer considerations
SFTPPlus supports point-to-point queues for IBM MQ transfers. Topics and publish/subscribe scenarios are not currently supported.
Each file is transferred as a single IBM MQ message because IBM MQ messages do not support streaming. The maximum file size is therefore limited by the maximum message size configured on the queue manager, which is 4 MB by default.
SFTPPlus can work with queues that grant only PUT permission for sending or GET permission for receiving. It does not require BROWSE permission. Messages are transferred as binary data with persistence enabled, and IBM MQ connections can be protected using TLS or mutual TLS.
Discuss your IBM MQ file transfer requirements
The SFTPPlus team can help you design a gateway between external file transfer users, internal applications, and IBM MQ. Contact us to discuss your queue, protocol, security, and deployment requirements.