WS-Notification roles and goals

This topics lists a set of computing roles that members of your organization might perform, and explains 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:
  • Service Oriented Architecture (SOA)
  • Enterprise Service Bus (ESB)

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 by 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:

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 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 tasks
Using WS-Notification for publish and subscribe messaging for web services
Securing WS-Notification
Accomplishing common WS-Notification tasks
Developing applications that use WS-Notification
Providing access for WS-Notification applications to an existing bus topic space
Configuring a WS-Notification service for use only by WS-Notification applications
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 of Use | Feedback

Last updatedLast updated: Sep 19, 2011 7:16:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=rjwsn_rolesandgoals
File name: rjwsn_rolesandgoals.html