Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Notification (WS-Notification) > Use WS-Notification for publish and subscribe messaging for web services > Accomplishing common WS-Notification tasks
Design a QoS-partitioned server topology for WS-Notification
Design a server topology in which customers receive quality of service (QoS) that reflects their customer status.
WS-Notification enables partitioned topologies in which some servers provide a different quality of service that can be used by customers of varying status. This might include configuring a cluster of servers for use by a particular customer in order to provide enhanced high availability or improved response times.
In the specific cases where you need Web services qualities of service, such as reliability, see also Design a server topology for web service qualities of service for WS-Notification.
Procedure
- Get a statement of the qualities of service required by each of the applications and customers that use WS-Notification.
- Identify, from the statements you collected in the previous step, the distinct groups of QoS requirements.
- Specify that higher QoS groups be isolated onto separate servers, and that a separate WS-Notification service must be defined on these servers that can only be accessed by the required applications.
- Design a configuration such that service integration bus topic spaces used by the different brokers do not overlap in cases where applications with one QoS should be isolated from others.
WS-Notification
Configure a v7.0 WS-Notification service with Web service QoS
Design a server topology for web service qualities of service for WS-Notification
Configure a QoS-partitioned server topology for WS-Notification
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Related
WS-Notification roles and goals
WS-Notification troubleshooting tips