Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Created by Guest
Created on Sep 27, 2013

Increased granularity for MQ Event Message Delivery

I am looking for IBM to enhance the granularity of delivery options for MQ generated Event messages. While newer Event Message types such as Configuration Events get their own queue (SYSTEM.ADMIN.CONFIG.EVENT), legacy events share common queues. Authority, Inhibit and Start Stop Events all use the SYSTEM.ADMIN.QMGR.EVENT queue and there is no option to tune this. See the Use Case below on why one would want this capability.

One potential solution would be to create an Event queue for each Event type. To be backward compatible the new Event specifc queues for legacy Event types could be defined as Alias queues resolving to the classic local queues. Potentially new Alias Queue SYSTEM.ADMIN.AUTH.EVENT could resolve to local queue SYSTEM.ADMIN.QMGR.EVENT. The change would be transparent to existing users, but would give me the ability to change the Alias Queue SYSTEM.ADMIN.AUTH.EVENT however I see fit, to allow me to send Authority Events and only Authority Events where I want.

Another solution would be to convert Eventing in MQ to a pure Pub Sub implementation. With a strong topic tree structure covering all Event types a user could subscribe to very specific Event types or all Event types. And multiple users could have overlapping subscriptions, each one to the queue of their choice. Events lend themselves to a Pub Sub model where multiple users, a single user or no users might be interested in a particular event.

Idea priority Medium
RFE ID 39722
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Reply
    |
    Jul 4, 2015

    In particular, *all* event messages should be published. For backward compatibility, the existing queue names continue to be defined and durable subscriptions created to point to them. However, as a security feature, the ability to subscribe to event messages such that they cannot be intercepted by an attacker is extremely useful.

  • Guest
    Reply
    |
    Jan 3, 2014

    I agree with Neil. PubSub to a more granular topic tree structure.

  • Guest
    Reply
    |
    Oct 2, 2013

    We are considering implementing something that would address this requirement in a future version of MQ.

  • Guest
    Reply
    |
    Sep 27, 2013

    In my opinion, Pub/Sub is the way to go for implementation of this RFE. While it is possible to use QAlias with targtype(topic) to convert the current structure of queues to topics publications, the granularity doesn't change. Also, doing pub/sub this way breaks backward compatibility as applications cannot get the messages from the original SYSTEM.ADMIN.*.EVENT queue names.

    So, improved separation of different event types into a well defined topic tree would have many advantages to MQ monitoring and event management.

0 MERGED

filter MQ AMS SYSTEM.ADMIN.CONFIG.EVENT messages by Pub/Sub

Merged
We need to filter MQ AMS audit messages in SYSTEM.ADMIN.CONFIG.EVENT by publish/subscribe.We need to send the SYSTEM.ADMIN.CONFIG.EVENT messages after a change/remove/add of a MQ AMS Policy to our Audit-system.All other SYSTEM.ADMIN.CONFIG.EVENT m...
about 10 years ago in MQ, MQ Advanced & MQ Appliance 3 Future consideration