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 Under review
Created by Guest
Created on Jan 22, 2026

Add support for setting JMSType / mcd.type via HTTP headers when using IBM MQ HTTP Endpoints.

When using IBM MQ HTTP Endpoints to put messages onto queues, there is currently no HTTP header available to set the JMSType (mapped to mcd.type in the MQ message descriptor).

Other commonly used JMS/MQ message properties such as JMSPriority (ibm-mq-md-priority) and JMSReplyTo (ibm-mq-md-replyTo) are already supported through HTTP headers. Providing similar support for JMSType / mcd.type would bring consistency to the HTTP Endpoint feature and make it easier for customers to migrate existing JMS-based integrations to HTTP-based messaging without changing message semantics.

Idea priority Medium