Creating a new WS-Notification service

Create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. A WS-Notification service provides access to service integration bus resources for Web services publish and subscribe clients.

Before you begin

Ensure that you have successfully configured an SDO repository, as described in Installing and configuring the SDO repository. The SDO repository is used to store WSDL documents during the creation of the WS-Notification service. If you do not configure the repository, an error message appears when you create the service.

You can create a new WS-Notification service through the administrative console as described in this task, or you can create a new WS-Notification service through the command line.

This task assumes that you 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 you can configure more than one. For more information, see Reasons to create multiple WS-Notification services in a bus.

Defining a WS-Notification service on a bus is not the same as exposing a NotificationBroker (WSDL) port to which Web services applications can connect. To do this, create one or more WS-Notification service points as described in this task.

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

A JAX-RPC handler list and WS-Security bindings define the parameters and security policy that are used when making outbound Web service invocations. These invocations include operations such as outbound event notification (in response to a subscribe operation) and controlling demand based publishers (subscribe, pause and resume).

When a WS-Notification service is created, three inbound services are configured for the WS-Notification service, one for each of the three WS-Notification service roles:
  • Notification broker
  • Subscription manager
  • Publisher registration manager
These inbound services are defined on the same service integration bus as the WS-Notification service, and each of these inbound services refers to the same bus destination. Usually, a bus destination can be used as described in Learning about bus destinations. However, this is not the case for WS-Notification. This destination does not relate to the topics for which the WS-Notification service can handle requests and you should not alter or mediate the destination. In WS-Notification, the configuring of topics is handled through topic namespaces. For more information, see Creating a new permanent WS-Notification topic namespace.

To create a new WS-Notification service use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Service integration > Web services > WS-Notification services or Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services. The WS-Notification services [Collection] form is displayed.
  2. In the content pane, click New. The New WS-Notification service wizard is displayed. For more information about the properties that you set with the wizard, see WS-Notification services [Settings].
  3. 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).
    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 that are 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.

      Note: 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 you 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. If no buses exist, provide the name for a new one; a default name of this_service_nameBus is offered.
    5. Click Next.
  4. Step 2: Configure JAX-RPC handler and Web services security settings. These settings are applied to the event notifications exchanged with WS-Notification client applications.
    1. 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 servce. That is, the name of the bus topic space that is 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.
    2. Optional: Choose a JAX-RPC handler list. The JAX-RPC handler list that is applied to inbound service requests for the WS-Notification service. For more information about handler lists, see Working with JAX-RPC handlers and clients.
    3. Optional: Choose a WS-Security configuration and bindings:
      Outbound security request binding
      The security binding to be used with consumer notifications and remote publisher requests sent by this WS-Notification service.
      Outbound security response binding
      The security binding to be used with remote publisher responses received by this WS-Notification service.
      Outbound security configuration
      Specifies the details of how security is applied to requests and responses.
      For more information about Web services security resources, see Configuring secure transmission of SOAP messages using WS-Security.
    4. Click Next.
  5. Step 3: 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 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 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 a listener application to use to expose the service. Either select an existing endpoint listener for this bus member, or Create a new endpoint listener. For more information, see Creating a new endpoint listener configuration.
    4. Click Next. The new service point is added to the list of service points for this WS-Notification service.
    5. Optional: To create another service point, repeat the previous substeps.
    6. When you have finished creating service points for this WS-Notification service, select No for the option to create another service point, then click Next.
  6. Optional: Step 4: Create permanent topic namespaces. For more information, see Permanent topic namespace. When you create a new permanent WS-Notification topic namespace, you 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. You 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 that you want 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 offered default name of this_service_nameTopicSpace for a new 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) that is assigned to messages published using this topic namespace. You can 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 WS-Notification service, and you are asked whether you want to create another permanent topic namespace (default is Yes).
    6. Optional: To create another permanent topic namespace, repeat the previous substeps.
    7. When you have finished creating permanent topic namespaces for this WS-Notification service, select No for the option to create another permanent topic namespace, then click Next.
  7. Step 5: Summary. Check that the summary of the actions taken by the wizard is as you expected, then click Finish. If the processing completes successfully, the list of WS-Notification services is updated to include the new WS-Notification service. Otherwise, an error message is displayed.
  8. Save your changes to the master configuration. 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.

What to do next

To perform advanced configuration tasks for this WS-Notification service (for example adding additional WS-Notification service points, or applying topic namespace documents to permanent topic namespaces), see Modifying a WS-Notification service.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tjwsn_wsnserv_new
File name: tjwsn_wsnserv_new.html