Service integration technologies
Service integration provides asynchronous messaging services.
- Buses and bus members
- Groups of servers cooperating to provide asynchronous messaing services are called a service integration bus. Each server on the bus is a bus member. We can also add WebSphere MQ servers as bus members, allowing messages to be written to WebSphere MQ queues.
Buses can be connected, allowing applications that use a local bus to send messages to destinations to a foreign bus. Note that applications cannot receive messages from a foreign bus.
- Messaging engines
- Each bus member contains a messaging engine that sends and receive requests, and hosts destinations. To host queue-type destinations, the engine includes a message store where for hold messages until consuming applications are ready to receive them, or preserve messages in case the messaging engine fails. If the bus member is a server cluster, it can have additional messaging engines to provide high availability, or workload sharing characteristics. If the bus member is an MQ server, it does not have a messaging engine, but it lets you access WebSphere MQ queues directly from WebSphere MQ queue managers.
- Messaging providers
- Applications use the Java Messaging Service to interface with messaging providers, including service integration, which is the default messaging provider, and WebSphere MQ as an external JMS messaging provider.
Related concepts
MediationsService integration buses Bus members Messaging engines Bus destinations Message stores Service integration security High availability and workload sharing Service integration configurations Service integration notification events Message reliability levels - JMS delivery mode and service integration quality of service Dynamic reloading of configuration files Service integration backup Administer service integration buses Administer messaging engines Manage messaging with the default messaging provider