+

Search Tips   |   Advanced Search

Creating a new WS-Notification administered subscriber

As part of the configuration of a WS-Notification service point we 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 using the console as described in this task, or 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 console to complete the following steps:

  1. 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.

  2. In the content pane, click New.

  3. 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 selected.

    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).

  4. 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.

  5. Save the changes to the master configuration.


What to do next

We can also use the console to list runtime information for administered subscribers. For more information, see Listing active WS-Notification administered subscribers.


Subtopics


Related concepts

  • WS-Notification
  • WS-Topics


    Related tasks

  • Create a new Version 7.0 WS-Notification service
  • Create a new Version 6.1 WS-Notification service
  • Create a new Version 7.0 WS-Notification service point
  • Create a new Version 6.1 WS-Notification service point
  • Create a new WS-Notification permanent topic namespace
  • Apply a WS-Notification topic namespace document
  • Use WS-Notification for publish and subscribe messaging for web services
  • Secure WS-Notification
  • Listing active WS-Notification administered subscribers

  • WS-Notification troubleshooting tips
  • createWSNAdministeredSubscriber command
  • listWSNAdministeredSubscribers command
  • showWSNAdministeredSubscriber command
  • WS-Topics Version 1.3 OASIS Standard


    Related information:

  • Publish the WSDL files for a WS-Notification application to a compressed file
  • Configure JAX-WS handlers
  • Administered subscribers [Settings]