Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

ADD A NEW IDEA

Workload Automation

Showing 281

Auto start netman when it goes down abruptly

Netman process helps in sending and receiving the messages to and from the agents. When it goes down unexpectedly, it has to come up automatically which will not impact the daily refresh as well.
about 1 year ago in Workload Automation 0 Future consideration

IWS auditing for Login events (DWC, conman, composer) and changes to configuration and security files

See attached
about 2 years ago in Workload Automation 0 Future consideration

Simplify ACL/SDOM management with IWS >9.5

Hello, Currently we use SDOM structure to limit our applicative manager to their application and to force norm usage. For exemple - For Job name: 3 characters for application code (CCX) 1 character for job type (one of these 3 letters XTM) 1 chara...
over 1 year ago in Workload Automation 9 Future consideration

Webservice Job: Pooling the execution status in the same webservice jobs

Hi team, We are using webservice jobs run various seeded jobs using the webservice plugins. In second step we are defining an executable job to fetch the report id/request id from the XM response. In last step we are doing the conditional checks i...
7 months ago in Workload Automation 0 Future consideration

installation improvement for LDAP

Today we solved the ldap authentication problem. It was due to a conflict of two users with the same username in two different user repositories: basic and LDAP. Since there is no more a local user repository in Liberty a copy of your real install...
over 1 year ago in Workload Automation 0 Future consideration

Support for containerized MDM and BKMDM on two different networks

Currently, creating two domain manager docker containers in one host machine, but on different docker networks, does not work. These DMs do not connect. Would like to have official support for having two containerized domain managers hosted on dif...
about 1 year ago in Workload Automation 0 Future consideration

DWC - Filters Improvements

We have more than one team that manages the production environment and in most of the time each team takes care of a group of applications running under IWS. Using standards for Job, JobStream and Resource names we managed to create filters that c...
over 5 years ago in Workload Automation 1 Future consideration

Improving Resiliency #3: gracefully resuming TWS services even after a sudden TWS stop

Event in a scenario of a sudden TWS Stop (abrupt kill of TWS services), the TWS Agent needs to have the capability of gracefully resuming its services after a failover.
about 1 year ago in Workload Automation 0 Future consideration

Improving Resiliency #1: re-attaching "running OS processes" in secondary node after a failover

Whenever a failover happens, we need the Agents to be capable of re-attaching the running OS processes (attached to each individual SAP Jobs) when its services are restarted/failed-over from Site A to Site B.
about 1 year ago in Workload Automation 0 Future consideration

Putting module EQQSSCNMx above the line

Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. When migrating IWSz we are using BUILDSSX REBUILD and SSCMNAME TEMPORARY to avoid IPLs. After migration we are restarting IWSz with SSCMNAME PERMANE...
over 4 years ago in Workload Automation 0 Future consideration