Reasons to create multiple WS-Notification service points

There are two main cases in which you might want to create more than one WS-Notification service point for a given WS-Notification service.

These two cases are as follows:

To provide WS-Notification access through more than one server in the cell, you must define at most one WS-Notification service point for each server in the cell. This enables work load balancing, either on the basis of manual distribution of clients across servers, or automatically as described in the Load balanced topology. Note that, for some or many servers, you might not define a service point at all.

To provide a mechanism through which WS-Notification applications can connect to the same server, by using different bindings or security parameters, you must define more than one WS-Notification service point on a particular server, then channel particular applications through particular service points. There are two further sub-cases to this option:




Related concepts
WS-Notification
Related tasks
Using WS-Notification for publish and subscribe messaging for web services
Securing WS-Notification
Creating a new Version 6.1 WS-Notification service point
Interacting at run time with WS-Notification
Related reference
WS-Notification troubleshooting tips
createWSNServicePoint command
Related information
WS-Notification service points [Settings]
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=cjwsn_multi_wsnservpt
File name: cjwsn_multi_wsnservpt.html