Skip to Main Content

This is an IBM Automation portal for Integration 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Aug 4, 2022

Need a better solution to modify this vmm_communication_locked setting in the file.

When there is an issue communicating to the hypervisor host server as defined and managed by VM Manager Tool after a number of attempts, the vmm_communication_locked will set to true value inside a referenced vmmconf_###### .properties file. This is becoming a very very ignorance that someone would have to manually edit this .properties file and change this vmm_communication_locked setting back to false. I personally have to manually go through a 130+ .properties files myself to update this setting and changed it back to false value. That is completely not acceptable solution for the manual task. It should have been provided an option in the VM Managers panel in the ILMT portal. It should have also reporting this vmm_communication_locked setting in this panel as well showing its value (true or false) so that it can be easily to identify the current value and also PROVIDE an option to change it to "false" ONLY if it is "true". This way, it is ease of use and provide a user friendly way to change this setting from the ILMT portal instead of manually changing this setting inside the .properties file especially the .properties file goes by the ID # instead of the hypervisor URL hostname. This makes it even hardly to identify which .properties file is belong to that hypervisor host server in question.

The bottom line is having this vmm_communication_locked setting reporting in the ILMT VM Managers panel and also provide an option to change it if it is "true" value.

Got it?

Idea priority High
  • Guest
    Nov 8, 2022

    Example in the VM Managers report, provide an option to add a column to display this filename "" and its vmm_communication_locked setting associated with that specific configuration.

  • Guest
    Nov 8, 2022

    Thanks Tomasz, it's good to hear from you. It would be also nice to have option to add additional columns similar to other reports in the VM Managers panel including:

    • user credential defined in each VM configurations. By adding this column in the report, it helps to oversee the user credential for each of the VM configurations instead of clicking on each one to see this information in the detail section.

    • the vmman configure .properties file name associated with each vm configuration. this helps to quickly identify which .properties filename related to that vm configuration in the event there is still a need to manually change or review any setting inside that ,properties file.

    Think of in a large ILMT infrastructure where there might be hundreds of VM configurations defined. Trying to identify which .properties filename is in question inside the /config directory could be a painful. The only way is to run "vmman -status > out.txt" command and review the out.txt file to identify the .properties file.

  • Guest
    Nov 7, 2022

    We are looking into improving experience and troubleshooting for VM Managers in general, so will consider this suggestion as well - thank you!