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)
Add historical reporting features available on IWS to IWS on Cloud.
IWS on Cloud (SaaS) does not provide the historical reporting features available in the on-premise versions. The "historical reports" features should be available to SaaS customers too. The priority is on "job run history".
Request to Add LDAP/NT/OAUTH Authentication Types to IBM Workload Scheduler - RESTful ,Webservices API Jobs
For using IWS RESTful , webservices jobs, the user' credentials have “Basic authentication with httpsurlconnection” to connect TWS REST endpoints. Request to Add LDAP/NT/OAUTH Authentication Types to IBM Workload Scheduler - RESTful ,Webservices A...
Allow users to set their own default columns per object type
For the DWC user interface, under "System Configuration" > "Set User Preferences" users should be able to set their own default column set for how they want to see result lists for each object type. This user-default set of columns would be use...
Oracle E-Business Plugin for Workload Scheduler - Job isn't terminated in Oracle upon termination in IWS.
After submission, when the job is running and is reported in EXEC status in IBM Workload Scheduler, you can stop it if necessary, by using the kill command. The kill command stops the job in IBM Workload Scheduler, but not in the Oracle E-Business...
Cancelation of WebSphere batch job (wsgrid.bat) on Windows should invoke shutdown hook i java
Cancelling a WebSphere Batch job on Windows, a java.exe process started from the wsgrid.bat only kills the java process. The shutdown hook in java is not called and the job/step i the websphere bacth container is not interrupted/stopped. This is "...
Currently the CP does not update in real time the ESTIMATED END of a critical chain. Considering that we now use the 'CRITICAL JOBS' panel as the only forecasting tool for what concerns the conclusion of critical batches, having the information re...
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.5It 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 DW...
Modify how DA launches a job to mimic how FTA launches the same job
FTA launches a job by first launching jobmanrc and then if LOCAL_RC_OK is set to true, it launches .jobmanrc in the logon user's home dir. In this process, it never sets the variable PATH. A DA launches a job by first launching taskLauncher.sh and...
Do not place IBM confidential, company confidential, or personal information into any field.