WS-Notification - supported bindings

This WS-Notification implementation supports both HTTP and JMS bindings. Which you choose depends upon your business needs and performance requirements.

WebSphere® Application Server supports the following Web service bindings for connection to a WS-Notification service point:

The choice of binding to use is a business decision based on existing Web service infrastructure and requirements. In situations where there is no business imperative, you should use the HTTP or HTTPS bindings rather than SOAP over JMS in order to minimize the path taken by the web service requests as shown in the following diagram. Invocation through SOAP over JMS requires an extra trip through the messaging provider before the event notification is inserted into the service integration bus topic space.

In the following figure, a SOAP over HTTP notification message is received by a listener, then routed through the associated notification broker and on to a topic space within a messaging engine. A SOAP over JMS notification message is received by a messaging engine, then routed back out of the messaging engine to a message driven bean, then into the notification broker and on to a topic space within the same messaging engine.

This figure is described in the surrounding text.



Related concepts
Learning about WS-Notification
Learning about WS-Notification
Related tasks
WS-Notification - publish and subscribe messaging for Web services
Securing WS-Notification
Related reference
WS-Notification troubleshooting tips
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=cjwsn_bind
File name: cjwsn_bind.html