简体   繁体   English

IBM MQ消息历史记录

[英]IBM MQ message history

Is it possible to keep a history of messages (with message content would be perfect) that have already been retrieved and are no longer on a queue? 是否可以保留已被检索且不再在队列中的消息历史(消息内容将是完美的)?

In the application I can see when the sender attempts to put the message in the queue and when the receiver attempts to pick the messages up, but I'd like to see when the message really arrived into the queue and when the messages were really received. 在应用程序中,我可以看到发送方何时尝试将消息放入队列中,以及接收方何时尝试提取消息,但是我想查看消息何时真正到达队列以及何时真正收到消息。 。

Does MQ Explorer have this function? MQ Explorer是否具有此功能? How would I use it? 我将如何使用它?

What you are looking for is a message tracking/auditing software for IBM MQ. 您正在寻找的是用于IBM MQ的消息跟踪/审计软件。 You can find a list of what is available here . 您可以在此处找到可用列表。

It is possible to use an API exit to make copies of messages in a queue or to audit both PUT and GET operations. 可以使用API​​出口在队列中复制消息或审核PUT和GET操作。

It is also possible to put messages to a topic, then create as many administrative subscriptions to destination queues as required. 也可以将消息放入主题,然后根据需要创建对目标队列的尽可能多的管理预订。 Something can then GET and log messages from one of those destination queues. 然后,某人可以从这些目标队列之一中GET并记录消息。 The problem with this is that MQ changes the message ID between publication and consumption whereas in a queue it remains static. 问题在于MQ会在发布和使用之间更改消息ID,而在队列中它保持静态。

There is no native MQ function to capture messages. 没有本机MQ函数来捕获消息。 It's possible to use linear logs and later scrape the logs but these do not necessarily capture all messages due to optimization. 可以使用线性日志,以后再刮日志,但是由于优化,这些日志不一定捕获所有消息。 (A message PUT to a waiting getter outside of syncpoint for example.) However there is at least one commercial product to scrape linear transaction logs to audit message activity. (例如,将消息PUT发送到syncpoint之外的等待获取器。)但是,至少有一种商业产品可以刮擦线性事务日志来审核消息活动。

The philosophy of MQ in general is that it is the delivery mechanism and deals with envelope data to route and deliver but does not deal with payload data. 一般而言,MQ的哲学是它是一种传递机制,处理信封数据以路由和传递,但不处理有效载荷数据。 WAS, IIB and other broker/transformation engines are where IBM has put all of the functions that deal with message payloads. WAS,IIB和其他代理/转换引擎是IBM用来处理消息有效负载的所有功能的地方。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM