Skip to Main Content
Cloud Platform

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 portals, 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 UrbanCode
Categories Deploy
Created by Guest
Created on Oct 22, 2019

Server-enforced agent concurrency limits

I propose a feature whereby agents can be configured in the server UI to have concurrency limits. Currently, concurrency limits can be specified in processes for multiple-component deployments. It would be useful to be able to specify how many Component Processes can run on a given agent at any one time. This would tie in with the workload assessment for Pools when assigning an agent, but also force processes to become 'queued' waiting for an available slot for shared agents. This would also allow administrators to provide some protection for agents that are shared among various users - at present, agents will just keep processing new component requests until they run out of resources, but with configurable limits in place, this would also guarantee a minimum level of performance.

Idea priority Low
RFE ID 137500
RFE URL
RFE Product UrbanCode Deploy
  • Guest
    Apr 16, 2021

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Jan 25, 2021

    Dev team investigating in Q1 2021