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
Workspace App Connect
Created by Guest
Created on Apr 23, 2012

We need a Topic Input Node in MQ Broker

Today MQ only seems to have solid support for Message Queues as the source for MQ Broker messages. We here at Blue Cross have a need for the ability to subscribe a message broker flow to a topic. It would be nice to have a Topic Input Node for that.

Idea priority High
RFE ID 21789
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Sep 25, 2020

    RFE Review. Although we have not yet managed to prioritize the implementation of this feature we continue to monitor its popularity. Status of the RFE is maintained as Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Jul 2, 2012

    Thanks for raising this requirement. We're sold on the utility of an TopicInput node, and we've spent some time investigating the technical engineering required. We'll look to schedule this work in a follow-on release or fixpack.

  • Guest
    May 13, 2012

    WMBv7 doesn't require an RFH2 for the Publication node; just the details in the Properties tree.

    I agree a Subscription node would be more intuitive & flexible than reading durable subscriptions with an MQInput node.

  • Guest
    Apr 25, 2012

    and this should be complemented by an Publisher Node that does not require the developer to create a RFH2 header manually.
    I think the best delivery would be an update to the existing MQ Nodes to include the 'new' MQV7 capabilities.