Balancing a WS-Notification workload across application servers
Configure a server topology such that the workload for web service clients that use the WS-Notification standard is balanced across the available resources.
WS-Notification enables server topologies in which web service clients connecting to the notification broker service are distributed across a set of logically equivalent servers. This configuration is described in the Network deployment of WS-Notification topology. You achieve this configuration by deploying a WS-Notification service across multiple servers in a network deployment environment, then configuring a WAS proxy server as the central point to which applications connect, and providing it with the knowledge of which servers should receive client requests (that is, where the WS-Notification service points are configured).
To configure a distributed connected servers WS-Notification solution...
- Use the task Configure a WS-Notification service for use only by WS-Notification applications to create a fully-configured WS-Notification service containing two or more WS-Notification service points on different servers.
- Create a proxy server inside the cell on which the WS-Notification service is defined. After the proxy is created configure it to route requests to the cluster, which might include configuring the virtual host settings.
- Ensure that the URL root of each endpoint accurately reflects the details of the proxy server, so that applications requesting the WSDL for the service use the proxy server as the external entry point to the service.
For information about how to do this, see one of the following topics:
- For applications associated with Version 7.0 WS-Notification service points, see Use URL resources within an application.
- For inbound services associated with Version 6.1 WS-Notification services, see Modify an existing endpoint listener configuration.
Results
Requests for the notification broker service are automatically shared across the available servers. When affinity with a particular server is established, for example by creating a subscription, information is stored in the WS-Addressing endpoint reference given to the application client. Consequently, subsequent requests that relate to that subscription are automatically returned to the same server.
Related concepts
WS-Notification Network deployment of WS-Notification topology
Related tasks
Use WS-Notification for publish and subscribe messaging for web services Secure WS-Notification
WS-Notification troubleshooting tips WS-Notification roles and goals Events and service-oriented architecture: The OASIS Web Services Notification specifications OASIS Web Services Notification (WSN) technical committee