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
Configure a QoS-partitioned server topology for WS-Notification
Create multiple WS-Notification services and instantiate WS-Notification service points on different servers in the cell depending upon the quality of service (QoS) that is required. This task assumes that you, or your solution architect, have already designed a QoS-partitioned server topology or designed a server topology for web service qualities of service for WS-Notification, and you therefore have a well-defined set of criteria for the different types of QoS that must be fulfilled by the server topology, and a configuration design 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 enables partitioned topologies in which some servers provide a different quality of service that can be used by customers of varying status. For example you might configure a cluster of servers for use by a particular customer in order to provide enhanced HA facility or improved response times.
Procedure
- Configure a cell containing multiple servers that can support the QoS requirements.
- Configure one or more service integration buses in the cell.
- Learn about the options that exist for partitioning access to messaging resources and defining non-overlapping WS-Notification services.
- We can define multiple WS-Notification services on a single service integration bus. By ensuring topic namespaces defined by the two (or more) services do not make use of the same service integration bus topic spaces you can ensure that there is no possibility for communication between the clients of respective WS-Notification services.
- We can also define multiple service integration buses and configure a single WS-Notification service on each. The choice of which of these two options to use depends upon the existing messaging infrastructure, and the enterprise's policy towards creation of multiple service integration buses.
- Allocate service integration bus members and WS-Notification service points to appropriate servers in the cell in order to provide the required speed of response to requests. For example a faster response time will require the elements to be deployed on faster (or less heavily loaded) hardware.
- Configure appropriate advanced settings associated with the WS-Notification service point to provide other QoS requirements such as security and reliability.
- For JAX-WS based v7.0 WS-Notification service points, attach policy sets to the application associated with the service point to provide these other QoS requirements. For example, the reliable secure profile default policy sets (WS-I RSP and WS-I RSP ND) contain instances of the secure conversation and reliable messaging policies that are configured to work together.
- For JAX-RPC based v6.1 WS-Notification service points, configure the inbound ports associated with the service point to provide these other QoS requirements.
WS-Notification
Configure a v7.0 WS-Notification service with Web service QoS
Design a QoS-partitioned server topology for WS-Notification
Design a server topology for web service qualities of service 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