JMS messaging

Liberty supports asynchronous messaging as a method of communication that is based on the Java™ Message Service (JMS) programming interface. The JMS interface provides a common way for Java programs (clients and Java EE applications) to create, send, receive, and read asynchronous requests as JMS messages. With Liberty, you can configure multiple JMS messaging providers, which can be used by the JMS applications.

The following JMS messaging providers are supported in Liberty:
  • Liberty embedded messaging engine, as the JMS messaging provider
  • Service integration bus, which is the default messaging provider of WebSphere® Application Server traditional
  • IBM® MQ messaging provider, which uses the IBM MQ system as the provider

Your applications can use messaging resources from any of the three JMS providers. The choice of the provider is made based either on your messaging requirements or for integration with an existing messaging system. For example, you might want your applications to connect locally to the Liberty messaging provider without the need to configure any external messaging provider, in which case you would use the Liberty embedded messaging engine. Alternatively, you might want to integrate with your existing messaging infrastructure, such as IBM MQ. In such cases, you can either connect directly by using the IBM MQ messaging provider or configure a service integration bus with links to the IBM MQ network and then access the bus through the default messaging provider.