Configure a server topology such that Web service clients
using the WS-Notification standard are workload-balanced across the
available resources.
About this task
WS-Notification enables server topologies in which Web
service clients connecting to the notification broker inbound service
are distributed across a set of logically equivalent servers. This
configuration is described in the Network deployment of WS-Notification use pattern. You achieve
this configuration by deploying a WS-Notification service across multiple
servers in a network deployment environment,
then configuring a WebSphere® Application
Server 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, complete the following steps:
Procedure
- Use the task Configuring a WS-Notification service for use only by WS-Notification applications to
create a fully-configured WS-Notification service that contains 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 you must configure it to route requests to the
cluster, which might include configuring
the virtual host settings.
- Ensure that the URL root of
each endpoint listener 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 more
information, see Modifying an existing endpoint listener configuration.
Results
Requests for the notification broker inbound service are automatically
work load balanced 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.