WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

WebSphere-specific WS-Notification terminology

The terminology defined in this topic is implementation-specific, over and above the terminology defined in the WS-Notification specifications, and applies to the WS-Notification implementation in WebSphere Application Server.

Note: This topic does not include definitions of the messaging and Web services terms that are used from existing WebSphere Application Server components such as service integration technologies.
WS-Notification service

A WS-Notification service provides the ability to expose some or all of the messaging resources defined on a service integration bus for use by WS-Notification applications.

You usually configure one WS-Notification service for a service integration bus, but you can configure more than one. For more information, see Reasons to create multiple WS-Notification services in a bus.

WS-Notification service point

A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified Web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service.

The existence of a WS-Notification service point causes Web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the server with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service. For more information, see Creating a new WS-Notification service point.

You can define any number of WS-Notification service points for a given WS-Notification service. Each service point defined for the same WS-Notification service represents an alternative entry point to the service. Event notifications published to a particular WS-Notification service point are received by all applications connected to any service point of the same WS-Notification service (subject to subscription on the correct topic) regardless of the particular service point to which they are connected. For more information, see Reasons to create multiple WS-Notification service points.

Topic namespace

A topic namespace is a grouping of topics that allows information to be shared between applications. A WS-Notification topic namespace is a logical grouping of topics which is referenced using a namespace URI such as http://www.example.com/widget.

WebSphere Application Server supports two patterns for the creation and use of topic namespaces:
Permanent topic namespace

You use a permanent topic namespace to statically define the association between a WS-Notification topic namespace URI and a service integration bus topic space destination.

A permanent topic namespace has the following characteristics:
  • It enables you to expose an existing service integration bus topic space for use by WS-Notification clients, thus permitting interoperation between the WS-Notification applications and existing publish and subscribe applications connected to the Bus such as JMS.
  • It allows you to restrict the structure and content of the topic namespace by applying one or more topic namespace documents that describe the required structure.
  • It allows the topic namespace to be used as part of a topic space mapping configured on a service integration bus link (between two service integration buses) or a topic mapping as part of a publish and subscribe bridge between a service integration bus and a WebSphere MQ network.

You can also set a configuration attribute of a permanent topic namespace to control the reliability (persistence or non persistence) setting that is applied to any messages inserted using a given topic namespace.

Dynamic topic namespace

A dynamic topic namespace does not require manual administration through the administration console or scripting. A dynamic topic namespace is used automatically in response to a request from a WS-Notification application for a topic namespace URI that has not been defined as a permanent topic namespace (assuming the WS-Notification service has been configured to permit use of dynamic namespaces).

A dynamic topic namespace has the following characteristics:
  • It does not support interoperation between WS-Notification applications and other clients of the bus such as JMS.
  • It is not possible to apply topic namespace documents to this topic space, and thus the structure and content of the topic space are unrestricted.
  • It cannot be used as part of the configuration of service integration bus links or a publish and subscribe bridge.
Administered subscriber
As part of the configuration of a WS-Notification service point you can configure any number of administered subscribers for that service point. An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.

An administered subscriber contains the name of a NotificationProducer application or a (different) NotificationBroker endpoint and details of a subscription request (for example topic) that the WS-Notification service point should register as part of the server startup procedure. This allows you to pre-configure links between the NotificationBroker and a NotificationProducer, which can be a remote NotificationBroker or a NotificationProducer application.

Related tasks
WS-Notification - publish and subscribe messaging for Web services
Learning about WS-Notification
Securing WS-Notification
Related reference
Terminology from the WS-Notification specifications
WS-Notification troubleshooting tips

Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/ref/rjwsn_terms_was.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)