WAS v8.5 > 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

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 WebSphere Application Server from v7.0.

Decide which method to use to configure these resources. We can create a new v7.0 WS-Notification service using the administrative console as described in this task, or using the createWSNService command.

This task assumes that we have an existing service integration bus, configured with at least one bus member.

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

Defining a v7.0 WS-Notification service is not the same as exposing a NotificationBroker (WSDL) port to which web services applications can connect. To do this, create one or more v7.0 WS-Notification service points as described in this task. 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.

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, then use this task to create a v7.0 WS-Notification service, one or more service points, and (optionally) a permanent topic namespace.

We can also apply JAX-WS handler lists to WS-Notification service points (for inbound invocation handling) and WS-Notification services (for outbound invocation handling).

When creating a v7.0 WS-Notification service, the wizard creates and deploys a JAX-WS based provider application. This application exposes the WS-Notification web service interfaces for each of the three WS-Notification service roles:

• Notification broker
• Subscription manager
• Publisher registration manager

1. Start the dmgr console.
2. Navigate to Service integration -> WS-Notification -> Services or Service integration -> Buses -> bus_name -> [Services] WS-Notification services. The WS-Notification services [Collection] form is displayed.
3. In the content pane, click New. The "New WS-Notification service" wizard is displayed. For more information about the properties set with the wizard, see WS-Notification services [Settings].
4. Step 1: Configure name, description, service integration bus and dynamic topic namespace settings.

   1. Enter your chosen name and an optional description.

      The name forms part of the endpoint on which the service is exposed (that is, the URL used to access the WS-Notification service points that are defined under the service). For v6.1 WS-Notification services, the service name is unique within a bus. For v7.0 WS-Notification services the service name is unique within the cell, which matches the administration model used for policy sets and therefore supports composition of v7.0 WS-Notification services with WS-ReliableMessaging.

   2. Select or deselect the option Enable dynamic topic namespaces?.

      Indicates whether dynamic topic namespaces can be used within the WS-Notification service. That is, whether this service allows dynamic topic namespaces to be created at run time. For more information, see Dynamic topic namespace.

      Use this option to tightly control the topic namespaces used when connecting to a particular WS-Notification service (for example for security or auditing requirements). If you deselect this option, any applications that connect to the WS-Notification service and request topics from a dynamic topic namespace are stopped from publishing or receiving messages.

      All messages published to a dynamic topic namespace are inserted with the default message reliability setting of reliable persistent. If this value is not acceptable, create a permanent topic namespace and manually configure the attribute to the appropriate value.

      The dynamic topic namespaces used on a particular WS-Notification service are backed by a service integration bus topic space that is created automatically when we create the topic namespace. The syntax of topics used within this topic space is internal to the WS-Notification service implementation.

   3. Select or deselect the option Requires registration.

      Indicates whether publisher applications are required to register with the broker before they can publish notifications.

   4. Select a service integration bus from the drop-down list.

   5. Click Next.

5. Step 2: Select WS-Notification service type.

   Select v7.0 as the type of service to create.

6. Step 3: Configure handler and web service policy settings.

   These settings are applied to the event notifications exchanged with WS-Notification client applications.

   1. Optional: Choose a JAX-WS handler list.

      The JAX-WS handler list that is applied to outbound requests from the WS-Notification service. A handler list defines the handlers that are applied when making outbound web service invocations, for example monitoring outbound event notification (in response to a subscribe operation) and controlling demand-based publishers (subscribe, pause and resume). For more information about handler lists, see Configure JAX-WS handlers.

   2. Enable or clear the Query WSDL option.

      Indicates whether the v7.0 WS-Notification service queries the WSDL of other WS-Notification web services when interacting with them. By default, this option is enabled. By clearing this option, we can improve performance by avoiding expensive WSDL queries. However, you should note the following considerations when WSDL querying is not enabled:

      • WS-Notification attempts to discover binding information (which is usually discovered through the WSDL) using other means. WS-Notification uses the SOAP version associated with the WS-Notification service point where subscriptions were made (by other web services), or where administered subscriptions were created (by an administrator).
      • There are some circumstances in which WS-Notification might be unable to determine binding information. This can happen when cleaning up subscriptions where the associated service point has been deleted and configuration information is no longer available. Under these circumstances WS-Notification makes a "best guess" at binding information to use to clean up the subscriptions.
      • There is one scenario where incorrect binding information is used. That is, when a subscriber subscribes to use a particular SOAP binding, on behalf of a NotificationConsumer that expects notifications through a different SOAP binding.

   3. Enter a dynamic topic space name.

      The name of the service integration bus topic space to be used as the dynamic topic space for this WS-Notification service. That is, the name of the bus topic space used to host the ad-hoc topic namespace, and to host dynamic topic namespaces if they are permitted. A default name of WSN_dynamic_this_service_name is offered.

   4. Click Next.

7. Step 4: Create WS-Notification service points.

   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. For more information, see WS-Notification service point.

   1. Select Yes to create a new WS-Notification service point, then click Next.

      A WS-Notification service must have at least one service point.

   2. Supply a name and (optional) description for the WS-Notification service point, and from the drop-down list select the bus member on which the service point is to be configured, then click Next.

      The service point name forms part of the URL used to access the service point. On a single server system there is only one bus member in the list.

   3. Select the transport settings for the new service point.
      

      Service point accessed via HTTP proxy

      If the service point is accessed through a proxy, select the check box, and type the root of the externally visible endpoint address URL for web services accessed through this endpoint.

      The URL for the proxy is used to populate the WSDL endpoint address fields when publishing WSDL files to a compressed file.

      SOAP Version

      Select the version of SOAP that is supported by the service point. This affects the WSDL definition that is exposed by the web service.

   4. Optional: Select the JAX-WS handler list settings for the new service point.
      

      NotificationBroker JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the NotificationBroker endpoint of the WS-Notification service point.

      SubscriptionManager JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the SubscriptionManager endpoint of the WS-Notification service point.

      PublisherRegistrationManager JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the PublisherRegistrationManager endpoint of the WS-Notification service point.

   5. Click Next. The new service point is added to the list of service points for this WS-Notification service.

   6. Optional: To create another service point, repeat the previous substeps.

   7. When we have finished creating service points for this WS-Notification service, select No for the option to create another service point, then click Next.

8. Optional: Step 5: Create permanent topic namespaces.

   For more information, see Permanent topic namespace. When creating a new WS-Notification permanent topic namespace, we specify the namespace and associate it with one of the service integration bus topic spaces configured on the bus on which the parent WS-Notification service is defined. We cannot modify a permanent topic namespace after it has been created, other than to apply or remove topic namespace documents.

   1. Select Yes to create a new permanent topic namespace, then click Next.

   2. Enter a name for the permanent topic namespace.

      This is the URI by which WS-Notification applications refer to topics hosted by this namespace.

   3. Associate this new permanent topic namespace with the service integration bus topic space to use to publish and receive messages.

      From the service integration bus topic space drop-down list, complete one of the following actions:

      • Select the name of an existing bus topic space.

      • Select the option to Create a new topic space, then enter a name for the new topic space.

   4. Select from the drop-down list the service integration bus reliability (quality of service) assigned to messages published through this topic namespace.

      Choose one of five values, each representing one of the service integration bus message reliability levels. The default value is reliable persistent, which is the value used by default for JMS Persistent messages.

   5. Click Next.

      The new permanent topic namespace is added to a list of permanent topic namespaces for this v7.0 WS-Notification service, and you are asked whether to create another permanent topic namespace (default is Yes).

   6. Optional: To create another permanent topic namespace, repeat the previous substeps.

   7. When we have finished creating permanent topic namespaces for this v7.0 WS-Notification service, select No for the option to create another permanent topic namespace, then click Next.

9. Step 6: Summary.

   Check the summary of the actions taken by the wizard is as you expected, then click Finish. If the processing completes successfully, the list of v7.0 WS-Notification services is updated to include the new v7.0 WS-Notification service. Otherwise, an error message is displayed.

10. Save your changes to the master configuration.
    

11. Optional: Restart the server if either of the following conditions apply:
    • A new bus or new bus member has been created as part of this task.
    • Configuration reload is not enabled for the bus.

To undertake advanced configuration tasks for this WS-Notification service (for example, adding additional service points and applying topic namespace documents to permanent topic namespaces), see Modify a v7.0 WS-Notification service.

To undertake advanced configuration tasks for the WS-Notification service point created as part of this task (for example, adding administered subscribers, publishing WSDL files to a compressed file, and configuring the enterprise application associated with this service point), see Modify a v7.0 WS-Notification service point.

To configure this WS-Notification service or service point with web service qualities of service (QoS) such as reliability or security, see Configure a v7.0 WS-Notification service with Web service QoS.

Subtopics

• Modify a v7.0 WS-Notification service
  Modify the description, Enabled dynamic topic namespaces?, Requires registration, JAX-WS handler list and Query WSDL properties of a v7.0 WS-Notification service, and follow links to complete advanced configuration such as adding additional WS-Notification service points, applying topic namespace documents to permanent topic namespaces, and applying policy sets to enable WS-ReliableMessaging.
• Delete WS-Notification services
  Remove all configuration associated with one or more WS-Notification services. A WS-Notification service provides access to service integration bus resources for web services publish and subscribe clients.

Related concepts:

WS-Notification
WS-Notification and policy set configuration
WS-ReliableMessaging default policy sets

Related

Create a new v6.1 WS-Notification service
Create a new v7.0 WS-Notification service point
Create a new v6.1 WS-Notification service point
Create a new WS-Notification administered subscriber
Create a new WS-Notification permanent topic namespace
Applying a WS-Notification topic namespace document
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Configure a v7.0 WS-Notification service with Web service QoS
Manage policy sets
Add assured delivery to web services through WS-ReliableMessaging

Reference:

WS-Notification troubleshooting tips

WS-Topics v1.3 OASIS Standard

Related information:

Publishing the WSDL files for a WS-Notification application to a compressed file
Configure JAX-WS handlers

+

Search Tips   |   Advanced Search