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.


ADD A NEW IDEA

Pinned ideas

View all
PINNED Add a "Maximum persistent reuse" parameter for the backside of an MPGW or WSP
On an MPGW or a WSP, I want to be able to configure that the persistent backside connection should be closed after X amount of requests have been sent through that connection. I can already do this for the frontside by setting the "Maximum persist...
Share feedback 1
PINNED OpenAPI schema validation including headers
Currently to schema validate a REST based API in DataPower you have to extract the JSON schema from the OpenAPI file and then code manually code the individual header checks defined in the OpenAPI file Would be a vast improvement to be able to j...
Share feedback 1

All ideas

    Showing 175

    Add support for Alias CipherSpecs in MQIPT

    Hello, since 9.2 IBM MQ support Alias CipherSpecs/CipherSuites, that is a keyword such as ANY_TLS13_OR_HIGHER for which the queue manager and the client will negotiate the best available CipherSpec/CipherSuite. This saves effort in constantly upda...
    over 1 year ago in MQ, MQ Advanced & MQ Appliance 1 Functionality already exists

    HTTP Request OAuth 2.1 Compatibility and Client Credentials Flow

    As an integration developer, I want the HTTP Request policy to support additional OAuth 2.0 flows like client_credentials (with claims such as scope and resource), so that I can call modern secured APIs that require scope, resource, or other custo...
    7 months ago in App Connect 2 Functionality already exists

    Enhancement Request for IBM MQ Web Console.

    Description: I would like to propose an enhancement to the current IBM MQ web console. The existing setup is a one-to-one mapping, where each queue manager must be accessed individually through its respective route. This limitation means that ...
    about 1 year ago in MQ, MQ Advanced & MQ Appliance 3 Functionality already exists

    A tool to recover message in MQ shared queue

    In the case of a queue manager failure, it would be nice to be able to recover messages. It's already exists a tool to recover message : CSQLOG utility. But for shared queues CSQLOG doesn't work, there are no tools for this purpose. It would be ...
    8 months ago in MQ, MQ Advanced & MQ Appliance 2 Functionality already exists

    Require MFA functionality for MQ

    As part of security standards we have enabled MFA(Multi Factor Authentication) to all our applications. We would like to enable the same for MQ Web Admin Console. This will bring in more secured logins to our console as MQ is being one of the crit...
    3 months ago in MQ, MQ Advanced & MQ Appliance 1 Functionality already exists

    Activate Service Result Cache Policy at Resource Level

    We request the ability to activate the Service Result Cache policy only for specific API resources rather than the entire API. This would enable more granular caching configurations. Benefits: Performance: Reduces server load by caching selectivel...
    5 months ago in webMethods API Gateway 1 Functionality already exists

    Enable a way to clean / refresh xml-names cache via manual / rest / soma

    - To have a mechanism wether is manual with a CLI command or via SOMA/REST to clean / refresh the xml-names cache when the limit is reached. - It is prefreably that we can set this limit to decide if this value is 50% or 60% or 70% for instance. T...
    almost 4 years ago in DataPower Gateway 4 Functionality already exists

    provide additional security to the cluster queues when using shared Qmgrs to send msgs to downstream qmgrs

    Whats missing?? With existing MQ product version 7 to 9.3 - when comes to Cluster design there is no control over shared applications using the same qmgr(shared qmgr) and sending msgs to downstream applications. With the MQ Cluster by design we se...
    almost 3 years ago in MQ, MQ Advanced & MQ Appliance 6 Functionality already exists

    Add the ability to turn on DataPower Probe for a single API or even a single API Operation

    Within our DataPowers in use for SOAP traffic we're able to turn on Probe in DataPower for a single Web Service Proxy to capture http requests and responses for that specific Web Service Proxy. Within DataPowers controlled by API Connect for REST ...
    about 1 year ago in API Connect 2 Functionality already exists

    Ability to delete files after they have been zipped in a folder

    Yes I know I can add another step, but should be an option when zipping files
    6 months ago in webMethods Managed File Transfer 3 Functionality already exists

    By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
    Do not place IBM confidential, company confidential, or personal information into any field.