IBM MQ JMS API
Java Message Service API for IBM MQ.
This event API exposes 7 operations across 4 channels, and defines 4 schemas. It is described by AsyncAPI 2.6.0, at version 9.3.
The API connects through 2 servers: {host}:{port} (ibmmq), {host}:{amqpPort} (amqp).
7 operations
4 channels
4 schemas
Metadata
The identity and technical contract details declared by the specification.
Channels & Operations 7
Across 4 channels, the API surfaces 7 operations. Each is listed below with its action, channel, parameters, and response codes.
Channels 7
SUB
queue/{queueName}
Receive a message from a queue
PUB
queue/{queueName}
Send a message to a queue
SUB
topic/{topicString}
Subscribe to a topic
PUB
topic/{topicString}
Publish a message to a topic
SUB
deadLetterQueue
Receive undeliverable messages
SUB
requestReply/{requestQueue}
Receive a reply message
PUB
requestReply/{requestQueue}
Send a request message
Messages & Schemas 4
The contract defines 4 schemas that model the data carried by its messages. Each schema is shown below with its type and property counts.
MQMessage
message
A message transmitted through IBM MQ
DeadLetterMessage
message
An undeliverable message routed to the dead-letter queue
RequestMessage
message
A request message in a request/reply pattern
ReplyMessage
message
A reply message correlated to a request
Specification
The full machine-readable AsyncAPI contract behind this narrative.
Source
#Java#Jms#Messaging