Initially this was one of the major turn off’s for me to switch to UM from Broker but i eventually learned to get past these limitations. I built a Custom UI (JS\HTML5 with rest calls to IS Java services) using the UMS Java API that provides developers some basic functions to have an insight(read only) in to UM in non-dev environments.
I personally believe that all the blocks to implement a full fledged operational UI like this in MWS are already out there in the form of Code samples\ snippets. The actual work is to create the CAF screens to embed these blocks in to MWS.
If you have OFI, you could create rules to monitor queues\channels for thresholds. This can be very helpful with operational monitoring of UMS at Queues\channels level.
I have been told that there is something in the works to get the same functionality that MWS provided for Broker with UM as well but haven’t heard anything back about it. This was from almost 2 years ago. Maybe its just not a priority for SAG at this time.
You can always open a feature request on Brainstorm to formalize the request.
#webMethods#Integration-Server-and-ESB#Universal-Messaging-Broker