Service integration bus messaging provider

A service integration bus is a group of one or more application servers or server clusters in a WebSphere® Application Server cell that cooperate to provide asynchronous messaging services. The application servers or server clusters on a bus are known as bus members. In the simplest case, a service integration bus consists of a single bus member, which is one application server.

The service integration bus messaging provider uses service integration functions and is part of the WebSphere Application Server runtime environment. To use the default messaging provider, your applications must connect to a service integration bus. You can assign JMS queues (for point-to-point messaging) or JMS topics (for publish/subscribe messaging) as destinations on the service integration bus.

The default messaging provider is characterized as follows:
  • A service integration bus consists of messaging engines that run in WebSphere Application Server processes and dynamically connect to one another by using dynamic discovery. A messaging application connects to the bus through a messaging engine.
  • Messaging engines use WebSphere Application Server clustering to provide high availability and scalability, and they use the same management framework as the rest of WebSphere Application Server.
  • The bus client applications can run from within WebSphere Application Server (JMS), or run as stand-alone Java™ clients (using the J2SE Client for JMS) or run as clients that are not Java based (XMS).

Icon that indicates the type of topic Concept topic



Timestamp icon Last updated: Monday, 5 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-libcore-mp&topic=cwlp_msg_sibus
File name: cwlp_msg_sibus.html