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,
Post an idea
Upvote ideas that matter most to you
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.
The IDEA is to let the "safe mechanism" be optional, by providing this:
An administrative option should be created in the UCD, leaving it up to the tool administrator to select how to use the simultaneos session licenses:
1) When exceeding the simultaneos session license limit, allow the deploys to continue (what you named as "safe mechanism", the way UCD is working today);
2) Limit the use of the tool's functionalities (Agents) when the licensing limit is reached (New option requested in this idea)
Attachments Open full size
Let's assume the following: A deployment is started and 3 agents are doing deployments in the first minutes and there are enough session licenses available. Now in the next minutes additional processes are started on other 2 agents and now the used sessions would swap over the "licensed" number. In the actual implementation it would write a log entry and goes on.
With the switch, the only feasible action would be to wait till licenses are available.
Do i have understood you correct?
Attachments Open full size
I do understand the designed tool's behavior and, beacause of this, we opened this Idea to change it. The point is that "Session licensing" for agents doesn't give UCD Admins the option to control the desired behavior for company. If we don not want to have the "safe mechanism" (of automatic use of more sessions) enabled, we have no alternatives. It is interesting that this safe mechanism can be available (If we set this option on), but it should not be a imposition, since we can choose to find other internal strategies of better using agents and, consequently its license consumption.
Attachments Open full size
IBM UrbanCode provides a number of different licensing types. The main ones are the "classic" Server/Agent and the other Session type.
Server/Agent requires that all the agents and servers which will be used need to have a license. Without a license they will either not work or will give you a restricted functionality.
Session licensing means that only agents are licensed (floating, simultaneous sessions). It also provides a safe mechanism, when more sessions are needed than available the deployment will be execute BUT a warning will be put into the log to check if this happens too often -> need to add additional licenses.
This is a design as requested by customers, so that they can still deliver deployments without having to wait till licenses are free to use.
More detail here: https://www.ibm.com/docs/en/urbancode-deploy/7.2.0?topic=management-license-scenarios
Attachments Open full size
Technicallly, authorized licenses (server/agent) are proxied by UCD to agents during startup time. Otherwise, floating licenses (simultaneous sessions) are acquired by each agent during deployment time… it should be simple as does not allow deployment by unlicensed agent anytime (enabled by flag at system settings to allow customer keep/change behavior from soft to hard block when using just simultaneous sesson or mixed licensing)…
Attachments Open full size