Broker administration is done via My webMethods. You can define Brokers, doc types, JMS topics, etc. via MWS.
You won’t be able to use the JMS API for administration activities. JMS is an API specification focused solely on message exchange. Administration of JMS varies depending upon the JMS provider tool being used.
Out of curiosity, what is driving the desire to use only Broker and eliminate IS? I would think the reverse would be more advantageous. And if you’re moving away from IS to something else, I would presume that something else has JMS facilities. Broker is a good, well performing component but it seems odd to me that someone would use just that out of the wM suite.
#Universal-Messaging-Broker#Broker-JMS#webMethods#Integration-Server-and-ESB