WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

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.

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.
Related tasks
WS-Notification - publish and subscribe messaging for Web services
Learning about WS-Notification
Securing WS-Notification
Related reference
WS-Notification troubleshooting tips

Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/concepts/cjwsn_bind.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)