IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > The enterprise service bus in IBM BPM > Messaging infrastructure
Service integration buses for IBM BPM
A service integration bus is a managed communication mechanism that supports service integration through synchronous and asynchronous messaging. A bus consists of interconnecting messaging engines that manage bus resources. It is one of the WebSphere Application Server technologies on which IBM BPM is based.
Some buses are automatically created for use by the system, the Service Component Architecture applications that you deploy, and by other components. You can also create buses to support service integration logic or other applications, for example, to support applications that act as service requesters and providers within IBM BPM, or to link to WebSphere MQ.
A bus destination is a logical address to which applications can attach as a producer, consumer, or both. A queue destination is a bus destination that is used for point-to-point messaging.
Each bus can have one or more bus members, each of which is either a server or a cluster.
The bus topology is the physical arrangement of application servers, messaging engines, and WebSphere MQ queue managers, and the pattern of bus connections and links between them, that makes up your enterprise service bus.
Some service integration buses are created automatically to support IBM BPM. Up to six buses are created when you create your deployment environment or configure a server or cluster to support SCA applications. These buses each have five authentication aliases that configure.
See