Event publication between cells through an MQ network topology
In this topology the service integration bus infrastructure is used to transmit event notifications between two cells (buses) through a network of WebSphere MQ queue managers.
This is achieved in a similar fashion to the Event publication between cells topology, by creating a new WebSphere MQ link and a publish and subscribe bridge between the first bus and the MQ network (and MessageBroker or EventBroker instance). This ensures that messages published to a service integration bus topic space are forwarded to the message broker. The same configuration is carried out between the second bus and the MQ network or MessageBroker instance to receive messages published from the first bus.
Thus messages published in either bus are forwarded to the service integration bus topic space (and thus notification consumers attached to the appropriate notification broker) on the other bus, through the MQ infrastructure.
In the following figure, there are two cells each on a separate bus. Each cell contains an application server, and every application server contains a WS-Notification service and messaging engine. Each cell is connected by a publish and subscribe bridge over an MQ Link to a network of WebSphere MQ queue managers. Requests received by a server in one cell are put on a queue, then routed by a message broker to another queue, then routed to consumers associated with the server in the other cell.
Figure 1. Example of event publishing between cells through a MQ queue manager network
Related concepts
WS-Notification
Related tasks
Use WS-Notification for publish and subscribe messaging for web services Secure WS-Notification
WS-Notification troubleshooting tips