Connectors

Messaging & Event Streaming

IBM MQ

Enterprise message queuing: put, get, and browse messages, check queue depth, and list queues
Signs in with
Connection details
Runs on
Cloud or On-Prem Worker
Operations
6
Ready-made triggers
0

Connect IBM MQ

  1. In Neblex open Connect › Connections and click New Connection.
  2. Search for IBM MQ and give the connection a clear name.
  3. Fill in the fields. Secret values are encrypted and never shown again.
  4. Click Test, then Create Connection.
If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.
FieldWhat to enter
Queue managerOptionalThe queue manager name. Leave empty to accept the queue manager the channel leads to.
HostRequired
PortOptionalExample: 1414
ChannelRequiredThe server-connection channel this connection uses.Example: DEV.APP.SVRCONN
UserOptional
PasswordOptionalSecret
TLS cipherOptionalThe cipher the channel requires. Leave empty for a channel without TLS.Example: ANY_TLS13_OR_HIGHER
Key repositoryOptionalThe key repository on the host that runs the step, without its file extension (for example /var/mqm/ssl/key).
Certificate labelOptionalThe label of the client certificate in the key repository, when the channel requires one.
Server certificate nameOptionalThe distinguished name the queue manager's certificate must match, for example CN=QM1,O=Example.

Use it in a flow

  1. Open a flow, open the node library and search for IBM MQ.
  2. Drag it onto the canvas and choose an Operation and your connection.
  3. Map the operation's fields from earlier steps, or click Map with Matt.
  4. Use Test this step to see what it returns, then save.

To start a flow from IBM MQ without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if IBM MQ can send webhooks, a Webhook trigger receives them at its own URL.

Operations

6 operations in 3 groups. Each one is a step you can add to a flow.

Connection1
Test the connectionpingConnect to the queue manager through the channel and disconnect.
Message3
Browse messagesbrowseRead messages without removing them from the queue.
Get messagesgetRemove messages from the queue with their body, properties and descriptor fields.
Put messagesputPut one message per record on the queue, with its properties and descriptor fields.
Queue2
Get queue depthinquireQueueReturn how many messages the queue holds, its limits and how many applications have it open.
List queueslistQueuesList the queue manager's queues, filtered by name and type.