Skip to main content
The connector provides access to queues through the REST API.

​
Key Capabilities

  • Enterprise message queuing through IBM MQ REST API integration
  • Queue manager connectivity with TLS encryption support
  • Bidirectional message processing with configurable authentication
  • Automatic retry logic with configurable intervals and maximum attempts

​
Overview

connectors are configured with a specific queue to which messages are pushed or from which messages are retrieved. Files that arrive in the Transactions tab of the connector are pushed as a message to the queue, and messages pulled from the queue are written as files to the Transactions tab. Each connector instance can only be configured with a single queue.

​
Prerequisites

To establish a connection with , at a minimum users must have:
  • An server and a clear network path to that server from
  • A queue manager with at least one active queue
does not provide setup assistance or support for the creation or configuration of the server. For questions about the setup of an server, consult the Introduction to documentation.

​
Connector Configuration

This section contains all of the configurable connector properties.

​
Settings Tab

​
Configuration

Settings related to the core configuration of the connector.

​
TLS Settings

Settings related to transport security.

​
Client Authentication

Settings related to authenticating against the remote service.

​
Other Settings

Settings not included in the previous categories.

​
Advanced Tab

​
Message

​
Logging

​
Other Settings

​
Miscellaneous

​
Automation Tab

​
Automation Settings

Settings related to the automatic processing of files by the connector.

​
Performance

​
Alerts Tab

​
SLAs Tab

​
Establishing a Connection

The following settings are required to establish a connection:
  • Remote Host
  • Remote Port
  • Queue Manager
  • Queue
If client authentication is required, you must also set the following:
  • Username
  • Password
Use the Test Connection button to verify the connection to the server.

​
Sending Messages

Files that arrive in the Transactions tab for the connector are pushed to the configured queue as a message. Files can arrive in this folder either by being placed there directly, or from another connector earlier in the flow. You need to set up multiple connectors to push messages to multiple queues. You can use a connector like the Branch connector to route files to the appropriate connector.

​
Receiving Messages

You can configure the connector to automatically poll the remote queue for messages to download. Use the Receive Automation and Receive settings on the Automation tab. When enabled, the connector waits for the specified interval before attempting to retrieve messages from the queue and pushing them to the Output folder. If the connector is connected to other connectors in a flow, downloaded messages are automatically passed to the next connector. Otherwise, the messages remain in the Output folder.

​
Macros

​
Examples