Reasons to create multiple WS-Notification services in a bus

In general it is not necessary to create more than one WS-Notification service in each service integration bus, however there are some cases where it is useful to do so.

If you have multiple service integration buses defined in a cell and you want to provide WS-Notification access to messaging resources defined on each of the buses, then you need to define a WS-Notification service on each of the buses. This configuration of one WS-Notification service on each service integration bus that needs WS-Notification access is the recommended approach. It ensures that applications connected to different WS-Notification services cannot pass information to each other, or cause interference.

You might choose to define multiple WS-Notification services on a single bus in order to segregate groups of client applications into disjoint sets, for example to meet one of the requirements listed below. However you should use this pattern with care, because there are significant implications to making this choice - in particular associated with the WS-Notification topic namespaces that are defined on the WS-Notification service. For more information about topic namespace patterns see Options for associating a permanent topic namespace with a bus topic space.




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 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=cjwsn_multi_wsnserv
File name: cjwsn_multi_wsnserv.html