Integration

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on Aug 7, 2020

MQ Support for Distributed Tracing

Existing Application Performance Management (APM) tools, and emerging W3C standards for Distributed Tracing require propagation of tracking meta data across application protocols.

For applications using HTTP as the communication protocol between application components, this meta data can be placed in HTTP headers to be accessed by downstream APM agents or tracers while not fundamentally impacting the application being monitored.

For applications that use messaging protocols for communication between application components, the propagation of tracking meta data is typically handled by adding the meta data in message properties.

For IBM MQ based applications, the insertion of unexpected message properties can cause the underlying application to fail. While is it possible to change the application to handle these additional properties, it is often not technically or financially feasible to do so.

Ideally there would be a mechanism to propagate distributed tracing meta data across IBM MQ messages without requiring application or MQ configuration changes.

Idea priority High
Use Case
If a Java application is instrumented with an APM agent or tracer, the agent will place transaction tracing meta data in JMS message properties. If the target queue for this application is IBM MQ, these message properties can be converted to RFH2 headers. If the consumer of these messages is a traditional z/OS application performing an MQGET, the application is typically not expecting the presence of RFH2 headers after the MQMD. This will cause the application to fail.
RFE ID 144500
RFE URL
RFE Product IBM MQ
  • Guest
    Sep 16, 2020

    We are considering adding support for this to a future version of MQ

  • Guest
    Aug 9, 2020

    To avoid message properties being given to an MQ application that does not understand them, define the queue with PROPCTL(NONE)