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

Provide highly available (HA) topologies for WS-Notification

Configure a highly available (HA) server topology that supports clients connecting through the WS-Notification standard.

WAS enables server topologies in which WS-Notification applications can continue their operations with a different server in the event of a server failure.

To achieve this topology you configure a WAS proxy server as the central point to which applications connect, providing it with knowledge of the clustered servers to which requests can be routed and how they are affected by failover, in accordance with the High availability topology.

To configure a highly available (HA) server topology for WS-Notification...

Procedure

1. Create an application server cluster within a cell.

2. Create a service integration bus within the same cell.

3. Configure a WS-Notification service on the bus.

   • For JAX-WS based v7.0 WS-Notification services, see Create a new v7.0 WS-Notification service.

   • For JAX-RPC based v6.1 WS-Notification services, see Create a new v6.1 WS-Notification service.

4. Add the cluster as a bus member.

5. Configure a "One of N" policy for the messaging engine in the cluster.

6. Add the server cluster as a WS-Notification service point by creating a new WS-Notification service point and selecting the required bus member (that is, the server cluster) from the drop-down list.

   • For JAX-WS based v7.0 WS-Notification services, see Create a new v7.0 WS-Notification service point.

   • For JAX-RPC based v6.1 WS-Notification services, see Create a new v6.1 WS-Notification service point.

7. 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.
8. 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. This causes requests for the WS-Notification service point to follow the endpoint as it fails across between servers in the cluster.

   For information about how to do this, see one of the following topics:

   • For applications associated with v7.0 WS-Notification service points, see Use URL resources within an application.

   • For inbound services associated with v6.1 WS-Notification services, see Modify an existing endpoint listener configuration.

WS-Notification in a clustered environment
WS-Notification
High availability and workload sharing for service integration technologies
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification

Related

WS-Notification roles and goals
http://www.research.ibm.com/journal/sj/444/niblett.html
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn
WS-Notification troubleshooting tips

+

Search Tips   |   Advanced Search