Watson Commerce Ideas

Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Call Center and CPQ are now a part of Watson Supply Chain. Please bookmark the Watson Supply Chain Idea Portal.

Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, Dynamic Pricing, Price Optimization, Promotion Optimization, Markdown and Deal Management. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and IBM experts on the Watson Marketing and Commerce Community and the Order Management Interest Group, now a part of Watson Supply Chain.

Submit ideas for other Watson Customer Engagement Products:

  • Watson Marketing
  • Watson Supply Chain

Order Managment on Cloud INT Server instance to log failing MQ message MSGId and create alert.

Within an OMoC (Order Management on Cloud) environment an INT server instance (IntgName) integrates with the MQ QMGR for reading/writing MQ messages for OMoC integration processing. When the MQGET of a message from an inbound queue fails we see a generic exception in the IntgName instance log, but we are not able to identify the actual message that has failed. The message is no longer on the queue, and so all we know is that there has been message processing in error, but not what the message is. We need to be able to track a message identifier in the IntgName instance log, such as the 'MQ MsgId'. We ideally also need a plugin to this log to create an alert for the message in exception. The first step is to identify what we should use as a unique message identifier, then make sure this is in the exception record.


This will benefit CoC OMoC support,  and OMoC customers, and SI teams to trace lost MQ messages.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 7 2019
  • Uncommitted Candidate
How will this idea be used?

This logging will be used by CoC support, customer OMoC support teams, and SI teams to troubleshoot lost MQ messages, that can be anything from a customer order, to a catalogue update.

What is your industry? Consumer Products
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    SUDHIR Balebail commented
    7 Mar, 2019 01:55pm

    This is a very valid requirement for troubleshooting and triaging issues relating to MQ interaction . I will move this to Under consideration. The way in which we choose to resolve this may differe from the ask, but the need is understood, and our effort will be to make sure it is met.