websphere 消息代理与 MQ
Websphere Message Broker 和 Websphere MQ 有什么区别？在 weblogic 环境中是否有相同的等效术语？ 另外，严格来说，两者（WMB 与 WMQ）中哪一个是 JMS API 的实现？
What is the difference between Websphere Message Broker and Websphere MQ? Is there any equivalent terminology for the same in a weblogic environment?
Also, strictly speaking, which one of the two (WMB vs WMQ) is an implementation for JMS API?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
WebSphere MQ 是一个消息传递引擎，可确保某些消息/负载的交付。 MQ 提供了一个队列管理器：一个托管队列（用于保存消息）和通道的服务器应用程序。侦听器（允许队列管理器相互通信）。 MQ提供了实现JMS的API接口。它还具有许多 MQ 原生的 API。从 WebSphere MQ 版本 7.0.1 开始，它还提供了发布-订阅引擎。 WebSphere MQ 基本上允许您将消息放在一个位置并在其他地方获取该消息，同时消息丢失的可能性最小。
WebSphere Message Broker 是一个尝试提供任意传输到任意传输接口以及任意语言转换引擎的程序。在传输方面，它提供了 MQ、JMS（大多数提供商）、MQ-FTE、本地文件、SMTP、FTP/SFTP、HTTP/HTTPS、TCP/TCPSSL、JDBC 以及可能还有一些我忘记的其他入口钩子。一旦消息进入 MEssage Broker，您就可以使用 ESQL（Message Broker 原生的类 SQL 语言）、Java、PHP、XSTL 来操作该消息。它还包含消息路由、收集、聚合、排序等功能。Message Broker 基本上允许您从多种格式（物理和逻辑）移动数据并在将数据放在其他地方（可能以不同的格式）之前对其进行操作。
WebSphere MQ is a messaging engine that provides assured delivery of some message/payload. MQ provides a Queue Manager: a server application that hosts Queues (to hold messahes) and Channels & Listeners (to allow Queue Managers to communicate with each other). MQ provides an API interface that implements JMS. It also has a number of APIs native to MQ. As of WebSphere MQ version 7.0.1 it also provides a publish-subscribe engine. WebSphere MQ basically lets you put a message in one place and get that message somewhere else with the smallest chance of the message being lost.
WebSphere Message Broker is a program that attempts to provide an any-transport-to-any-transport interface, and an any-language transformation engine. In terms of transports, it provides MQ, JMS (most providers), MQ-FTE, local files, SMTP, FTP/SFTP, HTTP/HTTPS, TCP/TCPSSL, JDBC and probably some other entry hooks I have forgotten. Once the message is in MEssage Broker, you can manipulate that message using ESQL (SQL-like language native to Message Broker), Java, PHP, XSTL. It also contains functionality for message routing, collecting, aggregation, sequencing etc. Message Broker basically allows you to move data from a number of formats (both physical and logical) and manipulate that data before putting it somewhere else, possibly in a different format.
AFAIK 消息代理将消息从一种格式转换为另一种格式（例如 JMS 到 MQ），或者根据内容或主题将消息路由到另一个位置/代理/队列；其中 MQ 是队列，消息最终会存放在其所在的位置，直到被其他应用程序使用。
如果您希望在将消息放入队列之前对消息进行转换/处理，那么您过去（WMB6）必须在 MQ 之前放置 WMB，我认为现在情况并非如此，因为 MQ 本身可以完成一些 WMB现在的功能。
AFAIK message broker transforms messages from one format to another (e.g. JMS to MQ) or routes a message to another place/broker/queue depending on content or topic; where as MQ is the queue the message ends up on where it's held until it's consumed by some other app.
You used to (WMB6) have to have WMB in front of MQ if you wanted your messages trasnformed/processed before being put on a queue, I don't think this is so much the case now as MQ itself can do some of the WMB functionality now.