Skip to Main Content
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
Workspace API Connect
Created by Guest
Created on Oct 7, 2021

High Availability just for Gateway on CP4I

We have been running API Connect on CP4I on Openshift on Azure cloud since 2019. For an API Connect instance (v10.0.3.0) that is deployed from deployment profile n1xc7.m48, we have been running high availability tests and have noticed that for this profile setting gateways to 3 pods neither provides high availability nor is it supported by IBM. In other words, we require high availability JUST for the Gateway component and not others (such as Analytics, Management Server, Developer Portal). Not having High Availability for the Gateway is a major setback in our Cloud Pak journey whereas going for high availability for all API Connect components is an overkill in terms of licensing and resourcing costs.
Idea priority Urgent
  • Admin
    Nathan Ziemann
    Nov 11, 2021

    Currently, deploying API Connect through the CP4i platform navigator simplified experience, two static deployment types are available. non-HA, where number of pods is 1 and HA, where pods is 3. Currently there is no way to mix and match HA vs non-HA of different component of the solution. I will accept this as a future candidate.