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 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)
Possible to see workstation pools associated or defined for an agent workstation.
TWS version 184.108.40.206 TDWC version 220.127.116.11 Possible to see workstation pools associated or defined for an agent workstation. In critical situations where a server with a TWS agent goes down or have severe performance problems, it is necessary, to identify which TWS agents as well as defined pools on this agent that is “hurt” by this situation. We know that the agent and pools will be marked as “Agent running = NO” in the TDWC, but if you have several agents and multiple pools on these agents, it can be very hard to answer question like: “Which pools is defined on this agent workstation?” Today one can open a pool definition in the TWS database and see agents defined as members on this pool. But it's not possible to see which pools that are served by a given agent. With this possibility operators can react promptly and without errors if critical situations occurs where an agent is down or have severe performance problems. It should be possible to create lists with information in TDWC as well as in TWS CLI (composer and/or conman). Please note that similar enhancements are addressed in RFE: 22540 and 25320.
Do not place IBM confidential, company confidential, or personal information into any field.