Websphere vs MQ message broker

Question

What is the difference between Websphere Message Broker and Websphere MQ? Is there equivalent terminology for the same in a web environment? Also, strictly speaking, which of the two (WMB vs WMQ) is an implementation of the JMS API?

Answer 1

AFAIK message broker converts messages from one format to another (for example, JMS in MQ) or sends a message to another place / broker / queue depending on the content or topic; where, since MQ is a queue, the message ends where it was stored until it is consumed by some other application. You used (WMB6) to have WMB in front of MQ, if you want your messages to be converted / processed before being queued, I don’t think this is the way MQ can do some of the WMB itself now .

Answer 2

WebSphere MQ is a messaging engine that provides guaranteed delivery of some message / payload. MQ provides a queue manager: a server application that hosts queues (for storing messages), as well as channels and listeners (to allow queue managers to interact with each other). MQ provides an API that implements JMS. It also has a number of APIs native to MQ. Starting with WebSphere MQ version 7.0.1, it also provides a publish-subscribe mechanism. WebSphere MQ allows you to place messages in one place and receive this message in another place with the least chance of message loss.

WebSphere Message Broker is a program that tries to provide an interface to any transport and any transport and a translation mechanism for any language. In terms of transport, it provides MQ, JMS (most providers), MQ-FTE, local files, SMTP, FTP / SFTP, HTTP / HTTPS, TCP / TCPSSL, JDBC, and possibly some other record interceptors that I forgot. After the message is in MEssage Broker, you can manipulate this message using ESQL (a language similar to SQL native to Message Broker), Java, PHP, XSTL. It also contains functions for message routing, collection, aggregation, sequence, etc. Message Broker basically allows you to move data from several formats (both physical and logical) and manipulate this data before placing it elsewhere, possibly in a different format.