Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 Not under consideration
Created by Guest
Created on May 28, 2026

Allow a transport to be excluded from the plug-in generation

To allow separation of applications on different thread pools (and associated transports), it would be useful to be able to specify which transport(s) propagate to the web server plug-in and which ones don't.

Be it with some custom property or else, marking a HTTP transport to not propagate to the plug-in would allow customer to set up the MetricsApp to run on a separate thread pool, so that it keeps responding even if the WebContainer thread pool gets saturated.

Right now, the only alternative is to stop automatic generation and propagation, and manually tweak the plug-in config to remove the "metrics transport" from it.

Idea priority Medium
  • Admin
    Jahnvi Bedia
    Jun 2, 2026

    Thanks for submitting your idea.

    We are not going to add this Idea to our roadmap right now, however we’ll keep it on record and revisit it if things change in the future. If you want to discuss this decision further, please contact Madhuri Mathur at Madhuri.Mathur@ibm.com or Jahnvi Bedia at jahnvibedia.28@ibm.com

    Looking forward to receiving more ideas from you on the IBM Ideas Portal.

  • Guest
    May 29, 2026

    Background. Multiple apps are deployed on the same WAS server. One particular app is "metrics" and other apps are business apps. The "metrics" app is associated with port 9082 in a custom transport chain, which has a dedciated thread pool. While other apps are associated with port 9080 the default WC transport chain with default webcontainer thread pool. This results in 3 transports in plugin-cfg.xml, For example, 2 HTTP transport (9080, 9082) and 1 HTTPS transport (9443) under the same WAS server. The "metrics" app is not mapped to webserver and requires direct access to WAS 9082 only. While business apps should go through IHS/plugin to WAS 9080. However, the presence of transport 9082 will be possibly selected, then business apps could be accidentally using the dedicated "metrics" thread pool.