WS-Notification roles and goals

A set of computing roles that members of your organization might perform, and how you can use WS-Notification to help meet the goals of each role.

For a general description of each of the following roles, see WebSphere® Application Server 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.

WebSphere Application Server 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:
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. For more information, see Designing a QoS-partitioned server topology for WS-Notification.

System administrator

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 that are 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 Developing applications that use WS-Notification.



Related concepts
Learning about WS-Notification
Related tasks
WS-Notification - publish and subscribe messaging for Web services
Securing WS-Notification
Accomplishing common WS-Notification tasks
Related reference
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
WebSphere Application Server roles and goals
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=rjwsn_rolesandgoals
File name: rjwsn_rolesandgoals.html