Network Deployment (Distributed operating systems), v8.0 > 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 you 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:
- 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.
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:
- 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. 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 and Design a server topology for web service qualities of service for WS-Notification.
System administrator
For the specific steps that 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.
- Balancing 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
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:
- 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 Develop applications that use WS-Notification and Filter the message content of publications.
WS-Notification
WS-Notification: How client applications interact at runtime
WS-Notification topologies
WS-Notification: Overview
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
Interacting at run time with WS-Notification
Configure a v7.0 WS-Notification service with Web service QoS
Design a QoS-partitioned server topology for WS-Notification
Design a server topology for web service qualities of service for WS-Notification
Balancing a WS-Notification workload across application servers
Provide highly available (HA) topologies for WS-Notification
Configure a QoS-partitioned server topology for WS-Notification
Provide access for WS-Notification applications to an existing bus topic space
Configure a WS-Notification service for use only by WS-Notification applications
Delete WS-Notification services
Delete WS-Notification permanent topic namespaces
Related
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
WAS roles and goals