Topology for WS-Notification as an entry or exit point to the service integration bus

In addition to the ability to pass information between WS-Notification producers and consumers, the WS-Notification support provided in WebSphere® Application Server also acts as an entry or exit point to the service integration bus. Event notifications that are published by WS-Notification applications are inserted into the service integration bus where they can be modified, rerouted or consumed by any of the other applications that are connected to the bus. Equally, publications sent by service integration bus clients such as JMS can be received by WS-Notification consumers.

In the following figure a WS-Notification publisher inserts an event notification into the notification broker that is received by a JMS message consumer. Conversely a JMS message producer can publish a message that is received by a notification consumer. Messages pass from the publisher into the notification broker, using SOAP over HTTP , and travel through a WebSphere Application Server, to the JMS provider, and out to the JMS message consumer using JFAP. Conversely, messages pass from the JMS message producer into the JMS provider using JFAP, and travel through a WebSphere Application Server to the notification broker, and out to the notification consumer using SOAP over HTTP.

Figure 1. Example of the message paths from a publisher and a JMS MessageProducer This figure is described in the surrounding text.

For details of how messages inserted by JMS applications are viewed by WS-Notification applications, see Interacting with JMS message types.

Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 1:44:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-dist&topic=cjwsn_scen2
File name: cjwsn_scen2.html