This portal is to open public enhancement requests for IBM Sterling products and services. 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.
Hi, Since we have not received any further information on business use cases requested on 3/10/21, I am closing this as. Please reopen the idea with all required information if needed
Hi, Thanks for creating this idea.
Could you please add business use cases for your idea? In your current on premise env, do you use separate channels for different systems. If yes, could you please include details about different errors that you see and how channels help to classify errors.
FYI
For OMS applicatiom receiving messages through different integration server, alert type can provide a classification of alerts raised from different queues.
2. Different source systems listed here , which connects to MQ to send messages will have an error handling mechanism to handle error scenarios if messages are not delivered to queue.
3.JMS metrics on monitoring dashboard with OMoC SST provides multiple parameters to track health of Cloud MQ.