---Micro Broker Commands---
broker - List micro broker properties
brokerclients [<client>]- List micro broker clients
brokerdisconnect <client> [flush] - Disconnect client
brokerreset - Delete and restart micro broker
brokersnap - Create micro broker snapshot
brokersubs [<topic>] - List subscribers
brokersubs delete <client> <topic> - Delete client subscription
brokertrace [html] - Create micro broker trace
brokertracebuffer <value> - Set micro broker trace buffer
brokerusage - List micro broker usage statistics
The brokertrace and brokersnap are possibly the most useful. The brokertrace command is somewhat moot in 6.2.2 and up; you can set the trace level com.ibm.micro FINEST to pipe micro broker debug to the trace log. Be aware that brokertrace and the micro broker in general buffer the trace messages (500 lines is the default). So brokertrace is a good "point-in-time" command but not applicable for long running servers. Again, com.ibm.micro FINEST is the better solution. The other commands allow me to check the broker's "health" as well as disconnect clients to test their ability to reconnect. The brokerreset command should be used with care. It could be the case that the broker's persistent store becomes corrupt. When this happens, you generally delete the broker from disk using the resetscript in Integrator. Be aware, reset using the script or the command can result in lost messages. It's a useful command in the rare circumstances that the broker continuously fails to start properly leading to the necessity of a reset. The other commands are simply calls into the micro broker's public API.
Here's an enviable screenshot.