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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
A key differentiator between a virtual appliance and software, is the appliance would not require O/S patching. Given patching is such a big issue for many organisations, an option to only have to patch an MQ appliance, rather than software MQ+O/S+monitoring agents (and so on) would be less disruptive, faster and cheaper.
A virtual image for learning, developing, or testing of administrative processes is under consideration. However, we would suggest that in many cases for messaging application development/test purposes, a software MQ installation such as MQ Advanced for Developers may be more appropriate than a 'Virtual appliance' (and is already available). It is important to note that this is exactly the same product, supporting exactly the same client application protocols, simply provided in an alternative 'form factor'.
Just wanted to +1 the point about having these available for development purposes.