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)
ITNM installs the client to connect to database for access the NCIM tables. For Oracle,having it installed and upgraded from 22.214.171.124 to 126.96.36.199 (with many steps in-between over the years), I see two clients at $NCHOME/precision/platform/linux2x86...
When scanning vulnereability of our application server(s), we've noticed that JBoss 4.x is no longer supported by Red Hat, which caused vulnerability flags. We've been informed that JBoss itself is tightly integrated with TNPMW application, so upg...
HuaweiM2K Java Collector should discover all neTypes as in XML dumps
This case is a follow up from the previous TS005353782 case which was closed even before our last inquiry was answered.
For the NeType combination below which the previous PMR support described as “Not Supported”, we would like to know when it wi...
Process to clean up old entities from active devices
Once a device is discovered bu ITNM, it creates many entities in NCIM database, representing the device, interfaces etc.If any of those entities are not valid anymore (e.g., one of the interfaces is disabled), it is not deleted from the database. ...
Gwconnect() rule functionality in StandardEventEnrichment
We need it to get entities, connected to one, we specify. We pass entityId to GwConnect and then fill variable ConnectedEntities with returned value. Alternatively, if ConnectedEntities == NULL, we pass entityId to GwContains and then pass resulti...
ITNM 188.8.131.52:Alcatel SAM 5620 Collector : Connect to Multiple EMS's
We are using Alcatel5620Sam Java collector to connect to single EMS and able to download topology successfully. Currently in customer environment, Nokia NFM-P EMS has been configured with High Availability so that any of the one instance will be i...
New Collector for Discovering FiberHome MSAN devices
The customer has a set of MSAN’s that are from FiberHome OEM. The OEM supports TL1 as NBI for collecting inventory data.
Since ITNM doesn’t have a generic TL1 collector, we will need a new collector developed.
The following are the TL1 commands ...
Add Failover/failback support for to Alcatel5620Sam Collector
In an environment with two NSPs, one acting as primary and another acting as cold-standby, the collector is not able to recognize that the currently configured NSP is not active and fails to run a discovery.
Do not place IBM confidential, company confidential, or personal information into any field.