Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Notification (WS-Notification) > Use WS-Notification for publish and subscribe messaging for web services > Configure WS-Notification resources > Configure WS-Notification resources by
Create a new WS-Notification 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.
Decide which method to use to configure these resources. We can create a new administered subscriber by as described in this task, or by using the createWSNAdministeredSubscriber command.
You should not define an administered subscriber for any of the endpoints exposed by the WS-Notification service on which it is being defined, because this would result in infinite looping of messages through the notification broker.
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 enables you to pre-configure links between the NotificationBroker and a NotificationProducer, which can be a remote NotificationBroker or a NotificationProducer application.
To create a new administered subscriber, use the administrative console...
Procedure
- In the navigation pane, click Service integration -> WS-Notification -> Services -> service_name -> [Additional Properties] WS-Notification service points -> point_name -> Administered subscribers or Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Additional Properties] WS-Notification service points -> point_name -> Administered subscribers . The Administered subscribers [Collection] form is displayed.
- In the content pane, click New.
- Specify the following properties for this administered subscriber.
- External web service endpoint
- The URL of the external web service to which the service should subscribe. That is, the endpoint reference (web address) of a notification producer or notification broker application. For example http://remoteproducer.com.
- Dialect
- The dialect in which the topic is expressed. The options are Simple, Concrete, or Full, as defined by the WS-Topics standard.
- Topic
- The topic on which the service should subscribe. This describes the class of notification messages that are delivered to the WS-Notification service point. For example stock/IBM. This property can include wildcards if they are supported by the topic dialect that you select.
- Topic namespace
- The URI that describes the topic namespace in which the specified topic is defined.
- Remote subscription timeout
- The length of time in hours after which the remote subscription will expire if not renewed by the server. This timeout minimizes the potential for orphaned subscriptions in the remote web service if the local server is uninstalled. Note that this field does not indicate the time at which the remote subscription is due to expire. Set the timeout length to something larger than the maximum length of time that the server is expected to remain offline, otherwise the stream of messages from the remote web service might be interrupted. While the server is running it occasionally renews the remote subscription termination time (with the specified timeout) to prevent it from expiring during normal operation. If not specified, this timeout defaults to 24 (hours).
- Click OK. If the processing completes successfully, the list of administered subscribers associated with the WS-Notification service point is updated to include the new administered subscriber. Otherwise, an error message is displayed.
- Save your changes to the master configuration.
What to do next
We can also use the administrative console to list runtime information for administered subscribers. See List active WS-Notification administered subscribers.
- Modify a WS-Notification 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.
- Delete WS-Notification administered subscribers
Delete one or more WS-Notification administered subscribers. An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.
WS-Notification
WS-Topics
List active WS-Notification administered subscribers
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Related
listWSNAdministeredSubscribers command
createWSNAdministeredSubscriber command
showWSNAdministeredSubscriber command
http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-os.pdf
WS-Notification troubleshooting tips
Administered subscribers [Settings]