A service integration bus is the messaging infrastructure of WebSphere Application Server's service integration technology. It supplies the transport, destinations, and persistence behind the default messaging provider: applications look up JMS connection factories and destinations that resolve to a bus, and the messaging engines running on bus members move the messages. Option C captures that relationship, a component used by the default messaging provider for transport.
Each alternative misplaces the bus. Option A is wrong because internal communication between administrative services is handled by the administrative connectors and the high availability manager, not by a bus. Option B is wrong because mediations are services that can be attached to bus destinations to process messages in flight; they are not deployed onto an embedded IBM MQ JMS provider, and the embedded provider concept does not apply to the bus in that way. Option D is wrong because the bus is not a separate product. IBM MQ is the separate product, and it can be connected to a bus through an MQ link or used directly through the IBM MQ messaging provider, but the bus itself is part of the application server.
When planning a bus, administrators add application servers or clusters as bus members, and each member hosts or can host messaging engines, which determines availability and scalability.
[Reference: Service integration technology; Default messaging provider; Service integration bus and bus members.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit