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 Submitted
Workspace API Connect
Created by Guest
Created on Nov 3, 2026

Smaller Deployment Profiles Options for APIc sub-systems like wM API gateway

Based on client observations, the minimum deployment profiles for certain API Connect components—specifically the webMethods API Gateway—are still too large for non-production test environments, even though actual resource utilization in these environments remains very low.

For example, a client with 4 different domains and 3 non-prod environments (Dev, Test, UAT) has 1 API Manager component managing 12 separate webMethods API Gateway clusters (4 domains x 3 environments). Because the minimum deployment profile for the webMethods API Gateway is set to n1xc3.m6, they are required to provision 36 CPUs just for the test environments.

This high baseline profile drastically increases underlying software licensing costs, including Red Hat OpenShift (OCP) and VMware.

Requested Solution:
Provide smaller/lighter deployment profile options for the webMethods API Gateway so clients can manage non-production topology requirements much more efficiently.

Idea priority High