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® Business Process Manager is based.
Some buses are created automatically for use by the system, the Service Component Architecture (SCA) 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 Business Process Manager, 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 Business Process Manager. Up to six buses are created when you create your deployment environment or configure a server or cluster to support SCA applications. Each of these buses has five authentication aliases that you must configure.
| Service integration bus | Description | System default bus name | Authentication alias |
|---|---|---|---|
| SCA system bus | The SCA system bus is used to host
queue destinations for Service Component Architecture (SCA) modules. The SCA run time,
which supports mediation modules, uses queue destinations on the system
bus as an infrastructure to support asynchronous interactions between
components and modules. The system bus is created automatically when you create a deployment environment or when you configure a server or cluster to support SCA applications. The system bus provides a scope within which resources, such as queue destinations, are configured for mediation modules and interaction endpoints. The bus enables message routing between endpoints. You can specify the quality of service for the bus, including priority and reliability. |
SCA.SYSTEM.busID.Bus | SCA_Auth_Alias |
| SCA application bus | The application bus destinations support the
asynchronous communication of WebSphere Business Integration
Adapters and other System Component Architecture components. The application bus is created automatically when you create a deployment environment or when you configure a server or cluster to support SCA applications. The application bus is similar to service integration buses you might create to support service integration logic or other applications. |
SCA.APPLICATION.busID.Bus | SCA_Auth_Alias |
| Common Event Infrastructure bus | The Common Event Infrastructure bus is used for transmitting common base events, asynchronously, to the configured Common Event Infrastructure server. | CommonEventInfrastructure_Bus | CommonEventInfrastructureJMSAuthAlias |
| Business Process Choreographer bus | The Business Process Choreographer bus name
and authentication are used for internal message transmission. The Business Process Choreographer bus is used for transmitting messages internally and for business flow manager's Java™ Messaging Service (JMS) API. |
BPC.cellName.Bus | BPC_Auth_Alias |
| Performance Data Warehouse bus | The Performance Data Warehouse bus is used for
transmitting messages internally by the infrastructure and for communicating
with IBM Business Process Manager clients. The Performance Data Warehouse bus is created automatically when you create a deployment environment. |
PERFDW.busID.Bus | PERFDWME_Auth_Alias |
| Process Server bus | The Process Server bus is
used for transmitting messages internally by the infrastructure and
for communicating with IBM Business Process Manager clients. The Process Server bus is created automatically when you create a deployment environment. |
PROCSVR.busID.Bus | PROCSVRME_Auth_Alias |