WAS v8.5 > Reference > Administrator best practices

WS-Notification roles and goals

This topics lists a set of computing roles that members of your organization might perform, and explains how we can use WS-Notification to help meet the goals of each role.

For a general description of each of the following roles, see WAS roles and goals.


Enterprise architect

IT environments are currently evolving towards the following concepts:

The goal of the enterprise architect might be to guide their organization towards appropriate utilization of these concepts to maximize the efficiency and responsiveness of the business as a whole.

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

The main goal of the solution architect is to design a solution that supports the specification set by the enterprise architect. This might include providing an environment in which web service applications can participate in publish and subscribe messaging patterns. This participation might also include the requirement to be able to exchange event notifications between web service clients and other clients of the enterprise service bus.

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


System administrator

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


Application developer

If the solution architect specifies a requirement to insert event notifications into the system (that is publish messages) or receive event notifications from the system as a result of creating a subscription containing an interest profile, then the application developer can use WS-Notification to meet this requirement.

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:

See also Develop applications that use WS-Notification and Filtering the message content of publications.


Related concepts:

WS-Notification
WS-Notification: How client applications interact at runtime
WS-Notification topologies
WS-Notification: Overview


Related


Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Accomplishing common WS-Notification tasks
Develop applications that use WS-Notification


Reference:

Events and service-oriented architecture: The OASIS Web Services Notification specifications

OASIS Web Services Notification (WSN) technical committee
WS-Notification troubleshooting tips
WAS roles and goals


+

Search Tips   |   Advanced Search