Broker Server is a message queuing facility. It support message routing, queuing, filtering, and storage.
It supports various APIs with which applications, including Integration Server, can interact.
“Broker messaging” consists of calling wM-defined APIs to interact with Broker. A client uses one of the Broker libraries (Java, C#, others) to communicate with Broker.
“JMS messaging” consists of calling Java-defined APIs to interact with a JMS provider. The client uses the JMS classes/methods defined by J2EE/JEE to communicate with a JMS provider. The JMS classes rely on a library provided by the JMS provider. You are free to use any provider. wM Broker is a JMS provider.
JMS isn’t a messaging backbone per se. Indeed, it is only an API.
Integration Server provides services to interact with Broker in either fashion. Which to use is mostly just personal preference. As Sumit notes, there are no hard and fast rules for deciding which will work best for your situation. If your organization already knows and understands JMS then perhaps that would be the way to go.
#broker#Universal-Messaging-Broker#Integration-Server-and-ESB#webMethods