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.
Idea review. Thank you for taking the time to raise this suggestion. In future we would like to support the ability to replay messages to remote MQ Queue Managers using an MQ Client connection. In these kind of situations, we think it would be an advantage to allow for a dynamic set of replay locations, and also suspect that carrying a default setting within the payload of the published monitoring message could be confusing (conceptually, the publication is the message being recorded, as opposed to dictating where it should be replayed ... so you could imagine some architectures wanting to subscribe to the recordings for replay to multiple destinations). Given this, we agree with the concept of offering a default setting in order to help avoid accidentally replaying to an incorrect destination, but feel this would be best implemented as a default setting in the replay configuration or in the Record and Replay WebUI settings, but probably best not in the recorded message itself. Status is updated to Future Consideration.