Skip to Main Content
Cloud Management and AIOps

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 notifications 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.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

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

This is not a new idea rather than reporting on a lost feature in TWS 9.5

There is no way to rename the Workload Broker Workstation in TWS 9.5
It take the host name and add _DWB as post fix to the name. This is not good when we use backup master and long term switch to the backup master. In fact I manage to rename the DWB workstation to a conman name between Master and Backup Master. Now the new name is visible but proctree of the netman process still show the old name.

Idea priority Medium
  • Guest
    Jul 28, 2021

    Can --brwksname <broker_workstation_name> use ./serverinst.sh with any upgrade type option ?


  • Guest
    Jul 2, 2021

    Thanks for that. I will try it with other future installations. I have already installed it in few environments like SIT and DEV. Can we update the already installed instances with this extra parameter of --brwksname <broker_workstation_name>?

    Hence, Is there any way to rename it after install it? As I mentioned, I have already renamed and it still works as the renamed DWB name. When getting the list of CPUs from the composer command it shows with the new name. The only place still it is referring to the old name is the 'proctree' of the 'netman' process. I strongly believe the 'proctree' is picking the old name from one of the xml or properties files, so there must be a way to change it too.


  • Admin
    Marco Cardelli
    Jul 1, 2021

    The requirement is valid, anyway we suggest to use the following variable at installation time to set the Broker Workstation: [--brwksname broker_workstation_name].