WS-Notification roles and goals

Enterprise architect

IT environments are currently evolving towards the following concepts:

• Service Oriented Architecture (SOA)

• Enterprise Service Bus (ESB)

WS-Notification enables publish and subscribe communication patterns (such as a stock ticker) to be exposed using web services in an SOA environment. This is done through open standards, enabling straightforward replacement of the service implementation. It promotes easy exchange of data between suppliers and customers through use of standard web service operations and prevents vendor lock-in or adoption of proprietary standards.

WAS also allows WS-Notification to be used as an on- or off-ramp to an ESB, providing seamless interchange of data between different types of client connected to the bus.

Solution architect

To create a design, the solution architect completes the following broad steps:

• Learn about the support provided for WS-Notification in WAS.

• Select a hardware and software product combination for the enterprise that supports the WS-Notification standards.
• Design a server topology to host the applications, in accordance with the particular WS-Notification topologies that are to be implemented.

Additional goals of the solution architect during the system design phase are as follows:

• To cater for the non-functional requirements of the system. For example workload balancing of clients across servers for performance or reliability, and providing services in a highly available fashion. For more information, see WS-Notification in a clustered environment.

• To create an infrastructure in which different qualities of service (QoS) can be offered depending upon business agreements. For example providing a higher QoS to gold-level customers than that provided to standard-level customers. See...
  • Design a QoS-partitioned server topology for WS-Notification
  • Design a server topology for web service qualities of service for WS-Notification

System administrator

For the specific steps the system administrator performs to help implement common WS-Notification tasks, see the following topics:

• Use a script to get up and running quickly with WS-Notification.
• Configure a WS-Notification service for use only by WS-Notification applications.
• Provide access for WS-Notification applications to an existing bus topic space.
• Balance a WS-Notification workload across application servers.
• Provide highly available (HA) topologies for WS-Notification.
• Configure a QoS-partitioned server topology for WS-Notification.
• Secure WS-Notification.
• Configure JAX-WS handlers.
• Apply a JAX-WS handler list to a WS-Notification service.
• Configure a v7.0 WS-Notification service with Web service QoS.
• Configure WS-Notification for reliable notification.
• Migrate a v6.1 WS-Notification configuration from WAS v6.1 to v7.0 or later.
• Prepare a migrated v6.1 WS-Notification configuration for reliable notification.
• Interacting at run time with WS-Notification.
• Publish the WSDL files for a WS-Notification application to a compressed file.

Application developer

There are various patterns of producing and consuming application defined by WS-Notification available for use by the application developer, depending upon the exact requirements of the application in question. These options are explored in the following common WS-Notification tasks:

• Write a WS-Notification application that exposes a web service endpoint.
• Write a WS-Notification application that does not expose a web service endpoint.

See also:

• WAS roles and goals
• Develop applications that use WS-Notification
• Filtering the message content of publications