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

Use the administrative console to configure individual WS-Notification services, service points, administered subscribers, permanent topic namespaces, topic namespace documents and JAX-WS handlers.

Decide which method to use to configure these resources. We can configure WS-Notification resources by as described in this task, or by using the commands in the WSNotificationCommands command group .

WS-Notification enables web services to use the publish and subscribe messaging pattern. See WS-Notification: Overview and WS-Notification.

For high-level configuration of WS-Notification, see Accomplishing common WS-Notification tasks. Use the steps for this task to configure individual instances of each type of WS-Notification resource.

You access the WS-Notification panels through the Service integration section of the administrative console navigation pane:

• To see a list of all the WS-Notification services within the cell, click Service integration -> WS-Notification -> Services .

• To see a list of all the WS-Notification services for a particular service integration bus, click Service integration -> Buses -> bus_name -> [Services] WS-Notification services .

To support the Java API for XML-based Web Services (JAX-WS) and composition with WS-ReliableMessaging, you create your WS-Notification services as JAX-WS applications. The implementation of WS-Notification in WAS v6.1 uses JAX-RPC applications, so there are now two different implementations of the WS-Notification service and service point:

• Version 7.0: Use this type of service to compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or to apply JAX-WS handlers to your WS-Notification service. This is the recommended type of service for new deployments. This WS-Notification option has been available in WAS from v7.0.

• Version 6.1: Use this type of service to expose a JAX-RPC WS-Notification service that uses the same technology provided in WAS v6.1, including the ability to apply JAX-RPC handlers to the service. This WS-Notification option has been available in WAS from v6.1.

To configure specific WS-Notification resources, use the administrative console to complete any of the following tasks:

Procedure

• Configure a WS-Notification service.

  Complete any of the following tasks:

  • Create a new Version 7.0 WS-Notification service.

  • Modify a Version 7.0 WS-Notification service.

  • Create a new Version 6.1 WS-Notification service.

  • Modify a Version 6.1 WS-Notification service.

  • Delete WS-Notification services.

• Configure a WS-Notification service point.

  Complete any of the following tasks:

  • Create a new v7.0 WS-Notification service point.

  • Modify a Version 7.0 WS-Notification service point.

  • Create a new Version 6.1 WS-Notification service point.

  • Modify a Version 6.1 WS-Notification service point.

  • Delete WS-Notification service points.

• Configure a WS-Notification administered subscriber.

  Complete any of the following tasks:

  • Create a new WS-Notification administered subscriber.

  • Modify a WS-Notification administered subscriber.

  • Delete WS-Notification administered subscribers.

• Configure a permanent WS-Notification topic namespace.

  Complete any of the following tasks:

  • Create a new permanent WS-Notification topic namespace.

  • Show the properties of a permanent WS-Notification topic namespace.

  • Delete WS-Notification permanent topic namespaces.

• Configure a WS-Notification topic namespace document.

  Complete any of the following tasks:

  • Apply a WS-Notification topic namespace document.

  • Show the contents of a WS-Notification topic namespace document.

  • Delete WS-Notification topic namespace documents.

• Configure JAX-WS handlers and handler lists.

  Complete any of the following tasks:

  • Load JAX-WS handler classes.

  • Create a new JAX-WS handler configuration.

  • Modify an existing JAX-WS handler configuration.

  • Delete JAX-WS handler configurations.

  • Create a new JAX-WS handler list.

  • Modify an existing JAX-WS handler list.

  • Delete JAX-WS handler lists.

• Create a new v7.0 WS-Notification service

  Create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. Use this type of service to compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or to apply JAX-WS handlers to your WS-Notification service. This is the recommended type of service for new deployments. This WS-Notification option has been available in WAS from v7.0.

• Create a new v6.1 WS-Notification service

  Create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. Use this type of service to expose a JAX-RPC WS-Notification service that uses the same technology provided in WAS v6.1, including the ability to apply JAX-RPC handlers to the service. This WS-Notification option has been available in WAS from v6.1.

• Create a new v7.0 WS-Notification service point

  We can add an additional v7.0 WS-Notification service point to an existing v7.0 WS-Notification service. 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 on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.

• Create a new v6.1 WS-Notification service point

  We can add an additional v6.1 WS-Notification service point to an existing v6.1 WS-Notification service. 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 on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.

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

• Create a new WS-Notification permanent topic namespace

  Create a new permanent topic namespace. A topic namespace is a grouping of topics that allows information to be shared between applications. 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.

• Apply a WS-Notification topic namespace document

  A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace. Use the administrative console to apply a topic namespace document to an existing topic namespace.

• Publish the WSDL files for a WS-Notification application to a compressed file

  Use the administrative console to download a compressed file with a .zip file extension that contains the published WSDL files for a WS-Notification application.

• Configure JAX-WS handlers

  A JAX-WS handler is a Java class that performs a range of handling tasks. For example: logging messages, or transforming their contents, or terminating an incoming request. We can create JAX-WS handlers, chain them together in the form of a handler list, then apply the handler list to a JAX-WS based v7.0 WS-Notification service point (for inbound invocation handling) or WS-Notification service (for outbound invocation handling).

WS-Notification
WS-Notification: How client applications interact at runtime
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification

Related

WSNotificationCommands command group
WS-Notification troubleshooting tips

+

Search Tips   |   Advanced Search