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
Created by Guest
Created on Oct 23, 2021

Support for profile change at sub-system level

The customer current has API Connect installed via CP4I, so the description here is specific to API Connect, but this RFE could also be applied to other products. 1. APIC consists of many components or sub-systems. A customer may have different HA requirements for different sub-systems based on their resource and license constraints. The current CP4I deployment through Platform Navigator only provides two pre-configured profile options: one for DEV and one for Production. 2. The profile change at sub-system level is supported if APIC is deployed as documented in https://www.ibm.com/docs/en/api-connect/10.0.1.x?topic=kubernetes-installing-api-connect-subsystems. With this installation, you can make changes following instruction in https://www.ibm.com/docs/en/api-connect/10.0.1.x?topic=configuration-switching-deployment-profiles-kubernetes. The customer would want the same capability to modify profile configuration at individual sub-system level through CP4I Platform Navigator or command line.
Idea Priority Urgent
  • Admin
    Andy Garratt
    Oct 29, 2021

    Thanks for submitting this, it's something we're looking at to give more flexibility in the deployment of the API Management capabillities, e.g. by subsystem as you say. We're looking at whether this will best be achieved by enhancements to the operator or by other means.