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

Simple Web services use pattern

In this use pattern WebSphere Application Server is used solely as a notification broker to enable producing and consuming WS-Notification applications to communicate with each other. The applications are unaware that the NotificationBroker service is implemented by WebSphere Application Server.

To the left are three small boxes labeled "publisher", "subscriber" and "notification consumer". To the right is a large box labeled "WebSphere Application Server". In the middle, attached to the left hand edge of the large WebSphere box, is a vertical bar labeled "notification broker". The publisher, subscriber and notification consumer boxes are each connected to the notification broker by arrows labeled "SOAP over HTTP". The publisher, subscriber and notification consumer are unaware that the broker is backed by WebSphere Application Server.

The following diagram illustrates the variety of clients that are able to connect to the notification broker provided by WebSphere Application Server. Any Web service client that implements or invokes the WS-Notification message exchanges can connect. This includes the various types of Web service clients that are supported directly by WebSphere Application Server (such as JAX-RPC, JSR172, JSR101) and other Web service clients that are capable of using JAX-RPC patterns (for example .NET).

This diagram is very similar to the previous one. The differences are that there are now four small boxes to the left, labeled "J2EE Publisher", "JSR172 Publisher", "JSR101 Publisher" and ".NET Publisher", and the arrows that connect these boxes to the notification broker are not labeled.

In this use pattern it is possible that none of the clients of the notification broker are written or hosted in a WebSphere Application Server environment, as shown in the following diagram. Note that the notification broker itself cannot determine the environment from which the clients connect because the only interaction is through the standard Web service exchanges defined by WS-Notification.

This diagram is very similar to the previous one. The differences are that there are now two small boxes to the left, labeled "non-IBM notification producer" and "non-IBM notification consumer"; the arrow pointing from the non-IBM producer to the notification broker is labeled "Notify", and the arrow pointing from the notification broker to the non-IBM consumer is labeled "Notify (as the result of a subscription)".

Similarly, WS-Notification applications written or hosted in a WebSphere Application Server environment (such as JAX-RPC from AppClient, JSR172, JSR101) can connect to non-IBM NotificationBrokers (or NotificationProducers) without any changes to the application code.

Related tasks
Configuring a WS-Notification service for use only by WS-Notification applications
WS-Notification - publish and subscribe messaging for Web services
Learning about WS-Notification
Securing WS-Notification
Related reference
WS-Notification roles and goals
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_scen1.html

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