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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Need a better solution to modify this vmm_communication_locked setting in the vmmconf_#######.properties 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.
Do not place IBM confidential, company confidential, or personal information into any field.